Skip to content

Create and manage a bucket

As a Membership Staff member, I want to create and manage a member's Initiation Fee, Step-Up, or Bad Check Fee bucket, so that the charge is on record and collectible, following the eligibility rules those charges are gated by.

Screen: Members > Buckets > Create New Bucket

This write access is specific to you (and Super User)

Per the Roles & Security Matrix, only Super User and Membership Staff have Add/Update on Buckets, including Add New Bucket — every other role (Business Agent, Management, Accounting, Contract, H&W Staff, ETF Staff) can only read the tab. See Understand a member's buckets for the read-only side.

Creating a bucket is restricted this way because it's a financial charge being placed on a member, not a read-only record, and it's gated by real business rules (a member's status and dues standing) rather than being a simple data-entry form.

No documented click-by-click walkthrough of the Create New Bucket popup's own fields exists yet from the crawl — the grid and its filter/footer were captured, but the creation form itself wasn't driven through in that pass. What is documented, and matters more than the exact field sequence, are the eligibility rules and known gotchas below.

Eligibility gates

Bucket creation is deliberately gated, not a bug waiting to be loosened:

  • Withdrawal Card buckets require Normal status + dues-current, by design — the Union is meant to receive dues before a member can withdraw. This is tied to BLR 6.1.2.2.x / 6.2.2.5.x. Loosening this rule would require a Change Order, not a ticket. (IUOE-2054)
  • A related, still-open question is whether PRIZM is too permissive in the other direction — allowing a Step Up bucket in a case BLR 6.1.2.2.3 says it shouldn't (IUOE-2060, same BLR citation area as IUOE-2054 above). This hasn't gone past a Phase 1 stub yet, so treat it as an open gap, not a confirmed rule.

The sanctioned PTD-adjust-create-revert workaround

For the common edge case where an employer is behind on remitting dues but a member otherwise needs a Withdrawal Card bucket created, the validated workaround is:

  1. Temporarily adjust the member's Paid-Through-Date (PTD) forward so the dues-current check passes.
  2. Create the Withdrawal Card bucket.
  3. Revert the PTD back to its correct value.

This is the sanctioned path for the employer-is-behind scenario — not a bypass to avoid, and not something to improvise a different way around. (IUOE-2054)

Things to watch out for

Partial bucket payment via Phone Payment has a known pre-2.19 bug pattern

A partial phone payment against a bucket used to incorrectly post the bucket's full remaining balance instead of just the amount paid (fixed in PRIZM 2.19). If a partial payment ever appears to "pay off" the whole bucket, that's the known bug pattern to check for, not expected behavior. Also by design: the paid-amount detail for a bucket payment is only visible in the payment popup/line-item view, not directly in the bucket grid itself. (IUOE-2492)

Step-up/bucket calculations need a realistic test member

Step Up and bucket amounts depend on the member having a realistic work history and a settled balance before testing — a terminated test member with no current work record, and a member without a settled balance, both produced apparent calculation errors that turned out to be test-scenario artifacts once retested correctly. (IUOE-1904, IUOE-2057)

Bucket payment allocation is only confirmed for one narrow scenario

Bucket payment allocation math (Amount Paid vs. Amount Applied) is confirmed working only for a full walk-in payment against an adjusted bucket. Phone payment, employer payment, and unadjusted-bucket scenarios have shown apparent mismatches and aren't confirmed reliable — see Reconcile an invoice discrepancy report for the fuller accounting-side detail on this. (IUOE-2705)

COBRA buckets follow different rules entirely

Don't use this page's rules for a member's COBRA premium buckets — those are auto-generated monthly by a system job and have their own payment/deletion rules. See Manage COBRA buckets.