A statement can help you catch up on expenses you've missed. It can also contain payments you've already entered, money coming in and dates outside the month you're working on.
That's why the preview deserves a little attention before you save. The file may be correct while your interpretation of its columns isn't.
Begin with a purchase you recognise
Pick a familiar transaction in the original statement and find it in the preview. Check the date, description and amount together.
If you can't match that one purchase, pause before importing the rest. A date format may have been read differently, or the amount may have come from the wrong column. It's easier to notice this with a transaction you remember than with a screen full of unfamiliar merchant names.
Keep the original statement available while you review. The preview is there to help you prepare entries; it isn't a replacement for the source document.
Make sure money out means money out
Some statements have separate columns for payments and receipts. Others use a single amount with a sign or a label to show its direction. A balance column may contain a number on every row without representing a purchase at all.
In BudgetQuest's statement flow, check the column mapping and proposed expenses before saving. Money coming into the account shouldn't be mistaken for spending just because it appears beside the same date and description fields.
Transfers deserve a closer look too. An entry on a statement doesn't automatically tell you how it belongs in your budget. Review what happened rather than treating every row as a new purchase.
Check the dates and existing entries
An exported file may cover more time than you intend to import. BudgetQuest provides an import date range, and entries outside its logging window may be excluded.
Review the selected dates before wondering why a row is missing. Then check purchases you've already logged through another route, such as a receipt upload or direct entry.
The app can flag rows as already logged, but it's still worth checking similar entries yourself. Two purchases can share an amount, and the same purchase can have different descriptions in different records.
When the file won't read cleanly
A readable spreadsheet export and a scanned image aren't the same kind of input. An unfamiliar layout, an image-only document or a protected file may not give you a usable preview.
Don't confirm a batch just because most of it looks plausible. If you can't get a reliable result, you can use the statement as a reference and enter the missing purchases manually.
After saving, look over the expenses you've added and the current plan. Importing a file isn't an automatic bank connection; the result still depends on what you selected and reviewed. A short check now is easier than untangling several questionable entries at the end of the month.