Buyers · A cost to neutralise

Clean your beneficiary data before it becomes your bank’s problem.

After 14 November 2026, your bank may correct its own records but is forbidden by EPC §3.2 from touching your counterparty addresses — so when the network rejects a payment for an unstructured beneficiary address, the liability is yours as originator. ioNova ARS fixes every address at source, inside your ERP, TMS and pain files, ~98% automatically and 100% accurately, before the file ever leaves your systems.

~98%
resolved automatically
0%
NAK at cutover
<$5
per exception (from $15–40)
2–4 wks
to go live
After 14 November 2026, any cross-border or SEPA payment we send with an unstructured beneficiary address is rejected at the network, and the liability is ours. Our bank can fix our address, not our counterparties’. We need every address fit to transmit, at payment speed, without our team learning the regulation.
The problem, in their words
Group Treasurer / Head of Payments

What You Can Do

Readiness scan
Read-only inventory of every stored address — see exactly what fails after cutover before spending a cent.
Classify
Scrub master data
One-time clean-up of the supplier/payee backlog, up to 10,000 addresses per call.
Correct · batch
Validate & auto-correct a pain file
Submit a pain.001 / pain.008, receive the corrected message back, ready to transmit — not a list of errors.
Process
Process a pain message end-to-end
One call classifies, validates, fixes, verifies against postal data, then re-validates.
Process

From Sandbox to Live

Span
2–4 weeks end-to-end
Shape
Single track · all At-Source (your master data + pain files)
Tier entry
Corporate (Enterprise if multi-entity)
1
Get started
Sandbox live, first resolved address in ~2 days
2
Build
Register channels, test; ioNova tunes ~10,000 representative addresses in parallel
3
Validate
Production validation — channels + integrations exercised together
4
Go live
Swap test keys for live keys — no code change

This is the canonical two-track plan. Get sandbox keys and your first resolved address in ~2 days; your team registers channels and tests in the production-shaped sandbox while ioNova tunes the engine on ~10,000 of your representative addresses in parallel. Swap test keys for live keys to go live in weeks 2–4 — comfortably before the cutover.

Why It Pays Off

0% NAK at cutover 98% STP per-exception $15–40 → under $5 native to SAP, Oracle, Kyriba, GTreasury, ION no PII persisted live in weeks
Where you start
Begin with a Compliance Readiness Assessment. Corporate tier (Enterprise if multi-entity).

Frequently asked questions

Can my bank correct my counterparty’s address for me?

No. Under EPC §3.2 a payment service provider may correct its own customer’s address but must pass counterparty addresses through unchanged — so a corporate must fix beneficiary data at source.

Who is liable if a payment is rejected for an unstructured address?

The originator. From 14 November 2026, CBPR+ and SEPA reject non-compliant payments at the network, and the liability sits with whoever assembled the payment.

Does ioNova ARS work inside SAP, Oracle, Kyriba, GTreasury and ION?

Yes — it deploys as a sidecar via REST, SFTP, JDBC and File Upload, with no core replacement.

How many addresses can I remediate at once?

Up to 10,000 addresses per call for batch master-data clean-up.

How fast can corporate treasury go live?

Typically 2–4 weeks end to end, with the sandbox live and returning resolved addresses within about two days.

Is the correction auditable?

Yes — every correction is deterministic and cites a regulatory rule_source, so the same input always produces the same output.

Live in weeks — before 14 November 2026.

First sandbox call in minutes, first channel live in days. Early Adopter terms end 31 July 2026.