CapitelistHelp Center

Connectivity guide

Step-by-step guide

Import a Bank Statement

Extract bank balances or cash-account rows from a statement without treating every transaction as current net worth.

Start from Cash and check whether the account already exists before importing another statement.

Before you start

Use this workflow when you have a bank, cash-account, payment-account, brokerage-cash or treasury statement and you want Capitelist to draft the cash record for review. The import is not a live bank connection. It reads the file you upload, prepares rows, and waits for you to approve what should become portfolio data.

You are in the correct portfolio.
The statement shows the account name, closing balance, currency and statement date.
You know whether the file contains only balances, only transactions or both.
You have checked Cash so you do not import the same account twice.
You understand that one current balance updates Net Worth; transaction rows are supporting history.

Detailed steps

01

Open Assets > Cash and check the current table

Start in Assets and select Cash. Look at the existing cash accounts before importing anything. If the same bank or cash account is already listed, update that record or exclude the duplicate import row later. Cash is for real cash-like balances, not credit limits, pending transfers or securities you might sell.

Start from Cash and check whether the account already exists before importing another statement.
02

Open Add Capital Item and choose Import Statement

Click Add Capital Item, keep Accounts selected, then choose Import Statement. Use this route for bank statements, cash account files, brokerage cash, Wise or Revolut style accounts, payment accounts and treasury-account statements. Use Cash Account instead when you only want to type one balance manually.

Use Accounts > Import Statement when the file is a bank, cash, brokerage cash, payment or treasury statement.
03

Upload the clearest bank file you have

Upload a PDF, CSV or screenshot that clearly shows the account, balance, currency and date. CSV is best when it includes structured columns. PDF is usually better than a cropped screenshot. If the file hides the balance, currency or account name, Capitelist can still draft rows, but you should not approve them until the source evidence is clear.

Upload a PDF, CSV or screenshot that shows balances and movements clearly.
04

Review the extracted balance and transaction rows

When the review screen opens, read the row counts and warnings first. A balance update is the row that can update Net Worth. Transaction rows explain cash movement under the account. They are useful history, but they do not add or subtract from Net Worth again when a current balance is already imported.

Review the balance row and transaction rows before anything touches Net Worth.
05

Open the Transactions filter and treat those rows as history

Use the Transactions filter to review deposits, withdrawals, transfers, fees and interest lines. Keep them only when they help explain the account movement. Do not treat each deposit as a separate asset. Do not treat ordinary money-out rows as debts unless they are actually outstanding liabilities.

Transaction rows explain account movement. They do not add or subtract from Net Worth again.
06

Open the Capital Item filter and verify the balance row

Use the Capital Item filter to isolate the row that will become the cash account value. Check the detected account name, mapped type, liquidity, amount and currency. The amount should match the closing or latest balance you want in Net Worth. If it is an opening balance, subtotal, converted value or stale balance, fix it or exclude it.

The balance row is the current cash/account value that will become the portfolio record.
07

Import only after the included rows are correct

Return to All and check the import button count before you click it. Included rows will be saved. Excluded rows will not become portfolio records. Import the current balance only once for each real account. If the same account already exists, exclude the new balance row and update the existing account instead.

Commit only after the balance row, included rows, warnings, amount and currency are correct.
08

Open Cash after import and reconcile the result

After import, return to Cash. Confirm the new account name, institution, value, currency and transaction count. The Cash total should increase by the imported current balance. If the total is too high, look for a duplicate account. If the currency looks wrong, open the record and correct it before relying on Net Worth, Forecast or Investment Plan.

After import, Cash should show the new account balance and its transaction-history count.

Field guide

Source file

The bank PDF, CSV or screenshot used as evidence.

Prefer files that show account name, balance, currency, date and transaction rows.
Balance update

The row that becomes or updates the cash/account value in Net Worth.

Use the closing or latest balance you want represented today.
Transactions

Deposits, withdrawals, fees, transfers and interest detected under the account.

Keep them as history; do not count them again as separate assets.
Include

Whether a row will be saved when you import.

Clear the checkbox for duplicates, subtotals, stale rows or rows you cannot verify.
Detected item

The account or transaction name Capitelist found in the file.

Match it to the statement, not just to a label that looks plausible.
Map to / Type

How the row will be stored, such as Cash account or Transaction.

A current account balance should map to Cash account; movement rows should map to Transaction.
Liquidity

How quickly the cash can normally be used.

Daily is normal for bank cash; restricted reserves, escrow or tax cash need notes.
Amount

The value that will be stored for the row.

For the balance row, match the statement balance. For transactions, check sign and absolute amount.
Currency

The currency shown by the statement.

Do not manually convert to the portfolio base currency unless the source already reports that value.
Warnings

Messages explaining how Capitelist interpreted the file.

Read warnings before import, especially when a transaction statement produced both balance and history rows.

Decision rules

What it adds

  • Adds cash accounts quickly while preserving statement context.
  • Helps Forecast and Capital Review understand liquidity.
  • Reduces manual entry errors from long bank documents.

What it does not do

  • The import does not keep the bank account synchronized after upload.
  • A statement balance may already be outdated.
  • Transaction classification is not full bookkeeping.

Common mistakes

What to check

  • Use ending balance, not every deposit line, as the current asset value.
  • Do not import the same account twice under different names.
  • Redact unnecessary account numbers before uploading when possible.
  • Check FX exposure if the account currency differs from the portfolio base currency.

Importing the same bank account twice because the manual Cash record already existed.

Counting every incoming payment as a new asset instead of using the current account balance.

Treating card payments, rent payments or transfers as outstanding debts when they are only completed transactions.

Approving a row from a screenshot that hides the currency or closing balance.

Using an opening balance or subtotal when the closing balance is the current value.

Manually converting the account value instead of preserving the source currency.

Assuming the import keeps the bank synchronized after upload.

Leaving old imported cash records in place after a newer statement replaces the balance.

After you save

  • Check Assets > Cash and confirm the imported account appears once.
  • Compare the Cash total against the statement closing balance.
  • Open Net Worth and confirm assets and liquidity changed by the expected amount.
  • Open the account details if the currency, liquidity or value looks wrong.
  • Keep or attach the source statement when the balance is material.
  • Update the same cash account when a newer statement arrives instead of creating a duplicate.
  • Use transaction rows as explanation, not as extra Net Worth value.

Keep reading