Verification of Payee

With the introduction of Verification of Payee (VoP), the European payments landscape has gained another important security layer. What initially appears to be an additional validation step in the payment process has, in practice, proven to be a fundamental transformation for banks, treasury management systems (TMS), and companies.

VoP is part of the Instant Payments Regulation and requires payment service providers to verify, before executing a SEPA credit transfer, whether the specified beneficiary name matches the IBAN. The goal is to effectively reduce misdirected payments and fraud. The check is performed in real time between the payer’s and payee’s banks and provides feedback indicating whether there is a full match, close match, or no match. Based on this feedback, the payer decides whether to proceed with the payment.

For banks, VoP requires the development of new, highly available verification processes including API-based communication, status feedback loops and clearly defined liability frameworks. VoP is not a standalone service, but an integral component of payment processing.

TMS providers face the challenge of seamlessly integrating this new verification logic into existing payment workflows. Unlike traditional validations, VoP intervenes between submission, approval and final execution of a payment. Systems must therefore be able to interpret VoP responses, display them clearly and embed them into existing approval and signature processes.

For organizations, the main impact lies in operational responsibility. While payments were previously initiated primarily based on internal approvals, an external validation now needs to be consciously assessed. In particular, discrepancies between beneficiary name and bank details introduce an additional decision point in the payment process. When approving a close match or no match, the organization assumes liability for incorrect payments, whereas liability shifts to the bank in the case of a full match. As a result, master data management becomes significantly more important, as inaccurate or inconsistent master data can lead to no match responses.

A key aspect of VoP is the availability of opt-in and opt-out options for organizations. While individual payments are generally subject to VoP, organizations can decide for bulk payments whether to actively use VoP (opt-in) or temporarily waive it (opt-out). This flexibility has proven particularly important during the early stages of implementation. Given the operational challenges, the continued use of opt-out for single payments is currently tolerated by BaFin to enable a gradual adoption of Verification of Payee. However, whether this tolerance is applied ultimately remains at the discretion of the respective bank.

The relevance of VoP extends well beyond regulatory compliance. Payment fraud has increased significantly in recent years, while payment processes have become faster and more automated. Instant payments in particular are irreversible, meaning that misdirected transfers immediately result in financial losses.

VoP addresses this gap by making errors and manipulations visible before a payment is authorized. For organizations, this means greater security, but also a higher level of process discipline in both master data management and payment approval processes.

The introduction of VoP was not gradual but took place under significant time pressure. Banks were required to be VoP-ready by October 2025, leaving limited time for banks, corporates and TMS providers to adapt technical interfaces, internal processes and governance structures.

ION Treasury responded early to the regulatory requirements and integrated VoP into its treasury management solution ITS in a timely manner. As part of multiple projects, KPMG supported ION clients in implementing VoP. While KPMG focused on accelerating implementation and operationalizing VoP across multiple clients, full responsibility for product functionality and regulatory compliance remained with ION, as outlined in the press release: ION brings mandatory EU payee verification live at scale.

Across the VoP implementations in ITS supported by KPMG to date, a consistent pattern has emerged. The process begins with a kick-off phase in which regulatory requirements, bank-specific options and system prerequisites are clarified. From a technical perspective, VoP is then introduced directly into the production environment in parallel with ongoing payment operations. Initially, an active opt-out approach is applied to avoid disrupting existing processes.

In the next phase, opt-in payments are gradually tested for selected transactions. This stage is characterized by close collaboration between KPMG, ION and the respective organization. In many cases, an initially cautious approach evolved into a smooth VoP process that is now fully embedded in day-to-day payment operations.

Even after formal implementation, VoP is far from complete. Many organizations are now deliberately differentiating between opt-in and opt-out scenarios and are gradually expanding usage. At the same time, new functionalities are emerging, such as the automated confirmation of payment files following successful full match results.

In practice, users report a significantly increased awareness of master data quality and payment risks. Errors are identified earlier and processes become more transparent. Looking ahead, it is expected that opt-in usage will increasingly be extended to batch payments once the necessary organizational conditions are in place.

The introduction of Verification of Payee clearly demonstrates that regulatory changes in payments are rarely purely technical adjustments. VoP fundamentally alters decision-making logic, responsibilities and risk awareness within organizations. Its true value is not realized with the first successful verification, but in day-to-day operations – through clear processes, clean master data and the conscious use of the new verification mechanisms.

For many organizations, VoP is therefore less a completed project and more the starting point for a sustainably more secure payments environment.