Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.
Kurze Fakten
- Preis
- $399.00 USD
- ERPNext-Versionen
- —
- Rüstzeit
- 30 Min
- Lizenz
- Einmalig und unbefristet
- Sprachen
- 11 Sprachen
Einmalkauf
Switzerland QR-Bill & Accounting for ERPNext
A build-to-order ERPNext app that adds Swiss QR-bill generation with QR-IBAN, camt.054 bank reconciliation, and pain.001 payment file export, plus a Swiss chart of accounts and MWST/VAT setup. ECOSIRE scopes, builds, installs, and supports it for your v15/v16 site.
$399.00USD
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Hauptfunktionen
Swiss QR-bill payment part generated on Sales Invoice submit via a `hooks.py` doc event, with the mandatory Swiss Cross and structured amount block
QR-IBAN validation and QRR (27-digit) reference computation with mod-10 recursive check digit, plus SCOR/Creditor Reference support for the non-QR-IBAN case
Compliant print format that renders the perforated payment part below the invoice and attaches it to the outbound PDF
camt.054 XML import through a whitelisted method that parses `<Ntry>` booking entries and normalizes debtor, amount, value date and reference
Automatic reconciliation matching camt entries to open invoices by structured reference, creating draft or submitted Payment Entries and routing only mismatches to an exceptions queue
Scheduler event for unattended, periodic camt.054 polling/ingestion with a per-file import log DocType for audit
ISO 20022 `pain.001.001.09` credit-transfer file export from selected Payment Entries for bulk supplier payment upload
Payment-run batch DocType that groups payables, enforces a maker/checker release step, and stamps the generated pain.001 message and payment IDs
Swiss chart of accounts template applied to the target Company with correct account types and groupings
MWST/VAT tax templates for standard, reduced and special accommodation rates, wired into Sales and Purchase taxes
Role profiles and DocPerm rules so only authorized users can release pain.001 files or post reconciliation entries
Frappe REST API and whitelisted endpoints to generate a QR-bill, fetch reconciliation status, or trigger a payment run from external systems
Configurable QR-Bill Settings single DocType for creditor details, IBAN/QR-IBAN, address type and default reference mode
Idempotent import handling that de-duplicates re-imported camt files and prevents double Payment Entry creation
Built and tested against ERPNext v15 and v16 with a bench app you install via `bench get-app` and `bench install-app`
Über dieses Produkt
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.
Warum Switzerland QR-Bill & Accounting for ERPNext wählen
Swiss QR-bill payment part generated on Sales Invoice submit via a `hooks.py` doc event, with the mandatory Swiss Cross and structured amount block
QR-IBAN validation and QRR (27-digit) reference computation with mod-10 recursive check digit, plus SCOR/Creditor Reference support for the non-QR-IBAN case
Compliant print format that renders the perforated payment part below the invoice and attaches it to the outbound PDF
camt.054 XML import through a whitelisted method that parses `<Ntry>` booking entries and normalizes debtor, amount, value date and reference
Automatic reconciliation matching camt entries to open invoices by structured reference, creating draft or submitted Payment Entries and routing only mismatches to an exceptions queue
Scheduler event for unattended, periodic camt.054 polling/ingestion with a per-file import log DocType for audit
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 2-4 weeks 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.
Was Sie bekommen
- Installable, versioned Frappe app (full source) for your ERPNext v15/v16 site
- Installation and configuration on your environment, including QR-Bill Settings, Swiss CoA and MWST tax templates
- Technical documentation: DocType reference, hooks/doc-events, whitelisted API endpoints and scheduler jobs
- End-user guide plus a live training session for your bookkeeping team
- UAT on a staging copy of your site with sign-off, plus a documented cutover and rollback plan
- Post-go-live support window for defect fixes and questions
- Git repository handover so you own and can extend the code
- Sample camt.054 / pain.001 test fixtures and a reconciliation test checklist
Für wen das ist
Swiss SME bookkeeper
Handles day-to-day invoicing, supplier payments and month-end in ERPNext. Needs QR-bills that print correctly, camt.054 statements that reconcile themselves, and a pain.001 file they can upload to e-banking instead of re-keying every transfer.
Finance manager / fiduciary (Treuhänder)
Owns the correctness of the books and MWST filing across one or several client companies. Wants the Swiss chart of accounts and VAT rates set up properly, a clean audit trail on every imported statement, and a maker/checker control before payment files go out.
ERPNext administrator / IT lead
Responsible for the Frappe site and integrations. Cares that this is a real app with sane DocTypes, hooks and role permissions, exposed through the REST API, testable on staging, upgrade-safe across v15/v16, and delivered as a git repo they can maintain.
Swiss SME owner-operator
Runs a small trading or services company on ERPNext and wants to stop paying for a separate Swiss banking tool. Needs a fixed-scope build, a predictable timeline, and support after go-live.
Installationsübersicht
Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei der Switzerland QR-Bill & Accounting for ERPNext-App von Ihrem Konto-Dashboard herunter.
Fügen Sie die App zu Ihrer Bank hinzu
Extrahieren Sie die ZIP-Datei in den Apps-Ordner Ihrer Bank oder führen Sie „bench get-app“ mit dem Pfad zur extrahierten App aus.
Installieren Sie es auf Ihrer Website
Führen Sie „bench --site SITE_NAME install-app APP_NAME“ gefolgt von „bench migrate“ aus, um Switzerland QR-Bill & Accounting for ERPNext zu installieren und sein Schema anzuwenden.
Aktivieren Sie Ihre Lizenz
Öffnen Sie die ECOSIRE-Lizenzeinstellungen auf Ihrer Website und aktivieren Sie Ihren Lizenzschlüssel. Erfordert die kostenlosen Apps ecosire_connect und ecosire_license_client.
Wie Switzerland QR-Bill & Accounting for ERPNext im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Swiss QR-bill on invoices | Compliant payment part with QR-IBAN, generated on submit | Possible but you build/validate the reference and QR yourself | Often present, but generic and not tuned to your bank/reference mode | |
| camt.054 reconciliation | Auto-match by reference, exceptions queue, idempotent import | Hand-built parser and matching logic, long to get right | Varies; matching rules often shallow or not configurable | |
| pain.001 payment export | Validated pain.001.001.09 with maker/checker release | You must implement and validate the ISO 20022 schema | Sometimes offered, schema version and controls may not fit | |
| Swiss CoA & MWST setup | Configured and wired into Sales/Purchase taxes | You research and build the templates | Rarely bundled; usually a separate step | |
| Fit to your bank & scope | Validated against your real camt/pain samples | Fully custom but slow and expensive to reach parity | One-size-fits-all; edge cases are your problem | |
| Delivery & timeline | Build-to-order, 2-4 weeks from confirmed scope | Open-ended; depends on in-house capacity | Instant install, but integration/config still on you | |
| Support & ownership | Post-go-live support window + git repo handover | You own everything, including all maintenance | Vendor support tiers; source usually closed | |
| v15/v16 compatibility | Built and tested on v15 and v16 | Your responsibility to keep upgrade-safe | Depends on the vendor's release cadence |
Häufig gestellte Fragen zu Switzerland QR-Bill & Accounting for ERPNext
+Is this a ready-made app I can download and install today?
No. It is build-to-order. ECOSIRE scopes it to your bank and your ERPNext site, then builds, installs and supports it. There is no instant download and no marketplace listing — you request a quotation and we deliver a tailored app.
+How long does delivery take?
Typically 2-4 weeks from confirmed scope. The scoping call defines your QR-IBAN details, your bank's exact camt.054 and pain.001 flavors, and your VAT setup; once that is signed off we build, test on staging, run UAT and cut over on an agreed date.
+Which ERPNext versions are supported, and how do updates work?
We build and test against ERPNext v15 and v16, packaged as a standard Frappe bench app. After go-live you get a support window for fixes; because you receive the full git repository, your team or ECOSIRE can carry the app forward across future ERPNext upgrades under a maintenance arrangement.
+Will it work with my specific Swiss bank?
That is exactly what the scoping call confirms. Swiss banks issue camt.054 and accept pain.001 with minor structural differences, so we validate against your bank's real sample files during the build and test reconciliation and payment upload against your actual formats before go-live.
+Does it handle both QR-IBAN (QRR) and standard IBAN with Creditor Reference (SCOR)?
Yes. The generator supports the QR-IBAN case with a 27-digit QRR reference (mod-10 recursive check digit) and the standard IBAN case with a structured Creditor Reference (SCOR), as well as bills without a reference, selectable in QR-Bill Settings.
+Is the camt reconciliation and pain.001 release safe to run on production?
The reconciliation is idempotent — re-importing the same camt.054 file will not create duplicate Payment Entries — and only clean matches post automatically while exceptions go to a review queue. Payment-file release is gated behind a maker/checker permission so an authorized user must approve before a pain.001 is generated.
+Will you set up the Swiss chart of accounts and MWST rates too?
Yes. Configuration of the Swiss chart of accounts and the MWST/VAT tax templates (standard, reduced and accommodation rates) wired into Sales and Purchase taxes is part of the delivery, so your books and tax reporting are aligned from day one.
Angebot anfordern
Switzerland QR-Bill & Accounting for ERPNext
A build-to-order ERPNext app that adds Swiss QR-bill generation with QR-IBAN, camt.054 bank reconciliation, and pain.001 payment file export, plus a Swiss chart of accounts and MWST/VAT setup. ECOSIRE scopes, builds, installs, and supports it for your v15/v16 site.
- Swiss QR-bill payment part generated on Sales Invoice submit via a `hooks.py` doc event, with the mandatory Swiss Cross and structured amount block
- QR-IBAN validation and QRR (27-digit) reference computation with mod-10 recursive check digit, plus SCOR/Creditor Reference support for the non-QR-IBAN case
- Compliant print format that renders the perforated payment part below the invoice and attaches it to the outbound PDF
- camt.054 XML import through a whitelisted method that parses `<Ntry>` booking entries and normalizes debtor, amount, value date and reference