Product guides

Importing a statement: from file to reviewed rows

Bringing in a bank statement as a PDF or CSV takes four stages. Know what happens at each one so nothing surprising reaches your records.

Editorial illustration for Importing a statement: from file to reviewed rows

Typing a month of bank transactions by hand is slow and error-prone. Importing a statement does the typing for you. The add menu offers an import option for PDF and CSV statements, and the process that follows has distinct stages, each with a purpose. Understanding them removes the anxiety of watching a file turn into transactions.

Stage one: choose the file and the account

You start by picking the statement file, and the account it belongs to. Choose carefully. A statement imported into the wrong account makes balances drift and confuses later reconciliation. If you have several cards or accounts, check the name at the top of the statement against the one you select.

Password-protected PDFs cannot be read as they are, and the screen says so. Remove the protection through the bank's own download options if you can, then try again.

Stage two: mapping

For many files, the app can read the columns directly. For files with unusual layouts, a mapping step asks you to tell it which column is the date, which is the description and which is the amount. Take your time here. The mapping offers separate debit and credit columns or a single signed amount column. Choosing the wrong style, or a date read in the wrong format, will cause errors in every row.

Stage three: staging and review

Imported rows do not go straight into your books. They are held as staged rows, which you can review, edit and flag before accepting. Filter chips help you focus on problems. Rows with likely duplicates or odd values are flagged, so your attention goes where it is needed.

  • Check that dates fall in the statement period.
  • Scan amounts against the statement totals.
  • Look at flagged rows first.
  • Edit categories or merchants where needed.

The review step is the heart of a safe import. It is the opportunity to catch mistakes while they are still cheap to fix.

Stage four: confirm and watch the status

Once happy, confirm the import. A status screen shows its progress. When finished, the transactions appear in your list. A reconciliation banner may compare the imported totals against the statement, showing whether opening and closing balances line up.

After the import

Open the transactions list for the period and give it a quick check. Run through the review queue for anything the app wants confirmed. Finally, consider whether new merchants deserve default categories, so the next import is easier.

StageWhat you doWhat it prevents
Choose file and accountMatch file to accountWrong-account imports
MappingConfirm columnsMis-read dates and amounts
Staged reviewCheck and edit rowsBad data entering the books
Confirm and verifyWatch status and bannerSilent mismatches

Overlapping statements

Statements sometimes overlap, for example when a new file starts a few days before the previous one ended. The staged review flags likely duplicates, and the right response is to remove the overlapping rows from the new batch before confirming. Checking the first and last dates of each file before importing prevents the problem in the first place.

If something looks wrong

If an import goes badly, you do not have to live with it. Discarding a batch removes its rows, which is covered separately. Do not try to patch a flawed import row by row; discard and redo it with the correct settings.

Keep original statement files somewhere safe. They are the ground truth against which any later question can be settled.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports