We made the mistake of merging workorders and invoices in v1. It cost us a year. Here’s what we learned.
What a Workorder Actually Is
A workorder is a unit of work for a crew. It answers: What work are we doing, for which crew, on which day?
A local move has one workorder: load, drive, unload, same day. A long-distance move has three: load day, drive day, unload day. A large packing job has four: pack day, load day, drive day, unload day.
Workorders live or die on dispatch. They’re operational documents. The dispatcher assigns them to crews. The crew lead sees them in the mobile app. The dispatcher tracks their completion status. The workorder doesn’t care about money — it cares about work.
Per IBM’s definition: a work order is “a document that describes an authorized maintenance or operational activity that is to be completed by an organization.” Per Microsoft Dynamics 365 Field Service docs: “Work orders are the foundation of field service operations. They organize and track service delivery.”
What an Invoice Actually Is
An invoice is a unit of money owed. It answers: How much does the customer owe, and have they paid?
A 3-day move typically has one invoice. A storage-in-transit job might have one invoice per month of storage — 12 invoices over a year. A multi-phase packing-and-moving job might have two invoices: one for packing, one for the move.
Invoices live or die on accounts receivable. They’re financial documents. The accountant tracks them. They sync to QuickBooks. They have due dates, tax calculations, and payment records. The invoice doesn’t care about crews — it cares about cash.
Why Merging Them Seems Clever and Isn’t
In v1, every workorder was an invoice. One record, two purposes. The logic was: a crew does work, the customer gets billed, why not have one thing that handles both?
The problems started immediately:
A 3-day move has 3 workorders and 1 invoice. Under the merged model, the system generated 3 invoices for a single job. The customer got three bills. The accountant had to manually combine them. Revenue reports triple-counted the job.
A storage-in-transit job has 1 workorder and 12 invoices. Under the merged model, the system couldn’t generate 12 invoices from 1 workorder. The accountant had to create manual invoices outside the system. The revenue tracking broke.
Per-workorder profitability was wrong. Because workorders and invoices were the same record, there was no way to measure crew productivity (workorder-level metric) separately from revenue collection (invoice-level metric). A crew that executed a job efficiently but had a slow-paying customer looked “bad” on both metrics, when only one was actually a crew problem.
QuickBooks sync was a mess. The accounting system expects invoices to represent financial obligations. When we synced workorder-invoice hybrids, QuickBooks treated every one as a separate financial event. Multi-workorder jobs generated duplicate revenue entries. The accountant spent hours reconciling.
What Separating Them Buys You
Per-workorder profitability. Track crew efficiency separately from customer payment behavior. A crew that completes a 3-workorder move on time and under budget is a good crew — regardless of whether the customer paid the invoice on day 1 or day 60.
Per-invoice aging. Track how long it takes customers to pay without confusing the operational timeline. A 90-day-old invoice on a completed job is a collections problem, not an operations problem. Keeping them separate lets you identify the right problem.
Per-job revenue recognition. Revenue belongs to the job, not the workorder or the invoice. A $3,000 job with 3 workorders and 1 invoice should show up once in your revenue report — at $3,000, not $9,000 or $1,000.
What This Looks Like in MoveRight
Workorders live in dispatch. They’re assigned to crews, tracked on the calendar, and completed in the mobile app. The dispatcher sees them, the crew lead executes them, and the ops manager measures crew productivity against them.
Invoices live in finance. They’re generated from the job record, synced to QuickBooks, and tracked for aging. The accountant sees them, the owner monitors them, and the collections process runs off them.
They share a job ID. The job is the parent. The workorders and invoices are children. A job can have many workorders and many invoices. The job’s total revenue is the sum of all invoices. The job’s total work is the sum of all workorders. The two maps are independent but connected.
The QuickBooks Question
What syncs: Invoices. The financial record. The invoice amount, line items, tax, and payment status flow to QuickBooks as standard invoices.
What doesn’t sync: Workorders. The operational record. The crew assignment, the time estimate, the completion status — these stay in MoveRight. QuickBooks doesn’t care about crew productivity. It cares about money.
This separation is deliberate. QuickBooks is an accounting system, not a dispatch system. Syncing operational data into an accounting system creates noise. Keeping the sync to financial records keeps both systems clean.
Demo the workorder-invoice flow with one of our team. 20 minutes, your data.
References:
- IBM — “What Is a Work Order?” — https://www.ibm.com/think/topics/work-order
- Microsoft Dynamics 365 Field Service — Work orders — https://learn.microsoft.com/en-us/dynamics365/field-service/create-work-order
- Salesforce — Work order management — https://www.salesforce.com/products/field-service/resources/organize-your-work-order-management/