Start every report from a decision someone makes, define each number once, and make every figure open into the documents behind it.
Start from the question, not the data
Most ERP reporting problems come from building reports around what the system can show instead of what someone needs to decide. The result is a long list of reports, each slightly different, most rarely opened, and none quite answering the question that prompted it.
Before building anything, write the question in one sentence and name the person who asks it. "Which customers are more than sixty days overdue, and how much do they owe?" belongs to the receivables lead. "Which items will run out before the next supplier delivery?" belongs to purchase. "Are we over budget in any cost center this quarter?" belongs to finance and the cost-center owners. If you cannot name the person or the decision, you probably do not need the report.
Define every number once
Arguments about reports are usually arguments about definitions. Does "sales" include tax? Is it net of returns and credit notes? Is it by invoice date or delivery date? Does "stock" include goods in transit and items in quality inspection?
Agree on definitions and write them into the report itself: a short note under the title saying exactly what is included. Then use the same definition everywhere. When the sales report and the profit and loss statement disagree, it should be because they measure different things that are clearly labeled, not because someone built one of them differently.
Dates deserve particular attention. A report by posting date and one by document date can disagree for perfectly good reasons, and so can a report in the fiscal year and one in the calendar year. Choose the default for each report, show it on the screen, and make it easy to change. Most "the numbers are wrong" complaints turn out to be two people looking at different date ranges.
Every figure should open into its documents
A number you cannot trace is a number people will not trust. Good ERP reports let you click any figure and see the documents behind it: the invoices that make up a customer's balance, the stock entries behind a warehouse quantity, the journal lines behind an account total.
This is one of the real advantages of running the business in one system. Because orders, stock, invoices and payments sit on the same ledgers, the report and the transaction are the same data. There is no export, no lookup table and no reconciliation between a reporting tool and the books.
Fewer reports, used more often
A small business usually needs a short core set: profit and loss, balance sheet and cash flow; receivables and payables aging; stock balance and stock aging; sales by customer and item; purchase by supplier; and budget against actual by cost center. Manufacturers add production and downtime. Service businesses add project profitability and unbilled time.
Before adding a new report, check whether an existing one with a saved filter answers the question. Saved views are cheaper to maintain than custom reports and stay correct when the underlying data changes.
Put the report where people already are
A report nobody opens might as well not exist. The engine underneath Sundial can email a report on a schedule, so the overdue list reaches the receivables lead every Monday without anyone remembering to run it. Use that for routine checks, and keep dashboards for the handful of numbers someone looks at every day.
Be strict about who receives what. A weekly email that goes to fifteen people and is read by two trains everyone to ignore the system's messages.
Review the schedule twice a year. Remove reports nobody has opened, merge ones that overlap, and ask each recipient whether the report still answers their question. Needs change as the business grows, and reporting should change with them.
Where plain-language questions fit
Some questions are one-off and do not justify a report at all: "What did we buy from this supplier last quarter?" Sundial is designed so that, over time, you can ask questions like that in plain language and get an answer that shows its filters and links back to the records. That is on our roadmap, not a replacement for a well-defined core set of reports. The definitions you agree today are what will make those answers trustworthy later.




