The ERP reports every finance team needs fall into five groups: management accounts (profit and loss, balance sheet, budget vs actual), working capital (receivables and payables ageing), cash (cash position and forecast), margin (by product, customer and channel) and stock valuation. The reports matter less than the definitions behind them: if two people calculate gross margin differently, no dashboard will fix it.
Most ERP projects deliver hundreds of standard reports and still leave finance exporting to spreadsheets at month end. That happens when reports are designed from the data outward rather than from the decisions finance has to make. This guide starts from the decisions, lists the reports that support them, defines the KPIs, and explains how to build reports that hold up at month end.
If your current ERP cannot produce these reliably, our custom ERP software team builds finance modules and reporting around how you close the books, and our business dashboards service covers reporting layers on top of existing systems.
Which ERP reports does a finance team need every month?
A dozen reports cover most monthly needs. Here is the core pack, with the question each answers and who reads it.
| Report | Answers | Main reader | Frequency |
|---|---|---|---|
| Profit and loss by period, with budget and prior year | Are we on plan? | Leadership, board | Monthly |
| Balance sheet | What do we own and owe? | Finance, lenders | Monthly |
| Trial balance with drill-down | Do the books balance; what is in each account? | Finance | At close |
| Receivables ageing | Who owes us, and how late? | Credit control | Weekly |
| Payables ageing | What do we owe, and when? | Finance, purchasing | Weekly |
| Cash position | How much cash, where, today? | Finance lead | Daily |
| Cash flow forecast | Will we have enough in 13 weeks? | Finance lead, leadership | Weekly |
| Gross margin by product, customer, channel | Where do we actually make money? | Sales, leadership | Monthly |
| Stock valuation | What is inventory worth, and is it right? | Finance, auditors | Monthly |
| Slow-moving and obsolete stock | What should be written down? | Finance, operations | Quarterly |
| Departmental or cost-centre P and L | Is each area within budget? | Budget holders | Monthly |
| Inter-company balances (groups) | Do entities agree with each other? | Group finance | Monthly |
Groups with several companies need the consolidation and inter-company reports covered in our multi-entity ERP governance guide.
How should finance KPIs be defined?
Write each KPI as a formula with its source fields, exclusions and owner, then lock it. Disagreements about numbers are nearly always disagreements about definitions.
A KPI definition card, illustrative:
| Field | Example: debtor days |
|---|---|
| Formula | Trade receivables at period end divided by credit sales in the last 90 days, multiplied by 90 |
| Includes | Open customer invoices and credit notes in base currency |
| Excludes | Inter-company balances, cash sales, VAT or sales tax if sales are measured net |
| Source | Receivables ledger and sales journal in the ERP |
| Owner | Financial controller |
| Refresh | Daily, final at period close |
| Target and alert | Set by the business, not the report |
Do the same for gross margin (which costs are in cost of sales?), cash conversion cycle, budget variance and stock turn. Our business dashboard KPI design guide covers how to choose and lay out KPIs so they lead to action.
What makes an ageing report trustworthy?
An ageing report is only as good as cash allocation. If receipts sit unallocated on account, invoices look overdue that are already paid, and credit control chases the wrong customers.
Checklist for receivables and payables ageing:
- Ageing basis stated: by due date or by invoice date (due date is more useful for collections)
- Buckets agreed: current, 1 to 30, 31 to 60, 61 to 90, over 90 days past due
- Unallocated cash and credit notes shown separately, not hidden
- Ageing total ties to the control account in the general ledger, every month
- Disputed invoices flagged and excluded from collection reminders
- Multi-currency balances shown in transaction and base currency
- Drill-down from customer total to invoice to the original document
What should a cash flow forecast include?
A short-term cash forecast, often weekly over 13 weeks, should start from today's bank balances and add expected receipts and payments by week, using ERP data wherever possible rather than typed-in estimates.
| Line | Source in the ERP | Adjustment |
|---|---|---|
| Opening cash | Bank balances, reconciled | None |
| Customer receipts | Open invoices by due date | Shift by each customer's actual payment behaviour |
| Expected new sales receipts | Sales orders and pipeline | Apply payment terms; mark as less certain |
| Supplier payments | Open bills by due date, approved purchase orders | Follow your payment run calendar |
| Payroll | Payroll calendar | Include employer taxes and contributions |
| Tax payments | Tax accounts and filing calendar | Use the actual due dates for each country |
| Loans, leases, capital spend | Schedules and approved budgets | Fixed dates |
Each week, compare the forecast with what actually happened. The size of that gap, tracked over time, tells you how much to trust the forecast and where the assumptions are weak, usually customer payment timing.
How should stock valuation be reported?
Stock valuation should use the cost method your accounting framework allows and reconcile to the inventory accounts in the ledger. Under IFRS, IAS 2 (as published by the IFRS Foundation) requires inventories at the lower of cost and net realisable value, and permits FIFO or weighted average cost for interchangeable items; LIFO is not permitted. US GAAP differs, so US companies should confirm their method with their accountants.
What the report must show:
- Quantity and value by item, location and, where tracked, batch or serial number
- Cost method applied, and when costs were last updated
- Goods received not yet invoiced, and goods in transit, shown separately
- A tie-out of total stock value to the inventory accounts, with differences explained
- Slow-moving and obsolete stock by age band, as input to any write-down
If the stock value and the ledger disagree each month, the cause is usually postings outside the ERP, manual journals to inventory accounts, or receipts costed before the supplier invoice arrives.
How do you build ERP reports that people trust?
Build from a governed data layer, not from ad hoc exports. Trust comes from three things readers can see for themselves: the numbers tie to the ledger, every figure can be drilled down to the documents behind it, and the same measure gives the same answer wherever it appears. A report that fails any of these will be quietly rebuilt in a spreadsheet, and the spreadsheet will become the real source of truth. The steps:
- Start from decisions. List the decisions each reader makes, then the report that supports each one.
- Define every measure using the KPI card above, and get finance sign-off.
- Fix the chart of accounts and dimensions first. Reports by product, customer, region or project only work if transactions carry those dimensions when posted.
- Choose where reports run. Operational reports (ageing, cash) run live in the ERP. Analytical reports (margin trends, multi-year comparisons) often run from a reporting database refreshed on a schedule, so they do not slow the ERP.
- Reconcile reports to the ledger. Every financial report should tie to the trial balance, and should show that tie-out.
- Show the as-of time on every report and dashboard.
- Control access. Payroll costs, margins and bank balances need role-based visibility.
An illustrative example: a wholesaler wanted margin by customer but saw different numbers in the sales dashboard and the management accounts. The cause was that rebates were posted as a monthly journal, not against invoices, so sales margin ignored them. The fix was a definition change (margin after rebates), a rebate accrual per invoice, and one shared margin measure used in both places.
When is a custom reporting build not the right answer?
If your ERP's standard reports already tie to the ledger and the issue is that nobody uses them, train people and remove the spreadsheet copies first. A separate BI tool on top of a clean ERP is often enough for analytical reporting. Custom reporting work makes sense when definitions are complex (rebates, landed costs, project revenue), when data sits across several systems, or when the ERP's report tools cannot handle your dimensions. AI features can help explain variances, but they depend on the same clean data; see AI in ERP.
How to start improving your ERP reporting
Before any build, prepare:
- Your current month-end pack, with the reports people actually open marked.
- A list of spreadsheets finance maintains outside the ERP, and why.
- Draft KPI cards for the ten measures leadership watches most.
- Your chart of accounts and the dimensions you need reports by.
Add these to a short brief or an ERP RFP if you are selecting a new system. Then discuss the project with us. Timeline Digital builds 2 to 3 key modules as a free pilot before the full project, which for reporting work is often the ageing, cash and margin reports tied out against your ledger.