Can Reviewers Reconstruct a Payroll Correction?

Research question: Which combination of source reference, prior value, proposed value, effective period, reason, and approval evidence lets a reviewer reconstruct a payroll correction?

Methodology: Build thirty-six de-identified correction packets with seeded missing sources, inconsistent periods, duplicate requests, unclear approvals, changed attachments, and clean controls. Assign packets across three conditions: request message only, basic cover sheet, or versioned evidence packet. Reviewers record whether they can trace and disposition each item.

Scope and measures: The unit is one correction packet. Measure successful reconstruction, missed conflicts, duplicate detection, correct approval identification, unresolved status, and review time. The study examines documentary traceability, not payroll calculation.

Inference limits: Better reconstruction in this set would support the tested packet design only. It would not prove wage compliance, tax treatment, payment accuracy, employee identity, or provider performance.

Limitations and use: De-identified packets omit some integration history and may make sources easier to compare. A payroll owner may use the results to choose required packet fields. Coordinators may assemble evidence, while authorized payroll and finance owners keep interpretation, approval, and release authority.

Sources consulted: NIST Cybersecurity Framework 2.0 (https://www.nist.gov/cyberframework); NIST Privacy Framework (https://www.nist.gov/privacy-framework); U.S. Government Accountability Office, Standards for Internal Control in the Federal Government (https://www.gao.gov/products/gao-14-704g); Google Search Central, Article structured data (https://developers.google.com/search/docs/appearance/structured-data/article); Sitemaps protocol (https://www.sitemaps.org/protocol.html). These sources supply general control, privacy, and publishing concepts. They do not report results for Outsourced Employment, create legal or employment requirements, guarantee search indexing, or validate a live workflow.