The short answer
Freeze all unresolved business-action identities, record the first mismatch time and latest evidence time separately, classify the missing or conflicting hop and consequence, apply reviewed age triggers by state rather than one generic SLA, query before retrying, escalate authority as uncertainty persists, and close only when external and local effects or an approved compensation are reconciled.
Operational checklist
Mark your progress, then save a working copy. Selections reset when you leave this page. A checked box is not an approval or evidence of completion.
0 of 8 marked
Key takeaways
Keep three clocks
Record action time, mismatch-detected time, and latest meaningful evidence time. A note, reassignment, or repeated query should not reset the business-age clock.
Preserve provider retention or query deadlines that may make evidence harder to obtain later.
Escalate by state and consequence
| Mismatch | Early action | Age trigger question | Escalation |
|---|---|---|---|
| Accepted, outcome unknown | Query stable identity; block duplicate | When does provider evidence expire? | Provider/incident owner |
| External-only | Protect against second effect | When does local reporting become misleading? | Operations/accounting owner |
| Local-only | Hold reliance and inspect posting | Could money/access/message be misstated? | Domain owner |
| Conflicting receipts | Preserve both and event order | Which source can authoritatively resolve? | Technical plus business authority |
Close the mismatch, not the ticket
Use reconciled complete, compensated, confirmed failed, duplicate representation, residual limitation accepted by authorized owner, or unknown/open. Link late evidence and reopen any downstream report based on the earlier state.
NIST audit-correlation concepts support joining records; the thresholds remain organization-specific.
Edge cases
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.