Treasury Desk follows a payment from its first draft to an approved proposal, simulated execution and a matching receipt.

Available balances and approved spending are shown separately; approval does not reserve funds.
Create a single payment or a batch, choose recipients and submit it for review. Switch between three fictional owners to collect two distinct approvals, discuss the proposal or request changes. Each submitted revision preserves the details that were reviewed. Changing those details requires a new revision and fresh approvals.

Review the payment details and collect approvals from two distinct owners.
Revision comparisons show what changed, while earlier approvals and change requests remain in the history. Editing a saved recipient does not rewrite the recipient details already attached to a submitted proposal.

A submitted revision keeps its own details, while earlier revisions remain visible.
Execution checks the current approvals and available balances, including the simulated fee. A successful batch commits every payment, the fee, its receipt and the executed status together. Approved proposals do not reserve funds, so a proposal can still fail its final balance check.

The simulated receipt and ledger debits are committed together.
The recipient directory, proposal discussion, activity view and exportable ledger make the full workflow inspectable. Failed saves preserve pending input, and conflicting edits across tabs have explicit recovery choices. A separate clean sandbox lets visitors create their own examples without changing the sample treasury.
The interface uses navy navigation, warm neutral surfaces and blue actions, with payment details and approval status kept close together. On mobile, the proposal, discussion and decision controls form one vertical review flow.

Batch details, discussion and approval controls in a 390-pixel mobile viewport.
Built with React, TypeScript, Vite and IndexedDB. This is an independent portfolio simulation with fictional owners, balances and recipients. The owner switcher simulates the participants; no wallets, blockchain networks or real transactions are connected. Changes stay in the current browser profile.