Skip to Content

E-invoice rejection: causes and corrections (1/4)

Identify the cause in one minute and fix it at the source, without resending blindly.
November 10, 2026 by
ANOR, Cyrille de LAMBERT

In brief An e-invoice rejection always has a precise technical cause: missing Peppol identifier, missing SIREN, credit note without an original invoice, a line with no tax or Chorus Pro workflow not activated. Identifying the right symptom in the error message allows you to fix it at the source in one minute, without resending blindly. The key habit: check the contact record before validation, not after the rejection.

Your invoice has come back with an error. The message is unclear, the situation is urgent and resending the same invoice without fixing it will get you nowhere. An e-invoice rejection always has a precise cause. The tree below guides you from symptom to correction, branch by branch.

Does the message mention a missing identifier?

This is the first thing to check. Two cases arise.

Case A: platform identifier missing. Odoo requires a routing scheme of 0225 and an identifier filled in on the contact record. In the contact view (Odoo 20), a button lets you search for the identifier directly in the Peppol directory: the tooltip reads "Search endpoint". If this field is empty, the invoice will not be sent. Open the record, run the search and save the identifier before making another attempt.

Case B: SIREN or SIRET missing. The message is explicit: "The following partner's SIREN or SIRET is missing". Add the number to the contact record, then revalidate the invoice.

Is the credit note linked to its original invoice?

Odoo blocks any credit note created as a free entry, with no reference to an existing invoice. The rule is straightforward: always create the credit note from the original invoice using the "Credit Note" button. This link is mandatory for the platform to accept the document. If the credit note has already been entered freely, cancel it and start again from the original invoice.

Does every line have a tax?

The check is formal: "Each invoice line should have at least one tax". A single line without a tax is enough to block the entire invoice. Check every line before validation, including lines for charges, discounts or rebates. Apply the appropriate tax or, if the line is legally exempt, enter the exemption reason required by the format.

Are the customer name and date filled in?

These two fields seem obvious and yet they are a common source of rejection. A missing customer name or absent date causes an immediate rejection. Check these values in the invoice header before any validation: it is a thirty-second habit that prevents an unnecessary round trip.

Is the customer a public authority?

Public procurement flows go through Chorus Pro and not the standard Peppol network. Odoo has a dedicated module for this workflow. If your customer is a local authority, a government ministry or a public institution, activate this module before issuing the first invoice. Without it, the invoice will not reach the right recipient.

Rejected or refused: know the difference

These two situations do not call for the same response.

  • Rejection: the platform did not accept the document. The invoice has no legal existence. Correct the technical error and reissue.
  • Refusal: the invoice reached the customer, who is disputing it. It has legal existence. The right response is a credit note, not a new issuance.

Confusing the two leads to duplicates or orphaned credit notes. Always read the status before acting.

Five points to check on the customer record before validation

The best time to correct a record is before validation, not after a rejection. Here is the checklist to go through for every new contact.

  • Peppol identifier (scheme 0225) filled in and verified via "Search endpoint".
  • SIREN or SIRET complete and accurate.
  • Company name identical to the one in the directory.
  • Billing email address present if required.
  • Chorus Pro workflow activated if the customer is a public authority.

A useful calendar reminder: according to Service-Public, receiving e-invoices will be mandatory for all businesses from 1 September 2026 and issuing them will be mandatory for SMEs from 1 September 2027. Getting ahead of the transition to an accredited platform and registering in the Peppol directory now will help you avoid a wave of rejections when the deadlines arrive.

To go further on compliance and managing your invoice flows, see our article E-invoicing with Odoo: from compliance to full control. And if you would like to secure your Odoo configuration, our team is available via the Support page.

The next instalment in this series will cover e-invoice statuses: how to read them, interpret them and respond at the right time. Stay tuned.

Not sure about your current configuration? Request a free audit: we review your Odoo setup and point out what needs correcting before the first rejection arrives.

Frequently asked questions

Where do you find the exact rejection reason in Odoo?

The reason appears in the invoice chatter as a system message as soon as the platform returns a negative response. Open the invoice in question and scroll down to the messages to read the full description.

Can you resend exactly the same invoice after a rejection?

No. Resending without correcting reproduces the same error. First identify the cause in the rejection message, apply the fix to the contact record or the invoice, then reissue.

What should you do if a customer does not yet have a Peppol identifier?

Use the "Search endpoint" button on the contact record to query the Peppol directory. If the customer is not listed yet, contact them to find out which partner dematerialisation platform they use and what identifier is associated with it before issuing the invoice.

in Blog
ANOR, Cyrille de LAMBERT November 10, 2026
Share this post
Tags
Our blogs

A question about your project? Talk to a consultant.

Book 30 minutes