<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.
Localisation engineered into the engine — not bolted on, not partner-maintained.
Spanish fiscal compliance (SII, TicketBAI, Verifactu, modelo 347 / 349), Peruvian (SUNAT CPE, libros electrónicos, IGV), Colombian (DIAN factura electrónica, RUT, IVA), and an extensible engineering pattern for additional regimes. The fiscal calendar is a release-process input, not a partner-pack dependency.
Spain — deepest
SII, TicketBAI, Verifactu, modelo 347 / 349, convenios, Seguridad Social — the deepest localisation in the family, reflecting the home market.
Peru — production
SUNAT CPE, libros electrónicos, PDT-PLAME, IGV, ESSALUD — in production at customers operating across Peru's fiscal regime.
Extensible
Colombia (DIAN), Pakistan (FBR), broader LATAM and EU regimes — engineered as commercial requirements warrant.
Engine, not bolt-on
Localisation released on the engine's cadence by the engineers who built it. No partner pack, no separate release calendar, no lag.
The four surfaces of Axional LC
Spain — deepest
SII, TicketBAI, Verifactu, modelo 347 / 349, convenios, Seguridad Social, real-estate registry integration.
Peru — production
SUNAT CPE, libros electrónicos, PDT-PLAME, IGV, ESSALUD, financial-regulator reporting.
Extensible — Colombia, Pakistan, more
Additional regimes engineered as commercial requirements warrant — Colombia DIAN, Pakistan FBR, broader LATAM and EU.
Why this is engine, not bolt-on
Localisation released on the engine's release cadence — no partner-pack lag, no regulatory drift.
Why localisation depth is the moat against the global ERPs
The global ERPs (SAP, Oracle, Microsoft) approach localisation through a partner network. Country-specific behaviour lives in localisation packs maintained by third parties. The economic model favours coverage breadth over coverage depth — every country covered, none deeply.
Axional approaches localisation as engineering. The home market — Spain — is implemented to a depth no global ERP partner pack matches. The neighbouring market — Peru — is implemented to production depth where the company runs customers. Additional regimes are engineered as commercial demand warrants, on the engine's release cadence. Depth where it matters; extensibility where the demand emerges.