01must proveProposed | Splitting uses the read version and a request key to create at least two same-sign parts whose amounts exactly equal the original. ✓ 250.00 split into 200.00 and 50.00.✗ 250.00 split into 200.00 and 49.99 is refused. | validation | api, service, database | test |
02must proveProposed | Only unresolved and unclaimed items can be split or resolved; a claimed item’s refusal identifies its reconciliation. | policy | service | test |
03must proveProposed | Split marks the original resolved, records the approving person and creates parts retaining the parent’s context and evidence with individual amounts and parent links. | lifecycle | service, database | test |
04must proveProposed | Split and write-off close an open overdue exception on the original item. | lifecycle | service | test |
05must proveProposed | Item resolution records a reason and chooses either write-off or another explained resolution. | validation | api | test |
06must proveProposed | Write-off creates a request debiting settlement write-off and crediting merchant clearing for a positive item, reversing those sides for a negative item, dated on the selected open batch with the resolution day retained separately. | calculation | service | test |
07must proveProposed | Write-off leaves the item unresolved when the write-off account or an accepting operational batch in an open period is missing. | validation | service | test |
08must proveProposed | An explained resolution other than write-off creates no ledger request. | policy | service | test |
09must proveProposed | Split and resolution keys replay identical requests, reject changed bodies and distinguish the operations even when their key text matches. | validation | api, service | test |
10must proveProposed | The sensitive administrator resolve permission governs both splitting and item resolution. | permission | api | test |
11Proposed | The console currently exposes neither splitting nor write-off. | policy | console | observed |