> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/finanzen-1/ausgangsrechnungen/delivery-of-x-invoice-via-peppol.md).

# Delivery of X-invoice via PEPPOL

(Pan-European Public Procurement Online)

Die Agenturverwaltung can send invoices via our partner efacto over the Peppol network.

{% hint style="info" %}
Talk to our customer service about this and we will register your company with efacto and extend your invoices with the fields "Leitweg-ID" and "purchase invoice number"
{% endhint %}

The use of the efacto service is chargeable (prices are comparable to postage stamps).

{% embed url="<https://efacto.de/pdftox>" %}

### This is how sending X-invoices from Die Agenturverwaltung works

After the field "Leitweg-ID" of an invoice has been filled in (and saved), an e-mail can be generated in the invoice. In this case the system does not suggest the linked contact from the address book as the recipient, but an address to your mailbox at efacto. The invoice is then sent there, processed, converted into an X-invoice format and sent to the recipient via Peppol or e-mail (this is then apparent from the Leitweg-ID). efacto charges for this service - in the smallest package at 12 EUR per month.&#x20;

### The following data should not be missing on an X-invoice

* Leitweg-ID -&#x20;
* purchase invoice number
* Delivery address - if different from billing address
* Due date
* Contact person at your side with phone and e-mail
* Service period from / to (if only one day, then DD.MM.YYYY or delivery date)
* your supplier number/creditor number at the invoice recipient
* VAT ID of the customer

{% hint style="info" %}
**More about Peppol and X-invoice**

<https://www.e-rechnung-bund.de/eingangskanal-peppol/>
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/finanzen-1/ausgangsrechnungen/delivery-of-x-invoice-via-peppol.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.