What an Auditor Asks For

General orientation, not legal advice.

The chain gets examined in a wage dispute, a statutory inspection and a financial audit. Each looks at a different part.

A wage dispute

One person, one period, the full chain: scheduled, actual, exceptions, classification, exported, paid.

Plus the rules in force at the time, which requires the rule register to be versioned.

And every correction with who made it and why.

If the chain cannot be shown end to end, the dispute turns on the person's account rather than on your records.

A statutory inspection

Records of hours actually worked, which is the time capture output rather than the schedule.

Rest and break compliance, which needs both scheduled and actual.

Retention, demonstrated across all systems rather than in one.

Evidence that workers can see their own records, which in several jurisdictions is part of the recording duty.

A financial audit

That labour cost reconciles between the operational systems and the ledger.

That the interface is controlled: who can change what crosses it, and is that logged.

Segregation of duties: the person who approves exceptions should not be the person who runs the pay file.

And that manual adjustments are documented, which is where the manual step register earns its keep.

What cannot be produced afterwards

The rule set as it was two years ago, without versioning.

Which system calculated a figure, without the register.

Whether an interface ran, without a delivery log.

Reference data structure at a past date, without effective dating.

Each costs nothing to capture continuously and is impossible to assemble later.

The self-audit

Take three people with complex pay and one closed period.

Reconstruct each payment from the raw records, following the register.

Time it.

Whatever you cannot answer, an auditor or a claimant's representative also cannot — and in the second case that works against you.

What to keep permanently available

Rule register versions with dates.

Interface delivery logs.

Reference data change dates.

Manual step register.

Reconciliation results, including the clean ones, because a series of clean months is itself evidence of control.

Keep the clean results too

A series of clean months is evidence of control.

Most organisations record the reconciliations that found something and discard the rest.

Which leaves no way to show the check was running in the periods where it found nothing.

Keep the result either way, dated, because an auditor asks whether the control operated, not only what it caught.

Reproduce the workflow

For another way to make this requirement testable, consult the form-based example. Reproduce the case with real roles, codes, failures and recovery steps.

Independent reference

For a thematic point of reference, see ISO. Use this established source as an outside check before turning the principle into a system rule.