The VeriFactu and e-invoicing module is currently implemented in the UBC core codebase (Level B) undergoing technical validation. We report only verified facts and make no promises of release dates: data schemas and cryptographic hash chaining are built in code; transmission connectors to AEAT and Facturae formats are in active development.
E-invoicing & VeriFactu: honest compliance roadmap
European and Spanish regulations (VeriFactu RD 1007/2023 and the Crea y Crece law) mandate tamper-proof, cryptographically chained invoicing software. In UBC, development is actively progressing: this page provides complete transparency regarding current capabilities and release milestones.
What VeriFactu mandates for SMEs and sole traders
Anti-fraud billing regulations aim to prevent invoice tampering through rigorous technological criteria:
Cryptographic Hash Chaining
Every issued invoice record must contain a hash generated from the preceding record, forming an unbroken cryptographic chain.
Verification QR Code
PDF and printed invoices must include a standardized QR code directing buyers to verify invoice submission on the tax agency portal.
Immutable Audit Logging
The system must record all additions, modifications, and cancellations in a secure, write-only audit trail.
What is built and what is underway in UBC
Honest technical evaluation based on our platform audit criteria:
| Technical Component | Status in UBC | Implementation Notes |
|---|---|---|
| Data schemas & SHA-256 chaining | Completed in code (Level B) | Cryptographic hash chaining implemented strictly following AEAT specifications. |
| VAT & Transaction Accounting Ledger | Level B (working in code, in verification) | VAT rates reconciliation, intra-EU transaction support, and procurement VAT registers. |
| Direct AEAT SOAP Transmission Node | Active development | Direct machine-to-machine SOAP gateway connecting to Spanish tax servers. |
| B2B Structured Invoicing (Facturae) | Under development | Electronic invoice XML generation for inter-enterprise commercial exchange. |
| European Gateways (KSeF / SDI) | Technical research | Unified data models ready for Polish KSeF and Italian SDI integrations. |
Regulatory compliance timeline
Official rollout phases established by tax authorities (Order HAC/1177/2024 and Crea y Crece law):
- Enterprises > €8M turnover
B2B electronic invoicing mandatory 12 months after royal decree finalization under Crea y Crece law.
- SMEs & Sole Proprietors
B2B electronic invoicing mandatory 24 months after final decree gazette.
- VeriFactu Software Enforcement (Order HAC/1177/2024)
For corporate taxpayers: before January 1, 2027. For sole traders and other taxpayers: before July 1, 2027 (official source: BOE No. 260, Order HAC/1177/2024: https://www.boe.es/buscar/act.php?id=BOE-A-2024-22138).
Practical tip
Do not rush into signing expensive multi-year contracts under false urgency claims from legacy ERP vendors. Tax authorities provide phased compliance periods. Choose platforms that treat legal compliance as standard core software rather than an expensive paid add-on.
Frequently asked questions about e-invoicing
Is instant submission to the tax authority mandatory for every invoice?
Under the VeriFactu system, immediate submission is optional but grants presumption of compliance. Non-verifiable systems must preserve signed immutable logs for audit.
Will UBC charge extra fees for VeriFactu compliance?
Today the adaptation is included in the standard subscription; any price change is announced in advance.
Where can technical details and integration progress be reviewed?
Through the UBC contact page, you can reach our engineering team directly regarding architecture and integration status.
Technical contact for VeriFactu
For inquiries regarding immutable ledger architecture, technical compatibility, or integration details: