BAS Digital product · included in implementation
Report map
One register that answers the owner's question: 'which reports do I receive, what does each one show, by what date does it arrive, and who is responsible for it'. Reporting stops being 'we'll look when it's ready' and becomes a rhythm.
A quick test: name the reports you are guaranteed to receive next week — with dates. If the list doesn't come together, your reporting lives 'on request', not by a system.
What's wrong with 'on request' reports
Different every timeToday the export includes VAT, a month ago it didn't. Comparing periods is pointless.
No date — no report'We'll put it together in a few days' turns into two weeks. The decision gets made without numbers.
No one to hold accountableThe report didn't arrive, or arrived broken — and there's 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, a correctness criterion (how to know the numbers can be trusted), frequency, deadline, and owner.
Report map — excerpt (a typical service-company package)
| Report | What it shows | Correctness criterion | Frequency · deadline | To whom | Owner |
|---|---|---|---|---|---|
| Weekly rhythm | |||||
| Cash balances | Money across accounts and cash desks | balances = bank and actual cash counts | weekly · Mon 10:30 | Owner | Financier |
| Receivables / payables | Who owes us and whom we owe, with due dates | payments linked to invoices | weekly · Mon | Owner, PM | Financier |
| Payment calendar | Planned inflows and outflows for 4–12 weeks | no overdue plans | updated · Fri | Owner | Assistant |
| Weekly report | Cash summary: balances · in · out · pending + a takeaway | reconciled with the database before sending | weekly | Owner | BAS financier |
| Monthly rhythm | |||||
| P&L | Profit by line item and business line | suspense = 0, line items per the chart | monthly · by the 20th | Owner | BAS financier |
| Balance sheet | Assets, debts, equity | assets = liabilities after the close | monthly · by the 20th | Owner | BAS financier |
| Monthly report + session | The full picture of the month with verdicts and risks | built on a closed month | monthly · meeting by the 20th | Owner | BAS CFO |
The package is fixed as a standard — 5–7 reports, not twenty. This is the Reporting area at level 2: what, to whom, by what date, who is responsible.
The rhythm it lives in
Monday
Balances + debtscash balances, receivables/payables — a short morning snapshotFriday
Week closedata consolidation, payment calendar update, the weekly reportBy the 20th
Month closeclose by checklist, the report package, the monthlyOnce a month
Session with the ownera walk through the numbers: not 'here's the report' but 'here's what it means and what we do'What it gives you
Reports arrive on their own. You don't have to remember to ask — the system is obliged to deliver by the date.
Every number has a check. The correctness criterion is built into the register: no report goes out without reconciliation.
Formats are frozen. The same report month after month — periods can be compared.
Every report has a name on it. If it's late, it's clear who to ask (most often us — and that's fine).
Honestly: what the report map does not do.
- It doesn't produce reliable numbers by itself — it needs working accounting underneath (the transaction map, checklists, controls).
- It doesn't replace a conversation — without the monthly session, reports gradually stop being read; the meeting rhythm is part of the package.
- More doesn't mean better: the package is deliberately short. Nobody reads twenty reports.
The report map is assembled in the third month of implementation
By the trusted close you have a fixed report package with dates and owners — and it starts arriving every week and every month. From then on, the subscription keeps it running.