Payroll Reconciliation: Matching What Was Worked Against What Was Reported

Every job dispatched out of the hall leaves two trails. One is the local's: the dispatch slip, the gang sheet, the check-in record, the name of the member who took the call. The other is the employer's: the report that comes back saying who worked, how many hours, at what rate, and what was deducted. Payroll reconciliation is the work of laying those two trails side by side and seeing where they stop matching.
Most of the time they match. When they don't, somebody's record is wrong — and it's usually the member who feels it first, in hours that never showed up on a seniority tally or dues that were never deducted.
Why Locals Do It
The hall already knows who it dispatched. That's the single most valuable piece of data a local owns, and it's the reason reconciliation is possible at all. Without the dispatch record, a local is taking employer reporting at face value with nothing to check it against.
With it, the local can ask a straightforward question for every shift: we sent this member to this job on this date — does the report back reflect that? Scale that question across a week, a quarter, a contract year, and patterns start to show up that nobody would ever catch one slip at a time.
The point isn't to assume bad faith. Reporting errors are ordinary. Payroll systems get updated, codes get entered wrong, a gang gets logged under the wrong job number, a member's name gets spelled two different ways across two systems. Reconciliation finds those things so they can be corrected while the paperwork still exists.
The Kinds of Discrepancies That Surface
When a local runs a serious reconciliation, the findings tend to fall into recognizable buckets:
- Missing shifts — a member was dispatched and worked, but no corresponding entry appears in the employer report at all.
- Hour mismatches — the shift is reported, but the hours don't line up with what the gang actually worked, including overtime, penalty time, or extended shifts.
- Wrong member attribution — hours reported under the wrong name, or under a member number that belongs to someone else.
- Classification and rate mismatches — work reported at a different classification than the one the member was dispatched in.
- Dues check-off gaps — hours reported, but no dues deduction shown, or a deduction that doesn't match what the hours should produce.
That last one matters twice. It's a money question for the local, and it's a standing question for the member, who may have no idea their check-off came up short.
Going Back as Far as the Data Goes
A reconciliation that only looks at last month tells you about last month. The real value is in depth. If a local can produce dispatch records going back five, ten, or more years, all of that is reviewable — and errors that repeated quietly for years are exactly the ones nobody has caught.
Older data is messier. It may live in binders, in spreadsheets, in an old system nobody logs into anymore, or in several formats across different eras of hall leadership. That's normal. The work is in getting it into a consistent shape so it can be compared, and then running the comparison year by year rather than trying to do everything at once.
How the Process Actually Runs
It goes in stages, and each one is worth doing properly before moving to the next.
Assemble. Pull the local's dispatch and check-in history and the employer reporting for the same periods. Note gaps on both sides — a missing month of reporting is itself a finding.
Normalize. Get names, member numbers, job codes, and date formats consistent across sources. This is the unglamorous step that determines whether the rest of the work produces real answers or noise.
Compare. Run the match. Flag every record that doesn't line up, and sort flags by type so similar issues can be worked together.
Review. A person goes through the flags. Some are data artifacts and get cleared. Some are real and get documented, with the supporting records attached.
Follow up. Documented discrepancies go to the employer through whatever process the local normally uses, and corrections get posted back to the member's record so hours and dues history reflect reality.
Keeping It From Being a One-Time Project
A big back-review is worth doing once. Doing it every few years from scratch is a waste of the local's time.
The better outcome is that reconciliation becomes routine — the same comparison running against current reporting as it arrives, so discrepancies show up in weeks instead of years. When dispatch, check-in, and dues records all live in one place, that comparison is something the hall can glance at rather than a project it has to schedule.
DockOps is set up around how each local already runs its hall — your dispatch rules, your record formats, your reporting cycle — rather than asking the local to change its process to fit the software. The reconciliation works off the records you already keep.
— The DockOps Team
See how DockOps would fit your local — book a demo at dockops.app/book.