Credit Notes and Electronic Invoicing: Managing Corrections in 2026

Introduction: Why Credit Notes Become a Critical Issue in 2026

With the mandatory electronic invoicing taking effect for large enterprises and mid-market companies as of September 1, 2026, finance and accounting departments face a challenge that is often underestimated: the processing of credit notes and debit memos in a dematerialized and controlled environment. Unlike traditional paper or PDF invoices, structured electronic invoicing imposes precise rules for correction, transmission, and archiving. This article details the regulatory framework, approved formats, workflows to master, and best practices for handling credit notes without error in the 2026-2027 reform. To understand the full scope of the reform, consult our comprehensive guide to electronic invoicing 2026-2027.

---

What Is a Credit Note in the Context of Electronic Invoicing?

Definition and Terminology: Credit Note, Debit Memo, Corrective Invoice

In French fiscal and accounting law, the term credit note designates any commercial document that cancels in whole or in part 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 standardized term in structured formats such as Factur-X and UBL 2.1. These two designations actually cover three distinct situations:

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

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

• Commercial credit note (or rebate): granted for loyalty, volume, or dispute settlement, unrelated to a factual error.

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

Why the Reform Complicates Credit Note Processing

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

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

• Transmitted via a Partner Dematerialization 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. To go deeper into formats, our article on Factur-X, the Franco-German electronic invoicing format details the structure of fields used in corrective 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 corrective document and not an invoice to be paid.

Specific mandatory fields include:

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

• 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 field BT-25 is a blocking error: the approved platform will reject the document. This is one of the most frequent pitfalls observed during the 2025 pilot phases.

Management of 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 payable by the recipient (buyer) must be explicitly stated and broken down by rate in the structured document. The reform prohibits corrective documents with global amounts without VAT breakdown.

If the credit note covers multiple 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 properly feed the e-reporting transmitted to the DGFiP, which uses this data to verify declared VAT. To understand fully this transmission obligation, consult our dedicated page on e-reporting and transaction data transmission.

---

Processing Workflow for a Credit Note on an Approved Platform (PDP)

From Issuance to Archiving: Steps in the Lifecycle

The processing of a credit note on an Approved Platform (PDP) follows a standardized lifecycle with 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.

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

• Accounting Recognition: status "Recognized" or "Rejected" depending on 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: the rejection of a credit note by the recipient is more complex. If the customer disputes the amount of the credit note, they cannot simply "refuse" the document; they must issue a formal correction request, potentially followed by a new corrective credit note. PDPs must support this structured dispute mechanism.

Regulatory Timeframes to Respect

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

Consult the detailed calendar for electronic invoicing 2026-2027 to avoid missing critical deadlines according to your company's size.

---

Best Practices for Accounting and Finance Teams

Update Internal Processes Before Deployment

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

• Identify all scenarios triggering a credit note in their activity (product returns, price errors, retroactive commercial discounts, partial service termination).

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

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

• Implement a 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 supplementary invoice. In an electronic environment, this trail must be traceable and tamper-proof, which means that each document must be time-stamped qualifiedly. Qualified electronic time-stamping is in this regard a non-negligible element of compliance: it proves the anteriority of each corrective document and secures the company in case of 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 Operations

Credit notes issued in the context of intra-community operations (supply of goods or services between taxable persons in different EU member states) are not subject to mandatory French electronic invoicing, but fall under e-reporting: data must be transmitted to the DGFiP. The distinction is important: the format of the document is not imposed for these flows, but correction data must appear in the periodic report transmitted via the PDP or PPF. Companies realizing a significant share of their turnover internationally must therefore ensure that their tool correctly distinguishes between domestic flows (subject to e-invoicing) and cross-border flows (subject only to e-reporting).

Legal Framework Applicable to Credit Notes and Electronic Invoices

Reference Texts

The legal regime for credit notes in electronic invoicing is built around several fundamental texts:

French General Tax Code (CGI):

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

• Article 289 bis: governs the conditions of electronic invoicing, data preservation, and the reliable audit trail.

• Article 289 VII: specifies the modalities of archiving and preservation guaranteeing the authenticity of origin, the integrity of content, and the legibility of invoices.

Order no. 2021-1190 of September 15, 2021 on the generalization of electronic invoicing in transactions between taxable persons. This order amended article 289 bis of the CGI and established the legal framework for the 2026-2027 reform, including corrective documents.

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

European Standard EN 16931: European semantic standard for electronic invoicing, transposed into French law. It defines mandatory fields for credit notes (code 381) and debit memos (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 to the legal value of the electronic signature affixed to invoicing documents, in particular when a qualified signature is required for certain sectors (public procurement, healthcare). The eIDAS 2.0 regulation (entered 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 sanction by the tax administration upon audit. Penalties provided for by article 1737 of the CGI can reach 50% of the VAT stated on the irregular document.

Moreover, issuance of a non-compliant electronic credit note (incorrect format, missing code 381, BT-25 missing) may result in automatic rejection by the recipient's PDP, delaying accounting processing and creating a commercial dispute risk. Companies must also ensure compliance with GDPR no. 2016/679 to the extent that invoices and credit notes contain personal data (name of billing contact, contact details): preservation on PDPs must be subject to contractual clauses compliant with designated sub-processors.

Use Cases: Electronic Credit Notes in Practice

Scenario 1: An Industrial Supplies Distributor Managing Supplier Returns

A mid-sized industrial company with about one hundred employees, distributing technical consumables to a B2B clientele, generates on average 150 credit notes per month related to returns of defective or erroneous goods. Before the reform, these credit notes were issued as PDFs sent by email, with an average processing time of five business days on the customer's side.

Since the deployment of mandatory electronic 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 automated acknowledgment of receipt. Accounting reconciliation, which previously required manual intervention by an accountant for each credit note, is now 80% automated. Industry reports on accounting dematerialization estimate that this type of automation allows reducing the processing time for corrective documents by 60 to 75% for companies of comparable size.

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 are for prorated amounts and involve multiple VAT rates (20% for software licenses, VAT exemption for certain training).

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

Scenario 3: A Food Product Wholesaler and Year-End Rebates

A food wholesaler with annual turnover of approximately 15 million euros grants conditional rebates each year in December to its customers based on volumes purchased. These rebates, formalized 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 over the year. In Factur-X, it is possible to reference multiple original invoices in fields BG-3, but this requires precise ERP configuration. After guidance by their PDP, the company implemented a multi-referenced annual credit note model in compliance. Result: zero rejections on the December 2026 rebate campaign, compared to 12% rejections during the pilot test conducted in 2025 with a non-optimized 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. Field BT-25, which contains the corrected invoice number, is automatically validated by the partner dematerialization platform. A credit note transmitted without this field will be rejected before it even reaches the recipient, making 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 extinguishes a debt and allows the issuer to recover the VAT originally collected, provided the customer is notified. A commercial credit note granted as a rebate or goodwill gesture also entitles the parties to VAT adjustment, but only if the credit note is properly issued and the customer repays 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 archival 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. Archival must guarantee the readability, integrity, and traceability of the document throughout this period, whether it is stored at the company, at 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?

As of the reform's entry into force, any corrective document relating to domestic B2B transactions must go through an approved platform or the Public Invoicing Portal, regardless of the format of the original invoice. The reform does not provide for a 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 reported anomalies, whether a missing field, an amount inconsistency, or a recipient identification problem, and then reissue a new corrective document. During this period, the correction is not legally enforceable against the recipient and the corresponding VAT cannot yet be adjusted.

Conclusion

The credit note constitutes a complete document in its own right within the new mandatory electronic invoicing system. Far from being a simple accounting gesture, its issuance in 2026 obeys 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 choosing an appropriate approved platform — avoid automatic rejections, tax penalties, and extended processing times.

Certyneo supports you in bringing your electronic invoicing flows into compliance, including the processing of credit notes and corrective documents. Discover our solutions and calculate your ROI on dematerialization or contact our experts for a personalized assessment.