How do I fix NL-R-005?

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

Is NL-R-005 a critical error?

NL-R-005 is a warning that may not always cause rejection, but indicates a compliance issue.

Can NL-R-005 be automatically fixed?

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

warningNLDNLCIUS (Netherlands)

`NL-R-005`:For suppliers in the Netherlands, if the customer is in the Netherlands, the...

When both parties are Dutch, the buyer must use KVK (scheme 0106) or OIN (scheme 0190) as legal entity identifier.

Severity

Warning

Rule set

NLCIUS (Netherlands)

Country

NLD

Fix type

AUTO-FIX

Confidence

75%

Engine Classification

Ensure Dutch seller KvK number is present

Confidence: 75% · Applied automatically in pipeline

What is NL-R-005?

NL-R-005 is a warning validation rule defined in the NLCIUS (Netherlands) specification (NLD national rules). It validates the CompanyID element under Party > PartyLegalEntity in the UBL invoice XML.

This is a soft validation failure. The invoice may pass initial transmission, but non-compliant values in this field can cause problems during tax audits, buyer-side processing, or downstream VAT reconciliation.

Target path: //cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by Dutch validation. Dutch buyers must use KVK or OIN scheme.

NL-R-005 is a soft failure. The invoice may pass initial validation, but the non-compliant field can cause issues at the receiving end — tax authorities may flag it during audits, buyer ERP systems may fail to process it, or VAT reconciliation may produce mismatches. Fixing warnings before they accumulate prevents larger compliance gaps.

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

·Generates validation warning
·Error returned: NL-R-005
·Specification: NLCIUS (Netherlands)

Before / After

Failing XML

<Invoice>
  <!-- Issue: For suppliers in the Netherlands, if the customer is in the  -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per NLCIUS (Netherlands) -->
</Invoice>

Technical Reference

XPath//cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID

SpecNLCIUS (Netherlands)

Operationset_default

StrategyEnsure Dutch seller KvK number is present

Common Causes

·Wrong scheme for Dutch buyer
·Non-Dutch identifier scheme used
·Scheme ID missing from buyer legal entity
·Generic scheme instead of KVK/OIN
·Customer registered with wrong scheme

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

Related Errors

NL-01

Dutch sellers should include KVK number

NL-02

Dutch VAT numbers must be in correct format

NL-R-009

Dutch suppliers using order line references must also have an order...

Last updated: 27 February 2026

Share this guide:

Handle NL-R-005 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

NL-R-005:For suppliers in the Netherlands, if the customer is in the Netherlands, the...