ISO 20022 for Small Businesses: What to Change on Invoices

ISO 20022 is the global standard for payment messages between banks. It replaces free-text fields with structured data for names, addresses and invoice references. For small businesses, the practical change is simple: give complete, structured addresses and clean invoice references on your invoices and bank details, so payments are not delayed or rejected.

You do not need to read message schemas or buy new software. You need to know what banks now expect, what changed with SWIFT in November 2025, where the structured address deadline stands in 2026, and which details to fix on your invoices. This guide covers all four.

What is ISO 20022?

The standard is published by the International Organization for Standardization, for how financial institutions describe payments and related messages. Compared with older formats such as SWIFT MT, it offers:

• Structured fields for each piece of data, such as street name, town and country, rather than four lines of free text.
• Richer data, including longer names, legal entity identifiers and purpose codes.
• Structured remittance information, so invoice numbers and amounts can travel with the payment.

The benefit is better automation. Banks can screen for sanctions and fraud more accurately, and businesses can match incoming payments to invoices without guesswork.

The ISO 20022 migration timeline

Many payment systems have moved to the new standard over the past few years. The milestones that matter most for small businesses:

System or milestone	Date	What it means
SEPA credit transfers and direct debits (euro)	Since SEPA launched	Already built on the standard, which is why IBAN payments carry structured references
CHAPS (UK high-value payments)	June 2023	Bank of England moved CHAPS to the new format, with enhanced data rules phased in afterwards
Fedwire Funds Service (US)	July 2025	The Federal Reserve moved Fedwire to the new format in a single cutover
SWIFT cross-border payments	November 2025	End of the MT coexistence period for cross-border payment instructions
Unstructured addresses removed (SWIFT CBPR+)	Originally November 2026, now being extended	Only structured or hybrid addresses accepted once the change takes effect

SWIFT November 2025

SWIFT ran a coexistence period from March 2023 in which banks could send cross-border payment instructions in either the old MT format or the new one. That period ended in November 2025. Since then, the new format has been the standard for cross-border payment instructions on SWIFT. For you, this mostly happened behind the scenes, but it is why banks became stricter about data quality.

Structured addresses in 2026

The next step was to stop accepting fully unstructured postal addresses in cross-border payments. SWIFT's plan was that, from November 2026, only fully structured addresses (each part in its own field) or hybrid addresses (some free-text lines plus structured town and country) would be accepted.

In August 2026, SWIFT said it had accepted a request from the banking community to extend the structured address migration for ISO 20022 payment messages. It said it would consult banks, market infrastructures and corporates on the timing and expected to give an update by the end of 2026. At the time of writing, no final new date had been confirmed, and some banks and euro schemes had published their own November 2026 changes. Check SWIFT's announcements and ask your bank what it requires.

Whatever the final date, the direction is fixed. Banks want town and country in dedicated fields at a minimum, and fully structured addresses are the safest choice.

Structured addresses: what they look like

Here is the same supplier address in three formats.

Format	How the data is held	Accepted going forward?
Unstructured	Line 1: "Unit 4, 12 Mill Lane"; Line 2: "Leeds LS1 4AB UK"	Being phased out for cross-border payments
Hybrid	Free-text line: "Unit 4, 12 Mill Lane"; Postcode: LS1 4AB; Town: Leeds; Country: GB	Yes, under SWIFT's plan
Fully structured	Building: Unit 4; Number: 12; Street: Mill Lane; Postcode: LS1 4AB; Town: Leeds; Country: GB	Yes, and preferred

For your own records, store each part of every client and supplier address in separate fields in your spreadsheet or accounting software, even if your invoice shows the address on a few lines. When a client's accounts payable team or your own bank asks for structured data later, you can copy each part straight across instead of splitting addresses by hand under deadline pressure.

Note the country is a two-letter ISO code (GB, not UK). Your invoice can show the country name in full; what matters is that every component is present and clearly separated, so a client's AP team can enter it correctly.

Structured remittance data and invoice references

The second big change is remittance information: the data that says which invoice a payment settles. ISO 20022 supports:

• Unstructured remittance: a free-text line, often limited to 140 characters.
• Structured remittance: fields for a creditor reference, the referred document number, and amounts, including several invoices in one payment.

In practice, many small payments still arrive with a free-text reference. The rule for you is the same either way: give one unique, short invoice number and ask clients to quote it exactly. Avoid long references like "Payment for consulting October invoice 41 thanks", which get truncated.

When a client pays several invoices at once, a remittance advice listing each invoice number and amount closes the gap. Our cash application guide shows how to match those payments quickly.

What small businesses need to change on invoices

Here is a checklist of invoice and bank detail changes that line up with ISO 20022:

1. Use your exact legal name, matching your bank account. Name-checking services such as Confirmation of Payee in the UK and Verification of Payee in the euro area compare names too.
2. Split your address clearly: building or unit, street number, street name, postcode, town, country on separate lines or clearly separated.
3. Collect complete client addresses in the same way. Our guide to billing vs shipping addresses explains which one to use.
4. Show full bank details: IBAN and BIC for international payments, plus local details where relevant. See how to show bank details on an invoice.
5. Use a short, unique invoice number as the payment reference. A tool like our invoice number generator helps keep the format consistent.
6. Add the client's PO number if they use one, so their system can link the payment. See invoice reference numbers.
7. State the currency clearly, especially for cross-border invoices. Our guide to invoicing international clients covers this.

Worked example: fixing a supplier record

A UK design studio invoices a German client 6,000 euro. The old invoice shows "Studio Nine, 3rd floor, 22 Kings Road Bristol". The client's AP team enters the address as one free-text line, and their bank, applying stricter cross-border rules, asks for town and country in separate fields. The payment is held for two days while the AP clerk emails back.

After the fix, the invoice shows: Studio Nine Ltd, 3rd Floor, 22 Kings Road, Bristol, BS1 5XX, United Kingdom, plus IBAN, BIC and reference INV-2026-118. The AP team can map every part to a field, and the payment goes through first time. The cost of the fix: five minutes, once.

If you send international payments

ISO 20022 also affects payments you make. Before your bank's deadline:

• Review supplier records in your banking app or accounting software and fill in town, postcode and country fields.
• If you upload payment files to your bank, ask whether your format needs updating.
• Ask suppliers who send unclear invoices for full structured addresses.
• Keep invoice numbers in the reference field so suppliers can match your payment.

For a comparison of how cross-border transfers move, see ACH vs wire transfer.

What changes in each region

The standard is global, but the way it reaches you depends on where you and your clients bank.

United Kingdom

CHAPS, used for high-value and time-critical sterling payments such as property completions, moved to the new format in 2023, and the Bank of England has been phasing in richer data requirements since. Everyday Faster Payments and Bacs still run on their own formats, so most small UK invoices paid by bank transfer will not look any different. Where it shows up is cross-border: a client abroad paying you through SWIFT, or you paying a foreign supplier. Our guide to VAT invoices covers the other details UK invoices need.

United States

The Fedwire Funds Service moved in July 2025. If US clients pay you by wire, their bank now sends a richer message, and complete name and address data reduces the chance of a payment being held for review. ACH, which carries most US business-to-business payments, has its own Nacha format and its own 2026 rule changes; see the Nacha 2026 rules.

Euro area

SEPA payments have used XML messages based on the standard for years, which is why euro transfers already carry IBANs and a structured creditor reference option. The European Payments Council has been aligning SEPA address rules with the cross-border changes, so ask your bank whether its address requirements for SEPA payments are changing at the same time.

Questions to ask your bank

A five-minute conversation with your bank, or a look at its business help pages, answers most questions. Ask:

• Which address format do you require for international payments I send, and from what date?
• Will you reject or repair payments with incomplete addresses?
• Do the same rules apply to SEPA, domestic and cross-border payments?
• Do my payment file uploads need a new format?
• Can I see structured remittance details, such as invoice numbers, on incoming payments in my statement or export?

Write down the answers with the date. Banks have been updating their guidance as SWIFT's timeline has moved, so check again before the end of the year.

Worked example: a multi-invoice payment

A client pays three of your invoices in one transfer: INV-2026-101 for 1,200 euro, INV-2026-104 for 850 euro and INV-2026-107 for 2,450 euro, a total of 4,500 euro. With only a free-text reference, you might see "INV 101 104 107" or just the client's name, and you would have to work out the split. With structured remittance data, or a separate remittance advice, each invoice number and amount arrives clearly. Either way, you can record each invoice as paid in full in minutes instead of chasing the client for a breakdown.

Common mistakes to avoid

• Writing "UK" in a country field that expects a code (the ISO code is GB).
• Putting the postcode and town in the same field or line as the street.
• Using a trading name that does not match the bank account name.
• Changing bank details without warning, which looks like fraud to automated checks.
• Long payment references that get cut off.

Conclusion

ISO 20022 is now the standard for payment messages, and the structured address change is coming even though SWIFT has extended its timing. You do not need new systems. You need complete, structured addresses, exact legal names and short, unique invoice references. Our free invoice generator lets you enter your full business address, client address, bank details and invoice number, and download a clean PDF ready to send. For anything specific to your payment flows, check with your bank or a qualified adviser.