elevatr guide ·
How to Import a Bank Statement File Carefully
A careful statement import starts with the right file, continues with a row-by-row review, and ends with a sensible check of totals—not an assumption that your bank is connected.
An import is a file workflow, not a bank connection
A statement import can save retyping transactions, but it is worth treating it as a review task rather than a one-click answer. In elevatr, you provide a statement file; the app does not connect directly to banks or keep a live feed of account activity. An import therefore reflects the file you selected, not necessarily everything that has happened since the statement was produced.
That distinction helps set expectations. You choose when to obtain and import a file, then inspect the proposed rows before deciding whether to bring them into your budget. Don’t assume that a new transaction will appear automatically, that an account is being monitored, or that a subscription has been identified or cancelled for you.
Choose a supported file and prepare it
elevatr supports statement imports in CSV, spreadsheet, and PDF formats. The best choice is usually the statement file your financial institution provides in a clear, usable form. CSV and spreadsheet files often present transaction details in rows and columns; a PDF may need more careful checking because the information is arranged for reading or printing rather than as a spreadsheet.
Before selecting a file, make sure you have the intended account and date range. If you download a new statement, keep the original unchanged as a reference. Avoid editing the source file just to make it look cleaner; instead, review the imported draft and make any permitted corrections there. If the file contains several accounts or periods, check which rows belong in this particular import.
- Confirm the file is CSV, spreadsheet, or PDF and that it covers the period you want to add.
- Check that the statement is readable and includes transaction dates, descriptions, and amounts.
- Keep a copy of the original file until you have finished reviewing and reconciling the import.
Review draft rows before importing
Imported statement rows are drafts until you choose to import them. Take advantage of that pause. Scan each row against the statement, paying attention to dates, merchant or transaction descriptions, and whether an amount is money in or money out. A description may be shortened, and a row that looks unfamiliar may simply need a closer comparison with the source document.
If a draft row is wrong, you can edit it before importing. For example, correct a date or description that did not come through as expected, or adjust an amount if the draft does not match the statement. If a row does not belong in this import, remove it from the draft list. Removing a draft row is different from importing it and later trying to correct your records, so make the decision while you are reviewing.
A practical pass is to check every row once for obvious mistakes, then revisit only the rows that are unclear. Don’t force a category or interpretation just because a description is vague. Use the information you can verify from the statement and your own records, and leave uncertain items for further checking rather than treating a guess as confirmed.
- Compare dates, descriptions, and amounts with the source statement.
- Edit draft details that are clearly incorrect before import.
- Remove rows that are outside the intended account or period, or otherwise do not belong.
- Import only after the rows you intend to keep look right.
Reconcile totals with a small, deliberate check
A matching row count is not enough to show that an import is complete. Compare the statement’s transaction activity with the draft rows and check the totals for the same date range. Keep money received and money spent distinct when making that comparison; combining them can make an error harder to spot. Also verify that you are comparing the same account and period on both sides.
For instance, imagine a statement shows three purchases of 12, 18, and 25 units of currency, plus a deposit of 100. The spending total is 55 and the deposit total is 100. Check that the draft contains those three outgoing amounts and the incoming amount, rather than looking only at a net figure of 45. This example is a checking method, not a prediction about anyone’s budget.
If totals do not agree, pause before importing. Look for a missing or extra row, a reversed sign, a duplicated transaction, or a date range mismatch. Correct or remove draft rows as appropriate, then compare again. A difference you cannot explain is a reason to recheck the file and source statement—not a reason to assume the import is accurate.
Import with clear expectations
When the draft rows and totals make sense, choose to import them. You remain in control of that step. A file import does not connect directly to a bank or update itself with future transactions. If you want to keep records current, you will need to obtain and import later statement files as needed, and review each new batch in the same careful way.
elevatr is free forever with optional Pro. Free includes CSV, spreadsheet, and PDF statement import, custom categories, monthly budgets, savings goals, and exports, with up to 100 transactions per month. Pro is $9.99 per month or $74.99 per year and adds unlimited transactions beyond the Free 100-per-month limit, AI receipt capture and monthly summaries, planning tools, recurring reminders, and multi-currency planning with manual FX quotes. Neither plan connects directly to banks.
A final pre-import checklist
A few minutes of checking can make a file import more dependable and easier to understand later. Use this short checklist before confirming the import:
- I selected the intended CSV, spreadsheet, or PDF statement and the correct account and period.
- I reviewed the draft dates, descriptions, and amounts against the statement.
- I edited clear errors and removed rows that do not belong in this import.
- I compared incoming and outgoing totals separately and investigated any mismatch.
- I understand that this is a manual file import, not automatic bank synchronization.