Every branch, one screen
Cash balances, thresholds, and requests — the full picture the moment you sign in.
Every approval, accounted for.
Flow Ledger routes disbursement, payment, and retirement requests through the approval chains your organization already runs — branch by branch, department by department, with a record of every decision.
New to Flow Ledger? Ask your administrator for access to your workspace.
How a request moves through Flow Ledger.
Four stages, the same ones your finance team already follows — just with a system tracking every handoff.
-
1.0
Submit the request
Staff raise payment, disbursement, or retirement requests tagged to a cost code, department, and branch — so every request starts with the context finance needs to review it.
-
2.0
Route it for approval
Multi-stage and parallel approval groups move the request through the right people, with per-stage thresholds and approver scopes. Edit a workflow later, and requests already in flight keep running on the version they started on — nothing breaks mid-approval.
-
3.0
Release the funds
Approved disbursements post to the branch cashbook. Cash counts reconcile what's on hand against what's been recorded, branch by branch.
-
4.0
Close the loop
Retirement requests tie spending back to the original disbursement — with the difference and any refund due tracked alongside a full activity log of who approved what, and when.
See Flow Ledger at work.
Five screens from a live workspace — the same views your finance team would open today.
Chains you already run
Sequential and parallel approval stages, configured to match how your team signs off.
Every request, tracked
Amounts, branches, and status for every payment and disbursement request.
Reconciled, branch by branch
Cash counts against what's on hand, across every branch in one ledger.
The loop, closed
Retirements tie spending back to the original disbursement, with the difference tracked automatically.
Built for organizations, not just users.
Every tenant is its own workspace, with its own people, permissions, and record of who did what.
| Multi-tenant workspaces | Every organization gets an isolated workspace — its own branches, departments, roles, and requests. |
|---|---|
| Roles & permissions | Granular, per-tenant roles decide who can submit, approve, or administer — down to individual permissions. |
| Single sign-on | Sign in through your identity provider. Logout stays in sync across sessions via backchannel logout. |
| Activity log | Every request, approval, disbursement, and retirement is recorded and attributable. |
Ready to route your first approval?
Get started with your Flow Ledger workspace.