Board MIS Pack: P&L, Cash, Runway and KPI Validation Checklist
Board MIS should not be a pretty deck with unverified numbers. Every KPI should tie back to books, bank, CRM or payroll source — a board that approves a burn plan or a fundraise on an untied ARR or runway figure is making that decision on a number the controller has not actually checked.
Use the Month-End Close Calendar for Startups: Controller Evidence Pack to apply these points to your figures or facts.
Detailed analysis
Financial statements need true and fair presentation under Schedule III; board MIS needs the same discipline applied to numbers that never go near a statutory audit — ARR, MRR, net revenue retention, CAC payback, gross margin and runway. None of these are defined by an accounting standard, which is exactly why they drift: a founder-friendly ARR definition that includes one-time setup fees, or a runway model that ignores a known GST or TDS payable due next quarter, can both look correct in isolation while giving the board a materially wrong picture. The controller's job before circulation is to tie each headline KPI back to a source system (billing/CRM, bank, payroll, GL) and disclose the definition used, not just the number.
Practical example
Board pack shows ARR ₹12 crore, but the deferred-revenue schedule supports ₹10.8 crore of annualised recurring revenue once one-time onboarding fees and a large multi-year prepayment are backed out. Finance revises the KPI definition, adds a reconciliation to the billing and revenue-recognition schedules, and includes a variance note explaining the ₹1.2 crore gap. Separately, the cash pack shows 14 months of runway at the current burn rate — but that burn rate excludes a ₹40 lakh GST liability and a ₹25 lakh employee bonus accrual both due within the quarter; once included, the funded runway is closer to 12 months, which is the number the board should actually be planning around.
Evidence and control checklist
| Area | What to check | Evidence to save |
|---|---|---|
| Financials | P&L, balance sheet, cash flow and variance notes. | TB, MIS schedule and GL tie-out. |
| Cash/runway | Bank balance, burn and runway assumptions. | Bank statement, cash forecast and burn bridge. |
| Revenue KPIs | ARR/MRR, churn, collections and deferred revenue. | CRM/billing/revenue reconciliation. |
| Working capital | AR ageing, AP ageing and tax payables. | AR/AP schedules and statutory liabilities. |
| Decision notes | Key variances, risks and actions. | Board pack and action tracker. |
For the connected rule, example or next step, see Cash Flow Statement Preparation: AS 3 Controller Tie-Out Checklist.
Common mistakes
- Presenting KPI definitions that change monthly.
- No tie between MIS and books.
- Ignoring deferred revenue in ARR.
- Showing cash runway without payables/tax dues.
- No action tracker from prior board meeting.
Official reference framework
Based only on official India Code, MCA and ICAI source pages listed below. Check the latest Companies Act, Schedule III, accounting standards, Ind AS/AS applicability and auditor guidance before closing or filing.
Official sources used
This article is intentionally source-limited to official India Code, MCA and ICAI material. Source validation date: 30 August 2026. Verify final positions with latest Companies Act, Schedule III, accounting standards, Ind AS/AS applicability and auditor guidance before closing or filing.
- India Code: Companies Act, 2013 Section 129 - Financial statement
- India Code: Schedule III to the Companies Act, 2013
- India Code: Companies Act, 2013 Section 128 - Books of account
For the connected rule, example or next step, see Internal Financial Controls for Startups: Process, Evidence and Risk Matrix.
2026 Accuracy & Decision Check
Turn Board MIS Pack: P&L, Cash, Runway and KPI Validation Checklist into a reconciled management decision, not a dashboard number
A CFO-grade answer states the definition, data source, formula/accounting treatment, period, owner and decision threshold. It then reconciles the metric to financial statements or source systems and tests a downside case. This prevents a KPI, valuation or budget from looking precise while being driven by hidden assumptions.
Decision / evidence controls
- Define numerator/denominator and accounting perimeter.
- Tie source data to ledger/bank/contract or audited reporting.
- Run base, downside and liquidity cases.
- Record owner, review frequency and action threshold for each metric.
Primary-source checks
FAQs
At minimum: P&L with variance to budget, cash position and runway, working-capital ageing (AR/AP), the 3-5 KPIs the board actually tracks (ARR/MRR, churn, CAC payback, gross margin), and a short risk/action-tracker section carried forward from the prior meeting. A pack that skips the action tracker tends to re-raise the same unresolved issue every quarter without anyone noticing the pattern.
Yes, wherever a KPI can be tied to the general ledger, bank statement, CRM/billing system or payroll register, it should be — with the reconciliation shown, not just asserted. Where a KPI genuinely can't be tied exactly (e.g. an operating metric like active-user count), the definition and its source system should be disclosed explicitly so the board knows what they are and are not looking at.
Runway is cash available divided by net monthly burn. It commonly overstates the real position when the burn figure excludes known near-term outflows that haven't hit the bank yet — a GST or TDS liability, an accrued bonus, a security deposit due on a lease renewal. A funded-runway figure that nets these out is materially more useful to a board than a raw cash-divided-by-burn number.
AR ageing shows how much of reported revenue has actually converted to cash and flags customers sliding toward default; AP ageing shows supplier and statutory dues the company is sitting on, which is exactly the kind of liability that can quietly erode a runway figure calculated on cash alone. Both belong next to the cash/runway section, not buried in a separate schedule.
ARR is an operating metric, not a defined accounting figure — it is meant to annualise recurring subscription/contract revenue, and it commonly gets inflated by including one-time fees, multi-year prepayments annualised at face value, or contracts already in their notice period. The accounting revenue-recognition schedule (and the deferred-revenue balance behind it) is the check: if ARR and the recognised-revenue run-rate diverge by a large margin, the gap needs an explicit variance note, not a silent restatement next quarter.
The finance controller or CFO, before the pack is circulated to the board — validation here means an actual tie-out to source systems and a stated downside case, not a read-through for typos. Where the company doesn't yet have a controller, an external accountant or fractional CFO should sign off on the reconciliation before founders present it.
Source and review trail
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.
- Primary category
- Business Case Studies & Corporate Strategy
- Official starting point
- www.mca.gov.in