warningNLDNLCIUS (Netherlands)

NL-R-003:For suppliers in the Netherlands, the legal entity identifier MUST be either...

Dutch suppliers must use either KVK number (scheme 0106) or OIN number (scheme 0190) as their legal entity identifier.

Severity
Warning
Rule set
NLCIUS (Netherlands)
Country
NLD
Fix type
AUTO-FIX
Confidence
75%
Category
identifier

Engine Classification

Ensure buyer reference is present for Dutch invoices

Confidence: 75% · Applied automatically in pipeline

What is NL-R-003?

NL-R-003 is a warning validation rule defined in the NLCIUS (Netherlands) specification (NLD national rules). It validates the BuyerReference element 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: /Invoice/cbc:BuyerReference

Why This Error Matters

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

NL-R-003 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-003
  • ·Specification: NLCIUS (Netherlands)

Before / After

Failing XML
<Invoice>
  <!-- Issue: For suppliers in the Netherlands, the legal entity identifie -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per NLCIUS (Netherlands) -->
</Invoice>

Technical Reference

XPath/Invoice/cbc:BuyerReference
SpecNLCIUS (Netherlands)
Operationset_default
StrategyEnsure buyer reference is present for Dutch invoices

Common Causes

  • ·Wrong scheme ID for Dutch legal entity
  • ·Using non-Dutch identifier scheme
  • ·Scheme ID missing from legal entity
  • ·Generic scheme used instead of 0106/0190
  • ·ERP does not set Dutch-specific schemes

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

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle NL-R-003 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.