Reconciliation Service Module
What This Service Is For
Reconciliation explains processor deposits and outstanding arrivals within Accounting. It owns payout and preparation work, retains investigations and supplies Close with financial readiness.
Boundary
The service owns the five domain-object designs and their supporting records. Books supplies configuration, Transactions supplies source effects, Batch Management executes accounting, and Close decides period completion; Platform provides shared facilities.
Operations in Words
Staff record and verify payouts, prepare holdings and deductions, approve or reverse explanations, and investigate outstanding money. Separate read operations support summaries and readiness. Internal callers use transaction-bound functions for recording, posting source reads and close assessment.
Events and Jobs
Module-local audit records, attention items and scheduled occurrences have different delivery semantics. There is no reconciliation lifecycle event stream or owned durable state machine; shared Accounting execution dispatches the daily work. No examined code calls a model, so inference lists remain empty.
Consistency Guarantees
The structured consistency rows define applicable commit boundaries and their limits. Atomic approval requests can remain unposted, console saving can partially commit, and attention can be disabled. Workspace records use forced row-level isolation; global timing seeds are read-only reference data. Code and migration evidence support these mechanisms, but the unavailable Platform standards do not establish independently verified cross-platform compliance.