Building an evidence index auditors can reuse

Auditors rarely ask for “everything.” They ask for paths: from a payroll total to a remittance, from a remittance to a ledger line, from a ledger line to an application extract. An evidence index makes those paths visible before the first request arrives.

Minimum columns that help

For each artefact, record: period covered, system of origin (payroll application, bank portal, financial audit application), owner, location or link, and sensitivity. Add a one-line note on known limitations — missing exports for a month are better declared than discovered live.

Group by question, not by folder habit

Organise around the questions you expect: statutory contributions, overtime, leavers, PCB, and payroll-to-ledger reconciliation. Inside each group, place the analytics extract beside the matching journal support. Folder trees built by “HR vs Finance” often hide the join.

Version the closed period

Label packs with the pay cycle close date and the date the pack was frozen. If someone regenerates an export after a prior-period adjustment, the index should show which version auditors received.

Where CogniConnect Digital fits

Our pre-audit readiness review often produces the first version of this index with your team. You keep the structure after we leave; it is not locked inside a proprietary portal.