When imported transactions have the wrong year in QuickBooks, the file almost always carried a bad year, or a date format QuickBooks read differently from the bank. The fix is to remove the whole batch, correct the year in the CSV or QBO file, and import it again, rather than retyping dates one line at a time.
Why do imported transactions get the wrong year?
A wrong year usually starts in the file, not in QuickBooks. Many PDF statements print dates as month and day only, so whoever built the file had to supply the year. Two-digit years and spreadsheet date conversion cause the rest. QuickBooks then records exactly what the file says.
The three common causes are:
- A year guessed from the wrong end of the period. A statement running from December 15 to January 14 prints "01/03" with no year. A converter that stamps every row with the year the period started files January lines twelve months early. The post on PDF statement dates that lack a year shows that slip row by row.
- Two-digit years. A cell reading "01/05/26" can be read in more than one way when the format is not stated.
- Spreadsheet conversion. Opening a CSV in a spreadsheet and saving it again can rewrite dates in a different order or year style.
In QuickBooks Online, the CSV upload asks you to state the date format your file uses. Intuit's page on manually uploading transactions into QuickBooks Online also asks you to keep every date in the file in one format. A mismatch between the format you pick and the format in the file is a quick way to get dates that are off.
Spotting a wrong-year batch in the QuickBooks register
A wrong-year batch shows up as a register that is suddenly too short for the month you imported and has an unexpected cluster a year away. Open the account register, filter to the month you expected, and count the lines. Then widen the filter by a year in each direction and look for the missing rows.
Two checks confirm that the problem is the year and not the account:
- The missing lines appear in the same account, twelve months earlier or later, with the right day and month.
- The amounts and payees match your statement exactly.
If the lines are nowhere in the account at all, the import may have gone into a different account or company, which is a separate fix.
Removing the wrong-year transactions from QuickBooks Online or Desktop
Take the whole batch out before importing a corrected file. In QuickBooks Online, lines still on For review can be excluded and then deleted from the Excluded tab. Lines already added have to be undone from the Categorized tab or deleted from the register. In Desktop, the cleanup runs through the Bank Feeds Center and the register.
QuickBooks Desktop has a rule worth knowing before you delete. Intuit's page on downloading bank feed transactions in QuickBooks Desktop says you can't download transactions into the same company file more than once, and that deleted downloaded transactions cannot be downloaded again. A corrected Web Connect file that reuses the same transaction IDs may therefore be skipped.
Two posts cover the Desktop side in more depth. Deleting downloaded transactions in QuickBooks Desktop handles lines still waiting in the Bank Feeds Center. Undoing a Web Connect import in QuickBooks Desktop handles lines that were already accepted into the register.
Correcting the year in the bank file before importing again
Fix the year in the file, then check every row before the next import. Every date should fall inside the statement period printed on the PDF. Write all dates with four-digit years in one format, and state that format on the QuickBooks Online mapping screen.
A worked example
This example uses made-up rows from a statement covering December 15, 2025 to January 14, 2026. The first file stamped every row with 2025.
| Row as imported | Correct date | Why |
|---|---|---|
| 12/28/2025, Flour Supply Co, -412.80 | 12/28/2025 | December falls in the period's first year |
| 01/03/2025, Card deposit, 1,906.00 | 01/03/2026 | January falls in the period's second year |
| 01/09/2025, Utility Co, -138.25 | 01/09/2026 | Same reason |
The test is simple. Any date before December 15, 2025 or after January 14, 2026 is wrong. Here the two January rows fail, so they are corrected to 2026. After fixing, the dates run in order from the start of the period to the end.
For a Web Connect file, editing dates by hand is fiddly, because each line also carries an ID that Desktop remembers. Rebuilding the file from the statement is usually safer than patching it. The same period test applies to any accounting program, so run it before you follow the guide to importing a bank statement into Odoo as well.
Can you edit the year one transaction at a time instead?
Editing the year on each transaction is fine for two or three lines that were already reconciled or matched, where removing them would undo other work. For a full batch it is a trap. It is slow, easy to miss one row, and leaves bank detail tied to dates that no longer match the bank's record.
A sensible line to draw:
- One to three lines, already matched or reconciled: open each one and change its date.
- A full statement or more: remove the batch, fix the file and import it again.
- Lines in a closed period: talk to whoever closed the books before you change anything there.
A file with the right year from the start saves the cleanup. SimpleBankConvert is being built to give every row of a PDF statement one consistent date format. Whatever made the file, check the January rows of a December statement against the PDF before you upload.