Reconcile a report with its source

What you will learn

Explain a mismatch using a small controlled dataset.

Prerequisites: IFS Cloud essentials. No IFS login is needed for this written exercise. Estimated reading time excludes practice.

The concept

A total is trustworthy when its inputs and transformations can be explained. Operational reporting separates data assembly from formatting; investigating an incorrect number should therefore begin with the records and calculation, not only the visual layout.

A worked scenario

A report total is 300 while a manual list totals 260. Rather than adjusting the report to match, compare both populations. One may include a 40-value cancelled item or the two may have been produced at different times.

Work through it

1. Use the same environment, time window, parameters, and authorized role.
2. Compare record identifiers before comparing aggregate totals.
3. Check duplicated rows, excluded states, nulls, rounding, and units.
4. Document each difference and rerun using an agreed baseline.

Try it yourself

Reconcile values 120, 80, and 60 against a report showing 300.

See a suggested answer

The visible values total 260. Look for an extra 40, a duplicate or transformed amount, or a different input population. The 40 difference is evidence to investigate, not proof of a particular defect. Capture the final explanation with record-level evidence.

Check your understanding

Changing a filter until the totals agree without explaining why those records belong in or out.

Expected result: a written answer that explains your decision and identifies what still needs confirmation in the actual environment.

Cleanup: none; this exercise changes no IFS data.

Sources and review status

IFS Cloud 26R1 documentation. Source consulted 2026-09-23. The scenario and exercise are original fictional examples. This concept draft has not been reviewed by an IFS specialist or executed in an IFS environment.

Apply this lesson in the handover-reference project.