Why doesn't the revenue in our field service system match our accounting?
Because they recognize revenue at different moments and count different things. The field service system typically thinks in completed work; accounting thinks in issued invoices and received payments, adjusted for credits, taxes and voids. They should not be equal. The goal is a reconciliation you can explain line by line, not a forced match — and a written rule about which system answers which question.
Different clocks, different definitions
A job completed on the last day of the month and invoiced three days later belongs to different months in the two systems. Progress billing splits one job across periods. A deposit taken in advance is cash in accounting and nothing operationally until work is done.
None of this is an error. It is two systems doing their jobs. The mistake is asking which number is right when the honest answer is that they measure different things.
The usual gap components
- Timing. Completion date versus invoice date versus payment date. Usually the largest single component.
- Tax. Field service totals often include tax; accounting revenue excludes it. Check this first — it explains a surprising share of mismatches.
- Credits, voids and refunds. Frequently applied in accounting only, leaving the operational record showing revenue that was reversed.
- Non-job revenue. Equipment sales, plan billing and miscellaneous income may never touch the field service system.
- Sync failures. Records that never crossed. Small in count, occasionally large in dollars, and the only component that is genuinely a defect.
Build the bridge once
The productive artifact is a reconciliation that starts with the field service revenue figure for a period and walks to the accounting figure through named adjustments. Once that bridge exists, month-end becomes checking whether each component is within its normal range instead of hunting for a difference from scratch.
The components that stay stable are structural and can be ignored. The one that varies is where to look. This is exactly the kind of recurring check that belongs in an automated operations brief rather than in a person's memory.
Declare the system of record per question
Write down which system answers which question and stop arguing. Operational questions — how much work did we complete, what did each job produce, how are we trending by job type — are answered by the field service system. Financial questions — what did we recognize, what do we owe in tax, what is our margin after everything — are answered by accounting.
Reporting built on top should read from the declared source and label it. A revenue dashboard that shows a number without saying where it came from becomes a third opinion, and three opinions is worse than two.
Topics: accounting · reconciliation · revenue · reporting
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.