Wevo is a purpose-built hierarchical reporting engine - not a dashboard bolted onto your GL. It rolls flat transactions up through the structures you define, lets you drill straight back down to the detail beneath, and keeps a whole group consolidated and current - near-real-time, minutes behind the GL.
A General Ledger stores transactions as flat rows keyed by segment values - cost centre, account, entity. Wevo maps those segment values to the bottom of a hierarchy you define, then aggregates every posting up through the parent-child chain to the root.
The result is responsibility reporting: each summary node shows the true total for the division, cost centre, or account group it represents - and every figure traces cleanly back to the postings beneath it.
Pair an organisational hierarchy (H1 - divisions, cost centres) with an account hierarchy (H2 - income, expenditure, account codes) and Wevo builds an analytical cube. Every node on one axis intersects every node on the other, so you can answer "what is total operating revenue for Europe?" by navigating to the intersection.
From any intersection, one click drills to the detail beneath - the children of the focused node pair at the leaf level (segment-value × account), with their accumulated balances and movements - typically in under a second, because the roll-ups are already calculated.
| Segment × Account (leaf) | P07 Bal | Movement |
|---|---|---|
| 41000 · Raw Materials | £(1,643,450) | £(342,100) |
| 41200 · Materials Accrual | £(580,000) | £(580,000) |
| 41500 · Stock Write-down | £(721,350) | £(721,350) |
| 41900 · Carriage Inward | £(817,090) | £(48,200) |
Wevo holds multiple years, record types, versions, and currencies side by side. Compare actuals to budget, this year to last, base currency to source currency - all within the same navigation context, with values scaled to units, thousands, or millions.
Access is controlled by hierarchy scope, not a blunt role flag. A node profile restricts a user to a branch and its descendants; a level profile grants a whole level and below. Users only see cube data where both hierarchies fall inside their profile - no separate report variants, no data leakage.
| Entity | CCY | Local | Group £ |
|---|---|---|---|
| UK Ltd | GBP | £ 22,104,000 | £ 22,104,000 |
| DE GmbH | EUR | € 14,820,000 | £ 12,598,000 |
| FR SAS | EUR | € 8,340,000 | £ 7,092,000 |
| SG Pte Ltd | SGD | S$ 3,940,000 | £ 2,310,000 |
| ▸ Group Total | GBP | - | £ 44,104,000 |
Wevo's core job is to keep its summarisation data in step with your General Ledger in near-real-time. Frequent, small extracts feed an incremental build that recalculates only the nodes that changed - so reporting reflects GL activity within minutes, not after an overnight run.
And because the engine releases new data one cube at a time - current year first - your team keeps working throughout the load. There is no maintenance window, even at millions of rows.
| Cube | Year | Status |
|---|---|---|
| Group · Operating P&L | 2026 | Released ✓ |
| Group · Operating P&L | 2025 | Released ✓ |
| Group · Operating P&L | 2024 | Building... |
| Group · Balance Sheet | 2024 | Queued |
Authorised users receive a report request form by email. They adjust the parameters in the browser, click send, and the finished report returns to their inbox within seconds - generated from the pre-calculated cube on near-live data.
Every request is scoped to the user's security profile, validated by token and sender, and fully audit-logged. Because recipients need no licence seat, you can report to the people you would never buy seats for.
| Step | Where |
|---|---|
| Request form pushed (Mon 07:00) | Inbox |
| Adjust parameters, click send | Browser |
| Token + sender + profile validated | Wevo |
| Report returned | < 10s |
Restructure the organisation whenever you need to. Prior years read through today's hierarchy for like-for-like comparison (as-is), while retained year-versioned hierarchies show history exactly as it was originally reported (as-was) - both from a single dataset.
Place any organisation × account intersection on the node pair watchlist and Wevo writes a time-stamped snapshot every time the engine runs, across all active years and currencies - a granular history that accumulates with no ongoing effort, ready for trend analysis and anomaly detection.
| Run | P07 Bal | Δ Movement |
|---|---|---|
| 18 Jun 06:00 | £ 4,118,200 | - |
| 19 Jun 06:00 | £ 4,204,650 | +86,450 |
| 20 Jun 06:00 | £ 4,191,900 | −12,750 |
| 23 Jun 06:00 | £ 4,402,300 | +210,400 |
The Business Introduction walks through every capability above - with diagrams, worked examples, and the architecture behind them.
Request a demo against a real GL dataset - your hierarchy, your numbers, your questions answered live.