Reconciliation Problem

What It Models

An exception retains a reconciliation concern and the investigation used to conclude it. Missing money, stale deposits, bank disagreement, drift and manually raised concerns share this work record.

Identity and Attributes

Condition keys prevent repeated detection from duplicating current work. Status records progress, severity controls readiness, and closing retains an explanation with its actors.

Relationships

Subjects identify the payouts, settlement effects or explanations involved. Readiness carries associated concerns with their principal finding and separately lists accepted period concerns.

Invariants

The structured invariants identify investigation, acceptance and retained-note protections. Blocker attention joins the business transaction when enabled; disabling publication leaves business records without attention.

How It Is Stored and Shared

Reconciliation owns the investigation and registers read-only exception metadata for Platform attention. Platform supplies audience resolution and presentation; custom fields are absent.

Open Design Questions

Acceptance currently suppresses future raising of the same condition. Product must decide whether that acceptance should ever be reconsidered, and late-posting review needs an implemented path.