Apply an accounting adjustment¶
As a member of Accounting Functions, I want to apply an adjustment to a member's, employer's, or miscellaneous accounting record, so that a discrepancy gets corrected with a clear, auditable trail of why it was made.
Screen: Accounting > Adjustments (nests Member, Employer, and Miscellaneous sub-tabs)
This is a signed-requirement area (Union BLR 2.1.2–2.1.2.7, plus the signed FDD "Reports Union 6.27 Adjustments") that had no training content anywhere on this site before this page — not an oversight in how it was documented, just not yet built.
What's on the Member sub-tab¶
Key fields: Member (via "Choose a member" button), Adjustment Type (dropdown), Current Paid Through Date (read-only once a member is chosen), Notes.
Required fields: Notes is marked red/mandatory — an adjustment cannot be submitted without a comment explaining why it was made. This isn't just good practice here; it's a signed requirement (see "Every adjustment needs a comment" below).
Actions available: Submit, Choose a member.
The Employer and Miscellaneous sub-tabs exist but aren't documented yet
This page covers the Member sub-tab, which is the one captured in this project's crawl of the screen. The Employer and Miscellaneous sub-tabs are visible on the same screen (same two-tab-bar pattern as other Accounting screens) but weren't driven through in that pass — their field layout isn't confirmed yet. Don't assume they work identically to the Member tab until someone verifies that directly.
The rules an adjustment follows (signed requirements)¶
- Every adjustment is "double sided." Per the BLR, each entry should post to two accounts so it's clear where the adjustment came from and where it went — this isn't a one-sided balance tweak.
- Adjustments across funds require the right security rights. The BLR frames cross-fund adjustments as something a user needs explicit "necessary security rights" for, gated by Roles-based Security — not a capability every Accounting-access user automatically has.
- Every adjustment needs a comment. Notes is mandatory for exactly this reason — the signed requirement is "so that it is clear in the future why the adjustment was made," not just a form-validation quirk.
- An adjustment shows up on the member's payment history. Once entered, it's expected to be visible there — if an adjustment seems to have "disappeared," check the member's payment history before assuming it failed to post.
- PEF Disability Dues Adjustment is a named, specific use of this screen: adjusting a member's Paid Through Date specifically to account for a PEF Disability Dues situation, from the Member sub-tab.
Related reports¶
Two signed report requirements are tied directly to this screen, not covered elsewhere on this site:
- Adjustment report — lists adjustments entered within a selectable date range.
- PEF Disability Dues Usage report — based on the effective date a member entered PEF Disability member status, so staff can track the 26-week milestone for that benefit.
Neither has been confirmed live in this project's crawl material yet — treat them as signed, expected report types to look for under Reports > Accounting, not something to guess the exact screen path for.
Things to watch out for¶
\"Money disappearing\" on an Overage→Dues adjustment is usually a display confusion, not a lost-funds bug
A real case traced a "money disappearing" report on an Overage-to-Dues adjustment back to confusing two different numbers: the member's static-bar Balance Due and the Payments-screen Overage figure. The adjustment itself was allowed by design and worked correctly — the actual gap was that the transaction wasn't visible enough across those two surfaces (since fixed). Before escalating a "the adjustment lost money" report, confirm which of the two figures is actually being read, the same core mental model covered in Reconcile an invoice discrepancy report. (IUOE-2311)
Whether cross-fund adjustments should be allowed \"by membership\" is an open question
A real request argued that adjustments should not be allowed cross-fund for certain membership scenarios — this sits in tension with the BLR's own "Adjustments across funds" story (which frames cross-fund adjustment as something a sufficiently-privileged user should be able to do). This hasn't gone past a Phase-1 stub — treat cross-fund adjustment permissioning as an area with a real, unresolved policy question behind it, not settled behavior either way. (IUOE-2380)