Maintenance and key considerations for FEC exports in Business Central

The two previous articles covered the architecture of the Audit File Export module, its configuration, and its daily use: map control, processing planning, and mapping of the eighteen regulatory fields of the FEC. One last, less visible but equally crucial aspect remains: the necessary permissions, the troubleshooting process, and, above all, the module's structural limitations—those that no official documentation explicitly mentions.

The necessary permissions

Each module extension exposes its own set of permissions. The core Audit File Export module provides access to common tables and pages (export header and rows, settings, account mapping) as well as the codeunits that control the processing. The FEC extension adds a restricted set of permissions, limited to the codeunits that verify and generate the file. These permissions are not granted by default: a user must have a role that grants them, either directly or via extensions provided to standard Business Central roles, to create and execute an export. A common oversight during deployment is to validate the settings with an administrator account, only to discover that end users do not have access to the map.

Diagnosing a failure

Three scenarios recur regularly.

• Unauthorized scheduling: A message indicates that the environment does not allow the creation of background tasks. The solution is to disable parallel processing and launch the export synchronously.
• Line blocked with no progress: most often indicates a lost server session. The module detects and automatically restarts the session in the next cycle; if this fails, manually restarting the affected line resolves the issue.
• Immediate failure at startup, specific to FEC: generally stems from two causes, either the SIREN number is not entered in the company information, or no entry corresponds to the period or account filter defined on the document.

In both cases, the activity log associated with the export line gives the exact details of the error, which is preferable to any assumption.

Purge and version upgrade

The generated files, such as the content of the processing lines, remain stored in the database until the export document is deleted. Over a full fiscal year, this can result in a significant volume of data.

A periodic review of obsolete documents, followed by their deletion, helps to contain the growth of the database: deleting a document first cancels ongoing tasks and then deletes associated lines and files.

Regarding version upgrades, SAF-T has a data update interface that detects changes in the structure of the standardized account repository and offers a guided migration.

Limitations to be aware of before considering an export as reliable

Three points deserve special attention, none of which are obvious to a user discovering the module.

The level of control

SAF-T includes a complete data control, which checks the completeness of customer, supplier, bank account records, and VAT settings before any export.

The FEC (File of Accounting Entries) has no equivalent: its preliminary verification is limited to period dates and the presence of the SIREN number. The quality of account and journal descriptions, their conformity to the French language, and the absence of mass transcoding (all requirements of the BOFIP (French Official Tax Bulletin) detailed in the first article of this series) are never checked by the module. This responsibility remains entirely with the person preparing the export.

The account filter

The account filter available on the FEC document applies in the same way to the calculation of opening balances and to the entries of the period.
Used indiscriminately, it can produce a file where the total debits no longer match the total credits, if certain counterparties are excluded from the exported scope. An unbalanced file will fail the first technical test of an analysis tool like Alto. This filter benefits from being documented and tested before any production use.

The accompanying description

The module never generates it, whereas its absence alone constitutes a non-compliance within the meaning of the BOFIP.
The conventions specific to the Business Central implementation (unique entry number set to zero for opening balances, conventional value for multi-tier transactions, correspondence between ValidDate and the creation date of the entry batch rather than a separate business validation) must all be included in this separately written document, otherwise they will appear as anomalies to an auditor who does not know their origin.

One final observation, common to the entire series: the module faithfully translates the data already present in Business Central into a file conforming to the technical specifications of the FEC.
It does not replace the quality of upstream accounting practices, the drafting of the accompanying description, or a human review before submission to the auditor. This division of responsibilities between the tool and the user aptly summarizes the key takeaways from this series of articles.