EPC QR Codes on Invoices: How Customers Pay by Scan — AI Automation article by Rui Codex

An EPC QR code is a standardised code on an invoice that carries the payee's IBAN, amount and payment reference. When a customer scans it with a supporting banking app, the app pre-fills a SEPA credit transfer for the customer to confirm. It removes typing errors, but only when the data behind the code is correct.

Key takeaways

  • The code pre-fills a SEPA credit transfer, so the customer confirms the payment instead of typing account details.
  • Errors in the IBAN, amount or reference are copied into the payment without any warning to the payer.
  • Bank app support varies, so the code should always sit next to the plain-text bank details.
  • Generate the code from your invoicing system rather than by hand, and test it with the banking apps your customers actually use.

What is an EPC QR code and what does it contain?

An EPC QR code is a two-dimensional code that encodes the data for a SEPA credit transfer in a fixed, line-by-line format. The format is defined in the EPC QR code standard (EPC069-12), which is published by the European Payments Council. Because every field sits in a known position, any compliant banking app can read the same data the same way.

A typical code holds the following fields, in this order:

  • A service tag and version identifier that tell the app which format is used.
  • An optional BIC of the beneficiary bank, depending on the version.
  • The beneficiary name, which must be kept within a length limit set by the standard.
  • The beneficiary IBAN.
  • The amount in euro, written with the currency prefix.
  • An optional purpose code and a structured or unstructured remittance field, which carries the invoice reference.

The code is a container for data, not a payment itself. The customer's bank app still shows the payment screen and requires a confirmation, which means the customer always sees the amount and payee before money moves.

How does a customer pay by scanning the code?

A customer pays by opening the payment function of their banking app, scanning the code on the invoice and confirming the pre-filled transfer. The app reads the fields, checks the format and presents the payment for approval. Nothing is typed by hand, so the customer has no chance to mistype the IBAN or reference.

  1. The customer opens the transfer or scan function in their mobile banking app.
  2. They point the camera at the code on the printed or PDF invoice.
  3. The app pre-fills the beneficiary, IBAN, amount and reference.
  4. The customer checks the screen against the invoice and confirms with their usual authentication.

For the seller, the benefit is that the reference arrives exactly as issued, which makes matching incoming payments to open invoices simpler. The trade-off is that the seller has no control over which apps the customer uses, so the code is an addition to the payment options, not a replacement for them.

Where does the approach fail?

The approach fails when the data in the code is wrong, when the customer's app cannot read it, or when the payment falls outside the SEPA scope. Each failure looks different from the customer's side, so each needs its own check.

Amount and reference errors

If the amount in the code differs from the amount on the invoice, the customer may pay the wrong sum without noticing. This often happens when an invoice is revised and the PDF is regenerated while an old image of the code remains in a template or a cached file. A missing remittance reference is another common failure, because the payment then arrives without a clear link to the invoice.

App support

Support depends on the bank and the app version, not on the code itself. A scan that fails in one app can work in another, so a customer may conclude that the invoice is broken. This is why the plain-text IBAN, account name and reference should always appear on the invoice as a fallback.

Scope limits

The standard is built for euro SEPA credit transfers. Invoices in other currencies, or payments to accounts outside the SEPA area, need a different payment route, and a code that suggests otherwise will cause confusion.

Tip: Print the bank details and the code together, and add a short line such as 'Scan to pay, or transfer manually using the details below'. The fallback costs nothing and prevents most support calls.

How should you generate the code in your invoicing workflow?

Generate the code automatically from the same record that produces the invoice total, so that the amount and reference can never diverge. Manual creation in a spreadsheet or a design tool is where most copy errors enter the process. Connecting the invoicing system to your bank data and ERP is usually the most reliable route; our work on ERP and CRM integration covers how these data flows are structured, and our system integration services cover connecting invoicing tools to banking data.

Once generation is automated, test the result. Scan each generated code with at least two banking apps used by your customers, check that the amount and reference match the invoice, and repeat the test after every template change or invoicing tool update.

Does the code change your obligations under EU rules?

The EPC QR code does not create a new legal obligation by itself, but the payment it triggers is a SEPA credit transfer, and those transfers are governed by EU rules on credit transfers in euro. The technical and business requirements for these transfers are set out in Regulation (EU) No 260/2012. This article is general information and not legal or tax advice.

Whether the code helps with e-invoicing rules is a separate question. A payment code is not an electronic invoice, so it does not replace structured invoice formats. If you are preparing for structured invoicing, our page on Peppol e-invoicing describes the technical side of that work, which we provide as implementation support only.

Hypothetical examples of QR payments

Here are two hypothetical scenarios:

  • Scenario A: a service firm adds the code to its PDF invoices, but its template pulls the amount from a cached field. A revised invoice goes out with the new total in plain text and the old total in the code, and the customer pays the old figure. The fix is to generate the code from the live invoice record and to test every revision.
  • Scenario B: a wholesaler adds the code only to the email version of its invoices and omits the plain-text bank details. Customers whose banking app cannot read the code have no fallback, and payments arrive late. The fix is to print both on every invoice format, including the printed copy.

What should you check before rollout?

Before you switch the code on for all customers, confirm that the generation, the data and the fallback behave as expected. The following checklist covers the points where most projects fail.

  • The amount and reference in the code come from the same record as the invoice total.
  • The IBAN and account name match the account your bank statements use.
  • Revised invoices regenerate the code, and old PDFs are no longer sent.
  • Plain-text bank details appear on every invoice format.
  • The code has been scanned with the main banking apps your customers use.
  • Your accounts team knows how incoming payments with a remittance reference are matched.

Frequently Asked Questions

Can every bank app read an EPC QR code?

Support depends on each bank and app version, not on the code itself. A scan that fails in one app may work in another, so the printed bank details should always remain on the invoice as a fallback. Test with the banks your customers actually use.

Does the QR code replace the bank details on the invoice?

No, the code should sit alongside them. The IBAN, account name and payment reference in plain text let customers pay by manual transfer, check the data and keep a record when a scan fails. Printing both is the safer design.

Can I use the code for payments in currencies other than euro?

The EPC standard is built for euro SEPA credit transfers, so it is not the right tool for payments in other currencies. For those invoices, use the standard transfer details your bank provides and agree the process with your bank before you publish it to customers.

Who is responsible if the code contains wrong data?

The business that issues the invoice is generally the party that generates and sends the code, so it should own the data quality. Rui Codex offers technical implementation support for generation and testing, not legal, tax or compliance advice. Check contractual and payment terms with your own advisers.

Conclusion

An EPC QR code shortens the payment step for customers who use a compatible banking app, and it reduces typing errors when the data behind it is right. Its value depends on three things: generating the code from the invoicing record, keeping plain-text bank details on every invoice, and testing with the apps your customers use. Rui Codex is led by a founder with 200+ projects delivered, and can help you connect invoicing and banking data. Request a project consultation at https://ruicodex.com/Contact or email info@ruicodex.com to discuss your project.

Sources

Tags: EPC QR code SEPA credit transfer invoice payments payment automation invoicing Belgium Benelux system integration

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request