<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.
Multi-dimensional analytics that ends at the operational document.
Pre-defined and ad-hoc OLAP cubes per module, drill-down through any dimension, drill-across between operational areas, drill-through to the source operational document. The analyst's question — *what does that row mean?* — answered without leaving the screen.
Multi-dimensional cubes
Revenue by region × product × customer × period. Cost by entity × cost-centre × project × period. The dimensions the function lead actually thinks in.
Drill-down
From group P&L to entity P&L to cost-centre P&L to line item. Each level is a query against the same live ledger.
Drill-across
From revenue to the customer master to the customer's orders to the customer's invoices. The operational web traversable from any starting node.
Drill-through
The leaf of any analytical view is the operational document — the invoice, the order, the journal entry. The analyst opens what they queried.
What the analytics surface covers
Pre-defined cubes
Per-module cubes shipped — revenue analytics, cost analytics, working-capital analytics, project P&L analytics. Refreshed against the live ledger.
Ad-hoc cube building
Authors compose cubes from the engine's dimensional model. Save, share, schedule — without code.
Drill operations
Drill-down (deeper into dimensions), drill-up (aggregate), drill-across (jump to a related analytical view), drill-through (open the source document).
Time intelligence
Period-over-period, year-over-year, rolling-window comparisons. Fiscal periods aware. Comparable bases (constant FX, constant scope) computable.
Access-aware
Cubes honour the same role × entity × data-scope rules as the operational engine. The CFO sees the group; the country controller sees the country.
Cross-currency
Cubes aggregate in group currency for cross-entity analytics, with FX-method transparency. Constant-FX views available for like-for-like comparison.
Why drill-through is the analyst's safety net
An analyst looking at an aggregate number has to trust it. The trust is misplaced if the analyst cannot verify the number by reaching the underlying transactions. Most BI tools answer the question *what is this number?* with a slow, separate query to a different system.
Axional's drill-through reaches the operational document in one click. The aggregate row resolves to the journal entries that compose it; the journal entries resolve to the operational documents they came from. The analyst's question is answered in seconds, against the live ledger.