Research note
How often do payroll input changes arrive without a source document?
A measurement design for counting payroll input changes that lack a source document and separating a missing file from a missing approval.
Published

Table of contents
Question and scope
This study asks how often a payroll input change reaches the payroll desk without a source document that supports the change. It treats the change as the unit and the source document as the evidence standard. The scope is one employment operations team and a fixed number of pay cycles. The result describes that team and should not be read as an industry benchmark.
The unit is one payroll input change tied to one employee and one pay period. A change is eligible when it affects pay, deductions, or tax treatment. Routine informational updates are excluded. Record the inclusion rule before reviewing so the denominator is not built from the easiest cases.
Record whether the change was initiated by the employee, the manager, or the payroll team. A change initiated by payroll may have a different evidence path. Report the initiator with the result. That variable helps separate an intake problem from an internal correction.
Definitions and evidence standard
Define a source document as the record that authorizes or explains the change, such as a signed rate letter, a time report, a termination notice, or an enrollment record. A chat message may be a request but is not a source unless the policy recognizes it. A change without a source is not necessarily wrong, but it is not verifiable. Record the decision and the date so the next reviewer can follow the same reasoning.
Separate a missing document from a missing approval. A change can have a source but no authorized approver, or an approval but no supporting record. Code the two gaps separately. A combined missing-evidence rate hides which control failed and what the team should repair.
Record whether the source was created before or after the change was requested. A document created after the request may be a reconstruction rather than the original evidence. Report the timing with the evidence category. That distinction matters when the team reviews the cause.
Sampling and measurement
Draw the sample from completed pay cycles and freeze the list before review. Include changes from more than one requester and more than one change type. If the team has a seasonal peak, report the peak and off-peak periods separately. Record the number of changes and the number of employees affected.
Measure the number of eligible changes, the number with a complete source, the number with a partial source, and the number with no source. Add the number with a missing approval. Report the counts by change type and by requester. A rate without these counts can make a small sample look more precise than it is.
If a change has more than one source, record the primary source and the secondary source. A rate change may have a letter and a system update. Report the pair rather than counting the change twice. The primary source should be the one the approver relied on.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of missing sources in one change type may mean the intake form does not require it. A cluster under one requester may mean the approval route is unclear. A cluster in one pay cycle may mean a cut-off or a staffing problem. Read the actual changes behind the largest cluster before naming a cause.
Compare the missing-source rate with the time the change arrived before the cut-off. A late change may be missing evidence because there was no time to collect it. A change that arrived early and still lacks a source may point to a habit or a form design. Report the timing with the result and avoid treating every gap as carelessness.
Compare the missing-source rate with the number of approvers in each change route. A route with several approvers may have more chances to lose the document. Report the count beside the rate. Do not compare a simple change with a multi-step approval as if they carried the same risk.
Limitations
The study sees recorded changes, not every conversation that produced them. A source may exist outside the payroll file and still be valid. The study also cannot decide whether a change was legally correct or whether the employee was paid properly. Those questions need a substantive review.
The window may include a system migration or a policy change that affects the evidence standard. If the payroll system changed during the period, the records may not be comparable. Record these limits with the result and keep the source extracts with the method. Keep the supporting evidence with the case rather than in a separate note.
Compare the missing-source rate with the number of changes per pay cycle. A heavy cycle may produce more gaps without any change in behavior. Report the volume beside the rate. If volume explains the pattern, the repair may be staffing or sequencing rather than a new form.
Practical next step
Choose one control that matches the most common gap, such as a required source field, a named approver, or a pre-cut-off reminder. Write the change, the owner, and the start date. Define the measure that will show whether it helped, using the same evidence categories. Test it on the next set of changes.
Keep the before and after changes separate so the comparison is honest. Record the changes that were excluded and why. Review the result with the payroll owner and the requesters. If the change does not help, record that result too. The purpose is to learn which control improves the evidence, not to blame the person who sent the request.
Test the checklist on one change type before applying it to every payroll input. A form that works for a rate change may not fit a termination. Record the test group and the result. A type-specific control is easier to verify than a broad policy change.
Comparing change types
Different change types carry different evidence expectations. A new hire may require a packet of documents, while a hours correction may require only a time report. Report the count and the rate for each type, and label small groups as descriptive only. A type that looks worse may simply have more requirements.
If one type shows a consistent gap, check whether its form or route collects the right evidence. A type that depends on a manager's letter may fail because the letter is not standardized. Compare the process, not the requester. The next study can test a type-specific form before applying it to every change.
Keep the source extracts in a restricted workspace because they may contain pay and identity details. Publish only the aggregate counts and the change categories. If a client asks for the result, describe the method and the control rather than sharing raw records. The study is an internal evidence tool, not a client-facing audit.
What the evidence does not show
The study does not establish that a missing source caused a wrong payment or a compliance problem. It also does not measure whether the approver had authority. Those are separate questions. A missing document is a records observation, not a legal conclusion.
Do not use the result to promise a client that every payroll change is documented or that no error will occur. Do not publish employee names or pay details. Keep the sample size, the evidence definitions, and the review decisions with the result. If the firm needs a compliance conclusion, it should ask the responsible owner.
Ask the payroll owner which missing source would be most serious if it reached the register. That answer helps the team prioritize the repair. Report the priority with the category. Not every gap carries the same risk.
Using the result in a client conversation
A client may ask how the team controls payroll input, and the study supports a careful answer. Describe the window, the number of changes, the evidence standard, and the control that was added. Do not say that every change is documented or that no correction will ever be needed. Explain that the measure covers recorded changes and that payroll reviews open items.
If the client asks for a commitment, offer a process commitment such as a source field, a named approver, and a pre-cut-off check. Record the commitment and the measure that will show whether it was met. Keep client-specific details out of any public write-up. The study is an internal control tool, not a guarantee about any pay cycle.
Keep the evidence extracts in a restricted workspace because they contain pay and identity details. Publish only the aggregate counts and the change categories. If a client asks for the result, describe the method and the control rather than sharing raw records. Review the result with the process owner before changing the rule.
Sources
References supplied with this research note.
| Source | Publisher | Context |
|---|---|---|
| U.S. Department of Labor, Fair Labor Standards Act | dol.gov | Primary reference supplied with this article. |
| U.S. Department of Labor, Recordkeeping | dol.gov | Primary reference supplied with this article. |
| Internal Revenue Service, Publication 15 | irs.gov | Primary reference supplied with this article. |
| NIST Cybersecurity Framework 2.0 | nist.gov | Primary reference supplied with this article. |