<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.
One ledger across companies, currencies and statutory regimes.
A multi-company general ledger with full sub-ledger reconciliation, configurable account hierarchies, parallel statutory and management views, and a journal layer that an auditor can open at any time. Period close becomes a query against a live ledger, not a project run on a spreadsheet.
Multi-company GL
Each legal entity has its own ledger; the engine consolidates across them on configurable hierarchies. Cross-entity transactions post matched documents automatically.
Sub-ledger reconciliation
AP, AR, fixed assets, cash, inventory and intercompany sub-ledgers reconcile to the GL by construction — every operational document writes its journal entry in the same transaction.
Audit-grade journal layer
Every entry preserves the source transaction, the user, the timestamp and the approval chain. A reversal generates a new entry; the original is not destroyed.
Statutory and management views
Spanish PGC, IFRS, US GAAP, internal management reporting — multiple views maintained in parallel from the same source entries, no reconciliation glue.
What the General Ledger covers
Configurable chart of accounts
Hierarchical account structures with arbitrary depth, multi-dimensional analytics (cost centre, project, business unit, segment), and per-entity overrides where local regimes require account-code conformance.
Real-time sub-ledger posting
Operational documents — supplier invoices, customer invoices, asset acquisitions, bank movements — post their journal entry as part of the same transaction. No periodic posting batches, no reconciliation drift.
Period control
Per-period open / closed status by entity, by sub-ledger, by user role. Soft-close (operational lockout but adjustment-allowed) and hard-close (audit-final) are first-class states.
Journal entry classes
Standard, recurring, accrual, reversal, allocation and intercompany journals — each with its own validation, approval and audit trail. Bulk entry uploads honour the same controls.
Drill-through reporting
From a consolidated group P&L row down to the source operational document in three clicks. The auditor's day-zero question — *show me the receipt* — is answered without leaving the screen.
Multi-currency at the entry level
Transactional, functional and group currencies maintained on every entry. Revaluation on the period close uses the methods each regime expects (closing rate, average, historical).
Why the journal layer matters more than the chart
The argument for a strong general ledger is not the chart of accounts — every ERP has one. The argument is the journal layer underneath. When every operational document writes its journal entry in the same transaction as the document itself, sub-ledger drift becomes structurally impossible. When the journal preserves the user, the timestamp and the approval chain, the audit becomes a query rather than a reconstruction.
This is the difference between a finance team that closes the month in five working days and one that closes it in fifteen. Period close is not a project at Axional customers; it is the natural consequence of an engine that already knows the answer.