An ERP centralizes a company’s information flows in a single system: accounting, purchasing, inventory, production, and human resources. Preparing a management file around this tool means gathering specific documents, while also distinguishing between those generated by the software and those the company must produce itself. This distinction becomes particularly important with the gradual introduction of mandatory electronic invoicing, which requires businesses to retain and transmit documents in standardized formats.
Documents generated by the ERP and documents required for electronic invoicing
A well-configured ERP automatically generates some of the documents needed for day-to-day management: sales invoices, purchase orders, delivery notes, accounting entries, and reconciliation statements. These documents feed into the internal management file and provide the basis for tax returns.
Electronic invoicing adds a separate set of requirements. The company must transmit its invoices through an approved partner dematerialization platform and retain the structured data (Factur-X, UBL, or CII format) for the legally required period. The ERP can generate these files, provided its invoicing module is compatible with the accepted formats.
A common misconception is that the ERP covers the entire process. In practice, some documents still need to be prepared manually or using additional tools: mandatory invoice details (SIREN number, registered office address, and, where applicable, the statement “VAT not applicable”), software compliance certificates, and certificates from the chosen platform. Putting together an effective management file therefore means mapping out what the ERP does and does not generate.

ERP specifications: documents to gather before deployment
The specifications document forms the project’s documentary foundation. It is not simply a list of desired features, but a document that commits the company in its dealings with the implementation partner.
Technical content of the specifications
A robust specifications document includes three distinct sections:
- A description of existing business processes, including data flows between departments (accounting to purchasing, production to logistics). Each flow should identify the documents currently used, including informal spreadsheets.
- Functional requirements ranked by priority: real-time inventory management, tracking supplier invoices payable, and automatic generation of VAT entries. Each requirement specifies the expected output format (PDF, XML, CSV).
- Integration constraints involving existing tools: payroll software, tax dematerialization platform, and CRM tool. These constraints determine which connectors are needed and, consequently, which interface documents must be prepared.
This specifications document also serves as a contractual reference. If a delivered module does not match what was described, this is the document that settles the matter.
Frequently overlooked supporting documents
In addition to the specifications themselves, the project file should include a map of user access rights. Who approves a purchase order, who issues an invoice, and who can view margins? These permissions determine how the ERP is configured and help ensure compliance with internal control rules.
The historical data migration plan should also be part of the file. Transferring accounting balances, product records, and outstanding customer invoices from the old system requires a field-by-field mapping document. Without it, data migration can create discrepancies that are difficult to correct after go-live.
Day-to-day management file: what the ERP should archive
Once the ERP has been deployed, the management file is no longer limited to project documents. It includes all the documents generated by the system and retained by the company to meet its legal obligations and support internal management.
Accounting journals generated by the ERP (sales journal, purchases journal, and cash journal) must be exportable in a tamper-proof format and retained for the entire applicable statutory period.
Purchase orders and delivery notes retain their evidentiary value even when stored electronically. An ERP that cannot retrieve a signed delivery note three years after the transaction exposes the company to risk in the event of a supplier dispute.
The management dashboard, generated periodically by the ERP (monthly or weekly, depending on the company), is a management tool. It aggregates data from several modules: revenue, gross margin, average customer payment time, and inventory turnover rate. This dashboard does not replace supporting documents, but it flags anomalies that require the source documents to be checked.

Electronic invoicing: documents the ERP alone cannot generate
The requirement for electronic invoicing between businesses liable for VAT changes the nature of the management file. Three categories of documents deserve particular attention.
Invoices in a structured format (Factur-X, UBL, CII) must include standardized details that the ERP can populate correctly only if it has been configured in advance: the customer’s SIREN number, VAT category code, and contract reference. Incomplete configuration results in invoices being rejected by the platform.
The invoice lifecycle (issuance, receipt, acceptance, rejection, payment) must be tracked. The ERP records part of this lifecycle, but statuses returned by the dematerialization platform must be fed back into the system. The lifecycle tracking document is therefore a hybrid record, produced jointly by the ERP and the platform.
Transmission reports (acknowledgments of receipt and rejection notifications) issued by the approved platform are not generated by the ERP. They must be archived separately or imported into the system. If they are missing, this can cause problems during a tax audit, as they prove that the invoice was transmitted on time.
Preparing an effective management file around an ERP means documenting every stage of the project, from the initial specifications to the archiving of day-to-day records, without overlooking documents the software cannot generate on its own. Electronic invoicing requirements make this even more important: a complete file brings together ERP outputs, documents from the dematerialization platform, and configuration records that demonstrate the system’s compliance.



