Bookkeeping & OCR
SEPA EPC QR Codes on Invoices: Data and Safety Checks
What an EPC QR code does
The European Payments Council’s QR guidance describes how a two-dimensional code can capture data to initiate a SEPA Credit Transfer. In an invoice use case, payment data encoded in the QR should also be shown in plain text so the payer can compare what the banking app reads with the invoice. The EPC says the QR guidance is informative and is designed for specific SCT use cases; it is not a generic QR standard for every payment context.
A common EPC payload includes a format indicator, service tag, beneficiary name, IBAN, optional BIC, amount and remittance information. The receiving bank app decides what it supports. Correctly encoding an IBAN only checks its structure/checksum; it does not prove that the account belongs to the named supplier.
Implementation checklist
- Confirm the beneficiary details and IBAN through a trusted channel.
- Set the amount only when it is fixed; otherwise leave it blank where appropriate.
- Keep a readable copy of payment details beside the code.
- Test with multiple banking apps and print sizes before rollout.
- Warn users to verify payee and amount before authorizing payment.
InvoiceConvertor’s QR tool creates a local EPC-style payload. It does not verify bank ownership or initiate a transfer.
Official sources
Frequently asked questions
Does an EPC QR code prove that the IBAN belongs to the supplier?
No. It encodes payment details but does not verify account ownership; confirm changes through a trusted channel.
Should payment details also appear as text?
The EPC invoice-use guidance recommends showing the transaction data in plain text so the payer can compare it with the scanned QR.