October 26, 2026 · 7 min read
QuickBooks Online for Oilfield Service Companies: What to Connect and What to Stop Re-typing
QuickBooks Online is the right accounting system for most oilfield service companies under 200 employees, and the wrong place to build field tickets. The setup that works is QuickBooks for the books (customers, items, invoices, payments, payroll) and a field system for the work (tickets, time, equipment), with the invoice crossing from the field system to QuickBooks once, automatically. Re-typing is where the errors and the days-to-invoice lag come from, so the goal is to make the field ticket the only place a line item is ever typed.
Set up QuickBooks the way the operators bill
Before any sync, three parts of QuickBooks need to match how your customers expect to be invoiced.
- Customers: one customer per operator, with sub-customers only if an operator wants separate invoices per area or AFE. Match the legal name on the MSA.
- Items (products and services): one item per line you bill, such as Roustabout crew hour, Backhoe hour, Water haul per barrel. Rates live in the field system's price book per customer; the QuickBooks item carries the income account.
- Classes or locations: use them for yards or divisions if you run more than one. Do not use them for customers.
What the sync should do
A good integration moves a few things and nothing else.
- Invoices: created in the field system from signed tickets and posted to QuickBooks with the same customer, lines and amounts.
- Customers: created once and reused, so the office never ends up with a duplicate customer.
- Payments: a card or ACH payment on the invoice marks it paid in both systems.
- Nothing else: tickets, timesheets and inspections are operational records and do not belong in the books.
What the sync should not do
It should not push every ticket into QuickBooks as a sales receipt or an estimate. Tickets are operational records; QuickBooks should only see the invoice. It should not change your chart of accounts or create items on its own. And it should not require the office to approve each line in both systems; approval happens once, on the ticket.
Payroll hours
Field time belongs in the field system, tied to the ticket, because that is where billable hours come from. Payroll should receive approved hours as an export in the format your provider uses, whether that is QuickBooks Payroll, Gusto or ADP. Typing hours twice, once for billing and once for payroll, is the second-largest re-typing cost after tickets.
How this looks in Stratorra
Stratorra keeps it one-directional on purpose. Invoices are built from signed tickets in Stratorra, and the owner connects QuickBooks Online once. From then on each invoice posts to QuickBooks with its customer (created there if it is new), its lines and its sales tax on a separate item, and a card or ACH payment taken through the invoice's pay link posts as the payment. Tickets, time and equipment stay in Stratorra; QuickBooks only sees invoices and payments.
Questions
Common questions
Do we need to switch from QuickBooks Desktop?
Stratorra integrates with QuickBooks Online. Companies on Desktop usually move to Online at the same time; Intuit has a migration tool for the move.
Can we keep invoicing from QuickBooks?
You can, but then the office is re-typing tickets. The point of the integration is that the invoice is built from the signed ticket and QuickBooks receives it.
Does anything flow from QuickBooks back into Stratorra?
No. The sync goes one way, from Stratorra to QuickBooks, so the field system never overwrites your books and your bookkeeper stays in charge of QuickBooks.
