Odoo SEPA PAIN 2026 Checklist: pain.001.001.09 for Odoo 19 and 20
Odoo SEPA PAIN 2026 checklist: check pain.001.001.09, direct debit pain.008, structured addresses and bank tests in Odoo 19 and 20 before files bounce.
SEPA PAIN readiness is a short, technical job, but a wrong file means vendors and staff do not get paid on time. Our Odoo customization services team fixes payment file settings, address data and custom SEPA modules in Odoo 19 and 20.
Related service: Odoo implementation services — fixed-scope implementations with a named senior team.
This checklist is for finance managers, controllers and Odoo admins in the euro area, and for non-EU companies paying European suppliers. If you collect recurring payments, our guide to Odoo GoCardless integration for direct debit covers a different collection route.
What is the SEPA PAIN change in 2026?
The SEPA PAIN change in 2026 is the move from the older ISO 20022 2009 messages, such as pain.001.001.03, to the 2019 messages, such as pain.001.001.09, plus a push toward structured addresses. It touches every Odoo database that uploads SEPA XML files to a bank.
PAIN stands for Payment Initiation. It is the XML message your ERP sends to the bank to request transfers (pain.001) or direct debit collections (pain.008). The European Payments Council (EPC) 2025 rulebooks took effect on 5 October 2025.
The EPC customer-to-bank implementation guidelines for 2025 state that they are based on the 2019 version of ISO 20022, which means pain.001.001.09 for credit transfers. Banks then set their own dates for dropping the older versions.
Which pain.001 version does Odoo 19 and Odoo 20 use?

Odoo 19 and Odoo 20 use pain.001.001.09 by default for SEPA credit transfer XML files, according to Odoo's own documentation. You can still pick another version if your bank or country needs one.
The Odoo 20 SEPA payments documentation states that SEPA files generated by Odoo use the PAIN.001.001.09 format by default. It also warns that PAIN.001.001.03 is being deprecated in November 2026.
The same warning and default appear in the Odoo 19 SEPA payments documentation. Country-specific PAIN versions appear only when the matching fiscal localization is installed.
| Item | Odoo 17 | Odoo 19 | Odoo 20 |
|---|---|---|---|
| Default SEPA credit transfer format | Set per journal (SEPA Pain Version) | pain.001.001.09 | pain.001.001.09 |
| Where you set the outgoing format | Bank journal, Outgoing Payments tab | Bank journal, Outgoing Payments tab, XML Format | Payment method line on the journal |
| Direct debit format named in docs | PAIN.008.001.02, optional pain.008.001.08 | PAIN.008.001.02 specifications | PAIN.008.001.02 specifications |
| Direct debit setting | Incoming Payments, SEPA Pain Version | Incoming Payments, SEPA Pain Version | Incoming Payments, SEPA Pain Version |
| pain.001.001.03 warning | Deprecated November 2026 | Deprecated November 2026 | Deprecated November 2026 |
| Non-euro and EFTA payments | ISO 20022 method | ISO 20022 method | ISO 20022 method |
Our Odoo 20 accounting release notes show the main Odoo 20 change: the PAIN version for outgoing payments moved from the journal to the payment method level, with the SEPA Credit Transfer line set to pain.001.001.09.
Where is the PAIN version setting in Odoo?
The PAIN version setting sits on the bank journal: the Outgoing Payments tab controls credit transfers and the Incoming Payments tab controls direct debits. Check every bank journal, not just the main one.
- Open Accounting, then Configuration, then Journals, and open your Bank journal.
- On the Outgoing Payments tab, find the SEPA Credit Transfer line and read the XML Format field.
- Set it to pain.001.001.09, or to the version your bank or country explicitly asks for.
- On the Incoming Payments tab, check the SEPA Pain Version field for direct debit.
- Repeat for each bank journal and each company in a multi-company database.
- Create a small test batch payment and download the XML file from the chatter.
Odoo 17's documentation named a direct debit option called "Updated 2023 (Pain 008.001.08)". In Odoo 19 and 20, read the list in your own database and pick the version your bank confirms in writing.
What happened to the November 2026 structured address deadline?
The EPC first set 15 November 2026 as the end of unstructured addresses, then removed that date in September 2026 and has not yet set a new one. Structured and hybrid addresses are still the direction of travel.
The timeline matters because many teams planned around one date that no longer holds:
- November 2024: the 2025 implementation guidelines said unstructured addresses would not be accepted from 22 November 2026.
- 2025 rulebooks v1.1: the EPC moved that date to 15 November 2026 to align with the Swift November 2026 release.
- September 2026: rulebooks v1.2 and address guidance v2.2 removed the 15 November 2026 date.
- 29 October 2026: the EPC board deferred setting a new end date until February 2027.
Danske Bank also reports that Swift postponed rejecting cross-border payments only because they contain an unstructured address, with a new Swift timeline expected in December 2026. The EPC still recommends moving straight to fully structured addresses.
Are your Odoo partner addresses ready for structured or hybrid format?
Most Odoo databases are close to hybrid format already, because Odoo stores city and country in their own fields. The weak spots are missing cities, missing countries and street lines that mix several details.
Bank guides agree on the core rule. Deutsche Bank says town name and ISO country code must sit in dedicated elements once an address is given. Hybrid format allows at most two free address lines on top of that.
UniCredit HypoVereinsbank adds that hybrid addresses are allowed in pain.001.001.09 and pain.008.001.08, with up to two unstructured lines of 70 characters each. Fully structured format uses no free lines at all.
| Address check | Odoo field | Structured format | Hybrid format |
|---|---|---|---|
| Country | Country | Required | Required |
| Town or city | City | Required | Required |
| Postcode | ZIP | Own element | Own element or free line |
| Street name | Street, or Street Name with Extended Addresses | Own element | Free line allowed |
| House number | Street, or House Number with Extended Addresses | Own element | Free line allowed |
| Extra details (c/o, floor) | Street 2 | Own element where it fits | Free line allowed |
For fully structured files, Odoo's Extended Addresses module (base_address_extended) adds separate street name, house number and door number fields in Odoo 19 and 20. Whether your SEPA export uses them depends on your modules, so check the XML.
In the Odoo Community Association contributor list, a member reported that Belgian banks were already rejecting SEPA files from older community modules, partly because street name and number share one field. Audit your vendor and customer addresses before you test.
How do you prepare SEPA direct debit in Odoo for 2026?
Prepare SEPA direct debit by confirming your creditor identifier, checking mandates and asking your bank which pain.008 version it accepts. Collections fail quietly if the format or mandate data is wrong.
Odoo's direct debit setup needs the Creditor Identifier in Accounting settings. Odoo's docs list the test identifier DE98ZZZ09999999999 for testing only. Each mandate holds the customer IBAN, the CORE or B2B scheme and an optional validity date.
- Format: Odoo's docs say SDD files follow PAIN.008.001.02 specifications; UniCredit HypoVereinsbank says pain.008.001.02 is no longer supported for SEPA direct debit from November 2026, and names pain.008.001.08 as the current version.
- Mandates: Odoo closes mandates automatically 36 months after the last collection, and closed or revoked mandates cannot be reactivated.
- Schemes: filter batches by SDD CORE and SDD B2B, since some banks do not accept B2B.
- Odoo 20: draft mandates are created automatically for online orders paid with SEPA Direct Debit.
- Rejections: reverse the payment entry and reconcile it with the negative bank transaction.
If your bank prefers a third-party collection route, compare it with the GoCardless option linked above. For a non-SEPA bank file example, see our Odoo Canada EFT payments guide.
What else in Odoo 20 affects SEPA payment files?
Odoo 20 adds a few payment changes that touch the SEPA routine, beyond the PAIN setting moving to the payment method line. Train your finance team on them before the first real batch.
Our Odoo 20 release notes list a "Pay bills from Odoo" option that sends single or batch payments for one signature through a payment initiation service provider. It needs a supported bank connected through Online Synchronization, so many teams will still upload XML.
Other changes: the payment wizard now detects payments already made but not yet matched to the bank, to prevent double payments. Payment statuses were also renamed, with "In Process" becoming "Paid" and "Paid" becoming "Reconciled".
The Odoo 20 batch payments documentation adds two rules to keep in mind. All payments in one batch must use the same payment method, and ISO 20022 batches carry a Charge Bearer field.
Do custom or community SEPA modules need an upgrade?
Custom and community SEPA modules are the highest risk, because they can override Odoo's default pain.001.001.09 export with older code. Check what actually writes your XML file.
Open a recent file in a text editor and read the namespace near the top. It names the message version, such as pain.001.001.09. If it still says pain.001.001.03, a setting, a localization or a custom module is forcing the old format.
Common causes we see in audits are copied journals from older versions, a custom bank format added for one client, and community banking modules carried over during an upgrade. Our Odoo ERP support team traces and fixes these.
Test any change on a database copy first. Our Odoo staging environment checklist explains how to neutralize a copy so test batches never reach a real bank.
SEPA PAIN readiness by industry
The SEPA PAIN work is the same in every industry, but the risk sits in different payment runs. Start with the run that would hurt most if the bank rejected it.
| Industry | Pain or cost driver | Odoo approach | How iVentureTeam helps |
|---|---|---|---|
| Subscriptions and SaaS | Recurring SDD collections at scale | SDD mandates, CORE or B2B batches | Mandate audit, pain.008 version check |
| Wholesale and distribution | Large weekly supplier runs | SCT batch payments, one method per batch | Vendor address cleanup, test batches |
| Manufacturing | EU and non-euro suppliers | SEPA for EUR, ISO 20022 for other currencies | Separate journals and methods per case |
| Professional services | Salary and expense transfers | SEPA payments for payroll | Employee bank data review |
| Non-EU groups with EU entities | EFTA or non-EEA rules | ISO 20022 method, localization formats | Multi-company journal setup |
Your Odoo SEPA PAIN 2026 readiness checklist
Work through these eight checks in order, and you will know within a day whether your Odoo database is ready. Most databases need settings and data fixes, not a version upgrade.
- List every bank journal in every company that sends or collects SEPA payments.
- Read the XML Format on each SEPA Credit Transfer line and set pain.001.001.09 unless your bank says otherwise.
- Read the SEPA Pain Version for direct debit and confirm the pain.008 version with your bank.
- Check company data: IBAN on the journal, Name Identification and Issuer for credit transfers, Creditor Identifier for direct debit.
- Clean partner addresses: every vendor, employee and debtor needs a city and a country.
- Inspect real XML files for the namespace and address blocks.
- Test with your bank using its format checker or test channel, and keep the result in writing.
- Plan reconciliation: confirm that batch payments still match bank statement lines after the switch.
For a wider look at your database, run the free Odoo health check tool. Our month-end close checklist for Odoo covers the bank reconciliation side.
How iVentureTeam helps with Odoo SEPA PAIN readiness

iVentureTeam checks your Odoo SEPA setup end to end, fixes what blocks pain.001.001.09, and tests files with your bank before you switch. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.
- Payment file audit: journals, payment method lines, PAIN versions and the XML your database really produces.
- Address cleanup: bulk fixes for missing cities and countries, plus split street fields where your bank wants structured data.
- Custom module review: we find code that forces old formats and rewrite it as a tested custom module.
- European rollouts: setup for SEPA countries through our Odoo implementation partner team for Germany and wider EU projects.
- Bank testing: test batches, bank format checks and reconciliation runs on a staging copy.
Our guide on how Odoo Accounting works is a good primer for team members new to journals and payment methods.
Odoo accounting customization case study: Fernando Tax Management
A Dutch tax and accounting firm moved to Odoo 18.0 and replaced manual, duplicated entries with one customized system. Fernando Tax Management B.V. is based in the Netherlands and was founded in 2008.
Its legacy system could not be adapted, and staff re-keyed data across systems. Reports and client documents also had translation gaps, which mattered because the output feeds government compliance.
We migrated the firm to Odoo 18.0 in 10 weeks, built a cost-tracking workflow in Sales and Purchase, and created tax compliance reports for the Netherlands and Curacao. Manual data entry fell by 60%. Read the Fernando Tax Odoo accounting automation case study.
The bottom line on Odoo SEPA PAIN 2026
If you run Odoo 19 or 20 with standard SEPA modules, you are most likely already sending pain.001.001.09, and your real work is addresses, direct debit and bank testing. Older versions and custom modules need a closer look.
The address deadline has moved, but bank format retirements have not waited for it. Confirm your bank's dates, clean partner data now and keep one tested XML file per payment type on record.
Ready to test your Odoo SEPA payment files?

Get a clear readiness report before your bank rejects a payment run. Ask for an Odoo SEPA payment file review, call +91-90235-15208, or email business@iventureteam.com.
Frequently Asked Questions
Does Odoo support pain.001.001.09?
+
Yes. Odoo's documentation for versions 19 and 20 says SEPA credit transfer files use PAIN.001.001.09 by default. You can choose another version on the bank journal if your bank or country requires it.
Is pain.001.001.03 still accepted after November 2026?
+
It depends on your bank. Odoo's docs say pain.001.001.03 is being deprecated in November 2026, and UniCredit HypoVereinsbank says only pain.001.001.09 is accepted for SEPA from then. Ask your bank for its date in writing.
Where do I change the SEPA PAIN version in Odoo?
+
Go to Accounting, Configuration, Journals, and open the bank journal. Use the Outgoing Payments tab for credit transfers and the Incoming Payments tab for direct debit. In Odoo 20 the outgoing format sits on the payment method line.
Was the 15 November 2026 structured address deadline cancelled?
+
It was postponed, not cancelled. The EPC removed the date in September 2026 and, on 29 October 2026, deferred setting a new one until February 2027. Structured or hybrid addresses remain the target.
What is a hybrid address in a SEPA file?
+
A hybrid address keeps town and country in their own XML elements and allows up to two free address lines for the rest. A fully structured address uses dedicated elements only, such as street name and building number.
Which pain.008 version does Odoo use for SEPA direct debit?
+
Odoo's 19 and 20 docs say SDD files follow PAIN.008.001.02 specifications, with a SEPA Pain Version field on the journal. Odoo 17 docs also named a pain.008.001.08 option. Confirm the version your bank needs.
Do I need to upgrade Odoo for SEPA 2026?
+
Usually not if you run Odoo 19 or 20 with standard modules. Older versions, copied journals or custom banking modules may still export old formats, so inspect a real XML file before you decide.
Can Odoo pay non-euro suppliers with ISO 20022?
+
Yes. SEPA methods only work for EUR. For other currencies, or for companies in EFTA and non-EEA SEPA countries, Odoo uses its ISO 20022 payment method, with country formats from your fiscal localization.
Free written answer from a certified consultant
Getting Odoo Accounting set up right?
We map your accounting, tax and reporting in Odoo and show what to set up first, and what to watch.
Free, with no obligation. A senior consultant replies within 12 business hours.
Free Odoo tools
All tools- Odoo Health CheckVersion, modules, findings and upgrade cost
- Odoo App SelectorWhich apps you need, by industry
- Odoo Project EstimateIndicative cost and timeline in minutes
- Odoo Implementation Cost CalculatorImplementation cost and timeline, in minutes
- Odoo Migration Cost CalculatorVersion jump or legacy ERP, priced in minutes
Continue reading
Spreadsheets After ERP Implementation: Why Odoo Users Keep Excel
Why teams keep Excel after an Odoo go-live, the hidden risks of shadow spreadsheets, and a fix plan using Odoo 20 Spreadsheet, Dashboards and imports.
Odoo ERP Implementation in Saudi Arabia: ZATCA, Arabic, Cost, Timeline
Odoo ERP implementation in Saudi Arabia: Odoo 19 vs 20, ZATCA Phase 2 onboarding, Arabic invoices, GOSI and WPS payroll, hosting, cost and timelines.
Odoo Post Implementation Review: 30/60/90 Day Checklist and Template
Run an Odoo post implementation review at 30, 60 and 90 days: go-live checklist, six KPIs, Odoo 19 and 20 checks and a report template you can copy.
