Expense management
Company crypto
that closes the books
A record for every token that leaves the company — who asked, who approved, which project it belongs to, and where it landed on-chain.
Built on Safe. No custody, no key escrow.
Month end
Crypto spending that nobody can reconcile
The chain is a perfect ledger of amounts and a poor ledger of reasons. Most of what an accountant needs was never written down anywhere.
Spending with no owner
A transfer left the company wallet. Which team's budget it came out of, and who decided it should, is a question with no authoritative answer left to consult.
Receipts that are screenshots
Explorer screenshots pasted into a spreadsheet are evidence of a transaction, not of an authorisation. They prove money moved, not that it was meant to.
Reconstructed at year end
Attributing a year of transfers to projects happens once, months late, from memory — which is exactly when discrepancies surface and can no longer be resolved.
How it works
Record it when it happens, not at year end
Every field an accountant will need is captured at the moment the spend is proposed.
- 1
Every spend starts as a request
Nothing leaves the treasury without a request naming its amount, recipient, project and purpose. The reason is captured while the person who knows it is still asking.
- 2
Projects carry the budget
Requests belong to a project and approvers are assigned per project, so departmental spending separates at the point of decision instead of being sorted out afterwards.
- 3
Approval is recorded, not remembered
Each approval is written to an append-only audit log with the approver, the time, and the exact request they saw. Nobody can edit it later — administrators included.
- 4
The hash closes the line
When the Safe executes, the transaction hash attaches to the request. One record then links the reason, the decision and the on-chain fact together.
Questions about expense records
Can we get the records out for accounting?
The audit log and request history are filterable by project and period, which is what a reconciliation needs — the reason and the approver alongside the transaction hash.
Who can change an audit entry?
Nobody. The log is append-only, so a correction is a new entry rather than an edit. That property is the whole reason the log is worth reading.
Does this replace our accounting software?
No. It produces the authorisation trail accounting software cannot: what was approved, by whom, and which on-chain transfer settled it.
What about spending that already happened?
Past transfers stay on-chain and unchanged. Recording begins when you start routing spending through WorkTGT — there is no back-filling of decisions nobody actually made.
Move your team's money
transparently, starting today
Start free without a credit card. Setup takes five minutes, and your funds stay inside your team's Safe.