← All articles

Short, Missed, or Misapplied: Catching Dues Problems Before They Snowball

November 14, 2026 · 5 min read · By DockOps

A dues problem almost never announces itself. It shows up as a number that's a little lower than last month, a member who doesn't appear on a remittance at all, or a payment that posted cleanly — to the wrong record. On the day it happens, none of that looks urgent. A year later, when someone is trying to reconstruct who owed what and when, it's a project.

The locals that stay out of that situation aren't doing anything exotic. They're looking at dues on a regular cycle, comparing what came in against what should have come in, and resolving the differences while the paperwork is still fresh and people still remember the circumstances.

What a Clean Dues Record Actually Looks Like

A dues record is clean when you can answer three questions about any member, for any period, without hunting:

  • What was owed, under which rate or category that applied to them at the time
  • What was received, when, and through what channel — check-off, direct payment, or an arrangement the local approved
  • What's outstanding, and whether anything about their standing depends on it

If answering those takes a stack of remittance sheets and a phone call, the record isn't clean yet. It's recoverable, which isn't the same thing.

Where Check-Off Quietly Breaks Down

Check-off is reliable right up until something changes, and something is always changing. A member picks up work under a different classification. A new member's authorization hasn't made it into the employer's payroll system yet. Someone works a short week and the deduction comes out proportionally — or doesn't come out at all. A member's name is spelled differently in two systems and their payments split across two records.

None of these are anyone's bad faith. They're the normal friction of information moving between a payroll system and a hall. But they all produce the same symptom: the total that arrives doesn't match the total that should have arrived, and nobody notices unless someone is checking.

The other common gap is members who worked but don't appear on the remittance at all. That's not a dues question first — it's a reporting question. It's also exactly the kind of discrepancy that a broader payroll comparison surfaces, which is why dues review and work-record review belong in the same conversation rather than separate ones.

Separate the Three Problems

Lumping everything into "dues issues" makes them harder to fix. In practice there are three different things, and they need three different responses.

Missed — nothing came in for a member who had earnings in the period. The first question is whether the hours were reported, not whether the member is delinquent.

Short — something came in, but less than the applicable rate would produce. Usually a rate, category or partial-period issue. Often it repeats until someone flags it.

Misapplied — the money arrived and posted, but to the wrong member, the wrong period, or the wrong category. The local's total looks fine. Two individual records don't.

Misapplied payments are the ones that cause the most trouble later, because nothing about the monthly total signals a problem. They only surface when you review at the member level.

A Monthly Review That Takes Less Time Than You'd Think

Run the same pass every cycle, in the same order:

  1. Compare each remittance against the members who show work in the period. Pull the names that appear in one place and not the other.
  2. Check amounts against the rate or category in effect for that member at that time — not the current one.
  3. Review any manual or direct payments and confirm they posted to the right member and period.
  4. Look at who's approaching the edge of a grace period or arrangement, and who crossed it this cycle.
  5. Close the period, note what was unresolved, and carry those items forward by name so they don't disappear.

Step five is the one locals skip. An unresolved item that isn't carried forward is an unresolved item you'll rediscover in two years.

Tell the Member Early

A member who finds out in month two that a deduction didn't come through can usually sort it out in a conversation. The same member finding out in month fourteen is facing a number large enough to be a real problem, over something that was never their decision in the first place.

Early notice is also a standing issue. Dues status touches a member's position in the hall, and the fairest version of that is one where nobody is surprised. That means a record the member can see, a clear statement of what's owed and for which period, and a documented path for questions.

Built Around Your Rules, Not Someone Else's

Dues categories, rates, grace terms, check-off arrangements and approval steps differ from local to local, and they exist for reasons specific to each hall. DockOps is set up around how your local already handles dues — your categories, your cycle, your sign-offs — rather than asking the local to adopt someone else's process. The point is to make the review faster and the record easier to trust, not to rewrite the rules.

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

— The DockOps Team