Accounting from the source
How to use bank activity to drive month-end close without missing off-bank items
Use statement activity as an investigation list while keeping bank evidence distinct from accounting vouchers, outstanding work and items not yet reflected by the bank.
A bank-led close does not treat the statement as the ledger. It uses statement activity as an investigation list: what caused each movement, what evidence supports it and has the accounting entry already been recorded? Off-bank items are then reviewed from document registers and outstanding-work queues.
This is Linda process-design guidance, not an accounting or tax rule. The scenarios are illustrative.
Begin with statement evidence you can recheck
Import a statement or bank feed while preserving date, amount, narrative, reference and bank transaction identifier. Avoid rewriting the bank narrative merely to make matching easier because those values support duplicate checks and traceability.
ERPNext describes a Bank Transaction as one statement or integration line and distinguishes it from Payment or Journal Entries that record the accounting movement. The distinction is useful regardless of software: bank evidence and book entries are related but not identical.
References: [1]
Search existing accounting records before creating another one
For each movement, search existing vouchers using amount, date, party and reference. One bank line may settle several invoices and one invoice may be settled by several payments, so an unmatched suggestion is not proof that a new entry is required.
ERPNext guidance recommends matching an existing voucher first and notes that a bank line can relate to several vouchers. Create missing accounting entries only after establishing that the underlying event has not already been recorded.
Turn unmatched lines into work queues, not mystery balances
Use explicit reasons such as missing evidence, unknown counterparty, grouped settlement, amount difference and awaiting owner confirmation. Assign an owner and follow-up date. A single generic “unreconciled” status hides what the team must do next.
Illustrative example: a THB 38,500 withdrawal says only “transfer”. Create a task to establish evidence and counterparty rather than guessing an expense category from the amount or bank narrative.
Review items that have not reached the bank
After statement review, examine supplier invoices, petty cash, accruals, tax records and documents awaiting approval. These may belong to the period even though no bank movement has occurred, so they need their own evidence and review path.
A bank-led close therefore has two views: the bank side for cash activity and an outstanding side for business events not yet visible at the bank. This prevents “not in the statement” from becoming “does not exist”.
Close on resolved evidence, not a matching percentage alone
Before close, summarise unresolved bank lines, off-bank records missing evidence and known differences with reasons and owners. When an item remains open, record who accepted that status and when it will be reviewed again.
Useful measures may include unresolved-item age, items without owners and time from bank visibility to review-ready evidence. Do not chase a 100% matching score so aggressively that users accept incorrect matches simply to make the dashboard green.
A practical starting checklist
- Preserve original statement data and bank transaction identifiers.
- Search existing vouchers before creating another record.
- Classify unmatched reasons and assign accountable owners.
- Review credit purchases, petty cash and outstanding off-bank records.
- Define the close gate and approved carry-forward items.
Apply it to your business
The bank is a strong starting point because it provides external evidence. A sound close still connects that evidence to documents, outstanding work and off-bank facts so bank-led review exposes problems rather than hiding them.
References
- Frappe. (n.d.). Bank Transaction. Retrieved October 1, 2026.
- Frappe. (n.d.). Banking in ERPNext. Retrieved October 1, 2026.
Numbered references support the attributed statements. Scenarios and recommendations are Linda’s examples, not verified client outcomes.
This article provides process-design guidance and illustrative examples, not an accounting, tax or legal determination or certification of every software module. Apply it with regard to your business, permissions and actual system scope.