Bank Reconciliation in Accounting Systems: Why Does the Balance Not Match the Bank Statement?
📅 16/11/2026
When performing bank reconciliation using an accounting system, reconciliation does not mean changing a figure to match the bank statement. It means explaining each difference and determining whether it is a timing difference, a missing transaction, or an incorrect entry. Start with a single cutoff date, a complete bank statement, and the corresponding bank ledger transactions.
A retail business accountant finds that the book balance of the bank account is higher than the bank statement balance at month-end, even though all sales receipts appear complete. Unreconciled transactions are not income or expenses merely because they appear in one of the two sources. They may be deposits in transit, unrecorded fees, or transfers pending settlement. Each case has a different effect on the accounting entries and expected cash.
This article explains a practical, step-by-step approach to diagnosing the problem, with examples from businesses operating in Saudi Arabia. It identifies the documents needed to resolve each issue and the testing criteria to apply after any correction. The article addresses a specific accounting problem in its operational context and does not treat technology as a substitute for professional judgment or original documentation.
How Do You Start Bank Reconciliation and Match a Bank Account in an Accounting System?
Start by defining the date as of which the figures must be correct and the scope of the accounts, customers, or branches included in the review. Keep a copy of the initial report, then separate source records from entries and aggregations. An accounting system helps bring these references together when permissions, accounts, and data are configured correctly. However, producing a single report does not replace comparing both sources and investigating the reasons for exceptions.
Practical application: Book a practical demonstration of the resolution workflow in the accounting system
Bank Reconciliation Steps for Resolving Bank Statement Differences
1. Identify the Account and Cutoff Date
The investigation starts with the warning sign the accountant encounters: a transaction appears on the Jeddah branch statement, but you are comparing it with another branch’s bank ledger or a different date. A common mistake is to jump to a corrective entry before understanding the source, because this can move the difference to another account rather than resolve it. The issue to investigate is that mixing accounts or using different period-end dates makes any subsequent comparison misleading. Review the transaction date and the associated branch or account, then ask whether the event actually occurred or whether it was recorded in a different place or period. This distinction shortens the investigation and prevents the error from multiplying at closing.
Assemble the following evidence file: the IBAN, account name, currency, monthly statement, and subsidiary ledger. Ideally, each document should have an original reference number and date and be linked to the same transaction in the general ledger or system record. Then carry out the practical action: establish the account, currency, and time period, then export transactions from both sources without changing their dates. Record the comparison results in a separate statement with columns for the amount, source date, and processing status. Avoid personal notes that a reviewer would struggle to understand. If a document is incomplete, flag the transaction for follow-up instead of assuming information that the relevant party has not confirmed.
Practical example: A business has an operating account and another account for depositing card sales, and mixes them up at the end of September. Case closure criterion: The documented opening balance must agree, and each file must have a known start and end date. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: Organizing General Ledger Accounts and Reconciliations
2. Review the Opening Balance and Identify Bank Statement Differences
When reports indicate that differences from a previous month recur in every new reconciliation despite current transactions matching, start by describing the difference in writing rather than merely telling management that the figures do not match. The cause worth testing is an old difference that was never cleared or a prior reconciliation entry that was recorded twice. Do not treat it as a conclusion before reviewing the evidence, however; a data-entry error can coexist with a legitimate timing difference. Determine the effect on revenue, expenses, assets, and liabilities, and establish whether the result changes an aggregate account or only its underlying detail.
To confirm or rule out the cause, obtain last month’s reconciliation statement, the closing general ledger balance, and the statement at the start of the month. Match documents by invoice or voucher number, amount, and bank or inventory reference where available, rather than by totals alone. The appropriate action in this case is to reconstruct the balance of the last approved month and avoid carrying forward an unsubstantiated figure. If more than one explanation emerges, test each separately and keep a copy of the report before correction. Comparing the situation before and after correction helps ensure that the entry or allocation has not created an additional difference.
Practical example: An old difference of SAR 680 was carried forward for three months and began to be treated as a new expense. Case closure criterion: This month’s opening balance equals the previous month’s closing balance after the explained differences. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: A Guide to Reading Financial Reports
3. Identify Deposits in Transit
This step becomes important when you notice that a receipt voucher appears in the system before the deposit appears at the bank. Before changing any balance, ask how the data moved from the document to the report. The initial hypothesis is a timing difference between submitting the deposit and the bank recording it. It requires independent supporting evidence. Correcting the final figure without correcting the procedure may cause the problem to recur the following month. Therefore, link the diagnosis to the transaction source, the approver, and the date, not just to the amount of the difference.
Do not start with a summary report without its details. The documents you need here are the deposit slip and its date, the cash ledger, and the bank statement after the cutoff date. Use them to reconstruct the transaction workflow in chronological order, then place the deposit on a pending-items list with its reference, amount, and deposit date, without creating a second entry. Prioritize cases by materiality, age, and transactions involving an external party. If an entry is necessary, link it to supporting documentation, approval, and user permissions, while retaining the original entry information for traceability and subsequent review.
Practical example: A shop deposits Thursday’s collections, and the deposit appears on the statement on the next business day. Case closure criterion: The deposit should subsequently appear for the same amount, or a separate follow-up case should be opened. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: Financial Reports Required from the System
Next step for your business: Compare system plans before moving away from manual spreadsheets
4. Reconcile Issued Checks or Outgoing Transfers
The situation may not seem significant at first: the system balance decreases before the bank debits the transfer or check. However, it reveals a potential weakness involving delayed execution, a rejected transaction, or an incorrect payment date, and its accumulation may affect another report or a collection or payment decision. It is better to isolate questionable transactions from valid ones and identify the time frame and responsible party before searching thousands of entries. Make a single document with a clear reference number the unit of review, then roll up the result to the aggregate account when finished.
The review requires more than a screenshot from the software. Use the payment order, transfer identifier, payment approval, and statements from subsequent days. Allocate one column to the source of evidence, another to the financial impact, and a third to the explanation accepted by management. Apply the following step: classify the transaction as pending or rejected after confirming its status with the bank, and avoid reversing it without supporting documentation. Do not delete the original transaction to make the records look clean. Instead, use a correction workflow that makes it possible to understand what happened, taking into account the documentation, invoicing, and internal control requirements relevant to the transaction.
Practical example: A supplier payment made at month-end remained under processing until the beginning of the following month. Case closure criterion: The pending item is cleared after execution, or the payment cancellation is documented with a clear notification. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: Understanding Customer and Supplier Account Statements
5. Record Bank Fees and Subscriptions
The accounting question here is not merely why one figure does not equal another, but why the bank statement includes fees that do not appear in the general ledger. This draws attention to a genuine bank expense that was omitted from the entries or classified in the wrong account. If an external party is involved, such as a customer, bank, or supplier, obtain its evidence. If the transaction is internal, retain the approval trail. Do not confuse an acceptable accounting explanation with an attempt to make the balance look better before submitting the report. A good correction can still be explained months after it is made.
Start with a single auditable file containing fee and commission notices, the bank statement, and the service invoice if available. First exclude differences that have been shown to belong to another period or account, then verify the nature of the fee, its associated tax, and its supporting document, then record the expense in accordance with policy. Place document reference numbers next to each other to make it easy to track each item without searching again. Do not combine multiple errors into a single reconciliation line if their causes differ. A solution that cannot be explained is not a sound basis for a reliable financial close.
Practical example: A monthly payment terminal fee is deducted without a separate notice being sent to the accountant. Case closure criterion: The transaction matches a clear expense item, and the entry is reviewed by the authorized person. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: Sales Operations Management
Next step for your business: Create an account to try organizing your business data
6. Reconcile Point-of-Sale and Card Payment Amounts
The investigation starts with the warning sign the accountant encounters: cash register revenue is higher than the net amount deposited by the payment provider. A common mistake is to jump to a corrective entry before understanding the source, because this can move the difference to another account rather than resolve it. The issue to investigate is that the differences may result from commissions, returns, or delays in batching payments. Review the transaction date and the associated branch or account, then ask whether the event actually occurred or whether it was recorded in a different place or period. This distinction shortens the investigation and prevents the error from multiplying at closing.
Assemble the following evidence file: closing reports, settlement reports, merchant fees, and payment references. Ideally, each document should have an original reference number and date and be linked to the same transaction in the general ledger or system record. Then carry out the practical action: match the gross amount before fees against payment terminal settlements, and record the commission separately when due. Record the comparison results in a separate statement with columns for the amount, source date, and processing status. Avoid personal notes that a reviewer would struggle to understand. If a document is incomplete, flag the transaction for follow-up instead of assuming information that the relevant party has not confirmed.
Practical example: A store makes SAR 20,000 in card sales and receives a lower net amount due to fees and returned transactions. Case closure criterion: Each payment can be traced from the day of sale to the bank deposit and the correct revenue account. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: Integrating Point-of-Sale Operations
7. Transfers Between Business Bank Accounts
When reports indicate that a debit appears at one bank without a corresponding credit at another, start by describing the difference in writing rather than merely telling management that the figures do not match. The cause worth testing is an unspecified counterpart account or a transaction that is still in transit. Do not treat it as a conclusion before reviewing the evidence, however; a data-entry error can coexist with a legitimate timing difference. Determine the effect on revenue, expenses, assets, and liabilities, and establish whether the result changes an aggregate account or only its underlying detail.
To confirm or rule out the cause, obtain the transfer reference, statements for both accounts, and internal transfer orders. Match documents by invoice or voucher number, amount, and bank or inventory reference where available, rather than by totals alone. The appropriate action in this case is to use a transfers-in-transit account if policy permits, and clear it when the transaction is completed. If more than one explanation emerges, test each separately and keep a copy of the report before correction. Comparing the situation before and after correction helps ensure that the entry or allocation has not created an additional difference.
Practical example: SAR 15,000 is transferred from an operating account to a payroll account and is mistakenly recorded as revenue. Case closure criterion: The transfer has no net effect on total cash and does not inflate revenue or expenses. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: Accounting Solution Features
8. Incorrectly Entered Dates and Amounts
This step becomes important when you notice that the transaction reference is correct, but the amount or date in the system does not match the bank. Before changing any balance, ask how the data moved from the document to the report. The initial hypothesis is a data-entry error, duplicate posting, or a transaction applied to the wrong customer. It requires independent supporting evidence. Correcting the final figure without correcting the procedure may cause the problem to recur the following month. Therefore, link the diagnosis to the transaction source, the approver, and the date, not just to the amount of the difference.
Do not start with a summary report without its details. The documents you need here are the original receipt or payment voucher, bank approval, and amendment log. Use them to reconstruct the transaction workflow in chronological order, then correct the transaction through its authorized workflow with an audit trail, instead of creating an unclear offsetting entry. Prioritize cases by materiality, age, and transactions involving an external party. If an entry is necessary, link it to supporting documentation, approval, and user permissions, while retaining the original entry information for traceability and subsequent review.
Practical example: A supplier transfer is entered as SAR 6,500 instead of SAR 5,600, creating a difference of SAR 900. Case closure criterion: The difference disappears, while document references and the amendment log remain traceable. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: Comparing Cloud and Traditional Accounting
Next step for your business: Request a demonstration of how to monitor controls and reports
9. Currencies and Foreign Currency Accounts
The situation may not seem significant at first: foreign currency bank statements differ from their Saudi riyal equivalents in the general ledger. However, it reveals a potential weakness involving confusion between the foreign currency amount and its revalued balance in Saudi riyals, and its accumulation may affect another report or a collection or payment decision. It is better to isolate questionable transactions from valid ones and identify the time frame and responsible party before searching thousands of entries. Make a single document with a clear reference number the unit of review, then roll up the result to the aggregate account when finished.
The review requires more than a screenshot from the software. Use the statement in the original currency, the approved exchange rate, and foreign exchange difference records. Allocate one column to the source of evidence, another to the financial impact, and a third to the explanation accepted by management. Apply the following step: separate the reconciliation of currency amounts from the revaluation entry in accordance with the applicable policy and standard. Do not delete the original transaction to make the records look clean. Instead, use a correction workflow that makes it possible to understand what happened, taking into account the documentation, invoicing, and internal control requirements relevant to the transaction.
Practical example: A business imports equipment and reconciles a US dollar bank account while its books show the equivalent in Saudi riyals. Case closure criterion: Match the amounts in the original currency first, then document revaluation differences without concealing transactions. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: Procurement System Functions
10. Approve the Bank Reconciliation and Document the Evidence File
The accounting question here is not merely why one figure does not equal another, but why quarter-end review findings recur because the reviewer cannot find an explanation for the differences. This draws attention to a lack of ownership for resolving pending items or reliance on a screenshot of the total. If an external party is involved, such as a customer, bank, or supplier, obtain its evidence. If the transaction is internal, retain the approval trail. Do not confuse an acceptable accounting explanation with an attempt to make the balance look better before submitting the report. A good correction can still be explained months after it is made.
Start with a single auditable file containing a final reconciliation statement, a schedule of differences, numbered documents, and the reviewer’s signature. First exclude differences that have been shown to belong to another period or account, then assign an owner and due date to each pending transaction, attach its supporting document, and approve the reconciliation. Place document reference numbers next to each other to make it easy to track each item without searching again. Do not combine multiple errors into a single reconciliation line if their causes differ. A solution that cannot be explained is not a sound basis for a reliable financial close.
Practical example: An accountant submits a file containing three pending deposits with their follow-up dates instead of a single difference figure. Case closure criterion: Only documented timing differences remain, and the closure date for each case is shown. Do not approve the resolution before verifying the result in the detailed report and the associated document.
For more on this stage: A Guide to Organizing Warehouses and Stocktaking
Practical Example: Reconciling a Bank Account from Start to Finish
A retail business accountant finds that the book balance of the bank account is higher than the bank statement balance at month-end, even though all sales receipts appear complete. Do not assume that the first difference you discover explains every figure. Create a working copy containing the balance or report before correction, then link it to the original document and record the dates and users. If the review reveals two different causes, separate them into two independent cases. One may require an accounting correction, while the other may be a timing difference that does not require a new entry.
Start with the highest-risk items and then complete the list in order: establish the account, currency, and period, then export transactions from both sources without changing their dates; classify a transaction as pending or rejected after confirming its status with the bank, and avoid reversing it without supporting documentation; use a transfers-in-transit account if policy permits, and clear it when the transaction is completed; assign an owner and due date to each pending transaction, attach its supporting document, and approve the reconciliation. After each step, produce a new detailed report rather than relying on a change in the total. Have the accounting manager or reviewer sign off on the reason for the correction and its effect on the period, and assign someone to follow up on cases that still lack adequate documentation.
Summary Comparison Table: Before and After Correction
| Status | Verification Indicator | Permitted Action |
|---|---|---|
| Initial observation | A transaction appears on the Jeddah branch statement, but you are comparing it with another branch’s bank ledger or a different date. | Establish the account, currency, and time period, then export transactions from both sources without changing their dates. |
| Decisive evidence | Fee and commission notices, the bank statement, and the service invoice if available. | The transaction matches a clear expense item, and the entry is reviewed by the authorized person. |
| Status after correction | Only documented timing differences remain, and the closure date for each case is shown. | Assign an owner and due date to each pending transaction, attach its supporting document, and approve the reconciliation. |
Bank Reconciliation Checklist for Accountants
• Define a single cutoff date and a list of accounts, branches, or suppliers included in the review.
• Retain the report and documents as they were before any amendment or posting.
• Match records at the individual transaction level, not merely at the total level.
• Classify each difference as a timing issue, a recording error, or a matter requiring professional judgment.
• Do not post a reconciliation entry without clear supporting documentation and approval from the authorized person.
• Regenerate the detailed report and entries, and document that the cause has been resolved.
• Assign an owner and review date to remaining cases, and record why they have not been closed.
• Keep a copy that can be rechecked when preparing or auditing financial statements.
Ready to Try the System?
Start your free trial or speak with the sales team to help choose the right solution.
Frequently Asked Questions
Can the month be closed with an unexplained difference?
It is not advisable to mark a reconciliation as complete while an unexplained difference remains. Document the difference and escalate it for review according to the business’s policy.
What is the difference between the transaction date and the value date?
The former records when the transaction is entered, while the latter may represent the date on which it is applied by the bank. Use a consistent reconciliation date without ignoring the distinction.
Should I adjust the bank balance with a direct reconciliation entry?
No. Post an entry only when there is an accounting event and supporting documentation. Timing differences should instead appear in the reconciliation statement.
Is a bank statement in Excel format sufficient?
It is preferable to link the transaction file to an official statement or an authorized bank source and retain the original statement and review procedures.
How does an accounting system help?
It helps extract the bank ledger, display references, and link receipt and payment vouchers, while responsibility for verification remains with the accountant.
Conclusion: Correct the Source Before Changing the Report
Success in resolving the problem is not measured by making a single difference disappear from the screen, but by the ability to trace each transaction, understand its effect, and prevent recurrence. Use an accounting system to bring accounts, documents, and reports together in a clear workflow, then link approval of the correction to a responsible person and a test. Above all, the results of reports must be capable of being rechecked. This is the difference between a figure that appears correct and accounting data that can be relied on for operations and decisions.
If you would like to test this workflow using your own business data: Start a trial of the accounting solution that suits your team
Manage Your Business with Greater Flexibility
Try Digital Business for free. Start issuing electronic invoices designed to meet ZATCA requirements in minutes.


