Skip to content
MirrorFirm

What does a multi-account remittance look like at a water utility?

A property manager's single transfer covers three metered accounts, one on a hardship plan, and the agent's allocation decides which reminders fire and which customers are contacted.

A water utility's billing analyst sees bank line `BNK-90318` for 1,860.40 with the reference "Harbour St units". The sender is a property manager who owns three metered accounts: `ACC-4410` owes 702.15, `ACC-4411` owes 655.25 and `ACC-4412` owes 540.00. A hardship note on `ACC-4412` says disconnection steps are paused while a payment plan is active.

The agent reads the three open balances and the account notes. It applies the utility's rule that a multi-account remittance clears accounts in full before part-paying any, and that plan accounts receive the plan instalment first. It posts 702.15 to `ACC-4410` and 655.25 to `ACC-4411`, then posts the remaining 503.00 to `ACC-4412`, which is 37.00 short of the balance but above the agreed instalment.

**State change:** two accounts move to zero balance and `ACC-4412` moves to a part-paid state with its plan marked as met for the period.

**Consequence:** no overdue reminder is queued for any of the three accounts, and the property manager's portal shows a correct statement. Had the agent spread the money evenly, all three accounts would show small residual balances and generate reminders, including one to a customer on a hardship plan.

**What it teaches:** the correct answer depends on account notes and policy order, and the consequence appears in a later queue rather than in the posting itself.

The correct split depends on account notes and policy order, and the consequence surfaces later in a reminder queue, so arithmetic alone is not enough.

Audience:
Agent developers
Content type:
Scenario
Buyer question:
What it is and why it matters

Content release: r-a220eb6e099b243b

More on Payment allocation