Multi-location and franchise systems
Why don't my POS and accounting numbers match across locations?
POS and accounting numbers rarely match across locations because each location records sales a little differently, deposits arrive on a different schedule from sales, someone types in daily summaries by hand, and item and tax setups drift apart over time. The fix is one agreed way to record a sale everywhere, a standard account mapping, an automated connection and a daily exception report.
If your controller spends the first week of every month chasing differences between the register reports and the ledger, you do not have an accounting problem. You have a standards problem. It shows up in accounting because that is where the numbers finally meet. This article is for owners and CFOs of multi-location operators: restaurants, retail, franchise networks, healthcare and service sites. Our multi-location and franchise systems page covers the wider approach.
What causes POS sales to differ from the books?
Look for one of four causes. Most companies have all four, in different amounts, at different locations.
Cause 1: Each location rings things differently
The register does what the person using it tells it to do. Two managers can handle the same situation in two ways, and both are logical to them.
- Discounts. One location uses a percentage button, another rings an open price lower, another uses a coupon code. Your reports cannot compare them.
- Comps and voids. A comped meal or a free service might be a discount in one store and a zero-price item in another.
- Gift cards. Selling a gift card is not revenue. Redeeming one is. If locations treat these differently, sales and liabilities drift.
- Delivery apps. Orders from third-party platforms may arrive in the POS, be rung in by hand, or never enter it. The payout from the app is net of fees and does not equal the sales it covers.
- Tips. Card tips, cash tips, tip pooling and service charges sit in different places, and they should not be part of sales.
Cause 2: Deposits and sales happen at different times
A sale made on Friday night may reach the bank on Monday. Card processors batch and hold funds, and they deduct fees before paying out. Cash is deposited when someone goes to the bank. If accounting reconciles sales to deposits directly, the numbers will never match on any given day. The answer is a clearing account that holds the money in transit, and a rule for how it is cleared. Without one, timing differences look like errors, and real errors hide among them.
Cause 3: Someone types the summary in by hand
In many multi-location companies, a manager or bookkeeper reads totals off the end-of-day report and types them into the accounting system. Every re-keyed number is a chance for an error: a transposed digit, a missed line, a different cut-off time. It also creates a quiet dependency on one person who knows which lines to include. When that person is on vacation, the numbers change in character, not just in quantity.
Cause 4: Item and tax setup drift
Over time, locations create their own items, rename existing ones and set tax differently. A menu item, product or service code in one store may not match the same item in another. A tax rate set up wrong in one jurisdiction can run for months. This drift is invisible at the register and obvious in the ledger, where the same sale lands in different accounts or tax buckets.
Not sure where your systems are leaking? Start with a free check of how your sales data moves.
Take the Systems CheckWhat is the fix?
Four moves, in this order. Doing the last one without the first three automates the problem.
Fix 1: One agreed way to record a sale, everywhere
Write a short standard, in plain language, that every location follows. It should say how to ring a discount, a comp, a void, a refund, a gift card sale and redemption, a delivery order, a house account and a tip. Give each a defined button, item or code in the POS. Then keep the POS configuration identical across locations, from a template, so that nobody has to remember the rules. The standard is a business decision for the owner and the CFO. It is not an IT task.
Fix 2: A standard chart of accounts mapping
Decide, once, which account every kind of POS activity lands in. Food sales, service revenue, discounts, comps, gift card liability, tips payable, sales tax, third-party fees, clearing. Write it as a table and keep it with the POS setup. If you have a franchise or multi-entity structure, decide how locations or entities are tracked, by class, department or entity, so you can report by location without rebuilding the ledger.
| POS activity | Where it goes in accounting | Who owns the rule |
|---|---|---|
| Item sale | Revenue account for that category, tagged to location | CFO |
| Discount or comp | Its own contra-revenue or expense account, by reason | CFO |
| Gift card sold | Liability, not revenue | CFO |
| Gift card redeemed | Reduces the liability, recognizes revenue | CFO |
| Tips and service charges | Payable, not revenue | CFO and payroll |
| Delivery app order | Revenue by channel, with fees tracked separately | Operations and CFO |
| Card and cash settlement | Clearing account until the deposit arrives | Controller |
Fix 3: An automated connection
Once the rules are agreed and the mapping exists, connect the POS to accounting so that daily summaries post themselves. Nobody retypes a number. The connection should post to the mapped accounts, by location, and keep a trail back to the source report. Choose a connection that handles your actual mix: multiple locations, delivery platforms, gift cards. And decide who fixes it when a sync fails, because it eventually will.
Fix 4: Daily exception reports
Do not wait for month-end. A short daily report, read by one named person, should show the items that break the rules:
- Locations whose POS total differs from what was posted.
- Unusual discounts, comps, voids or refunds against a location's normal.
- Deposits that have not arrived within the expected window.
- Items or tax codes that exist in one location and not in the others.
The report turns drift into a small daily correction, instead of a large month-end investigation.
How do you reconcile by tender and by location?
Reconcile in layers, one location and one day at a time, not as a single monthly total. For each location and day, tie the POS sales report to what was posted in accounting. Then tie each tender to its own settlement: cash to the bank deposit, card to the processor batch and payout, gift cards to the liability account, and delivery apps to the platform's payout statement.
Differences should land in a clearing account with a reason: timing, fees, tips, a refund, or an unexplained amount. Only the unexplained amount is an error to chase. Working by tender isolates the cause, since a gap that appears only in card payouts points to fees or batch timing, not to the register. Working by location shows which store is drifting. The daily exception report in Fix 4 makes this a routine for one named person, not a monthly project.
Is the fix in the POS, the integration or the chart of accounts?
It is in all three, and the order matters. Start in the POS, because that is where the data is created: one standard way to record every kind of sale, from a single template. Then the chart of accounts, so each kind of activity has a defined home, tagged to location. Only then the integration, which should carry the clean, mapped data into accounting without anyone retyping it.
Reversing that order is the common mistake. An integration built on inconsistent POS data and no mapping automates the problem. If you are deciding where to spend first, spend on the standard and the mapping. Both are business decisions for the owner and CFO, not IT tasks, and they hold up even if you change POS or accounting software later.
Why do this before the next location opens?
A new location is the cheapest moment to be consistent. It starts on the template, with no old habits. If you wait until after opening, you must retrofit every existing location while it runs, change how staff ring sales, and clean months of history. The checklist in the systems checklist before you open your next location shows what to settle first. The same standardization matters in a deal: when you buy a multi-location company, test this in due diligence.
If one location is not behaving like the others, do not solve it location by location. Fix the standard, then bring every location to it.
Common questions
Is it normal for POS and accounting totals to differ?
Some timing difference is normal, because deposits land after sales are rung. A difference that cannot be explained line by line, or that differs by location, is a sign that locations record sales in different ways.
Can an integration fix this by itself?
No. An automated connection moves data faster, but it moves whatever each location entered. If locations ring discounts and comps differently, the connection will copy the inconsistency into your books faster.
Why is the problem worse with more locations?
Each location adds its own habits, its own setup and its own local fixes. With one location the owner sees the differences. With several, nobody sees the whole picture until month-end.
When is the best time to fix it?
Before the next location opens. A new location can start on the standard setup. Retrofitting existing locations later means changing habits while the business is running.
Not sure where to start?
Take a free three-minute score. If a conversation makes sense, it will offer one.