# Fix Wrong or Shifted Transaction Dates After Importing into QuickBooks _Canonical: https://qbomaker.com/blog/fix-wrong-dates-quickbooks-import.html_ When dates land on the wrong day after a QuickBooks import, the cause is almost always a format mismatch: your file uses day/month order (or a two-digit year, or no year) and QuickBooks reads it as month/day. Fix the date column in the source file before you convert, and every transaction posts on the correct date. ## What a shifted date actually means A shifted date is not a QuickBooks bug. It is a reading mistake. QuickBooks US expects dates in month/day/year order. If your bank exports day/month/year (common in the UK, Canada, Australia, and most of Europe), QuickBooks still reads the first number as the month.Look at 03/05/2026. To a UK bank that is the 3rd of May. To QuickBooks US that is March 5th. The number imports without an error, so nothing warns you. The transaction simply lands two months early.The tell is that some dates fail and some do not. 15/04/2026 (15 April) cannot be read as month 15, so QuickBooks rejects it or flips it. But 04/06/2026 reads cleanly as either order, so it imports silently on the wrong day. A column that is half rejected and half wrong is the classic sign of a day/month swap. ## US vs UK date order, side by side The two orders collide whenever the day is 12 or less, because both numbers are valid months. That is why the problem hides in roughly the first 12 days of every month.Source value: 06/07/2026UK / day-first reading: 6 July 2026QuickBooks US / month-first reading: July 6, 2026One file, one row, two different dates, no error message. The fix is to stop relying on either side to guess. Convert the column to an unambiguous format before import. YYYY-MM-DD (for example 2026-07-06) cannot be misread, because the year comes first and the order is fixed.If you map dates to MM/DD/YYYY for QuickBooks US instead, that works too. The point is that you decide the order, not the importer. ## The missing-year and two-digit-year problem Some bank exports drop the year entirely (06/07) or use two digits (06/07/26). Both cause posting errors.No year: QuickBooks fills in a default, often the current year, so December transactions from last year jump forward 12 months.Two-digit year: 26 can be read as 1926 or 2026 depending on the importer's cutoff. Old transactions can land a century off.Year boundary: a statement that crosses 31 December into 1 January is the worst case, because half the rows belong to one year and half to the next, and a missing year sends them all to one side.Always supply a full four-digit year in the source file. If your export only has month and day, add the correct year before converting, and watch the rows around January 1st. ## Why opening the CSV in Excel often makes it worse The instinct is to open the file in Excel and reformat the date column. Resist it. Excel reinterprets dates the moment the file opens, based on your computer's regional settings, and it does this silently.A UK column of 13/04/2026 may load fine, but 04/13/2026 gets treated as text while 04/12/2026 becomes a real date. Now half your column is text and half is a serial number.Leading zeros disappear, so 04/06/2026 can become 4/6/2026.Saving back to CSV writes whatever Excel guessed, which may be a different order than you started with.If you must use Excel, import the file through Data > From Text/CSV and set the date column type explicitly, rather than double-clicking the file. Better still, fix the order at conversion time so Excel never touches it. ## Fix the dates before you convert, not after Correcting dates after they post means deleting and re-entering transactions, or excluding and re-importing them. It is slow and error-prone. Fix the column once, in the source file, and the import is clean the first time.QBO Maker reads your bank's CSV or Excel export and lets you map the date column to the correct order before it builds the .QBO file. You tell it whether the source is day-first or month-first, and it writes proper, unambiguous dates into the output. Because a .QBO file carries fully specified dates internally, QuickBooks imports them exactly as written, with no second guess about US or UK order.Steps to a clean date import:Export the statement as CSV or Excel from your bank (do not re-save it through Excel first).Drop it into the converter at the QBO Maker tool.Confirm the date column and its order (day-first or month-first), and check the preview around any month/year boundary.Download the .QBO file and import it into QuickBooks.Convert your file now and check the date preview before you download. ## A quick way to spot-check before importing Before you commit an import, find a transaction you remember and compare it against the source. Pick one with a day above 12 (say the 15th or 28th), because that is the row that exposes a swap. If a payment you know happened on 15 April shows up as something else, the order is wrong and you should re-map it.Also scan the converter's preview for any date that sits in the wrong month or year. One bad row usually means the whole column is mapped the wrong way, so fix the mapping rather than editing single transactions. **Why did all my transactions import on the wrong date in QuickBooks?** Your file almost certainly uses day/month/year order while QuickBooks read it as month/day/year. The numbers import without an error, so the transactions just land on the wrong day. Re-map the date column to the correct order and convert again. **Does QuickBooks Online support DD/MM/YYYY for imports?** QuickBooks US expects month/day/year for CSV imports and does not reliably auto-detect day-first dates. The safest approach is to convert dates to an unambiguous format (such as YYYY-MM-DD) or build a .QBO file with fully specified dates, so the order can never be misread. **Why do only some of my dates fail and others import wrong?** Dates where the day is 13 or higher cannot be read as a month, so they fail or get flagged. Dates where the day is 12 or less are valid in both orders, so they import silently on the wrong day. A column that is part rejected and part wrong is the signature of a day/month swap. **My export has no year. What happens on import?** QuickBooks fills in a default year, usually the current one, which sends older transactions forward. Add a full four-digit year to the source data before converting, and pay attention to any statement that crosses 31 December into 1 January. **Can I just fix the dates in QuickBooks after importing?** You can, but it means editing or deleting and re-entering each transaction, which is slow and easy to get wrong. It is faster and cleaner to fix the date column in the source file and re-import. Fix it once at conversion time and the import is correct from the start. --- Convert free at https://qbomaker.com/#tool, runs entirely in your browser.