EU finance teams running ERPNext quickly hit a wall when it comes to bank payments and collections. ERPNext core can record a Payment Entry and generate a Bank Transaction, but it has no native way to produce a SEPA-compliant pain.001.001.09 credit transfer file, no direct debit engine with mandate lifecycle handling, and no built-in importer for camt.053/camt.054 bank statements. Teams end up keying payments into bank portals by hand, chasing mandates in spreadsheets, and reconciling statements line by line — slow, error-prone, and impossible to audit at scale.

ECOSIRE builds a proper Frappe app (ecosire_sepa) that fills exactly this gap inside ERPNext. It ships new DocTypes — SEPA Mandate, SEPA Payment Batch, SEPA Direct Debit Batch and a camt import staging DocType — plus link fields on Customer, Supplier and Bank Account for IBAN/BIC. Payment Entries and Payment Requests are grouped into a batch, and a whitelisted server method renders standards-compliant XML: pain.001 for outgoing credit transfers and pain.008 for direct debit collections, with the correct SeqTp handling (FRST/RCUR/OOFF/FNAL) driven by each mandate's usage history. IBANs and BICs are validated on save via hooks.py doc events (mod-97 checksum on the IBAN, BIC format and country-consistency checks) so malformed account data never reaches the bank.

On the inbound side, the suite parses camt.053 (end-of-day) and camt.054 (debit/credit notifications) into ERPNext Bank Transactions and drives auto-reconciliation against open Payment Entries, Sales Invoices and the direct-debit batches — matching on end-to-end IDs, amounts and remittance information, and flagging R-transactions (returns, refunds, reversals) so a bounced direct debit automatically reopens the invoice and updates the mandate's sequence state. Mandate management is first-class: a full lifecycle (draft, active, suspended, expired, cancelled) with unique mandate references, signature-date capture, first-use tracking and the 36-month dormancy rule enforced by a scheduler event in scheduled_tasks. Role profiles and permission rules keep file generation and mandate approval separate from data entry, and everything is reachable through the Frappe REST API and whitelisted methods for integration with your bank connectivity or treasury tooling.

Because this is build-to-order, nothing is auto-provisioned. We start with a scoping call to confirm your bank(s), the exact ISO 20022 schema versions they require (banks differ on pain.001 variants and country addenda), your reconciliation rules and your ERPNext version (v15 or v16). ECOSIRE then builds your version of the app, tests it on a staging bench with your real message samples, walks your team through UAT, and installs it to production with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the installable source, a git repository handover, technical and user documentation, a training session and a post-go-live support window — you own the code and can extend it in-house afterward.