Instant payments in the EU: what changes for payment matching and cash flow

Monday morning. The accountant opens the bank statement and starts matching payments. 340 incoming transactions over the weekend. 280 have a matching reference and amount. The remaining 60 need manual work. One payment came without any reference. Three are off by a few cents. Seven arrived from a different account than what's on the invoice. This takes until lunch. Every Monday.

If this sounds familiar, the next two years will bring changes that could either simplify or complicate this process significantly. It depends on whether you prepare.

What's changing on the regulatory side

The EU adopted the Instant Payments Regulation in February 2024. This is not a directive that each country transposes at its own pace. It's a directly applicable regulation with concrete deadlines.

For the eurozone, the milestones are already here. By January 9, 2025, banks had to be able to receive instant payments. By October 9, 2025, they must also be able to send them. From autumn 2025, every bank in the eurozone must process SEPA Instant Credit Transfers as standard. Not as a premium product with extra fees. The charge for an instant payment cannot exceed the charge for a regular transfer.

For non-euro countries (Czech Republic, Poland, Hungary), the deadlines come two years later: January and July 2027. Companies trading across both eurozone and non-euro countries will feel both waves.

Verification of payee: a new layer before every payment

The regulation also introduces an obligation that most companies haven't registered yet. It's called verification of payee (VoP). Before sending a payment, the bank checks whether the IBAN on the payment order belongs to the person or company you intend to pay. If the payee name doesn't match the account holder, the bank flags it.

The reason: invoice fraud and IBAN swap scams are growing. An attacker sends a company an invoice with a legitimate-looking IBAN that actually points to their own account. The accountant checks the amount, maybe the reference number, and sends the payment. The money is gone. With VoP, the bank automatically compares the IBAN to the payee name before sending. If they don't match, the payment won't go through without explicit confirmation.

For business payments, this changes the established workflow. Your ERP or accounting system generates payment orders with IBANs and counterparty names. If these records are inconsistent (say the IBAN was updated but the account holder name wasn't), the VoP check will block the payment. Vendor master data quality becomes an operational concern, not just an administrative one.

Why payment matching doesn't work today

If you've ever done bank reconciliation at a company, you know the problem isn't the bank. The problem is that invoices and payments can't reliably reference each other.

In many countries, the reference field on which matching depends is voluntary, unstandardized, and unvalidated. The buyer can enter it incorrectly, truncate it, confuse it with a purchase order number, or leave it blank. The bank passes it through as-is.

International payments are worse. SEPA transfers have a "Remittance Information" field, but many banks truncate or ignore it during processing. Result: the payment arrives, but the system can't automatically assign it to an invoice.

The migration to ISO 20022, the messaging format eurozone banks have been adopting since November 2022, partially addresses this. ISO 20022 messages have structured fields for references, invoice identifiers, and payment purposes. But for it to work, both sides (sender and receiver) must populate these fields correctly. Most corporate systems don't yet.

From invoice to cash: what automation looks like

Invoice-to-cash is the entire chain from issuing an invoice to receiving payment and posting it. Automating this chain isn't a single product. It's a set of changes across processes and systems.

It starts with the invoice. If the invoice is issued in a structured format (UBL, EN 16931), it contains machine-readable identifiers: invoice number, supplier ID, amount, due date, reference. These can be carried forward automatically into the payment order.

It continues with the payment. If the payment leaves with the correct reference and arrives with that reference preserved (which ISO 20022 enables), matching happens automatically. The system compares reference, amount, and date. If they align, it posts.

The key metric is DSO (days sales outstanding). Companies with automated invoice-to-cash processes typically get DSO below 30 days, compared to 40-50 for companies relying on manual reconciliation. That difference of 15 days, applied to €200,000 in monthly revenue, means €100,000 tied up in receivables. Money the company earned but doesn't have in its account.

With instant payments, this cycle shortens further. If a payment arrives in 10 seconds instead of one day, reconciliation can happen in real time. The CFO isn't looking at yesterday's numbers. They're looking at now.

How this connects to ViDA and e-invoicing

This is where the pieces fit together. The ViDA regulation (VAT in the Digital Age), adopted March 2025, introduces mandatory structured e-invoicing. The Instant Payments Regulation introduces fast, structured payment messages. Verification of payee introduces counterparty verification. Together, they form the foundation for a fully automated invoice-to-cash cycle.

We wrote about what ViDA means for your ERP and accounting systems in a separate article on e-invoicing.

When a company issues a structured invoice, the payment arrives instantly with the correct reference, and the bank verifies the recipient before sending, manual matching becomes the exception rather than the rule. Not entirely eliminated. There will always be edge cases. But the ratio of automatically matched payments can move from today's 70-80% to above 95%.

What your ERP needs to handle

If you run an ERP or accounting system, these changes require specific upgrades.

Payment formats. The system must generate payment orders in ISO 20022 format (pain.001) and process bank statements in the same standard (camt.053, camt.054). If you currently export payments in legacy formats, it's time to migrate. Banks will phase out older formats.

Vendor master data. Every supplier record must contain the current IBAN and the exact account holder name. VoP will compare these against the bank's records before every payment. Outdated or incorrect data will cause payment rejections.

Reconciliation engine. Automated matching must work with the reference from ISO 20022 messages, not just legacy variable symbols. It must handle partial payments, advance payments, credit notes, and payments bundled into a single transaction. Matching rules should be configurable, because every company has different exceptions.

Cash flow reporting. If payments arrive in real time, reporting should be real time too. A CFO dashboard showing yesterday's position loses its value when payments arrive in seconds. This is an area where data analytics and BI dashboards significantly improve decision quality.

Bank API integration. Banks are gradually opening API interfaces (PSD2, Berlin Group standard). An ERP system that communicates with the bank via API instead of manual statement imports can process payments continuously, not once a day.

What to do now

Map your payment cycle. From invoice issuance to payment receipt and posting. How long does it take? How much is manual work? What percentage of payments match automatically versus manually?

Check what format your system uses for payment orders and bank statements. If it's anything older than ISO 20022, you'll need to migrate.

Review your vendor master data quality. If you have 500 suppliers and half of them have IBANs without the correct account holder name, verification of payee will block your payments this autumn.

If you're planning an ERP upgrade, include ISO 20022 payment formats, bank API integration, and a reconciliation module with structured reference support in your requirements. If you have a custom system, consider whether it makes sense to build the reconciliation module to spec rather than from scratch.

These upgrades can be co-funded through EU digitalization grants. SIEA innovation vouchers cover financial process automation projects.

Need to assess how your payment flows will handle the shift to instant payments? Get in touch, we'll walk through it together.