Account
English

DK-R-013: For Danish Suppliers it is mandatory to use schemeID when PartyIdentification/ID is…

Peppol national rule · Error · UBL, CII

StandardPeppol BIS Billing 3.0 country rules (NL, DE, IT, SE, DK, NO, GR, IS)CountryDenmarkSeverityError: the invoice is rejectedSyntaxUBL, CIIApplies toOnly when the seller (or for some rules the buyer) is in the named country: the rule is triggered by the country code of the party. Dutch rules implement NLCIUS, German rules the XRechnung requirements inside Peppol.

Official rule text

[DK-R-013] For Danish Suppliers it is mandatory to use schemeID when PartyIdentification/ID is used for AccountingCustomerParty or AccountingSupplierParty

Why this error occurs

This rule only applies when another field has a certain value (for example a payment means code or an invoice type). Your file triggers the condition but does not provide the data that then becomes mandatory, or provides data that is then forbidden.

How to fix it

Either change the triggering value so the condition no longer applies, or add/remove the dependent elements as the rule text describes. Check the condition in the XPath test above to see exactly which value triggers it.

What the validator checks

Checked element (context):

UBL

ubl-creditnote:CreditNote[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification | ubl-creditnote:CreditNote[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification | ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification | ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification

Test (XPath):

not((boolean(cbc:ID))
						 and (normalize-space(cbc:ID/@schemeID) = '')
						)

CII

rsm:CrossIndustryInvoice[$DKSupplierCountry = 'DK']

Test (XPath):

not(($DKCustomerCountry = 'DK') and
                                  ( ((boolean(rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:GlobalID))
                                     and (normalize-space(rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:GlobalID/@schemeID) = ''))
                                   or
                                    ((boolean(rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:GlobalID))
                                     and (normalize-space(rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:GlobalID/@schemeID) = ''))
                                  )
                              )

Check your invoice

Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.

Check your invoice →

Same check via API:

curl -F file=@invoice.xml https://einvoicechecker.com/v1/validate

Related rules

Frequently asked questions

What does DK-R-013 mean?

DK-R-013 is a peppol national rule: For Danish Suppliers it is mandatory to use schemeID when PartyIdentification/ID is used for AccountingCustomerParty or AccountingSupplierParty

Will my invoice be rejected because of DK-R-013?

Yes. DK-R-013 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals, KSeF) reject the invoice until it is fixed.

Which formats does DK-R-013 apply to?

Only when the seller (or for some rules the buyer) is in the named country: the rule is triggered by the country code of the party. Dutch rules implement NLCIUS, German rules the XRechnung requirements inside Peppol. Syntax: UBL and CII.

Source: Peppol BIS Billing 3.0.20 national rules (November 2025). Catalogue generated from the official rule sets on 2026-10-15.