Electronic Advance Invoice: VAT, Taxability and 2026 Reform

The widespread adoption of electronic invoicing in France is fundamentally disrupting accounting and tax practices that have been established for decades. Among the most sensitive issues is the electronic advance invoice: this document triggers specific obligations regarding VAT, taxability, and transmission to approved platforms. Since September 1, 2026, all large enterprises and medium-sized enterprises (ETIs) are required to issue invoices in structured format. SMEs and microenterprises will follow as of September 1, 2027. Understanding the tax mechanisms linked to advances, the accepted formats, and the pitfalls to avoid has become an absolute priority for finance and accounting departments. This article provides a comprehensive overview of the applicable rules, reporting obligations, and best practices to secure your compliance.

What is an advance invoice and why is it specific?

Definition and distinction from the final invoice

An advance invoice is issued when a customer pays a partial sum before the complete delivery of goods or completion of a service. It differs from the final invoice, which settles the entire transaction. From an accounting perspective, the advance invoice represents deferred income for the service provider and deferred expense for the customer.

This distinction is not merely semantic: from a tax perspective, the VAT regime applicable to the advance invoice varies depending on the nature of the transaction (supply of goods vs. service provision), and this is precisely the point that the 2026 reform has clarified and strengthened.

VAT Taxability: the heart of the matter

In French tax law, VAT taxability refers to the moment from which the tax authority can claim payment of the tax. This moment differs depending on the type of transaction:

• Supply of goods: VAT is taxable upon delivery (transfer of ownership). An advance paid before delivery does not trigger VAT taxability for goods, unless an invoice is issued before delivery — which changes the regime.

• Service provision: VAT is taxable upon receipt of payment. Consequently, receipt of an advance immediately triggers VAT taxability on that amount.

This dichotomy, established in Article 269 of the French General Tax Code (CGI), lies at the heart of the issues surrounding electronic advance invoices. Since the reform, the structured format of electronic invoices allows the tax authority (through the DGFiP) to automatically cross-reference transmitted data with VAT returns, making any anomaly immediately detectable.

New mandatory mentions from the reform

Ordinance No. 2021-1190 of September 15, 2021 and its implementing decrees introduced additional mandatory mentions on electronic invoices. For an advance invoice, the following elements must be included:

• The invoice number: unique and sequential, assigned by the issuing system or the Partner Dematerialization Platform (PDP).

• The nature of the transaction: the invoice must indicate that it is an advance and specify the nature of the goods or service concerned.

• The gross amount, the VAT rate and the VAT amount corresponding to the advance.

• The date of VAT taxability: mandatory mention since January 1, 2026 for service provision.

• The reference to the initial order or contract.

• The SIREN identifier of the issuer and recipient.

• The delivery address if different from the billing address.

The absence of even one of these mentions can result in rejection of the invoice by the reception platform, with cascading consequences for VAT deductibility for the customer.

Accepted electronic formats for advance invoices

Factur-X: the Franco-German hybrid format

The Factur-X format is now the reference format for B2B exchanges in France. It is a hybrid PDF/A-3 format integrating structured XML data according to the EN 16931 standard. For advance invoices, it offers the advantage of combining human readability (the PDF) and automated processing (the embedded XML).

The EN 16931 profile (minimum legal profile) is sufficient for the majority of advance invoices, but certain complex transactions (construction work, staged contracts) require the Extended profile, which allows additional fields to detail the breakdown of advances and balances.

You can verify the compliance of your Factur-X files using our free Factur-X validator, which checks the XML structure, mandatory data and compliance with the declared profile.

UBL and CII: the other accepted formats

In addition to Factur-X, two other purely structured formats are accepted by the Public Invoicing Portal (PPF) and PDPs:

• UBL 2.1 (Universal Business Language): an international standard widely used in European exchanges.

• CII D16B (Cross Industry Invoice): a format derived from the UN/CEFACT standard, used notably in exchanges with Germany and Nordic countries.

For advance invoices, the choice of format depends primarily on the business sector and the technical constraints of the recipient. Approved platforms (PDPs) are required to accept and convert these three formats.

The role of the invoice lifecycle

One of the major innovations of the reform is the introduction of a standardized lifecycle for each electronic invoice. An advance invoice can take the following statuses:

• Deposited: received by the issuer's platform.

• Made available: transmitted to the recipient's platform.

• Received: acknowledged by the recipient's system.

• Rejected: refused for technical or formal non-compliance.

• Accepted: validated by the recipient.

• Submitted for payment: payment triggered.

This real-time tracking represents a major departure from previous practices and requires a complete revision of collection follow-up and recovery processes. The electronic invoicing schedule 2026-2027 details the implementation phases according to the enterprise category.

VAT on advances: precise rules according to the nature of the transaction

Advance on service provision: VAT on receipt

For service providers subject to the accrual basis regime (the general regime in France for VAT on receipt of payment), receipt of an advance immediately triggers VAT taxability. The electronic advance invoice must therefore:

• Clearly indicate that VAT is calculated on the amount of advance received.

• Mention the effective receipt date (or expected date if the invoice is issued before payment).

• Be transmitted to the platform within a maximum of 2 business days after issuance (rule introduced by the decree of October 7, 2022).

Caution: a service provider who fails to report VAT on an advance received faces a VAT adjustment plus late payment interest (0.20% per month, Article 1727 of the CGI) and, in case of repeated non-compliance, a 40% increase for intentional non-compliance.

Advance on supply of goods: the rule of invoice priority

For supplies of goods, VAT is in principle taxable only upon delivery. However, if an advance invoice is issued before delivery, it triggers VAT taxability up to the invoiced amount, in accordance with Article 269-2-c of the CGI. This rule, confirmed by the CJEU in the BUPA Hospitals judgment (C-419/02 of February 21, 2006), applies as long as the goods are precisely identified and the amount of tax can be calculated.

In the context of electronic invoicing, this anticipated taxability must be explicitly stated in the invoice XML via the `TaxPointDate` field (Factur-X) or equivalent UBL/CII.

The case of mixed transactions and staged contracts

Construction contracts, IT projects, or long-term maintenance contracts often combine supplies of goods and service provision. In this case, the breakdown of advances by nature of transaction is mandatory. The Factur-X Extended format allows this breakdown via separate invoice lines with different VAT categories.

Non-compliance with this rule exposes the issuer to automatic rejection by the PDP and, in case of wrongful acceptance, to a risk of adjustment during a tax audit.

E-reporting and transmission of advance data to the DGFiP

What is e-reporting?

E-reporting is the obligation to transmit to the tax authority data for transactions that do not involve a B2B electronic invoice (B2C transactions, transactions with foreign enterprises). For domestic B2B electronic advance invoices, data is transmitted automatically via the PDP or PPF — no separate e-reporting flow is necessary.

However, if an assujetti enterprise issues an advance for a service provided to a private customer (B2C), it must transmit the data for this transaction via the e-reporting channel, including the gross amount, VAT rate, and receipt date.

Transmission frequency and deadlines

E-reporting data must be transmitted according to the enterprise's VAT return filing frequency:

• Monthly regime: transmission within 10 days following the end of the month.

• Quarterly regime: transmission within 10 days following the end of the quarter.

These deadlines are strict. Late transmission results in a fine of €250 per missing invoice, capped at €15,000 per fiscal year (Article 1737 of the CGI, as amended by the 2024 Finance Law).

Automatic reconciliation of advances and balances

One of the major contributions of the new system is the DGFiP's ability to automatically reconcile advance invoices with corresponding balance invoices. For this reconciliation to work, balance invoices must obligatorily reference the numbers of previous advance invoices. This documentary chain, made possible by structured formats, is algorithmically verified by platforms before transmission to the authority. Any break in the chain generates a compliance alert.

Legal framework applicable to the electronic advance invoice

The electronic advance invoice is part of a set of legislative and regulatory texts that must be mastered to ensure full compliance.

French General Tax Code (CGI): Article 269 of the CGI defines the rules for VAT taxability according to the nature of transactions. Article 289 imposes mandatory mentions on all invoices, reinforced for electronic invoices by Decree No. 2022-1299 of October 7, 2022. Article 1737 sets out the penalties applicable in case of non-compliance with transmission obligations.

Ordinance No. 2021-1190 of September 15, 2021: It constitutes the founding text of the electronic invoicing reform in France, partially transposing Directive 2014/55/EU and anticipating Directive DAC7. It introduces the obligation to use a PDP or the PPF for domestic B2B exchanges.

Decree No. 2022-1299 of October 7, 2022: It specifies the technical implementation procedures, the accepted formats (Factur-X, UBL, CII), transmission deadlines and the standardized lifecycle of invoices. It makes transmission of processing statuses between PDPs mandatory.

VAT Directive 2006/112/EC (amended by the ViDA Directive, 2025/516/UE): The "VAT in the Digital Age" (ViDA) directive, adopted in 2025 and progressively applicable until 2030, harmonizes VAT taxability rules on advances across Europe. It notably requires that any advance invoice on intra-EU cross-border service provision immediately triggers VAT, regardless of the receipt date.

eIDAS Regulation No. 910/2014 and eIDAS 2.0 (EU Regulation 2024/1183): Although electronic signature is not mandatory on French B2B invoices (the electronic seal of the PDP is sufficient), the use of a signature conforming to eIDAS strengthens the evidentiary value of the invoice in case of dispute. eIDAS 2.0 regulation, applicable since May 20, 2024, introduces the European Digital Identity Wallet (EUDI Wallet), which will eventually allow the parties to be authenticated when issuing invoices.

Standard EN 16931: European standard defining the semantic model of electronic invoices. All accepted formats (Factur-X, UBL, CII) must comply with it. The standard includes specific elements for managing advances (`PREPAID_AMOUNT`, `DUE_PAYABLE_AMOUNT`).

GDPR No. 2016/679: Personal data contained in invoices (contact name, email address) must be processed in accordance with GDPR. PDPs are processors under Article 28 and must provide a conforming DPA (Data Processing Agreement). The legal retention period for invoices is 10 years (Article L.123-22 of the Commercial Code), which imposes security and integrity guarantees over this entire period.

Non-compliance risks: A VAT adjustment on improperly reported advances can reach several years of arrears, increased by 0.20% interest per month and a penalty of 40% to 80% depending on severity. Non-transmission of electronic invoices via a PDP or the PPF also exposes you to a fine of €15 per invoice (minimum €60,000 per fiscal year), without prejudice to criminal proceedings in case of proven fraud.

Usage scenarios: the electronic advance invoice in practice

Scenario 1 — A digital transformation consulting firm managing 150 missions/year

A consulting firm of 25 consultants issues on average 3 to 4 advances per mission, representing 30% to 50% of the contract amount. Before the reform, these advances were issued as free PDF, without explicit mention of VAT taxability date. The firm had to manually reconcile advances with balance invoices in its ERP.

Since deploying a PDP interfaced with its ERP, each advance invoice is generated in Factur-X EN 16931 format, automatically transmitted to the client's platform, and status is updated in real time. VAT on advances is now automatically attached to the receipt period in accounting. Result: 65% reduction in advance invoice processing time, zero rejections over the first 6 months, and elimination of VAT timing risks that previously averaged 3 to 4 annual adjustments with the authority.

Scenario 2 — An industrial SME manufacturing custom equipment

An 80-employee SME manufacturing custom industrial machines systematically invoices 40% advance at order and 40% at delivery. The remaining 20% is invoiced after final acceptance. These transactions involve supplies of goods — the rule of invoice priority therefore applies: issuing the advance invoice before delivery immediately triggers VAT taxability.

The challenge was to correctly configure the `TaxPointDate` field in Factur-X files to reflect the issuance date (not the delivery date) as the VAT taxability starting point. After configuration and training of the accounting team, the SME reduced average collection cycles by 18 days, thanks to real-time lifecycle tracking. Any rejections (less than 2% of invoices) are now handled in less than 4 hours thanks to automatic PDP notifications.

Scenario 3 — A real estate developer managing new construction programs

In the real estate development sector, the use of calls for funds (forms of regulated advances) is systematic. A developer managing about ten programs simultaneously issues hundreds of advance invoices per year, addressed to professional buyers (institutional investors, civil partnerships) and individuals.

The B2B portion is processed via a PDP in Factur-X Extended format, allowing the breakdown of calls for funds by lot and by construction phase. The B2C portion is transmitted via e-reporting. Integration with the program management software enabled automation of advance invoice generation upon validation of the construction milestone, reducing issuance times from 5 days to less than 24 hours. VAT on collection risks (VAT on margin in real estate development) were secured by specific rate configuration in the system, validated by the group's accountant.

Frequently Asked Questions

Is VAT due upon receipt of a deposit for goods delivery?

No. For goods deliveries, VAT becomes due at the time of transfer of ownership, that is, upon actual delivery. A deposit paid before this delivery therefore does not trigger VAT liability, unless an invoice is issued before the delivery itself. In this specific case, the issuance of the invoice creates VAT liability, which modifies the declarative obligations of the issuer.

What is the difference between a deposit invoice and a progress invoice in the construction sector?

A deposit invoice corresponds to a partial payment made before any commencement or progress of performance. A progress invoice, used notably in construction, certifies actual and measurable progress of works on a given date. Both documents are subject to VAT on cash basis for service provisions, but the progress invoice must additionally detail the items completed, which implies additional structured fields in XML formats.

Can an electronic deposit invoice be cancelled after transmission to the platform?

An electronic invoice that has been transmitted cannot be deleted: it must be the subject of a credit note referencing the original invoice. This credit note document follows the same transmission circuit as the original invoice and triggers an update of the lifecycle. Any partial correction of the amount follows the same logic, via a partial credit note followed by a new corrective invoice, in order to maintain the traceability required by the tax authority.

How can the customer deduct VAT shown on a deposit invoice?

For service provisions, the customer may deduct the VAT shown on the deposit invoice as soon as it is received and the corresponding payment is made. The invoice must explicitly state the VAT amount, the applicable rate, and the date of VAT liability. In the absence of one of these mandatory mentions, deductibility may be challenged during a tax audit, regardless of whether payment has actually been made.

Must microenterprises issue electronic deposit invoices before September 2027?

Before their mandatory entry into force date, microenterprises are not required to issue structured electronic invoices. They remain obliged, however, to receive electronic invoices sent by their taxable-person suppliers. It is nevertheless recommended to anticipate the transition, as exchanges with customers subject to the obligation since 2026 can generate practical format compatibility requirements well before the regulatory deadline.

Conclusion

The electronic advance invoice concentrates within itself the main issues of the 2026 reform: compliance of formats, VAT taxability according to the nature of the transaction, documentary chain with balance invoices, and real-time transmission to approved platforms. The rules from the 2021 ordinance and 2022 decree, reinforced by the ViDA directive, leave little room for approximation: an error in taxability date or the absence of a mandatory mention can trigger automatic rejection, a VAT adjustment, or a fine.

Implementing a robust solution, interfaced with your ERP and connected to a certified PDP, is no longer optional but an operational necessity. Certyneo supports you in this transition with tools adapted to your business realities. Discover our pricing and start your compliance today.