Skip to content
MirrorFirm

What would a generated task for an insurance short-pay look like?

A task fixes a premium instalment, a bank line that is short by a fee-sized amount and a grace deadline, so grading checks the posting and the timed follow-up.

An insurer's premium team holds policy `POL-5520`, paid by monthly instalments of 142.00 with a 14-day grace period before cover is suspended. Instalment `INS-5520-06` fell due on the 3rd. On the 12th, bank line `BNK-71204` arrives for 124.00 with the reference "5520 June". The payer is 18.00 short, probably because a bank fee was deducted.

A generated task starts with that state: the line, the policy, the instalment schedule, the grace rule, and a policy note that short-pays inside a stated tolerance can be accepted with a follow-up. In this task the tolerance is 10.00, so 18.00 is outside it.

The correct action is to apply 124.00 to `INS-5520-06` as a part payment, leave 18.00 outstanding, and create follow-up case `CASE-0412` for the policy servicing team before the grace period ends on the 17th. An agent that marks the instalment as paid would close the item and drop the reminder, and the policy would lapse unnoticed on the 18th. An agent that rejects the payment would leave the customer with no recorded money and the same risk.

**What it teaches:** a task pack can encode a deadline inside the state, so evaluation checks not only the posting but whether the follow-up exists and is timed before the consequence.

Tasks can encode deadlines inside the starting state, so evaluation checks whether the follow-up exists in time, not only whether the posting is right.

Audience:
Agent developers
Content type:
Scenario
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Payment allocation