Manage COBRA buckets¶
As an H&W Staff member, I want to understand how COBRA premium buckets are created and paid, so that I can reconcile a COBRA member's balance and answer why their bucket behavior looks different from an ordinary dues bucket.
Screen: Members > Buckets (same tab Membership Staff uses for ordinary buckets), fed by the Benefits History COBRA workflow.
COBRA buckets are a distinct, auto-generated flavor of bucket tied to the COBRA benefit
enrollment process — grounded in the signed fdd-docs/assets/04.Final/IUOE 399 FDD 7.2 COBRA
Invoicing v1.2.1.md requirements doc.
How a COBRA bucket actually gets created¶
- MRC notifies H&W Staff that a member is COBRA-eligible (cross-reference Understand MRC triggers and pre-population for how MRC triggers work generally).
- H&W Staff creates the COBRA benefit record (status Notified, at the jobsite the member was previously working), fills in Start date/End date/expected coverage/reason and Member Plus eligibility period, and the member is notified. The member has 60 days to decide whether to take COBRA.
- On confirmation, a Benefits History record with Benefit type COBRA is created (status Elected) — the coverage level is derived from the jobsite, and the start date is typically in arrears (COBRA-eligible periods are always complete months).
- Creating that COBRA Benefits History record triggers automatic bucket creation: one bucket per month (or partial month) from the benefit's start date through the current month, each valued at the premium for that coverage level (from the Local/Dues Rate table — COBRA rates are not Dues rates, but share the same maintenance table). A monthly system job keeps creating the current month's bucket for every member whose COBRA record has no end date or a future termination date.
How a COBRA bucket gets paid¶
- Members pay COBRA premiums via the PRIZM Mail-in function, which displays their current open COBRA buckets.
- Standard bucket rules apply, including partial payment — an earlier draft of this requirement required full payment only; the signed FDD was updated to allow partial payment on COBRA buckets like any other bucket.
- Where previously approved, a COBRA premium can instead be paid from a member's HRA balance via the Accounting Adjustment functionality — validated so the adjustment can't exceed the HRA account's available balance.
- Posting a COBRA payment shows up in both the member's Payments tab and H&W History tab.
Things to watch out for¶
A COBRA bucket payment does NOT update PTD or Status
Unlike a dues bucket, paying a COBRA bucket deliberately does not touch the member's Paid-Through-Date or Status — COBRA coverage and union membership status are tracked independently. Don't expect (or try to force) a COBRA payment to move PTD.
Unpaid COBRA buckets only show in the Buckets tab, never H&W History
An unpaid COBRA bucket has no corresponding row in H&W History — that ledger only reflects posted payments. If you're trying to confirm what a member still owes, check Members > Buckets directly rather than expecting H&W History to show an outstanding balance.
A bucket can't be deleted once a payment has applied to it
Same rule as an ordinary bucket: once any payment has posted against a COBRA bucket, it can no longer be deleted outright — a payment rollback/void is the path to undo it, not deletion.
No work record is required for COBRA — don't expect one
There's no requirement to create a Work record for a COBRA-eligible member, which can leave a visible gap in their Work History. That's expected for a COBRA case, not a data-entry omission — see Maintain a member's Work History for the general Work History picture this differs from.
This is governed by a signed FDD, not reverse-engineered from tickets
Unlike most pages on this site, this page is sourced directly from the signed
IUOE 399 FDD 7.2 COBRA Invoicing v1.2.1 requirements document rather than a ClickUp ticket
cluster — no closed/completed COBRA tickets have been mined into training material yet
(task-management/cases/closed/COBRA-CLUSTERS.md exists but is currently empty of clustered
detail). Treat the mechanics above as signed-requirement-accurate, but flag any live-app
behavior that contradicts it as worth a dedicated UAT pass, not an assumption either way.