Convert Excel to Nordea pain.001 XML
Convert Excel or CSV to Nordea-ready pain.001.001.03 for Danish payments.
Nordea (Denmark) profile
Open the converter with the Nordea bank profile already selected.
Launch ConverterWhat's changing at Nordea Denmark
- Nordea is decommissioning its legacy file formats (EDI4/UTF) in Denmark.
- Cross-border and SEPA payments: from 15 November 2026 you can no longer send them with EDI4/UTF.
- Domestic payments: EDI4/UTF is expected to end in Q1 2027; the formats are then removed completely.
- Replacement: ISO 20022 pain.001. Nordea continues to accept pain.001.001.03.
- Address rules for payments to Denmark apply in the first half of 2027; Danish krone bulk payments move to STEP2 DKK in Q2 2027.
- Unstructured addresses are not rejected after 15 November 2026; Nordea accepts all three address formats.
Last updated: 15 Nov 2026
Source: Nordea's announcement. All sources are listed at the bottom of the page.
What Nordea expects in a pain.001 file (Denmark)
- Service level NURG on standard payments; no local instrument for standard Danish domestic transfers.
- Charge bearer SHAR or SLEV for payments within the EU/EEA (DEBT is rejected).
- Creditor BIC required for cross-border payments; only Nordea-supported clearing codes.
- Recipient name: up to 35 characters domestic, 70 cross-border.
- Execution date within −7 to +365 days.
How the converter handles it
- Select the Nordea bank profile; the converter applies these rules and flags rows Nordea would reject before you download.
- Long names are shortened and every change is shown to you.
- If your debtor BIC is a Nordea BIC but you chose a generic profile, you're prompted to switch.
How the validator checks Nordea files
Nordea Denmark files are checked with 18 rules (14 errors, 4 warnings: N5, N8, N13, N16). Validate a Nordea pain.001 file to see which rule a file breaks, or read all 18 rules with examples and fixes.
pain.001.001.03 credit transfers (domestic DKK and cross-border). pain.001.001.09 for Nordea: planned.
Generate Nordea XML now
Bank-Grade Security
Your financial data security is our top priority. The free converter processes your file locally and never uploads it. Optional features — AI address-parsing, our Developer API, and Payroll recipient storage — do process data on our servers; see our Privacy Policy for details.
No Data Storage
We do not store your files. They are processed and deleted immediately.
Client-Side Processing
Data processing happens securely in your browser session.
SSL Encrypted
All transfers are protected by 256-bit SSL encryption.
Simple, Transparent Pricing
Choose the plan that fits your needs.
Free Preview
Validate your Excel files and preview the output structure.
- Unlimited Validations in the Converter
- IBAN & BIC Check
- Preview XML Structure
- Privacy-First Processing
24-Hour Pass
Unlimited use of the converter and camt → Excel for 24 hours.
- Unlimited XML & NACHA downloads for 24 hours
- camt → Excel without the daily limit
- Full IBAN visibility
- No subscription
Pro Subscription
For regular users who need unlimited access.
- Unlimited XML Downloads
- SEPA + SWIFT + NACHA support
- Priority Support
- Cancel Anytime
Teams
For teams up to 5
For teams who want to share company settings and mappings across up to 5 members.
- Everything in Pro
- 5 team members included
- Shared company settings & mappings
- SEPA + SWIFT + NACHA support
Business
For teams that need reliability guarantees
- Everything in Pro
- API access — SEPA + NACHA generation & validation
REST API with sandbox environment
- Dedicated support & SLA
- Priority onboarding
- Multi-entity / multi-subsidiary licensing
Enterprise
For larger organizations
For organizations that need on-premise deployment, ERP integration, and dedicated support.
- On-premise / self-hosted deployment
- SAP, Oracle, NetSuite integration
- Custom business rules & approval limits
- Dedicated support & SLA
- Multi-entity / multi-subsidiary licensing
Nordea pain.001 FAQ
Does Nordea still accept pain.001.001.03?
Yes. Nordea continues to accept pain.001.001.03.
What happens to my payments on 15 November 2026?
From 15 November 2026 you can no longer send cross-border and SEPA payments to Nordea Denmark with EDI4/UTF. Send them as ISO 20022 pain.001 instead.
When do domestic EDI4/UTF payments stop?
The expected date for domestic payments is Q1 2027. After that the legacy formats are removed completely.
Are payments with unstructured addresses rejected after 15 November 2026?
No. According to Nordea, payments with unstructured addresses are not rejected after 15 November 2026; all three address formats are accepted.
Do I need a local instrument code for Danish domestic payments at Nordea?
Not for standard transfers. Nordea uses SDCL only for same-day payments.
Is my data uploaded?
Your financial data security is our top priority. The free converter processes your file locally and never uploads it. Optional features — AI address-parsing, our Developer API, and Payroll recipient storage — do process data on our servers; see our Privacy Policy for details.
Sources
- Nordea e-Markets support: EDI4/UTF changes in Denmark
- Nordea: upcoming changes in cash management
- Nordea ERP newsletter, April 2026 (PDF)
Nordea is referenced here for informational purposes to describe file format compatibility. This tool is not affiliated with or endorsed by Nordea. Nordea is a trademark of its respective owner.
Nordea (Denmark) rules in this tool
Read directly from the rule file our validator uses for Nordea (Denmark).
File settings
How the converter writes the XML when the Nordea (Denmark) profile is selected.
| Topic | Setting |
|---|---|
| Message version | The file is written as pain.001.001.03. |
Bank-specific checks
What the validator tests when you check a file against Nordea (Denmark).
| Check | What it tests | Severity |
|---|---|---|
| Payment type at one level only | PmtTpInf must be given at PmtInf level or at transaction level, not both; LclInstrm only at PmtInf level | Error |
| Local instrument | LclInstrm/Cd must be SDCL or NDAV (or absent); ONCL is not valid for Nordea | Error |
| No intermediary agent | IntrmyAgt1 must not be used | Error |
| Charge bearer within EU/EEA | Payments to an EU/EEA creditor must use ChrgBr SHAR or SLEV; DEBT is rejected | Error |
| SEPA service level for EUR | Nordea expects SvcLvl SEPA for EUR to SEPA countries; NURG may be processed as a cross-border payment. | Warning |
| Creditor agent BIC for cross-border | Cross-border payments (creditor country other than DK) need the creditor agent BIC or a valid ClrSysMmbId; not required for SEPA payments (SvcLvl SEPA, or EUR to a SEPA country with an IBAN) | Error |
| Clearing system code | ClrSysMmbId needs ClrSysId/Cd of AUBSB, CACPA, GBDSC, HKNCC, INFSC, NZNCC, USABA or ZANCC; DKNCC is not valid | Error |
| Debtor agent BIC | Debtor agent BIC is not NDEADKKK (Nordea DK file) | Warning |
| Remittance information length | Each Ustrd element max 140 characters; total 140 cross-border, 1435 domestic (DK to DK in DKK) | Error |
| Forbidden characters | The characters < > " & ¤ are not allowed (ÆØÅæøå are allowed) | Error |
| Identifier slashes | MsgId, PmtInfId, InstrId and EndToEndId must not start or end with "/" or contain "//" | Error |
| EndToEndId length | EndToEndId may have at most 35 characters | Error |
| EndToEndId prefix unique | The first 20 characters of EndToEndId are not unique in the file (the statement shows only those) | Warning |
| Creditor name length | Creditor name max 70 characters cross-border, 35 domestic (DK to DK in DKK) | Error |
| Hybrid address | Address: at most 2 AdrLine together with TwnNm and Ctry | Error |
| Execution date window | Execution date is more than 7 days in the past or 365 days ahead | Warning |
| Amount digits | Amount: at most 11 integer and 2 decimal digits | Error |
| Domestic account number | Domestic BBAN (no IBAN) must be exactly 14 digits: 4 registration + 10 account, zero-padded, no separators | Error |