Content reviewed and verified by Graham Chee, with FCPA-led practice at Local Knowledge, Mascot NSW. Continuous CPA Australia member since 1986. Prior career at Goldman Sachs, BNP Investment Management and Merrill Lynch.. Last reviewed October 2026. Next review scheduled for December 2026.
TL;DR
A practical, step-by-step bookkeeping workflow to find discrepancies, fix imported transactions, and achieve a true zero-variance month-end balance.
Key Takeaways
- A zero-variance balance means your software statement balance matches the actual bank balance down to the cent at month-end.
- Bank feeds are convenient, but third-party data connections can pause, drop out, or deliver duplicate lines after major digital banking updates.
- Reconciling transactions is not the same as verifying the statement balance; you can reconcile broken feeds and still have an incorrect cash position.
- Under Section 382-5 of the Taxation Administration Act 1953, the ATO requires Australian businesses to maintain records that accurately record and explain transactions.
- Unchecked feed errors skew your GST calculations on quarterly BAS lodgments, leading to underreported sales or claimed expenses you cannot substantiate.
Introduction
Getting your bank balance back on track without the stress
A bank feed break happens when your accounting software balance does not match your actual bank account balance, usually due to missed days or duplicated statement lines during direct feed refreshes. To achieve a zero-variance close, bookkeepers match the software statement balance to the official bank closing figure, isolate the broken dates, and restore accuracy by deleting duplicates or importing a cleaned CSV file. This process ensures your quarterly Business Activity Statement (BAS) submissions to the Australian Taxation Office (ATO) remain accurate and audit-ready.
This analysis on a methodical bookkeeping workflow for diagnosing open balance discrepancies caused by disrupted bank feeds, isolating deleted or double-imported statement lines, and importing corrected CSV statements to achieve a true zero-variance month-end close is written by Graham Chee, FCPA, CPA — Fellow of CPA Australia since November 2005, continuous CPA member since 1986, and principal of Local Knowledge accurate SME financial reporting. Based in Mascot NSW and running a principal-led practice since 2003, our focus under the CPA Code of Ethics is keeping books clean, compliant, and straightforward for Sydney trade businesses, local cafes, and growing operations.
Key Considerations
Six vital points every business owner should understand about feed breaks
A zero-variance balance means your software statement balance matches the actual bank balance down to the cent at month-end.
Bank feeds are convenient, but third-party data connections can pause, drop out, or deliver duplicate lines after major digital banking updates.
Reconciling transactions is not the same as verifying the statement balance; you can reconcile broken feeds and still have an incorrect cash position.
Under Section 382-5 of the Taxation Administration Act 1953, the ATO requires Australian businesses to maintain records that accurately record and explain transactions.
Unchecked feed errors skew your GST calculations on quarterly BAS lodgments, leading to underreported sales or claimed expenses you cannot substantiate.
Manual adjustments inside software should never be patched with dummy journal entries; fixing the actual statement lines maintains a transparent audit trail.
Practical Application
How feed breaks show up in day-to-day trade and cafe operations
In a busy Sydney operation, feed breaks usually happen silently. Consider an electrical contractor in Alexandria buying materials daily from trade suppliers, or a cafe in Surry Hills running dozens of merchant card settlements every week. The owner logs into Xero or MYOB, clicks OK across thirty transactions, and assumes everything is sorted because the dashboard shows no pending items. However, when checking the actual CBA, Westpac, ANZ, or NAB online banking app, the bank statement shows $14,250 while the software balance shows $16,800. This $2,550 variance can lead to overspending or underpaying superannuation.
To resolve this, the bookkeeper pulls the Bank Reconciliation Report in Xero or the Reconcile Accounts screen in MYOB as of the last day of the calendar month experienced Sydney bookkeeping and accounting professionals. Compare the Statement Balance in the software directly against the opening and closing figures on your official PDF bank statement. If the opening balance matches but the month-end closing balance diverges, a break occurred inside that 30-day window. You isolate the exact day by comparing weekly milestones. Once the specific dates are identified, you inspect the Statement Exceptions or Bank Statement tab to find duplicate entries that slipped through or gap dates where no transactions fed into the system.
Recommended Steps
A structured workflow to restore a zero-variance bank reconciliation
Isolate the Variance Date
Run your reconciliation report. Compare your weekly balances against your actual bank statement to pinpoint the exact day the discrepancy began.
Remove Duplicate Statement Lines
If transactions imported twice, select the duplicated statement lines in your software bank tab and delete them. Never delete created spend or receive money transactions without removing the statement line first.
Export and Prepare Clean CSV Lines
If days are missing, log into your online banking portal, download a CSV statement for only the missing date range, and ensure column headers match Date, Amount, and Description.
Import and Verify Zero Variance
Upload the CSV statement directly into the bank account register, reconcile the newly restored items, and re-run your reconciliation report to confirm a exact zero-dollar variance.
Common Questions
Practical answers for Sydney business owners managing their day-to-day books
Q.Why does my software show reconciled when my bank balance is wrong?
Software reconciliation only confirms that the statement lines imported into the system have been matched against internal transactions. If the bank feed missed an entire week or imported transactions twice, you can successfully reconcile all visible lines while your overall software balance remains completely wrong. cash flow management and financial oversight tools
Q.Can I just enter a manual journal entry to fix the difference?
No. Entering an adjustment journal masks underlying errors, distorts your GST reporting on your BAS, and can cause compliance headaches with the ATO. The correct method is always to delete duplicates or import the missing statement lines so your software reflects real-world banking records.
Q.How often should I check for bank feed discrepancies?
We recommend checking your statement balances against actual online banking figures weekly, and performing a full reconciliation report sign-off at the end of every calendar month. This ensures you catch feed dropouts before processing Single Touch Payroll (STP) or quarterly BAS.
Q.What causes bank feeds to stop working or create duplicates?
Bank feeds rely on secure API connections between financial institutions and software platforms. Scheduled bank maintenance, security token expirations, multi-factor authentication resets, or account changes often pause feeds, occasionally resulting in missed days or duplicated imports once reconnected.
About the Author
Graham Chee, FCPA, CPA, GRCP, GRCA
Principal and Founder, Local Knowledge
Graham Chee is the principal and founder of Local Knowledge, an FCPA-led Australian practice that brings institutional-grade compliance, investment-structure and intellectual-property experience directly to owner-managed businesses. Graham is a Fellow of CPA Australia (FCPA since November 2005, continuous CPA member since 1986) and holds the OCEG Governance, Risk & Compliance Professional (GRCP) and Governance, Risk & Compliance Auditor (GRCA) designations. His prior career includes senior roles at Goldman Sachs, BNP Investment Management and Merrill Lynch. Graham was previously portfolio manager of the Asian Masters Fund (IPO December 2007 – 31 December 2009), which returned +29% in AUD terms versus the MSCI Asia Pacific (ex Japan) benchmark. He signs off on 100% of client files personally.
Areas of Expertise: