ISO 20022 is an international standard for financial messaging — the structured format banks and payment systems use to exchange payment instructions and related information. It is replacing older message formats globally, including in South African payment infrastructure.
For most businesses this is a change their bank implements rather than something they implement themselves. Where it does affect you directly is in the data you supply with payments, because the new standard carries far more structured information and payments with incomplete data are rejected.
Business Requirements at a Glance
Who is actually affected, and how.
- Banks and payment service providers — directly, through system migration governed by scheme rules
- Corporates with direct host-to-host or bulk payment file connections to a bank — directly, since file formats change
- Businesses using accounting or ERP software to generate payment files — indirectly, through software updates
- Businesses making cross-border payments — directly, through stricter data requirements on beneficiary and originator details
- Ordinary consumers and small businesses using banking apps and online banking — largely unaffected, since the bank handles it
Registration and Legal Requirements
The practical impact is data quality. ISO 20022 carries structured fields for originator and beneficiary names, addresses, account identifiers, purpose codes and remittance information. Payments submitted without complete, correctly structured data are rejected or delayed.
For cross-border payments in particular, complete beneficiary and originator details are now enforced rather than tolerated as free text. That means full legal names, structured addresses and correct account identifiers. Businesses that maintained loose supplier master data find this out through failed payments.
The first practical step for any business is a data clean-up. Check that your supplier and customer master records contain complete, accurate, structured names, addresses and banking details. That is work you control and it prevents most of the pain.
Talk to your bank. If you have a direct file connection, the bank will have a migration plan, a testing window and a cut-over date. Get those dates and build them into your own planning, because testing a payment file integration takes longer than people expect.
If you use accounting or ERP software, confirm with your vendor that the version you run supports the required formats and when the update is due. An unsupported legacy version is a real risk at cut-over.
Documents and Ownership Information Required
What to gather before engaging with your bank on a migration.
- An inventory of every system that generates or receives payment files
- The current file formats in use for each
- Your supplier and customer master data, reviewed for completeness and structure
- Full legal names and structured addresses for all payment counterparties
- Correct account identifiers, including IBAN and BIC where cross-border payments are made
- Your accounting or ERP software version and its supported formats
- Contact details for your bank’s implementation team and your software vendor
- A record of any customisations made to existing payment file formats
Tax, Licence and Compliance Requirements
This intersects with regulatory obligations. The structured originator and beneficiary information ISO 20022 carries is exactly what anti-money-laundering and sanctions screening rely on, so the data requirements are enforced for compliance reasons rather than technical preference. Under the Financial Intelligence Centre Act, institutions must be able to identify parties to transactions.
It also intersects with the Protection of Personal Information Act, since payment messages carry personal information. Ensure the data you transmit is accurate and that your handling of counterparty data complies.
Cross-border payments additionally involve exchange control administered through the South African Reserve Bank, requiring balance of payments reporting categories on outward payments. Those purpose codes must be correct, and ISO 20022 structures them.
Timelines are set by the payment schemes and the banks, not by individual businesses. Migration in South African payment infrastructure has been phased, and dates have moved. Confirm the timeline applicable to you with your bank rather than working from a general announcement.
Process, Deadlines and Ongoing Obligations
If you use ordinary banking channels, there is little for you to do beyond keeping counterparty details accurate. If you have a direct integration, start with your bank and your software vendor, and allow more time for testing than the plan suggests.
Do the master data clean-up regardless. It is the highest-value work, it is entirely within your control, and it prevents failed payments whatever the timeline does.
- Establish whether you have a direct file integration or use standard banking channels
- Ask your bank for the migration timeline and testing window that applies to you
- Confirm your accounting or ERP software supports the required formats
- Clean up supplier and customer master data — full legal names and structured addresses
- Verify account identifiers, including IBAN and BIC for cross-border payments
- Check that balance of payments purpose codes are correctly applied
- Allow more time for integration testing than the plan suggests
- Confirm current timelines with your bank rather than general announcements
Frequently Asked Questions
Does this affect my ordinary business banking?
Largely not. If you use banking apps or online banking, your bank handles the migration. Direct file integrations and cross-border payments are where businesses are affected.
Why are my payments being rejected?
ISO 20022 enforces complete, structured data. Incomplete beneficiary or originator details — particularly on cross-border payments — cause rejection where free text was previously tolerated.
What should I do first?
Clean up your supplier and customer master data so that names, addresses and banking details are complete and correctly structured. It is the highest-value step and entirely within your control.
Who sets the deadlines?
The payment schemes and the banks. Confirm the timeline that applies to you with your own bank rather than relying on general announcements, since dates have moved.
Migration timelines, message specifications and data requirements are set by the payment schemes, the banks and the South African Reserve Bank, and they change. Confirm the requirements and dates applicable to you with your bank.