A Solana treasury can show the right USDC balance and still produce an incomplete month-end close. A customer receipt needs an invoice reference, an internal transfer needs both sides matched, and a network fee may belong to a different wallet from the one receiving the payment. Bitwave, Cryptoworth and TRES document Solana accounting coverage. Their most useful distinctions emerge from the transactions a finance team has to explain.
Which accounting platform fits a Solana treasury?
| Platform | Solana-specific evidence | Useful demonstration to request |
|---|
| Bitwave | Separates validator income streams and recognises vote-account activity | Trace one validator reward and a batch of voting fees into a report |
| Cryptoworth | Documents transaction categorisation, staking and custom reconciliation rules | Apply a repeatable rule across a month's wallet transactions |
| TRES | Lists historical balances, staking rewards and DeFi positions in its Solana coverage | Reconcile a period-end balance and drill into its movements |
The shortlist uses each provider's published Solana integration as of 10 November 2026. It compares documented coverage. A journal export, protocol-specific decoder or integration with your accounting system should be demonstrated using your own representative transactions.
Bitwave for validator and staking activity
Bitwave describes importing Solana stake-account rewards by reward period and retaining validator commission information. Its Solana integration also groups frequent voting fees and separates sources such as block rewards, commissions and tips. This matters when an operating wallet contains many small transactions with different business purposes. Ask to go from a grouped line back to the underlying signatures. Bitwave Solana integration · MadeOnSol Bitwave profile
Cryptoworth for repeatable reconciliation rules
Cryptoworth documents automatic wallet imports, staking activity and custom reconciliation rules for Solana. A useful demonstration is to label an internal transfer once, apply the rule across a period and inspect which transactions remain unmatched. Then add a second wallet owned by the same company. Transfers between the two should be identifiable without inflating operating receipts. Cryptoworth Solana month-end documentation
TRES for historical balances and positions
TRES, acquired by Fireblocks, lists transactions, historical balances, staking positions, daily staking rewards and DeFi positions for Solana. Its network page lists feature categories but does not enumerate supported protocols there. A treasury using a particular pool or lending position should request a sample showing that exact position at two period ends. Reproducing an old balance is a different test from displaying the current one. TRES Solana coverage · Reconciliation workflow
A worked acceptance test for a USDC receipt
Suppose a customer pays a 1,000 USDC invoice to treasury wallet A. The sender pays the network fee. The company later moves 600 USDC from A to its own wallet B, paying the network fee from its SOL balance. Starting with zero USDC in both wallets, the end balances should be 400 USDC in A and 600 USDC in B. The company received 1,000 USDC from outside once. Counting the internal move as another receipt would produce 1,600 USDC of apparent inflows.
Give each provider the invoice reference, both treasury public keys, transaction signatures and period boundaries. Request the two ending balances, the internal-transfer match, the actual fee payer and an export retaining the evidence. An accounting team can then apply its own valuation and posting policy. Re-import the same sample to see whether duplicate postings appear.
A portfolio dashboard answers what the treasury holds now. A close needs a reproducible explanation of how it got there. The Solana portfolio tracker comparison covers the dashboard decision; the Solana tax software guide covers individual filing workflows.
