A monthly return needs a daily evidence trail.

Begin with a field map

For each reported field, record the source, entity, currency, cut-off, transformation and reviewer. Keep the mapping versioned. It should be possible to explain a changed number without rebuilding the whole report from scratch.

Separate a calculation from a judgment. A total can be mechanically derived, while deciding whether a balance belongs in that total may require an assessment under the applicable rules. Preserve the reasoning and approval for that assessment.

Assign preparation and challenge

Name the preparer, reviewer, submission owner and backup. Define what the reviewer actually checks. “Reviewed” is not informative if it means only that the file opened successfully. Useful checks include reconciling totals to the retained source records and understanding differences from the previous period.

Retain the submitted version

Keep the final submission, acknowledgement, supporting calculations and any subsequent correction together. Do not overwrite the version that was sent. A corrected figure needs a record explaining what changed and why.

Submitting a return does not demonstrate that every underlying safeguarding control is effective. The report, reconciliations, issue log and assurance work should form connected but distinct records.