CSV vs Excel vs QBO: which statement export should I use?
Use Excel XLSX when you want a workbook for review, CSV when you need a flat transaction table, and QBO when you are preparing a QuickBooks-style handoff and can check the import details.
Which export fits the job?
If CSV fits your workflow, see how to convert a bank statement PDF to CSV for the current column order and review checklist.
| Format | Use it when | Check before handoff |
|---|---|---|
| Excel XLSX | You want transaction rows alongside summary and reconciliation worksheets. | Review the Summary, Reconciliation, and Rows sheets; confirm any warnings and source details. |
| CSV | You need a flat, portable table for a spreadsheet or another import workflow. | Check dates, separators, signs, debit/credit columns, descriptions, and the target system’s expected column mapping. |
| QBO | You are preparing a QuickBooks-style statement-file handoff. | Choose the correct date convention, inspect the import preview and account mapping, and verify each transaction before accepting it. |
CSV and XLSX keep review data in a spreadsheet-friendly form. QBO is a transaction statement file; it is not a connection to your bank and does not transfer data directly into an accounting account.
What is different about ExtractMint’s QBO file?
The current QBO output is generated as OFX SGML version 1.02. Its file contains BANKID 0000 and ACCTID 0000000000, generic bank and account identifiers. Review the target account mapping and import preview before accepting the file. This project has not verified an external QuickBooks import across account setups.
If the date order is ambiguous, ExtractMint pauses QBO until you choose DD/MM/YYYY or MM/DD/YYYY. The QBO export also has stricter text limits than CSV or Excel; if a row cannot be represented, use the error message to correct the row or choose a spreadsheet export.
CSV or QBO for a QuickBooks handoff?
Choose CSV when you need to inspect or correct a flat table and map its columns during upload. For ExtractMint's current three-column workflow, keep only Date, Description, and the signed Amount field in a copy of the CSV. Remove extra columns, including separate debit/credit fields and balances, before uploading. Map those three columns to the matching QuickBooks fields; do not map a balance as the transaction amount. Intuit's CSV troubleshooting guidance recommends removing unnecessary columns and checking date formatting.
Choose QBO when the recipient wants a statement-file handoff and can inspect the destination account and transaction preview. Resolve any ambiguous date order before export. QBO avoids preparing a three-column CSV, but the generic identifiers and unverified-import caveat above still apply; the file extension does not establish compatibility with your account setup. Use XLSX first if you still need its review worksheets, then prepare the chosen import file after checking the rows.
For CSV preparation, use the PDF-to-CSV column and review guide. If the destination is Xero, use the separate Xero import decision guide.
Uploading transaction files to QuickBooks Online
As checked October 29, 2026, Intuit's US manual-upload instructions list .csv, .txt, .qbo, and .ofx for transaction-list uploads, with up to 1,000 transaction lines per upload and a 350 KB file limit. Split larger files into smaller date ranges without overlapping transactions. Menu labels and available steps can change by account or region.
- In Bank transactions, select the account tile when available and choose Upload from file.
- Choose your prepared file, then confirm the destination bank or credit-card account in the account selector.
- For CSV, map
Date,Description, and signedAmountto their matching fields and choose the date format used in the file. Intuit also documents a four-column credit/debit format; the ExtractMint workflow here uses three columns. - Inspect the preview using the checks below, select only the intended transactions, and confirm when they are accurate. Then review, match or categorize, and reconcile the uploaded transactions in QuickBooks.
ExtractMint has not verified that its generated QBO file imports successfully in every QuickBooks account setup.
What should I check in the QuickBooks preview?
- Destination account: compare the source statement's account and currency with the selected bank or credit-card account. ExtractMint's generic QBO identifiers do not identify your real account. Check the destination explicitly before confirming.
- Dates: compare the earliest and latest transaction dates and several individual rows with the statement. If day and month appear swapped, stop and correct the date-format choice. For QBO, resolve ExtractMint's DD/MM/YYYY or MM/DD/YYYY prompt before exporting again; do not infer the order from one ambiguous date. See how to choose the statement date order.
- Amount direction: compare at least one known incoming transaction and one known outgoing transaction where present. Confirm that signed
Amountproduces the expected money-in and money-out direction. If direction is reversed, check the selected account type, source signs, and column mapping before accepting anything. Correct individual row errors at the source; only use a bulk reversal when every affected row has been checked and the entire selection is reversed. - Rows and duplicates: check descriptions, amounts, transaction count, and date range against the prepared file and statement. Look for entries already present through an earlier upload or bank feed. Select only the intended new transactions; do not accept a preview with unexplained missing or repeated rows.
If QuickBooks rejects the file or shows unexpected values, stop the import and use the linked Intuit instructions to check formatting and account restrictions. Recheck the corrected file's preview before confirming; a completed upload is not proof that extraction or bookkeeping is correct.
What about uploading a PDF or image directly to QuickBooks?
Intuit also documents a separate native PDF/image statement workflow, distinct from uploading an ExtractMint CSV or QBO export. It includes side-by-side review and editing before saving. Intuit says a statement flagged for review may be reviewed by its global experts. Check the current native-upload instructions and handling details before sending a statement to that service.
What about the other download options?
- DOCX or PDF: document-style summaries for reading or sharing, not substitutes for checking transaction rows.
- Review JSON: saves extracted rows and validation details so a conversion can be resumed later.
- Review-pack ZIP: combines review files and can include source PDFs if you enable that option. Treat it as a financial document.
- Combined XLSX: combines multiple converted files in a workbook when more than one result is loaded.
Review before you import or share
Check dates, descriptions, references, amounts, debit/credit direction, and running balances against the source. A balance match is a useful consistency check, but it does not prove that every transaction is present or correct. No bank-specific format has been independently validated against real statements.
Core statement conversion runs in your browser. See the privacy page for data-flow details and export handling.