Process a walk-in or mail-in payment¶
As a member of Accounting Functions, I want to enter a payment a member handed to me in person or mailed in, without needing an invoice to already exist, so that their dues (or other transaction) are posted and tied to the right bank deposit right away.
Screen: Accounting > Payments > Add New Payments
This is a different screen from Post a payment and complete the deposit
Post a payment and complete the deposit covers Process Remittances — applying a payment against an already-Finalized invoice. This page covers Add New Payments, the direct walk-in/mail-in entry screen: there's no invoice prerequisite here at all. If the money is tied to a specific employer/period invoice, use Process Remittances instead; if it's a member paying dues (or another transaction type) directly, with no invoice in the picture, this is the right screen.
Steps¶
- Accounting > Payments > Add New Payments.
- In the Choose Member picker, search for the member. An exact Reg# match auto-selects and closes the modal directly — no grid pick needed.
- Member/Reg#/Status/Type populate read-only once the member is chosen.
- Bank Deposit: pick from the dropdown of open deposits for the selected account.
- Transaction Type: selecting it auto-populates Amount to the member's dues rate (or the applicable special rate — see below).
- Payment Method: Cash, Credit Card, Check, or Money Order.
- Fill Payment Amount and Payment Date.
- Click Post (or Post & Exit).
Signed payment-processing rules (Union BLR 2.1.6)¶
This screen is the "Mail-in" function the signed Union BLR describes (User Story Scenario 2.1.6, "Payment Mail-in processing" — covering both a true mail-in check and an in-person walk-in). The signed requirements under it:
- 2.1.6.1 — enter any amount paid, as necessary.
- 2.1.6.2 — accept any of the listed transaction types: Dues, Initiation fees, various Membership fees (reinstatement, withdrawal, transfer in, etc.), Fed Pac, PEF, Special Events, Merchandise, Special Dues Offers.
- 2.1.6.5 — accept and record payments made with a Gift Certificate, properly recorded as such.
- 2.1.6.7 — overages on a member's account are available for dues payments only.
- 2.1.6.8 — Advance PTD: when a dues payment covers the member's outstanding balance for the period, their Paid Through Date auto-advances.
- 2.1.6.9 — the payment allocates to the correct GL account based on transaction type.
- 2.1.6.13 — Dues special rates (out of work, disabled, COVID layoff, management, out of trade, etc.) are accepted according to the dues rate rules.
- 2.1.6.14 — the check is added to the selected bank deposit.
- 2.1.6.15 — payments process for any active member status (Retired, Management, Salt, Non-Union, Fair Share, Permit Members, etc.).
- 2.1.6.17 — a Member Payment Receipt can be generated for any payment type.
- 2.1.6.18 — a Fed Pac Gift Certificate Redemption report exists under Reports, covering gift-certificate redemptions processed here.
- 2.1.6.19 — any of the listed payment types is accepted: cash, money order, checks, credit card, gift certificates, other.
Things to watch out for¶
PTD overrides do NOT happen here — use Accounting > Adjustments
Signed requirement 2.1.6.15.3 is explicit: when processing a payment via Mail-in (this screen), the user should not be able to override the PTD. Advance PTD (2.1.6.8) is the only PTD movement this screen does, and it's automatic — triggered by the payment amount covering the outstanding balance, not something you set directly. If a member's Paid Through Date needs a manual correction, that goes through Apply an accounting adjustment instead. Don't go looking for a PTD field to edit on this screen — by design, there isn't one.
Cash posts immediately; Check is presumed to hit the same gateway gap as Phone Payment
Payment Method: Cash posts immediately with no external gateway call (PostMailPayment
returns success) — this is the confirmed Walk In path. Payment Method: Check wasn't
tested directly on this screen, but IUOE's FluidPay merchant account isn't set up for ACH
(a merchant-account choice, not a PRIZM defect) — confirmed on the member's Phone Payment
tab, where selecting Check still tokenizes through FluidPay but the charge call always fails
with "no default processor set." Assume Check behaves the same way here until proven
otherwise. See Record a phone payment for
the full writeup of that gateway gap — it isn't re-explained here.