Payments modernisation always sounds elegant until the first mismatch lands and nobody agrees what should happen next.
Instant payments sound elegant until the exception queue arrives.
The Verification of Payee scheme is a good example. The EPC’s version 1.1 rulebook was issued on 16 March 2026 and becomes effective on 20 September 2026.
The accompanying API specifications, also effective on that date, tighten standards around fields, timestamps, headers and message handling. In other words, the market is moving from principle to operational detail.
That matters because payment change programmes do not fail on the “happy path”. They fail on mismatches, incomplete data, name discrepancies, manual review, customer communications and evidence handling when something goes wrong.
Verification of Payee is framed as a fraud-reduction and confidence measure, but in practice it creates a workflow challenge as much as a policy one.
This is where Tungsten has a practical story to tell. Not payments transformation in the abstract…but the document, decision and exception processes that sit around it: customer case routing, mismatch handling, evidencing, communications and control. The edge cases are where operational credibility gets tested. That is where automation earns its place.
Which payments clients are likely to be feeling the greatest strain from exception handling, evidencing and manual review?
Häufig gestellte Fragen
Why is payment exception handling important?
Payment modernization initiatives often succeed or fail based on how effectively organizations manage mismatches, incomplete data, manual reviews, customer communications, and evidence handling.
What is Verification of Payee?
Verification of Payee is a payment verification scheme designed to confirm that the name of a payment recipient matches the intended account before the payment is completed.
Why does Verification of Payee create a workflow challenge?
When payment details do not match, organizations must route cases for review, gather supporting information, communicate with customers, document decisions, and maintain evidence of how the exception was resolved.
How can workflow automation support payment exception handling?
Workflow automation can coordinate case routing, document collection, customer communications, approvals, escalations, and audit trails, helping financial institutions resolve payment exceptions more consistently and efficiently.
Glossary
| Term |
Definition |
| Verification of Payee |
A payment verification process that checks whether the recipient name entered by the payer matches the name associated with the destination account. |
| Payment Exception |
A payment case that cannot follow the standard processing path because of missing, inconsistent, or mismatched information. |
| Exception Queue |
A work queue containing payment cases that require additional review, supporting evidence, customer contact, or manual decision-making. |
| Payment Modernization |
The transformation of payment infrastructure and operations through faster payment rails, improved standards, automation, and stronger controls. |
| Workflow-Automatisierung |
The use of software to coordinate tasks, documents, approvals, communications, and system actions across a business process. |
| Evidence Handling |
The collection, organization, and retention of documents and records used to demonstrate how a payment exception or decision was managed. |
| Happy Path |
The standard process route followed when all payment data is complete, accurate, and requires no exception handling. |
| EPC |
The European Payments Council, an organization that develops payment schemes, rulebooks, and standards for payments in Europe. |
