---
title: "FAQ"
weight: 50
description: "Frequently asked questions about the Peppol module for Dolibarr: common errors, compliance and troubleshooting."
source_hash: "4201348b"
---

# FAQ

## The XML file is not generated when the invoice is validated

Check that your company information is complete in **Home > Setup > Company**: VAT number, address, zip code, city and country. Also check that the customer has a name, a complete address and a VAT number or a Peppol identifier.

See the error messages displayed on the invoice to identify precisely the missing field.

## The message "your module version is not consistent" is displayed

This message means that the installed module version does not match the version stored in the database. Deactivate the module in **Home > Setup > Modules/Applications**, then reactivate it. This operation applies the database structure updates.

## My customer has no VAT number

Two options are possible:

- **Assign a specific Peppol identifier** on the third party's card via the **PeppolFinder** button
- **Enable the option "Force creation of an XML file without a VAT number"** in the [configuration](/peppol/configuration). The generated file then uses the code `ZZ00000000` and is not compliant with the Peppol standard, but it can be used for internal dematerialization.

## The "Send" button is greyed out on my invoice

Several possible causes:

- The invoice has already been sent and the **Allow resending a document** option is disabled in the [access point configuration](/peppol/configuration)
- The Peppol XML file does not exist for this invoice (check the linked documents)
- No access point is configured

## Sending fails with a connection error

1. Go to the **Check** tab of the module configuration
2. Click **Test connection with your Peppol server**
3. Check that the API key, password and customer ID are correct
4. If you are in test mode, check that your Peppol provider has activated your test account

## Rounding errors prevent the XML file from being generated

The Peppol standard requires line amounts to have a maximum of 2 decimals and the sum of the lines to match the invoice total with a tolerance of 0.02 EUR.

If you have unit prices with many decimals (for example prorated calculations), round them before validating the invoice. The module pinpoints exactly which lines are problematic.

## How to configure automatic sending?

1. Enable the **Automatically send invoices to PEPPOL** option in the [Auto send](/peppol/configuration) tab
2. Enable the Peppol scheduled task in **Home > Setup > Scheduled tasks**
3. Configure the task's execution frequency (default: every 24 hours)

Only validated invoices with an XML file and a customer with a Peppol identifier are sent automatically. Individuals are always ignored.

## How to find a customer's Peppol identifier?

Use the **PeppolFinder** tool from the third party's card, or consult the public Peppol directory directly at [directory.peppol.eu](https://directory.peppol.eu/).

You can also use the **Third parties** tab in the module configuration to mass-assign Peppol identifiers from VAT numbers.

## My third party's Peppol identifier is rejected

The Peppol identifier must follow the format `XXXX:YYYYYYYYYYYYYY` where `XXXX` is an ICD (International Code Designator) compliant with the ISO 6523 list. The most common codes are:

- `0002` -- SIRENE (France)
- `0009` -- SIRET (France)
- `0088` -- EAN/GTIN
- `0208` -- Belgian VAT number
- `9925` -- Intra-Community VAT number (European format)

If the ICD code used is not recognized, check with your access point which identifier to use.

## How to manage VAT exemptions?

When an invoice includes zero-rated lines, select the appropriate exemption code in the invoice's **VAT exemption code** field. The available codes are managed in the [VAT exemption](/peppol/configuration) tab of the configuration.

The most used codes are:

- **VATEX-EU-IC** -- Intra-Community supply
- **VATEX-EU-AE** -- Reverse charge
- **VATEX-EU-G** -- Export outside the EU
- **VATEX-EU-O** -- Not subject to VAT
- **VATEX-FR-FRANCHISE** -- VAT franchise in base (France)

## The supplier invoice has no linked bank account

The Peppol file includes the seller's bank details if a bank account is linked to the invoice. If the bank account has no IBAN filled in, a warning is displayed. Edit the bank account to add the IBAN, then regenerate the invoice.

## Production mode and test mode

By default, the module runs in test mode (sandbox). Documents sent in test mode are not transmitted to real recipients. Once your tests are validated, enable **production mode** in the [Access point configuration](/peppol/configuration) tab.

> **Warning**: in production mode, each sending may incur fees depending on your contract with your Peppol provider.

## How to receive supplier invoices?

1. Configure your access point for receiving (API key and identifier)
2. Access the **Peppol AP Import** page via the menu **Billing > Supplier invoices**
3. The invoices available on the access point are displayed in the list
4. Click a document to view it and create the corresponding supplier invoice

If the webhook is enabled, your Dolibarr is automatically notified when new documents arrive.

## My company has two VAT numbers (BE + LU), how to configure?

If your company has a main VAT number and a secondary VAT number (for example a branch in another country), follow this procedure:

1. Enter **only the main number** in **Setup > Company > VAT number**. This is the number linked to your Peppol identifier registered in the SMP (network).
2. Enter the **secondary number** in the Peppol module configuration, **Secondary VAT number** field (e.g. `LU98765432`).
3. On customer invoices, a **Peppol VAT number** drop-down list will then appear automatically. Choose the number to use in the Peppol XML for each invoice (default: Main).

> **Important**: **never** enter two numbers separated by a dash in the main VAT field (e.g. `BE0123456789 - LU98765432`). This generates an invalid VAT number in the Peppol XML and the invoice is rejected by the network. The module detects this erroneous case and uses only the first number, but the good practice is to correctly configure the secondary number in the module.

> **Note**: Peppol routing always remains linked to your main identifier. This option only changes the VAT number written in the body of the XML, to respect the tax consistency of the issued invoice.
