When POS and accounting systems don't agree: why workflow understanding matters
Point-of-sale systems are supposed to make life easier. Ring up a sale, and the sales figure, the GST, and the payment method should all flow through to the accounting system without anyone touching it twice.
Automation doesn't always mean accuracy, though. That's the lesson underneath a reconciliation we worked through recently.
When the numbers don't match
During a routine review, we found the sales reported at G1 on the Business Activity Statement didn't match the sales sitting in the Profit and Loss Statement. Not a rounding difference. A gap significant enough to need a proper investigation.
The systems were connected. Data was flowing. On paper, the integration was doing its job. And yet two reports that should have told the same story about the same sales were telling different ones.
Where a POS integration can quietly go wrong
A POS-to-accounting connection looks simple from the outside: sales happen, a total gets sent through, done. In practice, a lot more is moving through that pipe, and each piece is a place things can drift:
GST-inclusive and GST-free sales
Cash, card, and online payment methods
Refunds, discounts, and voided transactions
Gift cards and customer deposits
Merchant fees
Sales made through third-party platforms
Timing differences between transactions, settlements, and accounting periods
Clearing accounts and bank deposits
Manual journals or adjustments
Failed, delayed, or duplicated syncs
Any one of those, misconfigured or changed without anyone reviewing it, is enough to pull BAS figures away from what the financial statements actually show.
Finding the actual problem took more than checking the software
Confirming the systems were "connected" told us almost nothing about why the numbers disagreed. Getting to the real answer meant tracing the whole path a transaction takes:
How the transaction originated in the POS system
How the information moved between the connected platforms
How different transaction types were mapped
Which entries landed in the Profit and Loss Statement
How sales and GST made it into the BAS
Whether manual adjustments or timing gaps had been introduced along the way
That's what let us isolate exactly where the figures diverged, rather than just narrowing it down to somewhere in the integration.
Confirming a system is connected tells you data is moving. It doesn't tell you the accounting treatment is right.
Why this is a workflow problem, not a software problem
Technology can automate the movement of data. It can't tell you on its own whether what landed on the other end reflects what actually happened in the business.
That's the gap werk:out spends most of its time in. We look past the individual transaction to the full path it travels: captured, transferred, classified, reconciled, reported, and ask where that path might be quietly bending away from reality. In practice, that means:
Spotting gaps between operational systems and financial reporting
Catching duplicated, omitted, or mismapped transactions
Reconciling POS sales against accounting records and bank settlements
Reviewing GST treatment and BAS reporting
Tightening up clearing accounts and reconciliation processes
Setting up controls that surface differences early, not at BAS time
Documenting the workflow so everyone knows who owns which exception
Fixing it once isn't the same as fixing it for good
Solving a historical discrepancy is useful. Preventing the next one is worth more.
Once the root cause is understood, the workflow can be strengthened with a few practical habits:
Regular POS-to-accounting reconciliations
A monthly comparison of BAS sales against the Profit and Loss Statement
A periodic review of integration mappings and tax codes
Ongoing monitoring of clearing accounts
Clear, agreed treatment for refunds, gift cards, merchant fees, and online sales
Exception reports that flag failed or duplicated postings
A named owner for investigating any difference that shows up
None of that is complicated to put in place. It just needs someone to actually own it.
Connected systems still need someone thinking about the connections
Integrations are genuinely useful, but they aren't a "set and forget" purchase. As a business adds more platforms, a single transaction might pass through a POS system, a payment gateway, an integration tool, the accounting system, and a bank feed before it ever shows up in a report. That's a lot of handoffs for one number to survive intact.
If your POS reports, accounting records, bank settlements, or BAS figures don't line up the way they should, that's usually not a sign your systems are broken. It's a sign the workflow between them needs a proper look, not just a check that everything's connected.
Whether you have been burnt by a big outsourcing firm before, or you are exploring offshoring for the first time, werk:out is built for exactly where you are right now. Head to werkout.com.au to learn more, or fill in our client intake form at werkout.com.au/contact and we will be in touch.
Your growth. Your decisions. Your business. We just make sure the engine is always running.
