Treasury
See treasury clearly.
Understand where organizational funds sit, what is available for operating needs, and the movement and control context around each destination.
Treasury overviewOrganizational view
Liquidity context
Primary reserve
AvailableReservedPending context
Vendor operationsInternal movement contextReviewed
Approved destinationExternal destination recordKnown
Treasury overview
Location before movement.
Operating fundsPrimary reserveWorking liquidity context
Committed fundsReserved contextObligations remain visible
DestinationsKnown endpointsAuthority travels with movement
Accounts and structure
Organize money by operating purpose.
A treasury view should explain the relationship between reserves, working funds and destinations without turning the page into a portfolio or performance screen.
Organization treasury
ReserveLiquidity context
OperationsWorking funds
DestinationsAuthorized context
Movement historyContextState
Reserve → OperationsWorking liquidityRecorded
Operations → DestinationVendor purposeUnder review
Destination updateAuthority changeRecorded
Movement visibility
Follow why money is moving.
Movement history should carry purpose and destination context, not just direction. Review lifecycle states separately so intent, authorization and downstream completion are never blurred together.
Authorized destinations
Destination context stays close.
Keep ownership, purpose, review status and changes visible around the endpoint a finance team intends to use.
Destination recordVendor operating destination
- Purpose
- Operating expense
- Authority
- Reviewed destination
- Change record
- History retained
Treasury