<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
Statutory and fiscal reporting — on every country's regulatory calendar.
SII, TicketBAI, Verifactu, modelo 347 / 349 in Spain; SUNAT libros electrónicos and PLE in Peru; DIAN factura electrónica in Colombia. The reporting engine generates each output in the regime's format, on the regime's calendar, against the live transactional ledger.
Real-time submissions
SII, TicketBAI and Verifactu submitted as transactions post — not as a batch on a deadline that fails when the network is unavailable.
Periodic declarations
Modelo 347 / 349, libros electrónicos, declaración jurada — generated against the live ledger on the regime's calendar, with the format the regime mandates.
E-invoicing channels
FACe, FACeB2B and PEPPOL in Spain; SUNAT CPE channels in Peru; DIAN PAC integration in Colombia. The right channel per buyer / per regime.
Submission audit
Every submission tracked with status (accepted, rejected, pending). Rejections routed to the controller; the original transaction is preserved with the rejection reason.
What the regulatory surface covers
Spain — SII / TicketBAI / Verifactu
Real-time invoice reporting to AEAT. TicketBAI signing in the Basque Country with the regional variation handling. Verifactu where applicable.
Spain — periodic declarations
Modelo 347 (operations > €3,005.06 per counterparty), modelo 349 (intra-EU operations), modelo 303 / 390 (VAT) — generated from the live ledger.
Peru — SUNAT
CPE (boletas, facturas, notas, comprobantes), libros electrónicos via PLE, PLAME for payroll, declaración jurada anual.
Colombia — DIAN
Factura electrónica with PAC integration, RUT integration, IVA periodic returns, retenciones reporting.
Extensible regimes
Additional country regimes (Pakistan FBR, broader LATAM) engineered as commercial demand warrants. The engine pattern is the same; the format and calendar are the variation.
Submission tracking
Every regime submission tracked. Acceptance, rejection, retry. The compliance team works against a live dashboard, not against an end-of-month panic.
Why the regulatory engine is the engine, not a partner pack
The traditional model for multi-country compliance is the localisation partner — a third party that maintains country-specific modules on a different cadence than the core ERP. The model works in theory; in practice, regulations change faster than partner releases, and the customer's compliance posture lags.
Axional implements country compliance in the engine itself. SII, TicketBAI, Verifactu, SUNAT and DIAN are behaviours the engine performs. When a regulation changes, the engineers who own the engine deliver the change. The customer's deployment inherits it through the same release process as any other capability — no partner-pack lag.