Management Reporting | Report Builder
The next report your CFO asks for, without a ticket.
Drag fields from a governed metadata library. Filter, group, pivot, choose the visualisation and preview as you build. Save it, scope who can see it, schedule it. The next ask becomes a thirty-minute build rather than an item in next quarter’s backlog.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| Governed fields | A metadata library defined once | Everyone composes from the same definitions of revenue, margin and spend |
| Build | Drag, filter, group, pivot | A working report with live preview as it is assembled |
| Visualisation | The shape of the data | Table, chart or summary, chosen rather than defaulted |
| Access scoping | A saved report | Who can see it, and which entities or cost centres they see |
| Scheduling | Any saved report | Delivered on a cadence, in the format the recipient wants |
| Drill-through | Any cell | The transactions behind it, same as the pre-built reports |
| Versioning | A report definition changing | The change tracked, so a number that moved can be explained |
-
Governed fields
- Input
- A metadata library defined once
- Output
- Everyone composes from the same definitions of revenue, margin and spend
-
Build
- Input
- Drag, filter, group, pivot
- Output
- A working report with live preview as it is assembled
-
Visualisation
- Input
- The shape of the data
- Output
- Table, chart or summary, chosen rather than defaulted
-
Access scoping
- Input
- A saved report
- Output
- Who can see it, and which entities or cost centres they see
-
Scheduling
- Input
- Any saved report
- Output
- Delivered on a cadence, in the format the recipient wants
-
Drill-through
- Input
- Any cell
- Output
- The transactions behind it, same as the pre-built reports
-
Versioning
- Input
- A report definition changing
- Output
- The change tracked, so a number that moved can be explained
Custom Report Builder FAQ
What buyers ask.
Why restrict fields to a library rather than opening the tables?
Because self-service on raw tables reliably produces two versions of revenue and an argument in a board meeting. Defining the fields once is what makes self-service safe, and it is the difference between distributed reporting and distributed disagreement.
Do you need to know SQL?
No. The build is drag, filter, group and pivot, and it is aimed at a controller or an analyst rather than an engineer. Where someone does want SQL, the underlying query is visible.
What happens when a report definition changes?
The change is tracked. A figure that moved between two months is either a real movement or a definition change, and being unable to tell which is how confidence in reporting erodes.
Can we share a report outside finance?
Yes, with access scoped to entities or cost centres, so a department head sees their own numbers rather than the whole company by accident.
Do custom reports drill through like the built-in ones?
Yes. There is no second class of report here; anything built from the library inherits the same drill-through to source.
Build the report you were going to ask IT for.
Connect your books, free. Compose from governed fields and see it run against your own data.