How to track expenses from a bank CSV
A bank CSV is a spreadsheet of transactions you can use to track spending without keeping a bank connection active. The useful part is turning those rows into a total you can explain. Start with one account, a complete month, and a copy of the original file.
Download one complete period
In your bank’s transaction history, choose the account and date range you want to review, then look for a CSV download. A CSV contains rows and columns; a PDF statement is a different format. Keep the original download so you can compare it with any changes you make.
Start with posted transactions from a completed month. If your export includes pending entries, keep those separate: a pending purchase may later appear again with its final amount. Record which account and dates the file covers before combining it with another export.
Check the date, description and amount columns
Find the transaction date, merchant or description, and amount. Check a purchase you recognize against your bank’s history. Some banks use negative amounts for money leaving the account; others use separate debit and credit columns. Do not assume that a positive number always means income.
Dates such as 03/04/2026 are ambiguous without knowing the source format. Check the export’s convention before changing it. If you make a working copy, an unambiguous format such as 2026-09-03 is easier to review. Retain the original descriptions until you have checked your mapping.
A statement ending balance is not a transaction amount. Import only the fields you need, and check the preview in your tracker before saving. A CSV can contain sensitive details, so there is no need to share the full file just to ask for help with its format.
Separate purchases, refunds and transfers
The fictional example below uses negative numbers for money leaving a checking account. Purchases total $70. A $10 grocery refund reduces net spending to $60. The $200 transfer to another account you own is movement between accounts, so it does not belong in that spending total.
Treat a credit-card payment the same way when the card’s purchases are already in your tracker: counting both would count the same spending twice. Income is also separate from a purchase total. Keep these distinctions visible before comparing categories.
| Date | Description | Amount | Treatment |
|---|---|---|---|
| 2026-09-03 | Groceries | −$45.00 | Purchase |
| 2026-09-05 | Train fare | −$25.00 | Purchase |
| 2026-09-08 | Grocery refund | +$10.00 | Refund |
| 2026-09-09 | To own savings | −$200.00 | Transfer |
Reconcile the import before reviewing categories
Compare the number of imported rows and several known transactions with the original export. Check the first and last dates, then look for missing amounts or unexpected signs. Match like with like: a total of all account movements will differ from a total that excludes income and transfers.
Avoid importing overlapping date ranges without checking what is already present. Two purchases can share a date, merchant and amount, so do not delete an apparent duplicate solely because those fields match. Compare with the bank’s transaction history first.
Once the records agree, group purchases into a few useful categories and open the transactions behind the largest changes. Repeating the same account selection and date range next month makes the comparison more meaningful.
Use CSV tracking in Loaf Budget
Loaf Free includes manual accounts and CSV imports. In the iPhone app, review the fields you choose to import and check the resulting transactions before using a spending total. CSV parsing happens on your device; the records you choose to import are stored and synced in your Loaf account.
Loaf is preparing its iPhone App Store release for US adults aged 18 or older with US-dollar accounts. Loaf Accounts on the web manages account access and connections; CSV spending tools are part of the iPhone app. You can use the review method above in a spreadsheet while waiting for the release.