What belongs in the evidence trail of a compliance reporting application

An application audit of a compliance reporting application spends most of its hours on evidence: not the policy binder, but the artefacts the system keeps when someone approves, overrides, or recalculates a figure.

Minimum useful trail

For each material adjustment, the trail should show who acted, when, on which pack version, and what the figure was before and after. If the application only stores the final number, owners are forced into side spreadsheets that examiners distrust.

Common weak spots

• Override screens that log a user but not the reason code
• Recalculation jobs that replace outputs without retaining the prior pack
• Evidence folders that allow silent deletion after filing
• Maker-checker steps that can be completed by the same credential under a shared account

Practical test before you invite auditors

Pick last quarter’s largest late adjustment. Ask a colleague who did not process it to reconstruct the story from the application alone. If they need hallway knowledge to finish the story, your trail is incomplete — and a full audit will say so.