Integrations
Vavang Invoice exposes provider connectors through a common platform contract. A connector is documented as available only when the corresponding behavior exists in the plugin repository and is covered by its connector tests.
Current status
| Integration | Status | Current plugin scope |
|---|---|---|
| Qonto | Available | connection checks, Factur-X import, production e-invoice send and lifecycle polling |
| Pennylane | Available | connection checks, Factur-X customer-invoice import, optional PA forwarding and lifecycle polling |
"Available" means the connector is implemented in the current plugin code. It does not mean every feature of the provider API is supported, nor does it replace the merchant's provider contract, onboarding or regulatory qualification.
No integration should be presented as available merely because generic connector infrastructure exists. Future connectors remain planned until their dedicated implementation, tests and documentation are shipped.
Shared safe rollout
For any provider:
- keep
transmission.mode: MANUALinitially; - configure credentials through secret references, never inline secrets;
- validate the provider organization/environment;
- run
bin/console sylius-invoice:platform:test-connection; - run the compliance diagnostics and validate a representative invoice;
- enable provider-specific sending options only after sandbox/pre-production validation;
- enable automatic transmission only when the operational prerequisites are met.
Provider APIs and commercial offerings can change independently of Vavang Invoice. Re-check the provider-specific plugin guide when upgrading.