An operator described watching his back office sales report and his point of sale report agree for a moment, then running both again five minutes later and finding them apart. The gap was small, persistent, and months old.
What he wanted was not the variance explained. It was something simpler and harder: to be able to tell his team which report to use.
That is the real cost, and it is not the gap between the numbers. A venue with two numbers has no number. Managers stop acting on either, and the reporting layer quietly becomes decoration.
Why Do Two Reports From The Same System Disagree?
Reports pulled from different systems disagree for obvious reasons, and that case has its own treatment in the report you rebuild every morning. Two reports from the same platform disagreeing is a different problem, and it usually comes down to five mechanisms.
Timing against a moving ledger. A report is a snapshot of a system that is still transacting. Tabs close, tips adjust. A report run at 7:02 contains a tab that closed at 7:01 and the 6:58 version does not. In a venue where tabs stay open for hours this is the single most common explanation, and it is not an error at all.
Different definitions of a sale. Gross or net. Whether comps, voids, discounts and refunds are deducted. Whether service charges count as revenue. Whether tax is in or out. Whether tips pass through. Two reports built for two audiences, one for operations and one for accounting, can both be correct and still differ by several percent every single day.
Stored value counted two ways. A game card load is a liability in an accounting report and frequently revenue in an operations report. In a venue that sells game cards this gap is large, and it moves with card sales, which makes it look alarmingly like a leak.
Refunds dated differently. A refund booked against the original sale date changes a number you already reported last week. A refund booked on the day it was issued does not. Run a month-to-date report before and after a large refund and the two conventions diverge visibly.
Late-arriving data. Offline transactions syncing once connectivity returns, tips adjusted after close, an event invoice posted the next morning. Reports that recompute will change, and reports that snapshot will not.
Notice what is and is not on that list. Only one of the five is a defect. The other four are two reports answering two different questions, which means the fix is not a support ticket.
Which Number Should You Actually Trust?
Neither, until you have said what each one is for.
The question of which report is right has no answer, because right depends on the decision being made. A manager deciding whether to cut a server at eight in the evening needs live gross sales including open tabs. A bookkeeper closing the month needs net revenue with stored value excluded, refunds dated to the original sale, and nothing still moving. Those are different numbers on purpose.
The useful reframe is to stop asking which report is right and start asking which report owns each number. That question has an answer, and it is a decision you make rather than one you discover.
How Do You Declare A System Of Record?
Write down, for each number that matters, which system is the authority and which systems merely display it. It fits on one page.
- Gross sales. Usually the point of sale, because it captures the transaction first.
- Net revenue. Usually the accounting-facing report, because it applies deductions consistently.
- Stored value balance. Exactly one system. If both the POS and the card platform hold a balance, they will eventually disagree, and no reporting layer can resolve a disagreement about how much money a guest has.
- Deferred revenue from deposits. The system that took the deposit.
- Labor. The scheduling or payroll system, not the POS estimate.
Then publish it. The document stating that stored value is owned by the card platform and revenue recognition is owned by the point of sale is worth more than any dashboard, because it converts a recurring argument into a lookup. A manager dashboard is only trustworthy to the degree that the ownership question has already been settled.
How Big A Difference Is Normal?
Set a tolerance before you start looking, or you will chase noise.
Compare four numbers daily for two full weeks, including at least two weekends and one heavy event day: gross revenue, revenue by line of business, stored value liability, and cash over or short. Investigate anything over one percent; log anything under it.
Expect most differences to resolve into the five mechanisms above rather than into errors. That is the point of the exercise. You are not hunting a defect, you are building a map of which differences are structural. Each one you find, write down beside the ownership table, and it stops being a surprise every month.
One warning from venues that have done this. Do not retire the old report until two consecutive weeks reconcile cleanly. Operators who skip the parallel run tend to be back on spreadsheets within a month, because the first unexplained variance permanently destroys confidence in the automation.
When Should You Escalate To Your Vendor?
When a difference survives all five explanations, moves without a corresponding change in trading, or changes direction from one day to the next.
Go in with specifics rather than a complaint. Give the vendor two report names, the exact timestamps at which both were run, the two totals, and the filters applied to each. Reporting that report A run at 07:02 shows 14,208.50 while report B run at 07:02 shows 14,061.25 under identical filters is usually the difference between a ticket that closes in a week and one that stays open for months.
Ask the structural question while you have their attention. Which report does the vendor consider authoritative, and is that documented anywhere? A vendor who cannot answer has told you something useful about the platform. It is a fair question to put to any family entertainment center POS during evaluation, well before you are live on it.
Who Does This Operational Approach Fit Best?
Declaring a system of record matters most in venues with more than one revenue line and any stored value, which is nearly every FEC with an arcade. The combination of game cards and food is precisely where two reports drift apart fastest.
It matters more still for multi-location operators, where the same ambiguity repeats at every site and the differences compound into a group number nobody can defend.
It matters less in single-attraction venues on one system with no stored value, where there genuinely is only one report. And it is worth deferring in venues under ninety days old, where the operating numbers are still moving too much for a two-week parallel run to mean anything. Fragmentation across systems is the prior problem to solve there, which is the subject of why FEC tech stacks end up with six systems.
Want one set of numbers you can hand your team without a caveat? Request a demo, or read the complete FEC technology stack.
FAQ
Why do my POS and back office sales reports show different totals?
Most often because they were computed at different moments against tabs that were still open, or because one deducts comps, voids and discounts while the other does not. Before assuming a defect, compare the exact run times and the filters on each report, and check how each one treats stored value loads.
Should game card sales appear as revenue in a daily sales report?
No. Value loaded onto a card is a liability until it is redeemed. Counting loads as revenue inflates the week you sell cards and deflates the week guests spend them. Loads, redemptions and outstanding balance belong on the report as three separate lines.
How much variance between two reports is acceptable?
Set the threshold in advance rather than judging case by case; one percent of gross is a workable start for most venues. What matters more is that differences above it are always investigated and structural explanations written down, so the same one is not re-investigated every month.
What is a system of record and why does a venue need one?
A system of record is the single system designated as the authority for a particular number, with every other system treated as a display. Without one, two systems holding the same figure will eventually disagree and no reporting layer can resolve it, because the disagreement is about ownership rather than arithmetic.
.avif)
