<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.
Invoices issued, reported and validated in the same transaction.
A customer-invoicing engine that handles line-level pricing, taxation, retentions, currency conversion and the fiscal-reporting obligation natively — SII, TicketBAI, Verifactu, modelo 347 / 349 in Spain; SUNAT CPE in Peru; DIAN factura electrónica in Colombia. The fiscal calendar is a feature, not a project.
Native fiscal reporting
SII, TicketBAI, Verifactu, SUNAT CPE, DIAN — built into the engine. The submission to the tax authority happens as part of the invoice posting, not as a follow-on batch.
Line-level pricing rules
Tariffs, contracts, promotions, retentions, discounts and currency conversion applied at the line level with a deterministic engine — the price the customer sees is the price the journal reflects.
B2B e-invoicing per market
FACe and FACeB2B in Spain; PEPPOL where required; SUNAT CPE in Peru; DIAN in Colombia. The channel the buyer's market demands, supported natively.
Multi-format outputs
UBL, Facturae, PDF/A — the standard the customer or the regime expects, generated from the same invoice record. No format-specific re-keying.
What the invoicing engine covers
Pricing and contract engine
Customer-specific contracts, tariff hierarchies, promotional overrides, scaled discounts and rebate accruals. The pricing decision and the supporting trace are visible on the invoice.
Multi-jurisdiction taxation
VAT and equivalent regimes (IVA, IGV, IRPF retentions) calculated at the line level by jurisdiction. Reverse charge, intra-EU acquisitions and triangular operations handled by configuration.
Spain — SII, TicketBAI, Verifactu, modelo 347 / 349
Real-time reporting to the AEAT under SII; ticket-by-ticket signing under TicketBAI in the Basque Country; Verifactu where the regime applies; and the periodic informative declarations on the regime's calendar.
LATAM — SUNAT, DIAN
Peru SUNAT CPE (boletas, facturas, notas, comprobantes de retención) with libros electrónicos and PLE; Colombia DIAN factura electrónica with the corresponding XML structures and PAC integration.
B2B e-invoicing channels
FACe and FACeB2B for the Spanish public sector; PEPPOL where the buyer is on the European network; bilateral EDI channels for retail and industrial buyers; direct portals where the buyer publishes their own.
Validation and dispute
The validation status of every submission tracked back to the source invoice. Rejections and disputes routed to the AR team for resolution without losing the original invoice context.
Why the regulation is the engine, not the project
Most ERPs treat fiscal compliance as a country-specific localisation pack. The pack is updated by a partner team on a different cadence than the engine, and a regulatory change becomes a coordination project between the customer, the partner and the vendor. The result is a brittle layer of glue that breaks on the day a regulation changes.
Axional engineers fiscal compliance into the invoicing engine itself. SII, TicketBAI, Verifactu, SUNAT and DIAN are not modules sold separately; they are behaviours the engine performs. When a regulation changes, the engine changes — by the engineers who wrote it — and the customer's deployments inherit the change through the same release process as any other capability.