Peppol BIS Billing 3.0 - Features and requirements
French translation of chapters 5 and 6 of the official documentation Source: https://docs.peppol.eu/poacc/billing/3.0/bis/
5. Invoice features
An invoice can support functions related to a number of related (internal) business processes. This Peppol BIS must support the following functions:
- Accounting
- Invoice verification against the contract, the purchase order and the goods and services delivered
- VAT return
- Audit
- Payment
In the following chapters, an assessment is made of the information needed for each of the functions listed above and whether they are in or out of scope of this Peppol BIS.
See also the chapter Business requirements for the invoice and the credit note for more details.
The explicit support of the following functions (but not limited to these) is out of scope:
- Inventory management
- Delivery processes
- Customs clearance
- Marketing
- Reporting
5.1. Accounting
Recording a business transaction in an organization's financial accounts is one of the main objectives of the invoice. According to financial accounting best practices and VAT rules, any taxable person must keep sufficiently detailed accounts for VAT to be applied and its application to be verified by the tax authorities. For this reason, an invoice must provide the information at document and line level that allows recording both on the debit and credit side.
The detailed requirements for supporting the accounting functionality are found in Accounting requirements.
5.2. Invoice verification
This process is part of the buyer's internal controls. The invoice must refer to an authentic business transaction. Invoice verification support is a key function of an invoice. The invoice must provide enough information to look up the relevant existing documentation, electronic or paper, for example, as applicable:
- the relevant purchase order
- the contract
- the tender that served as the basis for the contract
- the buyer's reference
- the confirmation of receipt of goods or services
- the delivery information
An invoice must also contain sufficient information to transfer the received invoice to an authority, person or department responsible for verification and approval.
The detailed requirements for supporting the verification functionality are found in Invoice verification requirements.
5.3. Audit
Companies self-audit as a means of internal control or may be audited by external parties as part of a legal obligation. Accounting is a regular and continuous process while an audit is a distinct review process aimed at ensuring that the accounting has been done correctly. The audit process imposes certain information requirements on an invoice. These requirements are mainly related to the ability to verify the authenticity and integrity of the accounting transaction.
Invoices compliant with this Peppol BIS support the audit process by providing sufficient information for:
- the identification of the buyer and seller concerned
- the identification of the products and services exchanged, including their description, value and quantity
- the information to link the invoice to its payment
- the information to link the invoice to the relevant documents such as a contract and a purchase order
The detailed requirements for supporting the audit functionality are found in Audit requirements.
5.4. VAT return
The invoice is used to carry VAT information from the seller to the buyer to enable the buyer and the seller to correctly record and declare VAT. An invoice must contain sufficient information to allow the buyer and any auditor to determine whether the invoice is correct from a VAT point of view.
The invoice must allow the determination of the VAT regime, the calculation and the description of the tax, in accordance with Directive 2006/112/EC and its subsequent amendments.
The detailed requirements for supporting the VAT return functionality are found in VAT return requirements.
5.5. Payment
An invoice represents a payment claim. The issuance of an invoice may take place before or after the payment is made. When an invoice is issued before payment, it represents a request to the buyer to pay, in which case the invoice generally contains information allowing the buyer, in its role as debtor, to correctly initiate the payment transfer, unless this information has already been agreed in prior contracts or by means of payment instructions deposited separately with the buyer.
If an invoice is issued after payment, as when the ordering process included payment instructions or in the case of payment by credit card, online or telephone purchases, the invoice may contain information about the payment made in order to facilitate invoice/payment matching on the buyer side. An invoice may be partially paid before issuance, as when a deposit is paid to confirm an order.
Invoices compliant with this specification must identify the means of payment for settling the invoice and clearly indicate the payment amount requested. They must provide the necessary details to support bank transfers in accordance with the Single Euro Payments Area (SEPA) for payments in euros and the relevant national payment practices for other currencies. Payments by credit transfer, direct debit and payment card are in scope.
The detailed requirements for supporting the payment functionality are found in Payment requirements.
5.6. Negative invoices and credit notes
In accordance with the requirements of EN 16931, this BIS supports negative overall totals in order to open up a broader spectrum of invoicing processes.
Examples of such processes are:
- Preliminary (estimated) consumption invoice that is balanced in a subsequent meter-based invoice;
- Deposit (with or without VAT) settled by a final invoice;
- Some user communities prefer to use a negative invoice rather than a credit note when correcting transactions.
This has the following implications on the transaction format:
- The invoice (now with "negative invoice capability") can function as an alternative to the credit note. Invoice-issuing systems can implement either option, while invoice-receiving systems must support both.
- The transaction format for the credit note must be designed to also accommodate a negative overall total; this is because an entire negative invoice may have to be offset by a credit note.
Attention is drawn to the intrinsic differences between the credit note and the negative invoice when it comes to transmitting credit information.
UBL example of invoice to be corrected:
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
<!-- Code omis pour clarté -->
<cac:AllowanceCharge>
<cbc:ChargeIndicator>true</cbc:ChargeIndicator>
<cbc:AllowanceChargeReason>Assurance</cbc:AllowanceChargeReason>
<cbc:Amount currencyID="EUR">25</cbc:Amount> <!-- (1) -->
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25.0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:AllowanceCharge>
<!-- Code omis pour clarté -->
<cac:LegalMonetaryTotal>
<cbc:LineExtensionAmount currencyID="EUR">1300</cbc:LineExtensionAmount>
<cbc:TaxExclusiveAmount currencyID="EUR">1325</cbc:TaxExclusiveAmount>
<cbc:TaxInclusiveAmount currencyID="EUR">1656.25</cbc:TaxInclusiveAmount>
<cbc:ChargeTotalAmount currencyID="EUR">25</cbc:ChargeTotalAmount>
<cbc:PayableAmount currencyID="EUR">1656.25</cbc:PayableAmount>
</cac:LegalMonetaryTotal>
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID> <!-- (2) -->
<cbc:InvoicedQuantity unitCode="DAY">7</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">2800</cbc:LineExtensionAmount>
<!-- Code omis pour clarté -->
<cac:Price>
<cbc:PriceAmount currencyID="EUR">400</cbc:PriceAmount>
</cac:Price>
</cac:InvoiceLine>
<cac:InvoiceLine>
<cbc:ID>2</cbc:ID> <!-- (3) -->
<cbc:InvoicedQuantity unitCode="DAY">-3</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">-1500</cbc:LineExtensionAmount>
<!-- Code omis pour clarté -->
<cac:Price>
<cbc:PriceAmount currencyID="EUR">500</cbc:PriceAmount>
</cac:Price>
</cac:InvoiceLine>
| Ref | Description |
|---|---|
| (1) | Charge amount |
| (2) | Invoice line 1 with positive quantity and line amount |
| (3) | Invoice line 2 with negative quantity and line amount |
5.6.1. When crediting by credit note
The credit or debit function is controlled only by the commercial document type (for example 380 or 381) while the representation of the amount, including its sign, is not affected.
UBL example of credit note correcting the invoice example above:
<cbc:CreditNoteTypeCode>381</cbc:CreditNoteTypeCode> <!-- (1) -->
<!-- Code omis pour clarté -->
<cac:AllowanceCharge>
<cbc:ChargeIndicator>true</cbc:ChargeIndicator>
<cbc:AllowanceChargeReason>Assurance</cbc:AllowanceChargeReason>
<cbc:Amount currencyID="EUR">25</cbc:Amount> <!-- (2) -->
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25.0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:AllowanceCharge>
<cac:LegalMonetaryTotal>
<cbc:LineExtensionAmount currencyID="EUR">1300</cbc:LineExtensionAmount>
<cbc:TaxExclusiveAmount currencyID="EUR">1325</cbc:TaxExclusiveAmount>
<cbc:TaxInclusiveAmount currencyID="EUR">1656.25</cbc:TaxInclusiveAmount>
<cbc:ChargeTotalAmount currencyID="EUR">25</cbc:ChargeTotalAmount>
<cbc:PayableAmount currencyID="EUR">1656.25</cbc:PayableAmount>
</cac:LegalMonetaryTotal>
<cac:CreditNoteLine>
<cbc:ID>1</cbc:ID> <!-- (3) -->
<cbc:CreditedQuantity unitCode="DAY">7</cbc:CreditedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">2800</cbc:LineExtensionAmount>
<!-- Code omis pour clarté -->
<cac:Price>
<cbc:PriceAmount currencyID="EUR">400</cbc:PriceAmount>
</cac:Price>
</cac:CreditNoteLine>
<cac:CreditNoteLine>
<cbc:ID>2</cbc:ID> <!-- (4) -->
<cbc:CreditedQuantity unitCode="DAY">-3</cbc:CreditedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">-1500</cbc:LineExtensionAmount>
<!-- Code omis pour clarté -->
<cac:Price>
<cbc:PriceAmount currencyID="EUR">500</cbc:PriceAmount>
</cac:Price>
</cac:CreditNoteLine>
| Ref | Description |
|---|---|
| (1) | Code 381 indicating a credit note |
| (2) | Charge amount |
| (3) | Invoice line 1 with positive quantity and line amount |
| (4) | Invoice line 2 with negative quantity and line amount |
5.6.2. When crediting by negative invoice
The credit or debit function is controlled only by the sign (i.e. plus or minus sign) of the amount concerned, while the commercial document type (for example 380) has no relevance on the ("credit") operation itself.
UBL example of negative invoice correcting the invoice example above:
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode> <!-- (1) -->
<!-- Code omis pour clarté -->
<cac:AllowanceCharge>
<cbc:ChargeIndicator>true</cbc:ChargeIndicator>
<cbc:AllowanceChargeReason>Assurance</cbc:AllowanceChargeReason>
<cbc:Amount currencyID="EUR">-25</cbc:Amount> <!-- (2) -->
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>25.0</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:AllowanceCharge>
<!-- Code omis pour clarté -->
<cac:LegalMonetaryTotal> <!-- (3) -->
<cbc:LineExtensionAmount currencyID="EUR">-1300</cbc:LineExtensionAmount>
<cbc:TaxExclusiveAmount currencyID="EUR">-1325</cbc:TaxExclusiveAmount>
<cbc:TaxInclusiveAmount currencyID="EUR">-1656.25</cbc:TaxInclusiveAmount>
<cbc:ChargeTotalAmount currencyID="EUR">-25</cbc:ChargeTotalAmount>
<cbc:PayableAmount currencyID="EUR">-1656.25</cbc:PayableAmount>
</cac:LegalMonetaryTotal>
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID> <!-- (4) -->
<cbc:InvoicedQuantity unitCode="DAY">-7</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">-2800</cbc:LineExtensionAmount>
<!-- Code omis pour clarté -->
<cac:Price>
<cbc:PriceAmount currencyID="EUR">400</cbc:PriceAmount> <!-- (5) -->
</cac:Price>
</cac:InvoiceLine>
<cac:InvoiceLine>
<cbc:ID>2</cbc:ID> <!-- (6) -->
<cbc:InvoicedQuantity unitCode="DAY">3</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">1500</cbc:LineExtensionAmount>
<!-- Code omis pour clarté -->
<cac:Price>
<cbc:PriceAmount currencyID="EUR">500</cbc:PriceAmount>
</cac:Price>
</cac:InvoiceLine>
| Ref | Description |
|---|---|
| (1) | Code 380 indicating an invoice |
| (2) | The charge amount is negative to correct the original invoice |
| (3) | All document-level amounts are negative |
| (4) | Invoice line 1 with originally positive quantity and line amount, now both negative |
| (5) | The price amount must always be positive and is not modified |
| (6) | Invoice line 2 with originally negative quantity and line amount, now positive |
6. Business requirements for the invoice and the credit note
The table below gives an overview of the Peppol/CEN/TC 434 business requirements supported by this BIS:
Legend: Requirements with an identifier Rnn come from EN 16931 (Example R19).
Table 1. Accounting requirements
| Id | Requirement (according to the applicable business case) |
|---|---|
| R1 | document-level information allowing the identification of the payee, if different from the seller |
| R2 | document-level information allowing debit and credit recording |
| R3 | invoice line-level information allowing debit recording |
| R4 | accounting information specific to the buyer (account numbers) |
Table 2. Invoice verification requirements
| Id | Requirement (according to the applicable business case) |
|---|---|
| R5 | information to trace back to a single linked purchase order from document level |
| R6 | information to trace back to a single linked purchase order line from the invoice line |
| R7 | information to trace back to a single contract and the underlying tender from document level |
| R8 | a reference provided by the buyer at document level |
| R9 | information to trace back to a single despatch advice from document level |
| R10 | information to trace back to a single receipt advice from document level |
| R11 | information to trace back to a related invoice to be corrected from document level |
| R13 | information allowing the transfer of an invoice and the related documents to an authority, entity, person or department responsible, for verification and approval |
| R14 | information on the net price and the quantity on which the price is based at invoice line level, additional information such as the gross price and the price allowance can be added |
| R15 | descriptive and coded information on allowances and charges at document level and at invoice line level |
| R16 | information on charges, taxes (excluding VAT), duties and levies, with their VAT information, which are not included in the line amounts at document level |
| R17 | information on charges, taxes (excluding VAT), duties and levies that make up the taxable amount and are not included in the unit price on separate invoice lines, with appropriate identification and/or description |
| R18 | information on charges at invoice line level that are part of the line amount |
| R19 | the amounts of allowances and charges at document and invoice line level |
| R20 | textual descriptions of the invoiced goods and services at invoice line level |
| R21 | identification of the invoiced goods and services by means of a seller's item number at invoice line level |
| R22 | identification of the invoiced goods and services by means of a buyer's item number at invoice line level |
| R23 | identification of the invoiced goods and services by means of a general qualified item identifier at invoice line level as agreed between the buyer and the seller |
| R24 | classification of the invoiced goods and services by means of applicable classification identifiers and scheme reference as agreed between the buyer and the seller at invoice line level |
| R25 | information on returned consigned assets and packaging, such as pallets, and packaging charges, indicated as normal invoice lines |
| R26 | information on consigned asset charges, indicated as normal invoice lines |
| R27 | information on returned goods, indicated as normal invoice lines |
| R28 | descriptive information on the attributes of the goods and services at invoice line level |
| R29 | information on the country of origin of the goods and services at invoice line level |
| R30 | an invoice line period at invoice line level |
| R31 | a delivery date at document level |
| R32 | a delivery place or address at document level |
| R33 | identification of the invoiced object at document and line level |
| R34 | a delivery/invoicing period at document level |
| R35 | attached documents of a limited set of file types |
| R36 | several attached or referenced documents at document level |
| R37 | a VAT category and a VAT rate at invoice line level |
| R38 | VAT totals by category at document level |
| R39 | a quantity and a net (excluding VAT) amount at invoice line level |
| R40 | all document and invoice line amounts that make up the invoice total amount and the amount due |
| R41 | reference to a sales order, issued by the seller at document level |
| R42 | percentage and base amount of allowance/charge at document and invoice line level |
| R44 | information allowing automated validation of a received electronic invoice |
Table 3. VAT return requirements
| Id | Requirement (according to the applicable business case) |
|---|---|
| R45 | information to determine the requirements of the applicable VAT legislation in force and its calculation and declaration |
| R46 | information on the VAT due date at document level |
| R47 | the elements necessary for the national VAT legal requirements that apply to invoices issued to domestic and foreign buyers, such as the seller's legal registration status |
| R48 | information to support the following VAT use cases: invoices for supplies for which VAT is charged; invoices for supplies for which VAT is not charged on the basis of an exemption reason; invoices for supplies for which the seller's goods and services are VAT-exempt at line level; invoices for supplies issued under reverse charge; invoices for exempt intra-Community supplies for which an intra-Community acquisition must be made; invoices for supplies outside the scope of Directive 2006/112/EC (non-VAT invoices) |
| R49 | the total VAT amount at document level |
| R50 | the total taxable amount per VAT rate at document level |
| R51 | any additional information required to substantiate the proof of exemption in the case where VAT is not charged on the basis of an exemption reason at document and invoice line level |
| R52 | the legal registration number and the VAT identification number of the seller and of the buyer and the VAT identification number of the supplier's tax representative |
| R53 | the official postal address of the buyer, the seller and the supplier's tax representative as well as their place of business and registered office |
| R54 | the billing currency and the VAT accounting currency at document level if different from the billing currency |
| R55 | exemption reason codes at document and invoice line level |
Table 4. Audit requirements
| Id | Requirement (according to the applicable business case) |
|---|---|
| R56 | sufficient information to support the audit process concerning: the identification of the invoice; the identification of the invoice issue date; the identification of the products and services exchanged, including their description, value and quantity; the information to link the invoice to its settlement; the information to link the invoice to the relevant documents such as a contract, a purchase order and a despatch advice |
| R57 | identification of the parties fulfilling the following roles at invoice level, including their company name and address: the seller (including the seller's trading name); the buyer; the delivery recipient (if different from the buyer); the payee (if different from the seller); the supplier's tax representative |
Table 5. Payment requirements
| Id | Requirement (according to the applicable business case) |
|---|---|
| R58 | identification of the means of settlement |
| R59 | the amount due requested |
| R60 | the payment due date |
| R61 | the necessary details to support bank transfers in accordance with SEPA and national systems |
| R62 | a reference number and any additional reference data to include in the payment |
| R63 | reference number and any additional reference data to include in the payment, in order to link the payment to the invoice |
| R64 | information to link an invoice to a payment card used for settlement |
| R65 | basic information to support national payment systems for use in domestic trade |
| R66 | information on the prepaid amount |
| R67 | invoices whose total amount is zero |
| R68 | invoices whose amount due is zero |
| R69 | the necessary details to support direct debits |
| R70 | deposit invoices |