Swiss SMEs running ERPNext hit a wall the moment they need to invoice or pay through their bank. ERPNext core has no concept of the Swiss QR-bill: it cannot produce the Swiss Cross payment slip with a valid QR-IBAN and reference (QRR/SCOR), it does not read the camt.054 bank notifications your bank exports for reconciliation, and it cannot emit an ISO 20022 pain.001 credit-transfer file to pay your suppliers in bulk. Bookkeepers end up re-keying every payment into e-banking by hand and matching statements line by line — slow, error-prone, and impossible to audit cleanly under Swiss expectations.

ECOSIRE builds a proper Frappe app (not a pile of loose customizations) that closes that gap end to end. On the outbound side, a print format and server-side generator produce a compliant QR-bill: we compute the structured reference, validate the QR-IBAN, render the Swiss QR code (with the mandatory Swiss Cross) via a hooks.py doc event on Sales Invoice submit, and attach the payment part to the PDF. On the inbound side, a whitelisted method and scheduler event ingest camt.054 XML, parse each booking entry, and auto-match it to the open invoice by reference — writing a draft or submitted Payment Entry and flagging only the exceptions a human needs to touch. For payables, we generate a valid pain.001.001.09 file from selected Payment Entries that you upload straight into your bank portal.

Technically this ships as a versioned Frappe module with its own DocTypes (e.g. a QR-Bill Settings single, a camt import log, a payment-run batch), server scripts and hooks.py document events, targeted client scripts for the invoice UI, role profiles and permission rules so only authorized users can release payment files, and scheduler events for unattended camt polling. Everything is reachable through the Frappe REST API and whitelisted methods, so your other systems can trigger generation or query reconciliation status. We also configure the Swiss chart of accounts and the MWST/VAT tax templates (standard, reduced, and accommodation rates) so your books line up with local reporting from day one. The app targets ERPNext v15 and v16.

Because this is build-to-order, nothing is downloaded and dropped in blind. We start with a short scoping call, confirm your bank's exact camt/pain flavors and your QR-IBAN details, then build against your requirements, test on a staging copy of your site, run UAT with your team, and cut over with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source, documentation, a training session, and a post-go-live support window — and the git repository is handed over to you so you are never locked in.