What is being tested
Did off-cycle payroll runs incur only the separately authorized run charges? The boundary for this investigation is payroll software off-cycle run fees. Begin with the disputed transaction or population, then identify which payroll run identifiers establishes the observed position and which run-type summary supports the comparison. A difference in totals should not replace this question.
Evidence: payroll run identifiers
For payroll software off-cycle run fees, payroll run identifiers must be linked to run-type summary. Retain stable identifiers and their effective relationships. Current labels are insufficient when assets or accounts changed during the period. Explain one-to-many relationships explicitly and preserve the history needed to distinguish an alias, replacement or reassignment from a genuinely additional item.
Evidence: run-type summary
For payroll software off-cycle run fees, run-type summary must be linked to off-cycle fee clause. Document the observation window, units, inclusion criteria and export version. Identify gaps and corrected events before using the total. Keep raw observations separate from derived quantities so a reviewer can reproduce the population without assuming every logged event is independently chargeable.
Evidence: off-cycle fee clause
For payroll software off-cycle run fees, off-cycle fee clause must be linked to payroll software invoice. Retain the applicable wording, effective dates and scope of covered transactions. Identify the event or population that controls the calculation. Do not silently replace a contractual definition with a dashboard label, customary practice or the latest published rule.
Evidence: payroll software invoice
For payroll software off-cycle run fees, payroll software invoice must be linked to payroll run identifiers. Keep the issued document version and line-level quantity, currency and service period. A header total cannot establish which component is being tested. Retain later corrections as linked versions, so a replacement does not create a second liability.
Reconciliation logic
Match billed run counts to accepted run events and distinguish corrected reruns from separately requested payments. Build the comparison at the level identified by payroll run identifiers and retain the governing version from run-type summary. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
An additional approved payroll can be a valid paid run. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked payroll run identifiers, run-type summary, off-cycle fee clause, payroll software invoice. Document the conflicting input or rule. A plausible operational explanation requires validation, but it should not be discarded to maximize an apparent financial difference.
Human review and outcome
Payroll administration validates run type using minimized aggregate records. Return a run-classification schedule without processing employee payment details. Keep the reviewer's reason and source references with that disposition. A supported correction should be followed to the revised record or settlement; an accepted explanation can close the question with no adjustment. Missing authority or evidence should remain an open task rather than a confirmed recovery.
Limitations and processing boundary
Do not infer license removability from activity alone or describe a proposed configuration change as confirmed savings. The authoritative spend, license and contract producer is not complete; customer evidence and processing validation are prerequisites to production conclusions. In this scenario, absence of payroll run identifiers or run-type summary limits whether the comparison can be completed. The review method describes what people should validate, not a promise that AuditRes automatically detects or executes this specific outcome.
AuditRes pathway
Discuss payroll software off-cycle run fees in the Technology Spend workspace. Review current plans, the shared platform and secure evidence requirements; use the existing contact path to confirm the sources and validation this scope requires.
AuditRes Technology Spend: Available for onboarding. Public previews use synthetic demonstration data; production processing remains gated until applicable customer sources and authoritative processors are connected and validated.
Neighboring financial questions
- AI inference retries and duplicate workload cost investigation
- Ecommerce software order-cancellation transaction fees
- AI tool-call fees separate from model usage
- Log archive restoration versus query scanning fees
Technology Spend resource hub · All guides in this evidence collection