Electronic invoicing by September 1, 2026: Concrete impact on logistics

There is something deeply ironic about this reform.

For twenty years, logistics departments have been asked to digitize their operations: scan packages, track batches, remove paper from the aisles. And for twenty years, in the majority of warehouses, the invoice remained the last bastion of the Excel file, copy-paste, and "I'll send it back to you on Monday.".

On September 1, 2026, this tolerance will end.

Yes, electronic invoicing doesn't tolerate approximations. It's structured, controlled, time-stamped, and its lifecycle is monitored by the tax authorities. Every line item must be verifiable. Every amount must be linked to a transaction actually carried out in your warehouse.

Finally comes the real question: do you know today, at D+1, how many billable work units you generated yesterday on each of your sites?

If the answer is "yes, in three clicks in my WMS software," you're 70% ready. If the answer is "I need to ask the site manager to send me back their file," you have a structural problem that the reform will make visible... and costly.

This article isn't just another legal analysis. It's a practical guide, written by people who have spent more time on the docks than in tax seminars. We'll be discussing delivery notes, receiving discrepancies, credit notes, units of work, order preparation, and inventory management. And we'll talk about how all of this connects, technically, to an Approved Platform.

The official calendar: What is required, and when

The three dates to mark on your IT roadmap

The French reform of electronic invoicing is based on a simple principle: generalize structured B2B invoicing, and transmit data to the administration in parallel (e-reporting).

One crucial detail that changes everything for many logistics SME managers: there is no extension for receiving invoices. As of September 1, 2026, if a major client sends you their transport or service invoice via an Approved Platform, you must be able to receive it, read it, and manage its entire lifecycle.

PPF, PDP, approved platform: What exactly are we talking about?

You will come across several terms, sometimes used interchangeably. Let's clarify all of this.

• The PPF (Public Billing Portal) is a government initiative. Its scope was refocused in October 2024: contrary to initial announcements, it will no longer provide a free invoice exchange service. It retains two roles: a directory (identifying the platform serving each company) and a central hub for data transmitted to the government.
• PDPs (Partner Dematerialization Platforms), also known as PAs (Approved Platforms ) , are private operators registered with the tax authorities. They are the ones who issue, receive, and transmit your invoices .

Translation for the logistics department: Thereis no longer a free public option. You will need to choose and contract with an Approved Platform.

What the reform does not mandate (and what they will try to sell you anyway)

Let's be honest, because the market is currently full of opportunistic offers.

The reform does not require :

• To change your ERP or warehouse management software
• To digitize your delivery notes or waybills
• To migrate your entire IT system to SaaS
• To subscribe to a publisher's "complete suite"

The reform requires :

• To be connected to an Approved Platform (available from 2026)
• To issue invoices in a standardized, structured format
• To transmit the mandatory billing data and lifecycle statuses
• To transmit payment data for services

The rest is optimization. Always separate "I must" from "I should" when you are making budget decisions.

Factur-X, UBL, CII: Understanding the formats without being a tax specialist

The basis of the three formats

The reform retains three core formats derived from the European standard EN 16931.

Why Factur-X is the natural format for logistics

Factur-X is a hybrid format. A single PDF file, which contains within it a structured XML file.

Why is this crucial for you?

Because in the real world of a warehouse, a logistics service invoice is read by humans. The client's operations manager wants to verify that the 1,240 pallets stored correspond to their average stock level. The buyer wants to check the applicable rate beyond the contractual threshold. The accountant wants to reconcile it with the delivery note.

With pure UBL or CII, these people need a viewing tool. With Factur-X, they open a PDF. And meanwhile, the machine reads the XML.

Factur-X offers several completeness profiles, from the simplest to the most comprehensive. For a multi-line logistics service invoice with detailed units of work, aim for at least the EN 16931 profile (also known as "BASIC WL" enhanced or higher). The simplified MINIMUM profiles do not include line-by-line detail. In short, they are unusable in a 3PL relationship.

The pitfall: The complexity of a logistics invoice versus a standard invoice

This is where, potentially, many projects will go off the rails.

A logistics service invoice is not a consulting invoice with three lines. It is a document that may include:

• Storage lines ( pallets/day, m²/month, spaces occupied per SKU)
• Handling lines ( receiving, storage, internal movements)
• Picking lines ( parcels, order lines, UVC, retail picking vs. pallet picking )
• Value-added operational lines ( co-packing, labeling, kitting, quality control)
• Re -invoicing (transport, packaging, consumables, pallets)
• Penalties and bonuses related to SLAs
• Contractual deductibles and decreasing tiers

Multiply that by 30 customer accounts on one site, by 12 sites. You get several thousand billing lines per month, each of which must be justified by a time-stamped operational data point.

The EN 16931 standard allows for this level of detail. However, the data must first exist, properly stored, in your upstream system. And this upstream system is neither your accounting nor your payroll system. It's your Warehouse Management System.

The real impact on your document workflows: delivery notes, pro forma invoices, credit notes

The delivery note: The document that will determine everything

A simple principle: in logistics, the invoice is the monetary translation of a physical flow. And the document that attests to this physical flow is the delivery note (or the waybill for transport).

Today, in many organizations, a tolerated discrepancy exists between the delivery note and the invoice. An extra pallet, a counting discrepancy, a damaged package refused at the delivery dock: the matter is rectified "at the invoice," by phone, by email, or by arrangement.

With the reform, this way of operating will become unsustainable. Why?

Because electronic invoices have mandatory lifecycle statuses: submitted, received by the recipient's platform, made available, and then recommended or optional statuses such as approved, rejected, disputed, and paid. These statuses are tracked. A rejection is a time-stamped event, reported to your platform, and potentially visible in your customer performance indicators.

In other words: the billing dispute becomes measurable, recorded historically and subject to adversarial proceedings.

If your goods receipt is not scanned in real time, if your discrepancies are not tracked with a reason, if your BL is not electronically signed by the driver or the customer, you will have no evidence to oppose in the event of a rejection.

What needs to be put in place, specifically:

• A single capture at the source: the movement scanned in the WMS is THE truth.
• A BL status : prepared, loaded, delivered, signed, discrepancy noted
• Traceability of discrepancies with coded reasons (breakage, missing items, quality rejection, non-conformity)
• A technical link between the delivery note and the resulting invoice line.
• An archive of the signed delivery note, referenced in the invoice

Pro forma invoices: Outside the scope, but not irrelevant

An important point, often misunderstood: a pro forma invoice is not an invoice in the tax sense. It does not establish a debt, does not include VAT due, and therefore is not subject to the obligation of electronic invoicing.

You can continue to send pro forma invoices in PDF format via email. It's not prohibited.

But let's be strategic. In the logistics and transportation industry, pro forma invoices are used extensively for:

• Validate a quote for an exceptional operation before execution
• Prepare an import/export or customs clearance file
• Obtaining budget approval from the client before providing value-added services
• Pre-invoice at the end of the month for validation before final issuance

It is this latter use that becomes strategic. If you implement a pre-invoicing cycle validated before the final electronic invoice is issued, you eliminate almost all downstream rejections.

The reasoning is simple: it is better to discuss a discrepancy of 40 pallets on a non-tax document than to suffer a time-stamped rejection on an invoice filed with an Approved Platform.

Assets: The red zone of the reform

This is the subject that's going to hurt, and nobody talks about it enough.

A credit note is an invoice. Therefore, it too must be issued in electronic format, pass through an Approved Platform, include the mandatory information and reference the original invoice.

But what is the reality on the ground in logistics services?

The credit rate is structurally high. Breakage in storage, order preparation error, inventory discrepancy, transport dispute, service billed twice during a peak in activity, year-end discount, retroactive price adjustment.

With the reform, each of these assets becomes:

• A structured document, with mandatory reference to the original invoice
• A feed to be transmitted to the Approved Platform
• E-reporting data submitted to the administration
• An event tracked in the lifecycle

The real risk: a company that currently manages its assets manually, in a spreadsheet, with approximate references, will end up with a massive rejection rate. And a rejected asset means incorrectly declared VAT.

WMS Integration ↔ Approved Platform: The Architecture That Makes the Difference

Why the WMS is the real starting point for invoicing

Let's look at the value chain from the other direction.

A compliant electronic invoice is a structured XML file containing valued lines. Each valued line represents a quantity × a price. The quantity comes from a physical transaction. The price comes from a contract.

Where does the physical operation reside? In the warehouse management software. Where does the contract reside? In the pricing repository, which, in a well-organized 3PL, also resides in the WMS.

Conclusion: your WMS is your primary invoicing system. Not your accounting system.

The target diagram looks like this:

WMS (work units + rates) → Pre-invoicing → Customer validation → ERP/Accounting (accounting document) → Approved Platform (Factur-X format) → PPF (tax data) → Customer

Each arrow represents an interface to be designed, tested, and monitored. And each broken arrow means a blocked invoice.

PRESTLOG from the EGO WMS: Supplier invoicing natively integrated into the WMS

At SITACI, we approached this subject from a business perspective, not a tax one. Because our teams are first and foremost logistics experts before they are IT specialists. It's been in our DNA since 1987.

The PRESTLOG module of our EGO WMS solution precisely addresses this issue: automatically transforming operational activity into billing elements .

The principle is simple:

• Every event in the logistics flow can be valued. A receipt, a stocking, a movement, a picking, a co-packing operation, a location occupancy: everything is automatically counted at the source, without re-entry.
• The pricing framework is multi-client and multi-contract. A 3PL provider rarely manages two clients with the same pricing structure. Sliding scales, deductibles, minimum billing amounts, seasonal rates, flat fees: the contractual modeling is integrated.
• The units of work are configurable according to the business. Pallet/day, m²/month, prepared package, order line, UVC, handling unit, movement, referenced SKU: you invoice as you have sold.
• The pre-invoice is generated automatically. A detailed, line-by-line verifiable statement is provided, which can be exported and sent to the client for validation before issuance.

Tax data is therefore no longer reconstructed after the fact. It is produced in real time by the operation.

A multi-site logistics provider switching from Excel-based invoicing to the EGO WMS with PRESTLOG typically sees its invoicing cycle reduced from 3 weeks to 3 days. This is simply the elimination of manual data re-entry and consolidation.

EGO: Warehouse management software, with over 580 satisfied customers already!

Discover how they optimized their logistics with the EGO WMS.

The three possible integration architectures

Technical points not to be overlooked in the integration

• Invoice numbering: It must be continuous, chronological, without any breaks in the sequence. If both your WMS and your ERP generate numbers, you're going to run into problems. Decide who's in charge, once and for all.
• Recipient identifier: The electronic invoice relies on the PPF directory, which lists recipients via their SIREN/SIRET number and their platform's routing code. Your customer database must be impeccable: valid SIRET numbers, up-to-date billing addresses, and correctly entered routing codes. This is a database cleanup project that needs to be started now, not in September 2026.
• Lifecycle statuses: Your system must be able to receive and use the statuses reported by the PA (Payment Administration). A rejected invoice should trigger an alert in your workflow, not just sit in an email inbox.
• Legally valid archiving: The storage of electronic invoices is subject to specific requirements (duration, integrity, readability, retrieval). Check what your insurance policy covers and what remains your responsibility.
• Degraded mode. What happens if your payment processing system is unavailable for 48 hours at the end of the month, when you're issuing 4,000 invoices? Ask your provider, demand a written SLA.

Choosing your Approved Platform: Logistics-specific criteria

What generic comparisons won't tell you

The market includes several dozen Approved Platforms registered by the DGFiP. Comparisons abound, often based on generic criteria: price per document, interface, standard ERP connectors.

In short, insufficient criteria for a logistics or transport company.

Here are the topics you need to discuss with platform providers.

Regarding volume and seasonality: Does your business experience massive peaks in activity? Black Friday, Christmas, sales, back-to-school season? An e-commerce merchant can multiply their invoice volume by 5 in November. Does your payment processor charge a flat fee, per tier, or per unit? Are there any penalty thresholds?

Regarding multi-line invoices: A 3PL invoice can contain 200, 500, or sometimes 2,000 lines. Some platforms apply technical limitations or charge extra beyond a certain threshold. Check beforehand.

Regarding attachments: Can you attach the detailed summary, the signed delivery note, and the work unit table? In what format, and with what file size limit?

Regarding international operations: Do you operate in Europe? Do you have intra-EU trade flows, international transport, or clients located outside of France? These flows fall under e-reporting, not electronic invoicing. Does your payment processing system (PA) handle both? Is it interoperable with networks like Peppol for your European transactions?

Regarding business connectors: Has your PA already integrated WMS or TMS software? Or will you be the guinea pig? The provider's sector experience has a significant impact on the project's time and cost.

Regarding dispute management: Is the rejection, follow-up, and reconciliation workflow usable by your sales administration teams, or is an accountant required for each action?

The specific case of transport and musculoskeletal disorders

If you operate a transport business in addition to your warehousing (a common case among 3PLs) you have an additional layer of complexity.

Transport invoicing has its own specificities: waybills, diesel indexation, surcharges, specific taxes, rebilling to the sender or recipient, groupage, cascading subcontracting.

A transport management system (TMS logistics) allows for the automatic generation of pre-invoicing for transport based on executed orders. Here again, the logic is identical to that of a WMS: execution data feeds into the tax data.

Transport industry players have largely anticipated this issue, with solutions dedicated to automating invoicing based on operational data. The message is clear: electronic invoicing is not an accounting project, it's an operational project.

If you have both a WMS and a TMS, consider the question of orchestration: who consolidates? Who issues? How do you manage a mixed warehousing + transport invoice for the same customer?

Successfully implementing an electronic invoicing project: A step-by-step guide for logistics departments

Here is the battle plan, organized by time horizon. Adapt the pace to your situation, but don't skip any steps.

Block 1: Diagnosis and framing (immediate)

• Appoint an operational project manager
• Assemble a mixed team: CFO, CIO, logistics management, sales administration, operations
• Determine your company category (Large Company / Mid-Sized Company / Small and Medium-Sized Enterprise) and therefore your mandatory issuance date
• Map all your billing flows: customers, suppliers, intra-group, international, B2C
• Identify your e-reporting flows (excluding domestic B2B)
• Analyze your volumes: number of invoices/month, average number of lines, seasonal peak
• Audit your customer database: valid SIRET number rates, completeness of addresses
• Measure your BL/invoice discrepancy rate and your current credit ratio

Block 2: Structuring choices (within 4 to 6 weeks)

• Select your Approved Platform (logistics criteria grid above)
• Choosing the architecture: WMS→PA direct, or WMS→ERP→PA
• Choose the target format(s) (Factur-X as a priority, UBL/CII if required by your clients)
• Validate your WMS software's ability to produce detailed billing information
• If necessary, begin the project to modernize your service provider billing tool
• Budgeting: PA licenses, interface development, change management, training

Block 3: Operational reliability (in parallel, priority)

• Systematize scanned traceability of incoming and outgoing goods
• Codify the reasons for discrepancies and disputes using a single nomenclature
• Implement electronic validation of delivery notes on critical flows
• Formalize and configure your multi-client pricing repository in the WMS
• Establish a pre-billing cycle with a contractually agreed dispute period
• Review your general terms and conditions and customer contracts: terms of issuance, dispute, and payment

Block 4: Technical Implementation

• Develop and test the WMS ↔ billing system ↔ PA interfaces
• Perform end-to-end testing on a representative sample (single invoice, multi-line invoice, credit note, special cases)
• Specifically test the credit notes and their linking to the original invoice
• Validate the processing of lifecycle statuses and the rejection workflow
• Verify the archiving compliance
• Test the degraded mode

Block 5: Change Management

• Train the sales administration and accounting teams on the new processes and statuses
• Train the operations teams on the impact of their data entry on billing
• Inform your clients about your switch to electronic invoicing and the terms and conditions
• Inform your suppliers and carriers of your Approved Platform and your routing code
• Implement monitoring: rejection rate, issue delay, DSO, credit rate
• Plan for a reinforced support team during the first two months of the transition

September 2026 will not test your accounting, but your operations

This reform will reveal, without bias, the quality of your information chain. A company whose logistics flow is tracked, whose units of work are measured at the source, and whose pricing framework is structured, will pass this stage painlessly and gain a competitive advantage: faster invoicing, reduced DSO, controlled disputes, and finally visible profitability per customer.

A company that still manages its supplier billing in a spreadsheet will discover, painfully, that rejecting an invoice is no longer a phone conversation but a time-stamped tax event.

And the best entry point isn't your accounting software or your Approved Platform. It's your data warehouse. That's where the data is created. That's where compliance is ensured.

At SITACI, we have been supporting logistics providers, manufacturers and multi-channel SMEs in structuring their flows since 1987.

Our EGO WMS solution, and in particular the PRESTLOG, has been designed to ensure that logistics service billing is reliable and seamless.

Contact us to review your billing maturity. We will assess your ability to produce reliable billing data from your operations.

FAQ: Everything you need to know about electronic invoicing in logistics

Is my logistics SME with 45 employees affected from September 1st, 2026?

Yes, but only partially.

From September 1, 2026, you must be able to receive electronic invoices via an Approved Platform. This obligation is absolute. Without a connection, you simply won't be able to process them.

However, your issuance obligationis postponed to September 1, 2027.

Our advice: don't separate the two projects. Connecting to the receiving end and then starting a new project a year later for the transmission end means paying twice for change management. Address the issue holistically, with a gradual switchover.

Is it mandatory to change the WMS to be compliant?

No. The reform does not place any requirements on your warehouse management software.

However, this is an opportunity to ask yourself the question: Is your current WMS capable of producing detailed, justifiable and exportable billing elements?

Ask yourself these five questions:

• Can I extract, by client and by site, the details of my units of work for the past month without manual reprocessing?
• Is my pricing framework (tiers, deductibles, minimums) configured in the tool?
• Is each billing line item attributable to a time-stamped transaction?
• Are my delivery discrepancies and disputes tracked with a coded reason?
• Can I generate a pre-invoice automatically?

If you answer "no" to three or more questions, the problem is not tax-related, but stems from your WMS solution.

What is the difference between a PDP and an Approved Platform?

It's the same thing. Only the name has changed.

The term PDP (Partner Dematerialization Platform) was officially replaced by Approved Platform (PA) in 2025. You will still encounter the old acronym extensively in documentation, commercial offers and articles published before that date.

Remember the simple formula: your invoices go through a PA. Your tax data arrives at the PPF (Public Billing Portal).

Does my delivery note also need to be electronic?

No, the reform only concerns invoices and credit notes. The delivery note, waybill, preparation slip or receipt are not within the legal scope.

But let's be pragmatic: this is where your rejection rate will be determined.

Without a reliable delivery note that can be linked to the invoice line, you have no evidence to present as proof. This is why we systematically recommend, before implementing an electronic invoicing project:

• Systematic scanning upon receipt and dispatch of goods
• Electronic validation of the delivery note by the driver or the recipient on sensitive shipments
• A traceable technical link between the WMS movement, the delivery note, and the invoice line

Digitizing the delivery note is not mandatory. It is primarily an insurance policy.

How to manage assets in electronic invoicing?

A credit note is legally an invoice. It therefore falls entirely under the obligation: structured format, transmission via Approved Platform, mandatory information and explicit reference to the original invoice.

This is the major point of weakness in logistics, where the ratio of assets is structurally high.

Three actions to take before the switchover:

1. Measure your current asset ratio and identify the three dominant root causes. An asset is almost always a symptom of a lack of upstream traceability.
2. Structure the reference to the original invoice in your tool. A credit note without a valid reference will be rejected.
3. Address complex cases early in the project: partial credit notes, credit notes covering multiple invoices, and year-end credit notes. These are the ones that cause technical acceptance tests to fail.

And the best lever remains preventive: a pre-billing validated by the customer before issuance eliminates the majority of adjustment credits.

Are pro forma invoices subject to this requirement?

No. A pro forma invoice does not establish any debt and does not make any VAT payable. It therefore does not fall within the scope of the electronic invoicing obligation.

You can continue to issue it as a PDF, by email, as you do today.

But in the logistics industry, the pro forma invoice is used in particular to pre-invoice at the end of the month for customer validation.

This last method is your best protection against rejections. The principle: between the 1st and 3rd of the month, send the customer a detailed summary directly from your WMS platform. Give them 48 to 72 hours to dispute it. Then issue the final electronic invoice.

You are therefore discussing discrepancies on a non-tax document.

What budget should be allocated for electronic invoicing?

The cost varies greatly depending on your starting point. Here are the items to budget for:

What happens if I am not compliant by September 1, 2026?

There are two levels of risk, and the second is much more immediate than the first.

The risk of sanctions: The system provides for fines in the event of non-compliance with data issuance and transmission obligations, with annual caps. This risk is real but deferred.

The operational risk: It is immediate and much more significant. Without connection to an Approved Platform by September 1, 2026:

• You can no longer receive invoices from your suppliers and subcontractors subject to the obligation to issue them
• You can no longer exercise your right to deduct VAT on these invoices
• Your major clients, committed to their own compliance efforts, will require your connection as a condition for continuing the relationship

I also run a transport business. Do I need to manage two separate sites?

No, but you have to deal with two kinds of complexity.

Transport invoicing has its own specific characteristics: waybills, fuel indexation, surcharges, taxes, rebilling to the sender or recipient, cascading subcontracting, and groupage. Transport management software (TMS logistics) allows for the automatic generation of pre-invoices from executed orders—exactly the same logic as a WMS for warehousing.

Three questions to resolve in your case:

• Which solution consolidates? If a customer uses warehousing and transportation, do you issue a single invoice or two separate invoices?
• Which numbering solution is used? Only one numbering sequence should be master. WMS, TMS, and ERP cannot generate concurrent numbers.
• Which PA? Check that it handles transport-specific information (reverse charge, exemptions, VAT on debits) and international flows related to e-reporting.

One single project, one single sponsor, one single governance structure. But two sets of functional specifications.

Are my international business flows and B2C sales affected?

They do not fall under electronic invoicing in the strict sense, but undere-reporting — the periodic transmission of transaction data to the administration.

In concrete terms:

Can electronic invoicing really improve my profitability?

Yes, provided that we don't stop at the regulatory minimum.

Three measurable levers:

Cash flow. Elimination of delivery delays, the undeniable starting point for payment deadlines, factual reminders supported by time-stamped statuses. For a €30 million 3PL business, reducing DSO by 10 days frees up approximately €820,000 in cash, enough to finance a mobile robot project (robot link).

The issuance time. A service provider who switches from Excel-based invoicing to invoicing natively generated by their WMS typically reduces their cycle from 3 weeks to 3 days.

Visibility into margins. Once the supply chain is connected, you know the actual profitability per customer, per site, and per logistics flow, as of the 5th of the month. You can then adjust your warehouse management fees to the actual costs per location and identify customers whose slow inventory turnover is tying up your most expensive locations.

Add to that a delayed but strategic benefit: the structured and reliable data you will produce will fuel generative AI and predictive logic use cases arriving on WMS platforms. Without clean data, no AI can predict anything.

This compliance budget is actually the foundation of your logistics performance for the next five years.