Problem guide
Two systems show different numbers
Two systems show different numbers when the same facts are entered separately into each one, at different times, by different people, with different rules. The lasting fix is to capture each fact once and have it arrive in every system that needs it in the right shape, so there is nothing left to disagree.
What it usually looks like
The operations manager reports that the crews logged a certain number of billable hours last month. The controller's number from accounting is lower. Both are sure they are right, and both are, for their own system. The field app counted a job the moment the technician closed it; accounting counted it when the invoice posted. Two jobs were credited in accounting but never changed in the field app. One technician's hours were typed with a wrong date. Nobody learns any of this until someone spends an afternoon matching records line by line.
Signs you have this problem
- The field app and accounting report different hours or job counts for the same period
- Meetings start with an argument about whose number is right
- Someone keeps a spreadsheet just to reconcile the two systems
- A correction made in one system never reaches the other
What usually causes it
- The same information is typed separately into each systemThe re-entry trap
- Each system updates on its own schedule, so one is always behind the otherThe handoff gap
- Edge cases like partial jobs, credits and rework are recorded differently in each placeThe exception swamp
What to try this week
- Pick one number and trace itChoose one figure that disagrees, such as last week's billable hours. Pull it from both systems and list the records behind each total side by side.
- Sort the differences by causeFor every record that does not match, write down why: timing, a typo, a missing entry, a different rule. The causes usually cluster into a few kinds.
- Decide which system owns each factWrite down which system is the source of truth for hours, parts, customers and revenue. Everyone should know which number to trust until the gap is closed.
- Record corrections in one placeWhen someone fixes a number, have them log where they fixed it and whether the other system was updated too. This shows how often fixes go only halfway.
Where do-it-yourself stops
These steps tell you where the numbers split and which one to trust. They do not stop the split, because the same facts are still being entered twice. A lasting fix is a tool built around your own systems that captures each fact once and delivers it to the others in the shape they accept, so nobody retypes it and nothing drifts. That is what a Workflow Spec designs.
Questions people ask
Why do our two systems show different numbers?
Usually because the same facts are entered into each one separately. Every separate entry is a chance for a typo, a delay or a different rule.
Which number should we trust?
Decide it explicitly for each kind of fact, and write it down. Without that decision, every meeting rebuilds the argument.
Is reconciling every week good enough?
It keeps the numbers close, but it is recurring work that exists only because of the gap. Measure how long it takes before deciding whether it is acceptable.
Will a new reporting dashboard fix it?
No. A dashboard that pulls from two disagreeing systems shows the disagreement more clearly. The fix has to happen where the data is entered.
How do we know the gap is closing?
Trace the same number each week and count the records that do not match. If the count falls, the fix is working.
Next step
Want this fixed for good?
This guide is how to find it and work around it. If it keeps coming back, the fix is usually a tool built around how your crew already works. Start with a free twenty-minute fit call.
Fox & Santiago, Genesee, Idaho. Home territory: the Inland Northwest, where we respond fastest. We fly anywhere in the United States for paid engagements.