ErrorPeppol BIS 3.0Input required

DK-R-010

For Danish Suppliers using PaymentMeansCode 93, PaymentID is mandatory. The first three characters of the PaymentID MUST be 71#, 73# or 75# (kortartskode), and PayeeFinancialAccount/ID MUST be exactly 8 characters long.

What does this rule mean?

The Danish payment reference is not in the form required for this payment means.

Danish giro/card payment means (50, 93) encode the card type code as a prefix of the payment reference (e.g. 01#, 04#, 15#, 71#, 73#, 75#) and require an account identifier of fixed length alongside.

Official rule message (standard)

For Danish Suppliers using PaymentMeansCode 93, PaymentID is mandatory. The first three characters of the PaymentID MUST be 71#, 73# or 75# (kortartskode), and PayeeFinancialAccount/ID MUST be exactly 8 characters long.

Where the rule applies

Syntax: CII · UBL

The same rule, expressed twice: UBL and CII name the same fields with different paths. Running a CII file against the UBL rules is why you get errors that mean nothing.

UBL

  • ubl-invoice:Invoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/cac:PaymentMeans

CII

  • rsm:CrossIndustryInvoice[$DKSupplierCountry = 'DK' and $DKCustomerCountry = 'DK']/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans

Technical test

The rule passes when this Schematron expression holds true:

not((ram:TypeCode = '93')
                              and not(((substring(../ram:PaymentReference, 0, 4) = '71#')
                                        or (substring(../ram:PaymentReference, 0, 4) = '73#')
                                        or (substring(../ram:PaymentReference, 0, 4) = '75#'))
                                      and (string-length(ram:PayeePartyCreditorFinancialAccount/ram:IBANID/text()) = 8)
                                      )
                              )

How to fix it

A missing or incorrect business entry only you can supply. Add or correct it, then re-check.

Set the right prefix and digit sequence in the payment reference, and check the length of the account identifier.

Correct the affected entry in your XML, then re-check the invoice. Validation runs locally in your browser — your file never leaves your machine.

Check an e-invoice here

Drop an XML or ZUGFeRD PDF file here. Validation runs locally in your browser against EN 16931 — your file never leaves your machine.

100% local — no upload, no account.

Related rules

← Back to the error library