Putting an EPC QR code on an invoice — placement and workflow

Why put one on an invoice

An EPC code removes the two failure points of paying an invoice manually: mistyped IBANs and missing references. The payer scans inside their banking app, the transfer form arrives prefilled — beneficiary, IBAN, exact amount, your reference — and they confirm. You get payments that reconcile automatically and arrive without transposed digits. That operational gain, not marketing, is the whole case.

This page is about the invoice workflow; the payload itself is documented line by line on the EPC format page.

What to prefill

• Amount — the invoice total, exactly. An EPC amount is EUR plus a value from 0.01 to 999999999.99. A code without an amount forces typing and reintroduces errors.
• Reference — the invoice number, once, in one field. Use either a structured ISO 11649 creditor reference or the unstructured remittance line (≤ 140 characters) — the two are mutually exclusive, and populating both is a classic generator bug.
• Name and IBAN — your legal beneficiary name (≤ 70 characters) and IBAN. UseQR's EPC builder validates the IBAN's mod-97 check digits before generating, which catches a transposed digit before it reaches 5,000 printed invoices.

Keep the whole payload under 331 bytes. A long trading name plus a long remittance line exceeds it; shorten the remittance first.

Where on the invoice

Put the code in the payment block, adjacent to the total — the place the reader's eye already is when deciding to pay. Top-right of the payment details or directly beside "Amount due" both work. Then:

• Print the IBAN as text next to the code, always. Support for reading EPC codes is strong in Germany and Austria and inconsistent elsewhere; the text line makes the invoice payable by everyone.
• Add a one-line instruction — "Scan with your banking app" — because the code does nothing in a camera app.
• Respect the basics: ≥ 2 × 2 cm printed size for reading at desk distance, a quiet zone of at least 4 modules, dark on light.

Embedding in a PDF invoice

Invoices live and die as PDFs, get emailed, and are printed at unpredictable quality. Embed the code as vector (SVG), not a pasted screenshot — vector survives every zoom level and print resolution. Most invoicing tools accept an SVG image block; the mechanics are the same as adding any QR code to a PDF. Generate per invoice — the amount and reference change each time, so this belongs in your invoicing template, or in a script against the keyless API (GET https://useqr.app/api/v1/epc?...&format=svg).

What happens on the payer's side

The payer opens their banking app, finds the scan function in the transfer screen, and scans. The app shows a filled-in credit transfer for review. Whether the money arrives in seconds or the next business day depends on whether their bank sends it as a SEPA Instant transfer — the code cannot influence that.

Adoption reality, stated plainly: in the German-speaking market this flow is normal and expected on invoices. Elsewhere in the eurozone it is a bonus feature some payers will use. It never makes an invoice worse — the fallback is the same IBAN-and-reference text the invoice always carried. For Swiss customers, use the Swiss QR-bill instead; the formats are incompatible.

FAQ

Where should the QR code go on an invoice?

In the payment block, directly beside the total or the bank details — where the payer's eye is when deciding to pay. Keep it at least 2 x 2 cm with a clear quiet zone, and print the IBAN as text next to it.

Should the amount be in the invoice QR code?

Yes — the exact invoice total. Prefilling the amount is half the point: it eliminates typing errors. Leave the amount out only for open-value requests such as donations.

Can I use both a creditor reference and a remittance message?

No. The EPC format makes the structured reference and the unstructured remittance line mutually exclusive. Pick one — a structured ISO 11649 reference if your accounting can match on it, otherwise the invoice number as unstructured text.

Do all banking apps read EPC invoice codes?

No. Support is strong in Germany and Austria and inconsistent in the rest of the eurozone, which is why the IBAN must always appear as text as well. The code accelerates payment where supported and costs nothing where not.