Finance Outflows

Purpose and states

Outflows controls planned and completed spending. The route distinguishes draft, submitted, approved, scheduled, paid, rejected, cancelled, and reversed states. Counts and amounts are shown per currency; rejected/cancelled drafts do not become cash movement.

Filters, rows, and detail

Search and filter by lifecycle, due date, account, event/cost dimension, payee, owner/approver, evidence, amount, and currency. Rows show payee, purpose/reference, amount, due date, scope, state, owner, evidence/approval health, and payment status. Detail includes request fields, versions, timeline, approvers, threshold/policy result, evidence, external payment reference, journal effect, provider delivery, and audit receipts.

Create and lifecycle commands

Create/edit requires payee, payment account, event/category/account dimensions, exact amount/currency, due date, reference, purpose, and required evidence. Submit freezes the review version. A different authorized checker approves or rejects. Schedule and mark paid require the current approved record; cancel/reverse follow state and period rules. Compatible bulk actions apply only to explicitly selected rows.

The server enforces thresholds, maker-checker separation, period locks, account/currency compatibility, outstanding amount, idempotency, and current version. A provider success message is not payment proof without canonical paid state, journal link, and receipt.

Recovery

On timeout or duplicate warning, inspect the record by reference and idempotency before retrying. Provider failure leaves the authoritative outflow in its safe prior or explicit retryable state. After posting, use reversal/correction rather than cancellation. Escalate a payment without a balanced journal or an action credited to the wrong actor.