Skip to main content
Before you sync journals to your accounting system, you want confidence that the balances in Breezing match reality. Balance Verification gives every wallet a verification status, an automated check against on-chain and exchange data, a manual attestation flow with evidence for everything else, and a full audit history.

​
Verification Statuses

Each wallet on the Wallets page shows a badge in the Balances column. Hover over it to see how, when, and by whom the wallet was last verified.
  • Verified: an automated balance check matched Breezing’s balances against the source, and nothing has changed since.
  • Attested: a team member manually confirmed the balances and recorded it.
  • Stale: the wallet was verified or attested before, but transactions have been edited or new activity has been imported since. Verify again.
  • Mismatch: the last automated check found a variance above the tolerance (0.01) on at least one token.
  • Not verified: the wallet has never been checked or attested.

​
Running an Automated Balance Check

Open a wallet from the Wallets page and find the Balance verification card.
  1. Click Run balance check.
  2. For supported blockchains, pick the date to verify. EVM chains and Solana support any past date, which is what you want for period closes. Bitcoin-family chains (BTC, BCH, LTC, DOGE, DASH) and exchange APIs only provide current balances, so those checks always run as of now.
  3. The check runs in the background; track it under Running tasks. Behind the scenes, Breezing generates an Explorer Balances Check report comparing its recorded balance for every non-spam token against the explorer or exchange balance.
  4. When it finishes, the wallet status updates to Verified or Mismatch, and the result appears in the history with a link to the full report.
If a check comes back as a mismatch, open the linked report to see which tokens are off, then work through Fix Wallet Balances.

​
Manually Attesting Balances

Some wallets cannot be checked automatically, such as CSV imports, exchanges without API access, or unsupported chains. For those, or whenever you have verified balances yourself against a statement, use manual attestation.
  1. In the Balance verification card, click Mark as verified.
  2. Set the Balances as of date. For a period close, pick the period end date; Breezing shows its computed balances as of that day so you can compare them against your statement or explorer.
  3. Describe what you verified and against what in the note field. The note is required.
  4. Optionally attach up to 3 evidence files (PNG, JPG, or PDF, up to 25 MB each), for example a screenshot of the exchange balance page or a custodian statement.
  5. Click Mark as verified. The wallet status changes to Attested.

​
The Sync Verification Gate

When you sync transactions to Xero, QuickBooks, or Bexio, Breezing checks the verification status of every wallet the sync touches. If any are unverified or stale, a dialog lists them in two groups: wallets that can be checked automatically and wallets that need manual attestation (exchange, CSV, or unsupported chain). From the dialog you can:
  • Run balance check on all checkable wallets at once.
  • Attest each manual-only wallet without leaving the flow.
  • Proceed anyway to sync without verifying. The override is recorded in each wallet’s verification history as “Synced without verification”, along with your reason.
The gate has three company-level modes: off, warn (the default, which allows proceeding), and require. In require mode, only an owner or admin can proceed, and a reason is mandatory.

​
Verification History

The Balance verification card lists the wallet’s most recent verification events: balance checks with their Matched or Mismatch outcome, manual attestations, and sync overrides. Click any entry to see the details: the as-of date, how many tokens matched, the worst mismatch if there was one, a link to the generated report, the balance snapshot, the note, and the attached evidence files, along with who recorded it and when. This history is append-only, which makes it a clean audit trail: you can always show an auditor when balances were verified, by whom, against what, and with what evidence.
Last modified on July 6, 2026