Accounts reconciliation vs bank reconciliation: what's the difference?

Bank reconciliation and accounts reconciliation are two terms that appear in every accounting practice — and are regularly used as if they mean the same thing. They do not. Bank reconciliation is one specific process; accounts reconciliation is a broader category that contains bank reconciliation along with several other processes. Conflating the two leads to gaps in month-end close procedures, incomplete audit trails, and compliance risk at BAS time.

This article defines both terms precisely, explains where the confusion comes from, and covers what a proper bank reconciliation audit trail looks like for Australian practices.

---

Bank reconciliation: the transaction-level check

Bank reconciliation is the process of matching every transaction on your client's bank statement against the corresponding entry in the accounting system's general ledger, and confirming that the two closing balances agree.

The objective is narrow and concrete:

Does the balance shown in the accounting software for this bank account equal the balance on the official bank statement, after accounting for any legitimate timing differences?

If the answer is yes, the account is reconciled. If not, there is an error, a missing entry, or a timing difference that needs to be explained and documented.

What bank reconciliation checks

Bank reconciliation happens at the transaction level. Its primary purposes are:

1. Fraud detection — unauthorised payments appear on the bank statement but not in the approved expense records
2. Error detection — duplicate entries, transposed figures, or bank errors that inflate or deflate the balance
3. Completeness — ensuring every transaction is captured before BAS preparation begins
4. Timing differences — accounting for end-of-period items such as outstanding cheques or deposits that have not cleared

For Australian practices, bank reconciliation is the foundation of GST reporting accuracy. An unreconciled cash account means the BAS is built on unverified transaction data.

---

Accounts reconciliation: the balance-sheet-wide check

Accounts reconciliation (sometimes called general ledger reconciliation) is the broader process of confirming that every account balance on the balance sheet is supported by underlying evidence. The question it answers is different:

Is every balance sheet account balance explainable by documents or sub-ledgers we can point to?

Bank reconciliation is one type of accounts reconciliation — specifically the reconciliation of cash accounts. But accounts reconciliation covers every line on the balance sheet:

Types of accounts reconciliation in Australian practices

1. Cash accounts — reconciled via bank reconciliation (bank statement vs ledger balance)
2. Accounts receivable — does the AR balance in the general ledger match the total of the debtor ledger or the aged receivables report?
3. Accounts payable — does the AP balance match the total of the creditor ledger and outstanding bills?
4. Payroll liabilities — does the PAYG withholding balance match what has been reported to the ATO via STP, less any payments made?
5. Fixed assets — does the asset balance match the depreciation schedule, accounting for additions and disposals during the period?
6. Loans and intercompany accounts — do balances match the loan agreement or the counterparty's records?
7. GST control accounts — does the GST collected/paid balance reconcile to the BAS lodgements and ATO running balance?

Accounts reconciliation is typically performed during month-end close and year-end procedures. It is the process that gives an auditor or the ATO confidence that every number on the balance sheet can be traced back to a source document.

---

Where the confusion comes from

The word "reconciliation" appears throughout accounting software without consistent meaning, which is the root cause of most confusion.

Xero's "reconcile" feature is specifically bank reconciliation. When Xero shows a transaction in the reconciliation screen and asks you to match or code it, that is bank reconciliation — matching a bank feed transaction to an accounting entry. Xero does not have a built-in accounts reconciliation workflow for AR, AP, or fixed assets in the same way.

MYOB's bank feeds work similarly — the reconciliation module is bank reconciliation.

"Accounts reconciliation" at year-end is a different, broader procedure that your practice runs across all balance sheet accounts before signing off on financial statements. Some practices use spreadsheets, others use dedicated software, and the process is often undocumented relative to bank reconciliation.

The practical consequence: a bookkeeper who "reconciles in Xero every month" may be doing excellent bank reconciliation but have never formally reconciled the AR, AP, or payroll liability accounts. This is a common gap in month-end close procedures, particularly in smaller practices.

---

The audit trail: why it matters for Australian practices

A bank reconciliation audit trail is a documented, timestamped record of how each reconciliation was performed — specifically:

• Which transactions were matched, and to what
• Who performed the match (or which rule or model made the decision)
• When the match was made
• Any exceptions, overrides, or unmatched items and how they were resolved
• The final reconciled balance and who approved it

Why Australian practices need a strong audit trail

The ATO's record-keeping obligations under the Tax Administration Act 1953 and the GST legislation require that records be kept for five years and be able to substantiate every amount reported on a BAS. In practice, this means that if the ATO reviews a client's GST, you need to be able to show:

1. The bank statement line that corresponds to a transaction
2. The accounting entry that recorded it
3. The GST code applied and why
4. Who made the coding decision and when

A manual reconciliation in a spreadsheet or a basic accounting software match satisfies the first two points reasonably well. It typically fails on points three and four — there is no record of who coded a transaction as BAS Excluded versus GST Free, or why.

What a complete bank reconciliation audit trail looks like

A complete audit trail for a bank reconciliation covers three layers:

Layer 1 — Matching evidence Each bank statement line is linked to its corresponding ledger entry, with both the bank reference and the accounting system transaction ID recorded.

Layer 2 — Coding evidence Each transaction's account code and GST treatment is recorded alongside:

• The rule or model that suggested the coding
• The confidence score (for AI or ML-assisted coding)
• Whether a human reviewed and confirmed or overrode the suggestion
• The timestamp of the decision

Layer 3 — Approval record The final reconciliation sign-off records who reviewed the completed reconciliation, when, and the reconciled balance at that point.

This level of documentation is what distinguishes a practice that is genuinely audit-ready from one that has technically reconciled but cannot reconstruct the process.

---

How ReconLink handles the audit trail

ReconLink is bank reconciliation software — it operates at the transaction level described above, not as a general accounts reconciliation tool. Its specific contribution to the audit trail question comes from the three-layer coding engine:

1. Deterministic rules — explicitly configured rules that match known merchants, transaction descriptions, or amounts to specific account and GST codes. Every match records which rule fired.
2. Machine learning model — trained on the client's historical coding patterns, the ML model suggests codes for transactions that do not match a deterministic rule. Every suggestion records the model version, confidence score, and the features that drove the recommendation.
3. Human review — where confidence is below the configured threshold, the transaction is flagged for human review. Any override is recorded alongside the original suggestion.

The result is a coding audit trail that answers not just what code was applied, but why — which matters in any compliance review where a coding decision is questioned. See how the automation layer works for more detail on the three-layer approach.

For practices that have previously relied on manual reconciliation or basic accounting software, the shift to a documented coding audit trail changes the compliance conversation with clients and with the ATO. See how ReconLink's audit trail works →

---

Practical implications for practice managers

Understanding the distinction between bank reconciliation and accounts reconciliation has concrete workflow implications:

For month-end close procedures:

• Bank reconciliation should be completed and signed off before any other month-end reporting
• Accounts reconciliation (AR, AP, payroll liabilities) should be completed before financials are presented to clients
• Do not assume that reconciling in Xero means all accounts are reconciled — it means cash accounts are reconciled

For year-end procedures:

• Every balance sheet account needs a reconciliation workpaper, not just the bank accounts
• The bank reconciliation audit trail should be retained as part of the year-end file
• Intercompany and related-party balances need specific reconciliation if the client has multiple entities

For ATO reviews:

• Bank reconciliation audit trails are the first evidence requested in a GST review
• The ability to trace a BAS line item back to an individual transaction, its coding decision, and the bank statement is the standard of proof
• Manual workpapers are acceptable but harder to produce quickly; software-generated trails can typically be exported in minutes

---

FAQ

What is the difference between bank reconciliation and accounts reconciliation?

Bank reconciliation is the process of matching transactions in the accounting system to the bank statement and confirming the balances agree. Accounts reconciliation is the broader process of confirming that every balance sheet account is supported by evidence — it includes bank reconciliation as one component, but also covers AR, AP, payroll liabilities, fixed assets, and other accounts.

Is bank reconciliation required by law in Australia?

There is no law that specifically requires a business to perform bank reconciliation. However, the ATO's record-keeping requirements under the Tax Administration Act 1953 require that records be accurate and able to substantiate amounts reported on tax returns and BAS lodgements. Bank reconciliation is the primary mechanism for ensuring that accuracy, so in practice it is an implied requirement for any GST-registered business.

What should a bank reconciliation audit trail include?

A complete bank reconciliation audit trail should include: matched transaction pairs (bank line to ledger entry), account and GST codes applied to each transaction, the basis for each coding decision (rule, model, or manual), any overrides and who made them, the final reconciled balance, and the sign-off record. The trail should be retained for at least five years in line with ATO record-keeping requirements.

Does reconciling in Xero create an audit trail?

Xero records that a transaction was matched and by whom, but it does not record the coding rationale — why a transaction was coded to a particular account or why a specific GST treatment was applied. For practices that need to defend coding decisions in an ATO review, supplementary documentation or purpose-built reconciliation software with a coding audit trail provides a stronger evidentiary position.

How often should accounts reconciliation be performed?

Bank reconciliation should be performed monthly at minimum, and ideally more frequently for clients with high transaction volumes. Other accounts reconciliation processes — AR, AP, payroll liabilities — should be performed at least monthly as part of the month-end close. Full balance sheet reconciliation (including fixed assets and longer-term accounts) is typically performed at year-end, though higher-risk accounts may warrant monthly review.