Skip to main content
Comparison · 6 min read

Unmatched Bank Items at Month-End: Ageing, Write-Off Approval and Period-Lock Rules to Test in Reconciliation Software

An unmatched bank item is a control, not just a to-do. Test how long it may stay open, who may write it off and what stops a closed month from changing, on day 31, day 61 and day 91 of an item's life.

Terra Insight
Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 14 October 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

Unmatched bank items are often treated as a to-do list, with no ageing policy, no write-off limits and nothing to stop a closed month from changing after sign-off.

How It's Resolved

Treat each unmatched item as a control and test the vendor's ageing, write-off approval, period lock and reopen rules on day 31, day 61 and day 91 of an item's life.

Configuration

Ageing from transaction date in 30, 60, 90 and over-90 buckets; write-off limits by amount and age with a second approver and reason code; period lock with logged, approved reopen.

Output

An ageing report by account and reason, a write-off log with approvers, and a change log for any reopened period.

An unmatched bank item is a control, not a to-do. Before you buy reconciliation software, test three rules: how items are aged, who may write them off, and what stops a closed month from changing. Run each test on an item at day 31, day 61 and day 91 of its life.

How exceptions are classified and routed is covered by criterion 6 of the 10-point evaluation framework and by the exception management guide. This page covers governance once an item stays open.

How should ageing work?

Age from the transaction date, or at least show both the transaction date and the date the item first appeared. Use buckets that match your policy, such as 0 to 30, 31 to 60, 61 to 90 and over 90 days. Items brought forward from last month must keep their original dates: an unexplained credit dated 31 July should show as 92 days old on 31 October, in the over-90 bucket, even if it was carried into a new tool in between. The ageing report should run by account and by reason, and your auditor should be able to reproduce it from the export.

Who can write off what?

Write-off rules should depend on both amount and type:

  • Bank charges and rounding: a preparer may clear up to a set limit, for example ₹500 per item, if the charge matches the bank’s schedule.
  • Unexplained debits: investigate first; write off only with a second approver.
  • Unexplained credits: never write off to income without review. The unreconciled credit decision tree explains why.

Every write-off needs a reason code, a link to the supporting note and the approver’s name. The priority vs materiality guide helps set the limits.

What should you ask the vendor to demonstrate?

RuleWhat to ask the vendor to demonstratePass or failAudit risk if missing
Ageing from original dateLoad a brought-forward item dated 45 days agoPass if it shows in 31 to 60Old items look new
Ageing buckets by policyChange buckets to your policyPass if no vendor change request is neededReport does not match policy
Write-off limitTry to write off ₹5,000 as preparer with a ₹500 limitPass if blocked and routed to approverUnauthorised write-offs
Reason codeWrite off without a reasonPass if blockedNo evidence for auditor
Period lockChange a match in a closed monthPass if blockedSigned figures change
Reopen with approvalReopen a closed monthPass if approval is needed and loggedSilent changes after close
Change log after closeExport the logPass if user, date and reason are shownNo trail of post-close edits

How do the rules apply in a worked month-end?

In an illustrative month, 120 lines remain unmatched at month-end. Apply each rule in turn:

  • 70 timing items, such as cheques in clearing and NEFT credits posted after the cut-off, stay open and are expected to clear in the first week. They age normally.
  • 30 bank charges, totalling ₹9,600 and each within the ₹500 limit, are cleared by the preparer with a reason code. With 18 percent GST included on the bank’s side, the ledger entry splits ₹8,136 to charges and ₹1,464 to input GST (₹8,136 × 18 percent = ₹1,464.48, rounded).
  • 20 items need review, including 6 unexplained credits. These go to a second approver and stay open.

After sign-off, the month is locked. The change log should meet the same standard the proviso to Rule 3(1) of the Companies (Accounts) Rules, 2014 has set for accounting software since 1 April 2023, and be kept for the eight financial years required by Section 128(5) of the Companies Act, 2013. If an approver later finds one of the 20 was a wrong match, reopening needs approval and the change is logged.

What does a weak answer sound like?

Watch for “you can export to Excel and track it there”, “any user can reverse a match” and “we do not lock periods, but you can see who changed what”. Each moves a control outside the tool.

How Terra Insight fits

TransactIG delivers bank-to-books reconciliation with an exception queue for unmatched items and audit-ready exports. Bring your open items and policy limits to a representative-sample fit benchmark and test these rules against our setup. See the bank reconciliation software page.

Primary reference: Institute of Chartered Accountants of India — whose Standards on Auditing guide how auditors test internal controls such as write-off approval and period close.

Frequently Asked Questions

How should unmatched bank items be aged?
Age each item from its transaction date, in buckets that match your policy, for example 0 to 30, 31 to 60, 61 to 90 and over 90 days. Items brought forward from earlier months should keep their original dates, not restart at zero.
Who should approve a write-off of an unmatched item?
Set limits by amount and age. Small bank charges and rounding differences can be cleared by a preparer within a limit, while unexplained credits and anything above the limit need a second approver and a reason code.
What is a period lock?
A period lock stops anyone from changing matches or entries in a month that has been closed and signed off. Reopening should need an approval and should be logged with user, date and reason.
Why treat unexplained credits differently from bank charges?
An unexplained credit may be a customer payment, a refund owed back, or money that does not belong to you. Writing it off to income hides a liability or a misapplied receipt, so it needs investigation rather than a write-off.
What is the risk if a tool has no period lock?
Matches in a closed month can change after the reconciliation was signed, so the figures given to the auditor no longer agree with the system. That is a control weakness an auditor may report.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.