Which business complications make a correction benchmark meaningful?

Use this checklist to choose correction cases whose operational context changes the decision, so evaluation results reveal business reasoning rather than recognition of a familiar journal pattern.

- Include a disputed source document that requires the agent to distinguish a supported discrepancy from an allegation that still needs investigation. - Include responsibility split across teams, with each role holding a necessary piece of evidence and no role owning the complete explanation initially. - Include a correction that would change a downstream operational decision, such as releasing an order currently blocked by an incorrect account balance. - Include an exception policy whose conditions must be established from evidence, rather than a prominent instruction telling the agent which action to choose. - Include a legitimate original entry followed by a new event, testing whether the agent preserves history instead of rewriting the earlier business position. - Include a request whose stated remedy conflicts with its evidence, requiring the agent to challenge the proposed change while still addressing the discrepancy. - Include a case where the available information supports investigation but not posting, so the benchmark rewards a precise unresolved status and useful next action.