What is bank statement column mapping?

It assigns source fields such as date, description, debit, credit and balance to the standard fields used by the review table and exports.

Should I edit rows before fixing column mapping?

Fix a systematic mapping issue first. Then review individual exceptions that remain, because row edits do not correct the underlying rule.

What is the safest way to apply this guide?

Start with an authorised, unlocked digital statement and a small representative period. Confirm the source layout, preserve the original file, review the resulting rows against the PDF and complete read the source headings, test known withdrawals and deposits, map references as text, preview several page layouts before relying on the output.

Can this bank statement workflow be completely automatic?

Automation can reduce initial data entry, but it cannot remove source and review risk. Editing many rows before fixing the source mapping wastes time and can introduce inconsistent corrections. Keep a human review step for important financial use.

Which records should be retained after using this workflow?

Retain the original statement, a reviewed master export, correction or mapping notes, control totals and the destination-specific file under your authorised retention policy. These records explain how the source became the converter review table and its Excel, CSV or QBO exporters.

Bank Statement Column Mapping Guide

Map bank statement dates, descriptions, debit, credit, amount, reference and balance columns before editing or exporting converted transactions.