Pay Changes and Overtime

Find pay above what was approved, and overtime far beyond an employee’s own pattern.

  • Ledger + payroll register
  • Key analysis in Payroll

How the result is read

Pay is approved twice: a salary in the HR file, and each change to it. Basic pay above the approved salary month after month, with no approved change on file, is an unlogged pay rise. Overtime is read against the employee’s own months, not a company average, so a spike stands out even for staff who always work some overtime; it must also be large against their basic pay to matter.

In the application

Pay Changes and Overtime is filed under Payroll, index letter H. "Run all analyses" runs it with every other analysis the ledger and the documents loaded can answer. The worksheet states the population it tested on its face — or "Not applicable" with the reason when a column it depends on is empty — and the Excel workbook the engagement exports files it under H, beside an index of the source files with their SHA-256 fingerprints.

Also listed in the application as Overtime Spike, Unlogged Pay Raise.

Run your next audit file test without the Excel crash.

One free engagement to evaluate, valid 60 days. The ledger never leaves the machine.

  • 20 minutes
  • Runs on a fictional engagement
  • No client data required

Cookie settings

This site sets no cookies. It keeps one preference in your browser's localStorage — the currency you chose on the pricing pages — and its analytics are cookieless, so there is nothing to opt in or out of.

View Cookie Policy