Nordea Denmark: EDI4/UTF is gone for cross-border and SEPA — what to send instead
Last updated: 15 Nov 2026
This is for finance teams that send payment files to Nordea Denmark in the legacy EDI4/UTF format. Since 15 November 2026 that format can no longer be used for cross-border and SEPA payments, so those payments have to go out as ISO 20022 pain.001.
What changed
- From 15 November 2026, Nordea Denmark no longer accepts EDI4/UTF files for cross-border and SEPA payments. Nordea e-Markets support
- Domestic payments: the expected date for the end of EDI4/UTF is Q1 2027; after that the legacy formats are removed completely. Nordea e-Markets support
- pain.001.001.03 is still accepted by Nordea, so you do not have to move to a newer pain.001 version to send these payments. Nordea e-Markets support
- Unstructured addresses are not rejected after 15 November 2026; Nordea accepts all three address formats. Nordea: upcoming changes in cash management
Dates at a glance
| Date | What happens | Source |
|---|---|---|
| 15 Nov 2026 | EDI4/UTF can no longer send cross-border and SEPA payments | Nordea e-Markets |
| Q1 2027 (expected) | EDI4/UTF for domestic payments ends; the formats are then removed completely | Nordea e-Markets |
| H1 2027 | Address requirements for payments to Denmark | Nordea ERP newsletter, April 2026 |
| Q2 2027 | DKK bulk payments move to STEP2 DKK | Nordea ERP newsletter, April 2026 |
The full picture is on one page: Denmark payments 2027 timeline.
What to send instead
Send a pain.001 credit transfer file. For Nordea Denmark that is pain.001.001.03 with MIXD grouping and the debtor bank BIC NDEADKKK. The Nordea profile in the Nordea converter applies this setup and asks for the debtor BIC.
Five Nordea checks to get right first
The validator checks Nordea files with 18 rules (14 errors and 4 warnings). These five are the ones most worth knowing when you leave EDI4/UTF behind, because they concern how pain.001 is built rather than your data:
| Rule | What Nordea expects | Typical fix |
|---|---|---|
| N1 (error) | PmtTpInf at one level only: payment-information or transaction, not both; LclInstrm only at payment-information level | Keep PmtTpInf once, at PmtInf level |
| N2 (error) | LclInstrm/Cd is SDCL or NDAV, or absent; ONCL is not valid for Nordea | Use SDCL or NDAV, or remove LclInstrm |
| N4 (error) | Payments to an EU/EEA creditor use ChrgBr SHAR or SLEV; DEBT is rejected | Set ChrgBr to SHAR or SLEV |
| N9 (error) | Each Ustrd has at most 140 characters; cross-border total 140, domestic total 1435 | Shorten the remittance text |
| N18 (error) | A domestic account without IBAN is exactly 14 digits: 4 registration + 10 account, zero-padded | Pad to 14 digits, no separators |
Every rule, with an example and the fix, is listed on Nordea pain.001 validation rules.
From Excel to a Nordea-ready pain.001
- Put one payment per row in Excel: recipient name, recipient IBAN (or 14-digit account for domestic DKK), amount, currency and your reference.
- Open the converter with the Nordea profile and upload the file. Map your columns to the payment fields.
- Check the notices. The Nordea profile flags rows Nordea would reject, shortens names that are too long and shows every change.
- Download the pain.001.001.03 XML and run it through the validator with the Nordea result open.
- Upload the file to Nordea. If you generate files at volume, the API applies the same profile.
Check your Nordea file before you send it
The validator runs all 18 Nordea checks and opens the Nordea result for you.
Validate a Nordea pain.001 fileSources
Ready to generate bank-compliant SEPA XML files?
Stop struggling with manual formatting. Generate compliant ISO 20022 XML files in seconds directly in your browser.
Start Converting Now (Free)