Need help?
Find answers right here

Common questions first, then detailed articles on uploads, categories, accounts, plans, and privacy.

Questions

Frequently asked

Do I need an account to use the free tier?

No. The free tier is completely anonymous: drop a CSV and go. Your uploads are stored on our servers and tied to a session cookie.

What happens if I clear my cookies?

On the free tier, your data is gone. On Personal and Pro, sign back in and everything is still there.

Can I upgrade later without losing data?

Yes. When you sign in, your anonymous session data migrates to your account automatically.

What counts toward the transaction limit?

The limit is based on how far back your transactions go, not the number of transactions. 1 months means any transactions within the last 30 days.

Articles

Detailed answers

5 articles

Importing statements from supported banks

The parser expects original bank CSV exports. The safest path is to export transactions directly from internet banking, keep the file untouched, and avoid PDF, Excel, OFX, or QIF downloads.

Before you upload

Use the original export from your bank and keep the file in CSV format. The app is built around bank-specific parser rules, so even small column changes can break detection.

  • Supported banks are ANZ, ASB, Kiwibank, Westpac, BNZ, and Wise.
  • Choose the transactions export from internet banking, not a PDF statement from the documents or statements area unless the bank explicitly gives you a CSV transaction export there.
  • Do not open and re-save the file in Excel, Numbers, or Google Sheets before upload.
  • If your bank offers CSV, OFX, QIF, JSON, TSV, PDF, or Excel, choose CSV.
  • You can upload more than one file into the same session.

ANZ

In ANZ Internet Banking, open the account, click Export, choose the date range, then pick CSV. The parser supports the normal ANZ transaction export and ANZ loan-account CSV exports.

  • If ANZ defaults to Excel, switch it back to CSV before downloading.
  • ANZ documents and old statements are usually PDFs, which are not supported for import.
  • ANZ may exclude unprocessed transactions from CSV exports, so a very recent card payment can appear in internet banking before it appears in the CSV.

ASB

In FastNet Classic, use Search and export transactions for the account or card you want, then export the results as CSV. The parser supports both standard ASB account CSVs and ASB credit-card CSVs.

  • ASB Document Centre is useful for PDF statements, but the app needs the CSV export instead.
  • ASB can include a few summary lines before the real header row, which is fine as long as the original CSV is untouched.
  • If you are exporting a credit card, use the card transaction export rather than a monthly PDF statement.

Kiwibank

In Kiwibank internet banking, open the account from the Accounts overview, then use the Export icon on the transaction history screen and choose CSV. Kiwibank also offers JSON, OFX, QIF, and PDF, but only CSV is supported here.

  • Statement Vault downloads are PDFs, not import files for this app.
  • If you need a specific range, apply filters first, then export the filtered transaction list as CSV.
  • Kiwibank exports are limited by the bank to the selected range shown in transaction history.

Westpac

In Westpac One online banking, choose the account, select Export transactions, set the date range, then download CSV. Exporting transactions is available in online banking rather than the mobile app.

  • Westpac also lets you download statements, but those are not the same as the CSV transaction export the parser expects.
  • If you are in the app, move to online banking for the export step.
  • Use the transaction export for the account you want to analyse, not a generic statement PDF.

BNZ

In BNZ Internet Banking, open the account, click Export, choose the date range and CSV format, then download the file. The parser supports BNZ account CSVs and BNZ credit-card style CSVs that include a processed date.

  • BNZ transaction history exports are the right source. Printed or saved transaction-history PDFs are not supported.
  • If you are reconciling, BNZ recommends exporting processed transactions; that matches the CSV format the app expects.
  • If the file came from a summary screen instead of transaction history, export it again from the account transaction view.

Wise

In the Wise app or on the web, open your NZD balance, tap the three dots, choose Statements and reports, then create a statement, pick a date range (up to 365 days), and download the CSV. From the home screen you can also reach it via your initials → Statements and reports → Statements.

  • Pick the CSV format, not PDF, XLSX, MT940, QIF, or CAMT.053.
  • Export your NZD balance. Wise statements are per-currency, and the app only accepts NZD. A USD or AUD statement is rejected so foreign amounts are never counted as dollars.
  • Wise caps each statement at 365 days, so download multiple files for a longer period and upload them into the same session.

If the file still fails

The next thing to check is whether the bank changed its export structure or whether the wrong export type was used.

  • Try a fresh export directly from the bank.
  • Check the first row of the CSV before upload. It should look bank-specific rather than generic or spreadsheet-formatted.
  • Check that the file came from the correct account or card export flow.
  • Keep the exact parser error message so you can compare it later or send it through if needed.

Fixing wrong categories and review decisions

Categorisation is rule-based and transparent, which is fast but not perfect. Ambiguous merchants will need occasional manual correction.

Why categories can be wrong

Transaction descriptions from banks are often inconsistent. The same merchant can appear under multiple labels, and generic descriptors can map to more than one category.

  • Some merchants share payment processors.
  • Some bank descriptions are too short to identify the real merchant.
  • Transfers and refunds can look like normal spending until reviewed.

What to do in the app

Override the category where it matters and use the review flow to clean up the obvious mismatches first.

  • Fix high-value or recurring merchants before one-off edge cases.
  • Use the ledger and review queue together when you need to spot patterns.
  • Saved overrides persist on Personal and Pro, while free-tier changes stay tied to the session.

Anonymous sessions, sign-in, and cookie retention

The free tier is session-based. Signing in attaches your session to an account so you keep your uploads and overrides.

How the free tier works

Anonymous usage is tied to the current session cookie. That keeps the app lightweight, but it also means browser cleanup can remove access to your saved data.

  • Free tier data is session-based.
  • Clearing cookies can remove access to that data.
  • The Personal plan keeps data across sessions and devices with 3 months of history.

What happens when you sign in

Signing in keeps your current session's data and attaches it to your account, so you do not start over.

  • Existing anonymous data migrates into the signed-in account.
  • Overrides and uploaded data remain available after login.
  • This is the cleanest path if you want to keep working across devices or browsers.

History limits, upgrades, and what changes by tier

Tier limits are date-based rather than row-based. Upgrading mainly changes how much history you can see and whether your data persists.

How history limits work

The app looks at transaction dates, not the total number of transactions in the file. Older transactions can be hidden even if the file uploads successfully.

  • Free shows the last 1 months.
  • Personal shows the last 3 months.
  • Pro unlocks unlimited history.

What changes when you upgrade

Upgrading removes the main storage and history constraints without changing the core CSV-first workflow. The pricing page shows the current plan breakdown.

  • Personal adds persistence across sessions and devices.
  • Pro adds full history and priority support.
  • You can upgrade after starting on the free tier without losing your current work.

Privacy and deleting your data

The app never asks for your bank login. You can wipe uploads in the app; email us to close an account.

What the app does not do

This app never connects directly to your bank account and never asks for your bank credentials.

  • Uploads come from exported statements only.
  • Bank usernames and passwords are never required.
  • The app stays focused on file-based analysis rather than live banking integrations.

Deleting your data

You can wipe spending data from the app, or email us to close the account.

  • Delete all data removes uploads, category overrides, custom categories, and renamed labels. Your account stays until you ask us to close it.
  • The Privacy Policy and Terms of Service pages cover the formal details if you need the legal version.
Still need help?

Reach out by email
and we’ll take a look

If you are stuck on imports, categories, account access, or billing, send a note to support@tallio.co.nz. Include the bank, what happened, and any error message you saw.

Email support