Skip to content

Understand bank balances and freshness

5 min readAll workspaces

Bank balances can come from a provider snapshot, a cached provider balance, or a ledger-based balance, and those values are not the same thing. This article explains how to read the balance fields, what freshness means, and why a balance may be shown as unavailable, unknown, or zero.

Before you start

  • You need access to the workspace and the Transactions page.
  • For business bank accounts, the workspace must have transaction review access.
  • For personal transactions, the workspace must have personal mode and personal transactions access.
  • Some balance details may depend on the connected bank provider, the ledger connection, and whether the account is hidden or filtered out.

What the balance fields mean

On the bank account cards, Finanly shows two different balance values. Bank Balance is the provider-side balance shown for that account, and In ERPNext or In your ledger is the ledger-side balance used for comparison. These values can differ because they come from different sources and may be observed at different times.

  • Bank Balance is the bank-side or provider-side balance currently available to Finanly.
  • In ERPNext or In your ledger is the ledger-side balance used for the comparison view.
  • Difference is the gap between the two values when both are available.
  • Balanced means the difference is below 0.01 in the account currency.
  • Last synced shows the most recent sync time available for that account view, if one exists.

If a value is unavailable, Finanly shows it as unavailable or leaves it blank rather than treating it as zero. A missing balance is not the same as a verified zero balance.

Freshness and sync time

Freshness tells you how recently Finanly last observed data for that account. The page may show a relative time such as Synced just now, Synced 5m ago, or No sync info if no usable timestamp is available.

For business accounts, the balance view can use a current connector read, a cached provider balance, or a stored connector timestamp depending on the account and provider. For personal accounts, the page uses the available transaction and provider data for that mode. In both cases, the displayed time is the most recent usable observation the page has for that account, not a guarantee that every number on the page was updated at exactly that moment.

Why balances can look different

A provider snapshot and a ledger balance often answer different questions. The bank balance is the financial institution view of the account, while the ledger balance reflects recorded activity in the connected ledger. If transactions are still being imported, categorized, or reconciled, the two numbers may not match yet.

  • A bank balance can be present even when the ledger balance is still unavailable.
  • A ledger balance can be present even when the bank-side snapshot is unavailable.
  • A stale observation may still be shown, but it should not be treated as a live bank confirmation.
  • For credit card accounts, the balance may use a different sign convention so the amount owed is represented clearly.

Ledger-only and account identity differences

The account you see on the page is the ledger-linked bank account identity used by Finanly, not just a displayed label. Multiple connected sources can have similar names, so the page keeps the account identity separate from the display name and nickname.

Some accounts appear only when they belong to the active ledger source for the workspace. In business workspaces, Finanly filters to ledger-sourced account rows for transaction review. In personal workspaces, the page uses personal-mode account and category data instead. This means two workspaces can show similar-looking accounts with different balance behavior or availability.

  • A nickname changes the display name only; it does not change the underlying account identity.
  • A hidden account can be excluded from the list unless hidden items are included.
  • The same bank name can appear on more than one account, so the page uses the account’s internal identity to keep balances distinct.
  • If a provider connection or ledger source is missing, the account may not appear in the balance list at all.

How to read unavailable, unknown, and zero

Use zero only when the page actually shows a zero amount. If the page shows unavailable, blank, or no sync info, Finanly is telling you that it does not have a confirmed balance for that field.

  • Unavailable means Finanly does not have a usable value for that field.
  • Unknown means the page could not confirm the observation it expected.
  • Zero means the value was actually observed as 0.00 or equivalent.
  • Do not treat missing data as a balance of zero unless the page explicitly shows zero.

This distinction matters when you compare the bank snapshot to the ledger balance. A missing provider read is not proof of a zero bank balance, and a missing ledger read is not proof that nothing has been recorded.

Common recovery steps

  1. Open Transactions and select the bank account you want to check.
  2. Read both the Bank Balance and the ledger balance for that account.
  3. Look at Last synced to see whether the observation is recent or stale.
  4. If the account is hidden, include hidden accounts and check whether it is still present.
  5. If the balance is unavailable, refresh the page or use Refresh to request a newer read.
  6. If the account still looks wrong after refresh, check whether you are in the correct workspace and whether the right ledger and provider connections are active.

If refresh does not change the result, the balance may still be unavailable because the connected provider, cached provider data, or ledger source does not currently have a usable observation for that account. In that case, the safest next step is to review the account’s connection status and compare the bank-side and ledger-side values separately rather than assuming one of them is correct.

Updated

Related guides

We can help

Still need a hand?

Tell us which workspace and page you were using, what you expected, and what happened. Include the time and any request reference shown on screen.

Keep passwords, access tokens and private bank details out of your message. Review screenshots before sharing them.