Bank Statement to CSV File: Formats Accounting Imports Need

Start with a source CSV, not a universal template

The exact bank statement CSV format depends on the accounting product and import screen. There is no single file that every tool accepts unchanged. The most durable workflow is to keep one reviewed source CSV, duplicate it, and map the duplicate to the destination's current fields without altering the source.

This distinction is practical, not theoretical. Current US QuickBooks documentation requires either Date, Description, and Amount or Date, Description, Credit, and Debit for a transaction-list upload. Xero's current troubleshooting guidance refers to assigning CSV columns to statement fields and requires valid date and numeric amount data. Always check the destination's own instructions on the day you import.

Choose a two-column or three-column source

A two-column source contains Date and Amount. Use it only when the destination explicitly allows Description to be omitted and you accept the loss of merchant or memo context. It can load a bare transaction sequence, but it is harder to recognize duplicates, match activity, or review an incorrect amount.

A three-column source contains Date, Description, and Amount. This is the recommended general-purpose layout because it keeps the essential matching text beside the signed value. StatementMint's standard CSV uses this three-column structure. It does not include categories, journal accounts, tax codes, or destination-specific fields, so those are mapped or added later in the accounting tool.

Understand the signed Amount column

A signed Amount column combines money in and money out into one numeric field. Under the convention used in StatementMint exports, a purchase, withdrawal, or fee is negative, while a deposit, payment, refund, or credit is positive. Store -86.42 and 2450.00 as numbers—not as text containing dollar signs or commas.

The sign describes movement in the exported transaction ledger; it does not assign an accounting debit or credit to a general-ledger account. Bank accounts and credit-card liabilities are accounted for differently, and an import screen may use labels such as spent, received, charge, payment, debit, or credit. Map by the destination's documented meaning and the selected account type, not by the label alone.

Split Amount only when the importer requires it

Some importers request separate money-in and money-out fields. Create that version from a reviewed signed Amount column rather than maintaining two unrelated source files. Put each transaction's absolute value in exactly one destination amount column and leave the other blank; do not place zero in both cells unless the destination explicitly requires it.

Column names are not universal. For example, current QuickBooks documentation describes a four-column Date, Description, Credit, and Debit layout alongside its three-column signed-Amount layout. That is a QuickBooks requirement, not a rule you should silently apply to every accounting product. Confirm which destination field represents money in and which represents money out before uploading.

Keep every field import-safe

Use one header row, one transaction per row, UTF-8 encoding, a consistent date format, and plain decimal amounts. Keep descriptions complete. If a description contains a comma, line break, or quotation mark, use standard CSV quoting; RFC 4180 describes enclosing the field in double quotation marks and doubling a quotation mark that occurs inside it.

Do not insert statement balances, subtotals, page headings, or blank separator rows into the transaction table. Xero's current error guidance specifically identifies invalid date or amount data, blank lines, incorrect field assignment, and malformed preparation as causes of failed imports. A destination may impose additional limits, so its own template remains authoritative.

• Date: use one consistent, destination-supported format.
• Description: preserve the source text and quote embedded punctuation correctly.
• Amount: use a decimal number with no currency symbol or thousands separator.
• Missing value: leave it blank rather than inventing zero.
• Account: import each file into the intended bank or credit-card account.

Map a destination copy field by field

Open the accounting product's manual bank-transaction import, select the correct account, upload a copy of the CSV, and map each source header to the displayed destination field. Check the import preview before accepting transactions. If the product offers a downloadable template, use the current template rather than an old file saved from a prior version.

Do not add Category, Account, Tax, or Payee columns unless the destination documents those fields for this specific bank-transaction import. StatementMint does not categorize transactions or connect directly to accounting software. It creates the source CSV and XLSX; the account owner performs the mapping, classification, and import review.

Prevent duplicates and check the result

Before uploading, identify the newest transaction already present in the accounting account and exclude overlapping rows only after confirming they are true duplicates. Never assume matching Date, Description, and Amount proves duplication; two legitimate purchases can be identical. Use the destination's preview and duplicate handling, then reconcile the imported period after acceptance.

Compare imported row count, first and last transaction, largest money-in and money-out values, and the period boundary with the reviewed source CSV and issued PDF. Save an import note containing the account, file name, period, row count, and import date. That small record makes a later duplicate or missing-period investigation much easier.

Create the source CSV before mapping it

When an issued PDF is the available source, StatementMint produces a clean Date, Description, and signed Amount CSV plus formatted Excel for a completed full statement. Convert the statement, compare the result with the PDF, and keep that reviewed file unchanged.

Then duplicate the CSV and map the copy using the accounting product's current instructions. This preserves a stable source ledger while allowing QuickBooks, Xero, or another destination to use its own headers and amount layout. StatementMint does not send the file into those products for you.

Frequently asked questions