Compliance

Vavang Invoice adds a compliance pipeline around Sylius InvoicingPlugin based on frozen fiscal data. It provides technical controls and transmission workflows; it does not determine a merchant's legal or tax position.

What the plugin does

For a compatible invoice, the flow is:

1. read the Sylius invoice;
2. create or reuse the immutable fiscal snapshot;
3. build the electronic-invoice model;
4. validate the business rules implemented by the plugin;
5. retrieve the source PDF;
6. generate EN16931 Factur-X;
7. store XML and PDF artifacts with checksums;
8. validate the electronic document;
9. record business-journal events;
10. transmit when the configured mode and connector allow it.

These controls help enforce the invariants implemented by the plugin. They are not a certification that every invoice is legally correct for every merchant, transaction or territory.

French e-invoicing reform

As checked against the French tax administration on 21 August 2026, the reform is being introduced in two stages:

• 1 September 2026: every business in scope must be able to receive electronic invoices; large companies and mid-sized companies must also issue electronic invoices and transmit the required e-reporting data;
• 1 September 2027: SMEs and micro-businesses must also issue electronic invoices and transmit the required e-reporting data.

Domestic B2B e-invoicing generally concerns supplies between businesses established in France and subject to French VAT. B2C transactions and transactions involving operators established abroad generally fall into e-reporting rather than the domestic B2B e-invoicing flow.

Official references:

• French tax administration — scope of electronic invoicing
• French tax administration — implementation dates

Regulatory rules evolve independently of plugin releases. Re-check the official sources before a production rollout or after a regulatory change.

Overseas France

Territorial treatment must not be inferred from the word "France" alone.

The French tax administration currently distinguishes notably:

• Guadeloupe, Martinique and La Réunion: VAT applies and transactions can fall within the French e-invoicing reform, subject to the transaction and parties;
• Guyane and Mayotte: VAT is not currently applicable there, so businesses established there are in principle outside the domestic e-invoicing scope; e-reporting can nevertheless apply to operations covered by the applicable rules;
• COM and TAAF: do not assume domestic B2B e-invoicing applies; the transaction can instead be outside scope or subject to e-reporting depending on the parties and operation.

Use the current DGFiP DOM/COM guidance for the actual merchant case: Overseas electronic-invoicing FAQ.

The plugin does not automatically qualify a company or transaction into one of these legal cases.

Responsibility boundary

The plugin guarantees only what it implements

Within a supported version and documented configuration, the plugin is responsible for its own technical behavior: frozen fiscal data, implemented validation rules, generated artifacts, checksums, audit records, connector calls and state transitions.

The plugin facilitates, but does not decide

The plugin can facilitate Factur-X generation, diagnostics, connector transmission and auditability. It does not decide:

• whether a merchant or transaction is in e-invoicing or e-reporting scope;
• the merchant's VAT regime, VAT due date or territorial treatment;
• whether an exemption, special tax treatment or accounting rule applies;
• which platform/provider contract the merchant must hold;
• the correctness of project-specific customizations or data supplied by the host application.

Those decisions remain the merchant's responsibility, with qualified accounting, tax or legal advice where appropriate.

MANUAL by default

The safe starting configuration remains:

sylius_invoice:
    transmission:
        mode: MANUAL

Before enabling automatic transmission, run:

bin/console sylius-invoice:check-requirements
bin/console sylius-invoice:compliance:doctor

A blocking diagnostic must be resolved before activation. Connector-specific prerequisites must also be validated before production transmission.