Detecting Reconciliation Cases

Detecting Reconciliation Cases A data-flow diagram generated by Archify. 01 / Capture 02 / Compare 03 / Classify 04 / Triage Source records · usage, billing, rate card · 01 / Capture · synthetic fixtures Source records usage, billing, rate card synthetic fixtures Immutable facts · versioned evidence · 02 / Compare · current projection Immutable facts versioned evidence current projection Settlement · within tolerance · 03 / Classify · no action request Settlement within tolerance no action request Case · mismatch or ambiguity · 03 / Classify · active investigation Case mismatch or ambiguity active investigation Review queue · evidence-led triage · 04 / Triage · reviewer work Review queue evidence-led triage reviewer work normalised facts provenance within tolerance deterministic unresolved residue case trigger case evidence review input Legend primary data data store data flow

Evidence becomes durable

  • • Each imported assertion is immutable and provenance-stamped
  • • Matching uses the selected current version

Deterministic exits are cheap

  • • Within-tolerance correspondences settle automatically
  • • Reviewer attention focuses on unresolved residue

Cases have a narrow purpose

  • • A case represents one unresolved correspondence
  • • Repeated detection reuses an active case