← All articles

Worked vs. Reported: The Discrepancies a Payroll Reconciliation Finds

November 12, 2026 · 4 min read · By DockOps

Every shift generates two records. The hall has one: who was dispatched, to what gang, on what date, for what shift, and who actually checked in and worked. The employer reporting has another: the hours and earnings reported to the local for that same work. Most of the time those two records agree. A payroll reconciliation is the disciplined process of finding the places where they don't.

This is not an audit in the legal sense, and it isn't an accusation. It's a comparison. Records drift apart for a dozen ordinary reasons — a gang got coded wrong, a shift got reported under the wrong date, a member's identifier changed after a name change, a pay period got skipped during a system migration. The point of reconciliation is to see the gaps clearly so the local can ask informed questions instead of general ones.

Matching Comes Before Comparing

You can't compare two records until you're confident they describe the same day of work. That sounds obvious, and it's where most of the real effort goes.

A good match key usually combines the member identifier, the work date, the shift, and the job or gang. Each of those can go wrong independently. Member identifiers change over a career. Work dates shift by one when a night shift crosses midnight. Shift labels differ between the hall's vocabulary and what appears in a remittance file. Gang designations get abbreviated inconsistently.

So the first pass is a clean match — records that line up on every field. The second pass is fuzzy: same member, same week, close enough on hours, but the date or shift code doesn't agree. Those near-matches are usually coding differences, not missing money, and separating them out early keeps the real exceptions from drowning in noise.

The Patterns That Show Up

Once records are matched, the mismatches tend to sort into recognizable categories:

  • Worked but not reported. The hall dispatched and checked in a member for a shift that never appears in the reporting at all.
  • Reported short. The shift appears, but with fewer hours than the dispatch and check-in record shows, or without overtime, penalty or shift differential that the record indicates applied.
  • Wrong member. Hours reported under one member that the hall's record attributes to another — often two members with similar names or sequential identifiers.
  • Missing periods. An entire week or pay period with no reporting, usually traceable to a file that never arrived or never got posted.
  • Duplicates. The same shift reported twice, which inflates one record and can mask a shortfall elsewhere.
  • Unmatched reported work. Hours reported for a member with no corresponding dispatch — sometimes a legitimate direct hire, sometimes a record the hall never captured.

None of these is proof of anything on its own. Each one is a question with a specific answer somewhere.

Triage: Data Problem or Real Gap

The discipline that keeps a reconciliation credible is sorting exceptions into two buckets before anyone picks up the phone.

Data problems get resolved internally: a mis-keyed date, a stale member identifier, a gang code that changed in the middle of a year. Fixing those improves the hall's own records and shrinks the exception list, often substantially.

What's left is the real exception list — mismatches that survive scrutiny on both sides of the comparison. Those are worth documenting carefully: the member, the date, the shift, what the hall's record shows, what the reporting shows, and what evidence supports the hall's version. A short, well-documented list gets a serious response. A long, unsorted list gets a shrug.

Why Dues Ride Along

Reconciliation isn't only about hours. Where dues are collected through check-off, the amount remitted is tied to the work reported. If a period of work was never reported, the dues for that period likely weren't either — and the member may show a gap in their dues record through no fault of their own.

That's why hours reconciliation and dues review belong in the same process. Resolving the hours question often resolves the dues question at the same time, and it protects a member's standing before anyone has to argue about it.

Set Up Around Your Records

No two locals keep records the same way. Shift vocabulary, gang naming, how far back the usable data goes, what arrives as a file and what arrives on paper — all of that is local. DockOps is configured around how your local already records work, so reconciliation runs against your definitions instead of forcing your history into someone else's template. The comparison engine is the same; the match rules are yours.

The value isn't a single big finding. It's having a repeatable monthly comparison so that next year's gaps get caught in weeks instead of years.

See how DockOps would fit your local — book a demo at dockops.app/book.

— The DockOps Team