What should a model recognise before treating a disputed charge as an error?

Use this checklist to distinguish a record error from other reasons a customer wants a balance changed.

- Identify whether the requester disputes the recorded event, its price or the obligation to pay. - Separate evidence of incorrect recording from expressions of dissatisfaction or financial difficulty. - Check whether a service concession belongs to a different approval route from an error correction. - Establish whether the underlying transaction occurred before proposing its reversal. - Keep unresolved factual questions visible instead of converting them into assumed corrections. - Select the permitted next step: investigate, refer for a concession decision or prepare an adjustment.

In a utilities task, a customer can reject a charge because the meter reading is wrong or because the service was interrupted. Those requests can produce different records and require different decision owners, even when both eventually reduce an amount payable.

Generated training material can include requests with similar wording but different supporting evidence. The learning objective is accurate problem classification before execution. This helps model labs assess whether an agent understands the reason for changing a record, rather than treating every complaint as permission to reduce a balance.