What records and relationships could a generated mismatch release contain?

A generated release for this workflow can contain more than two mismatched rows. The useful content is the surrounding structure.

**Core records**

- The two records in conflict, from two systems with different identifiers and update times. - Related transactions: reversals, partial settlements, amendments, credit notes. - Master data such as accounts, suppliers, patients, meters or products.

**Process records**

- The exception or case, with its owner, status and history. - Handover notes between shifts or teams. - Approval requests and decisions.

**Rules**

- Tolerances, authoritative-source rules, approval limits and cut-off times.

**Hidden labels**

- The root cause, the correct action, acceptable alternatives and the expected final state.

**Relationships**

Links between records matter as much as the fields. An invoice that was amended after a payment run, or a claim split across two remittances, only makes sense when the links are present and can be followed.

The records are generated and are informed by direct observation of how businesses work. They are not real business records. A buyer can ask for variation in cause type, domain and difficulty, and should inspect a sample for grounding and any resemblance to real entities before relying on it.