Why a balance differs from the platform

The known balance changes that no transaction records, by platform, how each one shows on the Reconciliation page, and what to do about it.

Where to find it:your-organization.conta.financeReconciliation

Conta Finance does not copy the balance of an account from the platform. It adds up every movement of the account, from its first transaction to now. On most platforms, this gives the balance on the platform exactly, to the smallest unit.

Some balance changes have no transaction. Other changes have a transaction that the data source does not give. In both cases the books cannot see the change, and the two balances differ. This article lists the known causes. They are limits of what the transaction history holds, not errors in your books.

How a known cause shows

Each cause shows on the Reconciliation page as a difference between the Projected balance and the Current balance:

Most causes show as Mismatch, after a short time as Pending verification. See Pending and confirmed differences.
stETH shows as Rebase difference, because its balance grows with no transaction.
A cause worth less than the reconciliation tolerance shows as Reconciled.

"Reads low" below means that the books hold less than the platform. The Delta is then positive. "Reads high" means the opposite.

What to do

Every cause has the same remedy: select Adjust balance on the account row and record a correction. The steps are in Fix a balance mismatch. The date you pick decides the period where the correction counts.

A cause that happens once needs one adjustment.
A cause that comes back, such as rewards, needs a new adjustment when the difference grows enough to matter.
A cause that clears on its own needs no adjustment. Wait for it.

Ethereum and other EVM blockchains

Cause	How it looks	What to do
stETH held before 16 May 2023	stETH grows by rebase, with no transfer. Conta Finance calculates each rebase from 16 May 2023. An account that held stETH before that day reads low by the growth of that period. It shows as Rebase difference.	Adjust once. The difference does not grow after that.
Monad proposer fees	An account that receives the fees of the blocks a validator proposes. The fees are written when each UTC hour ends, so the hour in progress reads low.	Nothing. The difference clears after the hour ends.

Solana

Cause	How it looks	What to do
Validator accounts: identity, vote account and withdrawer	Block rewards and commission arrive with no transaction. Vote fees and withdrawals from the vote account are not in the history the data source gives. Conta Finance calculates them for each epoch from epoch 560. Everything earlier shows as one large difference on each of the three accounts.	Adjust each account once for the period before epoch 560.
The epoch in progress	The epoch in progress is written when it closes. Until then, an identity account can differ by up to a few SOL.	Nothing. It clears when the epoch closes. Do not include it in an adjustment: type the amount yourself.
Epochs that cannot be measured	The validator was down at the end of an epoch. The vote fees of that epoch and of the next one then come from a third party, and can be short by a fraction of a SOL.	Adjust when the amount matters.

A correction that falls in a closed period is not written either, so that epoch keeps its difference. See Close a period.

Cosmos blockchains

Cause	How it looks	What to do
Slashing of a validator	Part of a delegation is burned with no transaction. Rare.	Adjust once for each incident.
Coins received at the launch of the blockchain	The account holds coins from the first block, and no transaction delivered them. The account reads low.	Select Genesis balance on the account page. See Cosmos genesis balance.
History older than the data source	The data source has no transactions before its coverage starts. On Shentu, that is about October 2023. Funding and delegations before that are missing.	Adjust once for each account.
Fees of transactions a validator signs	An account that runs a validator pays the fees of transactions the data source does not list under the account. The account reads slightly high.	Adjust when the amount matters.
Osmosis pool lockups and epoch rewards	Pool shares that come back after unbonding, and pool or superfluid rewards, arrive at the end of an epoch with no transaction. The difference grows with the rewards.	Adjust from time to time.
Refunds of governance deposits	A deposit on a proposal is recorded as a movement out. Its refund arrives with no transaction. The account reads low by the deposit.	Adjust once for each refund, dated when the vote of the proposal ended.

Bitcoin

Cause	How it looks	What to do
Addresses beyond the gap limit	Conta Finance follows an HD account up to 20 unused addresses after the last used one. Coins paid to an address further out are not seen, so the account reads low.	Adjust once.
A transaction the data source left out	The data source did not give a transaction, so it is not in the ledger.	Select Rescan history on the account page. It can recover the transaction. If not, add it by hand. See Add a transaction.

Aptos

Cause	How it looks	What to do
A token held outside the main balance of the account	An account can hold a token in more than one place on Aptos. Conta Finance counts all of them, and the platform figure covers the main one only, so the token reads high. Rare.	Nothing: the ledger is right. Do not adjust it.
A token whose balance changes by itself	Some tokens change their balance with no transfer, like a rebasing token. The account drifts from the platform. Rare.	Adjust when the amount matters.

NEAR

Cause	How it looks	What to do
An account that holds a contract	A multisig, a DAO or a staking pool. NEAR pays such an account a part of the gas of each call to it, in no transaction. The account reads low by a very small amount for each call.	Adjust when the amount matters. An account with no contract does not differ.
The account of a staking pool	NEAR pays a validator its reward at each epoch change, about every seven hours, in no transaction. The account of the pool reads low by every reward.	Track the account that owns the pool, not the pool. Its commission is recorded for each epoch.
A token that the first bridge from Ethereum issued	That bridge wrote no record when it issued a token to an account or took it back. The transfers of the same token are read. The token reads low or high by those amounts.	Adjust once for each such deposit or withdrawal.

Exchanges

Cause	How it looks	What to do
Entries the exchange does not give (KuCoin)	KuCoin hides some entries of its history. Conta Finance rebuilds them from deposits, withdrawals and trades while the account still holds the token. A token sold in full stays incomplete.	Adjust what the rebuild does not cover.
A token the exchange renamed	Old entries keep the old ticker, and the balance uses the new one. Both tickers show a difference: the old one reads high, the new one reads low.	Adjust the old ticker to zero and the new one to its balance.
Rounding	Amounts far below one cent, because Bit2Me rounds before it reports, or KuCoin hides entries too small to notice.	Usually nothing: the tolerance covers them.
Earn rewards with no movement (Bit2Me)	An Earn balance can change with no movement.	Adjust when the amount matters.
History that Binance has no list for, or no longer gives	Binance keeps one list for each product. Conta Finance does not read card purchases, P2P, Binance Pay, Earn rewards or referral kickbacks, and Binance stops giving the old rows of some lists. The currency reads high or low by those amounts.	Adjust once for the old history, and again when the amount matters. See What Conta Finance reads from Binance.

A difference that is not on this list

The most common cause of a Mismatch is not on this list: a transaction that is simply not imported yet. Look for it first. See Fix a balance mismatch. If you find no missing transaction and no cause above explains the difference, write to [email protected].

Why a balance differs from the platform

Related