E-invoice / Rules / PEPPOL-EN16931-P0100

E-invoice rule Peppol BIS Billing 3.0

PEPPOL-EN16931-P0100: For an ordinary invoice use 380

For an ordinary invoice use 380.

Original wording of the rule

Invoice type code MUST be set according to the profile.

Source of the quotation: Peppol BIS Billing 3.0 (OpenPEPPOL, peppol-bis-invoice-3)

How to fix it

1. Open the XML file and find the element cbc:InvoiceTypeCode.
2. Add or correct the element the way the wording of the rule above asks for.
3. Save the file and check it again with our checker. It runs in your browser, the file is never uploaded.

A correct UBL 2.1 snippet

<cbc:InvoiceTypeCode
    xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">380</cbc:InvoiceTypeCode>

The snippet is only the part of the document the rule is about. Put it in the right place inside your invoice; the namespaces are written here only so that the snippet reads on its own.

When it is reported

Profile: Peppol BIS Billing 3.0

How we rate it: error

Where we point in the file: /Invoice/cbc:InvoiceTypeCode

Related rules

• PEPPOL-EN16931-P0101 For an ordinary credit note use 381
• PEPPOL-EN16931-P0104 The exemption reason code VATEX-EU-G belongs to VAT category G, but
• PEPPOL-EN16931-P0105 The exemption reason code VATEX-EU-O belongs to VAT category O, but
• PEPPOL-EN16931-P0106 The exemption reason code VATEX-EU-IC belongs to VAT category K, but
• PEPPOL-EN16931-P0107 The exemption reason code VATEX-EU-AE belongs to VAT category AE, but

Our check is not complete: we do not check the XSD schema and we do not implement every rule, and a file that passes says nothing about whether the buyer or the Peppol network will accept it. Licences for the quoted wordings are listed in our sources.