QuickBooks CSV Import Date Format: How to Fix Date Errors
No account needed for your first conversions. We never store your bank login.
For US QuickBooks accounts, the CSV import date format is MM/DD/YYYY. If your file uses DD/MM/YYYY, YYYY-MM-DD, text month names, or backslashes instead of slashes, QuickBooks either rejects the file or, worse, reads the dates wrong without telling you. The fix is to put every date in your account's expected format before you import, or convert the CSV to a .qbo file that carries dates QuickBooks reads the same way every time.
The dangerous case is not the obvious error. A date like 01/04/2026 means January 4 to a US QuickBooks account and April 1 to a UK or Australian one. If your bank exported it in the other order, the import can succeed while every transaction lands in the wrong month, and you will not notice until reconciliation. That is why the date format matters even when QuickBooks does not throw an error.
| What's in your CSV | How QuickBooks reads it | Fix |
|---|---|---|
| DD/MM/YYYY (04/01/2026) | Misread as MM/DD, so April 1 becomes January 4 | Convert to MM/DD/YYYY for US accounts |
| YYYY-MM-DD (2026-01-04) | Often not recognized as a date | Reformat to MM/DD/YYYY |
| Backslash separators (01\04\2026) | Not recognized as a date | Replace backslashes with forward slashes |
| Text month names (Jan 4, 2026) | Not recognized | Convert to numeric MM/DD/YYYY |
| Mixed formats in one column | Some rows fail, some import to the wrong month | Normalize the whole column to one format |
| File edited in Excel | Leading zeros stripped, dates shifted by locale | Do not edit the CSV in Excel; convert it instead |
What date format does QuickBooks use for CSV import?
US QuickBooks accounts expect MM/DD/YYYY. The exact format follows your company's region setting, so a UK or Australian account expects DD/MM/YYYY. Check Account and Settings, then Advanced, for the region before you import, and match every date in the CSV to that format with forward slashes and a four-digit year.
Why is QuickBooks reading my CSV dates wrong?
Because the day and month are ambiguous. A date like 03/07/2026 is March 7 in US format and July 3 elsewhere, and QuickBooks applies your account's region rule regardless of what your bank intended. If the bank exported in the opposite order, every transaction shifts to the wrong month even though the import looks like it worked.
How do I fix the date format in a CSV for QuickBooks?
Put every date into your account's expected format, usually MM/DD/YYYY for US QuickBooks, using forward slashes and four-digit years. Avoid editing the file in Excel, which silently reformats dates by your system locale. A converter that normalizes dates as it builds the import file is the safest fix and removes the guesswork.
Why does QuickBooks say the date is invalid?
QuickBooks flags a date as invalid when it cannot match the cell to a real calendar date in the expected format. Common triggers are text month names, two-digit years, backslash separators, a day and month swapped past the twelfth, or blank and footer rows mixed into the data. Clean those cells and the row imports.
Should I open my bank CSV in Excel to fix the dates?
No. Excel reinterprets dates by your computer's locale the moment you open the file, strips leading zeros, and can turn 01/02 into a serial number. You may fix one problem and create three. Edit the CSV in a plain text editor, or convert it with a tool that handles date formatting for you, so Excel never touches the raw file.
What date formats does QuickBooks accept in a CSV?
During a QuickBooks Online CSV upload you pick the date format from a list, so several orders work as long as you choose the one that matches your file: day-month-year, month-day-year, and year-month-day are all options. The catch is consistency. Every row must use the format you select, or the mismatched rows fail or import to the wrong month.
How to set the correct date format before importing
Start by confirming your QuickBooks region so you know the target format. Open the CSV in a plain text editor, not Excel, and check that every date uses the same order, forward slashes, and a four-digit year. Remove footer rows, running balances, and any blank lines the bank added. If a column mixes orders, fix the whole column to one format. Then either upload the cleaned CSV and select the matching date format, or convert the file to a .qbo so the dates are locked in.
How does converting to QBO fix the date problem?
A .qbo Web Connect file stores each date in a fixed machine format that QuickBooks reads the same way every time, so there is no day-month ambiguity to misread. When you convert a CSV to .qbo, the dates are normalized once and locked in, which removes the most common reason transactions land in the wrong month.
Does the date format differ between QuickBooks Online and Desktop?
Both follow your company's region setting, but the import paths differ. QuickBooks Online asks you to confirm the date format during a CSV upload, while QuickBooks Desktop imports a .qbo where the date format is already fixed. Converting to .qbo gives both the same clean, unambiguous dates and skips the format selector entirely.
The reliable way to avoid date problems is to stop hand-formatting CSVs and convert them into a file QuickBooks reads natively. The CSV to QuickBooks Online converter and the CSV to QuickBooks Desktop converter both normalize dates as they build the .qbo, and the Excel to QBO converter does the same straight from a spreadsheet. If a failed import already left bad dates behind, the Web Connect import error guide covers the cleanup, and you can compare the best CSV to QBO converters if you are choosing a tool.
If your transactions are stuck in a PDF statement rather than a CSV, the dates are even easier to garble during extraction. Convert the PDF bank statement to clean Excel or CSV first, or go straight from the PDF statement to a .qbo. And if you are also digitizing receipts and bills for the same set of books, extract receipt and invoice data to a spreadsheet with consistent dates before you import.