A transaction CSV needs a mapped date, description and amount. The amount can come from one signed column or separate money-in and money-out columns. Review the mapping before checking rows against the books.
- Keep one row per bank movement and include a clear header row when available.
- Map the Date and Description fields to the corresponding source columns. If the file uses a payee as its description, check that it identifies the movement clearly.
- Choose the amount-column layout that matches the export, then verify several money-in and money-out examples in Preview.
Optional Payee, Bank reference and Currency columns can preserve useful source detail. They do not replace the required date or a valid amount.
Check the source, not only the headings
Banks use different labels for similar fields. A column called Value might be the transaction amount, while Balance is the running account balance. Map the actual movement amount and inspect the result against the original export.
If a row lacks a required value, correct it from source evidence or exclude it from the current import. Do not invent dates, descriptions or amounts merely to make the row pass validation.
Was this article helpful?
Tell us whether this answered the question you came with.