A build-to-order ERPNext app that turns your Sales Invoices into Factur-X / ZUGFeRD compliant PDF/A-3 documents with embedded EN16931 XML, and parses inbound hybrid invoices into Purchase Invoices. ECOSIRE scopes, builds, installs, and supports it for your French and German entities. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext app that turns your Sales Invoices into Factur-X / ZUGFeRD compliant PDF/A-3 documents with embedded EN16931 XML, and parses inbound hybrid invoices into Purchase Invoices. ECOSIRE scopes, builds, installs, and supports it for your French and German entities.
Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.
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.
Generates Factur-X / ZUGFeRD compliant PDF/A-3 invoices with the XML embedded as an AF (Associated File) per the ISO 19005-3 profile
Maps ERPNext Sales Invoice fields to the EN16931 semantic data model, including VAT breakdown, allowances/charges, and payment terms
Selectable Factur-X profiles — BASIC, EN16931, and EXTENDED — configurable per company or per customer
Inbound Factur-X/ZUGFeRD parser that extracts embedded XML and drafts a ready-to-review Purchase Invoice
`on_submit` document event in `hooks.py` triggers generation without changing your existing invoicing workflow
Whitelisted Frappe REST API method for programmatic generation, re-processing, and inbound ingestion
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 2-4 weeks from confirmed scope, and the full git repository is handed over to you at the end.
Needs outbound invoices that carry structured EN16931 XML inside a PDF/A-3 so the business is ready for e-invoicing and e-reporting obligations without leaving ERPNext or re-keying into a portal.
Receives and sends hybrid invoices with German trading partners and public bodies, and wants inbound ZUGFeRD parsed straight into Purchase Invoices and outbound generated automatically on submit.
Manages multiple companies with different profile requirements and languages, and needs per-company configuration, role-restricted compliance settings, and a consistent audit trail across both jurisdictions.
Owns the ERPNext deployment and wants a clean Frappe app on v15/v16 with proper hooks, permissions, and a git handover rather than brittle customizations bolted onto core.
Compre la licencia en ecosire.com y descargue la aplicación ZIP de Factur-X / ZUGFeRD Hybrid E-Invoicing for ERPNext desde el panel de su cuenta.
Extraiga el ZIP en la carpeta de aplicaciones de su banco o ejecute `bench get-app` con la ruta a la aplicación extraída.
Ejecute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench migrar` para instalar Factur-X / ZUGFeRD Hybrid E-Invoicing for ERPNext y aplicar su esquema.
Abra la configuración de licencia de ECOSIRE en su sitio y active su clave de licencia. Requiere las aplicaciones gratuitas ecosire_connect y ecosire_license_client.
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| Hybrid PDF/A-3 with embedded XML | Built to EN16931, profiles selectable per company/customer | Possible but you own the whole PDF/A-3 + XML pipeline | Often single-profile or PDF-attach only | |
| Inbound Factur-X/ZUGFeRD parsing | Whitelisted method + scheduler drafts Purchase Invoices | Must be designed and built from scratch | Frequently outbound-only | |
| France 2026 reform readiness | EN16931 structure ready to extend to PDP/PPF flows | Depends entirely on your in-house roadmap | Varies; may lag mandate updates | |
| Multi-language templates (FR/DE/EN) | Configured from one structured dataset | Extra build effort per language | Usually limited language coverage | |
| Fit to your ERPNext setup | Scoped to your v15/v16 entities and profiles | Fully bespoke but slow and costly to reach parity | Generic; may need workarounds | |
| Permissions & audit | Role profiles + DocType perms + generation/parse audit log | You implement and maintain it | Depends on the vendor | |
| Delivery & handover | 2-4 wks, staging UAT, rollback plan, full git handover | Timeline and handover depend on your team | Install now, limited customization | |
| Ongoing support | Post-go-live window + quotable upgrades | Your team carries all maintenance | Subscription/support tier dependent |
No. This is a build-to-order product. ECOSIRE scopes it with you, builds it against your ERPNext version and entities, tests it on staging, then installs and supports it. There is no instant download.
Typical delivery is 2-4 weeks from confirmed scope. The exact timeline depends on how many entities, profiles, languages, and inbound sources you need, all of which we lock down during the scoping call before any build starts.
We build to the EN16931 semantic model and support the BASIC, EN16931, and EXTENDED profiles, selectable per company or per customer. We confirm which profiles your buyers and authorities require during scoping.
Yes. A whitelisted Frappe method and a scheduler event extract the embedded XML from inbound Factur-X/ZUGFeRD PDFs and draft a Purchase Invoice with supplier, tax, and line data pre-filled for your AP team to review and submit.
The data structure is built to the EN16931 model that the reform relies on, so the same engine is positioned to extend to PDP/PPF exchange flows as the specifications finalize. We track the mandate and scope any reform-specific work with you explicitly.
Every build includes a defined post-go-live support window for fixes and questions. Because you receive the full git repository, your team can also maintain it, and ECOSIRE can quote ongoing support or upgrades (for example, moving from v15 to v16) separately.
No. It hooks into the standard Sales Invoice `on_submit` document event and reuses your existing print formats, so your team keeps working the way they do today while the compliant PDF/A-3 is generated in the background.
A build-to-order ERPNext app that turns your Sales Invoices into Factur-X / ZUGFeRD compliant PDF/A-3 documents with embedded EN16931 XML, and parses inbound hybrid invoices into Purchase Invoices. ECOSIRE scopes, builds, installs, and supports it for your French and German entities.