Typical delivery is roughly one working week from scope sign-off, depending on the complexity of your tax setup, how many profiles (ZUGFeRD / XRechnung / Factur-X) you need, and whether we integrate with Magento's native PDF renderer or a third-party invoice extension. We confirm a concrete timeline in writing before any payment-to-build, and we install on a staging environment first.

Yes. Every build includes a defined post-launch support window and bug-fix period. Because the e-invoicing standards (EN 16931, XRechnung CIUS, Factur-X profiles) evolve as the 2025-2028 mandates phase in, we offer an optional ongoing maintenance arrangement to keep your module aligned with new schema and Schematron versions. We agree the terms up front rather than leaving it open-ended.

No. Magento Open Source and Adobe Commerce produce a plain PDF invoice with no embedded structured XML and no Leitweg-ID or B2G routing fields. There is no native EN 16931 output. That gap is exactly what this module fills.

In most cases, yes. We adapt the embedding logic to your actual PDF pipeline using a plugin or observer rather than assuming the native renderer. If you run a third-party PDF invoice extension, we inspect how it builds the PDF during scoping and wire the PDF/A-3 attachment into that flow. Highly unusual or closed renderers are flagged before build so there are no surprises.

Yes. The module uses standard Magento 2 architecture — di.xml, service contracts, observers/plugins, system.xml and ACL — so it runs on both Magento Open Source and Adobe Commerce, including multi-store and multi-website setups where seller master data differs per store view.

Yes. Each generated document is checked against the EN 16931 XML schema and the relevant Schematron rules before it is attached to the PDF, so malformed invoices are caught inside Magento. Note that we deliver technically conformant ZUGFeRD/XRechnung/Factur-X output; final regulatory and tax acceptance for your specific entity should still be confirmed with your tax advisor.