← All articles

Pulling the Records: How a Local Prepares for a Multi-Year Payroll Reconciliation

November 19, 2026 · 4 min read · By DockOps

A payroll reconciliation is only as good as the records it runs on. Comparing what members actually worked against what employers reported sounds straightforward until you go looking for the source data — and find it spread across dispatch sheets, check-in logs, remittance reports, dues ledgers, old spreadsheets and a filing cabinet that three different office managers have organized three different ways.

That's normal. Most locals have more usable history than they think. The work is pulling it together in a form that can actually be compared, and knowing what to do when a stretch of it is thin. Here's how that preparation typically goes.

Decide How Far Back You Can Realistically Go

The honest starting point is a question: how many years of data does the local actually have, and in what condition? Not how many years you'd like to review — how many you can support with records.

Some locals have clean digital remittance files going back a decade and paper dispatch records going back further. Others have solid recent years and patchier older ones. Either way, start by inventorying what exists before deciding on scope. It's better to review eight years thoroughly than to announce twelve and stall out in year three.

Work backward from the present. The most recent years are usually the best documented, the easiest to match, and the most immediately relevant to members' current standing.

Identify the Three Record Sets You're Comparing

A reconciliation generally leans on three categories of record, and you need all three to tell a complete story:

  • What the local dispatched — dispatch records showing who was sent where, on what date, for what job and shift.
  • What members reported working — check-in records, timekeeping entries, or whatever the local maintains to confirm a dispatched member actually worked the job.
  • What was reported and remitted — employer reports of hours and earnings, and the dues amounts that came in against them.

When those three line up, there's nothing to chase. When they diverge — a dispatch with no corresponding report, reported hours that don't match the shift worked, dues that don't track the earnings reported — that's where the review focuses.

Expect the Data to Be Messy, and Plan for It

Older records rarely arrive in matching formats. Dispatch sheets may be scanned paper. Remittance reports may be PDFs, spreadsheets, or printouts in a binder. Columns get renamed. Job codes change. Shift labels from twelve years ago may not mean the same thing today.

A few things worth sorting out early:

Member identity. The single biggest source of friction is matching the same person across years of records. Names get entered differently, nicknames appear, badge or register numbers change, and members move between categories. Establishing one reliable identifier per member — and a map of the variations that appear in historical files — saves enormous time later.

Date and period alignment. Payroll periods, dispatch dates and remittance periods don't always share the same boundaries. Agreeing on how periods line up prevents a long argument about whether a gap is real or just a calendar artifact.

Job and category definitions. If a job classification was renamed or split at some point, the review needs to know when and how, or it will look like work simply stopped.

Document the Gaps Instead of Hiding Them

Every multi-year review has holes — a quarter where files were lost, a period before a system changeover, a stretch of paper records that never got scanned. The right move is to log each gap: what period, which record type, why it's missing, and what partial information exists.

A documented gap is defensible. An undocumented one looks like an error in the review itself. When officers present findings to a board or raise a question with an employer, being able to say precisely what the local does and does not have is part of what makes the rest credible.

Keep the Current Year Clean While You Work Backward

One practical note: while the local is digging through history, the current year keeps generating records. If dispatch, check-in and dues entries are being captured cleanly and consistently right now, next year's reconciliation starts from a much better place — and the local stops adding to the backlog it's trying to clear.

That's the long-term payoff of the exercise. The first multi-year review is the hard one, because it means reconstructing history. After that, it becomes a routine comparison against records that were built to be compared.

Fit the Process to the Local

No two locals keep records the same way. The categories, job types, shift structures, dispatch rules and reporting formats all differ, and a reconciliation process that assumes otherwise will produce noise instead of answers. DockOps is set up around how each local already works — its own member categories, its own dispatch practice, its own record formats — so the comparison reflects reality on that hall's floor rather than a generic template.

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

— The DockOps Team