Ask a corporate treasurer how they pay suppliers and they won't describe typing IBANs into a banking app. They export a payment file from the ERP — a batch of supplier or payroll lines — and release it in one approval. That efficiency is also the risk: one swapped IBAN sails through with everything else.
Why batch verification matters
Checking IBANs by hand doesn't scale past a handful of payees. The fix is to verify each record in the file programmatically before release, so a mismatched supplier or a redirected salary is caught while you can still stop it — not after the money has left.
Verify the file, not just the vendor
Onboarding checks age. Bank details change between onboarding and the next run. Re-verifying the whole file at payment time catches mid-cycle invoice-redirection fraud that a one-off onboarding check would miss.
A simple bulk-verification pattern
- 1 Export the payment file from your ERP as you do today.
- 2 For each line, call the Verification of Payee endpoint with the payee name, IBAN and your line reference as the external id.
- 3 Collect the results: release MATCH lines, hold NO_MATCH and NOT_APPLICABLE for review, and confirm CLOSE_MATCH against the suggested name.
- 4 Log every verification id against the payment record for audit and dispute handling.
Doing it without a heavy build
You don't need a new payments stack. Because the VoP API uses one authenticated REST call per record, a small script or middleware between your ERP export and your bank can verify a file end to end. RoxPay exposes the same check via API for bulk runs and via the RoxBusiness dashboard for ad-hoc lookups, so treasury can validate supplier-invoice IBANs before every transfer.