French and German finance teams are moving toward hybrid e-invoicing mandates where a human-readable PDF and a machine-readable XML must live in the same file. ERPNext core produces a print-format PDF and can attach files, but it does not emit a PDF/A-3 with a conformant Factur-X / ZUGFeRD XML embedded to the EN16931 semantic model, and it has no path to read an inbound hybrid invoice back into a Purchase Invoice. That gap is where teams fall back to spreadsheets, a third-party portal, or manual re-keying — exactly the friction the France 2026 reform and the German B2B rollout are designed to remove.

ECOSIRE builds a proper Frappe app (its own module, DocTypes, and hooks.py wiring) that sits on top of your existing Sales Invoice flow. On on_submit of a Sales Invoice, a server-side document event maps ERPNext fields — customer, tax IDs, line items, VAT breakdown, payment terms — into a validated EN16931 dataset, generates the Factur-X / ZUGFeRD XML, and merges it into a PDF/A-3 container built from your existing print format. We support the standard profiles (BASIC, EN16931, and EXTENDED) selectable per company or customer, so you can dial the level of structured detail to what each buyer or authority requires. A configuration DocType holds profile defaults, seller identifiers, and template mappings; a Client Script surfaces validation results directly on the invoice so a booking is never submitted with a broken cross-border VAT number or a missing mandatory field.

Inbound is handled symmetrically. A whitelisted method (exposed over the Frappe REST API) and a scheduler event ingest hybrid PDFs from a monitored source, extract the embedded XML, and draft a Purchase Invoice with supplier, tax, and line data pre-filled for your AP team to review and submit — no re-typing. Multi-language invoice templates (French, German, and English) are driven from the Frappe print-format layer so the same structured XML renders with the right legal wording per recipient. Access is governed with role profiles and DocType permissions so only authorized finance roles can change compliance settings or reprocess documents, and every generation and parse writes to an audit trail.

Because this is build-to-order, nothing ships until we agree scope. We start with a short scoping call, confirm your ERPNext version (v15/v16), entities, profiles, and inbound sources, then build against a copy of your data on staging. You get the installable source, a UAT window on staging with a rollback plan, and a defined post-go-live support period. Typical delivery is one working week from confirmed scope, and the full git repository is handed over to you at the end.