Search
Image Pexels.com
Secure your data flows, control evidentiary value, and automate your compliance.
Secure your data flows, control evidentiary value, and automate your compliance.

Electronic invoicing, successful legal archiving, e-reporting and status tracking

Published on 09/10/2026  |  Microsoft Business Central  |  Post read 596 times  |  Read in 5,82 Mn  | Article 2 of 2  | Electronic Invoicing

Index toggle


On the previous post allowed us to establish the regulatory framework for the 2026 reform, anticipate the deployment schedule, and detail the preparation of reference data in Microsoft Dynamics 365 Business Central. However, compliance is not limited to simply transmitting a structured file in Factur-X or PEPPOL format.

To secure the organization from a legal standpoint and meet tax requirements, two complementary areas must be mastered: legally valid archiving and data lifecycle management through e-reporting and monitoring of statuses.

Tax archiving vs. legally admissible archiving: understanding the issues

A common misconception is that storing an invoice digitally in an ERP system or via the Public Billing Portal (PPF) is sufficient to guarantee its legal validity. Legal requirements impose a clear distinction between tax retention and archiving with probative value.

The limitations of the Public Billing Portal

The free service offered by the government ensures the retention of mandatory data for ten years to meet tax audit requirements. However, its scope has limitations for businesses:

  • Limited scope of documentation:The PPF focuses its storage on the structured data of the invoice. It does not systematically integrate the contextual attachments (quotes, purchase orders, time sheets) necessary for the Reliable Audit Trail (PAF).
  • Targeted legal scope:The archiving of the PPF is designed for the tax administration, but proves insufficient in a commercial dispute before a civil court, where the evidence must meet strict criteria.

The four pillars of probative value

For a digitized document to retain its probative value throughout its retention period (six years for tax purposes, ten years for commercial purposes), the archiving system must comply with the NF Z42-013 standard. This standard is based on four fundamental requirements:

  • Authenticity:The issuer of the document must be irrefutably identified, usually by means of a qualified electronic signature or an organizational seal.
  • Integrity:The system must guarantee that no changes have been made to the document since its creation. Any attempt to update it must be blocked and logged.
  • Readability:The readability of the file must be ensured over time, which validates the use of long-lasting and hybrid formats such as Factur-X.
  • Traceability:An unalterable audit log must record all operations associated with the document (consultation, export, attempted access).

The positioning of stakeholders, PDPs and Digitalization Operators

Within the Business Central ecosystem, the chosen architecture determines the level of legal coverage:

  • Partner Digitalization Platforms (PDPs):Certified by the DGFiP and often qualified ISO/IEC 27001 or SecNumCloud, PDPs natively integrate electronic safes that meet the NF Z42-013 standard. They ensure the sealing and autonomous archiving of flows.
  • The Digitalization Operators (DOs):Integrated solutions within the ERP system provide reliable technical storage linked to accounting entries. While this level of monitoring meets daily management needs, it must be combined with a Disaster Recovery Plan (DRP) or a certified third-party archiving service to ensure absolute legal validity for the stored documents.

The invoice lifecycle and status management

The reform introduces continuous two-way communication between the ERP, the document management platform, and the invoice recipient. Invoice management no longer ends with simple accounting; it follows a lifecycle characterized by mandatory and recommended statuses.

Mandatory processing statuses

Each invoice issued or received changes according to several statuses transmitted in real time to the tax authorities:

  • Filed:The invoice is handled by the issuer's platform.
  • Rejected:The document has a structural or mandatory data anomaly (missing SIRET number, VAT calculation error) and is rejected by the platform before distribution.
  • Refused:The recipient disputes the invoice for commercial or operational reasons.
  • Cashed in:The payment has been recorded, triggering the VAT liability for the services provided.

Integration of statuses into Business Central

The ERP system must capture these status changes to provide clear visibility to accounting teams. Thanks to PDP connectors, status changes are automatically imported into Business Central worksheets.

A statusDeniedgenerates an alert on the relevant sales document, preventing any undue lettering and guiding the user towards the creation of a corrective credit note.

E-Reporting covers the entire tax scope

Yes, theE-Invoicinggoverns domestic B2B transactions between companies subject to VAT in France, theE-Reportingcompletes the system by requiring the transmission of data for flows outside the scope of direct electronic invoicing.

Operations covered by E-Reporting

The company must transmit to the tax authorities data relating to three categories of transactions:

  • B2C transactions:Sales to individuals, accountants or retail.
  • International B2B transactions:Sales and purchases made with partners located outside of France (European Union and third parties).
  • Cash receipt data:For services subject to VAT on cash receipts, the date and amount of payments received must be transmitted.

Automated processing within the ERP

Business Central centralizes this information when entering sales and payments:

-Automatic extraction:Accounting entries from B2C sales or large exports are isolated via market accounting groups and VAT categories.
-Periodic transmission:The ERP groups these entries and generates the structured e-reporting flow to the PDP according to the frequency defined by the administration (decadally or monthly depending on the tax regime).
-Monitoring of cash receipts:During the execution of bank reconciliation and the matching of customer payments to service invoices, the triggering event for e-reporting of receipt is automatically recorded.

Managing lettering and unlettering errors in E-Reporting

In accounting practice, payment reallocations occur regularly, for example, when a customer payment has been mistakenly applied to the wrong invoice. Regarding e-reporting, the tax authorities do not allow direct modification of a previously submitted transaction; they require processing based on real-time adjustments.

When a delettering and then relettering operation is performed in Business Central:

  • Cancellation of the initial payment:The ERP system automatically generates a negative adjusting entry (reversal entry) linked to the identifier of the first invoice. This entry is transmitted during the following payment period to cancel the VAT collection previously incorrectly declared on that document.
  • Declaration of the new cash receipt:The ERP system simultaneously generates a positive cash receipt linked to the second invoice number (the invoice actually paid). VAT then becomes due on this invoice.[NT]If the unbundling and rebundling occur during the same reporting period, the flows are directly offset in the mailing. If the correction occurs in a subsequent tax period, the negative adjustment regularizes the current fiscal year, guaranteeing perfect tax neutrality and flawless traceability.

The Reliable Audit Trail in the Digital Age

Despite the widespread adoption of structured formats, the Reliable Audit Trail (PAF) remains a cross-cutting legal requirement. It mandates documenting and proving the unbroken link between the initial commercial transaction (quote, order), the logistics flow (delivery note, receipt), and the final accounting entry.

Within Business Central, this continuity is natively ensured by the traceability functions (functionalityNavigateorFinding writings). Associated with the changelog (Change Log), which records any alteration of reference data or third-party records, the organization has a controlled environment, capable of demonstrating the regularity of its operations during any tax control or independent audit.

In summary

Compliance with the 2026 reform should not be approached as a mere technical constraint of file formatting. Combining an ERP like Business Central with a legally compliant archiving architecture and a status management module transforms this obligation into an opportunity to clean up master data, secure debt collection processes, and automate all of the company's financial flows.

Virgile Petrantoni
Help the blogger by rating this post:
vote 1 vote 2 vote 3 vote 4 vote 5
Comments

No comments yet.

Feel like commenting on this article? sign up, it's free!


Other posts
#Accounting entries file (FEC) in Business Central

Generating the FEC in Business Central: usage, planning, and field mapping

This article explains how to pilot an FEC export from the Audit File Export Doc. Card page, how background processing scheduling works, and how each of the eighteen regulatory FEC fields is built from Business Central data.

Calendar Icon  Published on 10/18/2026 | 
Microsoft Business Central | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
Does an ERP translate a regulatory obligation into a software functionality?

The Audit File Export module in Business Central: architecture and configuration

This article presents the architecture of the Audit File Export module of Business Central, its pivot objects, the extension mechanism by interface, then the configuration common to all formats before detailing the specificities of SAF-T and FEC.

Calendar Icon  Published on 10/04/2026 | 
Microsoft Business Central | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
Avoiding customs complexities

Declaration of Exchange of Goods, setup and execution in Business Central

This guide details the configuration and execution of the Intrastat declaration (DEB/EMEBI) in Microsoft Business Central. It covers the setup of reference data (bills of materials, countries, third-party records, and items), audit rules via the checklist, and the monthly workflow: extracting entries, checking for errors, and generating the XML file.

Calendar Icon  Published on 09/13/2026 | 
Microsoft Business Central | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
AI no longer just responds, but executes your processes from end to end

The architecture of AI agents in Business Central, understanding the pivotal role of the MCP server

Integrating agentic AI into Microsoft Dynamics 365 Business Central is transforming the ERP. Thanks to the standardized Model Context Protocol (MCP), AI agents become autonomous collaborators capable of executing end-to-end business processes. Discover a secure, three-part architecture where humans retain control over every accounting transaction.

Calendar Icon  Published on 05/31/2026 | 
Microsoft Business Central | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off