The QR-bill in practice, from issuing to bank matching

Three reference variants, two vocabularies to name them

A QR-bill carries a machine-readable payment part, and that part does not have a single form. smallinvoice documents three variants, without reference, with QR reference and with the structured international SCOR reference, generated automatically in the document's language. KLARA documents the same three cases under other names, without QR, with Creditor reference, and QR-IBAN combined with a QRR reference. The vocabulary changes from vendor to vendor; the question put to the company stays identical: which reference will the invoice carry.

The QR-IBAN is not a secondary setting. KLARA puts it in the very name of the variant, and its documentation makes it mandatory for eBill sending. At Crésus, eBill issuing assumes an active QR-IBAN, an entry in the commercial register, an issuing contract and registration fees of CHF 20. The number printed on the invoice therefore conditions what will be possible next, and these two vendors write it explicitly in their documentation, read on 23 August 2026.

The rest hangs on the template. Banana Comptabilité Plus documents a CH10 layout for the Swiss QR-bill as well as a payment QR code. SelectLine documents automated generation from commercial documents, with customisation through the form editor. bexio documents native generation together with automatic payment matching. Three close formulations, three very different depths of configuration as soon as an SME wants its own template and its own layout.

Issuing is documented everywhere, at entry prices from CHF 15 to CHF 69

Of the eleven products studied, ten explicitly document issuing a QR-bill. The eleventh, Odoo, is a special case, since its Swiss localisation documentation read on 23 August 2026 still describes the BVR and the ISR and the 2018 change to 7.7 per cent, without mentioning the QR-bill, while the vendor elsewhere documents the Swiss payment format pain.001.001.03.ch.02. Issuing is therefore not the point that separates Swiss software.

What separates them is the entry ticket and what that ticket contains. smallinvoice opens its API from the STARTER plan at CHF 15 per month, while SelectLine reserves its own for the Premium edition at CHF 119 per user per month, the base edition staying at CHF 69. WinBIZ lists CHF 64 before tax per access on annual invoicing and CHF 74 on monthly, with an initial period of twelve months and three months' written notice.

Reading a supplier's invoice requires tooling that issuing does not

Five documentations describe reading a received invoice. WinBIZ announces the QR-bill for issuing as for reception. Crésus documents issuing and the processing of received invoices. SelectLine documents reading supplier QR-bills and taking them into open items. Infoniqa documents the QR invoice for issuing and its reading by QR scanner, with a scan of supplier invoices on the ONE 50 side. Abacus documents a native QR-bill for issuing as for reading.

Elsewhere, the page read stops at issuing. bexio's QR-bill page describes generation and automatic payment matching, without describing the reading of a received invoice. At smallinvoice, the API specification has no creditors or expenses endpoint, so an automated supplier flow is built outside the interface. Run my Accounts treats the question differently: the provider takes the documents in charge and invoices them per unit, with post-scanning at Fr. 2.- per document.

A printed QR becomes a receipt only when the camt comes back

The sensitive point is not generating the QR, it is the bank's return. Crésus documents pain.001 for orders, pain.002 for statuses, camt.053 and camt.054 for movements and QR receipts. WinBIZ documents fetching and processing camt.053 and camt.054 files, with automatic matching against sales, purchase and payroll documents. Infoniqa documents pain.001.001.09 with fallback to pain.001.001.03 and a synchronisation of the SIX bank file.

The access routes to these files differ more than the formats themselves. Crésus Banking goes through EBICS and a PostFinance API channel. bexio goes through SIX's bLink to take over accounts and transactions. Banana imports camt.053 and camt.054, the Camt ISO 20022 Switzerland extension and MT940; its PAIN.001 orders remain marked beta. At KLARA, Raiffeisen and Basler Kantonalbank require an e-banking login at each fetch, PostFinance goes through a signed paper form, and movements prior to activation do not come back.

eBill leaves from the same software and yet takes another network

Three vendors appear themselves as eBill network partners: Epsitec SA for Crésus, ePost Service AG for KLARA and Abacus Research AG. Sending then leaves directly from the software. Crésus charges 20 centimes per dispatch before tax and documents issuing only; its help page states that Crésus Facturation cannot receive eBill invoices. KLARA requires a QR-IBAN for sending. The register of network partners kept by SIX allows checking this status before any commitment.

The others go through a carrier. SelectLine documents transmission via PostFinance, specifying that the client does not need a PostFinance account. WinBIZ goes through PostFinance's e-invoicing platform, for sending as for receiving. Infoniqa requires a contract with PostFinance or PayNet and the E-Services licence option; its documentation states that there is no other provider for now. bexio points to a third-party Marketplace application, eBill by iomarket AG, paid on top.

Elsewhere again, the connection reads differently. Banana lists automated sending via eBill among the functions not available for now in its Offers and Invoices application. smallinvoice presents eBill as a function of the Pingen integration. At Odoo, the existing building blocks are OCA community modules the vendor does not maintain. Run my Accounts documents no eBill sending on the day of reading and does not appear among the network partners published by SIX.

What the documentation no longer says has to be checked at the source

A ticked box in a comparison table does not replace the help page. Odoo gives the example: its real behaviour is further along than its Swiss localisation documentation, which forces checking version by version before committing. Infoniqa publishes 985 help articles in German against 452 in French and 28 in Italian, and its commercial site exists only in German, the French address redirecting to the German home page.

The data exit deserves the same examination as the entry. WinBIZ writes that access to WinBIZ Cloud data ceases at the end of the contract and recommends printing or archiving the accounts as PDF before leaving, the export to XLS, CSV or XML being done closing document by closing document. An archive of issued QR-bills and a recoverable database are not the same thing.

What we do when a QR receipt does not find its invoice

We sell no licences. Our work begins where the vendor's documentation stops: on the choice of the reference variant, on connecting the software to the bank's camt file, on taking over creditors when the interface does not expose them. We read your vendor's help pages, we set up a trial run with your own documents, and we document what was tested as well as what was not.

When a match fails, the cause is to be found in the reference typed by hand, in the camt.054 advice that does not arrive, or in the supplier sending a PDF without a payment part. We treat these cases one by one, with the software you already use and the bank you work with, without starting from a blank sheet.

Where these answers come from

Every fact on this page can be checked at the source. The links open directly the website of the vendor or body concerned.

• KLARA, setting up the bank connection and the QR-billThree QR-bill variants, without QR, Creditor reference, QR-IBAN with QRR, and QR-IBAN mandatory for eBill sending
• smallinvoice, integrationsNative connectors, including Pingen for eBill and mail, PostFinance E-Finance for reconciliation, exports to Banana, Infoniqa ONE 50 and Topal
• Crésus Facturation, eBill help pageeBill sending via the SIX network, 20 centimes per dispatch, CHF 20 registration fees, active QR-IBAN required, and no eBill reception
• Crésus Facturation, product specificationsSupported platforms, single-user write lock, multi-client capability, multilingual and multi-currency options
• SelectLine, ERP pageAutomated generation of the QR-bill from commercial documents and customisation through the form editor
• bexio, QR-Rechnung pageNative generation of the QR-bill with automatic payment matching, with no mention of eBill or Peppol on this page
• WinBIZ, product pageIncluded modules, QR-bill for issuing and reception, camt file processing and data hosting in Switzerland
• Infoniqa, E-Services group of the help centreeBill subject to a PostFinance or PayNet contract and the E-Services licence option, with no other documented provider
• Odoo, Swiss fiscal localisationDocumented content of the Swiss localisation, payment format pain.001.001.03.ch.02, mentions of ISR and 2018 rates
• Banana Comptabilité Plus, Offers and Invoices applicationAutomated invoice sending via eBill appears among the functions not available for now
• Register of eBill network partners, SIXOfficial list of eBill network partners, allowing to check whether a vendor sends directly or via a carrier
• Official directory of Peppol Certified Service ProvidersList of certified Peppol providers, to be consulted separately from the QR-bill question

SURVEY OF 23.08.2026

Frequently asked questions