How do I fix NL-R-008?

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

Is NL-R-008 a critical error?

Yes, NL-R-008 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can NL-R-008 be automatically fixed?

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

errorNLDNLCIUS (Netherlands)

`NL-R-008`:For Dutch domestic invoices, payment means code must be one of: 30, 48, 49,...

For Dutch domestic invoices, payment means code must be one of: 30, 48, 49, 57, 58, or 59. Other codes are not accepted.

Severity

Fatal

Rule set

NLCIUS (Netherlands)

Country

NLD

Fix type

AUTO-FIX

Confidence

80%

Engine Classification

Normalize Dutch VAT number format (NL + 9 digits + B + 2 digits)

Confidence: 80% · Applied automatically in pipeline

What is NL-R-008?

NL-R-008 is a fatal validation rule defined in the NLCIUS (Netherlands) specification (NLD national rules). It validates the CompanyID element under PartyTaxScheme[cac:TaxScheme > ID='VAT'] in the UBL invoice XML.

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.

Target path: //cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by Dutch validation. Domestic payments must use approved codes.

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

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

·Causes invoice rejection
·Error returned: NL-R-008
·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:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID

SpecNLCIUS (Netherlands)

Operationnormalize

StrategyNormalize Dutch VAT number format (NL + 9 digits + B + 2 digits)

Common Causes

·Invalid payment means code for NL domestic
·Payment code not in Dutch allowed list
·Wrong code for payment type
·ERP default code not valid for Netherlands
·Non-Dutch payment method used

Seeing this in production? The API handles NL-R-008 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-008 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-008:For Dutch domestic invoices, payment means code must be one of: 30, 48, 49,...