Loading converter...
Loading converter...
CSV (Comma-Separated Values) is the universal plain-text format for tabular data. Every bank, credit card company, and financial institution offers CSV exports — making it the most common starting point for importing transactions into QuickBooks®.
CSV stands for Comma-Separated Values. It is one of the oldest and simplest file formats in computing — a plain text file where each line represents a row of data and values within each row are separated by commas. No special software is needed to create or read CSV files; any text editor or spreadsheet program can handle them.
For QuickBooks® users, CSV files are typically encountered when downloading transaction history from a bank's online portal. Banks offer CSV as a download option because it is universally compatible — unlike proprietary formats such as QBO or QFX, CSV can be opened in Excel, Google Sheets, or any data processing tool without specialized software.
The challenge with CSV is that there is no formal standard governing how banks format their exports. While RFC 4180 provides guidelines for CSV formatting, banks are not required to follow it. This means every bank produces slightly different CSV files — different column orders, date formats, number formats, and header conventions. This inconsistency is the primary reason why importing CSV files directly into accounting software can be frustrating.
Converting CSV to QBO format with PrimeConnect solves this problem by normalizing your bank's specific CSV layout into the standardized OFX/QBO format that QuickBooks® expects. The converter handles date format detection, column mapping, and encoding issues automatically — turning a potentially error-prone manual process into a one-click operation.
Supported by every operating system, programming language, and spreadsheet application. No proprietary software required — CSV works everywhere.
Unlike binary or XML formats, CSV files can be opened in any text editor and read directly. This makes them easy to inspect, edit, and troubleshoot.
Every major bank worldwide offers CSV as a transaction export option. It is often the only format available for credit card statements and smaller financial institutions.
Opens natively in Microsoft Excel, Google Sheets, LibreOffice Calc, and Apple Numbers. Data can be sorted, filtered, and manipulated before conversion.
While every bank formats their CSV differently, most bank exports include at minimum a date, description, and amount. Here is an example of a typical US bank CSV export:
Date,Description,Amount,Balance 02/03/2026,"DEBIT CARD PURCHASE - OFFICE SUPPLY STORE",-45.99,8188.57 02/05/2026,"ACH PAYMENT - ELECTRIC UTILITY CO",-89.50,8099.07 02/07/2026,"CHECK #1042",-250.00,7849.07 02/10/2026,"DIRECT DEPOSIT - PAYROLL",3200.00,11049.07 02/12/2026,"ONLINE TRANSFER FROM SAVINGS",500.00,11549.07 02/14/2026,"POS PURCHASE - RESTAURANT",-32.75,11516.32 02/15/2026,"WIRE TRANSFER RECEIVED",1500.00,13016.32
Note: Some banks use separate Debit and Credit columns instead of a single Amount column. Others include additional fields like transaction type, check number, or category. The header row names also vary by bank (e.g., "Date" vs "Transaction Date" vs "Posted Date").
Because CSV has no enforced standard, bank exports frequently cause problems when imported into accounting software. Here are the most common issues QuickBooks® users encounter:
US banks typically use MM/DD/YYYY, but European banks use DD/MM/YYYY and some international banks use YYYY-MM-DD. A date like "03/04/2026" is ambiguous — is it March 4 or April 3? Incorrect date parsing leads to transactions appearing on the wrong dates.
Most modern files use UTF-8 encoding, but some banks export in Windows-1252 (ANSI) or ISO-8859-1. When encoding is wrong, special characters (accented names, currency symbols) appear as garbled text or cause import failures.
Despite the name "Comma-Separated Values," many European banks use semicolons (;) as delimiters because commas are used as decimal separators in those locales. Some banks use tabs. Opening a semicolon-delimited file as comma-delimited puts everything into one column.
Some banks include a header row with column names, others don't. Some include multiple header lines with account information before the data starts. Some even include summary rows at the bottom. These extra rows confuse automated parsers.
US banks use periods for decimals ($1,234.56) while European banks use commas (1.234,56). Some banks include currency symbols in the amount field. Others use parentheses for negative numbers instead of a minus sign.
Instead of a single signed amount column, many banks provide separate "Debit" and "Credit" columns. One column will be empty while the other has a value. This requires special handling during conversion.
Getting a clean CSV export from your bank makes the conversion process much smoother. Here are practical tips for the best results:
QBO (Web Connect) is a structured XML format with built-in duplicate detection, account metadata, and standardized field definitions. CSV has none of these — converting CSV to QBO adds the structure QuickBooks® needs for clean imports.
OFX is the open standard behind QBO, supported by thousands of financial applications. CSV is more universally available from banks, but lacks the metadata and validation that OFX provides.
Excel files preserve formatting, formulas, and data types that CSV loses. However, bank CSV exports are more portable and lighter than Excel files, and most converters accept CSV rather than XLSX.
Use our free CSV to QBO converter to turn your bank CSV into QuickBooks® format.
Start Converting Free