Credit Notes and E-Invoicing: Managing Corrections in 2026

Introduction: why credit notes become a critical issue in 2026

With mandatory e-invoicing coming into force for large enterprises and mid-market companies from 1 September 2026, finance and accounting departments face a challenge that is often underestimated: the handling of credit notes and correction documents in a dematerialised and controlled environment. Unlike traditional paper or PDF invoices, structured e-invoicing imposes precise rules for correction, transmission and archiving. This article outlines the regulatory framework, accepted formats, workflows to master and best practices for processing credit notes correctly within the 2026-2027 reform. To understand the full scope of the reform, consult our comprehensive guide to e-invoicing 2026-2027.

---

What is a credit note in the context of e-invoicing?

Definition and terminology: credit note, correction document, corrective invoice

In French tax and accounting law, the term credit note (or avoir in French) designates any commercial document that partially or fully cancels a previous invoice, or grants a commercial gesture to the customer. The reform introduces an important terminological clarification: the credit note (or credit note in English) is now the standardised term in structured formats such as Factur-X and UBL 2.1. These two terms actually cover three distinct situations:

• Cancellation credit note: fully cancels an issued invoice (error in amount, recipient, VAT).

• Partial credit note: corrects a specific line or amount without affecting the rest of the invoice.

• Commercial credit note (or rebate): granted for customer loyalty, volume or dispute resolution, without being linked to a factual error.

These distinctions are not merely academic: they determine the type of electronic document to be issued, the transmission workflow via the approved platform and the e-reporting data to be transmitted to the French tax authority (DGFiP).

Why the reform complicates credit note processing

Before mandatory dematerialisation, a credit note could be issued as a simple PDF mentioning the number of the original invoice. The reform now requires that every credit note be:

• Structured in a standardised format (Factur-X, UBL 2.1 or CII) containing specific mandatory fields for correction documents.

• Transmitted via an Approved Dematerialisation Platform (PDP) or the Public Invoicing Portal (PPF).

• Referenced to the original invoice by its unique identifier.

• Archived under the same security and integrity conditions as original invoices, for a minimum of ten years.

These technical requirements transform a once-simple accounting act into a structured process in its own right. For more information on formats, our article on Factur-X, the Franco-German e-invoicing format details the structure of fields used in correction documents.

---

The format of electronic credit notes: mandatory fields and technical specifics

Fields specific to credit notes in Factur-X and UBL

In the Factur-X format, a credit note is distinguished from a standard invoice by the document type code: code 381 (Credit Note) according to the UNTDID 1001 code list. This code indicates to the receiving platform that this is a correction document rather than an invoice to be paid.

Specific mandatory fields include:

• BT-3: Document type (code 381 for credit note, 383 for debit note).

• BT-25: Number of the previous invoice (mandatory reference to the original invoice).

• BT-26: Date of the original invoice.

• BT-5: Currency (identical to the original invoice).

• BG-3: Reference to the previous invoice (complete data group).

The absence of the BT-25 field is a blocking error: the approved platform will reject the document. This is one of the most frequent pitfalls observed during the pilot phases of 2025.

Managing VAT amounts in an electronic credit note

The treatment of VAT in an electronic credit note follows precise rules. The amount of VAT recoverable by the issuer (seller) or to be remitted by the recipient (buyer) must be explicitly stated and broken down by rate in the structured document. The reform prohibits correction documents with global amounts without VAT breakdown.

If the credit note covers several lines at different rates (for example 5.5% and 20%), each rate must be the subject of a separate data group (group BG-23 in the EN 16931 standard). This level of detail is necessary to correctly populate the e-reporting transmitted to the DGFiP, which uses this data to verify declared VAT. To fully understand this transmission obligation, consult our dedicated page on e-reporting and the transmission of transaction data.

---

Processing workflow for a credit note on an approved platform (PDP)

From issuance to archiving: the lifecycle stages

The processing of a credit note on an Approved Platform (PDP) follows a standardised lifecycle comprising several mandatory statuses:

• Issuance: the company creates the credit note in its ERP or invoicing tool, in structured format.

• Deposit on the PDP: the platform validates the document syntactically and semantically (check of mandatory fields, consistency of amounts, presence of BT-25).

• Transmission: the PDP routes the document to the recipient's PDP or the PPF.

• Acknowledgement of receipt: the recipient acknowledges receipt, triggering the "Received" status.

• Accounting processing: status "Accounted" or "Rejected" according to the recipient's practices.

• Archiving: the document is time-stamped and archived in both directions (issuer and recipient).

This cycle differs from the processing of an ordinary invoice on a single important point: rejection of a credit note by the recipient is more complex. If the customer disputes the credit note amount, they cannot simply "refuse" the document; they must issue a formal request for correction, potentially followed by a new corrective credit note. PDPs must support this structured dispute mechanism.

Regulatory timeframes to observe

Article 289 of the French General Tax Code (CGI) requires that the corrective invoice be issued within the usual invoicing timeframes, that is to say no later than the 15th of the month following that in which the tax event giving rise to the correction occurred (error identified, goods returned, dispute settled). In an electronic environment, this timeframe is all the more imperative because the e-reporting system transmits data to the DGFiP in near real-time. A significant gap between the date of the original invoice and the date of the credit note can trigger alerts in automated tax control tools.

Consult the detailed timetable for e-invoicing 2026-2027 to ensure you do not miss critical deadlines depending on the size of your business.

---

Best practices for accounting and finance teams

Update internal processes before deployment

The transition to e-invoicing requires reviewing dispute management and correction processes well before the obligation date. Teams must in particular:

• Identify all scenarios triggering a credit note in their business (product returns, price errors, post-invoice commercial rebates, partial service termination).

• Verify that their ERP or invoicing tool correctly generates the code 381 and automatically populates the BT-25.

• Train accounting teams to distinguish between cancellation credit notes, partial credit notes and commercial rebates, as these three cases may require different type codes.

• Set up an internal validation workflow before issuance, to avoid cascading credit notes (credit note correcting an erroneous credit note).

Archiving and reliable audit trail (PAF)

The reliable audit trail (PAF), required by article 289 VII of the CGI, must cover the entire documentary chain: original invoice → credit note → any complementary invoice. In an electronic environment, this trail must be traceable and tamper-proof, which means that each document must be qualified time-stamped. Qualified electronic time-stamping constitutes in this respect a non-negligible element of compliance: it proves the anteriority of each correction document and protects the company in the event of a tax audit.

Companies that relied on non-structured PDF archiving will need to migrate to compliant archiving solutions NF Z 42-013 or ISO 14641, capable of preserving XML or Factur-X files with their metadata for ten years.

Special cases: cross-border credit notes and intra-Community transactions

Credit notes issued as part of intra-Community transactions (supplies of goods or services between taxable persons in different EU Member States) are not subject to mandatory French e-invoicing, but fall under e-reporting: data must be transmitted to the DGFiP. This distinction is important: the document format is not mandatory for these flows, but correction data must appear in the periodic report transmitted via the PDP or PPF. Companies realising a significant share of their turnover internationally must therefore ensure that their tool correctly distinguishes domestic flows (subject to e-invoicing) from cross-border flows (subject only to e-reporting).

Legal framework applicable to credit notes and e-invoices

Reference texts

The legal regime for credit notes in e-invoicing is structured around several fundamental texts:

French General Tax Code (CGI):

• Article 289: defines invoicing obligations, mandatory information and conditions for issuing corrective invoices. It notably requires that any corrective invoice (credit note) makes reference to the original invoice and states the reason for the correction.

• Article 289 bis: establishes the conditions for e-invoicing, data retention and the reliable audit trail.

• Article 289 VII: specifies the terms of archiving and retention guaranteeing the authenticity of origin, integrity of content and readability of invoices.

Ordinance no. 2021-1190 of 15 September 2021 relating to the generalisation of e-invoicing in transactions between taxable persons. This ordinance amended article 289 bis of the CGI and establishes the legal framework for the 2026-2027 reform, including correction documents.

Decree no. 2022-1299 of 7 October 2022 specifying the technical conditions for implementing the reform, accepted formats and transmission methods via platforms.

European standard EN 16931: European semantic standard for e-invoicing, transposed into French law. It defines the mandatory fields for credit notes (code 381) and debit notes (code 380). Compliance with this standard is mandatory for any invoice or credit note transmitted via the Peppol network or French PDPs.

eIDAS Regulation no. 910/2014: applicable for the legal value of electronic signatures affixed to invoicing documents, particularly when a qualified signature is required for certain sectors (public procurement, healthcare). eIDAS Regulation 2.0 (which came into force in 2024) strengthens these requirements.

Obligations and legal risks

The failure to mention the original invoice in an electronic credit note constitutes a formal irregularity subject to sanctions by the tax authority during an audit. The sanctions provided for in article 1737 of the CGI can reach 50% of the VAT amount mentioned on the irregular document.

Furthermore, the issuance of a non-compliant electronic credit note (incorrect format, missing code 381, missing BT-25) can result in automatic rejection by the recipient's PDP, delaying accounting treatment and creating a commercial dispute risk. Companies must also ensure compliance with GDPR no. 2016/679 insofar as invoices and credit notes contain personal data (name of the invoicing contact, coordinates): retention on PDPs must be the subject of contractual clauses compliant with designated sub-processors.

Use cases: the electronic credit note in practice

Scenario 1: an industrial supplies distributor managing supplier returns

A small industrial SME of around one hundred employees, distributing technical consumables to a B2B clientele, generates on average 150 credit notes per month related to returns of defective or incorrect goods. Before the reform, these credit notes were issued as PDFs sent by email, with an average processing time of five working days on the client side.

Since the deployment of mandatory e-invoicing in September 2026, the company has integrated the automatic generation of credit notes (code 381 + BT-25) into its ERP. Processing time has fallen to less than 24 hours, thanks to direct transmission via the PDP and automatic acknowledgement of receipt. Accounting reconciliation, which previously required manual intervention by an accountant for each credit note, is now automated at 80%. Sector reports on accounting dematerialisation estimate that this type of automation allows companies of comparable size to reduce the processing time for correction documents by 60 to 75%.

Scenario 2: an IT services provider and credit notes on annual subscriptions

An IT services company with 80 employees markets annual subscriptions to software solutions. It regularly issues partial credit notes when a customer cancels a module during the year. These credit notes cover prorated amounts and involve several VAT rates (20% for software licences, VAT exemption for certain training).

Before the reform, VAT errors on these credit notes accounted for approximately 8% of issued documents, generating correction requests and extended payment delays. With automatic validation of structured formats on the PDP (semantic checking of the EN 16931 standard), the error rate has fallen below 1%. The reliable audit trail automatically generated has also simplified tax audit preparation, reducing the time to prepare an audit file from several days to a few hours.

Scenario 3: a food products wholesaler and year-end rebates

A food wholesaler with annual turnover of approximately 15 million euros grants conditional rebates to its customers each year in December based on volumes purchased. These rebates, formalised by commercial credit notes, represent on average 200 documents per year, concentrated over three weeks.

The specific difficulty: these credit notes are not linked to a single original invoice but to a series of invoices issued throughout the year. In Factur-X, it is possible to reference multiple original invoices in the BG-3 fields, but this requires precise ERP configuration. After support from their PDP, the company implemented a multi-referenced annual credit note model that complies with the standard. Result: zero rejections on the December 2026 rebate campaign, compared to 12% rejections during the pilot test conducted in 2025 with a non-optimised format.

Frequently Asked Questions

Must an electronic credit note necessarily reference the original invoice?

Yes, referencing the original invoice is a non-negotiable technical obligation in structured formats such as Factur-X or UBL 2.1. The BT-25 field, which contains the number of the corrected invoice, is automatically validated by the partner dematerialisation platform. A credit note transmitted without this field will be rejected before it even reaches the recipient, rendering the correction invalid from a tax perspective.

What is the difference between a cancellation credit note and a commercial credit note for VAT purposes?

A cancellation credit note cancels a debt and allows the issuer to recover the VAT initially collected, provided the customer is informed. A commercial credit note granted as a rebate or loyalty gesture also entitles the parties to VAT adjustment, but only if the credit note is properly issued and the customer reverses the corresponding amount. In both cases, the breakdown by VAT rate must appear explicitly in the structured document.

Is an electronic credit note subject to the same archiving obligations as the original invoice?

Yes, electronic credit notes are tax documents in their own right and must be retained under the same conditions of security and integrity as invoices, namely for a minimum of ten years in France. The archiving must guarantee the readability, integrity and traceability of the document throughout this period, whether it is stored by the company, by a PDP or with a certified third-party archiver.

Must an electronic credit note be transmitted via a PDP even if the original invoice was issued in PDF?

From the date the reform takes effect, any corrective document relating to domestic B2B transactions must be routed through an approved platform or the Public Invoicing Portal, regardless of the format of the original invoice. The reform does not provide for any specific transitional regime for credit notes correcting old paper or PDF invoices: the corrective document must itself comply with the mandatory structured format.

What happens if a credit note is rejected by the recipient's platform?

The rejection generates a negative status in the document's lifecycle, visible to the issuer on its own platform. The issuer must correct the anomalies flagged, whether a missing field, an amount inconsistency or a recipient identification issue, and then reissue a new corrective document. During this period, the correction is not legally binding on the recipient and the corresponding VAT cannot yet be adjusted.

Conclusion

Credit notes constitute standalone documents within the new mandatory e-invoicing system. Far from being a simple accounting gesture, their issuance in 2026 must comply with precise technical rules: code 381, BT-25 reference to the original invoice, VAT breakdown by rate, transmission via PDP and compliant archiving. Companies that anticipate these requirements — by updating their ERPs, training their teams and selecting an appropriate approved platform — avoid automatic rejections, tax penalties and extended processing times.

Certyneo supports you in achieving compliance with your e-invoicing workflows, including the processing of credit notes and correction documents. Discover our solutions and calculate your ROI on dematerialisation or contact our experts for a personalised assessment.