DK-R-013:Danish suppliers must specify the schemeID when using PartyIdentification/ID...
Danish suppliers must specify the schemeID when using PartyIdentification/ID for either supplier or customer. The scheme identifies what type of ID is being used.
Engine Classification
Ensure order reference is present for Danish public invoices
Confidence: 80% · Applied automatically in pipeline
What is DK-R-013?
DK-R-013 is a fatal validation rule defined in the OIOUBL (Denmark) specification (DNK national rules). It validates the ID element under OrderReference 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: /Invoice/cac:OrderReference/cbc:ID
Why This Error Matters
Invoice will be rejected by Danish validation. Party IDs must include scheme identifier for proper interpretation.
DK-R-013 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-013
- ·Specification: OIOUBL (Denmark)
Before / After
<Invoice> <!-- Issue: For Danish Suppliers it is mandatory to use schemeID when Pa --> </Invoice>
<Invoice> <!-- Issue resolved per OIOUBL (Denmark) --> </Invoice>
Technical Reference
/Invoice/cac:OrderReference/cbc:IDCommon Causes
- ·SchemeID missing from party identification
- ·ID provided without scheme identifier
- ·ERP does not export scheme information
- ·Party ID copied without scheme attribute
- ·Manual invoice creation missed scheme requirement
Seeing this in production? The API handles DK-R-013 automatically. See the fix response →
Related Errors
Last updated: 27 February 2026
Handle DK-R-013 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.