Reading piece-rate earnings on a pay stub
Delpack Logistics
October 26, 2026
10 min read
Reconcile one piece-rate paycheck by matching the pay period, eligible stops, rate, adjustments and recorded hours to route evidence.
A driver's pay stub lists 92 paid stops, while the route records seem to show 97 stops eligible for the same pay period. The five-stop gap may reflect a cutoff, an exclusion rule, a corrected scan, or an error. Reading piece-rate earnings on a pay stub means reconciling the specific units, rate, adjustments, and hours behind one check before deciding what question to send payroll.
The U.S. Department of Labor recognizes piecework as a wage basis in its FLSA recordkeeping guidance and explains that hours and earnings still matter when workers are paid by the piece. Those rules do not define Delpack's stop eligibility or rate schedule. A driver needs the employer's written pay terms and the records for the particular pay period. The point of the review is to find a dated, explainable difference, not to assume every route scan is a payable unit.
Match the pay period
The pay period on the stub sets the first boundary. Ask for its start and end dates, then gather route records for exactly those dates. A stop completed on the last night of one period may appear in the next check if the employer's cutoff operates that way. Compare dates before counting units. A correct total for a different week is still the wrong comparison.
Find out whether a shift that crosses midnight is assigned by route date, completion timestamp, or payroll date. The employer's terms should say how such work enters a period. If the app lists a Tuesday route but the last stops occurred just after midnight Wednesday, a candidate should not assume the pay stub uses the same date label. Keep the raw timestamps available when asking payroll.
Ask whether the pay stub covers one week, two weeks, or another cycle and whether an adjustment from an earlier period appears in the current check. A correction line can increase today's gross pay without changing today's stop count. Separate current-period units from prior-period adjustments so the arithmetic remains understandable.
Find out which version of the route record is final. A driver may have an initial manifest, a live app log, and a corrected end-of-day report. The first list can include canceled or reassigned stops that never became the driver's payable work. The final record may be the right starting point, but the employer should identify the controlling source rather than leaving the worker to guess.
Keep a simple period worksheet with route date, route ID, completed units, excluded or questioned units, and the total. Do not alter the original records. A dated worksheet helps the driver see whether the gap is concentrated on one day or spread across many routes. It also gives payroll a narrow question instead of a general complaint that “the check looks low.”
Reading piece-rate earnings on a pay stub starts with matching the same time window. Once the period is correct, the driver can test whether the count on the stub uses the same definition of a payable unit as the offer or pay policy.
Count the eligible units
The eligible units are the pieces or stops the employer's written terms say are payable. Ask whether the unit is a completed stop, a delivered parcel, a successful handoff, or another measured result. One address with several packages could count once under a per-stop arrangement and more than once under a per-piece arrangement. The label on the stub should match the definition in the pay terms.
Find out how exceptions affect the count. An attempted delivery, refused parcel, customer absence, duplicate scan, or reassigned stop may be treated differently. The driver should not assume an app event marked “completed” is automatically payable, nor accept an exclusion without locating the rule. List each disputed stop with its ID and actual final status.
Ask whether a route that was split between drivers creates separate unit counts. A stop originally on one manifest may have been completed by another worker after a reassignment. The records should identify who performed the payable work and when. A driver can compare assignment changes with the final delivery event before including a stop in a discrepancy total.
Find out whether the employer has a review or correction window for late customer claims, reversed deliveries, or duplicate entries. A unit could move between pay periods after a scan is corrected. The pay policy should explain how and when that happens. The worker should retain both the original and corrected status rather than silently replacing one in the worksheet.
Ask how the company reports excluded units. A stub may show only the paid total; an accompanying statement may list deductions or exclusions. If neither exists, request the itemized unit calculation for the period. The goal is to understand why 92 units were paid when the driver's route evidence suggests 97, not to declare all five missing without checking eligibility.
Reading piece-rate earnings on a pay stub works best when the driver tests each contested unit against the same written rule. A broad count from the app can locate a gap. The final question should identify which specific stops and statuses were excluded and whether those exclusions match the agreed terms.
Verify the piece rate
The piece rate may be fixed, tiered, or tied to a route or service type. Ask where the rate appears in the offer, pay agreement, or current compensation schedule. A stub that lists units but not a rate may require a payroll detail report. Multiplying units by the wrong rate can create a false discrepancy even when the unit count is correct.
Find out whether the rate changed during the period. A new rate might start on a particular date, after a training phase, or for a defined category of work. The driver should split the units by the applicable dates or categories before multiplying. A single blended average on the stub may hide a correct two-rate calculation or an incorrect one.
Ask whether a stop's rate depends on location, package type, service commitment, or a bonus threshold. Only the actual written terms should control the calculation. A candidate should not infer a premium from a difficult route unless the employer promised it. Conversely, if a premium appears in the agreement, it should be traceable to the eligible units.
Write the arithmetic openly: number of units at each rate, subtotal for each group, then the sum. If the stub uses a code rather than a plain description, ask payroll what the code means. A worker can verify the calculation without knowing the company's entire payroll system. The key is to match each line to a term and a set of units.
Find out whether the displayed amount is gross earnings before taxes and deductions. Take-home pay can differ for reasons unrelated to the piece-rate calculation. Compare the unit subtotal with the correct gross-earnings line, then look separately at other additions or reductions. Mixing gross and net amounts makes a precise discrepancy harder to explain.
Reading piece-rate earnings on a pay stub is a check of count times rate under the actual terms, with adjustments kept visible. The review should yield a small number of specific questions: which rate applied, which units qualified, and where each adjustment entered the check.
Review adjustments and hours
The adjustments and hours may appear on lines separate from the basic piece subtotal. Ask whether the stub includes training pay, a prior-period correction, a bonus, a minimum-pay adjustment, or overtime. Each line should have a description and period. A positive adjustment can mask a missing unit, while a negative adjustment can make a correct unit subtotal appear wrong.
Piece-rate pay does not make hours irrelevant. DOL's regular-rate guidance explains that piecework earnings can be part of an overtime calculation for covered non-exempt employees. The driver should compare the hours shown with time records for the workweek, while avoiding an individual legal conclusion from the stub alone. The employer should explain how hours and piece earnings interact under this role's classification.
Find out whether non-delivery duties have their own pay line or are reflected in a minimum or other adjustment. Loading, return handling, meetings, and required paperwork may take time without adding a stop unit. The pay terms and applicable law control treatment. A driver should ask how those hours are recorded rather than assume the piece count is the whole wage record.
Ask whether the stub shows reversals or corrections from a prior period. A negative line may reverse a duplicate payment; a positive line may repair an earlier omission. Request the underlying reference if the description is too vague. A correction from last month should not be counted as the rate for this week's stops.
Check whether the employer's payroll detail uses daily or weekly groupings. Hours and overtime are often evaluated by workweek even when the paycheck covers two weeks. A candidate should understand the period boundaries before averaging earnings across a whole check. A two-week gross total alone may not show whether one workweek had more hours than the other.
Reading piece-rate earnings on a pay stub ends with the whole check, not just a unit multiplication. The count and rate explain the core piece earnings; hours and adjustment lines show how that subtotal becomes the paycheck's gross amount under the actual arrangement.
Work through the 92-versus-97 example
Imagine a two-week pay stub showing 92 paid stops at an illustrative rate of $2.50 each, for $230 in piece earnings before other lines. The driver's route log shows 97 entries they initially believe qualify. This example does not describe Delpack pay or establish whether any particular stop is eligible. Its purpose is to show how to investigate a five-stop gap.
The driver first checks dates. Two of the 97 entries were completed after the pay-period cutoff, so they belong on the next check under the employer's stated rule. Another entry was reassigned and completed by a different driver. That leaves 94 possible units for this check, not 97. The initial five-stop gap has narrowed to two disputed stops.
Next, the driver checks the two remaining stop IDs. One shows a delivery scan but an end-of-day correction to a customer refusal. Whether that counts depends on the pay terms, so the driver marks it “policy question.” The other shows a completed eligible stop with no visible exclusion. The driver can now ask payroll for the reason each of those two IDs is absent from the paid unit list.
Suppose payroll finds that one eligible stop was omitted and adds $2.50 to a later check, while the refused item is excluded under a written rule. The driver can verify the correction line and keep the explanation with the original stub. If payroll instead says both were included under a different code, the worker can ask which line and count contain them. The result should be traceable to records, not an unsupported assurance.
Finally, the driver compares the hours and any other pay lines with the workweek records. The $230 piece subtotal alone is not enough to explain the full check if training, adjustments, or overtime appear. The example keeps the unit audit narrow while showing why the worker should review the whole gross-pay calculation.
Choosing between a per-stop and hourly offer is an earlier decision based on expected routes and work time. Correcting a paycheck for missing training hours is a different discrepancy. This article stays with one actual piece-rate check and the records needed to explain its units, rate, and associated hours.
Bring a precise question to payroll
Ask for the pay period, the definition of one paid unit, the rate schedule, and any report that itemizes excluded or adjusted units. Keep the stub, the written pay terms, relevant route IDs, final statuses, and a dated worksheet. Avoid sending a customer address or other private information through an unapproved channel when a stop ID is enough.
State the difference plainly: “The stub shows 92 paid stops for this period; after removing two next-period stops and one reassignment, I see two stop IDs that need an explanation.” Ask which rule or adjustment accounts for each. If a correction is promised, note the expected pay period and verify that it appears. A specific record-based question is easier to resolve than a general complaint about pay.
Reading piece-rate earnings on a pay stub helps a driver turn one confusing check into a count, rate, adjustment, and hours review. Related work guidance is in the driver guide hub , and local roles appear on the Fort Wayne driver careers page .
Continue with Delpack
Review the Fort Wayne career overview or contact Delpack with a question about the company.
Topics
Browse Topics
All Guides
346
Job Search, Applications & Offers
79
Role Types & Job Fit
83
Schedules, Policies & Work-Life
40
Route Operations & Performance
91
Logistics & Warehouse Operations
53
Delpack Logistics Delpack Logistics is an Amazon Delivery Service Partner and last-mile logistics company serving the Fort Wayne market. Explore Welcome Meet Delpack Fort Wayne Delivery Driver Careers Driver Resources Contact Delpack Delpack News Legal Terms of Service Privacy Policy SMS status Contact info@delpacklogistics.com 260-306-5806 View market and mailing address © 2026 Delpack Logistics . All rights reserved.