Outstanding Settlement Item
What It Models
A settlement item records a single processor money effect that may increase or reduce a later deposit. The same collection supplies matching candidates and the outstanding-money view.
Identity and Attributes
Effect keys prevent repeated observation from creating another item. Financial facts remain fixed, arrival dates are calculated when eligibility is established, and outstanding standing is derived for the requested day.
Relationships
Reconciliations hold items through claims and create manual items within their drafts. Concerns investigate missing arrivals; readiness uses the effects to explain clearing and period positions.
Invariants
The structured invariants distinguish service checks from database constraints. In particular, service logic fills eligibility dates once, while database triggers protect financial identity and external references.
How It Is Stored and Shared
Transactions records effects through Reconciliation’s transaction-bound port. Rhythm supplies timing seeds and holiday calendars; Books owns merchant overrides, and these records have no customer-defined fields.
Open Design Questions
Product must distinguish timing policy from operational defaults. Dispute references remain unchecked, and write-off has no implemented undo command.