# Imported Transactions in a Closed Period in QuickBooks

- Author: SimpleBankConvert (https://www.simplebankconvert.com)
- Published: 2025-12-20
- Updated: 2025-12-20
- Category: Undoing and fixing imports
- Canonical: https://www.simplebankconvert.com/blog/imported-transactions-in-a-closed-period-in-quickbooks

> What to do when imported transactions land in a closed period in QuickBooks: why the closing date warns you and how to move or remove them safely.
Imported transactions in a closed period in QuickBooks are lines dated on or before the books' closing date. QuickBooks warns, or asks for a password, before anyone accepts or changes them. Work out whether each line truly belongs in that period. If it does not, remove it or redate it. If it does, involve whoever closed the books.

## What does a closed period mean for imported transactions in QuickBooks?

A closed period is every date up to and including the closing date someone set for the company. Closing protects work that is finished, such as a reconciled year or a filed return, from quiet changes. Imported bank lines dated in that span bump into the protection the moment anyone tries to accept them.

[Intuit's guide to closing your books in QuickBooks Online](https://quickbooks.intuit.com/learn-support/en-us/help-article/close-books/close-books-quickbooks-online/L59LelyPM_US_en_US) sets this up under Settings, Account and settings, the Advanced tab, then the Accounting section. You switch on Close the books, enter a closing date and pick a security option. The guide says to review and reconcile accounts before locking them, which tells you what a closed period usually means: someone already checked those months.

QuickBooks Desktop has the same idea, with a closing date and an optional password in its company accounting preferences. The steps differ, but the reasoning in this post applies to both.

Lines waiting on the review tab are not yet in the books. A bank line dated last December can sit there safely. The closed period only matters once a line is added, matched or edited, because only then does it change a locked month.

## Why the closing date warning appears when an imported line is accepted

The warning appears because accepting the line would add to, or change, a period QuickBooks was told to protect. Adding a bank line creates a new record dated on that line's date. If the date is on or before the closing date, the record lands inside the closed span, and QuickBooks stops to check you meant it.

Intuit's guide describes two security options. One lets people make the change after viewing a warning. The other also asks for a password, which only the person who closed the books should know. The warning version is easy to click through without reading, and that is how most closed-period imports end up in the books.

Treat the warning as a question, not an obstacle. It is asking whether a bank movement from a finished month should change that month's figures. Sometimes the honest answer is yes. More often, the date is wrong or the line should never have been imported.

## Why do imported transactions land before the closing date?

Old-dated lines come into an import for a handful of reasons, and the fix depends on which one applies. A file can reach back further than intended, carry the wrong year, belong to another company, or hold real transactions someone forgot to record before closing.

The common causes:

- **A download range that started too early.** The bank export covered the whole quarter, while the books were closed through last month.
- **A wrong year.** Dates printed without a year, such as "12/28", were read as the current year or the previous one.
- **The wrong company.** A client's file went into your company, where its dates mean nothing. The post on [importing into the wrong QuickBooks company](/blog/imported-into-the-wrong-quickbooks-company) covers that clean-up.
- **A genuine late find.** A bank fee or a deposit from the closed month never made it into the books.

### Worked example: a March upload with February lines

The details are an example. The books are closed through 28 February. A March CSV is uploaded, and the review tab shows 46 lines. Five of them are dated in February, from the 25th to the 28th, because the bank export started a week early.

| Line (example) | Date | Amount | Already in February's books? | Action |
| --- | --- | ---: | --- | --- |
| Rent | 25 Feb | -1,800.00 | Yes, matched in February | Exclude |
| Card payout | 26 Feb | 640.20 | Yes | Exclude |
| Supplier ACH | 27 Feb | -315.00 | Yes | Exclude |
| Bank fee | 28 Feb | -15.00 | No | Ask before adding |
| Customer deposit | 28 Feb | 1,120.00 | Yes | Exclude |

Four of the five lines are copies of entries made before closing, so they are excluded without ever touching the closed period. Only the bank fee is genuinely missing. Whether it goes into February or gets recorded another way is a decision for whoever closed the books.

## Removing closed-period imports that should not be there

If a closed-period line is a copy, out of range or from the wrong company, remove it without changing the closed months. While it is still on the review tab, exclude it. Excluding does not add a record, so no closing date warning is involved and the locked period stays as it was.

Lines already accepted take more care. Undoing an added line removes the record it created. Undoing a matched line disconnects it from an entry that was in the books before. In both cases the closed month changes, so you will see the warning again. That second warning is legitimate: the first acceptance changed the period, and the undo puts it back.

For an import that went badly wrong across many months, removing lines one by one may not be practical. The post on [deleting all bank transactions in QuickBooks Online](/blog/delete-all-bank-transactions-in-quickbooks-online) explains what a bulk clear-out can and cannot do. Agree on it with your accountant first if any of those months are closed.

After you finish, compare the balance of the account on the closing date with the bank statement for that date. It should equal the figure that was agreed when the books were closed. If it differs, a line inside the closed span is still added or a needed one was removed.

## Moving a closed-period import to the right date or account

When the line is a real transaction that simply landed in the wrong place, move it. A line with the wrong year should be redated to the true date. A line accepted into the wrong bank account should move to the account it belongs to. Both changes touch the closed span if the old date or account is inside it.

[Intuit's article on unmatching and moving downloaded transactions](https://quickbooks.intuit.com/learn-support/en-us/help-article/bank-registers/unmatch-downloaded-bank-transactions-move-another/L71oaBb86_US_en_US) shows how to move a line. You open the Posted tab, select the blue link in the Added or Matched column, choose a new account in the Account dropdown and select Save and close. For a wrong date, open the record and correct the date the same way.

Fix the cause before you import more. If the dates came out wrong because the source file printed them without a year, the next file will do the same. Converted files are prone to this too. An OFX file writes dates as year, month and day in one fixed order, while QIF files appear with several date styles, so a conversion between them is a point where years can slip. The guide to [OFX to QIF conversion](/blog/ofx-to-qif) covers that route. SimpleBankConvert is being built to put every date in one consistent format, so a statement line does not drift into the wrong month. It has not opened yet; [the get started page](/get-started) lists you for an invite.

## Closed-period imports in filed returns: when not to change them

If the closed period sits behind a filed tax return, an issued financial statement or a finished audit, do not change it yourself, even when the line is a real transaction. The figures in that period have been reported to someone else. Changing them makes your books disagree with what was filed.

The usual alternative is to record a missed item in the current open period, with a note explaining it. Whether that is right depends on the size of the item and the rules that apply to you, which is why this is a question for your accountant, not a click-through of the warning.

The same caution applies to reconciled lines. Intuit's unmatching article says that if you already reconciled a transaction, you should ask your accountant before changing it. A closed period is almost always a reconciled one, so assume every line in it is reconciled until you check.

## The Exceptions to Closing Date report as a record of the fix

QuickBooks Online keeps a report of changes made inside a closed period, and it is the best way to show what your fix did. [Intuit's article on changing the closing date and password](https://quickbooks.intuit.com/learn-support/en-us/help-articles/change-the-closing-date-password/00/239369) points to the Exceptions to Closing Date report for reviewing changes made after closing.

Run it after you finish. It should list every line you added, undid, redated or moved within the closed span. Compare that list with your own notes from the worked example step. Anything on the report you do not recognise is a change someone else made, perhaps by clicking through the warning on an earlier import.

Share the report with whoever closed the books. It turns an awkward conversation into a short check: these are the lines that changed, this is why, and the closing balance still matches the bank statement. The same article notes that only admins can change the closing date or password, so if the security settings need tightening afterwards, an admin has to do it.