How much evidence do we need before proposing a change?

Start with a representative reporting cycle, clearly defined activities and input from the people doing the work. If timing or workload varies materially, examine more cycles and explain the variation. A labelled estimate can support an initial investigation. A funding decision may need firmer evidence.

Can time saved be counted as a financial return?

Time released is capacity. It becomes a cash saving only where an identifiable expense will actually be avoided. If finance puts a cost on released capacity, keep that valuation separate from budget savings and do not count the same benefit twice.

Why involve IT if finance owns the reporting problem?

Finance defines the reporting need, the acceptable measures and the business priorities. IT enterprise or solution architects assess access, security, compatibility and ongoing operation. Including both helps the proposal account for the work needed to make the improvement repeatable.

Do we need to replace every ERP before improving reporting?

No. Begin by defining the required inputs and reporting rules. A common reporting workflow does not require every business unit to use the same ERP. The approach still needs to be evaluated against your systems, controls and implementation requirements.

What should we ask leadership to approve first?

Ask for the smallest decision that resolves the next uncertainty. That may be time to measure the baseline, access to evaluate representative inputs or a scoped pilot. State the resources, owner and decision criteria before seeking a broader commitment.

Should finance and sales figures always match?

Only when the reports show the same measure, period and scope. Sales bookings and recognised revenue can differ legitimately. What matters is an approved definition and an explainable relationship between the measures.

Who should investigate a reporting discrepancy?

The reporting lead can raise the issue, and finance managers and controllers can investigate the submissions. Involve IT enterprise or solution architecture when assessing platform fit and data flows. Confirm who owns definitions and financial policy separately.

How can data quality checks reduce repeated handling?

Check submissions against agreed rules before combining them. Find missing or invalid data, return failed submissions to the responsible team and track the corrected version. Standardisation and checks can reduce repeated spreadsheet handling, but the benefit depends on the process and the implementation.

How can finance investigate a variance when the explanation sits outside the financial system?

Compare the financial result with relevant operational information, such as planned resource start dates and onboarding progress. Where those datasets are loaded into CryspIQ® and mapped, finance can see how timing relates to actual spend. Check the explanation with the responsible team. The data comparison alone does not prove the cause.

How does data access work when asking CryspIQ® questions from Microsoft Copilot?

Each question runs under the person’s own Microsoft sign-in, not a service account. Access follows Microsoft Entra ID security groups, so people see only what they are allowed to see. The relevant datasets still need to be loaded and mapped in CryspIQ®. The Copilot integration is part of CryspIQ® v3.3.0, due for release in November 2026. Your Microsoft administrator connects Copilot to CryspIQ® once, and the CryspIQ® team helps with the set-up.

2 posts tagged with "Finance and Reporting"

Finance, forecasting and reporting — consistent numbers, variance and the business case for change.

View All Tags

How to build a business case for reducing repeated data and reporting work

October 28, 2026 · 13 min read

Dan Peacock

CEO

Build the case around one recurring workflow, measure the work honestly and ask leadership for a small, specific decision.

The short answer

Build the case around one recurring reporting workflow. Measure its current effort and delays, find the cause of the repeated handling, compare realistic options and include the full cost of change. Then propose a limited pilot with agreed success measures. Treat staff time released as capacity unless you can show a genuine budget saving.

Every month, someone on your finance team reformats a file, chases a correction and reconciles the result. The report goes out on time, so the work stays invisible. A business case makes it visible.

If you lead forecasting, planning and analysis, you may already see the problem. Finance managers and controllers know where the work happens. A useful proposal brings that knowledge together in a form that finance leadership and IT can evaluate.

Why do finance, sales and operations report different numbers?

October 5, 2026 · 14 min read

Dan Peacock

CEO

They count different events on different dates. Some differences are legitimate. The problem starts when nobody can explain how the figures relate.

The short answer

Finance, sales and operations report different numbers because they count different events, use different dates and apply different definitions and adjustments. Some differences are legitimate. A reporting problem starts when teams cannot explain how their figures relate, or when one agreed KPI is calculated in more than one way.

At month-end, finance collects actuals from subsidiaries that run different ERPs. Forecasts add another set of spreadsheets and CRM inputs. Before anything reaches leadership, finance has to bring the figures together, explain the differences and say why actuals moved away from the forecast.

If you lead forecasting, planning and analysis, or work as a finance manager or financial controller, you need data that is consistent enough to use and a way to spot the submissions that need correcting. Data and systems colleagues can help trace the technical causes.