Once your invoices and your Company are configured, the generation of Transaction data (flows 10.1 and 10.3) can happen automatically or, on an ad hoc basis, for a specific period.
To visualize how your data is linked together before generation, here is the simplified data model (objects and field names) that feeds this flow:
Automatic generation
In practice, every day, a scheduled automation triggers a check for your Company:
The configured VAT scheme is read, along with today's date.
If today's date does not exactly match a filing deadline for that scheme, nothing happens.
If today's date matches a deadline, the eligible invoices for the relevant period are retrieved.
If at least one eligible invoice exists, the XML file is generated and a Deposit is created.
Two equivalent mechanisms enable this automation:
A Flow scheduled per Company, which calls the Generate e-reporting XML for the current period action. This action protects itself: it can and should be called every day, and it does nothing on days that are not filing dates.
A scheduled Apex batch covering all entities (useful if you report for several Companies): a single job processes every entity with a configured VAT scheme each day. If generation fails for one entity (for example, an invalid SIREN), the other entities in the same batch are still processed, and the error is logged without blocking the rest. At the end of the run, a notification (and an email in case of error) indicates the exact number of files generated.
No blank filing
If no invoice matches the period on the filing date, nothing is generated — no file, no Deposit. This is the intended behavior: e-reporting does not require an empty declaration.
No duplicate protection
Neither the Flow nor the batch checks whether a Deposit has already been generated for the same period and the same entity. If the automation triggers twice on the same day, two Deposits will be created for the same period. Make sure your scheduling only runs once a day.
Manual generation for a specific period
To replay or test a specific period outside of the automatic schedule, you need to create a Salesforce workflow that calls the “Generate e-reporting XML for period” action, then specify a start date and an end date to run your workflow.
⚠️ This explicit-period entry point applies across all reporting entities: only use it if a single Company has invoices for the targeted period, to avoid mixing data from several entities.