Bank statement CSV: check the format before an accounting import
Updated · 6 min read
Corrected October 12, 2026: removed unsupported platform schemas and direct-import guarantees.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Identify the importer before changing the file
Record the software product, country edition, account type and actual import feature. A bank-feed upload, expense import and journal import can be different tasks even within one product. Obtain that feature’s current template or instructions; do not copy another platform’s headers.
For example, Intuit’s QuickBooks Desktop bank-feed instructions specify a bank-downloaded .qbo Web Connect file for Web Connect. A CSV does not become that file by renaming its extension. QuickBooks Online is a separate product; do not transfer an Online CSV workflow to Desktop.
| What you have | Decision before importing |
|---|---|
| Bank-offered file for the exact software | Confirm account, period and that software’s supported format |
| Transaction CSV | Check the importer’s fields, date interpretation and amount direction |
| Issued PDF (Portable Document Format) statement | Extract transaction rows, then verify them against the document |
| Combined or multicurrency record | Separate account and currency identification before mapping; do not infer either from an amount alone |
LocalExtract processes one PDF at a time on your device, including local OCR (optical character recognition) for scans, and exports date,description,amount CSV. It does not export .qbo files or synchronize accounting accounts. Review downloads and limits.
Read the raw CSV, not only the spreadsheet display
The example follows RFC 4180’s informational CSV description; importers may require other dialects.
This synthetic file contains three transaction records and three fields per record:
date,description,amount
2026-03-02,Customer payment,250.00
2026-03-03,"Office supplies, downtown",-40.00
2026-03-05,Account fee,-10.00
The comma inside the quoted description belongs to that description. Splitting every comma as though it ended a field would move the amount into the wrong column. Do not repair a decimal-comma file by globally deleting or replacing commas; delimiters, decimals and descriptions need different treatment.
Open a copy through Excel’s Data → From Text/CSV import, inspect the delimiter preview and use the appropriate conversion options for your version. Microsoft explains that directly opening CSV uses default format settings, which can reinterpret dates and numeric identifiers. Preserve leading zeros as text when they are identifiers.
Resolve dates and money before mapping
Do not guess whether 03/07/2026 means March 7 or July 3. Compare it with the source statement’s date convention and period, record the interpretation, and create the target date format in a separate column or working copy. Keep the original value until the check is complete. An unambiguous teaching example does not establish what a particular importer accepts.
This example defines deposits as positive and withdrawals as negative for one invented USD deposit account. Its currency is stated here because the three-field file has no currency column. A credit-card liability or another target importer may use a different direction. Compare one known incoming entry and one known outgoing entry with the source and import preview. Do not reverse every amount just because a column is called Debit or Credit.
Test completeness separately from arithmetic
For the invented example, an opening balance of 1,000.00 USD, deposits of 250.00 USD, withdrawals of 40.00 USD and a fee of 10.00 USD produce 1,200.00 USD. This check applies only if those are all posted movements for that exact period and the balances use the same convention.
A matching total still cannot detect every error: omitting a +40.00 and a −40.00 movement leaves the net change unchanged. Check transaction count, first and last dates, individual descriptions, signed amounts and all source pages as well. Do not add statement totals as new transactions, or manufacture an adjustment simply to force a match.
When the target expects Quicken QFX, CSV repair is a different task
For Quicken Classic US Web Connect, record the exact product, Windows/Mac platform, version, subscription status, financial institution, requested connection method, original downloaded filename and the last observed stage/error. A readable, nonempty CSV or QFX file cannot establish that this institution still supports that connection. Quicken’s Web Connect troubleshooting requires a bank-supported QFX download and online validation using a supported product/subscription; QIF is not a Web Connect replacement.
Distinguish “no bank file downloaded,” “file downloaded but did not open in Quicken,” and “Quicken received the file and returned an error.” For the second branch, locate the actual download and use the product’s documented import interface if appropriate; a file-association issue is different from institution support. Do not rename CSV/PDF to QFX or edit institution identifiers to bypass validation. Quicken expressly excludes third-party PDF-to-QFX files from its support for this route.
Preserve the observed interface rather than treating one help label as universal. Quicken’s Windows bank-import guide and troubleshooting page use different import-menu wording. The troubleshooting page’s Windows 11 association paragraph also prints .qxf, despite the surrounding QFX instructions. Do not turn that inconsistency into a file-renaming or association-repair instruction. Ask support to confirm the applicable product/version route when it does not match the interface.
A zero-byte or incomplete original bank download needs the issuing institution’s investigation; a persistent product error needs Quicken support with the recorded stage and original-file context. This preserves a useful boundary between source-format preparation and product/protocol support without claiming a successful import or live institution eligibility. Quicken sources checked October 17, 2026.
Save an import copy and review the result
-
Keep three artifacts: the original statement or native download, the reviewed transaction data, and the target import copy. Record which account, dates, currency and field mapping the copy represents. Back up the accounting file where applicable; Intuit explicitly recommends this before Desktop downloads.
-
Use the actual importer’s preview or review stage. Confirm a known receipt and payment land with the right date and direction, then check how it handles already recorded transactions. Stop on a reversed amount, unexpected account or changed identifier. Successful file acceptance is not proof of correct bookkeeping.
-
CSV saves the selected worksheet’s text and can omit workbook features. Keep an XLSX copy separately and inspect the saved CSV.
Import-check worksheet: record source, target, date/sign mapping and unresolved rows. This is a manual aid, not an import template or validator.
PDF parsing and OCR run locally; account, subscription, update and periodic Pro verification functions need a network. Free evaluation is a cumulative ten pages; Pro is USD 10/month or USD 60/year. Export CSV, and use Excel’s Save As if you need an XLSX workbook. There is no desktop batch queue or automatic accounting import.
Need transaction rows from a PDF? Download LocalExtract.
Official sources checked October 12, 2026.
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy