ERPNext reconciles your bank account through a dedicated Bank Reconciliation Tool: you import a bank statement, the system matches each line to existing vouchers by ranking how many fields agree, and you clear the rest by creating vouchers on the spot. For Indian SMBs, statement import (CSV, Excel, or MT940) is the practical route, because the built-in bank feed does not cover Indian banks.
Short answer
To reconcile a bank account in ERPNext, open the Bank Reconciliation Tool, select your company, bank account, and statement date range, then confirm the opening balance matches. Import the statement, let ERPNext auto-match transactions to Payment Entries and Journal Entries, and use Match, Create, or Update actions to clear the remaining lines until the summary card turns green.
I run ERPNext implementations at MithTech, a team of Frappe specialists in Bengaluru, for organisations with several branches, warehouses and dealer networks. Bank reconciliation is often where a finance team first sees the system pay off: done well, the month-end match moves out of spreadsheets. The tool is good, but it rewards clean master data more than clever clicking. Messy party names and duplicate ledgers slow you down far more than the software does.
What is bank reconciliation in ERPNext?
Bank reconciliation in ERPNext is the process of matching every line on your actual bank statement against the payments, receipts, and journal entries already recorded in your ledger, then clearing differences until the two balances agree. ERPNext handles this through a single-screen Bank Reconciliation Tool that stores each cleared line as a Bank Transaction record.
The tool sits in the Accounting workspace. You reach it from Accounting > Bank Statement > Bank Reconciliation Tool, or just type "Bank Reconciliation Tool" into the awesomebar. Before matching, ERPNext asks you to confirm the opening balance in the system equals the opening balance on your statement, and to enter the statement's closing balance — that closing figure is your finish line. Summary cards at the top track progress and turn green when the reconciled amount lands on the statement balance.
Skimmable summary: ERPNext reconciles by matching statement lines to ledger vouchers on one screen, with a green summary card confirming the balances agree.
How do I import a bank statement into ERPNext?
Importing a statement starts from the reconciliation screen and runs as a background job so large files do not time out. ERPNext accepts CSV, Excel, and MT940 files, and needs at minimum the date, the debit or credit amount, and the currency on every row. The first import asks you to map statement columns to Bank Transaction fields; ERPNext saves that mapping to the Bank record for next month.
Prepare the statement file
Download the statement from your bank in CSV or Excel. Keep one clean header row and confirm each line has a date, an amount (debit or credit), and the currency. Delete summary or footer rows the bank adds.
Open the tool and set filters
Go to the Bank Reconciliation Tool, then pick Company, Bank Account, and the statement start and end dates. Verify the ERPNext opening balance matches the statement, and enter the statement closing balance.
Upload and map columns
Choose Upload Statement, select your file, and click Map Columns. Tell ERPNext which column is the date, which is debit, credit, description, and reference. Save the mapping.
Start the import
Click Start Import. ERPNext creates Bank Transaction records via a background job and shows progress. Once done, every statement line appears in the reconciliation table, ready to match.
Skimmable summary: Import CSV, Excel, or MT940 files from the reconciliation screen, map columns once, and ERPNext creates Bank Transactions as a background job.
How does ERPNext match bank transactions to vouchers?
Matching in ERPNext works by pulling candidate vouchers that share fields with a bank line — posting date, amount, and reference number — then ranking them by how many of those fields agree. The strongest candidate sits at the top of the list. Supported voucher types include Payment Entry, Journal Entry, Sales Invoice, Purchase Invoice, and Expense Claim.
To match a line, choose Match Against Voucher in the Action column. ERPNext shows the ranked list, and you tick one or several vouchers against the same bank transaction using checkboxes — useful when a single bank credit settles multiple invoices. The redesigned engine ranks matches with a single database query rather than stitching results together afterward, which keeps large statements responsive.
You can also let ERPNext help with the party. Under Accounts Settings > Banking, enabling Automatic Party Matching auto-fills the customer or supplier on a transaction when the system recognises it. Turning on Fuzzy Matching lets ERPNext approximately match a party name in the statement description against your party master — useful when banks truncate or garble names.
| Action | When to use it | Result |
|---|---|---|
| Match Against Voucher | A payment or invoice already exists in ERPNext | Links the bank line to existing voucher(s) |
| Create Voucher | No entry exists yet (bank charge, interest) | Creates a Payment or Journal Entry inline |
| Update Bank Transaction | The line needs a party or reference fix | Edits the transaction without leaving the screen |
| Transfer | Money moved between your own accounts | Records an internal transfer |
Skimmable summary: ERPNext ranks candidate vouchers by matching fields, lets you tick one or many, and can auto-fill the party using automatic or fuzzy matching.
How do I create missing vouchers during reconciliation?
Creating vouchers during reconciliation covers the statement lines that have no ledger entry yet — bank charges, interest credits, or a receipt nobody recorded. ERPNext lets you generate a Payment Entry or Journal Entry directly from the bank line, pre-filling the amount and date from the transaction so you only choose the account and party.
Pick the unmatched line
In the reconciliation table, find a transaction with no suggested match — often a bank fee or interest posting.
Choose Create Voucher
Select Create Voucher in the Action column. Decide between a Payment Entry (for a receipt or payment) or a Journal Entry (for charges and interest).
Fill the account and party
ERPNext carries over the amount and date. Add the ledger account — for example, a bank-charges expense head — and the party if relevant. Save and submit.
Confirm it clears
The new voucher links back to the bank line automatically. Watch the summary card: as each line clears, the reconciled total climbs toward the statement closing balance.
Skimmable summary: For lines with no ledger entry, Create Voucher builds a Payment or Journal Entry inline with amount and date pre-filled, then links it back automatically.
Can ERPNext connect directly to my bank feed?
Direct bank feeds exist in ERPNext through the Plaid integration, which can sync linked accounts automatically — including an hourly option — so transactions land without a manual upload. Plaid coverage, however, is limited to the United States, Canada, the United Kingdom, and Europe, and does not support Indian bank accounts.
For businesses in India, that leaves statement import as the dependable method. Your bank's net-banking portal exports CSV or Excel, and many corporate banking platforms also offer MT940 — all three import cleanly into the reconciliation tool. The difference is small: once your column mapping is saved, a monthly CSV import takes little longer than a feed, and you control exactly which lines enter the ledger.
Skimmable summary: ERPNext supports live feeds via Plaid, but Plaid does not cover Indian banks — so Indian SMBs reconcile through CSV, Excel, or MT940 statement import.
What keeps reconciliation reliable?
Reliable reconciliation depends less on the tool and more on the data feeding it. Clean, deduplicated master records let ERPNext auto-match a high share of lines on the first pass, so your team only judges the exceptions. A few habits separate a smooth month-end from a painful one.
One ledger per bank account
Map each real bank account to exactly one ERPNext ledger. Duplicate or overlapping bank ledgers are the most common reason opening balances refuse to agree.
Reconcile monthly, not annually
Small, frequent runs keep the unmatched pile short. A backlog of twelve months makes every ambiguous line harder to place.
Standardise party names
Consistent customer and supplier names raise the hit rate of automatic and fuzzy party matching, cutting manual tagging.
Record payments promptly
The more receipts and payments already sit in ERPNext, the more lines auto-match. Reconciliation then verifies rather than re-enters.
If you also run other finance tools during a transition, keep their scope clear so entries do not double up — the same care applies when you bridge systems like QuickBooks with ERPNext during a migration.
A webhook or an import can miss a payment or book it twice, so compare books and bank on a schedule. Reconciliation as a job shows that comparison on sample data, with only the exceptions left for people.
Skimmable summary: Clean single-ledger mapping, monthly runs, standardised party names, and prompt payment entry drive the auto-match rate and make reconciliation fast.
How does ERPNext compare with standalone accounting tools?
Against standalone accounting apps, ERPNext reconciliation differs on control and the licence model, and asks for a little more discipline up front. As open-source software, the reconciliation tool carries no separate licence fee and lives inside the same system as your invoices, inventory, and payroll — so a matched bank line ties straight to the source voucher.
| ERPNext | ||
|---|---|---|
| Licence model | Open source (GPLv3), no licence fee; you pay for hosting and support | Usually per-user subscription |
| Reconciliation location | Inside the same ERP as invoices, stock, payroll | Separate app; often needs sync back to ERP |
| Statement import | CSV, Excel, MT940 | Varies by vendor |
| Bank feed in India | Not via Plaid; use statement import | Varies — check the vendor's official page |
| Customisation | Full source access, custom fields, scripts | Limited to vendor's options |
Pricing varies by vendor and edition, so check the vendor's own page for current figures. The structural point stands: in ERPNext, reconciliation is part of the accounting module, not a bolt-on. More on how we run ERPNext is on the Frappe and ERPNext page.
Skimmable summary: ERPNext offers open-source, in-system reconciliation with no per-user licence, trading a little setup discipline for full control and tight ledger links.
Frequently asked questions
+Where is the Bank Reconciliation Tool in ERPNext?
Open it from Accounting > Bank Statement > Bank Reconciliation Tool, or type "Bank Reconciliation Tool" in the awesomebar. Select your company, bank account, and statement date range, confirm the opening balance matches, and enter the statement closing balance to begin.
+What file formats can I import for reconciliation?
ERPNext imports bank statements in CSV, Excel, and MT940 formats. Each row needs at least a date, a debit or credit amount, and the currency. On the first import you map statement columns to fields, and ERPNext remembers that mapping on the Bank record.
+How does ERPNext auto-match bank transactions?
ERPNext pulls candidate vouchers that share fields with each bank line — date, amount, and reference — then ranks them by how many fields agree. The best match appears first. You confirm with the Match Against Voucher action and can tick multiple vouchers against one bank line.
+Can I connect my Indian bank directly to ERPNext?
Not through the built-in Plaid feed, which currently covers the United States, Canada, the United Kingdom, and Europe but not Indian banks. Indian businesses reconcile by exporting a CSV, Excel, or MT940 statement from net banking and importing it into the reconciliation tool.
+What if a bank line has no matching entry in ERPNext?
Use the Create Voucher action on that line. ERPNext generates a Payment Entry or Journal Entry with the amount and date pre-filled, so you only add the account and party. Common examples are bank charges and interest credits.
+Is the Bank Reconciliation Tool a paid add-on?
No. The Bank Reconciliation Tool is part of core ERPNext, which is open source under GPLv3 with no licence fee. There is no separate per-user licence for reconciliation; your only costs are hosting and any implementation or support you choose to bring in.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 20 July 2026
Worked with us? Leave a Google review