Bank feeds
Plaid automatic feed in supported regions, or CSV, Excel and PDF statement import elsewhere, landing as Bank Transactions ready to reconcile.
Financial automation, from bank feed to reconciled book
A complete guide to the banking and accounting integrations available in ERPNext: bank statement import, automatic bank feeds, auto reconciliation, UPI and payment collection, vendor payouts over NEFT, RTGS, IMPS and UPI, and cash flow sync. Each integration is marked as native, an official app, a regional app, or third-party and custom, so you know exactly what is a configuration and what is a build.
Real-time
Bank Feeds Sync
Automated
Vendor Payments
Unified
Cashflow Sync
How money and bank data move through ERPNext
Bank data flows in through a feed or statement import, lands as a Bank Transaction, and is reconciled into the books. Payouts and collections flow back out and in.
Step 1
Bring data in
A Plaid feed syncs automatically, or you import statement files (CSV, Excel, PDF) and map columns.
Step 2
Land Transaction
Each line becomes a Bank Transaction record in ERPNext with auto-matched customer or supplier details.
Step 3
Match to vouchers
ERPNext proposes the matching voucher, which you confirm or create to balance.
Step 4
Close difference
The goal is zero difference, at which point books are reconciled and cash flow updates.
➔ Flows back: payouts and collections flow back out and in.
The native banking foundation
Because ERPNext is itself the accounting system, a large part of banking is native and needs configuration only, not a build. This is the base every other integration plugs into.
Every possible integration, in full
The tables below list the banking and accounting integrations available with ERPNext, grouped by function. The Type column shows what each one is.
Bank feeds and reconciliationTable 1 of 4
| Integration | What it does | Type |
|---|---|---|
| Statement import (CSV, Excel, PDF) | Import bank lines with column mapping into Bank Transaction | Native |
| Plaid bank feeds | Automatic incremental sync of bank transactions (region limited) | Native |
| Automatic and fuzzy party matching | Auto set the party on each bank transaction | Native |
| Bank Clearance Tool | Match clearance dates for cheques and payments | Native |
| Payment Reconciliation | Match payments and advances to invoices | Native |
Note on Plaid: Plaid covers banks mainly in the US, Canada, UK and EU. Indian banks are not on Plaid, so Indian businesses use statement import for feeds. This is an important point when scoping for an Indian client.
See the integration in action
Representative dashboard views showing auto reconciliation, vendor payouts, UPI collection and cash flow. These are illustrative mockups, not live ERPNext screenshots.
Auto reconciliation: match transactions automatically
Imported or fed bank transactions are matched to the right voucher automatically, with the party set for you. You match or create anything left over, and the difference lands at zero.
Automatic party matching maps bank lines to customers or suppliers
Matches invoices and bank transactions using amount and dates
Zero-difference targets ensure 100% bookkeeping accuracy
Auto Reconciliation
Illustrative dashboard mockup, not a live ERPNext screenshot.
How the three use cases are delivered
Three primary functional pipelines mapped to native or custom ERPNext triggers.
Vendor payments
Payment Entry then a payout over NEFT, RTGS, IMPS or UPI through RazorpayX, Cashfree or a connected banking API, with an approval workflow.
Cashflow sync
Reconciled bank balances feed the Cash Flow statement and cash position, kept current by the bank feed or regular statement import.
How a reconciliation runs, step by step
Simple workflow path ensuring bookkeeping accounts land exactly at a zero difference.
Bring the data in
A Plaid feed syncs automatically, or you import a CSV, Excel or PDF statement and map the columns.
Land it as a Bank Transaction
Each line becomes a bank transaction, with the party auto-matched where possible.
Match to vouchers
ERPNext proposes the matching payment or voucher; you confirm or create the missing one.
Close the difference
The goal is a zero difference, at which point the account is reconciled and the books are accurate.
Scoping notes for India and beyond
Critical guidelines to plan for prior to banking and compliance implementation.
🔄 Feeds
Outside India, Plaid gives an automatic feed. In India, plan for statement import since Plaid does not cover Indian banks.
💸 Payouts
For Indian vendor payments, RazorpayX is the quickest official route for NEFT, RTGS, IMPS and UPI. Connected banking APIs are an option where the bank supports them as a custom build.
💰 Collection
UPI collection runs through a gateway such as Razorpay or Paytm using payment links and QR codes and reconciles back to the invoice.
📋 Compliance
For India, GST e-invoicing and e-way bills come from the India Compliance regional app, scoped alongside the banking work.
Frequently Asked Questions
Everything you need to know about setting up and running ERPNext banking integrations.
Yes. Statement import is native and accepts CSV, Excel and PDF files, mapping the columns into bank transactions for reconciliation.
Yes, through Plaid for banks in supported regions such as the US, UK, Canada and EU. Indian banks are not on Plaid, so Indian businesses use statement import.
Yes. RazorpayX Integration, an official Frappe app, runs bulk payouts over NEFT, RTGS, IMPS and UPI with an approval workflow and 2FA. Cashfree and connected banking APIs are alternatives.
Imported or fed transactions are matched to existing vouchers automatically, with the party set where possible, and you match or create anything left until the difference is zero.
Yes, through gateways such as Razorpay and Paytm, using UPI payment links and QR codes, with the collection reconciled against the invoice.
Ready to automate yourAccounting & Banking?
Connect ERPNext to Plaid, RazorpayX, Stripe, or corporate banking APIs. Streamline ledger reconciliations and cash flow views on autopilot.
