Spanish companies running ERPNext hit a hard wall the moment invoicing compliance stops being optional. The Verifactu regime under the Anti-Fraud Law (Ley Antifraude, RD 1007/2023) requires billing software to generate tamper-evident, chained, hash-signed invoice records — and the phased B2B e-invoicing mandate (Ley Crea y Crece) will require structured Facturae exchange between businesses. ERPNext core produces a clean Sales Invoice, but it has no concept of a Verifactu registro de facturación, no invoice-record hash chain, no Facturae 3.2.x XML export, no TicketBAI flow for the Basque foral territories, and no connection to the AEAT web services. Bolting this on with ad-hoc report exports is exactly the kind of manual, unauditable process the law is designed to eliminate.

ECOSIRE builds a proper Frappe app — not a spreadsheet macro or a one-off script — that installs cleanly alongside ERPNext and owns the entire Spanish compliance surface. We add a Verifactu Invoice Record DocType that captures the mandated fields (issuer NIF, invoice series and number, issue timestamp, tax breakdown, previous-record hash and current SHA-256 fingerprint) so every submitted Sales Invoice produces an immutable, chained record. hooks.py document events (on_submit, on_cancel) fire server scripts that build the record, compute the chained hash, and stamp the invoice — so compliance happens automatically at submit time, not as an afterthought. A Facturae Export module generates signed Facturae 3.2.x XML (XAdES) for B2B counterparties, and where the customer operates in Álava, Bizkaia or Gipuzkoa, the TicketBAI variant produces the province-specific chained XML and QR/TBAI identifiers required by the foral haciendas.

Submission is wired to the tax authority, not left to manual upload. Scheduler events poll a submission queue and push records to the AEAT Verifactu web service (or the relevant provincial TicketBAI endpoint) with certificate-based authentication, then write the acknowledgement, CSV/response code and any rejection reasons back onto the record. Whitelisted methods exposed through the Frappe REST API let your other systems trigger generation or re-submission programmatically, while dedicated role profiles and DocType permissions keep certificate handling and AEAT submission scoped to the finance and compliance roles that should own it. Client scripts add the practical touches — a compliance status indicator on the Sales Invoice, a one-click "view Verifactu record", and validation that blocks submission when NIF, tax codes or series configuration are incomplete.

Because this is build-to-order, nothing ships until we have agreed your scope. We start with a short scoping call to confirm your ERPNext version (v15 or v16), which regimes apply (national Verifactu, Facturae B2B, and/or one or more TicketBAI provinces), your invoice series design, and your AEAT/foral certificate setup. From confirmed scope, typical delivery is one working week: we build on a staging copy of your site, run UAT against real invoice scenarios and the AEAT test environment, then install to production with a rollback plan. You receive the full source, a git repository handover, documentation and a training session — and a post-go-live support window so the first real filing period is covered.