--- id: CON-ACC-REC-004 name: Reconciliation Problem feature: FEAT-ACC-REC-05 product_area: accounting module: reconciliation revision: 2 status: draft product_intent: confirmed implementation_evidence: observed source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f definition: >- A reconciliation exception is a retained investigation or policy decision about a payout, settlement item or reconciliation. It can come from a detector or a person and keeps the problem, responsible work and resolution together. owned_by: MOD-ACC-REC synonyms: - exception - reconciliation problem - blocker - warning not_to_be_confused_with: - a refusal of a command - a close readiness finding - an attention item facets: - name: Problem category meaning: >- The category identifies missing money, an unexplained deposit, drift, bank disagreement or a manually reported concern, with later import categories reserved. used_for: Understanding detection and resolution. - name: Close significance meaning: Blocker and warning distinguish concerns that prevent close from information for review. used_for: Prioritizing readiness work. - name: Work status meaning: 'Open, investigating, resolved and accepted describe investigation progress and its conclusion.' used_for: Managing the exception queue. - name: Affected records meaning: Subjects connect the problem to its financial records and navigation targets. used_for: Inspecting the underlying money. - name: Investigation record meaning: 'Owner, checklist and immutable notes preserve who works the concern and what they find.' used_for: Coordinating accountable investigation. - name: Condition identity meaning: The detector’s key identifies repeated observations of one condition. used_for: Avoiding repeated open problems. - name: Policy acceptance meaning: 'A recorded reason accepts the understood condition, with independent approval for blockers.' used_for: Distinguishing approved risk from repaired money. - name: Period context and money meaning: The anchor day assigns period context and the amount describes the financial exposure. used_for: Assessing which period needs attention. - name: Required attention meaning: Active blocker publication reaches people holding the unit’s reconciliation responsibility. used_for: Making unfinished work visible. relationships: - to: CON-ACC-REC-002 statement: Settlement exceptions organize investigation of an item’s missing arrival. provenance: observed source: 'services-accounting:modules/reconciliation/services/persistence/reconciliation-exceptions.ts' - to: CON-ACC-REC-001 statement: Payout exceptions capture bank disagreement or unfinished deposit work. provenance: observed source: 'services-accounting:modules/reconciliation/services/persistence/reconciliation-exceptions.ts' - to: CON-ACC-REC-005 statement: Readiness associates financial findings with relevant exception records. provenance: observed source: 'services-accounting:modules/reconciliation/services/persistence/reconciliation-exceptions.ts' - to: CON-ACC-REC-003 statement: Reconciliation exceptions identify discrepancies in an explanation or its related payouts. provenance: observed source: 'services-accounting:modules/reconciliation/services/persistence/reconciliation-exceptions.ts' lifecycle: - state: Open meaning: The concern is recorded and remains available for investigation. how_it_changes: 'Investigate, resolve, accept or let its detector clear it.' - state: Investigating meaning: The concern is being worked while remaining active. how_it_changes: Return it to open or conclude through resolution or acceptance. - state: Resolved meaning: The concern is closed with an explanation of its resolution. how_it_changes: A detector may reopen it when its condition recurs. - state: Accepted meaning: The condition is retained as handled under policy. how_it_changes: Current raising suppresses accepted conditions even though transition rules permit detector reopening. acted_on_by: - CAP-ACC-REC-003 - CAP-ACC-REC-015 - CAP-ACC-REC-016 - CAP-ACC-REC-017 - CAP-ACC-REC-020 visible_to: - ACT-ACC-017 - ACT-ACC-018 - ACT-ACC-007 - ACT-ACC-019 - ACT-ACC-011 evidence: - >- Inspected concept support: db/reconciliation-exceptions.table.ts; services/persistence/reconciliation-exceptions.ts, reconciliation-blocker-items.ts, bank-mismatch-exceptions.ts; services/exceptions/*; rules/transitions.ts, blocker-attention.ts; attention/reconciliation-blockers.attention.ts; metadata/reconciliation-exceptions.object.ts; docs/reconciliation/architecture.md §13. - 'Inspected concept support: components/accounting/reconciliation/exceptions-screen.tsx.' supersedes: [] --- # Reconciliation Problem ## What It Is A reconciliation exception gives an unresolved financial concern a continuing place to be worked. Rhythm can detect overdue settlement, an old unexplained payout, inconsistent totals or bank disagreement. Staff can also record a concern that automatic checks cannot understand from financial data alone. In each case the record keeps the question visible after the original screen or request is gone. The exception brings together a readable title, severity, affected records and investigation context. Its period anchor matters to close assessment, while an owner, checklist and notes support the work of explaining the condition. Those details let finance staff distinguish an active concern from a previous concern already concluded under policy. There are two kinds of conclusion. Resolution records that the work is complete or its condition no longer holds. Acceptance records that an authorized person understands the remaining condition and permits it under policy. A blocker needs independent acceptance approval; a warning does not use the same two-person process. ## What It Is Not An exception is a saved work record, while a command refusal is an immediate response to a particular attempted action. A close-readiness finding is recalculated for an assessment rather than stored as the investigation itself. An attention item helps the responsible person discover a blocker but does not replace its financial record or its resolution history. ## How It Is Used Preparers investigate affected money and record what they learn. They can assign work, move an active concern into investigation and append notes. The service also supports checklist work and manual problem creation that the current console does not expose. A product manager should account for that gap when evaluating the end-to-end staff journey. Approvers review acceptance requests rather than treating a requested acceptance as a completed decision. Controllers inspect remaining blockers before closing a period. Daily and hourly work serve different purposes: daily detectors identify financial conditions, while hourly attention repair restores their visibility to responsible people. Neither replaces a person’s financial investigation. ## Its Facets **Problem category** explains the condition being investigated. **Close significance** distinguishes a blocker from a warning, and **work status** describes progress independently of severity. **Affected records** connect the concern to the money. **Investigation record** preserves owner, checklist and notes. **Condition identity** lets detectors recognize another observation of the same concern. **Policy acceptance** keeps the decision and its independent approval when required. **Period context and money** place the exposure in the assessment. **Required attention** distributes active blocker work through responsibility assignments. ## How It Relates The exception concerns payout, settlement or reconciliation records, and the operations on those records can explain its condition. Readiness associates it with the principal financial finding to avoid counting one problem twice. Platform delivers attention to the assigned responsibility holders; it does not decide whether the financial concern is resolved. ## What It Could Become The product should decide when accepted conditions need reconsideration, because the transition vocabulary allows reopening while current detectors suppress acceptance indefinitely. Duplicate and late-after-close concerns also need complete detection and review paths. Future processor imports can add evidence-led concerns, while console checklist and note-permission work can make investigation consistent with the service.