Why some statement lines were skipped or flagged

Why you see this

When you import a bank statement, IzzyTap does not blindly load every row. It quietly drops rows that are not real transactions, warns you about dates it could read two ways, and skips any line you have already imported before. This keeps your books clean and stops the same payment appearing twice.

You will see these messages on the Which column is which? screen (as amber warnings) and in the green banner after the import finishes. Here is what each one means.

Lines with no date or no amount are skipped

On the mapping screen you may see an amber note like:

3 line(s) were skipped (no date or no amount, e.g. opening-balance or summary lines).

A row is skipped when it has no readable date, or when it has no money movement (its amount is blank or zero). These are almost never real transactions. Typical examples are:

• The opening balance or closing balance row.
• Sub-total and summary lines at the bottom of the statement.
• Blank spacer rows.

This is normal and nothing to fix. A bank statement of, say, 40 transactions often shows one or two skipped lines because of the balance rows.

Dates that could be read two ways are flagged

UAE statements are usually written day first, as DD/MM/YYYY. But a date like 04/03/2026 could mean 4 March or 3 April. When IzzyTap meets dates that could be read either way, it uses the UAE day-first reading and warns you:

5 date(s) could be read two ways, we used day-first (DD/MM/YYYY). Check they look right.

The lines are still imported, they are just flagged for a quick check. Look at the Date column in the preview. If a transaction you know happened on 4 March shows as 4 March, day-first is correct and you can carry on. Dates written as 2026-03-04 or 04 Mar 2026 are never ambiguous, so if your bank offers that format it avoids the warning entirely.

Lines you already imported are dropped automatically

You can safely import an overlapping statement (say, last month and this month share a few days) without creating duplicates. After the import you will see a banner such as:

Imported 28 transactions · skipped 6 already-imported lines.

IzzyTap recognises a line it has seen before by its date, amount, description and running balance, and skips it. The skipped number here is not an error. It is the count of lines that were already in this account from an earlier import.

If you re-upload the exact same file, every line is a duplicate, so you will instead see:

Every one of those 34 lines is already imported, nothing new to add.

That message means the import worked correctly and there was simply nothing new to bring in.

Once your lines are in, move on to Match a line vs categorise it when reconciling.