Reporting Treasury Data from Gnosis Safe: A Practical Guide

Gnosis Safe is the standard for institutional crypto treasury management, but it adds real complexity to financial reporting. Here is how to get accurate data without going mad.

Safe's transaction model is fundamentally different from an EOA. Internal transactions, batch calls, delegate calls, and module interactions all appear differently in block explorer data. A simple 'export CSV from Etherscan' workflow breaks down immediately when you try to categorize Safe transactions.

Use the Safe Transaction Service API

The most reliable way to get structured data from a Safe is the official Safe Transaction Service API (transaction.safe.global). It gives you decoded transaction data, signers, execution status, and historical queued transactions. Unlike raw RPC calls or explorer scraping, it is consistent across chains and handles all Safe-specific transaction types correctly.

Handling multi-asset transfers

A single Safe transaction can move multiple tokens in one on-chain call. Most reporting tools treat this as one transaction and miss the individual line items. You need to parse the internal transfer events from the transaction receipt to get accurate per-asset accounting. This is where most manual reporting goes wrong.

How Vault Brief handles Safe wallets today

Today, Vault Brief reads Safe multisig balances and transaction history through Alchemy and Dune Sim — the same path used for any EVM treasury address. Internal-transfer parsing and Safe-specific categorisation (signers, queued transactions, module calls) is on the near-term roadmap; for now Safe transactions are reported as standard ERC-20 / native transfers, which is enough for the treasury-balance and inflow / outflow numbers most monthly reports need. If you operate a Safe and need richer Safe-aware parsing, drop us a note at hello@vaultbrief.io — that input directly shapes the prioritisation.

Get these metrics in every report automatically

Vault Brief generates investor-ready reports from your on-chain data. No spreadsheets.