Skip to main content

Upcoming Changes and New Releases

On this site, you can find information about upcoming changes and new releases related to files, channels and security.

Subscribe to receive email notifications for new and updated announcements on the Upcoming Changes and New Releases page related to Integration Services. To get started, create an account and select Integration Services from the dropdown menu. You can unsubscribe at any time.

Subscribe for updates here

Latest update 28 May 2025

 

  • No action required

    In the File Validation Tool you can validate pain.001.001.03 payment initiation files against the overall ISO 20022 XML schema standard. If the file is schema valid, the tool can also validate the payments and display some Payment Details e.g.

    • Amount
    • Date
    • Payment type
    • Payment status

    To learn more about the File Validation tool and to test your files, click here.

  • Action required

    From 1 May 2025, the Bank of England has introduced new Purpose Codes for property transactions made by CHAPS payments. You can find the full list of UK Purpose Codes on the Bank of England website. There will be further changes to the CHAPS payment journey over the coming months, including a full list of purpose codes and address requirements. These will be advised in due course.

    What does it mean for you?

    • The use of CSV/Paymul files for CHAPS payments should no longer be used from 1 May.  We would encourage you to use the ISO 20022 XML file format from this date.
    • Please add a purpose code to your file payments.
    • To ensure the purpose code is included with the payment, we strongly recommend that you going forward use the ISO 20022 XML pain.001.001.03. format to initiate CHAPS payment.

  • Action required

    From 5 October 2025, SEPA payments will follow the EPC (European Payments Council) Guidance document about use of address fields.

    As a result, Hybrid Address of Beneficiary will be introduced.

    It is not mandatory to include beneficiary’s address in SEPA payments but if you initiate SEPA payments in ISO 20022 XML format, then beneficiary’s address should comply with one of the below formats:

    • UNSTRUCTURED ADDRESS - until 22 November 2026
    • STRUCTURED ADDRESS - 'Town Name' and 'Country' are mandatory. 'Address Line' is not allowed. It is recommended to provide as many structured elements as possible.
    • HYBRID ADDRESS - 'Town Name' and 'Country' are mandatory. At least one occurrence of 'Address Line' is mandatory.

    If beneficiary’s address does not comply with the requirements, then beneficiary’s address will be ignored and the SEPA payment will be sent for processing without any beneficiary’s address.

    We recommend you switch to ISO 20022 XML and use structured Beneficiary’s address in SEPA payments.

  • Action required

    Payment infrastructure in Sweden is undergoing modernisation works. The most important changes are:

    • Migration from the existing Bankgirot’s file formats – KI, LB and BgMax – to the ISO 20022 XML format.
    • All file communication will no longer go via Bankgirot and will be routed via each bank instead.

    Danske Bank deadlines for Swedish legacy formats:

    • KI-Lön - 14 November 2025.
    • LB (Leverantörsbetalningar), Utlands-LB - 12 May 2026.
    • Account transfer with long-form advice - Gradually discontinued during 2026 (same as sector deadlines).
    • Money orders (Värdeavier) - 8 September 2026.
    • BG Max format  - 27 November 2026 (same as sector deadline).

    To find out more, please visit our dedicated Swedish sector transformation page here.

    Additionally, Swedish Domestic Batch payments will move to the new clearing by 27 November 2026. We recommend transitioning to ISO 20022 XML to be prepared for the new clearing process. Please see more details here.

  • Action required

    From 22 November 2026, use of Unstructured address on beneficiary will no longer be accepted in SEPA payments. SEPA payments follow the EPC (European Payments Council) Guidance document about use of address fields.

    It is not mandatory to include beneficiary’s address in SEPA payments but if you initiate SEPA payments in ISO 20022 XML format, then beneficiary’s address should comply with one of the below formats:

    • STRUCTURED ADDRESS - 'Town Name' and 'Country' are mandatory. 'Address Line' is not allowed. It is recommended to provide as many structured elements as possible.
    • HYBRID ADDRESS - 'Town Name' and 'Country' are mandatory. At least one occurrence of 'Address Line' is mandatory.

    If beneficiary’s address does not comply with the requirements, then beneficiary’s address will be ignored and the SEPA payment will be sent for processing without any beneficiary’s address.

    We recommend you switch to ISO 20022 XML and use structured Beneficiary’s address in SEPA payments.

  • Action required

    Swedish Domestic Batch payments will have moved to a new clearing by 27 November 2026, and we recommend transitioning to ISO 20022 XML to be ready for the new clearing when it arrives.

    Please see more details here.

  • Action required

    During 2025 the security requirements for SFTP file transfer service will be upgraded.

    Log on keys must be:

    • FIPS 140-2 compliant
    • SSH-2 with key type RSA (recommended), DSA, or ECDSA
    • Minimum 2048 bits

    Host key algorithms supported will be RSA-256 and RSA-512 only.

    Please contact Integration Services in Danske Bank if you need to get your public key validated.

  • No action

    SWIFT network (CBPR+) is changing the messaging standard from the current MT format to the ISO 20022 XML format for payment initiation and statement messages. 

    Via the communication channel SWIFTNet Fileact, Danske Bank will continue to support  

    • MT101 – Payment initiation
    • MT940 – Account statement
    • MT941 – Balance report
    • MT942 – Transaction report

    until at least 2028.

    If you have accounts in other banks and access them via Danske Bank, your MT-files may be impacted. We will keep you updated here.

  • No action required

    In two to three years, Danske Bank will support the below messages

    • camt.052.001.08
    • camt.053.001.08
    • camt.054.001.08

    camt-messages v.8 offer more features i.e. StatementPagination and Unique Technical Reference.

    We will notify you in due time regarding plans for other payment related ISO 20022 XML message types that we will support.
Stay Informed with Our Subscription Service

Subscribe to receive email notifications for new and updated announcements on the Upcoming Changes page related to Integration Services. To get started, create an account and select Integration Services from the dropdown menu. You can unsubscribe at any time.

Subscribe for updates here

Archive of past events

  • 1 May 2025 - Telepay and BBS formats no longer accepted

    Action required

    Danske Bank will not accept the Norwegian formats Telepay and BBS (Direct Remittance) and we recommend you to move to ISO 20022 XML formats at your earliest convenience.

    You can find more information here: Moving from Telepay and BBS to ISO 20022 XML: What You Need to Know.

    22 April 2025 - Danish Domestic Instant (Express) payments will be cleared via new clearing platform, TIPS

    Action required

    From 22 April 2025 Danish Domestic Instant (Express) payments will follow the NPC rulebook for payments.

    This means

    • beneficiary name will be mandatory for all Danish Domestic Instant payments - if beneficiary name is not provided, the payment will be rejected
    • the ‘Message to beneficiary’ field will be limited to a maximum of 140 characters of text. Any message exceeding the limit will be cut after 140 characters.
    • the ‘Text on beneficiary’s account statement’ field will not be supported for instant payments and will be ignored. To include information regarding the payment, you should use the ‘Message to beneficiary’ field instead.

    You can find more information on our website or read the NPC rulebook for payments to familiarize yourself with the new ruleset and adjust your payments accordingly from 22 April 2025.

    30 November 2024 - Some Danish and Irish payment formats will no longer be accepted

    Action required

    Danske Bank will not accept these formats anymore and we recommend you to move to ISO 20022 XML format.

    • PBS-OS: Danish Payments in PBS-OS format processed by Danske Bank. (The pass-through solution with Danske Bank as data provider to MasterCard Payment Services is not affected by the change)
    • KASEL - Danish payments in KaSel format
    • CMIIS - Irish bulked payments in Danske Bank comma separated format

    15 November 2024 - EDIsec security solution will no longer be supported

    Action required

    Danske Bank will stop supporting EDIsec security solution on 15 Nov 2024. We recommend you to move to the new OpenPGP solution at your earliest convenience.

    If you haven't been contacted by Integration Services yet, please reach out to ints@danskebank.com

    October 2024 - Swedish Domestic Instant payments will be cleared via new clearing platform, TIPS

    No action required

    Danske Bank will not support outgoing Swedish Domestic Instant payments for the time being.

    However, you will potentially start receiving Swedish Domestic Instant payments.

    Swedish Domestic Instant payments will follow the NPC rulebook for payments, meaning the payment data might look different compared to a Swedish Domestic Batch or Swedish Domestic Express payment.

We recommend you to switch to ISO 20022 XML

Watch video about ISO 20022 XML and read implementation guides
View benefits of moving to ISO 20022 XML
How to prepare your payment initiation files for future changes


Benefits of moving to ISO 20022 XML format

A global, standardized format for all payment types

  • You can initiate different types of payments across currencies in one file (versus several) allowing for simplification and cost savings
  • When you need to update your payment files – e.g., due to regulation – you only need to update one file format
  • ISO 20022 XML follows defined standards, meaning increased degree of standardization across systems and involved parties

You are prepared for the future

  • ISO 20022 XML is a flexible, extendable format, which means that it allows for the addition or modification of information if needs or requirements change (e.g., due to regulation)
  • By using ISO 20022 XML you are prepared for the future as ISO 20022 XML will support future changes and requirements
  • ISO 20022 XML improves compliance screening making your payments safer

Access to all payment features and richer data

  • New features and options will always be possible to utilize using ISO 20022 XML as future development will be focused on XML
  • Since XML is extendable it allows for carrying more structured data for e.g. reconciliation
  • You can use existing and new payment features when you prefer since ISO 20022 XML is a flexible format that allows you to conduct payments based on your needs

How do I validate my payment files?

If you want to validate your pain.001.001.03 payment initiation files as part of the transition to XML, you can use our file validation tool.

Open validation tool


How to prepare your payment initiation files for future changes

The table below gives you an overview of the features and requirements that have to be fulfilled when NPC rulebook for payments becomes effective. For each format, you can see how to include the required information and how to use optional features when NPC rulebook for payments becomes effective.

 

Field/FeatureMandatory or Optionalpain.001.001.03
MIG*
Examples		EDIFACT
MIG*
Examples		MT101
MIG*
Examples		Danske Bank format
MIG*
Examples 		When can I add the field/feature to my payment file
Creditor name MandatoryYesYes
Yes
PartlyNow
Unstructured adviceOptional
Yes
Yes
Yes
YesNow***
OCR referenceOptional
Yes
Yes
Yes
Yes
Now**
InvoiceOptional
Yes
No
No
No
To be confirmed
RF referenceOptional
Yes
Partly - see MIGNo
Yes
To be confirmed
Extended Remittance Information (ERI)Optional
Yes
No
No
No
Partly - see Appendix K
Ultimate creditorOptional
Yes
No
No
No
Now - will be ignored
Ultimate debtorOptional
Yes
Yes
No
No
Now - will be ignored
SalaryOptional
Yes
Yes
No
Yes
Now


* Message Implementation Guide
** Already supported in local Swedish clearing
*** Already supported in local Swedish clearing as a payment with long form advice

FAQ about ISO 20022 XML

  • Do I need to change file format?

    If you initiate Swedish domestic payments via:

    • ISO 20022 XML you can continue to use the format.
    • EDIFACT you can continue to use the format with limited support for new features.
    • Danske Bank formats you can continue to use the format with limited support for new features.
    • MT101 you can continue to use the format with limited support for new features.
    • Bankgirot's formats for Bankgiro supplier- and salary payments you must switch to ISO 20022 XML. (Customers using this service can NOT see payment details in the List of outgoing payments screen in District when sending payment files to Danske Bank)
    • Bankgirot's formats for Danske Bank supplier- and salary payments you must switch to ISO 20022 XML. (Customers using this service CAN see payment details in the List of outgoing payments screen in District when sending payment files to Danske Bank)

  • Which payment date should I use for salary payments in ISO 20022 XML format?

    The payment date in <ReqdExctnDt> should be the date for when the beneficiary’s account will be credited.  The salary file must be sent to the bank at the latest at 12.30 the banking day before the payment date written in <ReqdExctnDt>.

    Ask your ERP-vendor how to set this up correctly in your system.

  • How do I bulk debet my payments in ISO 20022 XML format?

    When you send an ISO 20022 XML file to Danske Bank, then you can decide if you want your payments to be debited as single transactions or as a bulked amount. 
    To bulk debit a payment file, then the file must be structured with one debit transaction and two or more underlying credit transactions.

    Example:
    Single transactions (more <PmtInf> tags)

    <PmtInf> Start payment 1
    <DbtrAcct> Sender account payment 1
    <CdtTrfTxInf> Start credit payment 1
    <CdtrAcct> Beneficiary's account payment 1
    </CdtTrfTxInf> End credit payment 1
    </PmtInf> End payment 1
    <PmtInf> Start payment 2
    <DbtrAcct> Sender account payment 2
    <CdtTrfTxInf> Start credit payment 2
    <CdtrAcct> Beneficiary's account payment 2
    </CdtTrfTxInf> End credit payment 2
    </PmtInf> End payment 2


    Bulked transaction (One <PmtInf> tag and more <CdtTrfTxInf> tags)
    <PmtInf> Start bulk debit
    <DbtrAcct> Sender account bulk debit
    <CdtTrfTxInf> Start credit payment 1
    <CdtrAcct> Beneficiary's account payment 1
    </CdtTrfTxInf> End credit payment 1
    <CdtTrfTxInf> Start credit payment 2
    <CdtrAcct> Beneficiary's account payment 2
    </CdtTrfTxInf> End credit payment 2
    </PmtInf> End bulk debit

    Please reach out to your ERP vendor to set up your system to fit your needs

    Appendix B: Use of 2.3 BtchBookg gives detailed information about the <BtchBookg> tag and bulk debitering rules.

  • Which ISO 20022 XML reconciliation files can I get?

    Danske Bank supports the following reconciliation file in ISO 20022 XML formats:

    • camt.052.001.02 - Account report
    • camt.053.001.02 - Account statement with balance
      The file contains incoming and outgoing transactions including end of day balance
    • camt.054.001.02 - Debit credit notification - transaction list
      The file has several options:
      • Both Debit and Credit transactions
      • Only Debit transactions  (All debit transactions on the account or only debit transactions from ISO 20022 XML payment files)
      • Only Credit transactions (All credit transactions on the account)

    Please note! Bankgiro Recivebles (BGI) can be included  in CAMT053 (extended) and CAMT054.

    You can find more information about the reconciliation files here.

    To order the reconciliation files, you need to contact: ints@danskebank.com (Please provide account number, file type, UserID)

  • Which options do I have in a pain.002.001.03?

    For each pain.001.001.03 file, Danske Bank will create one or more pain.002.001.03 files (PSR)

    • Feedback on file level
    • Feedback on payment level

    Per default, a PSR on file level will be created and if any payment is rejected, then a PSR on payment level will be created too.

    In the pain.001.001.03 file, you can choose which type of PSR you want.

    Example:
    If you do not want any feedback on payment level, then the <Authstn> tag can be used.
    <Authstn>
    <Prtry>Feedback=XI</Prtry>
    </Authstn>

    Danske Bank offers several types of PSRs on payment level – see Appendix A: Use of 1.3 Authstn

  • How do I use invoices and credit notes in my domestic Swedish payments in ISO 20022 XML?

    If you want to include invoices and credit notes in your domestic Swedish payments in ISO 20022 XML format, then you need to follow some rules:

    • Only Swedish Bankgiro payments and Account transfers support invoices and credit notes
    • Invoices and credit notes must be sent in the same payment file
    • Invoices and credit notes must have the same date
    • OCR number cannot be used
    • Amount must be higher than 0 (zero) 
    • Credit notes will no longer be monitored 
    • Due to limitation in the current clearing channel in Sweden, we recommend to use only 10 <Strd> (Structured) tags with invoices and credit notes until the Swedish clearing channels are updated.

    Appendix K provides more detailed information about how to use invoices and credit notes.

  • Which payment types and remittance information can I use for my Swedish payments?

    Danske Bank offer several Swedish domestic payment types:

    • Salary

    • Account transfer – short advice (Max. 12 characters)
    • Account transfer – long advice (Max. 525 characters) 
      • Beneficiary address must be included in the file  (<PstCd> and <TwnNm>)

    • Cash payment (will disappear when Swedish clearing channels have been updated)

    • Bankgiro Transfer – Text  (Max. 25 characters) 
    • Bankgiro Transfer – OCR reference (Max. 25 characters) 
    • Bankgiro Transfer – Long advice (Max. 525 characters)

    • Plusgiro Transfer – Text  (Max. 25 characters) 
    • Plusgiro Transfer – OCR reference (Max. 25 characters)
    • Plusgiro Transfer – Long advice (Max. 10*35)

    When the Swedish clearing channels have been updated, Nordic Credit transfer and Nordic Salary will replace the above payment types and Beneficiary's name will be mandatory. 

    Appendix L: provides more details about Nordic Credit Transfers and Nordic Salary (only SEK and from Swedish accounts).

Channels and security

Danske Bank offers a wide range of channels for data sharing. Here you get an overview of channels available and required security solution for each channel.

Read more

File formats

Do you want to read about other formats than ISO 20022 XML?

Read more

Contact Integration Services

If you have questions or need to know more, please reach out to:
integration-services@danskebank.com

Want to get in touch?

Contact us
Show
Hide
Show more rows: All table rows are already visible for screen readers.
Show less rows: All table rows are already visible for screen readers.