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 run a Wallet Integrity Check to find and reconcile the missing or duplicate transactions behind it.

​
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.

​
Checking Balances on a Block Explorer

Whenever you want to verify balances by hand, whether to double-check an automated result or to prepare a manual attestation, compare Breezing’s balances directly against a block explorer. Breezing supports 80+ blockchains and exchanges, which means a single wallet address might hold tokens on Ethereum, Polygon, Optimism, and more. Check each network against its respective explorer (like Etherscan or Polygonscan).
  1. Navigate to the Wallets page in Breezing.
  2. Select the wallet address you want to verify.
  3. Open a new tab and go to a block explorer, such as Etherscan for Ethereum. Paste your wallet address to pull up the live token balances.
  4. Back in Breezing, click the Filter button.
  5. In the Network filter, select the exact network you are checking (e.g., Ethereum). This hides transactions from other chains so you can compare apples-to-apples.
  6. Compare the token balances listed in Breezing (e.g., your total ETH or specific DAO tokens) against the balances reported by Etherscan.
  7. Repeat the process for other networks by changing the filter in Breezing to Polygon and checking Polygonscan, etc.
Once you have confirmed the balances match, record it with a manual attestation (see above) so the wallet shows as Attested. If the balances do not match and you haven’t started categorizing transactions yet, the quickest fix is to delete the wallet connection and re-add it; a fresh read usually resolves a dropped API pull. If you have already started working on the wallet, run a Wallet Integrity Check instead to find and reconcile the exact discrepancies without losing your work.
All right, cool. Once you got your wallet address in, now you need to verify the balances are accurate. So, what you’re going to do is you’re going to you see kind of there’s a a wallet here. I added the Treasury wallet. There’s an ops wallet. So, I need to verify these balance. So, I’ll go to the Treasury wallet first. I’ll select the wallet address up here. I’m going to go to Ether Scan. Throw an Ether Scan. Throw that wallet in there. It’s going to give me kind of the balance. And then I now need to verify. So, these are all the balances that I’ve for all the transactions I’ve added. I’ve added 55 of them. I first just need to filter for just the Ethereum network because again I’m just checking E ether Ether scan right now which is on the Ethereum blockchain. Click filter and you see it’s kind of like filtered out the transaction. So two transactions were not related to Ether Scan. So that’s pretty important. So now I want to verify that this Ethereum balance matches with this Ethereum balance right here. And it looks like it does. 062464 0644. And then you do kind of the same thing all the way down. You come down here look at Dow. the Dow balance is 64906. Look at Dow 64906. Looks like it’s matching pretty well. Um, that’s kind of what you want to do mostly. And then once you kind of have done it for Ethereum, you then want to kind of see what other chains there are. You see there’s like one for Polygon. So now you want to check Polygon. And the way you do Polygon is again you come down here, you then select the uh the chain in, you select Polygon, go ahead and filter it. There’s two transaction polygon. And now don’t worry about this negative balance on Madic because this is actually they changed their symbol recently to pull. So that’s why it’s appearing negative right now. So yeah, you go to polygon scan. Take wallet as well in here. You then just want to throw it in here. And then you want to check the 544831. 5483. It does match once you subtract this one. So there you go. Um that’s good to go. If the balances do not match, the best way to do it is to just read the wallet. So, if you haven’t done any work yet, the best way to do it is just read the wallet. Click here, delete the wallet, and then again, just do the same steps and just read it. Usually, that kind of fixes the problem. Sometimes there might be like a slight delay on the API, but yeah, that kind of gives you an idea how to work this. And yeah, looking forward to showing more

​
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 August 10, 2026