Importing your transactions

Automatic bank feeds are coming; today, CSV and Excel upload is how transactions get into BrickTrack.

Export from your bank

Most banks let you export a date range as CSV or Excel from online banking. Grab the full financial year if you're setting up for the first time — you can always top up with a shorter range later.

Upload and match to a property

Head to Transactions and upload the file. If you've got more than one property, BrickTrack asks which property each line belongs to — you can split a single transaction across properties if a cost is shared.

Let auto-categorisation do the sorting

Each line gets a suggested ATO category. Anything the AI isn't confident about waits in Review rather than getting guessed at silently. Confirm or correct it once and BrickTrack remembers the pattern for next time — the more you correct early on, the less you'll need to touch later.

Re-importing without duplicating

If a row matches a transaction you've already imported on date, amount and description, it lands on a Duplicates tab at preview instead of going straight in. Review that tab and confirm which ones are genuine repeats — a rent payment and a loan repayment can land on the same day for the same amount and both be real. It's safe to re-export a wider date range than you need; anything already in BrickTrack gets flagged rather than doubled up silently.