What’s Actually Happening
You reconcile the bank account, everything shows as matched, and you think the file is fine. Then you open the BAS report in Xero and the GST payable doesn’t look right. Maybe the GST on sales feels too high, or the GST on purchases doesn’t tie back to what you reviewed earlier. Sometimes it even matched last week and now it doesn’t.
When people search “BAS not matching in Xero” or “GST not matching BAS report,” it’s usually because the reconciliation balances but the BAS figures don’t. The key thing to understand is that reconciliation and BAS reporting are not the same. Reconciliation confirms the bank statement matches the ledger. The BAS report pulls directly from the GST tax codes applied to transactions during the reporting period.
Where It Breaks
Most BAS mismatches are not one big mistake. They build up quietly. A bank feed drops out and transactions are uploaded using a CSV import. Later, the feed reconnects and some transactions come in again, creating duplicates. Everything still looks reconciled, but the GST coding may not be consistent.
Other common causes include GST inclusive versus exclusive errors, backdated journals, unreconcile and redo changes, or director loan payments coded as expenses instead of balance sheet movements. Even small rounding differences across split transactions can shift the BAS position without breaking reconciliation.
That’s why a file can feel balanced and still produce the wrong BAS figures in Xero.
The Takeaway
If your BAS is not matching in Xero, don’t patch the final number. Go back and check for duplicate bank transactions, review any CSV imports, confirm GST tax codes were applied correctly, and look for backdated edits during the quarter.
A reconciled file is not automatically a BAS-ready file. Fix the transaction layer, and the BAS report will usually correct itself.
