The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | createPayout | Record the deposit’s merchant, signed money, reported day and processor reference. | CAP-ACC-REC-001 | The payout is numbered, manually entered, unverified and waiting for reconciliation. | test |
| 2 | createReconciliationBatch | Start an explanation for that payout. | CAP-ACC-REC-008 | An open draft begins with the negative payout amount as its difference. | test |
| 3 | listReconciliationCandidates | Compare suggested candidates with the complete candidate view. | CAP-ACC-REC-008 | Expected captures and refunds include their matching reasons without amount-combination proposals. | test |
| 4 | claimReconciliationItems | Allocate the settlement effects that belong to the deposit. | CAP-ACC-REC-009 | Claims change the difference and the displayed preparation progress. | test |
| 5 | addReconciliationManualItem | Document the processor fee and reserve hold. | CAP-ACC-REC-010 | The explanation reaches zero difference while remaining open. | test |
| 6 | finalizeReconciliationBatch | Attempt finalize as its preparer. | CAP-ACC-REC-011 | Missing approval authority or the preparation guard prevents finalization. | test |
| 7 | finalizeReconciliationBatch | Have an independent eligible approver finalize. | CAP-ACC-REC-011 | The record becomes finalized, the payout reconciled and accounting requests retain the transfer and recognition effects. | test |
| 8 | batch posting of the operational batch | Post the carrying operational batch. | CAP-ACC-REC-014 | Each pending request receives its balanced reconciliation entry. | test services-accounting:modules/reconciliation/tests/integration/services/batch-lifecycle/finalize-posts-to-subledger.integration.spec.js#leaves no request pending: each is posted |
| 9 | /console/{tenantId}/accounting/reconciliation | Inspect the Reconciliation Center views. | CAP-ACC-REC-019 | Service-backed payout and settlement records show the completed explanation without prototype money. | test |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 4 | A concurrent preparer uses an earlier draft version. | Refresh after the version or active-holder refusal. | The surviving claims remain exclusive and totals stay consistent. | test |
| alternate | 4 | Processor references establish authoritative matches. | Accept the supported candidates together. | The referenced effects enter the explanation. | test services-accounting:modules/reconciliation/tests/e2e/reconciliation-matching.e2e.spec.js#claims the two captures carrying PX-1083 at tier 1, balancing RB-10001 |
| failure | 7 | The explanation differs by one cent, a claimed item became resolved, or no operational batch accepts its requests. | Reject finalization with the relevant financial or batch refusal. | The draft stays open; a missing batch rolls back all writes. | test |
| failure | 5 | The fee’s required default account has not been configured. | Refuse the eventual finalize and identify the missing account purpose. | No recognition is requested until configuration is complete. | test |
| Id | Statement | Provenance |
|---|---|---|
01 | Accounting produces one deposit transfer and the required manual recognitions without duplicate effects. | test services-accounting:modules/reconciliation/tests/e2e/reconciliation-scenario.e2e.spec.js#step 7: posts the fee 22500, the reserve 5000 and the bank 972500 against the clearing account, each balanced |
02 | Competing allocations retain one active claim and consistent committed totals. | test |
03 | The preparer is refused and an independent eligible person completes finalize. | test |
04 | The console displays service-backed financial records rather than invented prototype money. | test |
End-to-end policy: required: Browser coverage is needed to establish the staff workflow across screens; separate API evidence supports the financial and permission decisions.