How do I fix DK-R-010?

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

Is DK-R-010 a critical error?

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

Can DK-R-010 be automatically fixed?

Many instances of DK-R-010 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-010`:Danish suppliers using FIK payment (code 93) must provide PaymentID starting...

Danish suppliers using FIK payment (code 93) must provide PaymentID starting with 71#, 73#, or 75# and an exactly 8-character creditor number.

Severity

Fatal

Rule set

OIOUBL (Denmark)

Country

DNK

Fix type

AUTO-FIX

Confidence

75%

Engine Classification

Ensure Danish NemHandel endpoint is present

Confidence: 75% · Applied automatically in pipeline

What is DK-R-010?

DK-R-010 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[@schemeID='0088']

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by Danish validation. FIK payments require specific Danish format.

DK-R-010 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-010
·Specification: OIOUBL (Denmark)

Before / After

Failing XML

<Invoice>
  <!-- Issue: For Danish Suppliers the PaymentID is mandatory and MUST sta -->
</Invoice>

Corrected XML

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

Technical Reference

XPath//cac:AccountingCustomerParty/cac:Party/cbc:EndpointID[@schemeID='0088']

SpecOIOUBL (Denmark)

Operationset_default

StrategyEnsure Danish NemHandel endpoint is present

Common Causes

·PaymentID missing or wrong prefix for FIK
·Creditor number not exactly 8 characters
·Kortartkode prefix invalid (not 71#, 73#, 75#)
·FIK details incomplete
·Payment means 93 selected without FIK setup

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

Related Errors

DK-R-002

Danish seller Peppol address missing

DK-R-003

If ItemClassification is provided from Danish suppliers, UNSPSC version...

DK-R-014

Danish company registration number has wrong scheme code

Last updated: 27 February 2026

Share this guide:

Handle DK-R-010 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-010:Danish suppliers using FIK payment (code 93) must provide PaymentID starting...