Final pay evidence at separation: a completeness review

This study asks which required elements are present in a separation file at the moment the final paycheck is calculated. The elements are the last day, the separation type, the time and pay inputs, the deduction basis, the leave treatment, the calculation, and the approval. The result is intended to improve preparation and review, not to decide whether a particular final pay amount is legally correct. The scope is one employer or one defined operations group during a fixed period. The study may compare separation types, but it should not present a local completeness rate as an industry benchmark.

The population should be a frozen list of separations processed during the window, with the worker, the last day, the separation type, and the pay date recorded. Include separations that were corrected after the final pay, because the correction is part of the record. Exclude separations that were rescinded before any pay was calculated, and record the reason. The unit is one separation file at the final pay review. If the final pay is delivered in more than one payment, treat the file as one unit and record each payment separately.

Define each element before reviewing any file. The last day and separation type should come from the approved separation record. The time and pay inputs should come from the time system and the approved pay rate. The deduction basis should name the policy or authorization for each deduction. The leave treatment should cite the policy and the decision. The calculation should show the gross, the deductions, and the net. The approval should name the authorized owner and the date. Distinguish a missing input from an input that is present but inconsistent with another record.

Draw the sample from the frozen separation list using a documented method. Stratify by separation type, pay frequency, and location so the study does not overrepresent voluntary resignations. Include files that were corrected and files that were paid without correction. Record the selection method and any replacement. If the sample is small, report every file rather than a rate. A sample of only routine resignations will overstate completeness, while a sample of only disputed cases will describe failure modes without showing the base rate.

Two reviewers should score a calibration set before the main review. Compare their judgments on each element and discuss the files where they disagree. A disagreement about whether a deduction is authorized is common, and it should be resolved in the standard rather than case by case. Revise the definitions and repeat the calibration. During the main review, preserve the initial ratings and the adjudication. If the reviewers cannot agree, the problem may be the evidence standard rather than the file.

Collect the separation record, the time report, the pay rate record, the deduction authorization, the leave balance, the final pay calculation, and the approval. Record the document identifier and the date of each item. If a stage happened without a written record, collect the message or note that shows it. Do not reconstruct a missing date from memory. If the calculation cannot be reproduced from the inputs, mark the file as unverifiable rather than assuming the amount is correct. Keep the export with the study file.

Report the number of files reviewed and the number with each element present, partial, or missing. Show the result by separation type and pay frequency. Include the number of files with a deduction that has no documented basis and the number with a leave treatment that is not explained. Use counts and rates together, and state the denominator. A single completeness score can hide the difference between a missing time report and an unauthorized deduction. Report the corrections separately, with the time between the final pay and the correction.

Compare element rates across separation types and locations only when the subgroup is large enough. Inspect the files behind the largest gaps before assigning a cause. A cluster of missing deduction authorizations in one team may reflect a template that does not require one, while a cluster across teams may reflect a payroll practice that needs review. A cluster of late final pays may point to a slow approval rather than a calculation problem. The remedy should match the stage where the gap entered.

The study reviews the separation file and cannot determine whether the final pay was legally correct or whether a deduction was permitted. It also cannot confirm that the worker received the payment on time unless the bank or payroll record supports that conclusion. The result describes the sampled files, not every separation the employer processes. System changes, pay practice changes, and manual adjustments can affect the record. Note the relevant dates and avoid comparing periods as if the instrument stayed constant.

Use the minimum worker and pay information needed for the study. Replace names and account details with study keys, restrict access to the crosswalk, and follow the employer's retention rule. Do not copy bank information or identity documents into the analysis file when a reference to the approved record is enough. The operations coordinator may prepare the sample and check administrative fields. The payroll owner or authorized HR owner decides whether a deduction or leave treatment is allowed. The study should not be used to make a legal or tax conclusion about an individual.

Choose one change based on the most common or most consequential gap. It might be a required deduction basis, a named approver, a final pay checklist, or a reconciliation step after the first payment. Name the owner, the due date, and the measure that will show whether the change helped. Recheck the same measure with the next cohort. Keep a short decision log with the finding, the change, the owner, and the result.

A worker resigns and the final pay is calculated from the time report and the approved rate. The file includes the gross and net but not the basis for a benefit deduction. The leave balance is listed but the treatment is not explained. The reviewer marks the deduction and leave elements as partial and routes the questions to the payroll owner before the payment is released. The owner adds the authorization and the policy reference, and the calculation is rechecked. The example shows why a final pay file needs more than a number that looks right.

Review a sample after each hiring cohort and whenever a pay practice, benefit plan, or separation process changes. A quarterly review may be enough for a stable operation, while a monthly review is more useful during a reorganization or a high separation period. Record the cadence in the separation procedure. Between reviews, keep an exception log for final pays that were corrected. The log helps the team see whether the process is drifting before the next formal review.

A short table can show the result without exposing worker pay details. Use one row per file and columns for the separation type, the last day, the time input status, the pay input status, the deduction basis status, the leave treatment status, the calculation status, and the approval status. Add a notes column for a brief reason when an element is partial or missing. Keep the definitions beside the table so a reader can interpret the codes. Report the frame size, the sample size, and the number of excluded files. End with the one change the team will test and the date of the next sample. A reader should be able to move from the summary to a specific file and then to the source record.

The report should not say that a final pay was lawful or that a worker was paid correctly. It should say which inputs, authorizations, and approvals were present against the employer's standard. That distinction matters because a complete file can still contain a substantive error, and an incomplete file can be corrected before payment. The report also should not compare separation types as if their rules were identical. Keep the comparison inside the defined standard.