MIS Report Structure: What Belongs Where

Anyone building a monthly MIS report from scratch faces the same two questions. What sections should the pack contain, and where does each line belong within them?

The answers are more settled than the variety of packs in circulation would suggest. A well-structured MIS has a canonical shape: a one-page summary, a management-style profit and loss, a balance sheet and working capital view, a cash flow summary, and variance commentary. Most of the packs that fail do so not because they lack data but because they scramble this structure — the summary buried on page nine, the P&L grouped the way the auditor likes it, the commentary restating what the tables already show.

This is a reference guide to the structure itself: what each section is for, what belongs in it, and where the common misfiles happen.

The summary page: five to seven numbers, with comparatives

The first page of the pack is the only page some readers will ever see, and the pack should be built with that assumption. It carries five to seven numbers — no more — each shown against at least two comparatives: prior month and budget at minimum, prior year same month if the business has seasonality.

For most businesses the summary set looks like this: revenue, gross margin percentage, EBITDA, closing cash, net working capital movement, and one or two operational metrics that genuinely drive the business — active customers, billable utilisation, units shipped. If a number does not change a decision when it moves, it does not belong on this page.

The discipline is in what the page excludes. A summary with twenty numbers is a table of contents, not a summary. The CEO reading this page is deciding, in under a minute, whether the month was fine or whether something needs attention. Everything on the page should serve that judgement; everything else lives in the sections behind it.

The management P&L: not the statutory grouping

The second section is the profit and loss, and this is where the most consequential structural decision sits. A management P&L is not the statutory P&L rearranged. It answers a different question.

The statutory grouping — revenue, cost of materials consumed, employee benefit expenses, finance costs, depreciation, other expenses — exists to satisfy disclosure requirements. It groups costs by their nature. It tells you nothing about which part of the business the money serves.

The management grouping is built around contribution and function:

• Revenue by stream. Not one line. If the business sells products and services, or operates two channels, or serves two customer segments, revenue splits accordingly. A single revenue line hides the story the P&L exists to tell.
• Direct costs, matched against each revenue stream: the costs that would not exist if that revenue did not exist. Materials, direct labour, payment gateway fees, fulfilment.
• Contribution, by stream and in total. This is the line most statutory P&Ls never show and most management decisions depend on.
• Overheads by function, not by nature. Not “salaries ₹42 lakh” but sales and marketing ₹18 lakh, technology ₹14 lakh, finance and administration ₹10 lakh. A salary line grouped by nature tells you what kind of cost it is; grouped by function it tells you what the business bought with it.
• EBITDA, then depreciation, interest and tax below it.

The functional grouping is what makes the P&L decision-useful, and it is also what makes it harder to produce: it requires a mapping from the chart of accounts to functions, applied consistently every month, and rules for apportioning shared costs across them. That apportionment deserves its own methodology, applied the same way every month — a discipline, not a formula dragged down a column.

Where the common lines belong

Most of the arguments about MIS structure are really arguments about five or six specific lines. These are the classic misfiles, and where each line actually belongs.

Founder and promoter salary. Frequently understated, omitted, or parked in “other expenses”. It belongs in overheads under the function the founder actually performs — usually general management, sometimes sales. If the founder draws below market rate, a note should say so, because the EBITDA the pack shows is otherwise flattering the business. A hypothetical ₹1.2 crore EBITDA that assumes a founder working for ₹6 lakh a year is not ₹1.2 crore of sustainable EBITDA.

Freight inward versus freight outward. Freight inward — bringing materials or stock into the business — is a direct cost and sits above contribution. Freight outward — delivering to customers — is also direct, but it belongs against the revenue stream that caused it, not pooled with inward freight in a single “freight” line. Merging the two is one of the most common ways contribution by stream gets quietly distorted.

Software subscriptions. The habit is to pool every SaaS invoice into one “software” line in overheads. But the payment gateway and the fulfilment platform are direct costs; the CRM belongs to sales and marketing; the accounting system belongs to finance and administration. Classify each subscription by the function it serves. A single software line is a nature grouping smuggled back into a functional P&L.

One-time costs. Restructuring, a legal settlement, an office relocation. These belong in the P&L — excluding them entirely is how packs drift into fiction — but on a separately disclosed line below EBITDA or in a clearly labelled “exceptional items” row, so the reader can see both the reported result and the underlying run rate. What they must never do is dissolve invisibly into overheads, where they make one month look inexplicably bad and the trend unreadable.

GST and other indirect taxes. GST collected is not revenue and GST paid on purchases is not a cost. It is a flow-through: the business collects it on behalf of the government and remits it. Revenue in the MIS is always net of GST. Packs built from bank statements or invoice totals get this wrong constantly, and the result is revenue overstated by the tax rate and margins that reconcile to nothing.

Owner-funded or inter-company recharges. Where a group entity or the owner pays costs on the business’s behalf, those costs belong in the P&L at their real value, with the funding shown separately. A business that looks profitable only because its rent is paid elsewhere is not profitable.

Balance sheet and working capital

The third section is the balance sheet — summarised, not the full statutory schedule — and a working capital view built from it. The balance sheet in an MIS exists to answer one question: is anything building up quietly that will become a cash problem later?

The working capital view carries the movement lines: receivables with debtor days (DSO), inventory with inventory days, payables with creditor days, and the net working capital cycle in days. Each shown as a trend across at least six months, because the single-month number is nearly meaningless — it is the direction that warns you. Debtor days drifting from 48 to 63 over a quarter is a finding; debtor days of 55 in isolation is a shrug.

Alongside working capital, the section carries closing cash and bank balances by account, borrowings and their movement, and any capex in the month. That is enough. The MIS balance sheet is a health check, not an audit schedule.

Cash flow summary

The fourth section translates the P&L and balance sheet into the only statement that describes survival. A simple indirect presentation is enough for a monthly pack: EBITDA, less working capital movement, less capex, less debt service and tax, giving net cash movement, reconciled to the opening and closing cash balances.

The point of the section is the bridge between profit and cash. A month with ₹40 lakh of EBITDA and a ₹55 lakh working capital build is a month the business lost cash, and the P&L alone would never say so. Where the business runs tight, this monthly summary is the backward-looking companion to a rolling thirteen-week cash forecast — one explains where cash went, the other where it is going.

Variance commentary: cause, not restatement

The final section is commentary, and it has one rule: explain cause, never restate the number.

“Revenue was ₹1.6 crore against a budget of ₹1.8 crore, a shortfall of 11%” is a restatement. The reader has already seen the table. “The shortfall is two delayed enterprise renewals, both now signed and billing from next month; the underlying run rate is on budget” is commentary. It attributes the variance to a cause, says whether the cause is temporary or structural, and implies what happens next.

Commentary should cover only the variances that matter — a materiality threshold, say anything over ₹5 lakh or 10% against budget, keeps it honest — and each item should answer three questions: what caused it, is it one-off or recurring, and what, if anything, should be done. The mechanics of doing this well are their own discipline, covered in budget versus actual variance analysis.

A skeleton you can copy

The full pack, in order:

1. Summary page
   • Revenue, gross margin %, EBITDA, closing cash, net working capital movement, one or two operating metrics
   • Each versus prior month, budget, and prior year
2. Management P&L
   • Revenue by stream
   • Direct costs by stream (including freight outward, gateway fees, fulfilment)
   • Contribution by stream and total
   • Overheads by function: sales and marketing, technology, operations, finance and administration
   • EBITDA
   • Exceptional or one-time items, separately disclosed
   • Depreciation, interest, tax, net profit
3. Balance sheet and working capital
   • Summarised balance sheet
   • Receivables and DSO, inventory days, payables and creditor days — six-month trend
   • Cash and bank by account; borrowings and movement; capex
4. Cash flow summary
   • EBITDA to net cash movement bridge, reconciled to closing cash
5. Variance commentary
   • Material variances only; cause, one-off or recurring, recommended action

Ten to fourteen pages for most businesses. Anything longer is usually workings that belong in an appendix; anything shorter is usually missing the balance sheet.

The structure is not the hard part — it fits on one page, as above. The hard part is applying it identically every month: the same mappings, the same allocations, the same definitions, so that March is comparable with February and the trends mean something. A pack whose structure drifts month to month is a new report every month, and no one can read a trend off a moving target. Fix the structure once, write it down, and let the monthly work be filling it in — not redesigning it.

Datavrn is being built for finance teams that produce management reporting. Request early access to hear when we’re ready.