Industries/ Finance/ Automated management reporting
Month-end numbers, assembled for you, explained by your team
We join your ledger, CRM and loan or client data on definitions your finance lead signs off, so the board pack, funder report and investor update build themselves each month. Unusual movements are flagged for a person to explain before anything leaves the building.

- Used by
- Finance directors, financial controllers and the board
- Takes the place of
- Monthly exports, the inherited workbook and copy-paste packs
- Connects to
- Your ledger, CRM, loan or client platform and bank feeds
- Built with
- Our automated reporting service
Where it hurts today
A normal week, before it exists
In a lender, a wealth firm or a fintech, month end means the same exports in the same order. The trial balance from the ledger, new business from the CRM, the loan book or assets under administration from the platform, and the bank balances. They land in a workbook passed between three finance managers, and the controller spends the first days of the month making the numbers agree before anyone can read them.
The definitions move without anyone deciding they should. Arrears in the board pack is counted one way, arrears in the funder report another, and the investor update rounds both. A new product line gets added to one tab and not the next. When a non-executive asks why two pages disagree, the answer involves a cell reference and an apology, and confidence in the whole pack takes the hit.
Then the same figures are needed again, cut differently. The funding line wants covenant tests on its own template. Investors want a quarterly letter. The risk committee wants concentration by sector. Each is rebuilt from the same exports by the same people, and the one person who understands the macros is the one person who cannot take leave in the first week of the month.
What it does
Automated management reporting, feature by feature
The figures are defined once and every report reads from them, so the board, your funders and your investors see numbers that agree.
- 01
Definitions signed off once
Arrears, new lending, net flows, assets under administration, cost per account: each measure is written down in plain English, agreed with your finance lead and calculated one way. When a definition changes, the change is dated and recorded, and every report uses the new version from the same month.
- 02
Reconciled before it is reported
The ledger is checked against bank balances, and the loan book or client platform against the ledger, before any report is built. Differences above a threshold you set are listed for the controller with the transactions behind them, rather than discovered by a board member.
- 03
Variance flags with draft commentary
Each headline figure is compared with last month, last year and budget. Movements outside the range you set are flagged, and the draft commentary states what moved and by how much. The reason why is left for a person to write, because it usually lives in someone's head.
- 04
One run, several audiences
The board pack as a PDF, the funder report on the funder's own template, an investor update in your house style, and a working file with the underlying rows for the finance team. All come from the same run, so they cannot drift apart between versions.
- 05
Covenant and facility reporting
For lenders with funding lines, eligibility, concentration and performance tests are calculated from the loan book on each facility's own definitions, with a clear flag when a test is approaching its limit. The finance team reviews and signs off before anything is sent to the funder.
- 06
Every issued pack kept as sent
Each report is stored exactly as issued, alongside the data and definitions it was built from. When an auditor or a funder queries a figure from March, you can show what was reported, how it was calculated and who approved it before it went out.
A day with it
How the day runs instead
The first week of the month in a lender's finance team once the pack builds itself.
- Day 1, 8.30amFinancial controller
Overnight, the ledger, loan platform and bank data were pulled and reconciled. The controller opens the checks screen and sees two items: an unmatched receipt and a fee posted to the wrong period. Both are fixed in the ledger, and the run repeats.
- Day 1, 2pmFinance analyst
The draft pack is built. Arrears have moved more than the agreed range, so the figure is flagged. The analyst checks the loan-level detail, finds three accounts on payment holidays, and writes two sentences of explanation beside the draft commentary.
- Day 2Finance director
The finance director reads the pack, reviews the flagged movements and their notes, and approves it. The board version goes to the company secretary for the papers, and the management team gets a shorter summary built from the same figures.
- Day 3Finance manager
The funder report for the warehouse facility is generated on its own template. Every covenant test is within its limit, and one is marked as close. The finance manager reviews, signs off and sends it, and the issued copy is stored automatically.
- Quarter endChief executive
The investor update draws on three months of the same approved figures. The chief executive writes the narrative around numbers the finance team has already signed off, instead of waiting for a separate set to be assembled.
What it connects to
Works with what you already run
The reports read from the systems that hold the figures. They never edit them.
Accounting software or general ledger
Trial balance, journals and department codes are read on a schedule, for example from Xero, Sage or NetSuite where it offers an API, or from a scheduled export where it does not.
Loan, policy or client platform
Loan-level balances, arrears status, new business and redemptions, or holdings and flows for a wealth firm. This is usually the largest and most valuable source, and we map its fields with your team before anything is built.
CRM and pipeline
Applications, conversions and adviser or broker activity, so new business figures in the pack match what sales and operations see in their own screens each day.
Bank feeds
Balances and transactions for reconciliation and cash reporting, read through your bank's feed or an open banking connection. We ask for read-only access, so the reporting has no way to move money.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- One recurring report, usually the monthly board pack, rebuilt from source
- Written definitions for every headline measure, signed off by your finance lead
- Reconciliation checks between ledger, platform and bank before the pack builds
- Variance flags against prior month, prior year and budget, with draft commentary
- Several months run side by side with the manual pack before switching over
Once it is in use
- Funder and covenant reports on each facility's own template
- Quarterly investor updates built from the same approved figures
- Risk committee views such as concentration, vintage and arrears ageing
- Consumer Duty outcome measures for a UK firm's annual board report
Buyer's guide
Before you commission one
Four decisions worth making before you automate the board pack.
- 01
Reporting software, or a build
If your figures live mainly in one accounting package, a packaged management reporting tool that connects to it may be all you need, and we will say so. A build earns its place when the pack depends on a loan book, a client platform or a CRM those tools cannot read, or when definitions and checks matter more than templates.
- 02
What to gather first
The last three packs as issued, the workbook behind them, every export it uses, and a list of who receives each version. Ask the person who builds the pack to write down the manual adjustments they make each month. Those notes usually hold the rules that never made it into the spreadsheet.
- 03
Who should own it
The finance director or financial controller owns the definitions and the sign-off. Someone in finance, not IT, should be able to change a threshold, add a recipient or approve a new measure. We build the plumbing and the checks so that ownership stays where the accountability for the numbers already sits.
- 04
How you will know it is working
Watch the working day the pack is ready, the hours your qualified accountants spend assembling rather than analysing, the corrections made after issue, and the questions the board asks about how a figure was calculated. When those questions turn into questions about what the figures mean, the definitions are doing their job.
Terms worth knowing
The words you will meet
- Metric definitions
- A written rule for each measure: what counts as arrears, when a loan becomes new business, which flows count towards assets under administration. Every report then calculates it the same way. Without them, two accurate spreadsheets can disagree, and the board loses confidence in both.
- Expected credit loss
- The provision a lender holds against loans that may not be repaid. Under IFRS 9, loans move through three stages, with lifetime losses recognised once credit risk has risen significantly. In the US, CECL recognises lifetime expected losses from the start. A good pack shows how arrears and staging feed the provision, using your finance team's model.
- Consumer Duty board report
- In the UK, firms under the Consumer Duty must give their board an annual report on whether retail customers are getting good outcomes. The FCA's review of the first reports praised conclusions backed by good management information. The definitions and checks behind your monthly pack can supply those outcome measures too.
Handled with care
The details that matter here
A report that goes to a board, a funder or an investor carries your firm's name. These are the details we handle with your finance team.
Your accountants own the numbers
We build the plumbing and the checks. The definitions, the judgements and the sign-off stay with your finance lead. We document each calculation in plain English so your auditors can follow it, and the system is set up so nothing is issued until a named person approves it.
Matching the old pack, honestly
When we rebuild a report from source, it rarely matches the manual one exactly. We list every difference and its cause, a filter left on or a range that stopped updating, and you decide which figure is right before the new pack replaces the old.
Who sees which rows
Loan-level and client-level detail stays with the people entitled to it. The board pack shows aggregates, regional managers see their own book, and the working file with names and account numbers goes only to the finance team. Distribution is tied to your existing staff accounts.
Late or missing data
If a source has not delivered or a total moves implausibly, the run stops and a person is told which source is missing. We agree the checks with your controller, because a pack sent with a gap does more damage than one that arrives a few hours late.
Questions
What buyers ask first
Does automated management reporting work with our accounting software?
Usually. Most accounting packages, for example Xero, Sage or NetSuite, offer an API or a scheduled export, and we read from them without editing anything. In a financial firm the harder source is usually the loan book or client platform, which we map field by field with your team before building. Where a source only produces spreadsheets, we can work with those, and we will tell you how fragile that is.
Will it replace our accounting system or our spreadsheets?
It does not replace your ledger, which stays the book of record. It replaces the assembly: the exports, the copy and paste and the inherited workbook. Your team can still download the underlying figures into a spreadsheet to explore them. What changes is that the pack itself is built the same way every month, from the same definitions, with the checks run first.
Can AI write the commentary for the board pack?
It can draft the factual part: what moved, by how much, and which products or regions drove it, calculated from the figures. It should not explain why, because the reason is usually context your team holds, such as a paused campaign or a large redemption. The finance team starts from an accurate draft and adds the judgement, which was always the part that needed them.
Our data is in a mess. Should we fix that first?
Sometimes, yes. If the loan book and the ledger disagree for reasons nobody can explain, automating the pack only delivers the disagreement faster. We start by taking the current workbook apart cell by cell, and we will tell you plainly what needs fixing at the source before automation is worth it. Often that is smaller than people fear, but it has to come first.
What happens when we add a new product or entity?
The new product or entity is added to the definitions and mapped from its source system, then run alongside the existing pack until the figures are agreed. The other reports pick it up from the same definitions. It is real work, and we will scope it honestly, but it does not mean rebuilding the pack.
Send us the workbook that builds the board pack
Attach last month's pack and tell us who receives it. We reply within 48 hours with what we would automate first and what we would cut.
More for finance
What else we build for finance and banking
Client portals
A secure login where clients see valuations, statements, documents and application status, upload what you have asked for, and sign or approve without a printer. Permissions are checked on the server for every request, and every view is logged.
Guided onboarding journeys
Application and onboarding flows designed around how customers think: one question at a time, errors explained where they happen, progress saved between visits, and identity and suitability checks handed to your chosen providers at the right step.
Policy and procedure search
An assistant that answers questions from your own policies, procedures, product terms and committee minutes, citing the document and the version it relied on, so staff stop guessing and reviewers can check the source for themselves.
Document reading and triage
Bank statements, payslips, claim forms, valuations and signed agreements read on arrival, key details extracted and checked against the client record, and anything ambiguous or above a set threshold routed to a person rather than processed automatically.
Secure cloud foundations
Hosting arranged so customer and account data are separated, encrypted and reachable only by the roles that need them, with access logged to storage nobody can quietly edit, and card details kept out of your own systems wherever possible.