Bank integration · Danske Bank

How to connect your ERP or system to Danske Bank.

Danske Bank is in the A++ tier of bank integrations. When our team of bank integration experts hears it is Danske Bank, we know the project will be straightforward, whatever the volume or complexity. Their web service is the most stable and secure we work with, and their IntegrationServices support is filled with incredibly competent people who are quick to help.

Danske Bank connectivity profile

Formats, markets, setup.

Bank
Danske Bank A/S
Markets
Denmark · Finland · Sweden · Norway · Northern Ireland (UK) · Poland · Lithuania
Connectivity
Danske EDI Webservices (District Agreement)
Outgoing payments
pain.001.001.03 · pain.001.001.09 · domestic and SEPA credit transfers · all local payment types
Status reports
pain.002.001.03 acknowledgements and rejections
Statements
camt.053 end-of-day · camt.052 intraday · camt.054 debit/credit notifications · quality data by default
Special features
Seven-country coverage · User ID + Pin-code activation · Quality statement data by default
Security
User ID and Pin-code · Signed requests · Verified bank responses
Typical onboarding
A few minutes

Connectivity

Danske EDI Webservices.

You sign a District Agreement with EDI Webservices. Danske gives you a User ID and a Pin-code. Entering those into BankConnector is the only thing you need, and then your agreement is live. No certificates. A full test environment is available.

Coverage

Denmark, Finland, Sweden, Norway, Northern Ireland (UK), Poland and Lithuania. All local payment types supported.

Data quality

Quality data in bank statements by default. Clean, structured statement data that reconciles properly out of the box.

Getting started

You can easily download the files you need inside Danske Corporate Netbank. Their IntegrationServices support is always nice to help if you need anything.

Why integration quality matters

Anyone can POST a file to Danske Bank. Doing it properly is the hard part.

There are a lot of shortcuts vendors take to get a green checkmark in a demo. Skip the signature check. Fire-and-forget the upload. Call it integrated. It works right up until the day it quietly does not, and with payments, quietly does not means real money in the wrong place.

We do not build it that way. If you care about security and usability the way we do, you do the unglamorous work:

Verify bank signatures

Every response and statement file from Danske Bank is cryptographically verified before we trust a single byte of it. If a file is not signed by Danske, it does not enter your reconciliation.

Sign our own requests properly

Outbound payment files are signed per the Danske spec, with credentials encrypted at rest and never logged. Your signing material is treated like the crown jewels, because it is.

Handle duplicates, every time

Network blips, retries, and double-clicks happen. We use end-to-end identifiers and idempotency checks so a payment is submitted once. A resend never becomes a second debit.

Reconcile status, do not assume it

We do not mark a payment done because the upload returned 200. We read Danske Bank's pain.002 acknowledgements and camt statements back, match them to what we sent, and tell you the real state: accepted, rejected, or pending, with the reason.

Fail loudly and recover gracefully

Rejections surface with the bank's actual reason code, not a generic error. Retries are deliberate and bounded. Nothing important fails in silence.

Encrypt the sensitive bits end to end

Credentials and personal data are encrypted in transit and at rest. Not as a checkbox, but as the default everything else is built on.

The lazy version of this integration is faster to ship. Ours is the one you actually want sitting between your ERP and your bank account.

How a Danske Bank integration goes live

From signed agreement to first reconciled payment.

  1. 1. Signed agreement. You sign the District Agreement with EDI Webservices with Danske Bank, listing the accounts and services.
  2. 2. User ID and Pin-code. Danske gives you a User ID and a Pin-code. Enter them into BankConnector. That is the only thing you need, and then your agreement is live.
  3. 3. Production. You are live. Onboarding takes a few minutes from the moment the agreement is signed.Wait?? Legacy Bank Integrators really charges thousands for this process?

Things teams ask about Danske Bank

Common questions.

What do I need to set up EDI Webservices?

A District Agreement with EDI Webservices with Danske Bank. They give you a User ID and a Pin-code. Enter them in BankConnector and you are live. That is it.

What markets does Danske Bank cover?

Denmark, Finland, Sweden, Norway, Northern Ireland (UK), Poland and Lithuania. One integration covers all of them.

Does Danske support local payment types?

Yes. Danske Bank supports all local payment types in the countries they operate in.

How is Danske statement data quality?

Danske Bank provides quality data in their bank statements by default. Clean, structured statement data that reconciles properly out of the box.

How long does onboarding take?

A few minutes once the District Agreement is signed and you have your User ID and Pin-code.

Can we run test payments first?

Yes. Danske Bank has a full test environment. We run test payments and statement pulls end to end before switching to production, so you see real reconciliation before money moves.

Ready to connect your Danske Bank accounts?

Talk to us about your accounts and your country footprint. We will tell you exactly what Danske Bank needs you to sign and how soon you can be live.