Configure Employer+ invoicing settings¶
Things to watch out for¶
A multi-fund Super User can see the same field group stacked several times with no header
When a Super User has access to multiple funds, the per-fund-duplicated field groups (like the four Invoice Preference fields) can appear stacked one after another with nothing labeling which fund each group belongs to. This is by design per BLR 7.2.5.1.4 — the fields really are meant to repeat once per fund — but the missing header made it look like the UI was double-rendering by mistake. If you see a field repeated several times with no labels on Employer+, check whether it's one row per fund before assuming it's a bug.
Invoice Sort Order is a config field, not a defect, when invoice ordering looks wrong
If an invoice's member ordering looks wrong, check this tab's Invoice Sort Order field before filing a new ticket — it's commonly set to jobsite-then-member instead of Member Alpha, and that's a config correction on Employer+, not a bug in the invoice itself. See roles/accounting/reconcile-invoice-discrepancies.md for the fuller invoice-discrepancy workflow this feeds into. (IUOE-2447)
Invoice Delivery Option defaults differ by fund — don't assume one fund's default applies to another
Union-fund Invoice Delivery Option is overwhelmingly defaulted to email; H&W is the opposite — overwhelmingly USPS, with only a handful of pre-existing email employers. The two funds were migrated/configured independently, so a default you've confirmed in one fund's Employer+ sub-tab does not carry over to another fund's sub-tab on the same employer.
Where these settings get used¶
Employer+'s Invoice Grouping, Sort Order, Delivery Option, and Billing Cycle don't do anything visible on this tab itself — they drive how invoices are built and delivered downstream. See roles/accounting/build-and-finalize-an-invoice.md for where Grouping/Billing Cycle take effect, and roles/accounting/reconcile-invoice-discrepancies.md for troubleshooting an invoice that doesn't match what you'd expect from this tab's settings.
Who can do this¶
| Role | Access |
|---|---|
| Super User | Add/Update (all funds) |
| Business Agent | Not Visible |
| Management | Not Visible |
| Membership Staff | Add/Update (Employer+ Union) |
| Accounting | Not Visible |
| Contract | Not Visible |
| H&W Staff | Add/Update (Employer+ H&W) |
| ETF Staff | Add/Update (Employer+ ETF) |
Employer+ is split into one sub-tab per fund, and each non-Super-User role that can touch it at all only touches its own fund's sub-tab: Membership Staff on Employer+ Union, H&W Staff on Employer+ H&W, ETF Staff on Employer+ ETF. Every other role (Business Agent, Management, Accounting, Contract) has View Only or Not Visible access to Employer+ — it isn't part of their job. Super User is the only role with Add/Update across all three fund sub-tabs at once.
The Employer+ tab is where an employer's invoicing/billing configuration lives, per fund: Number Of Buildings, Dues Ded Flag, Pac Ded Flag, and the four fields that actually drive how invoices get produced — Invoice Grouping (Employer or Jobsite), Invoice Sort Order ("member alpha" or "member within jobsite"), Invoice Delivery Option (email or USPS), and Invoice Billing Cycle (monthly or annual) — each repeated once per fund (Union, H&W, ETF). Save Changes is the only action on this tab.
If you need to query these fields directly (PRIZM Query, not the UI), note that the backing
entity is per-fund, not a single Fund-selector-scoped view — v_pq_shop_plus for Union vs.
v_pq_shop_plus_HW for H&W, with different field-id suffixes on each. See
Understand fund-sharded entities and
prizm-queries/README.md for the full schema note; it's not repeated here since this page is
about the UI configuration, not the query layer.