Numbering

Vavang Invoice does not introduce a second competing numbering sequence. The invoice number consumed by the compliance pipeline comes from the source Sylius InvoicingPlugin invoice.

The Factur-X generator maps that number from the immutable invoice representation; it does not renumber the document during export or transmission.

Integration consequence

The source invoice numbering strategy must therefore be validated in the Sylius/InvoicingPlugin application before enabling Vavang compliance flows.

A historical invoice that has already been issued must not be mutated merely to repair current configuration. Accounting corrections must follow the legal and functional workflow appropriate to the project.

This page documents Vavang’s responsibility boundary; source numbering options belong to the upstream invoicing engine and are not invented in sylius_invoice.yaml.

Customization boundary

There is currently no Vavang numbering interface, service alias or sylius_invoice.* numbering strategy to decorate. Do not derive an integration from an internal Vavang class in order to renumber invoices.

If the project needs a different invoice-number format or sequence, configure or extend the source Sylius InvoicingPlugin numbering mechanism before the invoice reaches Vavang Invoice. The compliance layer must consume the number already assigned to the source invoice.

This separation is intentional: allowing the compliance layer to assign another number would risk a divergence between the business invoice, its immutable fiscal snapshot and the generated Factur-X document.