Bank reconciliation: matching, adjustments, and audit evidence
Bank reconciliation is a control, not a clerical task. When reconciliation is weak, businesses can 27t trust cash balances, and fraud or errors stay hidden. When reconciliation is strong, month-end close becomes predictable and audits become easier.<\/p>
This guide outlines a practical reconciliation process and what evidence you should keep.<\/p>
What you are trying to prove<\/h2>- Your system 27s cash\/bank ledger matches the bank statement for the same period.<\/li>
- Every difference is explainable: timing, bank fees, reversals, chargebacks, or corrections.<\/li>
- Approvals and audit logs exist for adjustments.<\/li><\/ul>
Matching patterns that work<\/h2>1) Exact match<\/h3>
Amount and date align. These are low-effort and should be automated where possible.<\/p>
2) Near match (timing difference)<\/h3>
Payment appears a day later in the bank due to settlement. Capture a reference and mark as timing difference.<\/p>
3) Split\/combined match<\/h3>
One bank deposit may represent multiple receipts, or one receipt may settle across multiple bank entries. Use matching rules and evidence links.<\/p>
Preparation: make matching easier<\/h2>
Most reconciliation pain comes from upstream inconsistencies: unclear references, missing receipts, and multiple systems representing the same payment differently. Before you reconcile, make sure your inputs are clean.<\/p>
- Consistent references<\/strong>: use invoice numbers and customer references consistently on receipts and bank descriptions where possible.<\/li>
- Clear bank account mapping<\/strong>: ensure each bank account in the statement maps to the correct ledger account.<\/li>
- Document discipline<\/strong>: record receipts when cash is received, not at month-end.<\/li>
- Controlled edits<\/strong>: limit who can edit receipts and bank entries using RBAC and approvals where configured.<\/li><\/ul>
Practical rule:<\/strong> the earlier you record receipts, the easier reconciliation becomes. Waiting until month-end increases ambiguity and disputes.<\/p><\/div>Common mismatch patterns (and fixes)<\/h2>Duplicate receipts<\/h3>
Duplicates happen when two teams record the same payment, or when payment confirmations arrive twice. Prevent this with clear references and periodic duplicate checks.<\/p>
Chargebacks and reversals<\/h3>
Chargebacks often appear days after the original receipt. Treat them as controlled adjustments with evidence links, and ensure reporting shows both the receipt and the reversal.<\/p>
Bank fees and withheld charges<\/h3>
Bank charges reduce the deposited amount, so the bank entry will not match the invoice total. Record fees as adjustments with the statement reference.<\/p>
Partial payments<\/h3>
When customers pay in parts, the bank statement will show multiple entries. Your customer ledger should support partial receipts so aging remains accurate.<\/p>
Timing differences<\/h3>
Settlement delays create legitimate timing differences. Record them explicitly so teams do not 22force match 22 by editing dates or amounts.<\/p>
Reconciliation cadence and ownership<\/h2>
Reconciliation should be a routine, not a crisis. Teams that reconcile weekly (or even daily for high volume) reduce end-of-month surprises and improve fraud detection.<\/p>
- High volume<\/strong>: reconcile daily or every 2 2D3 days to keep unmatched items small.<\/li>
- Medium volume<\/strong>: reconcile weekly and review exceptions in a short meeting.<\/li>
- Low volume<\/strong>: reconcile at least monthly, but still review large or unusual entries promptly.<\/li><\/ul>
Ownership matters: one team should own reconciliation, while exceptions route to sales, collections, or operations for clarification.<\/p>
Adjustments: treat them like mini-accounting entries<\/h2>
Adjustments should be controlled because they change financial statements. Examples include bank charges, interest, reversals, and corrections.<\/p>
- Require approvals for adjustments above a threshold.<\/li>
- Document the reason and attach statement evidence.<\/li>
- Lock periods after close to prevent silent back-dated edits.<\/li><\/ul>
FAQ<\/h2>Should reconciliation be done before period close?<\/h3>
Yes. Reconciliation is a prerequisite for a confident close. Once reconciliation and reviews are complete, use period lock controls (where configured) to keep prior months stable.<\/p>
How do I make audits easier?<\/h3>
Keep evidence linked: bank statements, reconciliation reports, adjustment documents, and audit logs. Review exception reports regularly instead of only during audit season.<\/p>
What is the best first metric to track?<\/h3>
Track unmatched bank entries and their aging. A small, stable unmatched list is a sign your process is working.<\/p>
Audit evidence checklist<\/h2>- Bank statement for the period<\/li>
- Reconciliation report showing matched\/unmatched items<\/li>
- Supporting documents for adjustments (fees, interest, reversals)<\/li>
- Audit logs showing who performed matches and approvals<\/li><\/ul>
Unmatched items playbook<\/h2>
Every team accumulates unmatched items. The goal is to keep the backlog small and aging low. A simple playbook is:<\/p>
- Group by type<\/strong>: deposits, withdrawals, fees, reversals, chargebacks.<\/li>
- Group by owner<\/strong>: sales (customer issues), operations (delivery\/returns), finance (fees and postings).<\/li>
- Set an SLA<\/strong>: for example, 22no unmatched item older than 14 days 22.<\/li>
- Review weekly<\/strong>: a 20-minute review prevents month-end chaos.<\/li><\/ul>
When backlog is visible and owned, reconciliation becomes predictable instead of a month-end emergency.<\/p>
Maker-checker controls for adjustments<\/h2>
Adjustments are a high-risk area because they can be used to hide mistakes or fraud. Treat adjustments like mini journal entries with controls.<\/p>
- Separate duties<\/strong>: the person who records an adjustment should not be the only approver for it.<\/li>
- Require reasons<\/strong>: capture a short reason and link to statement evidence.<\/li>
- Thresholds<\/strong>: route large adjustments to senior approvers automatically.<\/li>
- Period lock<\/strong>: once the month is closed, corrections should be posted in the current period with clear references.<\/li><\/ul>
KPIs to monitor<\/h2>- Unmatched count and aging<\/strong>: number of unmatched items and oldest age.<\/li>
- Adjustment volume<\/strong>: total adjustments by type (fees, reversals, chargebacks).<\/li>
- Close duration<\/strong>: days to complete reconciliation and close.<\/li>
- Reconciliation drift<\/strong>: changes made after close (should trend to zero).<\/li><\/ul>
To automate these KPI reviews, use Reporting 26 Audit<\/a> with report schedules and history.<\/p>Implementation checklist<\/h2>- Ensure bank accounts are mapped correctly in the ledger.<\/li>
- Define matching rules and train the team on how to handle splits and timing differences.<\/li>
- Define approval thresholds for adjustments and enforce maker-checker separation.<\/li>
- Schedule a weekly unmatched-items review and assign owners for each mismatch category.<\/li>
- Lock the period after month-end close to prevent historical drift (where configured).<\/li><\/ul>
If your team wants a structured way to report reconciliation issues and improvement requests, consider a tenant Support Portal<\/a> workflow.<\/p>Where NAViCalC fits<\/h2>
NAViCalC supports accounting workflows such as bank reconciliation, journal entries, and period controls. Combine this with Reporting 26 Audit<\/a> to keep evidence accessible across teams.<\/p>How reconciliation connects to billing and payables<\/h2>
Reconciliation improves when upstream processes are disciplined. Two areas matter most:<\/p>
- Billing\/AR<\/strong>: invoices and receipts should be posted promptly so deposits have clear references.<\/li>
- Payables\/AP<\/strong>: vendor payments and bank charges should be recorded with evidence links and approvals where needed.<\/li><\/ul>
When billing and operations share one system, it becomes easier to trace a bank statement line back to an invoice, receipt, vendor bill, or adjustment.<\/p>
Mini case study: chargeback handling<\/h2>
A chargeback appears in the bank statement 10 days after a customer payment. Teams often miss it until month-end, then scramble to explain a mismatch.<\/p>
- Record the chargeback as a controlled adjustment with evidence links.<\/li>
- Link it back to the original invoice\/receipt so the customer ledger remains consistent.<\/li>
- Route the exception to the account owner for follow-up and dispute handling.<\/li><\/ul>
When this process is repeatable, reconciliation becomes faster and the business learns from patterns instead of repeating the same surprises.<\/p>
Include chargebacks, reversals, and fees in your close checklist, then enable period lock after sign-off (where configured) so historical cash numbers do not drift.<\/p>
Get started<\/h2>
Review pricing<\/a> and explore Accounting 26 Finance<\/a> features.<\/p>Start by reconciling one bank account end-to-end, then scale the cadence across accounts.<\/p>Start 15-day Free Trial<\/a><\/article>Continue with NAViCalC<\/h2>
Matching patterns that work<\/h2>1) Exact match<\/h3>
Amount and date align. These are low-effort and should be automated where possible.<\/p>
2) Near match (timing difference)<\/h3>
Payment appears a day later in the bank due to settlement. Capture a reference and mark as timing difference.<\/p>
3) Split\/combined match<\/h3>
One bank deposit may represent multiple receipts, or one receipt may settle across multiple bank entries. Use matching rules and evidence links.<\/p>
Preparation: make matching easier<\/h2>
Most reconciliation pain comes from upstream inconsistencies: unclear references, missing receipts, and multiple systems representing the same payment differently. Before you reconcile, make sure your inputs are clean.<\/p>
- Consistent references<\/strong>: use invoice numbers and customer references consistently on receipts and bank descriptions where possible.<\/li>
- Clear bank account mapping<\/strong>: ensure each bank account in the statement maps to the correct ledger account.<\/li>
- Document discipline<\/strong>: record receipts when cash is received, not at month-end.<\/li>
- Controlled edits<\/strong>: limit who can edit receipts and bank entries using RBAC and approvals where configured.<\/li><\/ul>
Practical rule:<\/strong> the earlier you record receipts, the easier reconciliation becomes. Waiting until month-end increases ambiguity and disputes.<\/p><\/div>
Common mismatch patterns (and fixes)<\/h2>
Duplicate receipts<\/h3>
Duplicates happen when two teams record the same payment, or when payment confirmations arrive twice. Prevent this with clear references and periodic duplicate checks.<\/p>
Chargebacks and reversals<\/h3>
Chargebacks often appear days after the original receipt. Treat them as controlled adjustments with evidence links, and ensure reporting shows both the receipt and the reversal.<\/p>
Bank fees and withheld charges<\/h3>
Bank charges reduce the deposited amount, so the bank entry will not match the invoice total. Record fees as adjustments with the statement reference.<\/p>
Partial payments<\/h3>
When customers pay in parts, the bank statement will show multiple entries. Your customer ledger should support partial receipts so aging remains accurate.<\/p>
Timing differences<\/h3>
Settlement delays create legitimate timing differences. Record them explicitly so teams do not 22force match 22 by editing dates or amounts.<\/p>
Reconciliation cadence and ownership<\/h2>
Reconciliation should be a routine, not a crisis. Teams that reconcile weekly (or even daily for high volume) reduce end-of-month surprises and improve fraud detection.<\/p>
- High volume<\/strong>: reconcile daily or every 2 2D3 days to keep unmatched items small.<\/li>
- Medium volume<\/strong>: reconcile weekly and review exceptions in a short meeting.<\/li>
- Low volume<\/strong>: reconcile at least monthly, but still review large or unusual entries promptly.<\/li><\/ul>
Ownership matters: one team should own reconciliation, while exceptions route to sales, collections, or operations for clarification.<\/p>
Adjustments: treat them like mini-accounting entries<\/h2>
Adjustments should be controlled because they change financial statements. Examples include bank charges, interest, reversals, and corrections.<\/p>
- Require approvals for adjustments above a threshold.<\/li>
- Document the reason and attach statement evidence.<\/li>
- Lock periods after close to prevent silent back-dated edits.<\/li><\/ul>
FAQ<\/h2>
Should reconciliation be done before period close?<\/h3>
Yes. Reconciliation is a prerequisite for a confident close. Once reconciliation and reviews are complete, use period lock controls (where configured) to keep prior months stable.<\/p>
How do I make audits easier?<\/h3>
Keep evidence linked: bank statements, reconciliation reports, adjustment documents, and audit logs. Review exception reports regularly instead of only during audit season.<\/p>
What is the best first metric to track?<\/h3>
Track unmatched bank entries and their aging. A small, stable unmatched list is a sign your process is working.<\/p>
Audit evidence checklist<\/h2>
- Bank statement for the period<\/li>
- Reconciliation report showing matched\/unmatched items<\/li>
- Supporting documents for adjustments (fees, interest, reversals)<\/li>
- Audit logs showing who performed matches and approvals<\/li><\/ul>
Unmatched items playbook<\/h2>
Every team accumulates unmatched items. The goal is to keep the backlog small and aging low. A simple playbook is:<\/p>
- Group by type<\/strong>: deposits, withdrawals, fees, reversals, chargebacks.<\/li>
- Group by owner<\/strong>: sales (customer issues), operations (delivery\/returns), finance (fees and postings).<\/li>
- Set an SLA<\/strong>: for example, 22no unmatched item older than 14 days 22.<\/li>
- Review weekly<\/strong>: a 20-minute review prevents month-end chaos.<\/li><\/ul>
When backlog is visible and owned, reconciliation becomes predictable instead of a month-end emergency.<\/p>
Maker-checker controls for adjustments<\/h2>
Adjustments are a high-risk area because they can be used to hide mistakes or fraud. Treat adjustments like mini journal entries with controls.<\/p>
- Separate duties<\/strong>: the person who records an adjustment should not be the only approver for it.<\/li>
- Require reasons<\/strong>: capture a short reason and link to statement evidence.<\/li>
- Thresholds<\/strong>: route large adjustments to senior approvers automatically.<\/li>
- Period lock<\/strong>: once the month is closed, corrections should be posted in the current period with clear references.<\/li><\/ul>
KPIs to monitor<\/h2>
- Unmatched count and aging<\/strong>: number of unmatched items and oldest age.<\/li>
- Adjustment volume<\/strong>: total adjustments by type (fees, reversals, chargebacks).<\/li>
- Close duration<\/strong>: days to complete reconciliation and close.<\/li>
- Reconciliation drift<\/strong>: changes made after close (should trend to zero).<\/li><\/ul>
To automate these KPI reviews, use Reporting 26 Audit<\/a> with report schedules and history.<\/p>
Implementation checklist<\/h2>
- Ensure bank accounts are mapped correctly in the ledger.<\/li>
- Define matching rules and train the team on how to handle splits and timing differences.<\/li>
- Define approval thresholds for adjustments and enforce maker-checker separation.<\/li>
- Schedule a weekly unmatched-items review and assign owners for each mismatch category.<\/li>
- Lock the period after month-end close to prevent historical drift (where configured).<\/li><\/ul>
If your team wants a structured way to report reconciliation issues and improvement requests, consider a tenant Support Portal<\/a> workflow.<\/p>
Where NAViCalC fits<\/h2>
NAViCalC supports accounting workflows such as bank reconciliation, journal entries, and period controls. Combine this with Reporting 26 Audit<\/a> to keep evidence accessible across teams.<\/p>
How reconciliation connects to billing and payables<\/h2>
Reconciliation improves when upstream processes are disciplined. Two areas matter most:<\/p>
- Billing\/AR<\/strong>: invoices and receipts should be posted promptly so deposits have clear references.<\/li>
- Payables\/AP<\/strong>: vendor payments and bank charges should be recorded with evidence links and approvals where needed.<\/li><\/ul>
When billing and operations share one system, it becomes easier to trace a bank statement line back to an invoice, receipt, vendor bill, or adjustment.<\/p>
Mini case study: chargeback handling<\/h2>
A chargeback appears in the bank statement 10 days after a customer payment. Teams often miss it until month-end, then scramble to explain a mismatch.<\/p>
- Record the chargeback as a controlled adjustment with evidence links.<\/li>
- Link it back to the original invoice\/receipt so the customer ledger remains consistent.<\/li>
- Route the exception to the account owner for follow-up and dispute handling.<\/li><\/ul>
When this process is repeatable, reconciliation becomes faster and the business learns from patterns instead of repeating the same surprises.<\/p>
Include chargebacks, reversals, and fees in your close checklist, then enable period lock after sign-off (where configured) so historical cash numbers do not drift.<\/p>
Get started<\/h2>
Review pricing<\/a> and explore Accounting 26 Finance<\/a> features.<\/p>
Start by reconciling one bank account end-to-end, then scale the cadence across accounts.<\/p>Start 15-day Free Trial<\/a><\/article>
Continue with NAViCalC<\/h2>
- Payables\/AP<\/strong>: vendor payments and bank charges should be recorded with evidence links and approvals where needed.<\/li><\/ul>
- Billing\/AR<\/strong>: invoices and receipts should be posted promptly so deposits have clear references.<\/li>
- Adjustment volume<\/strong>: total adjustments by type (fees, reversals, chargebacks).<\/li>
- Require reasons<\/strong>: capture a short reason and link to statement evidence.<\/li>
- Group by owner<\/strong>: sales (customer issues), operations (delivery\/returns), finance (fees and postings).<\/li>
- Group by type<\/strong>: deposits, withdrawals, fees, reversals, chargebacks.<\/li>
- Medium volume<\/strong>: reconcile weekly and review exceptions in a short meeting.<\/li>
- Clear bank account mapping<\/strong>: ensure each bank account in the statement maps to the correct ledger account.<\/li>