Credit Notes and Electronic Invoicing: Managing Corrections in 2026

Introduction: Why Credit Notes Become a Critical Challenge in 2026

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

---

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

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

In French fiscal and accounting law, the term credit note refers to any business document that fully or partially cancels a previous invoice or grants a commercial concession to a customer. The reform introduces important terminology precision: the credit memo (or credit note in English) is now the standardized term in structured formats such as Factur-X and UBL 2.1. These two names actually cover three distinct situations:

• Cancellation credit note: fully cancels an issued invoice (incorrect amount, wrong recipient, 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 customer loyalty, volume discounts, or settlement of disputes, unrelated to a factual error.

These distinctions are far from purely academic: they determine the type of electronic document to issue, the transmission workflow on the approved platform, and the e-reporting data to submit 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 Certified 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 action into a structured process in its own right. For more details on formats, our article on Factur-X, the Franco-German electronic invoicing format outlines the structure of fields used in corrective documents.

---

The Format of Electronic Credit Notes: Mandatory Fields and Technical Specifics

Fields Specific to Credit Memos in Factur-X and UBL

In the Factur-X format, a credit memo is distinguished from a standard invoice by the document type code: code 381 (Credit Note) according to the UNTDID 1001 code list. This code signals to the receiving platform that this is a corrective document and not an invoice to be paid.

The specific mandatory fields include:

• BT-3: Document type (code 381 for credit memo, 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 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.

Managing VAT Amounts in an Electronic Credit Note

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

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

---

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

From Issuance to Archiving: Stages of the Life Cycle

The processing of a credit note on a Certified Dematerialization Platform (PDP) follows a standardized life cycle with several mandatory statuses:

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

• Upload to the PDP: the platform validates the document syntactically and semantically (checking 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 Processing: status "Recorded" 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 one 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 submit a formal correction request, potentially followed by a new corrective credit note. PDPs must support this structured dispute mechanism.

Regulatory Timelines to Observe

Article 289 of the French General Tax Code (CGI) requires that the corrective invoice be issued within the normal invoice issuance deadline, meaning no later than the 15th of the month following the month in which the correction fact occurred (error discovered, merchandise returned, dispute settled). In an electronic environment, this deadline is even more critical because 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 timeline for electronic invoicing 2026-2027 to ensure you don't miss 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 that you revise dispute management and correction processes well before the obligation date. Teams should specifically:

• Identify all scenarios triggering a credit note in their business (product returns, price errors, retroactive trade 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 cancellation credit notes, partial credit notes, and commercial rebates, as these three cases may require different document type codes.

• Implement an internal validation workflow before issuance to avoid cascading credit notes (a 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 document chain: original invoice → credit note → any subsequent supplementary invoice. In an electronic environment, this trail must be traceable and unfalsifiable, which means each document must be qualified time-stamped. Qualified electronic time-stamping is therefore a non-negligible element of compliance: it proves the priority of each corrective document and secures the company in the event of a tax audit.

Companies that relied on unstructured PDF archiving will need to migrate to compliant archiving solutions meeting NF Z 42-013 or ISO 14641 standards, 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 in the context of intra-community transactions (supply of goods or provision of services between taxable persons in different EU member states) are not subject to mandatory French electronic invoicing, but are subject to 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 submitted via the PDP or PPF. Companies conducting a significant share of their turnover internationally must therefore ensure 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 Electronic Invoices

Reference Texts

The legal regime for credit notes in electronic invoicing is built around several key 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) reference the original invoice and state the reason for the correction.

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

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

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

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

European Standard EN 16931: European semantic standard for electronic invoicing, implemented in French law. It defines mandatory fields for credit memos (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 n° 910/2014: applicable to the legal value of electronic signatures affixed to invoicing documents, particularly when a qualified signature is required for certain sectors (public procurement, healthcare). The eIDAS 2.0 regulation (effective 2024) strengthens these requirements.

Obligations and Legal Risks

The failure to mention the original invoice in an electronic credit note constitutes a formal irregularity sanctionable by the tax administration during an audit. Penalties under article 1737 of the CGI may reach 50% of the VAT amount stated on the irregular document.

Furthermore, issuing a non-compliant electronic credit note (incorrect format, missing code 381, missing BT-25) 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 n° 2016/679 insofar as invoices and credit notes contain personal data (name of billing contact, contact information): retention on PDPs must be covered by contractual clauses compliant with designated subprocessors.

Use Case Scenarios: Electronic Credit Notes in Practice

Scenario 1: An Industrial Supplies Distributor Managing Supplier Returns

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

Since the mandatory electronic invoicing deployment in September 2026, the company has integrated automatic generation of credit memos (code 381 + BT-25) into its ERP. Processing time has dropped to under 24 hours thanks to direct transmission via the PDP and automatic acknowledgment of receipt. Accounting reconciliation, which previously required manual intervention by an accountant for each credit note, is now automated at 80%. Industry reports on accounting dematerialization estimate that this type of automation enables reducing corrective document processing time by 60 to 75% for companies of comparable size.

Scenario 2: An IT Services Provider and Credit Notes on Annual Subscriptions

A software company of 80 employees markets annual subscriptions to software solutions. It regularly issues partial credit notes when a client terminates a module during the year. These credit notes concern 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 accounted for approximately 8% of issued documents, generating correction requests and extended payment delays. With automatic validation of structured formats on the PDP (semantic validation of EN 16931 standard), the error rate has fallen below 1%. The reliable audit trail automatically generated has further 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 grants conditional rebates to customers each year in December based on purchase volumes. These rebates, formalized through commercial credit notes, represent an average of 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 the BG-3 fields, but this requires precise ERP configuration. After guidance from their PDP, the company implemented an annual multi-referenced credit note model that is compliant. 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 mandatorily reference the original invoice?

Yes, referencing the original invoice is a non-negotiable technical requirement 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, 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 erases a debt and allows the issuer to recover the VAT initially collected, provided the customer is informed thereof. A commercial credit note granted as a rebate or loyalty gesture also gives rise to VAT adjustment, but only if the credit note is duly issued and the customer remits 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 security and integrity conditions as invoices, namely a minimum of ten years in France. Archival must ensure the document's readability, integrity, and traceability throughout this period, whether it is stored with the company, with a certified dematerialization platform (PDP), or with a third-party certified archiver.

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

As of the reform's effective date, any corrective document relating to domestic B2B transactions must be transmitted through an approved platform or the Public Invoicing Portal, regardless of the format of the original invoice. The reform does not provide a specific transition regime for credit notes correcting older paper or PDF invoices: the corrective document itself must 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 issue, 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

The credit note and credit memo constitute standalone documents within the new mandatory electronic invoicing system. Far from being a simple accounting entry, their issuance in 2026 follows 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 delays.

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