Payroll Import Validation: Checklist & Control Totals

Roger Wood — Tue, 27 Oct 2026 18:41:32 +0000

Payroll Import Validation: Checklist & Control Totals

A payroll file can import successfully and still contain the wrong hours. Payroll import validation compares the approved source, the file you send and the records your payroll system actually accepts. Check all three before releasing the payroll.

Start with a three-way comparison

Confirm the pay period and employee population, match employee IDs and earning codes, reconcile hours by employee and code, then review the destination results. Keep the batch reference and resolve rejected or duplicate rows before retrying.

This checklist is for a recurring handoff from time and attendance to a separate payroll provider. The controls and fictional example below are a suggested operating procedure. Adapt them to the destination's current import specification and your approval process.

Define exactly what this batch contains

Write down the company, pay group, period start and end, intended payroll date, export time and person responsible for the transfer. These details prevent a valid file from being loaded into the wrong run. Give the batch an internal reference, such as OPS-2026-10-B-v1; this is an example naming convention, not a required TimeTrex field.

Freeze an approved source snapshot for the comparison. If a manager corrects time afterward, record the change and create a controlled revision rather than silently replacing the file. Use the same population and period filters for every report used to reconcile the batch.

Identify deliberate exclusions. A salaried employee whose hours are not sent, a new hire awaiting setup and a worker paid in another pay group need different treatment. A list of excluded IDs with reasons is more useful than a single expected headcount. Assign someone to resolve each exception before the payroll deadline.

Check employee IDs, codes and units

A mapping is the agreement between a source field and a destination field. Review it whenever the provider, file format, employee numbering, earning codes or costing structure changes. Save the version used for each batch.

Employee identity: confirm that each source identifier matches the correct active destination record. Preserve leading zeroes, and check transfers, rehires and new employees individually. Names alone are a weak matching key.
Earning codes: verify regular, overtime, paid leave and each premium separately. Do not assume that similarly named codes calculate pay the same way.
Time units: distinguish decimal hours from hours and minutes. Seven hours and thirty minutes is 7.50 decimal hours; a value of 7.30 decimal hours is seven hours and eighteen minutes.
Amounts and rates: establish which system calculates earnings and where rates come from. A premium may be an additional amount or a separate earning; confirm the destination's treatment before mapping it.
File structure: check required columns, header rows, date formats, delimiter, character encoding and allowed precision against the selected import format.

Confirm whether an overtime entry expects hours at an overtime earning code, a separate premium, or a precomputed amount. Sending both a full overtime earning and another premium without understanding the specification can overstate pay. This is a configuration check; applicable wage rules and payroll calculations still need their usual review.

Use control totals at more than one level

Keep a small control sheet beside the file. Record the approved source value, exported value, accepted destination value, difference, explanation and reviewer. Use the same units and level of detail in all three columns.

Batch control sheet template

Batch and mapping version: Company / pay group / period / file name / revision / export timestamp.
Population and detail: Expected employee IDs / actual distinct IDs / expected row structure / rejected rows.
Hours and earnings: Totals by employee and earning code; compare amounts and rates only when the file supplies them.
Disposition: Difference / cause / correction owner / destination batch reference / reviewer approval.

Row count is not employee count. One employee may have several earning-code, date or job rows. Compare distinct employee IDs separately from detail rows. If the source is daily and the destination is summarized, aggregate both to employee and code before comparing.

Check an overall hours total, totals by earning code and employee-level totals. Add department or job totals when the file carries labor distribution. Matching a grand total does not prove that hours reached the right person or pay category.

Define precision before testing. Compare the source using the destination's documented decimal precision and record any rounding difference. Do not invent a blanket tolerance that can hide a missing row. A difference that has no explained cause remains an exception even when it is small.

Worked example: the total matches, but the import is wrong

Assume a fictional batch contains three employees and 120.00 approved hours. Each employee has one regular row and one overtime row. The intended file therefore contains three distinct employees and six detail rows.

Fictional source and accepted hours
Employee	Source regular	Source overtime	Accepted regular	Accepted overtime
A101	38.00	2.00	40.00	0.00
A102	36.00	4.00	36.00	4.00
A103	40.00	0.00	40.00	0.00
Total	114.00	6.00	116.00	4.00

Both sides total 120.00 hours. The destination nevertheless has 2.00 extra regular hours and 2.00 fewer overtime hours. Employee A101's code-level comparison exposes the mismatch. Investigate the mapping and accepted detail before correcting the batch; a successful upload message would not resolve it.

The file's structure is another control. If the destination suppresses zero-hour entries, its accepted row count can be lower than the source's six detail rows. That difference can be explained only after confirming that all three employees and every nonzero earning row are present. Do not force unlike row structures to match by deleting legitimate detail.

After the hours reconcile, review the payroll preview for expected earning treatment and unusual pay results. Use a broader payroll exception report for the rest of the run. Hours validation does not establish that taxes, deductions, rates or net pay are correct.

Handle rejected rows and uncertain retries

When an import reports an error or times out, first inspect the destination batch history and accepted detail. Determine whether nothing loaded, some rows loaded, or the full batch loaded despite the missing confirmation. Preserve the original response and file.

Find out whether the destination appends, replaces or updates records on a second upload. Never assume that the same file name makes a retry safe. If some rows were accepted, use the provider's supported correction or reversal process, or a confirmed file containing only unresolved records. Reconcile the final combined result to the approved source.

Watch for plausible duplicate keys: employee, period, earning code, date and job may identify an unintended repeated line. The same employee and code can also appear legitimately on several rows, so investigate the file's intended grouping before removing anything.

Keep a short incident note: what was accepted, what was rejected, the correction made, the replacement batch reference and who verified it. If the result is still uncertain, escalate to the payroll owner or provider while preserving the current batch. An unexplained retry can create a second problem on top of the first.

Payroll import release checklist

Use these checks for the batch review. The boxes are an on-page working aid and do not save an approval record.

The company, pay group, period and approved source snapshot match this run.Employee IDs, earning codes, units and mapping version have been checked.Expected employees, detail rows and documented exclusions reconcile.Hours match by employee and code; any precision differences are explained.Accepted, rejected and previously loaded records have been reconciled without duplicate uploads.The destination payroll preview and evidence package have a named reviewer.

Retain the source snapshot, exact transmitted file, control sheet, import response and final destination report under your organization's access and retention rules. Store employee-level payroll data in approved systems rather than attaching it to broad email chains.

Where this fits in a TimeTrex workflow

TimeTrex's Payroll Export Report exports time and earnings for a selected period to third-party payroll software. Its templates allow different employee, date, department and pay-period groupings. Choose a grouping that supports the comparison you need.

The payroll export instructions describe selecting an export format, configuring provider-specific fields and mapping hour codes. Confirm the exact receiving product and import specification; a general integration listing does not establish the field requirements for your account.

If you process payroll inside TimeTrex, the documentation says this third-party Payroll Export Report is unnecessary. Use the appropriate internal timesheet and pay-stub reports instead. For a separate provider, compare the export with its accepted results and preserve the final review evidence.

Review the complete handoff

Explore TimeTrex time and attendance and integration options. Bring a sanitized sample file, your earning-code map and the destination import specification when discussing your workflow.

Explore TimeTrex

Frequently asked questions

Does a successful import mean payroll is correct?

Timesheet Approval Backup Plan: Checklist & Handoff Template

Roger Wood — Tue, 27 Oct 2026 16:14:08 +0000

Timesheet Approval Backup Plan: Checklist & Handoff Template

A timesheet approval backup plan names who reviews time when the usual manager is away, which employees they cover, and what must reach payroll before cutoff. Put those decisions in writing and test access before the absence begins.

The practical starting point

Assign one accountable backup for each team and pay period. Give that person a short handoff listing pending timesheets, unresolved corrections, review deadlines and the escalation contact. Close the handoff by checking the actual approval status, including any timesheets changed after review.

1. Define exactly what the backup owns

“Please cover my approvals” leaves too much open. A replacement supervisor may see several teams, several request queues and more than one pay period. Specify the employee group, coverage dates and review tasks. Distinguish timesheet review from leave requests, punch corrections and final payroll release.

The absence window and the payroll period are separate fields. A supervisor can be away for three days while the review covers two weeks of time. Record both, together with the time zone for each deadline. This makes the handoff usable across branches and avoids a last-minute argument about which cutoff applied.

Primary backup

Owns the review queue during the coverage window, follows up on missing information and sends the status update to payroll.

Escalation owner

Resolves questions the backup cannot decide, arranges authorized coverage if the backup is unavailable and confirms the handling of outstanding items.

Name the person responsible for reviewing the absent manager’s own timesheet as well. Covering a team does not automatically assign review of the supervisor’s hours. Where your internal controls require a separate reviewer for a person’s own changes, preserve that arrangement during the absence.

Use the organization’s existing payroll cutoff policy to set the deadline. Avoid creating a second cutoff that conflicts with the payroll team’s processing plan.

2. Test the approval route before the manager leaves

Test with the backup’s own account. Ask them to locate a representative employee and the relevant period, open the pending review and confirm who receives any next step. Viewing a timesheet is not enough to prove that the person can complete the required authorization.

In TimeTrex, check both the hierarchy configuration and the backup’s permission group. The hierarchy identifies the supervisor relationship; permissions determine available actions. Have the administrator verify the intended scope and test the result. The documentation recommends consulting support when modifying permissions.

A backup may already have the required access. If a change is needed, record its owner, scope and planned end date through your normal access process. Check a team inside the coverage scope and an unrelated team outside it. Use named accounts so the review remains attributable to the person who performed it.

Keep request routing distinct from timesheet approval.

TimeTrex documents higher-level coverage behavior for requests in its hierarchy guide. Confirm the applicable timesheet authorization route in your own configuration before relying on that behavior for time review. Do not assume every object follows an identical approval sequence.

Include a short practice handoff before a planned absence. The normal manager can explain one open issue while the backup finds the record and identifies the next action. This reveals missing context much earlier than a reminder sent on payroll morning.

3. Copy this timesheet approval handoff template

Keep the handoff in the team’s approved shared location. Link to the underlying records rather than copying unnecessary employee information into an email or a personal spreadsheet. Update the queue summary when an item changes owner or status.

Team / employee group: [Coverage scope]

Pay period: [Start date] through [End date]

Coverage window: [Start date and time] through [End date and time, time zone]

Normal approver / named backup: [Names and work contact route]

Escalation owner: [Name and contact route]

Review deadline / payroll cutoff: [Separate deadlines, time zone]

Queue at handoff: [Expected timesheets; authorized; ready for review; awaiting correction; not yet submitted]

Open items: [Record reference, issue, owner, next action, due time]

Access test: [Who tested, when, employee group and observed result]

Status update: [Where and when the backup reports to payroll]

Return handoff: [Remaining items, late changes and temporary access review]

Use status labels that describe evidence. “Awaiting employee response” is more useful than “in progress.” “Authorized at 10:15, then changed at 10:40; review reopened” is more useful than a permanent checkmark beside the employee’s name.

The handoff supports review; the saved timesheet and its current authorization status remain the operational record. Reconcile the summary with the live system before declaring the team ready for payroll.

4. Worked example: covering a 24-person team

This fictional example shows how to reconcile a review queue. It does not set a required approval timetable or payroll rule. A warehouse supervisor is away Thursday and Friday. The backup owns review of 24 employee timesheets; payroll requests a status update Friday at 11 a.m. in the branch’s stated time zone.

Queue at Thursday’s handoff
Current status	Timesheets	Backup’s next action
Already authorized	14	Watch for later changes; avoid repeating completed work.
Ready for review	6	Review the records and resolve or route questions.
Awaiting correction	3	Follow the named owner and due time for each issue.
Not yet submitted	1	Contact the employee and check for a submission blocker.

The opening check is 14 + 6 + 3 + 1 = 24. Each timesheet belongs to one current status, so the count reconciles to the team. The backup reviews all six ready items, then reviews two corrected records and the newly submitted record. That leaves 23 authorized and one unresolved.

Before the Friday update, an authorized record changes. Its authorization must be checked again. In this example the dashboard now shows 22 authorized, one awaiting renewed review and one unresolved correction. The total is still 24. A summary that simply added nine approvals to Thursday’s total would miss the reopened item.

The backup resolves and reauthorizes the changed record, then escalates the last correction with its record reference, known facts, owner and next action. Payroll receives a clear status of 23 authorized and one outstanding. An outstanding approval should trigger the organization’s timely-pay and correction process; it should not become an undocumented reason to omit known work.

5. Handle cutoff, late corrections and the return handoff

Use a short queue review at an agreed time before cutoff. Check missing submissions, unresolved exceptions, records waiting for employee verification and timesheets changed after approval. Give each outstanding item an owner and a due time. If the backup cannot establish what happened, escalate the evidence gap instead of guessing a punch or copying scheduled hours as actual work.

TimeTrex’s timesheet authorization guide explains that edits after verification or authorization clear the authorization and require employee re-verification. Recheck the resulting workflow after a correction, especially near the deadline. A screenshot of yesterday’s completed queue cannot establish today’s status.

When the manager returns, provide the remaining item list, important decisions and records changed during coverage. Confirm which person now owns follow-up. Ask the administrator to review any temporary access arrangement at its planned end, then close the coverage record after the handoff is acknowledged.

Keep the first return review brief: Did the backup find the right employees? Were pending items visible? Did a correction reopen review as expected? Which question required knowledge that should have been documented? Use the answers to improve the next handoff.

6. Approval coverage checklist

Use these checkboxes for a review session. They reset when the page reloads; keep the completed handoff in your approved record system.

Coverage dates, employee group, pay period and time zone are recorded. A named backup and escalation owner have accepted the handoff. The backup has tested the required review route using their own account. Pending timesheets and open corrections have owners and due times. Current counts reconcile, including timesheets changed after approval. Payroll has received the status update and the return handoff is assigned.

Common questions

Who should approve timesheets when a manager is away?

PTO Balance Reconciliation: Checklist & Worked Example

Roger Wood — Mon, 26 Oct 2026 18:24:35 +0000

PTO Balance Reconciliation: Checklist & Worked Example

PTO balance reconciliation explains how an employee's time-off balance moved from one verified point to the next. Instead of changing a number until two screens agree, trace the hours earned, taken and adjusted, then compare reports that cover the same dates.

The basic reconciliation

Expected closing hours = verified opening hours + hours earned − hours used + signed adjustments. Compare that result with the recorded closing balance for the same employee, leave account, unit and date scope.

This guide gives payroll and HR teams a repeatable review sheet, a fictional worked example and a way to investigate differences. Use your approved leave policy to decide which transactions belong in the account; this process does not establish a leave entitlement or authorize a policy change.

1. Define what you are reconciling

Reconcile one employee and one leave account at a time. Vacation, sick leave and banked time may follow different rules, so combining them can hide an incorrect posting. Record the employee identifier and account name before doing the arithmetic.

Start with an opening balance that was previously reviewed. If the opening figure came from a migration, retain the approved source and conversion notes. A correct sum of this month's movements cannot prove that an unsupported opening balance was correct.

Use one unit throughout the review. If your records use hours, keep the calculation in hours. Convert days only with the applicable documented hours-per-day assumption. Write that assumption beside the conversion, especially where employees work different shift lengths.

A useful review cadence is after each payroll or at a regular monthly close, with extra checks after a migration or a policy assignment change. Choose the cadence according to transaction volume and your team's review needs, then give one person responsibility for closing unresolved items.

2. Match dates before comparing balances

A balance needs a date definition. A report of activity during a month, a balance through a cutoff date and a balance that includes future records answer different questions. Save the report name, filters and generation time with each reconciliation.

Future approved leave can explain a difference.

TimeTrex's Requests documentation states that approval of an absence request under an absence policy updates the accrual balance immediately, including future-dated requests. Inspect the underlying records and report scope before deciding that a lower displayed balance is an error.

Keep future commitments separate in your worksheet until you know whether the comparison balance already includes them. Subtracting an approved future absence from a balance that already reflects it counts the same leave twice. Likewise, a pending request should not be treated as a posted withdrawal without checking its actual status and resulting records.

For a repeatable close, write a clear scope such as “transactions dated through October 31, reviewed November 2.” Then identify any later-dated records included in the screen you are comparing. The goal is an explained bridge between the two numbers, with each movement counted once.

3. Copy this PTO reconciliation template

Create one review record per employee and leave account. Store supporting exports in the team's approved location and reference them from the worksheet.

Employee and account: Employee ID; leave account; policy assignment; unit of measure.
Scope and evidence: Opening date; closing cutoff; report/template name; filters; generated-at time; source-file references.
Opening balance: Verified hours and reference to the previous signed-off review or approved migration total.
Movements: Earned hours; used hours; each positive or negative adjustment; transaction dates and supporting record IDs.
Comparison: Expected closing hours; recorded closing hours; difference; future records included or excluded.
Resolution and sign-off: Cause; owner; approved correction reference; before/after balances; preparer; reviewer; review date.

Use a consistent difference convention: recorded balance minus expected balance. A negative result means the recorded balance is lower than the worksheet expects. Keep the sign visible; an unsigned “8 hours” does not tell the reviewer which direction needs explaining.

4. Worked example: explain an eight-hour gap

Consider a fictional employee, Jordan, whose vacation account is measured in hours. The opening balance is verified at 40 hours. During the review period, Jordan earns 6 hours, takes 8 hours of leave and receives an approved 2-hour correction for an earlier under-credit.

Fictional transactions through the review cutoff
Movement	Hours	Evidence to retain
Verified opening balance	40	Previous signed-off balance
Accrual earned	+6	Accrual transaction and policy reference
Leave used	−8	Absence record and approval
Approved correction	+2	Correction reason and authorization
Expected closing balance	40	40 + 6 − 8 + 2 = 40

Now suppose the comparison screen shows 32 hours. The initial difference is 32 − 40 = −8 hours. Before entering a correction, the reviewer finds an approved 8-hour absence for a date after the cutoff, already reflected in that balance.

The comparison bridge is therefore 40 cutoff hours − 8 future approved hours = 32 hours. The gap is explained by scope. No balancing adjustment is needed. Retain the future request reference and label both figures so the next reviewer can reproduce the explanation.

If there were no supporting future withdrawal, the eight-hour difference would remain open for investigation. The same arithmetic does not justify a correction by itself. Every adjustment needs a documented cause and the appropriate authorization.

5. Investigate the cause before correcting a balance

Check scope and units first

Compare the employee, leave account, cutoff and units on both sides. Look for a missing opening balance, a report limited to current-period activity or an hours-to-days conversion using a different workday length. Resolve these comparison problems before touching employee records.

Match movements to their source

For each unexplained withdrawal, locate the absence or adjustment that produced it. For each missing credit, identify the accrual transaction that should exist and why. Check for duplicate entries, a changed absence date, a correction posted to the wrong account or an import counted twice.

Review the policy that actually applied

TimeTrex's Accrual Policies documentation distinguishes calendar-based and hour-based accruals, eligibility settings, service milestones, balance caps and rollover settings. A cap or eligibility condition can explain why a simple “rate × hours” estimate differs from actual records. Check the employee's assigned policy and relevant settings rather than assuming every employee accrues identically.

If a policy appears wrong, route it to the policy owner for review. Do not change a shared rule solely to make one employee's reconciliation agree. Assess who else could be affected and retain the decision with the correction evidence.

Close with a traceable resolution

Record whether the issue was a reporting difference, a source-record error or a policy question. After an authorized correction, rerun the same report and retain both versions. If the correction affects payroll, coordinate the related review through your normal payroll cutoff process and record any remaining follow-up.

6. Review the supporting records in TimeTrex

Start with the Accrual Balance Summary report. The documentation distinguishes “Overall Balance To Date” from “Overall Balance” and notes that the latter defaults to “All Years,” including past records and a year into the future. Select the template and period that match your question, and save those settings with the review.

Then inspect individual transactions under Attendance → Accruals. TimeTrex's Accruals guide explains how positive and negative records combine into a balance and how authorized users can view individual entries. It also describes initial balances, paid-out time and other adjustment types. Follow a record back to the relevant timesheet where available, and retain its date, amount and reason.

Use these views as evidence for the reconciliation. A summary total is the starting point; the underlying movements explain it. Menu access and available actions depend on the employee's permissions and your configuration.

Connect time-off records with attendance

Review how TimeTrex Time & Attendance can fit your team's timekeeping workflow. Bring a sample leave account and your reconciliation questions to the evaluation.

7. Six-point reconciliation sign-off

Use this checklist while reviewing the account. These browser checkboxes are a temporary reading aid; save the completed review in your team's recordkeeping system.

Employee, leave account, units and cutoff match on both sides. The opening balance has a verified source. Earned, used and adjusted hours each have supporting records. Future approved leave is identified and counted only once. Each difference is explained or assigned to an owner with a next action. Any correction is authorized, reread and retained with reviewer sign-off.

8. Common PTO reconciliation questions

Why can two PTO reports show different balances?

Employee Department Transfer: Payroll & Timekeeping Checklist

Roger Wood — Fri, 23 Oct 2026 18:22:21 +0000

Employee Department Transfer: Payroll & Timekeeping Checklist

An employee department transfer changes more than a name on the organization chart. Payroll needs the correct effective date, timekeeping needs the right department, and managers need a clear handoff for schedules and approvals. Use this checklist to carry one employee record through the move without losing track of the work already performed.

Define exactly what is changing

Start with the employee number and a written, approved transfer instruction. Distinguish a permanent department change from a temporary assignment or a few hours spent helping another team. Those situations may need different time-entry and reporting treatment.

Write an explicit value or “no change” for the department, branch, manager, scheduled shifts, wage, policy assignment and pay-period schedule. A move to another team does not, by itself, tell payroll that all of those settings should change. Keep changes to the approved scope.

This guide covers an internal move within the same employer. If the employing entity, work jurisdiction or employment arrangement changes, route the instruction to the people responsible for those requirements before using this routine checklist.

A copyable employee transfer handoff form

Copy these fields into your existing change-request process. Use one record with an owner and revision date so the outgoing manager, receiving manager and payroll team are working from the same instruction.

Employee and request: Employee number: ____ · Name: ____ · Request reference: ____
Effective boundary: Date and time, if needed: ____ · Time zone: ____ · First affected shift/pay period: ____
Assignments: Old → new department: ____ · Branch: ____ · Job/task, if used: ____
Manager handoff: Outgoing manager: ____ · Receiving manager: ____ · Backup reviewer: ____
Pay and policies: Approved wage change or no change: ____ · Policy/pay-period changes or no change: ____
Open work: Unresolved punches, requests, leave and approvals: ____ · Owner and deadline for each: ____
Completion evidence: Changed by/date: ____ · Independently checked by/date: ____ · First payroll reviewed: ____

Keep this handoff in the appropriate restricted company record. Put the operational instructions managers need in the handoff; keep unnecessary personal information out of widely shared scheduling notes.

Before the move: prepare the records and reviewers

1. Preserve the starting point

Capture the current assignments, future shifts and unresolved items before editing. Record which manager will review work performed before the transfer, who will handle later work, and who owns a correction discovered afterward. Give each unresolved item an owner instead of treating the department change as its resolution.

2. Separate assignment changes from wage changes

If pay stays the same, record that explicitly. If an approved wage change accompanies the transfer, confirm its own effective date. The two dates can differ. TimeTrex’s Wages documentation directs administrators to add a new wage record for a wage change to preserve wage history. It also describes a recalculation option affecting open pay periods from the wage’s effective date. Review the affected period before accepting recalculated results.

3. Check the actual approval relationship

Do not assume changing a department also assigns the receiving manager as approver. TimeTrex’s Hierarchy documentation describes separate relationships for requests, timesheets, exceptions and permissions. Confirm the relevant objects and the manager’s permitted employee scope. Have an authorized administrator coordinate the change and test the intended access.

Agree on a handoff deadline that leaves payroll time to resolve questions. Your payroll cutoff policy provides the wider close calendar; the transfer record should name the people accountable within it.

At the changeover: test the work the employee will do

Update the approved fields, then read them back. TimeTrex’s Employees documentation identifies default branch, department, job and task as fields used for report filtering and new records such as schedules. Check existing future records separately rather than assuming a new default has rewritten them.

Schedule: Check the employee’s next shifts, assigned department and any overlaps or missing coverage. Confirm that both managers understand the handoff.
Time capture: Confirm that the employee can select the intended department using their normal time-entry method. Explain how temporary work back in the old department should be recorded.
Approvals: Verify the receiving manager can see the intended employee and work. Check where pre-transfer pending items are now visible, and retain a named reviewer until they are resolved.
Reporting: Test both employee-level totals and department-level results for the affected dates. A current profile field and the department recorded on a time entry answer different questions.

Worked example: a midweek department move

In this fictional example, Alex moves from Packing to Dispatch before Thursday’s shift. The approved hourly rate stays at $24, the pay period stays the same, and Alex works 24 straight-time hours in Packing and 16 in Dispatch that week. The example excludes overtime, premiums, deductions and employer costs.

Expected review totals for the example
Department	Hours	Straight-time wages
Packing	24	24 × $24 = $576
Dispatch	16	16 × $24 = $384
Total	40	$960

The outgoing manager reviews the Packing entries; the receiving manager reviews Dispatch. Payroll compares the 40-hour employee total with the 24/16 department split and checks for duplicate or missing entries. The receiving manager also checks next week’s schedule so the old assignment does not continue unnoticed.

If the employee total is 40 hours but all 40 appear under Dispatch, investigate the report’s grouping and filters and the departments attached to the underlying records. Do not change accurate hours just to make a report match the example. For a deeper explanation of grouping costs, see labor cost allocation by department.

First-payroll transfer review checklist

Use this checklist as a review aid. Checks on this page are temporary and do not save a company record; record completion and exceptions in your own transfer request.

The approved effective boundary and old/new assignments match the saved employee record. Future shifts and normal time entry show the intended assignment, with no duplicate or missing work. Pre-transfer and post-transfer items have named reviewers, and pending items remain accounted for. The wage history and effective date match the approved pay instruction, including an explicit no-change decision. The first affected timesheet and payroll result reconcile with the underlying entries and expected department totals. Both managers and payroll have acknowledged the handoff, and unresolved exceptions have owners and dates.

Close the transfer only after the first affected payroll review. If something differs, keep the request open, document the cause and route the correction through the normal review process. Avoid making undocumented changes to a previously reviewed period.

Connect the transfer to everyday timekeeping

TimeTrex brings employee records and timekeeping into the workforce workflow. Review your existing configuration with your administrator and use TimeTrex time and attendance to explore how time capture and review fit your team’s process.

Common questions

Does a department transfer require a new employee record?

PHP2Shell: How TimeTrex Responded to Protect Customers

Roger Wood — Thu, 22 Oct 2026 19:32:17 +0000

TimeTrex Security Update: Our Response to PHP2Shell Vulnerabilities

Summary

TimeTrex responded immediately to the PHP2Shell security vulnerabilities, implementing proactive security measures before official patches became available. All public-facing TimeTrex servers were fully patched within 22 minutes of the security release, with no noticeable disruption to customers. Our subsequent security review found no evidence of attempted exploitation or suspicious activity related to these vulnerabilities.

No action is required for Cloud-Hosted customers. Customers with On-Site installations should ensure their PHP environments are updated. The latest TimeTrex stack installer already includes the necessary security patches.

Detailed Security Response

The following outlines the steps TimeTrex took to assess the PHP2Shell vulnerabilities, implement preventative safeguards, deploy security updates, and verify the security of our infrastructure.

At TimeTrex, protecting our customers' systems and sensitive workforce data is a responsibility we take extremely seriously. When critical security vulnerabilities are disclosed, our priority is to respond quickly and comprehensively while maintaining the reliability and availability of our services.

TimeTrex is developed using PHP, one of the world's most widely used programming languages for web applications, powering approximately 70% of websites with a known server-side programming language. On October 21, 2026, the PHP development team released security updates addressing two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, collectively known as PHP2Shell. These vulnerabilities could potentially allow attackers to execute unauthorized code on affected servers.

Because these vulnerabilities affect the underlying technology used by TimeTrex and many other web applications, our team took immediate precautions to protect customer environments, deploy the necessary updates, and minimize operational disruption.

Here is how TimeTrex responded to protect our customers.

Proactive Protection Before Patches Were Available

Within hours of the PHP development team's pre-announcement on the afternoon of October 20, our team began working around the clock to implement additional security measures as guidance became available from security professionals.

Because the PHP development team had indicated that security patches could be released earlier than scheduled if circumstances warranted, we ensured staff were available and actively monitoring developments so we could respond immediately.

As an additional precaution, we proactively implemented perimeter firewall rules to block and log potentially related requests, even when their connection to the vulnerabilities was only a remote possibility. These temporary safeguards provided an additional layer of protection while we prepared to deploy the official security updates.

All Public-Facing Servers Patched Within 22 Minutes

Every public-facing TimeTrex server was fully patched within 22 minutes of the official PHP security updates becoming available on the morning of October 21.

Thanks to our fully redundant, load-balanced infrastructure, we were able to deploy these critical updates across our production environment with no noticeable disruption to our customers.

At the same time, our development team updated the TimeTrex stack installer for On-Site customers to include the patched version of PHP, ensuring customers managing their own installations could also obtain the necessary security updates.

Independent Verification and Security Review

Deploying security patches is only one part of an effective incident response. Following the updates, our team independently verified that every server had been successfully patched at least twice.

We then conducted a thorough review of our traffic logs to identify any indications of attempted exploitation or other suspicious activity associated with these vulnerabilities.

Our review found no evidence of attempted exploitation or suspicious activity related to PHP2Shell.

Only after completing these verification and security checks did we remove the temporary firewall restrictions.

While the additional precautions were in place, certain legitimate operations, including file uploads and other related functions, were temporarily restricted. Customers attempting these operations may have encountered an error message. These restrictions were removed following successful verification.

What TimeTrex Customers Need to Know

Cloud-Hosted Customers: No action is necessary. All required security updates have already been applied to TimeTrex's cloud infrastructure, and our team continues to monitor the situation.

On-Site Customers: Customers using the TimeTrex stack installer can obtain the latest version, which includes the patched PHP release. Customers managing their own PHP environments should ensure the applicable security updates have been installed and verify that their systems are running patched versions.

Our Ongoing Commitment to Security

Security is an ongoing responsibility, not simply a response to newly disclosed vulnerabilities. Our team continues to closely monitor guidance from the PHP development team, security professionals, and the broader security community, and we will take additional action as necessary should new information become available.

Throughout this incident, our focus has remained on responding as quickly and comprehensively as possible, minimizing operational disruption, and maintaining the security and integrity of the TimeTrex platform.

We understand that businesses depend on TimeTrex for critical workforce management, time and attendance, and payroll operations. Protecting those systems and the sensitive information they contain remains a fundamental part of how we develop, maintain, and operate our software.

If you have any questions regarding these vulnerabilities or the security of your TimeTrex installation, please contact our support team. We are happy to assist.

```

Share the Post:

About The Author

Time To Clock-In

Start your 30-day free trial!

Experience the Ultimate Workforce Solution and Revolutionize Your Business Today

Saving businesses time and money through better workforce management since 2003.

Contact Us

Solutions

Products

Services

Guides & Tools

Support

Company

The post PHP2Shell: How TimeTrex Responded to Protect Customers appeared first on TimeTrex.

Employee Availability Form: Template & Review Checklist

Roger Wood — Thu, 22 Oct 2026 17:49:44 +0000

Employee Availability Form: Template & Review Checklist

An employee availability form records the days and times someone can work, when that information takes effect, and who reviewed it. A useful form gives the scheduler clear time windows instead of a vague note such as “mostly evenings.” It also keeps a recurring availability change separate from a request for a particular day off.

Use the template below to collect consistent information, check it against staffing needs, and carry approved changes into the working schedule. The form is a planning input: employees still need a clear record of their assigned shifts.

Start with three dates: the submission date, the requested effective date, and the next review date. Add an end date for temporary changes. Those fields help prevent an old form from silently driving a new schedule.

Keep availability, preferences and assignments separate

A single “available” checkbox can conceal several different meanings. An employee may be able to work a time window, prefer another window, and already have an assigned shift somewhere else. Give each concept its own field or process.

Availability: the time windows the employee reports they can work during the stated period.
Preference: shifts or days the employee would favor within those windows. A preference is useful when several workable assignments exist.
One-off time off: a request tied to a specific date or date range. Route it through the normal leave or absence process.
Assigned schedule: the actual shifts communicated to the employee after the scheduler reviews coverage and other applicable requirements.

Define these terms at the top of the form. Explain how a change is requested and how the employee learns the outcome. Do not let a submitted form automatically cancel an existing assignment or stand in for an approved leave request.

Employee availability form template

Copy this structure into your existing form or document system. The blank fields are intended for your internal process; this webpage does not collect employee information.

Employee and change details

Employee name and internal employee ID: ____________________
Department, role and normal work location: ____________________
Schedule time zone, including the named location: ____________________
Submitted on: __________ Requested effective date: __________
Change type: new record / recurring update / temporary update
Temporary end date, if applicable: __________ Next review date: __________
Form version or reference: __________ Replaces reference: __________

Instructions: Enter each workable window with a start and end time. Write “unavailable” when no window exists. Write “no preference” in the preference column when appropriate. Do not treat an empty cell as all-day availability. For overnight windows, name both days, for example “Friday 22:00 to Saturday 06:00.”

Weekly recurring availability — blank template
Day	Available windows	Preferred windows
Monday	________________	________________
Tuesday	________________	________________
Wednesday	________________	________________
Thursday	________________	________________
Friday	________________	________________
Saturday	________________	________________
Sunday	________________	________________

Review and confirmation

Desired weekly hours or shift count, if useful: ____________________
Scheduling notes needed to interpret the windows: ____________________
Reviewer and review date: ____________________
Outcome: accepted / clarification needed / discussion required
Agreed effective date and any agreed limits: ____________________
Working schedule updated by and on: ____________________
Employee informed on, by and through: ____________________

Collect the scheduling facts needed to make the assignment. Keep unnecessary personal explanations out of a general roster file. If a request needs a separate HR review, use the appropriate private channel rather than placing sensitive details in a shared schedule note.

Desired hours help a manager understand the employee’s request, but they are not a promise of hours or a substitute for reviewing the terms that apply to the role.

Worked example: a temporary evening-availability change

The following example is fictional. Jordan normally works weekday afternoons. For a six-week training course, Jordan requests a temporary change beginning November 2 and ending December 13. The record uses the worksite’s named time zone and gives these windows:

Jordan’s requested availability for the temporary period
Days	Available windows	Preference
Monday–Thursday	16:00–22:00	Three evening shifts per week
Friday	Unavailable	No shift
Saturday	09:00–17:00	Optional fourth shift
Sunday	Unavailable	No shift

The manager compares those windows with the required roles and coverage. A Tuesday 15:00–21:00 assignment does not fit merely because most of it falls within Jordan’s window: the first hour is outside it. A Tuesday 16:00–22:00 assignment fits the reported availability, but still needs the normal scheduling review.

The manager discusses workable coverage, records the agreed effective date, and checks any shifts already communicated for the change period. The accepted form is version 2. Its end date prompts a review before the following roster is prepared; it does not silently reinstate an old pattern without confirming that the information is still current.

A practical manager review workflow

Check completeness. Confirm that all seven days are addressed, the time zone is clear, and each start and end time is unambiguous. Ask about missing fields instead of filling them by assumption.
Check the effective period. Separate a future recurring change from an urgent problem with an already assigned shift. Record both issues if both need action.
Compare with coverage. Review the role, work location, shift length and required coverage. Several employees available for the same hour may still leave a different role uncovered.
Review the applicable constraints. Consider approved absences, existing assignments, work-hour limits, rest requirements, agreements and local scheduling rules that apply. An availability form alone does not establish that a proposed shift is appropriate.
Record the outcome. State what was agreed, what needs clarification, and when the decision takes effect. If coverage is unresolved, arrange a discussion instead of letting the form disappear into a pending folder.
Update and communicate. Apply the accepted information to the planning process, review affected shifts, and tell the employee where to check the current schedule. Retain the prior version with its replacement date.

Set an internal response target that your managers can consistently meet. A weekly scheduling team might review routine requests before its next roster-building session. That is an operating choice; use any required notice periods and procedures that apply to the workplace.

For the wider planning process, see the guide to creating employee work schedules. The availability review supplies one input to that process, alongside demand, role coverage and the hours already assigned.

Handle exceptions without losing the current version

One date changes, but the recurring pattern stays the same

Keep the recurring availability record in place. Use a dated request for the exception, then confirm whether it affects a shift already assigned. This avoids rewriting a weekly pattern for a single Saturday.

The employee has two available windows in one day

Record both windows explicitly, such as 08:00–11:00 and 15:00–19:00. Do not combine them into 08:00–19:00: the gap is unavailable. Any decision to schedule separate work periods needs its own review.

A request arrives after the schedule is communicated

Identify the exact affected shift, owner and response needed. A revised form is useful evidence of the request, but employees and supervisors also need confirmation of the actual shift arrangement. Keep the form decision and the schedule change connected by a reference or date.

Different managers hold different copies

Designate one current record location. Give each accepted update a version or reference, effective period and reviewer. Archive superseded copies so a manager can explain an earlier decision without accidentally scheduling from an old form.

No update arrives

Use a planned review date to request confirmation. Silence should not be interpreted as unlimited availability. If information remains incomplete, flag the record for follow-up and resolve the affected assignments through the normal scheduling process.

Carry accepted availability into the working schedule

A tidy form has value only when the scheduler uses the accepted information. Keep it close to the current roster, approved time off and shift-change process. Recheck the affected dates whenever an update is accepted; a form stored in a separate folder can otherwise leave the working schedule unchanged.

TimeTrex shift management brings schedule planning, adjustments and employee access into a workforce-management workflow. Its employee guidance documents access to schedules and requests for time off or schedule changes, with availability depending on the features the employer has configured. The form above is a suggested internal template, rather than a claim that every field is a built-in TimeTrex screen.

When evaluating your process, walk through one real scenario: a future temporary availability change, an affected assigned shift, the manager’s decision, and the employee’s view of the final schedule. Confirm how your team will store the accepted record and manage its review date.

Make schedule changes easier to follow

Explore how TimeTrex connects shift planning with employee access, time tracking and attendance.

Explore TimeTrex shift management

Availability review checklist

Use these checks before closing a request. Checkmarks are temporary browser aids and are not submitted or stored.

Every day has clear windows or an explicit unavailable entry, and the time zone is named.The effective date, temporary end date where relevant, and next review date are recorded.Preferences and one-off time-off requests are separate from recurring availability.The reviewer checked coverage, existing assignments and applicable scheduling constraints.The outcome, current version and affected schedule changes are recorded.The employee knows the outcome and where to find the current assigned schedule.

Frequently asked questions

Does available mean the employee is scheduled?

Payroll Exception Report: Catch Errors Before Payday

Roger Wood — Wed, 21 Oct 2026 22:38:10 +0000

Payroll Exception Report: Catch Errors Before Payday

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.

Quick answer: Review exceptions after time approval and a preliminary payroll calculation, then run the checks again after corrections. Give every flag an owner, a deadline and evidence of resolution. A flag means “investigate”; it does not, by itself, prove an error or justify reducing pay.

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.

Payroll exception checks and the evidence needed to resolve them
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.

Illustrative gross-pay review before and after correction
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.

Why “the total matches” is not enough: two equal and opposite errors can leave the total unchanged. Check employee count, hours, earnings codes and individual results before treating a balanced total as evidence of accuracy.

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 workflow

Payroll 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.

The report identifies the correct period, employees and final run version. Missing time, duplicate records and import rejections have been investigated. Employee-level hours, rates, earnings and unusual net-pay results have been reviewed. Each exception has an owner, supporting evidence and a verified resolution or documented escalation. The checks were rerun after the final correction or late change. The payment output reconciles to the approved register and has the required authorization.

0 of 6 review checks complete.

Frequently asked questions

How often should you run a payroll exception report?

Parallel Payroll Run: Checklist & Worked Example

Roger Wood — Wed, 21 Oct 2026 16:33:28 +0000

October 21, 2026 · Roger Wood

Parallel Payroll Run: Checklist & Worked Example

A parallel payroll run calculates the same pay period in your existing payroll system and your proposed system, then compares the results before the new system becomes the payment source. A useful test goes beyond matching the company total: it explains differences in each employee’s hours, earnings, deductions and net pay.

This guide gives payroll managers a repeatable comparison process, a worked example and a sign-off checklist. Use it when changing providers, replacing a timekeeping integration or introducing a major pay-rule change.

1. Set the test boundary before calculating

Write down the pay-period dates, payment date, employee population, currencies and system configuration versions. Select an approved period with enough variety to exercise the rules you actually use. A period containing only regular hourly pay will tell you little about premiums, leave or one-time deductions.

Assign three roles: an operator to prepare and calculate, a payroll reviewer to investigate differences, and an approver to accept the evidence. In a small team, record who performed the independent review even if people cover several responsibilities.

Agree with your implementation team how the test environment prevents payment files, direct deposits, employee notices and tax submissions from being released. Retain a clear owner for the real payroll and its deadlines throughout testing. Label all comparison exports with a test-run ID.

Choose scenarios deliberately

Hourly and salaried employees, where both are used.
Overtime, shift premiums and multiple rates.
Paid leave and unpaid time.
New hires, pay changes and employees with no payable hours.
Benefit deductions, reimbursements and relevant opening balances.
Department or job splits needed for accounting.

Use controlled supplemental cases for important scenarios absent from the selected period. Clearly distinguish those cases from actual employee payroll.

There is no single test-cycle count that proves every implementation is ready. Set the plan around your payroll complexity, scenario coverage, outstanding defects and reviewer acceptance.

2. Match inputs before comparing outputs

Create a frozen comparison pack. Include the approved time export, employee identifier mapping, effective pay rates, earnings and deduction definitions, tax settings, leave inputs and year-to-date balances relevant to the test. Record the export time and version. Use employee IDs for matching; names alone can produce false matches.

Define how an old pay code maps to a new one. A code called “OT” may represent total overtime earnings in one export and only the premium in another. Compare equivalent components before calling the difference a calculation error. Check time units too: 7 hours 30 minutes is 7.5 decimal hours, not 7.30.

Input	What must align	Evidence to retain
People and dates	Employee IDs, population, period and payment date	Roster and run header
Time and earnings	Approved hours, units, codes and effective rates	Time export and code map
Deductions and tax	Elections, calculation basis and applicable settings	Configuration comparison
Opening balances	Relevant year-to-date amounts and limits	Balance reconciliation

If an input changes after the freeze, issue a new version and rerun both calculations. Comparing a corrected timesheet in one system with the old timesheet in the other creates a misleading variance.

3. Compare in an order that reveals the cause

Start with employee counts and missing or duplicate IDs. Then compare hours and earnings by pay code, gross pay, taxable bases and withholding, employee deductions, net pay, employer costs and accounting allocations. Later results depend on earlier ones: a net-pay difference may begin with an incorrect earnings input.

For each comparable field, use variance = new-system amount − baseline amount. Keep the signed amount so the reviewer can see the direction. Also review absolute differences; a positive amount for one employee can cancel a negative amount for another.

Record the employee ID, field or code, both values, variance, likely cause, owner, corrective action and retest result. Add the source evidence and reviewer decision. A useful cause list includes input mismatch, code mapping, effective date, configuration, opening balance, rounding or an error in the old baseline.

A legacy result is a comparison point, not proof of correctness. If the systems differ, check approved source records and the applicable calculation requirements. Have qualified payroll staff resolve tax or wage-rule questions using current jurisdiction-specific guidance.

4. Worked example: a $15 net-pay difference

The following fictional comparison uses the same approved 40 hours at $25 per hour. Withholding and deduction figures are illustrative fixed inputs, not tax estimates or a statement of required deductions. There are no reimbursements or other net-pay adjustments in this simplified example.

Field	Baseline	New run	Variance
Regular earnings	$1,000	$1,000	$0
Employee withholding	$180	$180	$0
Benefit deduction	$50	$35	−$15
Net pay	$770	$785	+$15

The arithmetic is $1,000 − $180 − $50 = $770 in the baseline and $1,000 − $180 − $35 = $785 in the new run. Gross pay agrees. The benefit deduction explains the entire net-pay difference.

The reviewer checks the approved benefit setup and discovers that a $15 additional deduction was omitted from the new configuration. After correcting the setup, the operator reruns the test. The deduction becomes $50 and net pay becomes $770. The evidence log links the configuration correction, new run ID and reviewer acceptance.

Now imagine a second employee has a −$15 net variance. The company net-pay total would match even before either issue was fixed. Employee-level review exposes both errors. This is why a grand-total match cannot replace line-by-line reconciliation.

5. Parallel payroll run sign-off checklist

Use these checks during review. Tick marks are a reading aid for this page; record approvals and supporting files in your controlled payroll records.

The employee population, dates, source inputs and opening balances are reconciled. Required pay scenarios and code mappings have been tested and documented. Employee-level differences have an evidenced cause, owner and final decision. Corrections were retested, including checks for effects on other employees. Payroll totals, employer costs and accounting allocations have been reviewed. An approver accepted the evidence and confirmed the live-payment handoff.

Keep unresolved material differences open. Decide whether they block cutover based on their cause and impact, with explicit payroll-owner approval. Record any accepted difference precisely, including the reason, affected population and follow-up owner.

Before the first live run, confirm which system will pay, who releases payments, who owns filings, and how approved test corrections reach the production configuration. Preserve the comparison history according to your records policy and provider guidance. Confirm how test data is isolated or cleared without changing genuine payroll records.

Connect the timekeeping review to payroll

TimeTrex combines payroll processing with scheduling and attendance, and provides digital pay stubs and reporting. During implementation, use your test plan to check that approved time, mapped pay codes and payroll results remain aligned. Confirm the reporting and configuration options appropriate to your edition and deployment.

TimeTrex’s implementation and setup services include assistance with data migration and initial configuration. Bring your employee scenarios, code map and variance log to the implementation discussion so the review addresses your actual payroll process.

Plan a payroll comparison with clear evidence

Discuss your timekeeping, payroll and migration requirements with TimeTrex before setting the cutover date.

Talk to TimeTrex

Parallel payroll run FAQs

How many parallel payroll runs should we complete?

Overnight Shift Time Tracking: Midnight & Payroll Rules

Roger Wood — Tue, 20 Oct 2026 18:15:18 +0000

Overnight Shift Time Tracking: Midnight & Payroll Rules

Overnight shift time tracking needs a full date and time for every punch, a clear rule for assigning shifts to dates, and a payroll check at workweek and pay-period boundaries. A shift that starts Tuesday at 10 p.m. and ends Wednesday at 6 a.m. is one continuous shift, even when reports show its hours on two dates.

For supervisors in a warehouse, hotel, care facility or production operation, the practical challenge is keeping three views aligned: the schedule employees follow, the work time they actually record, and the hours payroll uses. This guide walks through the arithmetic, the records to keep and a repeatable review process.

Record dates, time zones and punch types

A row containing only “10:00–6:00” leaves too much to interpretation. Record the start date, end date, local times, time zone and whether each event is an in punch, out punch, meal or return from a meal. Use a consistent 24-hour display where it helps prevent confusion between morning and evening.

Keep the employee, work location and department or job assignment attached to the record. If someone changes jobs during the night, record when the transfer happens so labor reporting can follow the work. Keep original punches when making a correction, along with the reason, supporting information and reviewer.

Example overnight record

Employee: Jordan · Location: Warehouse A · Time zone: America/Chicago
In: Tuesday, October 20, 2026, 22:00
Meal out: Wednesday, October 21, 02:00
Meal in: Wednesday, October 21, 02:30
Out: Wednesday, October 21, 06:00
Elapsed shift: 8:00 · Verified unpaid meal: 0:30 · Work time: 7:30

Use the employee’s actual events when work differs from the schedule. An early arrival, late handover or interrupted meal should prompt review. Copying the scheduled eight hours into the timesheet can hide the very differences the review is meant to explain.

How to calculate hours across midnight

On a night without a clock change, count the time from the start until midnight, add the time from midnight until the end, and subtract only verified unpaid time. For the example above: 2 hours before midnight + 6 hours after midnight − 0.5 hours = 7.5 work hours.

Illustrative overnight shift calculations
Recorded interval	Unpaid time	Work time
Tuesday 22:00 → Wednesday 06:00	00:30	07:30 = 7.50 hours
Tuesday 23:45 → Wednesday 08:15	00:45	07:45 = 7.75 hours
Sunday 20:00 → Monday 04:00	None in this example	08:00 = 8.00 hours

Hours and minutes are not decimal hours. Seven hours and 45 minutes is 7 + 45 ÷ 60 = 7.75 hours. It is not 7.45. Keep that distinction visible in spreadsheets, payroll imports and approval reports.

Keep break review separate from the clock calculation

Do not assume an overnight meal was unpaid merely because it was scheduled. Ask whether it occurred and whether the employee worked during it. For covered U.S. employees, the Department of Labor explains that short rest breaks generally count as work time, while bona fide meal periods are generally treated differently. Review the applicable rules and circumstances before deducting time. See the DOL guidance on breaks and meal periods.

Give the night supervisor a simple way to report an interrupted meal before approval. Payroll should see the correction reason alongside the total, rather than discovering it after a paycheck question.

Check the workweek and pay-period boundary

A calendar date, a shift label, an overtime workweek and a pay period answer different questions. Write down the exact boundary for each calculation your operation uses. A Sunday night shift may cross into a new overtime week even when a scheduling report lists the entire shift under Sunday.

For covered nonexempt U.S. employees, the FLSA generally requires overtime after 40 hours in a fixed, recurring 168-hour workweek. That week can begin on a day and hour other than Monday at midnight, and hours cannot be averaged across multiple weeks. State rules and special arrangements can change the analysis. Use the DOL overtime guidance alongside the requirements that apply to your workforce.

Example: Sunday 20:00 to Monday 04:00

Assume the established workweek begins Monday at 00:00, no clock change occurs and all eight hours are work time. The interval contains four hours before the boundary and four after it. If the employee already has 38 hours in the ending week, that week reaches 42 hours; four hours fall into the new week. Under the ordinary federal 40-hour example, two hours in the ending week exceed the threshold.

This is a deliberately simple example. Premiums, multiple rates, daily overtime, alternative work periods and local rules need their own calculation. The control to copy is the reconciliation: the two segments still total eight hours, and the payroll calculation follows the established boundary.

Apply the same discipline when a shift spans a pay-period end. Confirm where each interval appears in payroll detail, when the remaining hours will be paid and whether the next period duplicates any time. Review the surrounding period when correcting a boundary shift.

Handle clock changes with timestamps

Where clocks change seasonally, displayed start and end times alone can be misleading. Preserve the applicable time zone and timestamp offsets so a repeated local hour can be distinguished. The DOL’s daylight saving example explains that a clock change can reduce or increase hours actually worked on a night shift. Verify the location’s current rules; do not assume every site changes clocks.

Review overnight settings in TimeTrex

TimeTrex’s Pay Period Schedules documentation describes several controls relevant to overnight work:

Time Zone and Overtime Week: establish the context for period and overtime boundaries.
Minimum Time-off Between Shifts: affects whether punches separated by a break across midnight remain part of one shift.
Maximum Shift Time: affects how far the system looks back when pairing punches. An unsuitable setting can join records incorrectly.
Assign Shifts To: offers start-day, end-day, most-time-worked and split-at-midnight options. The documentation warns that these settings can affect overtime calculations.

Ask your administrator to validate the configuration against your approved pay rules using representative records. Test a normal overnight shift, a meal across midnight, a missing out punch and a workweek-boundary shift. Compare the detailed time record and payroll output before rolling out a change.

TimeTrex brings scheduling, attendance and payroll into a shared workflow. Explore the TimeTrex features for the wider process, then confirm the settings and permissions available in your deployment.

Give the night supervisor a clear handover

Assign an owner for reviewing the shift after its actual end, including any handover work. A midnight reporting cutoff should not leave the second half unreviewed. Define who covers the review when the supervisor is off, and how unresolved records reach payroll before its approval deadline.

A useful handover note identifies the employee, dated shift, exception, evidence still needed, assigned reviewer and due time. For example: “Jordan, Oct. 20–21, meal return punch missing; employee confirmation requested; Casey to review by 10 a.m.” Keep the note focused on the record and the next action.

Review recurring exceptions weekly. If meals around midnight repeatedly create separate shifts, investigate configuration and training. If missing out punches recur at one device, examine that process. Correct the cause as well as each timesheet.

Overnight payroll review checklist

Use these checks before approving the period. The boxes are a temporary reading aid and reset when the page reloads.

Every in, out and meal event has the correct date, time zone and punch type.
Elapsed hours reconcile to the dated punches and verified unpaid time.
Cross-midnight meals and missing punches have been reviewed with the employee or supervisor.
Workweek and pay-period boundary totals reconcile without missing or duplicated hours.
Applicable overtime, premiums and clock-change exceptions have been checked.
Corrections, reviewer and approval are documented before payroll is finalized.

Frequently asked questions

Does an overnight shift belong to the day it starts or ends?

Time Clock Outage Procedure: Backup & Recovery Checklist

Roger Wood — Mon, 19 Oct 2026 18:05:56 +0000

Time Clock Outage Procedure: Backup & Recovery Checklist

A time clock outage procedure tells employees how to record work when the usual device or connection fails, who reviews those records, and how payroll checks them after service returns. The goal is a complete record of actual work without missing time or counting the same punch twice.

A broken tablet, a local network problem and an unavailable timekeeping application require different technical fixes. They can use the same operational sequence: declare the interruption, start one approved backup log, reconcile it against recovered records, and confirm the return to normal timekeeping.

What to do when the time clock stops working

1. Confirm the scope and name an owner

Record when the problem was first reported, the affected site and device, and the last time a punch was visibly confirmed. Ask the technical contact whether the issue affects one terminal, one location or the whole application. Keep the incident description factual; a failed screen does not establish whether a punch reached the server.

The supervisor owns time capture. The technical contact owns diagnosis. Payroll owns reconciliation and approval. In a small business, one person may fill more than one role, but each responsibility still needs a named backup.

2. Announce one temporary recording method

Tell employees exactly where to record the next work start, work stop and relevant break events. Use an approved paper log or an accessible controlled form. Avoid collecting the same events through several messages, spreadsheets and notebooks.

If an alternative authorized clock-in method still works, test and confirm a saved punch before directing staff to it. Do not assume that a mobile app, kiosk or browser works offline, or that a failed punch will automatically upload later. That depends on the device, application, configuration and failure involved.

3. Keep recording actual work

Capture events as they happen, with the work date and local time zone. If someone reconstructs an earlier event, label it as a later report and record the basis for the time. The posted schedule can help identify a gap, but it should not silently replace the employee's actual work record.

For U.S. employers covered by the FLSA, the Department of Labor's recordkeeping guidance allows different timekeeping methods when the records are complete and accurate. In British Columbia, the province's guidance requires employers to keep daily hours records. Apply the requirements that cover your employees; this backup process is an operational template.

A backup time log employees can actually use

Prepare the log before the shift begins. An outage is a poor time to decide how employees identify themselves or whether a time means morning or evening. Keep employee pay rates, government identifiers and other unnecessary personal information off a shared sign-in sheet.

Incident header
Incident reference: ______
Site / affected clock: ______
Outage reported at, including date and time zone: ______
Supervisor / backup contact: ______
Temporary capture method starts at: ______

One row per event
Employee name or approved employee ID: ______
Work date: ______
Event: work start / work stop / meal start / meal end / other
Actual event time, including a.m./p.m. or 24-hour time: ______
Local time zone: ______
Department or job, if needed: ______
Recorded by and recorded at: ______
Employee confirmation / correction: ______

Reconciliation fields
Matching system punch found: yes / no / uncertain
Action taken and reason: ______
Entered or reviewed by, with timestamp: ______
Final timesheet reviewed by: ______

Record breaks as they actually occurred. A break entry does not, by itself, determine whether that time is paid. Payroll should apply the relevant policies and legal requirements. If work stops or employees are sent home, escalate the pay treatment separately instead of marking every minute of the outage as unpaid.

Use a separate sheet for each date or clearly label overnight events with both dates. For a shift across a time change, preserve the time zone or offset for each event and have payroll resolve elapsed time before entry. Give only the people who need the log access to it, and retain it under the applicable recordkeeping policy.

Reconcile recovered punches before adding missing time

Restoring the screen is the start of recovery. First determine whether any events were saved, queued or recovered. Preserve the original log and the available system records. Assign one reviewer to each employee and date range so two people do not enter the same correction.

Establish the recovery window. Include the last confirmed events before the interruption and the first confirmed events after it.
Compare event by event. Match employee, date, event type, time and any job or department information.
Resolve uncertainty. Ask the employee and supervisor about conflicts. Keep the original report and the reason for the final value.
Enter only the missing or corrected events. Mark each backup row with the action taken. If a matching punch already exists, record that it was matched rather than entering it again.
Review resulting totals. Check work and break intervals, daily and weekly totals, time categories and exceptions before approval or export.

Hypothetical recovery example: an 8:55–9:40 a.m. outage
Backup entry	Recovered record	Review action
Alex: work start, 9:00 a.m.	Matching 9:00 a.m. work-start punch	Mark as matched. Add no second punch.
Blair: work start, 9:05 a.m.	No corresponding punch found	Confirm the event and enter the missing 9:05 a.m. punch.
Casey: work start, 9:10 a.m.	Work-start punch shows 9:25 a.m.	Investigate the difference. Preserve the evidence and reason for any correction.

For Blair, a confirmed 9:05 a.m. start and 5:05 p.m. finish span eight elapsed hours. If a confirmed 30-minute meal period is unpaid under the applicable rules, the example contains 7.5 work hours. Keep paid time categories and overtime calculations separate from this simple duration check.

Do not delete a record just because its timestamp looks close to another one. Two legitimate events may be near each other, particularly a job transfer or a break transition. Use the event context to decide whether the records are duplicates.

Bring reviewed backup records into TimeTrex

TimeTrex's Enterprise TimeSheets guide documents selecting an employee and date in Attendance → TimeSheet, then using New Punch or Edit for the appropriate event. Access depends on permissions and the employees the supervisor is allowed to manage. Follow the guide for your edition and configuration.

Before entering a historical event, confirm the displayed time zone. The guide describes a Use Employees Timezone setting that can display and edit punches in the selected employee's time zone. Check the event date, In/Out direction, punch type and any required job information against the reviewed backup log.

Next, inspect the affected days and the Exceptions list. Missing punches can affect recorded totals. Correct the underlying record when it is wrong; an exception alone is a reason to investigate, not permission to change a real event to match the schedule.

A normal timesheet edit recalculates the related days in the week, according to TimeTrex's recalculation documentation. Still review the resulting totals. Do not change pay policies or run retroactive policy operations merely to resolve an outage entry.

Finally, compare the approved time with the payroll input or export. If the pay period has already been processed, use your authorized correction process and involve payroll before changing it. The payroll cutoff policy template can help define who owns late corrections and escalation.

Closeout checklist before normal timekeeping resumes

These checkboxes are for an on-screen review and reset when the page reloads. Keep the signed closeout record with the incident file.

A named owner recorded the affected devices, employees and outage window.
Every affected employee has complete work and relevant break records, with unresolved gaps assigned to an owner.
Backup entries were matched against recovered punches; missing events and conflicting records were reviewed.
Daily and weekly totals, exceptions and payroll inputs were checked after corrections.
A test punch was confirmed, and employees were told exactly when to return to the normal method.
The original backup log, correction reasons and closeout approval were retained; the next drill has an owner.

Test the backup plan before the next interruption

Run a short supervised drill that does not disrupt live payroll. Ask an employee to find the log, record a sample event and identify the contact. Ask payroll to explain how it would match that event against a recovered punch. Fix any ambiguity in ownership, access or time-zone labels, then replace outdated copies of the procedure.

Time clock outage FAQs

Can we use a paper timesheet during an outage?