What the Swiss QR-bill is
One payment slip, fixed by a Swiss standard, printed on the invoice instead of tucked in beside it.
The QR-Rechnung is a strip across the foot of a page, 210 × 105 mm, made of a receipt on the left and a payment part on the right. The payment part holds a Swiss QR Code that carries the entire payment instruction in machine-readable form: who is being paid, into which account, how much, in which currency, and under which reference.
Two things follow from that. The payer never types an account number, because their banking app reads it out of the code and fills its own transfer form. And the money arrives carrying a reference that you chose, which is what lets a credit on your bank statement be tied back to one invoice rather than to a name and an amount that three of your clients happen to share.
The layout is not a design decision. The size of the strip, the position of each block, the length of every field and the contents of the code are all fixed, which is why a banking app can read a QR-bill from a business it has never seen before and get it right the first time.
- QR-Rechnung / QR-bill
- The Swiss standard payment part carried on an invoice. It is produced for that one invoice and belongs to it.
- Payment part
- The right-hand section of the strip, with the Swiss QR Code. This is what the payer scans, or hands in at a counter.
- Receipt
- The left-hand section, which stays with the payer as proof of what they instructed their bank to do.
- QR-IBAN
- A second account identifier your bank issues for QR-bill collections. It points at the same account as your ordinary IBAN but changes which reference the bill must carry.
- camt.053
- The ISO 20022 XML bank statement you export from e-banking. It carries the reference the payer actually used, which is what makes automatic matching possible at all.
Why the orange and red slips are gone
Two incompatible stocks of paper became one machine-readable payment part.
For decades a Swiss invoice went out with a pre-printed slip attached to it. There were two, and they were not equals. The orange ESR, the Einzahlungsschein mit Referenznummer, carried a reference number, so a payment made on it came back to the payee as structured data that software could match. The red Einzahlungsschein carried no reference, so the payee matched payments by reading names off a statement.
Both were ordered from a bank as physical stock, in fixed formats, and a business that wanted references had to buy into the orange system specifically. The Swiss migration of payment traffic to ISO 20022 replaced the pair of them with a single payment part that can carry a reference or not, in one format every Swiss financial institution reads the same way. The old slips were withdrawn; an invoice that still carries one cannot be paid the way it was printed to be paid.
- You no longer order slips from a bank. The payment part is generated for each invoice and printed with it.
- A structured reference is no longer the privilege of one slip type. Any QR-bill can carry one.
- The payment part is part of the document, so there is no separate piece of paper to lose or to attach to the wrong invoice.
- Scanning replaced typing. The payer confirms fields that are already filled rather than copying an account number by hand.
What the payment part must contain
A fixed set of fields, each with a length the standard sets and a rule about when it may be left out.
A payment part is not free-form. The printed block has to fit a strip of a known size and the code has to stay readable by a scanner, so every field has a maximum length and the caps are real caps rather than guidance. A long company name has to be shortened somewhere, and it is better that you decide where.
| Field on the payment part | What it carries | The limit it must respect |
|---|---|---|
| Account | The creditor IBAN or QR-IBAN the money is paid into | A Swiss (CH) or Liechtenstein (LI) account, check digits validated by ISO 7064 mod-97-10 |
| Creditor | Who is being paid: name, street, postal code, town, country | 70 characters for the name, 35 for the town |
| Currency | The currency of the payment | CHF or EUR, and nothing else |
| Amount | What is being asked for | 0.01 to 999'999'999.99 |
| Reference | The structured reference the payment travels under | A QR reference on a QR-IBAN, a Creditor Reference on an ordinary IBAN, or none |
| Debtor | Who is being asked to pay, the Zahlbar durch block | The same 70- and 35-character caps, and a complete address or nothing |
| Additional information | A free message, in practice the invoice number | 140 characters, and this is the field that reaches the statement |
| Language | The language the printed wording appears in | German, French, Italian or English |
The debtor block is the one most people get half right. Name, street, postal code, town and a two-letter country code are one unit: with three of the five known, the correct output is an empty block the payer fills in themselves, not a partial address printed as though it were complete.
IBAN or QR-IBAN, and why it decides your reference
They are the same length, they look alike, and they are not interchangeable.
An ordinary IBAN is the account number you already have. A QR-IBAN is a second identifier your bank issues on request for QR-bill collections. It points at the same account, but it tells the banking system that payments made to it carry a QR reference, which your bank then delivers to you as structured data on the statement.
From that follows a rule with no exceptions: a QR-IBAN must carry a QR reference, and an ordinary IBAN must not. This is the single most common way a QR-bill is built wrong, and the symptom is not a warning but a payment that will not go through.
| Question | QR-IBAN | Ordinary CH or LI IBAN |
|---|---|---|
| Where it comes from | Your bank issues it for QR-bill collections | The account number you already use |
| Reference it must carry | A QR reference (QRR) | A Creditor Reference (SCOR), or no reference |
| Reference it may not carry | A Creditor Reference | A QR reference |
| What you do to get one | Ask your bank. It is not something you can derive yourself | Nothing, you already have it |
| What it changes on the statement | The reference is delivered as a structured field | The reference is delivered as a structured field |
The three reference types
QR reference, Creditor Reference, or no reference. The choice decides whether a payment can ever be matched back by machine.
- QR reference (QRR)
- The Swiss structured reference, and the only one a QR-IBAN may carry. A 26-digit body plus a recursive mod-10 check digit, so a transposed digit is caught before the payment is made rather than after it has landed somewhere unhelpful.
- Creditor Reference (SCOR)
- The international structured reference, defined by ISO 11649. It does the same job as a QR reference and is the correct choice on an ordinary IBAN, where a QR reference would not be legal.
- No reference (NON)
- Permitted by the standard. The payment then arrives identified by the payer's name, the amount, and whatever they typed in the message field, which means you match it by reading rather than by machine.
The reference is the point of the whole exercise. It travels with the payment through the banking system and comes back on the camt.053 statement you export from e-banking, and it is the only field a piece of software can rely on to tie a credit to exactly one invoice. Without it you are back where the red Einzahlungsschein left you: a name, a date and an amount.
Solory always attaches one of the two structured references and never the third. A QR-IBAN gets a QR reference derived from the invoice number; an ordinary IBAN gets a Creditor Reference. The invoice number also goes into the message field either way, because that is the field forwarded to the statement.
What your client does with it
From the payer's side, a QR-bill is a scan and a confirmation.
They receive one document
The payment part is a page of the invoice PDF, or the strip at the foot of a printed page. There is no second attachment to lose and nothing to ask you for separately.
They open the scanner in e-banking or TWINT
The Swiss QR Code can be scanned with TWINT and with every Swiss banking app. Nothing has to be installed, and your client does not create an account anywhere in order to pay you.
The transfer form fills itself
Account, creditor name and address, amount, currency and the reference all come out of the code. The payer checks the figures and confirms them instead of retyping them, which is where wrong-account and wrong-reference payments used to come from.
Or they pay it on paper
The payment part detaches and can be handed in at a counter or posted to a bank, with the receipt half staying behind. A QR-bill nobody scans is still a valid payment order.
A payer outside Switzerland can settle the same bill by ordinary bank transfer, because the account, the creditor and the reference are printed in readable text beside the code as well as encoded inside it. The QR Code is a convenience for Swiss banking apps, not the only route to the account.
The mistakes that get an invoice sent back
Almost all of them are one stored field, not a step somebody forgot on the day.
A QR-bill fails in one of two ways. Either the payment part cannot be produced or read at all, so nothing is paid; or it is paid and then cannot be tied to anything, so the invoice stays open in your books while the money sits in your account. Both are usually traceable to a single field in a client record or in your business settings.
- The wrong reference type for the account: a QR reference on an ordinary IBAN, or a Creditor Reference on a QR-IBAN. Neither is a matter of preference.
- A mistyped IBAN. The check digits catch most typos, so the usual symptom is not a payment going to a stranger but no payment part appearing at all.
- A currency that is not CHF or EUR. A QR-bill may carry no other currency, so an invoice in USD or GBP is an invoice with no payment part on it.
- An amount outside 0.01 to 999'999'999.99. This is also why a credit note never carries a payment part: a QR-bill is an instruction to pay and cannot be zero or negative.
- An incomplete debtor address. Street, postal code, town and a two-letter country code are one block, and a partial address prints nothing rather than part of something.
- A creditor name or town over the field caps, 70 and 35 characters. Something has to give, and a silently truncated legal name on a payment instruction is the wrong thing to give.
- No structured reference on an invoice you will later have to reconcile. The payment arrives; identifying it is manual from that point on.
- A payment part that no longer matches the invoice in front of it. If the total changes after the PDF was made, the two pages disagree, and a careful client stops and asks which one is right instead of paying either.
How Solory prints it, and what it does not do
Everything above is the standard. This is the part of it a Solory account takes off your hands, and the part it deliberately does not.
- The payment part is drawn from the invoice's own figures and from the bank account that invoice points at, and appended to the PDF as its own page so the payer can detach it cleanly.
- A structured reference is always attached, and the account decides which: a QR reference on a QR-IBAN, a Creditor Reference on an ordinary IBAN. There is no dropdown to get wrong.
- The IBAN is validated by shape and by ISO 7064 mod-97-10 check digits before anything is drawn, so a typo skips the payment part instead of producing a tidy PDF nobody can pay.
- One eligibility check drives both the PDF and the interface, and it names every missing prerequisite at once, so the form tells you why no payment part will appear before you download anything.
- The payment part is printed with a Unicode font, so an ä, an ö, a ü or a Hungarian accent in a name prints as itself.
- The QR-bill is not a paid extra. It is on every plan, including Free at CHF 0.
- No eBill. The QR-bill here is a printed payment part on a PDF; nothing is delivered over the Swiss eBill network.
- No card payment and no pay-now link on an invoice. Your client pays by transfer or TWINT from the payment part, and there is no checkout page.
- No bank connection and no open banking. Statements arrive as a camt.053 or camt.054 file you export from e-banking yourself, and that import is on the Business plan at CHF 89 per month.
- No blanket automatic reconciliation. Only a credit whose structured reference exactly matches an open invoice is matched on its own; an amount match is a suggestion you confirm, and an ambiguous amount produces no suggestion at all.
- The AI assistant drafts and asks for approval. It plans read-only, waits for an explicit confirmation before any write, and has no step in its vocabulary that sends an invoice, an estimate or a reminder to a client.
- Not a Treuhänder, and not double-entry bookkeeping. Solory keeps the documents, the payments and the Swiss reference material; the judgement calls stay with you and your Treuhänder, who can be given read-only access on Professional and above.
Questions people ask
What is the Swiss QR-bill?
The QR-bill (QR-Rechnung) is the Swiss standard payment slip carried on an invoice: a 210 × 105 mm strip made of a receipt and a payment part, with a Swiss QR Code holding the creditor, the account, the amount, the currency and a structured reference. It replaced the orange ESR and the red Einzahlungsschein. Every Swiss banking app and TWINT can read it, so the payer scans and confirms instead of typing an account number.
Can I still send the old orange or red payment slip?
No. The orange ESR and the red Einzahlungsschein were withdrawn when Swiss payment traffic moved to ISO 20022, and the QR-bill took their place. An invoice that still carries one of the old slips cannot be paid the way it was printed to be paid, so it has to be reissued with a payment part.
What is the difference between an IBAN and a QR-IBAN?
An ordinary IBAN is the account number you already have. A QR-IBAN is a second identifier your bank issues for QR-bill collections, pointing at the same account. The difference matters because a QR-IBAN must carry a QR reference (QRR) and an ordinary IBAN must not, taking a Creditor Reference (SCOR) instead. They are the same length and you cannot tell them apart by eye, so check your bank's documentation.
Which reference should I put on my QR-bill?
The account decides, not you. A QR-IBAN takes a QR reference, a 26-digit body with a recursive mod-10 check digit. An ordinary CH or LI IBAN takes an ISO 11649 Creditor Reference. The standard also permits a bill with no reference, but then every payment has to be identified by hand, because nothing structured comes back on your statement.
What has to be on the payment part?
The creditor's IBAN or QR-IBAN, the creditor's name and address, the currency (CHF or EUR only) and the amount, plus the reference where the account requires one. The debtor block and the message field are optional, and every field has a fixed cap: 70 characters for a name, 35 for a town, 140 for the message. Your line items, MWST breakdown and UID stay on the invoice page, not on the payment part.
Why does my invoice have no payment part on it?
A QR-bill is only produced when the invoice can legally carry one: a valid CH or LI IBAN, a complete postal address, a creditor name, CHF or EUR as the currency, and an amount between 0.01 and 999'999'999.99. In Solory the invoice PDF is still produced when one of those is missing, simply without a payment part, and the app names the field that is missing rather than leaving you to guess.
Can a client outside Switzerland pay a Swiss QR-bill?
Yes, by ordinary bank transfer. The account, the creditor and the reference are printed in readable text on the payment part as well as encoded in the QR Code, so a payer whose bank cannot scan a Swiss QR Code can still enter them manually. The QR Code is a convenience for Swiss banking apps rather than the only way to the account.