How can we help?

Use this workflow to add a bank or card account in a business workspace with the correct bank, account number, and current ledger account. If a save is already in progress, recover the original request instead of creating a duplicate, and do not treat a missing balance as zero.

Attach a receipt or invoice file to an existing transaction so it can be stored with that transaction for later review. On supported business transactions, a successful upload attaches a PDF, PNG, or JPEG to the linked ERPNext bank transaction and returns the saved file name; it may also return a file URL and the bank transaction reference. This does not approve or post a ledger entry.

Review a transaction’s exact account, party, and category before you save changes, and use Undo to reverse a confirmed categorization instead of starting over blindly. For pending transfer or export outcomes, wait for the original request to finish and use the same request flow only when the app tells you to resume it.

Use the Transactions screens to narrow the list by account, status, source, date, and amount, then review each row’s freshness, markers, and available actions. Business and personal screens are separate, and the controls you can use depend on your workspace mode, role, and enabled features.

You can save a manual transaction in the current workspace and then use the saved-request checker to verify the receipt if the confirmation is not immediate. Choose the correct account first, because the amount must match that account’s verified 3-letter currency before you can save.

Use transfer matching when both bank entries already exist, or record a transfer when you need Finanly to classify the movement from one entry. In business mode, a confirmed transfer can be exported through your connected ledger; in personal mode, the transfer is recorded as a local classification for review.

Use this flow to refresh an existing bank account from your connected ledger, or to continue, cancel, or review an original refresh request. You can only work with the current company and the same saved request; no new financial replay is started from this screen.

Review the preview before posting matched transactions in bulk. You can include or exclude rows, then confirm the run; the app rechecks each row before it posts anything and shows per-row results after execution.

Review transaction suggestions in your current business workspace, then confirm, edit, or undo them only when the row shows the result you want. If AI Matching returns an unresolved warning or no eligible suggestion for a row, treat that as an unavailable or partial outcome, not a confirmed match.

Manage bank account display names and cutover settings in Settings > Account > Bank accounts. Use nicknames and visibility to control how accounts appear in the UI, and use the suggested cutover anchors to mark where seeded history ends and live activity begins without changing the account’s underlying identity, balances, or transaction history.

Use Split when a transaction needs to be divided into multiple lines that add up exactly to the original amount and use the same currency. Use Exclude when a transaction should leave review; it removes the item from the review flow, but it does not delete the original provider record or imported history.

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.