The complete financial reporting guide for SMEs
Key takeaways
- What you report depends on who's reading. Lenders, investors, boards, and internal teams each read a different page first.
- Cadence beats depth. A one-page report that ships on the 7th every month beats a beautiful pack that ships whenever.
- The core monthly set for most SMEs: the three statements, budget vs actual, a cash forecast, and a short commentary.
- A realistic close-to-distribute cycle for a team of one is seven working days.
- Most reporting time goes into assembly, not analysis, and assembly is the automatable half.
What to report
The core three
The foundation is the three financial statements: income statement, balance sheet, and cash flow statement. They're the standardized picture of profit, position, and cash that every external reader expects. We've written a full guide to the three statements and how they connect, so this post won't repeat their anatomy.
Management reports beyond the statements
The statements say what happened. Management reports say what it means and what's next:
Budget vs actual. Every major line: what you planned, what happened, the gap, and one sentence on why. This is the report that turns numbers into decisions, and the analytical skill behind it is variance analysis.
Cash forecast. Where the bank balance is heading over the next quarter, week by week. For any business with under six months of runway, this is the single most important document it produces; the 13-week format is the standard.
KPI dashboard. The five to eight numbers that define your business model: growth rate, gross margin, burn, runway, plus whatever your model adds (MRR and churn for SaaS, inventory turns for product businesses). One page, trended over time. The discipline is subtraction: every metric on the dashboard should be tied to a decision someone would make differently, and a dashboard that's grown past ten numbers is usually a dashboard nobody reads anymore.
One report deliberately missing from this list: the ad-hoc analysis. Someone will always want a one-off cut of the numbers, and that's fine, but it lives outside the recurring set. The recurring pack's power comes from being the same every month, so readers compare instead of re-learn. Keep the one-offs one-off.
What your audience reads first
Nobody reads a reporting pack front to back. A lender flips to cash and debt coverage. An investor flips to growth and runway. Your board flips to the variance commentary to see if you understand your own numbers. Build each report knowing which page gets read first, and put that page first.
This has a practical consequence for how you assemble the pack: build one master set of numbers, then reorder and trim per audience rather than building separate reports. The lender version leads with cash and covenants and drops the KPI dashboard; the investor version leads with the growth chart and compresses the statements to a summary page. Same numbers everywhere, different front doors. Maintaining one source with three covers takes a fraction of the time of three reports, and it eliminates the worst reporting failure there is: two audiences receiving two numbers for the same thing.
How often to report
| Report | Frequency | Audience |
|---|---|---|
| Cash position | Weekly | Founder, ops |
| 13-week cash flow | Weekly rolling | Founder, board |
| Management pack | Monthly | Leadership |
| Budget vs actual | Monthly | Department heads |
| Board pack | Quarterly | Board, investors |
| Statutory accounts | Annually | Regulator, lender |
Three notes on this table. First, weekly items are short: the cash position is one number and a glance at the forecast, five minutes on a Monday. Second, the monthly pack is the anchor; the quarterly board pack should be assembled from three monthly packs plus a strategy narrative, not built from scratch. If your quarterly reporting requires archaeology, your monthly reporting isn't working. Third, cadence should tighten with risk: a business with four months of runway moves the 13-week forecast from "founder reads it" to "leadership reviews it," and a business in a covenant-tight year reports covenant metrics monthly even if the lender only asks quarterly. The table is the default, not the law.
Who receives what
Lenders
Lenders care about one thing: will you service the debt. They read cash, debt balances, and covenant metrics like the debt service coverage ratio (DSCR), which is roughly operating income divided by annual debt payments; a DSCR of 1.25 means you earn a quarter more than the debt costs, and many loan agreements set their floor near that level. If your agreement names covenants, report against them explicitly every period, because discovering a covenant breach in your lender's spreadsheet instead of your own report is how relationships sour. Consistency matters more than polish here; lenders get nervous when formats change, and they get generous when a borrower flags a tight quarter two months before it arrives with a plan attached.
Investors
Investors read growth, burn, and runway, in that order. A monthly or quarterly update should lead with the trajectory (revenue, key growth metric), state the burn plainly, give runway in months, and flag anything that changed since last time. Two habits make these updates compound in value: keep the metric definitions identical from update to update, so the numbers are comparable without footnotes, and include one honest "what's not working" item every time. Investors punish surprises far more than they punish bad news delivered early, and the update that admitted a problem in March buys enormous credibility for the numbers reported in June.
The board
The board's job is judgment, so give it the material judgment needs: budget vs actual with commentary, the updated forecast, and the two or three decisions you actually want input on. A good board pack is short enough to read the night before and specific enough to argue with. Send it 48 hours before the meeting, and structure the meeting around the decisions rather than around reading the pack aloud; a board that reads numbers in the meeting is a board you're wasting.
Internal teams
Department heads need their own budget vs actual, and only theirs. Sending the marketing lead the full company P&L generates questions; sending them their marketing budget line with the variance highlighted generates accountability. Small companies skip this until they have departments, and should start the month they do, because the first month a manager sees their own variance is the first month they start managing to it.
A monthly cadence that actually holds
Day-by-day, sized for one person who owns finance alongside other jobs. Days are working days after month-end:
- Days 1-3: close the books. Or chase your bookkeeper to. Reconcile bank accounts, post the recurring journals, make sure revenue and major costs are in the right month. Nothing downstream works on unfinished numbers.
- Day 4: pull actuals. Generate the three statements and the budget vs actual view. If this step takes more than an hour, it's an assembly problem, not a finance problem.
- Day 5: variance work. Investigate the three biggest gaps against budget. One sentence of cause per gap. Resist explaining everything; materiality is a feature.
- Day 6: update the forecast. Roll what you learned into the projection. Permanent cost changes stay in; one-offs get noted and excluded.
- Day 7: write and distribute. One page of commentary on top of the pack: what happened, why, what changes. A structure that works: two sentences of headline ("Revenue $108k against $120k budget; the miss is one delayed enterprise deal, now expected in August"), the three variance explanations from day 5, one paragraph on the forecast change, and one line naming any decision you've made or need input on. Send it to the people the table above says should get it.
Seven working days means your stakeholders have June's story by roughly July 10. Hold that date for three consecutive months and it becomes the easiest credibility you'll ever build. Miss it twice and every number you send afterward gets the skeptical read.
Where the time goes
An honest accounting of the manual version, from doing this ourselves and with the founders we work with. Take a typical eight-hour monthly reporting cycle done in spreadsheets and it splits roughly like this: an hour or two exporting from the accounting system and pasting into the model, another hour fixing what the paste broke (rows that moved, formulas that now point at the wrong cells), an hour or more reconciling the one number that doesn't match QuickBooks, an hour reformatting the same tables for different audiences, and half an hour on distribution. The thinking part (why did margin slip, what does it mean for the forecast, what should we do) gets whatever's left, often under a fifth of the total, and it's the only part that creates value.
We're not citing an industry statistic here because the honest data is your own: time your next cycle and split it into "assembly" and "analysis." Most people who do this once stop defending the spreadsheet. The ratio is the whole argument for automating reporting; not to remove the human, but to spend the human on the fifth that matters.
Turn day four of the cadence into minutes instead of a week.
What can and can't be automated
Can be automated: data pull from your accounting system, statement assembly, budget vs actual calculation, chart generation, formatting, distribution. This is exactly the assembly work above, and it's what management reporting software exists to do.
Can't be automated: deciding what the variance means, choosing what to do about it, writing commentary your board trusts, and the judgment call about which numbers matter this quarter. Any tool claiming to automate the second list is overselling, and knowing the boundary is what makes the first list credible. The realistic outcome of automation is that day 4 of the cadence above becomes minutes, day 5 starts from a prepared variance view, and the seven-day cycle becomes four.
Frequently asked questions
How often should a small business do financial reporting?
Monthly for the management pack and budget vs actual, weekly for cash position, quarterly for the board. Monthly is the anchor; less frequent than that and problems get expensive before they get visible.
What's in a monthly management pack?
The three financial statements, budget vs actual with brief commentary, an updated cash forecast, and a small KPI dashboard. One page of narrative on top; ten pages total is plenty for most SMEs.
What's the difference between financial reporting and management reporting?
Financial reporting produces the standardized statements outsiders expect; management reporting adds the internal, decision-focused layer like budget vs actual and forecasts. In practice an SME's monthly pack contains both.
How long should a monthly close take?
Three to five working days for a small business with clean books, with the full report distributed by day seven. If close alone takes two weeks, fix the bookkeeping before fixing the reporting.
What do lenders ask for?
Typically annual statements, interim management accounts on request, and ongoing evidence you can service the debt, especially any covenant metrics named in your agreement, like DSCR. Report against covenants proactively rather than waiting to be asked.
If your day 4 currently takes a week, see how Reportly's management reporting software turns the assembly work into a data connection, or start from a ready-made pack structure in the reporting blueprint.