Most finance teams hit the same wall in ERPNext: month-end bank reconciliation is still largely manual. ERPNext core ships a Bank Reconciliation Tool and a Bank Statement Import, but matching is one bank statement at a time, largely by hand, with limited fuzzy logic and no live bank feed. There is no native open-banking connection, no persistent multi-condition matching rules, and weak handling of the messy real-world cases — partial settlements, bundled payouts (Stripe, PayPal, marketplaces), FX differences, and bank charges — so reconciling hundreds of lines a month becomes a multi-day slog and the GL drifts out of trust.

This build-to-order app closes that gap as a proper Frappe application installed on your bench. We add a Bank Statement and Bank Statement Line DocType pair that ingests transactions from CSV, MT940/CAMT.053, or a live open-banking/aggregator API, plus a Reconciliation Rule DocType where you define ordered, weighted matching conditions (exact reference, amount within tolerance, date window, counterparty name similarity, party mapping). A server-side matching engine — implemented as whitelisted methods with frappe.enqueue background jobs so large imports never block the UI — proposes matches against existing Payment Entries, Journal Entries, Sales/Purchase Invoices and unreconciled GL rows, and can auto-create the settling Payment or Journal Entry on confirmation.

Technically it is wired the ERPNext-native way. hooks.py doc events on Payment Entry and Journal Entry keep reconciliation state in sync when documents are amended or cancelled; scheduler_events (cron/hourly) poll the open-banking feed and refresh pending statements; a client script on the reconciliation workspace gives reviewers a fast keyboard-driven match/split/ignore screen. Unmatched or ambiguous amounts route to a configurable suspense/clearing account so nothing is silently dropped, and everything respects ERPNext permissions — we ship a dedicated Role and Role Profile plus Permission Level rules so approvers, clerks and auditors see the right scope. Multi-bank and multi-currency are first-class: each feed maps to a Bank Account and Company, and FX gain/loss on settlement posts to the accounts you nominate. Reads and writes are also exposed over the Frappe REST API so an external cash-management or treasury tool can push statements or pull reconciliation status.

Because this is build-to-order, you are not downloading a fixed app off a marketplace — ECOSIRE builds your version around your banks, statement formats and chart of accounts. Engagement starts with a short scoping call to confirm banks, feed method (file vs. API/aggregator), currencies and match tolerances. We build on a staging bench, run UAT against your real (sanitised) statements, then install on your production site (Frappe/ERPNext v15 or v16, self-hosted or Frappe Cloud). Typical delivery is one working week from confirmed scope, and you receive the full source in a git repository along with a post-go-live support window.