Skip to main content
alongside

Case · Twinfield → AIB and Bank of Ireland

Twinfield files that AIB and Bank of Ireland accept

Twinfield exports pain.001.001.03 with supplier addresses on one free-text line. From November 2026 the banks reject that. We built the converter that closes the gap.

4pointzero

4pointzero

Twinfield partner for accounting firms and finance teams in Ireland

Source
Twinfield · pain.001.001.03
Output
pain.001.001.09 · hybrid address
Banks
AIB · Bank of Ireland
First test files
One week after design

4pointzero looks after Twinfield for Irish groups that pay their suppliers in bulk through AIB and Bank of Ireland. Twinfield writes the payment file in the 2009 version of pain.001, with each supplier’s address as free text. From November 2026 both banks only take pain.001.001.09 with the town and country as separate elements, and Twinfield will not change in time.

So we built a converter. A finance user uploads the Twinfield export, the agent completes every address it can from the supplier list, asks only about the ones it cannot, and hands back a file that passes the ISO schema and the bank’s rules. The first client was testing real files one week after the design was agreed.

November 2026: bank files without a town are rejected

ISO 20022 · pain.001

November 2026

AIB

12 November 2026

Older bulk payment file formats are no longer processed. Files must follow AIB’s pain.001.001.09 specification.

SEPA · Bank of Ireland

22 November 2026

Only structured and hybrid postal addresses are allowed: town name and country are mandatory in every address.

Rejected · unstructured<AdrLine>Unit 4, Quay Road, Dublin 2</AdrLine>
Accepted · hybrid<TwnNm>Dublin</TwnNm> <Ctry>IE</Ctry>

1 / 5
The scene in words
  1. In November 2026, Irish and European banks stop accepting payment files the way most accounting systems write them.
  2. AIB stops processing older bulk payment formats after 12 November 2026.
  3. From 22 November 2026, SEPA payments need a town and a country in every postal address. One free-text line is no longer enough.
  4. The Twinfield and Xledger exports we work with are still pain.001.001.03. Nobody re-types hundreds of supplier addresses in a week.
  5. So agents do it: they read the export, complete the addresses, and hand back a file the bank accepts.

One payment, from Twinfield to the bank

Twinfield

pain.001.001.03 · Twinfield export

<Cdtr>  <Nm>Harbour Supplies Ltd</Nm>  <PstlAdr>    <Ctry>IE</Ctry>    <AdrLine>Unit 4, Quay Road, Dublin 2</AdrLine>  </PstlAdr></Cdtr>

Agent

TwnNm missing

Reviewed by a person

pain.001.001.09 · hybrid address

<Cdtr>  <Nm>Harbour Supplies Ltd</Nm>  <PstlAdr>    <TwnNm>Dublin</TwnNm>    <Ctry>IE</Ctry>    <AdrLine>Unit 4, Quay Road</AdrLine>  </PstlAdr></Cdtr>
✓ ISO 20022 XSD✓ Bank of Ireland v09 rules✓ NbOfTxs · CtrlSum
Uploaded to →
AIB
Bank of Ireland

1 / 6
The scene in words
  1. Twinfield exports the month’s supplier payments as pain.001.001.03. Every address is one free-text line.
  2. The agent reads every payment and flags what the bank will reject: no town, the whole address in one line, dates already past.
  3. It completes the town and country from the supplier list imported from Twinfield, and asks a person only about the rest.
  4. It writes pain.001.001.09 with a hybrid address: town and country as elements, at most two address lines.
  5. Every file is validated against the ISO 20022 schema and the bank’s usage rules before it can be downloaded.
  6. The finance team uploads it to AIB or Bank of Ireland as before. Next month, the saved addresses mean one click.

What the converter does

It accepts pain.001.001.03 and pain.001.001.09, so a file that was converted elsewhere can be checked again. It fixes what is safe to fix on its own: characters outside the bank’s Latin set, the transaction count and control sum, identifiers and the file name.

It never guesses an address or a payment date. Addresses come pre-filled from the supplier list and the saved address book, and a person confirms them. A date already in the past stops the file until someone changes it.

Each account can hold several group companies, and the originator ID in every upload is checked against the company being worked on, so one company’s payments cannot leave under another’s name. Files are encrypted at rest and deleted after 90 days.

What is a pain.001 file?

pain.001 is the ISO 20022 XML message a company sends its bank to start credit transfers. One file carries a batch of payments: who pays, who is paid, the IBANs, the amounts and the execution date. Accounting and ERP systems such as Twinfield and Xledger export it, and the finance team uploads it to the bank or sends it over SFTP.

The bank checks the file against the ISO schema (XSD) and against its own usage guidelines before it pays. A file that fails either check is rejected as a whole or payment by payment.

pain.001.001.03 and pain.001.001.09

pain.001.001.03 is the 2009 version of the message, and it is still what most accounting systems export. pain.001.001.09 is the 2019 version, which the European Payments Council adopted for SEPA in November 2023. It adds structured address elements, the LEI and a few other fields, and some elements move or change name.

Converting is not a find-and-replace on the namespace. The group header, the execution date format, the address and the bank-specific identifiers all change, and every bank publishes its own rules on top of the standard.

Structured, hybrid and unstructured addresses

An unstructured address is free text: “Unit 4, Quay Road, Dublin 2” in one or two AdrLine elements, plus the country. From November 2026 this form is rejected.

A structured address uses separate elements only: street (StrtNm), building number, post code, town (TwnNm), country (Ctry). A hybrid address keeps up to two AdrLine elements, but the town and the country must be there as separate elements. Hybrid is the practical route for files exported from an accounting system, because the street can stay as it was typed.

Questions about this case

Does Twinfield export pain.001.001.09?

The Twinfield exports we work with are pain.001.001.03, with supplier addresses in free-text AdrLine elements. That is why AIB and Bank of Ireland reject them from November 2026, and why the converter exists.

What is a hybrid address in pain.001.001.09?

A postal address with the town (TwnNm) and country (Ctry) as separate elements and at most two free-text AdrLine elements. Bank of Ireland requires town and country in every hybrid or structured address, and stops accepting unstructured ones on 22 November 2026.

When do AIB and Bank of Ireland stop accepting the old format?

AIB stops processing older bulk payment formats after 12 November 2026. Bank of Ireland follows the European Payments Council rule that from 22 November 2026 only structured and hybrid addresses are allowed.

Do we have to re-enter every supplier address?

No. The supplier export from Twinfield is imported once, matched to payments by IBAN, and every confirmed address is remembered. Only suppliers with no usable town or country are asked about, once.

Does the converter send payments to the bank?

No. It produces the validated file and the finance team uploads it to AIB or Bank of Ireland exactly as before. Direct submission over SFTP is what we built for Lloyds, and can be added per bank.

Same problem, another bank?

Case · Xledger → Lloyds Bank

From an Xledger export to Lloyds Commercial Banking Direct, over SFTP

Read the case