A 6-point reporting health check for Business Central

2026-07-14 · 5 min read

You don't need a project to find out whether your reporting is healthy. Six questions will do it, and you can answer them in ten minutes.

A six-point reporting scorecard covering: reports without exporting, a close measured in hours, figures that agree, self-service for non-finance staff, live dashboards, and whether the reporting tool is actually configured.Six questions that tell you where you stand1Core reports without exporting to Excel?2Does month-end close in hours, not days?3Do the same figures agree everywhere?4Can non-finance staff self-serve numbers?5Are dashboards live, not last month?6Is your reporting tool actually configured?Mostly yes: healthy. A few no: quick wins. Mostly no: it is costing you.

The six checks

1. Can you get your core reports without exporting to Excel?

Good: the pack refreshes from live data. Bad: someone exports and rebuilds monthly. If bad, start here — it's the highest-return fix and we cover it in stop exporting to Excel every month.

2. Does month-end close in hours, not days?

Good: two to three working days for a business of your size. Bad: a week or more, most of it manual. A slow close is usually a reporting problem in disguise.

3. Do the same figures agree wherever you look?

Good: the dashboard, the pack and the ERP agree. Bad: the answer depends on who ran it. This is the most corrosive failure — it undermines trust in every number, including the correct ones.

4. Can non-finance staff self-serve the numbers they need?

Good: operations can answer their own questions. Bad: everything routes through one person in finance, who becomes a bottleneck and a risk.

5. Are dashboards live, not last month?

Good: current data, refreshed automatically. Bad: a slide someone updates manually. Decisions on stale data look fine until they don't.

6. If you own Jet Reports, is it actually configured?

Good: reports built, data sources sound, more than one person can maintain them. Bad: licensed, installed, barely used. This is more common than vendors admit — the tool gets bought, the configuration never gets finished.

Scoring it

  • Mostly yes — you're in good shape; focus on keeping definitions documented
  • A few no's — there are quick wins, usually in reporting setup rather than software
  • Mostly no — reporting is costing you real time, and probably real decisions
Notice what isn't on this list: which product you own. In our experience the product matters far less than whether it was ever set up properly.

What to do with a bad score

Resist the urge to change tools first. Work in this order: agree definitions, fix the highest-frequency manual report, then automate refresh, then extend self-service. Tool changes belong at the end of that list, if at all — and quite often the list resolves the problem before you get there.

Frequently asked

We scored badly but just bought new software. What now?
Finish the configuration before judging the tool. Most disappointment with new reporting software is unfinished setup, not the product.
How often should we re-run this check?
Annually, or after any major change — new finance lead, restructure, acquisition, system upgrade.
Is a three-day close realistic?
For most SMEs on a well-configured system, yes. It needs clean cut-off discipline as well as good reporting.
Who should answer these questions?
Ideally finance and IT together, separately first. Where their answers differ is usually where the real problem is.
Book a free reporting review

Book a free reporting review

← All insights