Export a CSV from the bank, keep the original unchanged, import a working copy, map date, description, and amount columns, preview several rows, and verify totals before accepting. Back up existing app data first.

Prepare the file

  1. Download the statement directly from the bank or e-wallet.
  2. Store the untouched original for reference.
  3. Check the date range and account identity.
  4. Remove summary rows from a working copy if the importer cannot ignore them.
  5. Confirm whether spending uses negative values or a separate debit column.

Never upload a statement to an unknown online converter merely to change delimiters. A financial file can contain names, account references, balances, and detailed behavior.

Check each column mapping

CSV fields to verify before importing
CSV fieldCheck
DateDay/month order, four-digit year, and any time value
DescriptionMerchant or transfer text remains readable
AmountDecimal and thousands separators are interpreted correctly
DirectionDebits become expenses and credits become income
AccountEvery row enters the intended Squirio account

Squirio provides mapping and a preview before import. Inspect the first row, a debit, a credit, and any unusual transaction. If the same date range was imported previously, stop and prevent duplicates.

Verify after importing

Compare the number of accepted rows, total credits, total debits, and closing balance with the statement. Spot-check descriptions and dates. Keep the original file until the account has been reconciled.

After import, follow the daily expense routine for new activity and create a new application backup. The free tracker guide explains export and backup options.