infobusinessPeppol BIS 3.0

IN-UNIT-CODES:Unit of measure codes validation

Fix: Update the `@unitCode` element to use a value from the allowed code list. Check the `cac:InvoiceLine/cbc:InvoicedQuantity/@unitCode` element.

Unit codes should be from UN/ECE Recommendation 20

Severity
Info
Rule set
Peppol BIS 3.0
Country
All EU
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: Unit of measure codes must match your product catalog and trading partner agreements. Invalid codes may indicate data mapping issues.

What is IN-UNIT-CODES?

IN-UNIT-CODES is a info validation rule defined in the Peppol BIS 3.0 specification. It validates the Name element under Party > PartyName in the UBL invoice XML.

This flags a compliance issue that should be reviewed to improve interoperability and audit readiness.

Target path: XPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Seller identification required.

Ignoring IN-UNIT-CODES degrades your invoice quality score. Receivers increasingly flag these for manual review.

Validator Behavior

  • ·Rejected by PEPPOL Access Points
  • ·Error returned: IN-UNIT-CODES
  • ·Specification: Peppol BIS 3.0

How to Fix It

1.

Add PartyName

Under seller Party

2.

Include Name

Legal company name

Before / After

Failing XML
<cbc:InvoicedQuantity>
  <@unitCode>INVALID_CODE</@unitCode>
</cbc:InvoicedQuantity>
Corrected XML
<cbc:InvoicedQuantity>
  <@unitCode>VALID_CODE</@unitCode>
</cbc:InvoicedQuantity>

Technical Reference

XPathXPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name
SpecPeppol BIS 3.0

Common Causes

  • ·Missing PartyName
  • ·Empty name

Seeing this in production? The API handles IN-UNIT-CODES automatically. See the fix response →

Frequently Asked Questions

Seller party must have name specified.

Update the `@unitCode` element to use a value from the allowed code list. Check the `cac:InvoiceLine/cbc:InvoicedQuantity/@unitCode` element. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

Yes, PEPPOL-EN16931-R009 is a critical error that must be fixed.

Related Errors

PEPPOL-EN16931-R010Buyer electronic address required

Related Content

Glossary
Evidence Packe-Reporting
Errors
Missing direct debit mandate referenceEndpoint identifier scheme identifier SHALL be chosen from the Electronic...
Answers
What is the difference between B2G and B2B e-invoicing?
Regulations
EN 16931

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for IN-UNIT-CODES

Detect IN-UNIT-CODES before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.

Fix it nowAutomate via API