Why are columns or dates wrong on a Kontuly CSV import?

Applies to Kontuly 0.2 beta Updated

When a CSV statement comes into Kontuly with wrong amounts or dates, the column roles, the First row is a header tick or the Date format in the Import statement window need changing. The preview updates as you change them, so fix them before you click import.

Checks in order

  1. Column roles. Above each column is the role Kontuly will use: Date, Description, Balance, and either Amount (signed) (one column, money out negative) or Debit (out) and Credit (in) (two columns). Set everything else to Ignore. A common mistake is mapping a single amount column when your bank uses two, or the other way round.
  2. First row is a header. Tick it if the first line holds column names. If it's wrong, your first transaction is missing, or the column names appear as a row with an error.
  3. Date format. Australian banks use Day/Month/Year. A file where every day is 12 or less can't be told apart from Month/Day/Year, so check a few dates early in the month in the preview.

Rows that are skipped

Rows that can't be read are shown faded with the reason, and aren't imported:

  • Unrecognised date: the date is empty or in another format. Check Date format and which column is mapped as Date.
  • Invalid amount: the amount isn't a number. Check the amount columns are mapped correctly.
  • Zero amount: a row with no money, often a heading or a "balance brought forward" line. These are safe to skip.

The import button shows how many valid rows will be imported. The preview shows the first 100 rows; all valid rows are imported.

I already imported it wrongly

Unassign any lines that were coded, delete the wrong lines (bin icon in Banking), then import the file again with the right settings. See How do I import a bank statement CSV?

More about troubleshooting