What does a part-payment across two utility accounts look like in practice?
A water utility receives one transfer covering two accounts but falling short of the total, and the billing analyst must apply it under a written policy.
A regional water utility receives bank line `PAY-5521` for 412.60 from a landlord. The remittance note reads 'both units'. The landlord holds two accounts, `ACC-1180` and `ACC-1184`, with open invoices `INV-30417` (268.10, older) and `INV-30422` (190.75). Together they total 458.85, so the payment is 46.25 short.
The billing analyst opens the case from the unapplied-cash queue. Policy `POL-ALLOC-07` says that when a reference names several accounts, funds clear invoices in due-date order across them, and any shortfall stays on the newest invoice. The analyst applies 268.10 to `INV-30417` and 144.50 to `INV-30422`, leaving 46.25 open.
**State changes:** `PAY-5521` moves from unapplied to applied, `INV-30417` closes, `INV-30422` becomes part-paid, and the reminder on `ACC-1184` is rescheduled for the smaller balance. Had the full amount been posted to `ACC-1180` alone, that account would have shown a credit while `ACC-1184` moved to a late-fee stage.
**What it teaches:** one payment changes several linked records, and the right answer depends on a written policy, not on amount matching. A reseller can use this shape to explain to buyers why relational consistency and policy links are the first things to inspect.
One payment changes several linked records, so relational consistency and policy links are the first things a buyer should inspect.
- Audience:
- Licensed resellers
- Content type:
- Scenario
- Buyer question:
- What it is and why it matters
Content release: r-a220eb6e099b243b
Related questions
- Where does an agent sit among the systems in a payment matching process?
- What traits make a payment workflow a good test for an agent?
- What does a multi-account remittance look like at a water utility?
- What does matching incoming payments to obligations involve in a real business?
- Why can't an agent just match payments by amount and reference?
- How does this workflow map onto environment state, tool actions and observations?