errorNLDNLCIUS (Netherlands)

NL-R-002:Dutch suppliers must provide complete address with street name, city, and...

Dutch suppliers must provide complete address with street name, city, and postal code. All three address components are mandatory.

Severity
Fatal
Rule set
NLCIUS (Netherlands)
Country
NLD
Fix type
INPUT REQUIRED

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Seller Street Name, Seller City, Seller Postal Code

What is NL-R-002?

NL-R-002 is a fatal validation rule defined in the NLCIUS (Netherlands) specification (NLD national rules). It checks whether dutch suppliers must provide complete address with street name, city, and....

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.

Why This Error Matters

Invoice will be rejected by Dutch validation. Complete seller address is required.

NL-R-002 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.

Validator Behavior

  • ·Causes invoice rejection
  • ·Error returned: NL-R-002
  • ·Specification: NLCIUS (Netherlands)

Before / After

Failing XML
<cac:PartyTaxScheme>
  <cbc:CompanyID>INVALID_CODE</cbc:CompanyID>
</cac:PartyTaxScheme>
Corrected XML
<cac:PartyTaxScheme>
  <cbc:CompanyID>VALID_CODE</cbc:CompanyID>
</cac:PartyTaxScheme>

Technical Reference

SpecNLCIUS (Netherlands)
StrategyRequires user input: Complete seller address - street name (StreetName), city (CityName), and postal code (PostalZone).

Common Causes

  • ·Street name missing from address
  • ·City not provided
  • ·Postal code missing
  • ·Incomplete company address
  • ·Address fields not fully mapped

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

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle NL-R-002 Automatically in Your Pipeline

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