Why is recognising lateness a policy decision rather than a date comparison?

A payment can be past its recorded due date without being eligible for follow-up. The applicable policy may allow a grace period, suspend contact during a dispute or require confirmation that a payment has not arrived through another channel. Recognising lateness therefore involves interpreting business state, not just comparing dates.

In financial services, a credit officer might need to reconcile an invoice, a payment allocation and a contact restriction before opening a collection task. Each record answers a different question: what was owed, what has been received and what action is currently permitted. Missing evidence should affect the decision rather than disappear behind a confident message.

For evaluation teams, this creates a useful separation between detecting an apparent delay and authorising the next action. A task can require the agent to identify the governing rule, retrieve the necessary evidence and either proceed or explain the unresolved condition.

MirrorFirm could generate cases that vary these conditions independently. The resulting evaluation can distinguish policy reasoning from superficial deadline recognition, including cases where the correct result is to hold contact and request verification.