What signs show a mismatch listing covers the whole job?

Before you list a mismatch dataset, check that it represents the whole job and not only the discrepancy.

- **Paired records:** both sides of each mismatch are present, with their own identifiers, dates and amounts. - **Stated cause:** each case has a root-cause label such as timing difference, duplicate, keying error, rounding or missing handover. - **Evidence trail:** notes, messages or system events that a person would consult to reach the cause are included alongside the records. - **Policy context:** tolerances, approval limits and posting rules sit with the case, so the correct fix is defined rather than implied. - **Resolution record:** the reversal, adjustment or escalation that closed the item is recorded with its reason code and the role that approved it. - **Unresolvable cases:** some items correctly end in escalation or no change, so models are rewarded for stopping when they should. - **Generated status:** the listing says the data is generated, and notes where grounding and disclosure risk can be inspected by the buyer.