42Open approvals
$1.8MPending settlement
0Unmatched exports
Money Room
The room for money that cannot drift.
Capital work breaks in the middle: a payout is approved in one place, matched in another, explained later in a spreadsheet. BunManage keeps the request, policy check, bank reference, match state, and close evidence in one receipt chain.
Approval routingReconciliationAudit exportsSettlement records
Capital receipt chain
From request to close packet.
This is not another finance screen. It is a memory system for the awkward middle: request, approval, money movement, match, exception, close.
Request lands
Invoice, counterparty, bank reference, entity, and purpose arrive as one packet instead of five loose tabs.
Policy bites
Thresholds, reviewer rules, missing evidence, and duplicate signals flag the request before money leaves.
Money matches
Settlement is tied back to the operating event so finance is not reverse-engineering context later.
Close remembers
The final export carries the approval chain, source proof, match state, and exception history with it.
What this room owns
The capital desk has real edges.
Each surface is named after the job it owns. Approval, matching, and close evidence now have places where future pricing, proof, and integrations can naturally live.
Who can move money?
Thresholds, reviewer chains, blackout rules, and missing-proof blocks before a payout becomes regret.
What did it settle against?
Bank movement, invoice line, entity, counterparty, and operating event stay stitched together.
What survives audit?
Every decision, attachment, exception, and export state can be replayed without archaeology.