> ## Documentation Index
> Fetch the complete documentation index at: https://docs.procuros.io/llms.txt
> Use this file to discover all available pages before exploring further.

# E-invoices Procuros delivers

> Learn which e-invoice formats Procuros delivers to buyers and what Procuros checks before it sends an invoice.

The buyer decides the format. Suppliers keep sending invoices the way they do today, and Procuros delivers them in the format the buyer asks for.

It does not matter how an invoice reaches Procuros: created in the Procuros Portal, sent as a PDF or an EDI file, sent from an ERP system or through the API, or sent as an e-invoice.

## Formats Procuros delivers

| Format | What the buyer receives |
| - | - |
| XRechnung 3.0 | An XML file |
| ZUGFeRD / Factur-X, profile EN 16931 or EXTENDED | A PDF with the invoice data inside |
| ZUGFeRD with the XRechnung profile | A PDF with XRechnung data inside |
| Peppol BIS Billing 3.0 | An e-invoice over the Peppol network, sent through a certified Peppol Access Point |
| EDI | An EDI file, as today |

* Each format covers invoices and credit notes.
* Each invoice is delivered as its own file.
* Procuros does not produce the ZUGFeRD profiles MINIMUM, BASIC WL and BASIC.

## Getting started

If your customer requires e-invoices, or you want to receive e-invoices yourself, contact us at [help@procuros.io](mailto:help@procuros.io). Send us:

* The customer and their e-invoice requirements
* The required format and version, if known
* How the invoice should be delivered, for example an email address or a Peppol participant ID
* Any buyer references the customer requires
* The planned start date

We then check what needs to change in your connection. Before the switch, we agree with you whether the buyer needs a test invoice and when to go live. Keep sending invoices the way you do today until we confirm the switch.

> [!NOTE]
>
> A buyer receives e-invoices in the same format from all their suppliers who invoice them through Procuros. When a buyer starts receiving e-invoices, Procuros delivers the invoices of all those suppliers in that format from the same date.

## Data validation before Procuros sends

Depending on the format, Procuros also validates the invoice data before it creates the e-invoice.

If something is missing or wrong, Procuros holds the invoice and does not deliver it. The [issue resolver](https://docs.procuros.io/en/general/troubleshooting/blocked-transactions.md#the-issue-resolver) receives an email that explains what to fix. The issue resolver either corrects the data directly in Procuros, or corrects it in their own system and then retriggers the document. The steps are in [Problem Resolution](https://docs.procuros.io/en/general/troubleshooting/blocked-transactions.md#problem-resolution). Once the corrected invoice passes the validation, Procuros delivers it to the buyer. This applies to every invoice, however it reached Procuros.

## What the buyer receives

For XRechnung and Peppol, the buyer receives one XML file per invoice.

For ZUGFeRD, the buyer receives one PDF per invoice. Procuros creates the PDF from the invoice data, so the readable PDF and the data inside always match. The supplier's own PDF is not used.

## Frequently asked questions

> **Does the supplier's system need to create an XRechnung or ZUGFeRD invoice?**
>
> No. The data the supplier sends to Procuros and the format the buyer receives are two separate things. Procuros creates the format the buyer needs from the invoice data it receives. The supplier's system must still include all the information the format requires.
>
> Before the supplier changes the export from their system, ask us to check the setup.

> **Can Procuros send invoices through Peppol?**
>
> Yes. Procuros delivers Peppol BIS Billing 3.0 invoices over the Peppol network, through a certified Peppol Access Point. It is set up for each customer: an existing email or EDI connection does not switch to Peppol on its own.
>
> Send the buyer's Peppol participant ID and requirements to [help@procuros.io](mailto:help@procuros.io).

> **Why was an e-invoice blocked, and who needs to fix it?**
>
> Usually because required information is missing, or the data does not meet the rules of the format. The issue resolver receives an email that explains what to fix, as described above.
>
> If you need help, send us the invoice number, the buyer's name and the full error message at [help@procuros.io](mailto:help@procuros.io).

> **Does "delivered" mean the buyer has accepted the invoice?**
>
> No. Delivered means Procuros has handed the invoice over to the buyer's connection. Whether the buyer has checked, posted or paid it happens in the buyer's own system.
>
> If a buyer says an invoice is missing, contact us at [help@procuros.io](mailto:help@procuros.io) with the invoice number, the buyer's name and the date it was sent. Do not send a second copy through another channel first, because that can create a duplicate invoice.

> **Does the supplier need to send a separate PDF or a second invoice?**
>
> No. The supplier sends each invoice once, the way they agreed with the buyer, and does not send it again through another channel unless the buyer asks for it.
>
> A ZUGFeRD invoice already combines a readable PDF and the invoice data in one file. An XRechnung is an XML file, and it is an e-invoice without a separate PDF.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.