> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/peppol-bis-billing-3.0.md).

# Peppol BIS Billing 3.0

### Overview

This section describes the implementation plan for importing and mapping data from XML files using the Peppol BIS Billing 3.0 schema. Peppol BIS Billing 3.0 was developed to standardize e-billing processes and ensure compliance with European standards.

### Objectives

* Ensure full compliance with Peppol BIS Billing 3.0 specifications.
* Seamless integration of e-invoice data into our accounts payable system using DocBits.
* Improve data quality and processing efficiency.

### Scope

The scope of this project is to map key elements of the Peppol BIS Billing 3.0 schema to our internal data structures. In particular, the mapping will cover the following areas:

* Vendor and Buyer details
* Invoice details
* Invoice lines
* Payment instructions
* Tax and legal information

### Key elements and mapping

**Vendor information:**

* cac:AccountingSupplierParty
  * cbc:EndpointID: Electronic address of the vendor
  * cbc:Name: Trade name of the vendor
  * cbc:CompanyID: Legal registration number of the vendor
  * cbc:StreetName, cbc:CityName, cbc:PostalZone: Address details of the vendor

**Buyer information:**

* cac:AccountingCustomerParty
  * cbc:EndpointID: Electronic address of the buyer
  * cbc:Name: Trade name of the buyer
  * cbc:CompanyID: Legal registration number of the buyer
  * cbc:StreetName, cbc:CityName, cbc:PostalZone: Address details of the buyer

**Invoice details:**

* cbc:ID: Invoice number
* cbc:IssueDate: Issue date of the invoice
* cbc:DueDate: Invoice due date
* cbc:InvoiceTypeCode: Invoice type

**Invoice lines:**

* cac:InvoiceLine
  * cbc:ID: Invoice line number
  * cbc:InvoicedQuantity: Invoiced quantity
  * cbc:LineExtensionAmount: Line extension amount
  * cbc:Description: Description of the billing position
  * cac:Item
    * cbc:Name: Item name
    * cbc:SellerItemIdentification/cbc:ID: Item number of the vendor
  * cac:Price
    * cbc:PriceAmount: Price per unit
    * cbc:BaseQuantity: Base quantity for the price

**Payment instructions:**

* cac:PaymentMeans
  * cbc:PaymentMeansCode: Code to identify the payment method
  * cbc:PaymentID: Payment identifier

**Tax information:**

* cac:TaxTotal
  * cbc:TaxAmount: Total tax amount
  * cac:TaxSubtotal: Details for each interim tax amount

### PDF preview for e-invoice

A PDF document is generated according to a standard layout with the imported fields in order to provide the user with a preview for reference purposes. Further customization of the PDF preview layout is possible but requires additional effort.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/peppol-bis-billing-3.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.