Ask a question, get a report.
Reporting that reads the same ledger the agents do, so a number in a board pack traces back to the posting that produced it — without a warehouse in between.
No separate warehouse·Drill to the posting·Scheduled packs
Reporting on the ledger itself.
The absence of a warehouse is the feature. It removes a nightly job, a schema to maintain, a lag, and the class of argument that begins 'which number is right'.
Reports that ship
The ones you would otherwise commission.
Statutory statements
Balance sheet, profit and loss, cash flow, trial balance, and consolidated versions across companies.
Operational registers
Stock balance and ledger, ageing, order analysis, production output, project profitability — several hundred across the modules.
Every module ships its own
A module page lists the reports it comes with, so the reporting question is answered before the project starts rather than during it.
Dimension-aware
Any ledger report can be read by cost centre, project, or a dimension you defined, without a new report being built.
Building your own
Without waiting for a developer.
Query builder
Filters, grouping, and totals over any record type, saved and shared like any other document.
Custom reports as code
Where a report needs real logic, it is a versioned script in an app rather than a definition in a settings table.
Dashboards and charts
Number cards, charts, and lists composed from saved reports, with the same permissions applied.
Print formats
Documents and packs laid out for the people who genuinely need them on paper or as a PDF.
Trust
Why the number in the pack is the number.
Drill to the posting
Every figure opens to the transactions behind it and then to the documents behind those. No dead ends at a summary.
One source
The board pack, the operational report, and the agent all read the same ledger, so they cannot disagree.
As-at reporting
Run a report as it stood at a past date, which is what makes a restated figure explainable.
Permissions carried
A shared report shows each recipient only what their role permits, rather than being shared with a snapshot of somebody else's access.
Distribution
Getting it to people without them asking.
Scheduled packs
Reports generated and sent on a cadence, to named recipients, in the format they want.
Threshold alerts
A report that only sends when a condition is met, which is the version people actually read.
Export
CSV and Excel from any report, plus the API, because somebody will always want it in a spreadsheet.
Ask in plain language
The console answers operational questions from the same records and names the documents used.
From a figure in a pack back to the document.
Four clicks, and the reason it works is that there is nothing between the pack and the ledger for the number to change in.
- 01
The pack
A scheduled report arrives with the figure on it, generated at a stated time from the live ledger.
- 02
The breakdown
The figure opens into its components by account, dimension, or period.
- 03
The postings
A component opens into the individual general ledger entries that make it up.
- 04
The document
A posting opens the invoice, delivery, or journal that created it, with its full audit trail.
The specification.
The questions a data team asks when they hear there is no warehouse.
- Source
- The operational ledger; no ETL, no separate schema
- Latency
- Live — a posted document is in the next report run
- Drill-down
- Figure to component to posting to source document
- Historic
- As-at reporting for any past date
- Dimensions
- Company, cost centre, project, and your own
- Permissions
- Applied per recipient, not baked into a share
- Export
- CSV, Excel, PDF, and the REST API
- Custom reports
- Versioned in an app, not stored as loose config
Where you will still want a warehouse.
Reporting on the operational ledger covers most of what a business needs, and it does not cover everything. Pretending otherwise would cost you a project later.
- Very large historical analysis
- Ten years of line-level history scanned repeatedly belongs in a columnar store. Export is supported and expected; we would rather help you build that than claim it is unnecessary.
- Blending with non-ERP sources
- Marketing spend, web analytics, and market data are not in this ledger. Where the question spans them, a warehouse is the right tool and the API is the feed.
- Data-science workloads
- Model training and heavy statistical work should not run against a production ledger. Export, and keep the operational system operational.
- It is not a BI product
- The visual sophistication of a dedicated BI tool is not the goal here. If your team lives in one, connect it — the API is the point.
Next step