Skip to content

Run a dues delinquency or Assessment report

Assessment report: a member "shows up twice" has at least three different causes

The single most recurring Reports failure pattern in this project's ticket history is a member appearing twice (or at a wrong rate) on the Dues Assessment Report whenever they have more than one work record. Three distinct root causes have been confirmed, not one:

Change History gap

A member with one active work record still showed up twice — traced to a gap in Change History, not the report's own calculation logic. (IUOE-2688)

COBRA and terminate/restart work records

Further triage of "several members duplicated" samples split into two separate mechanisms: COBRA records need to be excluded from a single-site member's assessment count, and a terminate/next-day-restart work record needs its date-selection logic checked. JayStar's internal fix reportedly resolved the specific scenario tested, but IUOE's own verification still found other members being assessed multiple times — the general pattern stayed open. (IUOE-2743)

Incomplete migrated dues-rate records

A duplicate-rate case traced to missing/incomplete dues-rate records in Change History left over from the Union Solutions data migration (delivered with PRIZM 2.20) — not a report bug at all. JayStar's position was that the report correctly reflected incomplete migrated data. (IUOE-2487)

Before filing a new "duplicate on the Assessment Report" ticket, check: does the member have more than one work record? Is one of them COBRA? Was one terminated and replaced the next day? Does Change History actually have an open dues-rate record for every active job? None of these are report calculation bugs in isolation — they're data/config conditions the report is faithfully reflecting.

Assessment report: aggregate totals can be wrong even when every member looks right

Trade-code / bargaining-unit misclassification is invisible at the member level

Non-Bargaining totals ran roughly $430,000 off from expected — root cause was a wrong trade-code-to-bargaining-unit mapping misclassifying a large set of bargaining trade codes as Non-Bargaining. This defect was invisible spot-checking individual members and only surfaced as an aggregate-total discrepancy; JayStar corrected the mapping and it was confirmed resolved against an independent reference extract. Periodically reconcile Assessment Report grand totals against an independent extract, not just a handful of member-level spot checks. (IUOE-2804)

Friendly & Final Letters runs on PTD, not balance owed

Zero-balance Gold Members can still appear on the letters report

Gold Members with a zero balance owing were appearing on the Friendly & Final Letters Report. No FDD requirement existed to exclude them; the team chose to suppress zero-balance rows (rather than touch Paid-Through Date logic or exclude Gold Members outright), and it shipped as included scope in PRIZM 2.20. The underlying mental model is the real training point: this report runs on PTD (paid-through date), not balance-due. Gold Members routinely carry a stale PTD with no current balance — don't assume a PTD-based report is balance-aware without checking. Late-breaking verification on this same ticket also surfaced the multi-work-record duplication pattern described above, on this report too. (IUOE-2409)

Member Delinquency report covers bulk, not a single member on the phone

The signed Member Delinquency report (FDD 6.12) answers a different question than 'what does this one member owe right now'

A front-line scenario — "where do I see assessed-but-unpaid dues for one member while they're on the phone" — wasn't answered by the existing FDD 6.12 Member Delinquency report, because that report only covers bulk/aggregate output, not a single-member, real-time, month-by-month view. This was escalated into an approved Change Order (CO 3248, the Dues History Tab) rather than treated as a report bug — the report was working as specified, the specified scope just didn't cover the real use case. If a request sounds like "I need this one member's delinquency status right now," check whether CO 3248's Dues History tab already covers it before assuming the Member Delinquency report should. (IUOE-2059)

Who can do this

Role Access
Super User View Only
Business Agent View Only
Management View Only
Membership Staff View Only
Accounting View Only
Contract View Only
H&W Staff View Only
ETF Staff View Only

Every role shares the same View Only access to this category of reports — the Reports module has no Add/Update anywhere. The reports covered here (Dues Assessment, Member Delinquency, Friendly & Final Letters) are run most often by Business Agent, Membership Staff, and Accounting staff working delinquency/collections and monthly-meeting reporting, but nothing in the system restricts them from any other role that can open Reports.

This group covers the reports a Business Agent or Membership Staff member reaches for to answer "who owes dues," "who's delinquent and needs a letter," and "who should be assessed this period" — and the recurring ways those reports can look wrong without actually being broken. See Navigate the Reports catalog and avoid parameter gotchas for the shared SSRS mechanics (checkbox-pickers, period dropdowns, render timing) that apply to every report named below.

No documented click-by-click walkthrough exists yet for any of these reports' parameter screens — the crawl captured the EMPLOYER/MEMBER/ACCOUNTING button lists themselves but hasn't drilled into Dues Assessment, Member Delinquency, or Friendly and Final Letter the way it has Per Capita Summary or Employer\Jobsite Invoice Detail. What follows is grounded in real ticket history instead — the mechanisms that have actually caused these reports to look wrong in practice.