A payroll total can look reasonable while an employee is missing two hours, a pay rate changed on the wrong date, or a deduction ran twice. A payroll exception report brings those unusual items into one review queue so someone can explain or correct them before the payment file is released.
What is a payroll exception report?
A payroll exception report is a list of records that need attention because they are missing information, conflict with another record or differ from an expected result. It might include an incomplete timecard, a payment for an inactive employee or an unexplained jump in net pay. The point is to focus review effort on the items most likely to affect an accurate, timely payroll.
The report can be an export, a saved set of system reports or a controlled spreadsheet. Its value comes from the quality of the checks and the follow-through. A long list of red flags with no assigned reviewers is simply another unfinished task.
Keep three jobs distinct. A payroll register shows the calculated pay. An exception report identifies items requiring investigation in the current run. A broader payroll audit tests records, processes and controls over a wider period. Use the exception review every pay cycle; use the audit to examine whether the overall system is working.
Eight payroll exceptions to check before payday
Start with these checks, then add the conditions that matter to your workforce. Separate a confirmed error from an expected difference, such as an approved bonus. Both can trigger a flag; only one requires a correction.
| Check | What to investigate | Evidence to review |
|---|---|---|
| 1. Missing or overlapping time | An open punch, two overlapping shifts, or the same hours imported twice. | Original punches, employee explanation, supervisor confirmation and import history. |
| 2. Unreviewed timecards | Hours reached payroll without the required review, or an edit occurred after approval. | Approval status, last edit, reviewer and reason for the change. |
| 3. Unexpected hours or earnings | A large change from a comparable period, unexpected overtime, or a missing premium. | Actual work, applicable pay rules, approved leave and the earnings-code breakdown. |
| 4. Rate or effective-date changes | A new rate is absent, applied too early or used for the whole period instead of the relevant dates. | Authorized rate change, effective date and hours worked at each rate. |
| 5. Deductions and contributions | A duplicate deduction, unexpected amount, missed limit or employer contribution mismatch. | Applicable authorization, configuration, year-to-date values and eligibility dates. |
| 6. Unusual net pay | Zero or negative net pay, a sharp change, or a result that conflicts with the earnings breakdown. | Gross earnings, taxes, deductions, reimbursements and adjustments. |
| 7. Employee and payment changes | Unexpected pay for an inactive employee, a missing new hire, duplicate records or changed payment instructions. | Employee status dates, approved onboarding or termination records, and independently verified payment changes. |
| 8. Import and allocation mismatches | Rejected rows, unmapped pay codes, missing employees or hours assigned to the wrong department. | Source and destination control totals, rejection log and code mapping. |
A scheduled shift is useful context, but it is not proof of the hours actually worked. For U.S. employers covered by the relevant FLSA requirements, the Department of Labor explains that records must accurately reflect hours and wages, including actual hours when work differs from a fixed schedule. See its recordkeeping guidance. Treat an attendance-policy issue and the calculation of wages owed as separate decisions.
Build a report someone can act on
One row should represent one exception with a clear resolution path. Give it a stable ID so the team can discuss the issue without emailing entire payroll files. Use employee IDs where possible, and keep supporting payroll records in access-controlled storage.
- Context: pay period, run version, employee ID, location or department, and exception ID.
- The flag: check name, expected result or comparison baseline, actual result, and the difference.
- Responsibility: risk level, assigned owner, due time and escalation contact.
- Resolution: evidence reference, explanation or correction, reviewer, timestamp and final status.
Use explicit statuses: Open → Investigating → Corrected or Explained → Verified. “Explained” means the difference is valid and supported, such as a documented one-time payment. “Verified” means the reviewer checked the final calculation or record after the explanation or correction. Avoid closing a row just because someone sent a message.
Start with a blank exception log
Download a CSV header template with the fields above. It contains no employee information. Store completed logs securely; keep bank details, government identifiers and unnecessary personal information out of the log.
For a small team, a few well-defined checks may be enough to begin. As the payroll grows, automate the comparisons you can reproduce reliably. Keep the definition of each check alongside the report so two reviewers do not interpret the same flag differently.
Worked example: the total stayed the same, but two people were wrong
Consider a simplified weekly payroll with two hourly employees, each paid $25 per hour for 38 confirmed straight-time hours. A duplicate import adds two hours to Employee A. A missing time entry removes two hours from Employee B. The errors cancel at the payroll-total level.
| Record | Expected gross | Draft gross | Variance |
|---|---|---|---|
| Employee A | $950 | $1,000 | +$50 |
| Employee B | $950 | $900 | −$50 |
| Payroll total | $1,900 | $1,900 | $0 |
The exception review checks employee-level hours and earnings as well as totals. The reviewer confirms the source records, removes A’s duplicate entry and restores B’s missing two hours. The next calculation shows $950 for each employee. The run total remains $1,900, but the payments now match the confirmed work.
Record both exception IDs, link the supporting evidence, save the corrected run version and verify both employees’ results. Then reconcile the output totals to the approved payroll register. This example isolates straight-time gross pay to show offsetting errors; it excludes overtime, premiums, taxes and deductions. A real review must apply the relevant rules to each employee.
A repeatable payroll exception review workflow
1. Define the run and capture the inputs
Identify the pay period, pay date, included employees, time-approval cutoff and version of the preliminary calculation. Record when the exception checks ran. A screenshot or export without a run version may refer to figures that have already changed.
2. Review source issues before calculation issues
Resolve incomplete time, duplicates, missing employees and unmapped codes first. Recalculating payroll cannot repair missing source information. Ask the supervisor to confirm actual work and the payroll specialist to validate how the confirmed input should be paid.
3. Assign each flag to the right owner
Supervisors usually explain work and attendance records. Payroll reviews earnings, deductions and calculation settings. HR confirms authorized employee-status and rate changes. A designated payment reviewer independently verifies sensitive payment changes through an established contact method. Set a deadline that leaves time to recalculate and review.
4. Correct the underlying record
Where possible, fix the source entry or approved configuration that caused the problem. A one-time adjustment may sometimes be needed, but it should carry a reason, authorization and a link to the original issue. Otherwise the same error can return next period.
5. Recalculate and rerun the checks
Review the revised results, including previously cleared records affected by the change. A corrected rate can alter more than one earnings line. A late import can introduce new exceptions. Preserve the earlier run version and a concise explanation of what changed.
6. Approve the final output
Reconcile employee count and relevant hours, earnings, deductions and net-payment totals between the approved register and the payment output. Assign final authorization according to your internal controls. If an item remains unresolved, escalate it promptly and document the lawful, approved handling; do not let a review process cause wages to be withheld or paid late.
After payment, reconcile what actually processed and keep any corrections linked to the original exception. A rejected payment or post-payroll correction belongs in the follow-up queue even if the pre-release checklist was complete.
Set alert thresholds that reduce noise without hiding errors
Use completeness and validity checks for missing information, duplicates and invalid mappings. Use comparison thresholds to prioritize unusual amounts. A percentage change is useful for triage; it is not a legal tolerance or permission to ignore a known error.
For example, a team might investigate gross-pay changes exceeding both 15% and $100 compared with the previous comparable period. Those are illustrative internal thresholds, not recommended universal limits. Smaller known discrepancies still need correction. New hires, final pay, unpaid leave and bonuses often need a separate comparison because the previous period is a poor baseline.
Check the denominator before calculating percentage change: when previous gross pay is zero, report the dollar change and mark the percentage as not applicable. Compare periods with the same pay frequency and similar working days. Separate recurring pay from one-time earnings so a valid bonus does not obscure a missing regular-pay line.
Review recurring flags monthly. If a valid condition is repeatedly cleared, improve the rule or baseline while keeping the evidence requirement. Track how many flags led to corrections, which exceptions recur and how long open items take to resolve. Lower flag counts are useful only when the checks still find the problems that matter.
Connect attendance review and payroll in TimeTrex
The strongest exception process connects the hours recorded, the approvals and the pay calculation. TimeTrex’s time and attendance software and payroll software support that connected workflow, helping teams review the records behind a payroll result.
Start by identifying the time, pay and approval reports available in your edition and configuration. Define which checks each report supports, who reviews it and how the results connect to the final payroll register. Report names and available options can vary; the exception log in this guide is an operating template, not a claim that every check appears in one prebuilt TimeTrex report.
When evaluating the workflow, test a missing punch, a duplicate import, a mid-period rate change and an expected one-time earning. Ask the reviewer to trace each result to its source and demonstrate the approval process. That exercise reveals more than a demonstration using only perfect timecards.
Make the next payroll easier to review
Discuss your timekeeping, approval and payroll requirements with TimeTrex, including the exceptions your team needs to see.
Discuss your payroll workflowPayroll exception report checklist
Use this as a final review aid for the current run. It resets when the page reloads and does not store payroll information.
0 of 6 review checks complete.
Frequently asked questions
How often should you run a payroll exception report?
Run it every payroll cycle after time approval and the preliminary calculation, then again after corrections or late changes. Leave enough time before payment release for owners to investigate and reviewers to verify the final output.
Does every payroll exception mean an error?
No. An approved bonus, a new hire or a planned deduction change can trigger a valid flag. Document the explanation and evidence, then verify the result. A flag is a request for review, not a conclusion.
What is the difference between a payroll variance report and an exception report?
A variance report compares amounts across periods, budgets or systems. An exception report can include those differences plus missing records, invalid codes, duplicate imports and approval issues. Use variance analysis as one part of the exception review.
Can a small business use a spreadsheet for payroll exceptions?
Yes, provided it has clear check definitions, controlled access, assigned reviewers and an evidence trail. Keep it linked to the payroll run and reconcile it to the final output. Avoid unnecessary personal information and move repetitive comparisons into reliable system reports when practical.
What should happen when an exception is still open near payday?
Escalate it to the authorized payroll decision-maker immediately. Confirm the facts, applicable requirements and payment deadlines; document the approved handling and follow-up. An unresolved alert is not a blanket reason to delay wages or substitute scheduled hours for actual work.
Sources and scope
Product references: TimeTrex Time & Attendance and TimeTrex Payroll. U.S. recordkeeping reference: U.S. Department of Labor Fact Sheet #21. Reviewed October 21, 2026.
This guide provides operational education, not legal, tax or accounting advice. Examples and alert thresholds are illustrative. Apply the rules, agreements, pay deadlines and recordkeeping requirements relevant to your workforce, and seek qualified advice where needed.
