How do I fix DK-R-003?

Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (DK-R-003). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is DK-R-003 a critical error?

Yes, DK-R-003 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can DK-R-003 be automatically fixed?

Many instances of DK-R-003 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

errorDNKOIOUBL (Denmark)

`DK-R-003`:If ItemClassification is provided from Danish suppliers, UNSPSC version...

Danish suppliers using item classification must use UNSPSC version 19.05.01 or 26.08.01. Other UNSPSC versions are not accepted for Danish e-invoicing.

Severity

Fatal

Rule set

OIOUBL (Denmark)

Country

DNK

Fix type

AUTO-FIX

Confidence

80%

Engine Classification

Ensure Danish buyer EAN/GLN endpoint identifier is present

Confidence: 80% · Applied automatically in pipeline

What is DK-R-003?

DK-R-003 is a fatal validation rule defined in the OIOUBL (Denmark) specification (DNK national rules). It validates the EndpointID element under Party in the UBL invoice XML.

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.

Target path: //cac:AccountingCustomerParty/cac:Party/cbc:EndpointID

Get API Access Test This Error ↓

Why This Error Matters

Invoice may be rejected by Danish validation. Item classifications must use approved UNSPSC versions.

DK-R-003 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.

Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.

Validator Behavior

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

Before / After

Failing XML

<Invoice>
  <!-- Issue: If ItemClassification is provided from Danish suppliers, UNS -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per OIOUBL (Denmark) -->
</Invoice>

Technical Reference

XPath//cac:AccountingCustomerParty/cac:Party/cbc:EndpointID

SpecOIOUBL (Denmark)

Operationset_default

StrategyEnsure Danish buyer EAN/GLN endpoint identifier is present

Common Causes

·Wrong UNSPSC version specified
·Old UNSPSC version used from legacy system
·Version identifier missing from classification
·ERP uses different UNSPSC version by default
·Classification copied from non-Danish invoice

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

Related Errors

DK-R-002

Danish seller Peppol address missing

DK-R-007

For Danish suppliers PaymentMandate/ID and PayerFinancialAccount/ID are...

DK-R-014

Danish company registration number has wrong scheme code

Last updated: 27 February 2026

Share this guide:

Handle DK-R-003 Automatically in Your Pipeline

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

Get API Access View API Documentation

DK-R-003:If ItemClassification is provided from Danish suppliers, UNSPSC version...