QuickBooks CSV Import Date Format: How to Fix Date Errors

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 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. Single-digit exports cause the same trouble: a TD Bank CSV written in M/D/YYYY is one of the exports QuickBooks most often misreads on a raw upload.

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.

How do I change the date format in Excel without breaking it?

If you do need Excel, force the format into text so the locale cannot touch it again. In a helper column, enter =TEXT(A2,"MM/DD/YYYY") (pointing at your date cell), fill it down, then copy the helper column and paste it back over the original dates using Paste Special, Values. Because TEXT() produces a literal string rather than an Excel date, saving the CSV will not reshuffle day and month behind your back. Two checks before you save: scan a date past the 12th of a month (like 03/25/2026) to confirm month and day did not swap, and make sure every row got the formula, since a half-converted column is exactly the mixed-format case QuickBooks rejects.

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. The QuickBooks Online vs Desktop CSV import comparison covers the rest of the differences. Converting to .qbo gives both the same clean, unambiguous dates and skips the format selector entirely.

Why does the QuickBooks help article say to use DD/MM/YYYY?

Because the article most search engines surface is Intuit's global version, not the US one. Intuit publishes the same CSV formatting page for several regions, and the "rest of world" edition recommends DD/MM/YYYY because that is what most of its readers need. If your company file is set to the United States, following that advice puts every date in backwards. Check the country on the article you are reading before you trust the example, and check Account and Settings, then Advanced, then Company, for your own region setting.

This is the single most common reason a careful bookkeeper ends up with a file full of transposed dates. The instructions were followed exactly. They were just the instructions for a different country.

What happens when Excel opens a CSV with two-digit years?

Excel silently expands them using a fixed cutoff. Two-digit years 00 through 29 become 2000 through 2029, and 30 through 99 become 1930 through 1999. So a bank export written as 01/04/30 becomes January 4, 1930, not 2030. Microsoft documents this as the default behavior, and the cutoff is a Windows regional setting rather than anything QuickBooks controls.

For bank statements the practical effect is small today, because almost every date you import falls inside the 2000 to 2029 window. It stops being small in 2030. Any workflow that leans on two-digit years and a spreadsheet round trip has a dated expiry on it, which is one more argument for four-digit years in every file you build.

Why did my dates shift by exactly four years?

You almost certainly moved the file between the two Excel date systems. Excel stores dates as serial numbers counted from a base date, and there are two bases: the 1900 system, which is the default on Excel for Windows, and the 1904 system, which is the default on Excel for Mac. Open a workbook built under one system in the other and every date lands four years and one day away from where it should be.

A four-year shift across an entire column is the signature. If you see it, do not fix the dates by hand. Go back to the original CSV your bank produced, and either edit it in a plain text editor or feed it to a converter, so the file never passes through a second spreadsheet with a different base date.

What date format does a .qbo file use?

A .qbo file is an OFX document, and OFX dates are unambiguous by design. The transaction date sits in a DTPOSTED element written as YYYYMMDD or YYYYMMDDHHMMSS, so April 9, 2026 is 20260409. There is no separator to misread and no day and month order to guess, which is why the same file imports identically on a US, UK or Australian company file.

The statement wrapper carries dates in the same shape: DTSTART and DTEND bound the period, and DTASOF stamps the closing balance. A timezone offset can be appended in brackets, as in 20260409143000.000[-5:EST]. If you ever build .qbo files yourself, stick to plain YYYYMMDD. Slashes, hyphens, ISO strings with a T in the middle, and Unix timestamps all break the import, and the error QuickBooks returns rarely says the word date.

Can I import a CSV into QuickBooks Desktop and fix the dates there?

No, and this trips up a lot of people. QuickBooks Desktop cannot import a bank or credit card CSV in any version. The Import Excel and CSV toolkit handles four list types only: customers, vendors, items and the chart of accounts. There is no bank transaction CSV path to fix dates in, so on Desktop the date format question resolves itself: you need a .qbo, and the converter that builds it decides the dates. Card exports are the ones that go wrong most often, because issuers vary the date style and the sign convention together, which we untangle in the guide to importing credit card transactions into QuickBooks.

QuickBooks Online is the product with a bank CSV upload, and that is where the date format selector lives. If you are reading date format instructions and running Desktop, you are reading instructions for the other product. The CSV to QuickBooks Desktop route covers what does work.

How do I fix dates that already imported into the wrong month?

Undo the batch rather than editing rows. In QuickBooks Online, open Bank transactions, which sits under All apps, then Accounting on current accounts and under Transactions on older ones, select the account, go to the For review tab, and use the history or the uploaded file list to undo the import in full. Editing a few hundred dates by hand invites a second, quieter error, and it leaves the original bad file in place to be re-imported later by someone else.

Two cautions before you re-import. First, anything you already categorized and accepted has moved into the register, so it has to be found and removed there, not in the review queue. Second, a CSV carries no unique transaction identifier, so re-uploading a corrected file after a partial cleanup will duplicate every row that survived. Delete the prior import completely, then upload once. A .qbo avoids the whole problem because each transaction carries a unique ID that QuickBooks matches against what it has already seen.

Do date errors look different in QuickBooks Online than in a spreadsheet?

Yes, and that asymmetry is what makes them expensive. A spreadsheet shows you a wrong date immediately, because the cell right-aligns as a number or shows a value you did not expect. QuickBooks shows you nothing: the row imports, the amount is right, the description is right, and only the month is wrong. Nobody catches it until the bank reconciliation for that month refuses to clear.

The cheap check takes ten seconds. Before you import, sort the date column and look at the first and last value. If your statement covers March and the extremes read January 3 and December 3, the day and month are swapped. Then look for any date past the twelfth of a month, which is the only kind of date that cannot be silently reversed, and confirm it reads the way you expect.

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.

Related guides: The surest way to avoid date errors is to skip manual mapping entirely: convert the file with the CSV to QBO converter, which normalizes every date into the format QuickBooks expects. See the exact column and date rules in the QuickBooks CSV import template, follow the full how to convert CSV to QBO walkthrough, and if the numbers live in a workbook use the Excel to QBO converter. Importing a big backfile? Check the QuickBooks CSV import limit before you start, so the 1,000-row cap does not surprise you mid-upload.

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.