A bank transaction CSV is a file of rows and columns that you can open in a spreadsheet or import into a spending tracker. A CSV export can contain purchases, salary, refunds and transfers in the same file. For a spending record, each of those entries needs a purpose before any totals make sense.
Match the export period and columns
Australian banks use different menus and export options. CommBank documents CSV export in NetBank. Westpac’s Online Banking export instructions for businesses show choices for accounts, date range and date format. The range and account details help you identify which transactions the file covers, especially if you keep an export for each month.
On a copy of the file, identify the date, amount and description columns. Some exports have one signed amount column. Others have separate debit and credit columns. Open at least one purchase and one incoming payment in your bank’s transaction history and match them to the signs or columns in the file. That gives you a reference for how your bank represents money in and money out.
Dates such as 05/06/2026 are ambiguous across software settings. In an Australian day-first export that date means 5 June. A copy using 2026-06-05 carries the same date without relying on month-first or day-first settings. If your statement shows a purchase date and a posting date, pick a consistent field for your spending periods and preserve the original export for reference.
Sort transactions before adding up spending
In a fictional AUD example, a bank CSV shows a grocery debit of AUD 84, a grocery refund of AUD 14 and an AUD 300 transfer from the transaction account to a savings account held by the same person. The purchase adds AUD 84 to gross grocery spending. If the report tracks net grocery spending, the refund reduces that category to AUD 70. The transfer moves money between accounts and has no effect on the household’s grocery spending.
A credit card payment is another transfer in a report that already includes the individual purchases from the card export. Counting both the AUD 84 grocery purchase and the payment that later clears the card bill duplicates spending. When using separate files, the matching payment out of the bank account and payment into the card account help reconcile that movement.
Overlapping export ranges can also repeat a row. A transaction identifier, if available, gives you one way to compare rows from the same account. Without it, compare the account, date, amount and description with the original transaction history. Two genuine purchases at the same shop for the same amount can occur on the same day.
Review the prepared file in FinTarget
FinTarget’s Expenses guide covers the Import CSV flow. It maps date, amount and description, then previews up to five valid rows before saving. One selected expense category and payment method apply to the batch. If a file has several categories or payment methods, separate batches preserve those distinctions.
The importer reads a negative amount as a positive amount, so a refund left in an expense file would add to spending. In the example, importing the purchase and the refund together would record AUD 98 in expenses. An expense batch containing the purchase alone records AUD 84. Keep the AUD 14 refund separate for a report where you account for refunds explicitly. The preview, valid row count and a check against the prepared file help you confirm the batch matches the entries you meant to save.