Skip to content
MirrorFirm

What happens to a plan when one instalment is missed and a grace extension is applied?

A utility hardship team applies a grace extension to a missed instalment, and the change cascades through ordering, end date, reminders and audit notes, showing why single-row checks are not enough.

The hardship team at a retail energy provider holds ARR-3301, an arrears arrangement for account ACC-5520. The balance is split into six fortnightly instalments, and the third was due on Friday. The payment did not arrive.

A collections officer opens the case. The record shows the plan status as active, a missed-payment counter of one, and a policy that allows one automatic grace extension of seven days before the plan is flagged for review. The officer, or the agent standing in for them, applies the extension to INST-3 only.

The state change has several parts. INST-3 moves its due date by seven days, which pushes it past INST-4, so the ordering rule forces INST-4 to move as well. The plan end date shifts, the reminder queue gains two new entries, and an audit note is written naming the policy clause used.

The consequence of a partial edit is concrete. If only INST-3 changes, two instalments fall on the same day, the customer receives conflicting reminders, and the plan ends earlier than its own final row.

**What it teaches:** a single action cascades through ordering, dates, notifications and audit. A grader should check the whole resulting schedule, not just the row the agent touched, and should confirm that the agent used the grace clause rather than inventing an exception.

One action in a schedule touches many records, so a good task grades the whole resulting state and the policy clause relied on.

Audience:
Environment builders
Content type:
Scenario
Buyer question:
What it is and why it matters

Content release: r-a220eb6e099b243b

More on Repayment scheduling