This is part 3 of a 3-part blog series on Verification of Payee (VoP). To read the other parts of this series, follow the links below:
Part 1:‘’Why VoP Doesn’t Protect You From the Fraud You’re Actually Worried About.’’
Part 2: ‘’ Verification of Payee (VoP): Why Vendor Master Data Accuracy Matters’’
There is a version of the VoP compliance story that is relatively straightforward. You have one primary banking relationship. You work with your bank’s implementation team. You update your EBICS configuration or your API connection. You run a test. VoP is live.
That version of the story applies to a small minority of corporate treasury functions.
For most multinational organizations — those with 10, 20, 40 or more banking relationships spanning multiple SEPA countries, multiple currencies, and multiple payment channels — VoP compliance is not a single project. It is an ongoing operational challenge with possibly a different answer for every bank in the network.
Why there is no single VoP standard at the corporate level
The EU Instant Payments Regulation and the EPC’s VoP Scheme Rulebook govern how Payment Service Providers communicate with each other. They do not govern how PSPs communicate VoP results to their corporate clients.
That gap between the PSP-to-PSP standard and the bank-to-corporate interface is where the complexity lives. Each bank has a certain level of discretion over:
- How and when VoP results are returned to the corporate
- What format those results take — free text at some banks, structured codes at others
- Whether VoP is opt-in or opt-out for different payment types
- How single payments versus bulk payments are handled
- What ERP and TMS configuration changes are required on the corporate side
For German banks operating under the Deutsche Kreditwirtschaft’s EBICS framework, bulk payments are treated differently from single payments. VoP is optional for bulk payments unless the corporate has explicitly configured the relevant BTF service option parameters. For single payments, opt-in is treated as mandatory under the regulation.
This means a corporate can be simultaneously opted in for single payments and opted out for bulk payments across the same banking relationship, with different liability implications for each. And that is just one bank. Multiply it by the size of a typical multinational bank network, and the compliance picture becomes genuinely complex.
Imagine if you have 30 banking relationships and each bank implements VoP differently, you don’t have one compliance problem. You have 30.
What bank-by-bank alignment actually costs
The work of achieving consistent VoP compliance across a multi-bank estate is often underestimated until treasury teams begin doing it. In practice, it involves:
Assessment
A structured review of every banking relationship to establish: Has this bank rolled out VoP? What channels are affected? What is their opt-in policy for single vs. bulk payments? What ERP configuration is required? The assessment itself requires direct dialogue with the individual banks.
Configuration
ERP and TMS systems must be updated for each banking relationship individually. In SAP S/4HANA Cloud environments running EBICS, this means configuring new BTF parameters and order types — CTV for SCT opt-in, CIV for SCT Inst opt-in — and ensuring the relevant bank has been specifically enabled to accept them. This is not a global setting. It is a per-bank, per-channel configuration exercise.
Response handling
Each bank may return VoP results in a different format. Some return structured match codes. Others return free text. TMS and ERP systems must be configured to capture these responses, gate payment authorization appropriately, and maintain an audit trail of what was received and what action was taken. The logic required to handle heterogeneous responses from 30 different banks is not trivial.
Ongoing maintenance
Banks are still rolling out and updating their VoP implementations. A bank that returned free-text responses last quarter may move to structured codes this quarter. Opt-out policies may be subject to change. New EBICS parameters may be introduced. A VoP configuration that is accurate today requires active maintenance to remain accurate.
For a lean treasury function — which describes the majority of corporate treasury teams — this is a significant and recurring burden. The question worth asking is whether this is the right level at which to solve the VoP compliance problem.
The case for moving validation upstream
The bank-by-bank compliance challenge is real, but it rests on a particular assumption: that VoP compliance needs to be managed at the bank interface layer. That is one way to approach it. It is, however, not the only way.
A growing number of treasury teams are re-framing the question. Rather than asking “how do we configure VoP correctly across every banking relationship?”, they are asking “how do we validate every payment before it reaches any bank?”
Pre-execution account validation operates upstream of the banking layer entirely. Before a payment instruction is formed and sent to a bank, the account is validated against live data: does this account exist? Does the payee name match? The answer is available in real-time, and it is the same answer regardless of which bank will ultimately process the payment.
This approach does not replace VoP compliance. Banks still require it, and the regulatory obligation sits with the PSP. But it provides something that bank-by-bank VoP configuration does not: a single, consistent validation layer that covers the entire payment estate, with no dependency on how each individual bank has chosen to implement its customer interface.
One validation layer, upstream of all your banking relationships, covering all of them consistently — that is a structurally simpler answer than 30 separate bank configurations.
What this means for multi-country operations
The multi-bank complexity of VoP is most acute for treasury functions managing global payment operations. Different regions have different schemes — EU VoP, UK Confirmation of Payee, SWIFT Pre-Validation — each with their own coverage and technical requirements. A European corporate with significant US supplier payments faces not just multi-bank complexity but multi-scheme complexity.
Pre-execution validation that covers multiple schemes through a single platform resolves both problems simultaneously. The treasury team does not need to maintain separate configurations for EU VoP, UK CoP, and US account validation. The validation runs through one interface, and the result is available before any payment is authorized.
For treasury functions managing complex global payment estates, this is not an incremental improvement. It is a structural simplification of a compliance problem that would otherwise require continuous bank-by-bank maintenance across an increasingly fragmented landscape.
A practical starting point
For treasury teams currently in the process of working through VoP compliance across their banking network, the most valuable near-term action is not necessarily completing that bank-by-bank work. It is assessing whether there is an upstream option that makes the bank-by-bank work less necessary.
The questions worth asking:
- Does our current TMS or payment platform offer pre-execution account validation as a native capability?
- If so, which markets does it cover, and which of our banking relationships would it effectively replace from a validation standpoint?
- What would the compliance and operational risk picture look like if every payment was validated before it reached any bank, as a baseline layer?
The answers will differ by organization. But for multinational companies managing complex bank networks across SEPA and beyond, the upstream approach is worth evaluating seriously — not as a replacement for compliance, but as a way to achieve something compliance alone cannot deliver: consistent, auditable, pre-execution validation at scale.
TIS Account Validation gives treasury teams a single pre-execution validation layer across all their banking relationships — covering EU VoP, UK CoP, SWIFT Pre-Val, and 95% of US institutions via LSEG — without bank-by-bank configuration. Live in 46 markets. Zero workflow disruption.
To know more, reach out to TIS team and set up a personalized demo.
