How do I fix PEPPOL-EN16931-P0112?

Invoice type codes 326 (partial invoice) and 384 (corrective invoice) are only allowed between German organizations. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is PEPPOL-EN16931-P0112 a critical error?

Yes, PEPPOL-EN16931-P0112 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can PEPPOL-EN16931-P0112 be automatically fixed?

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

errorEN 16931

`PEPPOL-EN16931-P0112`:Invoice type code 326 or 384 are only allowed when both buyer and seller are...

Invoice type codes 326 (partial invoice) and 384 (corrective invoice) are only allowed between German organizations.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

80%

Engine Classification

Change invoice type code to 380 when 326/384 used for non-German parties

Confidence: 80% · Applied automatically in pipeline

What is PEPPOL-EN16931-P0112?

PEPPOL-EN16931-P0112 is a fatal validation rule defined in the EN 16931 specification. It validates the InvoiceTypeCode element 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: /Invoice/cbc:InvoiceTypeCode

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by PEPPOL validators. These rules ensure VAT exemption codes match their required tax categories and restrict certain invoice types to German-only transactions.

PEPPOL-EN16931-P0112 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: PEPPOL-EN16931-P0112
·Specification: EN 16931

Before / After

Failing XML

<Invoice>
  <!-- Issue: Invoice type code 326 or 384 are only allowed when both buye -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPath/Invoice/cbc:InvoiceTypeCode

SpecEN 16931

Operationset_value

StrategyChange invoice type code to 380 when 326/384 used for non-German parties

Common Causes

·German-only invoice type used for non-German parties
·BT-3 code 326/384 restricted to German organizations
·Partial or corrected invoice type for cross-border
·Both buyer and seller must be German for these codes
·Invoice type not permitted for international trade

Seeing this in production? The API handles PEPPOL-EN16931-P0112 automatically. See the fix response →

Handle PEPPOL-EN16931-P0112 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

PEPPOL-EN16931-P0112:Invoice type code 326 or 384 are only allowed when both buyer and seller are...