Skip to content

Bank statement upload problems

Only CSV and XLSX are accepted

The upload screen overstates this

The dialog advertises PDF, CSV, XLS and XLSX. The server accepts .csv and .xlsx only and refuses the rest:

Invalid file type. Please upload a CSV or Excel (.xlsx) file.

This is a known defect in the wording, not in the upload. Convert to CSV or .xlsx first.

.xls — the old Excel format — is not accepted despite being offered. Open it in Excel and save as .xlsx or CSV.

PDF statements cannot be imported. Ask your bank for CSV; every Saudi bank offers it in online banking.

If the file is silently ignored

Dropping an unacceptable file on the upload area may do nothing at all, with no message. If nothing happens when you drop a file, that is what occurred — check the extension is .csv or .xlsx.

Rows that go missing

Clix reports how many rows it skipped. That count does not include every dropped row.

Rows with a date it cannot parse or an amount it cannot read are dropped silently and are not counted in the skipped total. So a statement can import "successfully" with fewer transactions than the file contained.

Always check the imported count against your statement. If they differ, the usual causes are:

Cause Fix
An unusual date format Reformat the date column to YYYY-MM-DD
Amounts with currency symbols or text Strip to plain numbers
Thousands separators the parser rejects Remove them
Header rows, totals or blank lines mid-file Delete them
Merged cells in an .xlsx Unmerge, or save as CSV

Preparing a file that imports cleanly

  1. One header row, then data — no bank logo block, no summary rows.
  2. A date column, a description column, and an amount column.
  3. Plain numeric amounts. Negative for money out, or a separate debit/credit column.
  4. No merged cells, no footnotes, no totals row.

CSV is more reliable than .xlsx because it cannot carry formatting that confuses the parser.

After the import

Imported transactions are matched against invoices in Payments → Bank reconciliation. Matching needs something to match on: an invoice reference in the transaction description, or an exact amount. A bank transfer with a bare reference and a merged amount may need matching by hand.

When to contact support

  • The count imported is materially short of the file and you cannot see why.
  • A .csv or .xlsx is refused as an invalid type.
  • The file imports but every row is dated wrongly.

Send the file with the problem rows. Write to support@goclix.ai.