Outsourced CFO
BAS Digital product · part of implementation
Report map
One register that answers the owner's question: “which reports do I get, what does each one show, by what date does it arrive, and who is responsible for it”. Reporting stops being “we'll look once it's put together” and becomes a rhythm.
Discuss implementationWhat's wrong with reports “on request”
Different every timeToday exported with VAT, a month ago without. Comparing periods is pointless.
No date — no report“We'll have it in a few days” turns into two weeks. The decision is made without numbers.
No one to hold accountableThe report didn't arrive, or arrived broken — and there is no one to ask: no owner was assigned.
What the report map looks like
Each report is a row with five mandatory attributes: what it shows, the correctness criterion (how to know the numbers can be trusted), frequency, deadline and owner. The package is fixed as a standard — 5–7 reports, not twenty.
The rhythm it lives in
1MondayCash balances, receivables and payables — a short morning snapshot.
2FridayWeek close: data consolidation, payment calendar update, weekly report.
3By the 20thMonth-end close by checklist, report package, monthly.
4Once a monthSession with the owner: going through the numbers — not “here is the report” but “here is what it means and what we do”.
What you get
Reports arrive on their ownYou don't have to remember to ask — the system must deliver by the date.
Every number has a checkThe correctness criterion is built into the register: no report goes out without reconciliation.
Formats are frozenThe same report month after month — periods can be compared.
Every report has a name on itIf it's late, it's clear who to ask. Most often that's us, and that's fine.
Honestly: what it does not do
—It does not produce reliable numbers by itself — it needs working accounting underneath: transaction map, checklists, controls.
—It does not replace the conversation — a report without a monthly session gradually stops being read; the meeting rhythm is part of the package.
—More is not better: the package is deliberately short. Nobody reads twenty reports.
The report map is built in the third month of implementation
By the trusted close you have a fixed package of reports with dates and owners — and it starts arriving every week and every month. From there, the subscription keeps it going.
Discuss implementationOther tools of the methodology
Area maturityBAS Digital methodology · basis for the audit and roadmapLearn more →Transaction mapBAS Digital product · part of implementationLearn more →Checklists and reconciliationsBAS Digital product · accounting disciplineLearn more →SOP: work standardsBAS Digital product · procedures and trainingLearn more →Weekly and MonthlyBAS Digital product · core of the subscriptionLearn more →Client hubBAS Digital product · transparency of workLearn more →Financial modelBAS Digital product · “Planning” packageLearn more →Niche reportsBAS Digital service · Market IntelligenceLearn more →