Rules to know & limitations

Rules to know

• A Deposit always corresponds to a full period, never to a single invoice.

• Flows 10.1 and 10.3 always share the same file and the same period; flows 10.2 and 10.4 form a separate file.

• The date that assigns an invoice to a period is the invoice date (flows 10.1/10.3) or the payment date (flows 10.2/10.4) — never the date the report is generated.

• Generation for the current period (Flow or batch) and corrections correctly filter by Company: two entities with the same scheme, and therefore the same calculated period, never mix their invoices. Only manual generation for an explicit period applies across all entities — only use it if a single Company has invoices for the targeted period.

• The transmission ID always carries a flow marker (TXN for transaction data, PAY for payment data), ensuring that Transaction data and Payment data for the same period never share the same identifier.

• An entity configured with the VAT chargeable event on invoicing never generates flows 10.2/10.4, regardless of its payments — this is not a bug.

Known limitations

"All or nothing" correction

A correction always regenerates the entire period — there is no fix targeted at a single invoice.

Foreign currencies (B2C)

For flow 10.3, the actual currency of each invoice is displayed, but VAT amounts are not converted to euros for transactions in a foreign currency. This has no impact as long as your invoicing remains exclusively in euros.