From QR-bill to camt.054: closing the loop between invoice and bank statement
How a Swiss QR-bill reference travels from invoice to payment order to the bank's camt.054 notification and camt.053 statement, what a matching process can and cannot decide by itself, and which controls keep receivables honest.
- By
- Finray
- Published
- Updated
- Reading time
- 8 min
How does a QR-bill payment find its way back to the invoice?
Through the structured reference. The invoice issuer prints a reference in the QR-bill, the payer’s order carries that reference to the payer’s bank, and the creditor’s bank reports it back in a camt message, as the Swiss guidelines describe it. When the reference, the amount and the currency agree with an open invoice, the match is straightforward. When they do not, a person has to decide. This note follows the loop step by step and shows where software helps and where it should stop.
What does the QR-bill put into the loop?
The QR-bill is defined in the Swiss Implementation Guidelines published by SIX Interbank Clearing. Version 2.4 is valid from 14 November 2026, and version 2.3 remains valid until November 2027. The QR code in the payment part carries the creditor’s account and address, the currency, the amount if it is fixed, a reference, and additional information. For matching, three things matter.
| Element | Rule | Why it matters for matching |
|---|---|---|
| Account | IBAN, or a QR-IBAN based on a QR-IID between 30000 and 31999 | The type of account decides which reference type is allowed |
| Reference type | QRR with a QR-IBAN, SCOR with an IBAN, NON for none | Tells the creditor whether a structured reference exists |
| Reference | 26 digits plus a modulo 10 recursive check digit for QRR; RF plus two check digits and up to 25 characters in total for SCOR | A well-formed reference can be validated on arrival |
Amounts lie between 0.01 and 999,999,999.99 in CHF or EUR. Version 2.4 states that the QR-IBAN and the QR reference are exclusively for CHF; for EUR invoices only the combination of an IBAN and a creditor reference, or an IBAN and an unstructured message, is possible. The guidelines also provide an optional billing information line, starting with two slashes, which is not forwarded with the payment and must not contain personal data.
The practical consequence is that a matching process should store, for every issued invoice, the reference exactly as printed, the account, the currency and the amount. Without those four, a later comparison is guesswork.
What does the payer’s order do with the reference?
The payer scans the code, or enters the data, in e-banking, mobile banking or their own software, which creates a credit transfer. When the payer’s own software sends the order, it is typically a pain.001 message, in which the reference goes into the creditor reference information of the credit transfer transaction; in e-banking and mobile banking the bank captures the order in its own system. The camt guidelines describe the reference as originally delivered to the bank in that element of the credit transfer, and then forwarded to the creditor in the later reports. If the payer types the reference by hand, a typing error is possible, which is why the check digit exists.
The payer’s side is outside the creditor’s control. Some payers pay several invoices in one batch, some pay late, some pay a partial amount. The creditor sees only what the bank reports.
What does the bank report back?
The creditor’s bank reports the credit in a camt message. The Swiss guidelines cover three: camt.052 for intraday reports, camt.053 for the day-end statement, and camt.054 for credit and debit notifications.
| Message | Timing | Balances | Typical role in matching |
|---|---|---|---|
| camt.054 | Event-driven | None | Early sight of a credit; detail of batch bookings |
| camt.053 | Day end | Opening and closing booked balances | Booking-relevant record; control total |
For an entry with a QR reference or a creditor reference, the structured reference is in the creditor reference information of the transaction details, and the entry carries a bank transaction code. For QR-IBAN entries, the guidelines describe an entry reference made of the QR-IBAN and, in one variant, the first six characters of the QR reference; for IBAN entries with a creditor reference, the IBAN and positions 5 to 10 of the reference. These entry references depend on the bank’s batch booking logic, so they are poor keys for matching, and the full structured reference in the transaction details is the better one. The statement shows the account itself, not the QR-IBAN.
A bank may book several payments as a single entry. In the internal variant, the camt.053 shows the batch total and lists the lines. In the external variant, the camt.053 shows only the total, and the entry can refer to one camt.054 message that holds the lines. Not every bank offers the external variant. A company that receives batch bookings must therefore import both message types, or learn which resolution its bank uses.
What cases does a matching process meet?
Most receipts are simple, but the exceptions decide whether the ledger can be trusted.
| Case | What the data shows | Safe handling |
|---|---|---|
| Exact match | Reference found, amount and currency equal to the open invoice | Propose the match for confirmation |
| Short payment | Reference found, amount lower | Keep the invoice open; show the difference; a person decides on discount, write-off or reminder |
| Overpayment | Reference found, amount higher | Hold the excess as unallocated; a person decides on refund or credit |
| Two invoices, one payment | Same payer, amount equals the sum of two invoices, batch or free text | Present candidate combinations; a person confirms |
| No usable reference | Amount and name only | Present candidates by amount and payer; a person chooses |
| Duplicate payment | Reference already settled | Flag, hold, and decide on a refund |
| Reference unknown | Well-formed reference with no invoice | Hold as unallocated; do not book as revenue |
Notice that the safe handling is a proposal in almost every row. Software can sort, rank and highlight candidates. The decision to close an invoice with a difference, or to treat a credit as revenue, has accounting and sometimes tax consequences, and that is a person’s call.
What does a worked example look like?
The figures are synthetic. A consultancy has three open QR-bill invoices, all in CHF and with QR references.
| Invoice | Amount (CHF) | Customer |
|---|---|---|
| 2026-0412 | 4,860.00 | Customer A |
| 2026-0398 | 1,200.00 | Customer B |
| 2026-0377 | 2,500.00 | Customer C |
During the day the bank sends three notifications and, in the evening, a statement.
| Notification | Amount (CHF) | Reference points to | Outcome |
|---|---|---|---|
| 1 | 4,860.00 | 2026-0412 | Exact match; proposed for confirmation |
| 2 | 1,140.00 | 2026-0398 | Short by 60.00; invoice stays open; a person decides on the difference |
| 3 | 2,500.00 | 2026-0377 | Exact match; proposed for confirmation |
The statement shows an opening balance of CHF 20,000.00, three credits of 4,860.00, 1,140.00 and 2,500.00, one supplier debit of 3,415.50, and a closing balance of CHF 25,084.50. Two checks follow. The statement ties: 20,000.00 plus 8,500.00 minus 3,415.50 equals 25,084.50. And the credits on the statement, 8,500.00 in total, equal the sum of the three notifications. If either check fails, something was missed or imported twice, and the books should wait.
Invoice 2026-0398 is the interesting one. The reference is right and the amount is not. The customer may have assumed a 5 percent discount (60.00 on 1,200.00), or may have paid the wrong amount. Closing the invoice automatically would hide a dunning question and a possible revenue difference.
What controls keep the loop honest?
| Risk | Control kept outside the matching logic | Owner |
|---|---|---|
| Reference typed wrongly by the payer | Validate the check digit on arrival; treat a failure as unallocated | Accounting software |
| Same notification or statement imported twice | Use message and statement identifications to refuse a repeat | Accounting software |
| Missing notification | Reconcile the sum of notifications to the day-end statement | Bookkeeper |
| Auto-closing of invoices with differences | Tolerance rules set by finance and approved; anything outside goes to a person | Finance lead |
| Credits parked indefinitely | Ageing report of unallocated credits with an owner and a date | Finance lead |
| Altered invoice bank details | A change of account or QR-IBAN on the invoice template is an approved change by a second person | Finance lead |
| Manual match edited later | Matches and corrections recorded in an append-only audit trail | Software owner |
What does Corebanq Accounting do today in this loop?
Corebanq Accounting from Finray creates QR-bill invoices that can be printed or saved from the browser. It can also read incoming QR-bills from a PDF, an image or the camera. Receivables are tracked in an ageing view, dunning reminders are available, and recurring invoice templates create drafts. On the bank side, the product imports camt.053 statement files and camt.054 notification files that the user uploads.
What it does not do: it has no live bank feeds, and no EBICS or open banking connection. This note does not describe automatic matching of imported entries to invoices, and the table of cases above is a design discussion, not a feature list. See Corebanq Accounting for the current scope.
Where to read more
The glossary has entries for the QR-bill, camt.054, camt.053 and pain.001. The companion note Swiss VAT effective method in software follows the same invoices into the VAT return.
Frequently asked questions
- Which reference should a QR-bill use for automatic matching?
- A structured reference. The guidelines offer the 27-digit QR reference, used with a QR-IBAN on CHF invoices, and the ISO 11649 creditor reference, used with a normal IBAN in CHF or EUR. Both let the creditor compare invoices and incoming payments automatically, and the choice depends on the account and currency the issuer has.
- Is camt.054 or camt.053 better for matching?
- They serve different purposes. A camt.054 is event-driven and reports individual credits and debits, while a camt.053 is the day-end statement with opening and closing balances. Many companies use the notifications for timely information and the statement as the control total. Availability of each message depends on the bank.
- What if the customer pays a different amount than the invoice?
- The structured reference still points to the invoice, but the amount does not close it. The difference, for example a discount the customer assumed, is a decision for a person. A matching process should show the reference, the invoice amount and the paid amount side by side and leave the invoice open until someone decides.
- Can one payment cover several invoices?
- Yes, but not with two structured references. A credit transfer carries at most one structured reference, so a customer who pays two invoices with one transfer leaves at least one invoice without its reference, and a person has to confirm the allocation from the amount and the payer. Separately, the creditor's bank may book several incoming payments as one entry; the Swiss guidelines then list the lines either inside the camt.053 or in a referenced camt.054.
- What does Corebanq Accounting do with camt files?
- It imports camt.053 and camt.054 files that the user uploads, and it issues QR-bill invoices that carry a structured reference. It has no live bank feeds, EBICS or open banking connection, and the matching cases in this note are a design discussion, not a feature list.
Sources
- SIX Interbank Clearing: Swiss Implementation Guidelines for the QR-bill, version 2.4 (valid from 14 November 2026)
- SIX Interbank Clearing: Swiss Implementation Guidelines for Customer-Bank Messages (Reports) camt.052 / camt.053 / camt.054, version 2.3, with effect from 14 November 2026
- SIX Interbank Clearing: Swiss Implementation Guidelines for Customer Credit Transfer Initiation (pain.001), SPS 2026 version 2.3
- ISO 20022: message definitions catalogue
Discuss how this applies to your institution with the Finray team.
Book a briefing