TRES integration

Overview

TRES is Fireblocks' accounting, reconciliation, and financial reporting service. It connects to your Fireblocks workspace with read-only access, ingests your on-chain and off-chain activity, and turns it into reconciled, audit-ready financial records you can sync to your ERP.

Following the Fireblocks acquisition of TRES, TRES is part of Fireblocks but remains a distinct service with its own console, packaging, and help center. Your Fireblocks workspace stays the system of record for custody and transaction execution; TRES becomes the system of record for how that activity is classified, valued, reconciled, and reported.

TRES holds SOC 1 Type II and SOC 2 Type II attestations, and sources financial data directly from blockchain nodes, processed inside that certified environment.

What you can do with TRES

• Automate classification, cost basis, revaluation, and journal entry generation across every wallet, exchange, and custodian you use
• Reconcile every wallet daily against blockchain data, with transaction history validated from genesis to the present against archive node balances
• Generate historical balance reports for any wallet at any point in time
• Sync journal entries directly to your accounting system, including NetSuite, QuickBooks, and Xero
• Track invoices and payments (AP and AR) alongside on-chain activity in one ledger
• Produce realized and unrealized gain and loss reporting, and a full breakdown of DeFi, staking, and validator reward activity
• Generate financial and regulatory reports aligned to MiCA, VARA, CARF, FCA, MAS, and FASB ASU 2023-08

How TRES uses your Fireblocks data

TRES reads your workspace through a dedicated API user with the Viewer role. It can retrieve vault accounts, asset wallets, addresses, balances, and transaction history, but it cannot initiate or approve transactions.

Once connected, TRES resolves each Fireblocks address to its full on-chain history, including activity that predates your Fireblocks workspace, and enriches it with fiat pricing, counterparty labels, tags, and chart of accounts mappings. Vault accounts and asset wallets appear in TRES as internal accounts; external addresses you transact with appear as contacts, which you can name, group, and use in classification rules.

Who uses TRES

Banks and financial institutions

TRES provides a daily reconciled position per wallet, entity, and jurisdiction, along with the audit trail supervisors expect: transaction-level evidence, historical balance attestation, and proof that client assets are segregated from house assets. TRES also connects to more than 10,000 banks, so the fiat legs of a trade or settlement reconcile against the on-chain legs in one ledger.

If your institution receives account statements in SWIFT MT940 or ISO 20022 CAMT.053 format and wants them reconciled against digital asset activity in TRES, confirm the current ingestion path with your TRES contact before you design the workflow.

Payment companies and PSPs

TRES classifies high-volume stable-coin payment traffic with rules rather than manual review, separates customer funds from operating funds, and reports on float positions per corridor and entity. Where you hold client money, the same balance snapshots support safeguarding and client asset reporting.

Crypto trading firms

TRES calculates cost basis across any method you elect, handles internal transfers between venues without creating phantom gains, and reconciles balances across exchanges, OTC counterparties, and your Fireblocks vault accounts. It detects and classifies DeFi and staking positions automatically, including liquidity provision, bridging, rewards, and validator commissions.

Fintechs and exchanges

If you hold assets on behalf of end users, TRES produces historical balance snapshots for any client wallet at any point in time, reconciled against custodian or internal records, supporting license applications and ongoing supervision under MiCA, VARA, FCA, and MAS. Revenue recognition on fees, spreads, and rewards flows into the same journal entries as other activity.

Tokenization issuers and fund administrators

TRES reports across multiple entities and any historical time frame, supporting NAV support files, investor reporting, and reconciliation between on-chain token supply and off-chain records.

Before you start

• You need a TRES package. Existing Fireblocks workspaces do not include TRES by default.
• Only the workspace Owner, Admins, and Non-Signing Admins can create the API user TRES uses.
• Decide which wallets TRES should ingest: the full workspace, or a scoped subset.

Integrate your Fireblocks workspace with TRES

1. In the Fireblocks Console, navigate to Transaction History > Generate report to schedule a demo with TRES.
2. Complete the demo, then work with TRES to purchase the package that fits your reporting requirements and onboard to the TRES platform.
3. In the Fireblocks Console, navigate to Settings > Users and select Add User.
4. Set the user type to API User, enter a name, and set Role to Viewer.
5. For Attach CSR File, upload the CSR file TRES provides at static.tres.finance/TresFireblocks.csr. This integration requires the TRES-provided CSR file; DO NOT generate your own.
6. Select Add User, then send the generated API key to TRES.
7. Confirm your ingestion configuration with TRES, including which wallets to include, how to treat internal accounts and contacts, and your cost basis method.

For the full onboarding steps on the TRES side, including chart of accounts mapping, ERP connection, and classification rules, see Integrate Fireblocks with TRES Finance in the TRES help center.

After you connect

TRES backfills historical activity for the wallets it ingests, which can take time on workspaces with long transaction histories. Once the backfill completes, work through the setup checklist in the TRES help center in this order:

1. Confirm every expected wallet appears under Accounts and shows as reconciled. A wallet marked Unbalanced has a gap to resolve before you rely on its reporting.
2. Resolve transactions missing a fiat value — these can't sync to your ERP and will cause cost basis calculation to fail. Common causes are assets with no market price, tokens that never had a public offering, and NFTs.
3. Set up tags and classification rules so new activity routes to the correct chart of accounts entry automatically.
4. Connect your ERP, then run the pre-sync journal report to validate mappings before you sync anything.