01must proveConfirmed | Payout pages sort by descending accounting day and descending identity within that day, with at most two hundred records and a continuation cursor. | policy | api, service | test |
02must proveConfirmed | The list rejects oversized pages, malformed cursors and dates outside the accepted year-month-day shape. | validation | api | observed |
03must proveConfirmed | Staff can filter payout lists by unit, merchant, processor, reference, inclusive accounting dates, reconciliation and verification states or void status, and search an exact reference or payout number with an optional prefix. | policy | service | test |
04must proveConfirmed | Reconciliation status is calculated from active holdings: open means in reconciliation, finalized means reconciled, and no active holding means unreconciled. | calculation | service | test |
05must proveConfirmed | Unreconciled results exclude voided payouts; the void filter can exclude them or select only them. | policy | service | test |
06must proveConfirmed | A payout read includes evidence, its holding reconciliation and the intersection of state-allowed and permission-allowed actions; a reader receives no write actions. | permission | service | test |
07must proveConfirmed | Payout activity is paged in chronological order from the earliest event. | policy | service | test |
08must proveConfirmed | A payout in another workspace is absent from both individual reads and lists. | invariant | api, database | test |
09must proveConfirmed | Payout reads require the read permission beyond Accounting access, while the console uses the selected business unit for its reconciliation workspace. | permission | api, console | test |