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.
Colombia — and extensible
Colombia supported : DIAN factura electrónica, RUT, IVA. 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.
Colombia — and extensible to more
Colombia supported : DIAN factura electrónica, RUT, IVA. Additional regimes engineered as commercial requirements warrant — 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.
What finance and compliance teams ask about Spain, Peru and beyond.
Does Axional ERP report to SII in real time?
Yes. Every issued and received invoice is submitted to the AEAT under SII as it posts, not by a batch routine at the end of the period. Validation status is tracked, rejections are routed for resolution and the original transaction is preserved.
Does Axional ERP support TicketBAI and Verifactu?
Yes. TicketBAI ticket-by-ticket signing follows the Basque tax authorities' specifications, with the provincial variations of Álava, Bizkaia and Gipuzkoa handled. Verifactu, the integrity and traceability framework for invoicing software, is applied where the regime applies.
Which Spanish tax returns does Axional ERP generate?
Modelo 347 (operations above €3,005.06 per counterparty), 349 (intra-EU), 303 and 390 (VAT), 322 and 353 (group VAT) and the 111, 190 and 216 withholding declarations, all generated from the live ledger. Public-sector and B2B e-invoicing run through FACe, FACeB2B and PEPPOL.
What does the Peruvian localisation cover?
SUNAT CPE electronic documents (boletas, facturas, notas de crédito and débito, comprobantes de retención and percepción), libros electrónicos submitted through PLE, PDT-PLAME payroll declarations, ESSALUD and AFP interfaces, periodic IGV returns and the declaración jurada anual. It is in production at customers operating under the Peruvian regime.
Does Axional ERP support Colombia and other countries?
Colombia is supported, including DIAN electronic invoicing, RUT and IVA. Further regimes, such as Pakistan (FBR) and broader LATAM and EU regimes, are engineered into the engine as commercial requirements warrant, following the same pattern. Talk to a localisation expert about the regime and scope your operation needs.
Who updates the localisation when a regulation changes?
The engineers who own the engine. Localisation is released on the engine's own cadence, so a regulatory change does not wait for a partner pack or a separate release calendar.