Why weren't my CSV columns recognised?

Every bank exports a different layout, so if BrickTrack can't match your columns automatically it opens the mapping step. Point the Date, Amount, and Description columns at the right fields and the rest of the file imports normally.

Why do I have duplicate transactions?

BrickTrack skips rows it has already imported, so re-uploading the same file is safe. Genuine duplicates usually come from two files that overlap in date range — import the non-overlapping range, or delete the extra rows from the transactions list.

Why is my report empty?

A report only includes transactions that are categorised, linked to a property, and inside the selected financial year. Check the date range, confirm anything waiting in Review, and make sure each transaction has a property assigned.

Common errors and how to fix them

Most problems in BrickTrack come from one of four places: importing transactions, categorising them, linking them to a property, or generating a report. Here are the ones people hit most often and how to fix each.

My bank's CSV columns weren't recognised

Every bank exports a slightly different CSV layout, so BrickTrack can't always match your columns on its own. When that happens the import opens a mapping step instead of failing. Tell it which column is the Date, which is the Amount, and which is the Description, then continue — the rest of the file imports normally, and BrickTrack remembers the layout for that account next time.

The amount imported with the wrong sign

Some banks put money in and money out in separate debit and credit columns, and others use a single signed column where expenses are negative. In the mapping step, choose the layout that matches your file. If a batch already imported with reversed signs, delete that import from the transactions list and re-import with the correct mapping rather than editing each row.

I have duplicate transactions

Re-uploading the same file is safe: BrickTrack skips rows it has already seen. Duplicates almost always come from two exports that overlap — for example a full-year file and a monthly top-up covering the same weeks. Import only the range you are missing, or remove the extra rows from the transactions list.

Transactions are stuck in Review

Anything the category suggestion is unsure about waits in Review rather than guessing. Confirm or correct each one once; BrickTrack learns your choice and stops asking for similar transactions. Nothing in Review is counted in your reports until you clear it, so this is the first place to check when a total looks low.

A transaction isn't linked to a property

Deductions are grouped per property, so a transaction with no property assigned won't appear in that property's figures or its report. Open the transaction and set the property. If most of an import belongs to one property, assign it in bulk from the transactions list.

My report looks empty or is missing a property

A report only includes transactions that are categorised, linked to a property, and dated inside the financial year you selected. If a property is missing, confirm it has transactions in that year, that they are out of Review, and that the date range covers your settlement date onward.

Check your spam or promotions folder first, then request a new verification email from the sign-in screen. Verification links expire, so use the most recent one. If you signed up with a different email address than you expected, sign up again with the correct one — portfolios aren't merged automatically.

Still stuck

If none of these match, the fastest path is the in-app feedback button — it sends us the context we need to help. The quick start walks through the whole flow from sign-up to your first report if you want to retrace a step.