The first week of an application audit moves faster when materials arrive together. Waiting for calendars after configuration exports are already under review creates idle days neither side wants.

Gather before the kickoff

  • Application name, version, and list of modules in live use
  • Current pay calendar and public holiday table loaded for the year
  • Glossary of company-specific allowance and deduction codes
  • Anonymised payslips from at least three closed months, including one atypical month
  • Name of an administrator who can answer configuration questions within two business days

Decide masking rules early

Agree which personal identifiers will be replaced. Keep hours, rates, grade codes, and cost centres readable enough to recalculate edge cases.

Tell us about pending changes

If a version upgrade, merger, or policy rewrite sits on the calendar, say so during scoping. Sampling against a configuration that will be retired in three weeks wastes effort.

Book the people, not only the files

Findings workshops work best when payroll, HR operations, and finance can sit together for ninety minutes. Reserve that slot when you confirm the engagement start date.