errorDNKOIOUBL (Denmark)

DK-R-006:For Danish suppliers bank account and registration account is mandatory if...

Danish suppliers using payment means 31 (credit transfer) or 42 (payment to bank account) must provide both bank account number and registration number.

Severity
Fatal
Rule set
OIOUBL (Denmark)
Country
DNK
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: Danish banking requirements mandate specific account information for payment processing. Bank details must be verified with your financial institution.

What is DK-R-006?

DK-R-006 is a fatal validation rule defined in the OIOUBL (Denmark) specification (DNK national rules). It checks whether for danish suppliers bank account and registration account is mandatory if....

When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

This error requires manual correction — financial fields are protected by policy.Test This Error ↓

Why This Error Matters

Invoice will be rejected by Danish validation. Bank transfers require complete account information.

DK-R-006 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

Validator Behavior

  • ·Causes invoice rejection
  • ·Fails UBL schema validation
  • ·Error returned: DK-R-006
  • ·Specification: OIOUBL (Denmark)

Before / After

Failing XML
<Invoice>
  <!-- Issue: Danish suppliers using credit transfer must provide bank acc -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per OIOUBL (Denmark) -->
</Invoice>

Technical Reference

SpecOIOUBL (Denmark)
StrategyBLOCKED: Bank account and registration numbers are sensitive financial data. Cannot generate or guess these values. Must be provided from verified banking records.

Common Causes

  • ·Bank account missing for credit transfer payment
  • ·Registration number not provided
  • ·Payment means changed without adding bank details
  • ·ERP does not export bank details for this payment type
  • ·Bank information stored separately from invoice

Seeing this in production? The API handles DK-R-006 automatically. See the fix response →

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle DK-R-006 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.