Bank reconciliation sits at the intersection of two truths that should agree but often do not: the balance your accounting system shows for a bank account and the balance the bank actually holds. The difference between these two figures is not always an error - outstanding cheques, deposits in transit, bank charges posted directly, and timing differences create legitimate gaps. The problem is that most Nepali businesses either reconcile monthly (too infrequently to catch issues promptly) or reconcile manually using Excel (too slowly and error-prone to be reliable).
Manual bank reconciliation at month-end consumes significant time for accounting teams. A business with three bank accounts - a common position for a trading company running a current account, a fixed deposit, and a payroll account - might spend a full day each month comparing bank statements line by line against the general ledger. When eSewa and Khalti collections are added to the picture, the volume of transactions requiring matching increases substantially. A retail operation processing 50-100 digital payment transactions per day needs a different approach than manually ticking off entries in a printout.
Bank reconciliation software automates the matching process. Bank statements are imported in digital format, and the system matches each bank line against open accounting entries by amount, date, and reference number. Matched items are cleared automatically. Unmatched items - outstanding cheques, unposted bank charges, timing differences - surface as an exceptions list for the accountant to review and resolve. The process that took a day becomes two hours; the exceptions list is the actual work, not the matching.
Import the Bank Statement
Most Nepali banks provide statements in Excel, CSV, or PDF format through their online banking portals. The first step is importing this statement into the reconciliation module. CSV and Excel formats import directly with field mapping (date column, description column, debit amount, credit amount, balance). PDF imports require OCR extraction - most ERP systems that support bank reconciliation handle this automatically for standard bank statement layouts. Once imported, every line from the bank statement appears in the system as an unmatched item awaiting clearance. The opening balance from the statement becomes the reconciliation starting point.
Run Automatic Matching Against Ledger Entries
The system compares each bank statement line against open (uncleared) entries in the bank account ledger. Matching uses amount first, then date tolerance (entries within 3-5 days of the bank date), and reference number when available. Payments made by cheque match when the bank clears the cheque - the accounting entry was made on the issue date, the bank line appears on the clearance date. For electronic payments via RTGS or NEFT, the dates typically align within one banking day. Direct bank charges (service fees, SMS alert charges, annual account fees) usually have no corresponding accounting entry and surface as unmatched bank items - these require a journal entry to post the charge before they can be cleared.
Nepal's major commercial banks (Nabil, NIC Asia, Himalayan, Standard Chartered, Everest, NMB, Global IME, and others) provide online banking with statement download. Statement formats vary between banks - some provide clean CSV exports, others provide formatted Excel files that require preprocessing before import. Khalti and eSewa settlement statements arrive separately from bank statements; these digital payment settlements batch-deposit to the bank account, so reconciliation requires matching the settlement batch amount to the bank deposit line, then reconciling individual Khalti or eSewa transactions against the sales records separately.
Resolve the Exceptions List
After automatic matching, the exceptions list contains three categories of items. First, outstanding cheques: cheques issued and recorded in the ledger but not yet cleared by the bank. These are legitimate timing differences - they will clear in a future period. No action is needed other than noting they are outstanding. Second, unmatched bank items: bank charges, interest credited, charges debited, or deposits that have no corresponding accounting entry. These require journal entries to post them to the correct account. Third, unmatched ledger items: accounting entries with no corresponding bank line - these warrant investigation, as they may represent errors or items that need to be reversed.
A common reconciling item in Nepal is bank interest on current account balances. Nepali banks typically credit interest quarterly or half-yearly, and some accounts earn a small interest even on current accounts. This interest credit appears on the bank statement but is not recorded in the accounting system until the reconciliation identifies it and a receipt entry is posted. Some businesses also find small monthly charges - SMS banking fees, debit card charges, annual maintenance fees - that were never set up as recurring accounting entries and accumulate as unmatched bank items over several months.
Post Adjustment Entries for Unmatched Items
For each unmatched bank item identified in step 3, the accountant posts the necessary journal entry. Bank charges go to the bank charges expense account. Interest received goes to interest income. Returned cheques (cheques that bounced) require reversing the original receipt entry and recording the returned cheque as a receivable from the party. RTGS transfer fees, if charged by the bank directly rather than raised as a separate debit, need to be posted to the finance charges account. Once each adjustment entry is posted, the system re-runs the automatic matching and the previously unmatched bank item clears against the new entry.
Confirm Closing Balance and Lock the Period
Once all exceptions are resolved, the reconciliation shows: opening balance per bank, plus deposits in transit (in ledger, not yet on bank statement), less outstanding cheques (on bank statement clearance date but already in ledger), plus or minus any other reconciling items, equalling the adjusted book balance. This adjusted book balance must match the general ledger closing balance for the account. When it matches, the reconciliation is complete. Locking the reconciled period prevents back-dated journal entries from disturbing the cleared position - any new entry dated in a locked period requires supervisor approval. This lock protects the integrity of the reconciliation for audit purposes.
Bank reconciliation is a five-step process: import the statement, auto-match against ledger entries, review the exceptions list, post adjustments for unmatched items, and lock the period once the closing balance agrees. Software handles steps 1 and 2 automatically. The accountant's time goes into steps 3 and 4 - the analytical work, not the mechanical matching.
Frequently Asked Questions
Digital payment gateways like eSewa and Khalti collect from customers and then settle to your bank account in batches - often daily or 2-3 days after the transaction. The accounting approach is to record sales against a "eSewa/Khalti clearing" account when the customer pays, then clear the settlement to the bank account when the batch deposit arrives. Reconciliation works in two steps: first match individual transactions in the gateway portal against the clearing account, then match the batch deposit on the bank statement against the clearing account. Most ERP systems with gateway reconciliation handle this with a dedicated clearing account per gateway.
A bounced cheque in Nepal requires both accounting and legal steps. On the accounting side: reverse the original receipt entry (debit the party's account, credit the bank), record the returned cheque fee charged by your bank as a bank charge expense, and create a receivable from the party for the original amount plus any penalty you are charging them. On the legal side, cheque bounce is a criminal offence under Nepal's Negotiable Instruments Act - the payee can file a complaint with the relevant court if the cheque issuer fails to settle within 7 days of notice. Accurate accounting records of the original receipt, the return, and any subsequent settlement are essential if legal action is necessary.
Weekly is the practical minimum for businesses with regular bank transaction volumes. Monthly is the absolute minimum and is inadequate for businesses processing more than 30-50 transactions per month. The case for weekly reconciliation is that errors and fraud are caught within 7 days rather than 30-90 days - the window during which damage accumulates. With automated statement import and matching, weekly reconciliation adds roughly 30 minutes per account, which is a small investment compared to the risk of discovering a problem that has run undetected for a quarter. For high-volume businesses (retail, hospitality), daily reconciliation of the main operating account is achievable and worthwhile.
Bank Reconciliation Built Into the Accounting Core
MISAC's bank reconciliation is not a bolt-on module - it is part of the accounting core. Every payment voucher and receipt voucher in MISAC automatically triggers the bank reconciliation queue for the account it affects. When the bank statement is imported, the system has a full picture of every entry that should appear in the statement, with the correct amount, date, and reference. Matching runs against this complete picture. The auto-match rate is typically 75-85% for businesses with clean voucher entry discipline, leaving a manageable exceptions list for the accountant to work through.
Nepal-specific payment channels are handled natively. eSewa and Khalti settlement reconciliation uses a clearing account structure that separates gateway settlement timing from individual transaction recording. Cheque payment tracking keeps outstanding cheques visible in the reconciliation view until the bank clears them - they do not require a separate outstanding cheques register. Bank statement imports handle the formats used by Nepal's major commercial banks, with field mapping that can be configured for new bank statement formats without developer involvement.
Because MISAC is accounting-first in architecture, the reconciliation feeds directly into your financial reporting. The bank balance per reconciliation agrees with the balance sheet bank balance by design - there is no step to "reconcile the reconciliation to the accounts". MISAC Intelligence Pvt. Ltd. has deployed bank reconciliation for trading companies, NGOs, hotels, and cooperatives across Nepal that moved from quarterly manual reconciliation to weekly automated matching with the same accounting team handling more accounts in less time.
Ready to See MISAC in Action?
Contact us to see how MISAC's bank reconciliation module works for your specific bank accounts and payment channels.