QuickBooks Desktop reports no new transactions in a Web Connect file when every transaction ID in it is one the company file has already recorded. The other causes are a download covering dates you have already imported and a bank export that holds no transactions at all. Open the file in a text editor to see which one you have.
What "account up to date" means for a Web Connect file
"Account up to date" is QuickBooks Desktop telling you it read the Web Connect file and found nothing it hasn't already taken in. Intuit's article on the message "Nothing imported. Account up to date" explains the check: every account and transaction in a Web Connect file carries a unique identifier, and QuickBooks remembers the ones it has seen.
That article is written for QuickBooks for Mac, and Intuit's Windows Desktop download guide, cited further down, states the same rule.
The message is not a failure in the usual sense. The file opened, QuickBooks understood it, and the import ran. It simply had nothing to add. Intuit says QuickBooks "will not allow you to import transactions with the same ID more than once," and that rule exists to stop duplicate entries.
So the useful question is not "why is it broken" but "why does QuickBooks think it has these already." Three answers cover almost every case:
- The transactions really are in the company file, perhaps from an earlier file or a bank feed download.
- They were in the company file once, then deleted, and QuickBooks still remembers their IDs.
- The file has no transactions in it, so there was nothing new to find.
The sections below take each one in turn, starting with the IDs.
Transaction IDs QuickBooks Desktop has already recorded
A transaction ID in a Web Connect file is a code the bank assigns to each transaction, written in a <FITID> tag. The OFX 2.2 specification describes it as the value a program "uses to detect whether the server has previously downloaded the transaction." QuickBooks keeps those IDs per account.
That is why a fresh download can still count as old. If you download September again after importing September last week, the bank sends the same transactions with the same IDs. QuickBooks compares, finds every one, and adds nothing. The download is new to you, but the transactions are not new to QuickBooks.
The OFX specification says each ID must be unique within the account, and that the same ID may turn up at a different bank. The account matters too. Intuit's article notes that the account in a Web Connect file carries its own identifier, which is why the account ID edit described further down changes what QuickBooks treats as new.
A worked example
Here is an example of how a partial overlap plays out. The IDs, dates and amounts are made up for illustration. The last import into this checking account ran to September 30. The new file covers September 28 to October 3.
| Date | Description | Amount | ID in file | Already recorded? |
|---|---|---|---|---|
| Sep 28 | Rent | -1,850.00 | 20260928A1 | Yes |
| Sep 29 | Card deposit | 412.60 | 20260929B4 | Yes |
| Sep 30 | Phone bill | -64.99 | 20260930C2 | Yes |
| Sep 30 | Bank fee | -12.00 | 20260930C7 | Yes |
| Oct 1 | Supplier payment | -230.00 | 20261001D3 | No |
| Oct 3 | Client payment | 980.00 | 20261003E9 | No |
QuickBooks would bring in two transactions here, not six, and that is correct. The message that nothing is new only appears when every row is a "Yes." If you expected October lines and got the message, the file probably stops before October.
Is the Web Connect file's date range the real problem?
A wrong date range is the most common reason a Web Connect file holds only old transactions. Banks usually let you choose the period on their download screen, and many remember the last range you used. A download that quietly reuses last month's dates produces a file of transactions QuickBooks already has.
Check the range before you blame anything else. Open the .qbo file in a text editor such as Notepad or TextEdit and find the <DTSTART> and <DTEND> tags inside <BANKTRANLIST>. They hold the start and end of the period as year, month and day run together. A file with <DTSTART>20260901 and <DTEND>20260930 covers September only.
Then look at the dates on the transactions themselves, in the <DTPOSTED> tags. Two things can surprise you:
- Posted dates, not purchase dates. Banks list transactions by the date they posted. A card payment made on the 30th can post on the 2nd and fall outside a range that ends on the 30th.
- Pending items left out. Transactions still pending at the bank are often not in the file at all. They appear in a later download once they post.
To fix the range, go back to the bank's download screen and set the start to the day after the last transaction already in QuickBooks. Intuit's article recommends downloading only the dates you need. A short, exact range is easier to check than a long one that mostly repeats.
If you also keep a set of books in Xero, its statement import has its own range trap. The guide to fixing a Xero CSV date error covers how Xero reads the day and month.
An empty Web Connect export from the bank
An empty Web Connect export is a file that contains the account details and balance but no transaction blocks. QuickBooks reads it, finds nothing, and gives the same up-to-date message. The bank created a valid file. It just had no activity to put in it for the period you chose.
The OFX specification allows this. When a bank finds no transactions for a request, its response may or may not include a transaction list, and if it does, the list has no <STMTTRN> entries. In a text editor, an empty file shows the <BANKACCTFROM> and <LEDGERBAL> blocks and nothing between them that starts with <STMTTRN>.
Common reasons for an empty export:
- The period you chose is in the future, or ends before the account's first transaction.
- The account really had no posted activity in that window. A savings account can go weeks without a line.
- You downloaded from the wrong account at the bank, such as a closed account or a different card.
- The bank's download only reaches back a limited time, and older dates come back empty.
Search the file for <STMTTRN>. Zero matches means the export is empty and no change in QuickBooks will help. Download again with the right account and dates.
Xero users see the same thing from a different angle. The guide to a Xero bank statement import that failed covers what Xero does with a file it finds nothing usable in.
Can deleted Web Connect transactions come back?
Deleted Web Connect transactions can come back, but not by downloading them again. Deleting a downloaded line in QuickBooks Desktop does not make QuickBooks forget its ID. Intuit's guide to downloading bank feed transactions in QuickBooks Desktop says you can't download transactions into one company file twice, and that deleting them prevents downloading them again.
This catches people out after a clean-up. You delete a batch you think is wrong, download the file again to start over, and QuickBooks reports that nothing is new. It is still holding the IDs of the lines you removed.
Intuit's "nothing imported" article gives three ways back, in this order:
- Restore a backup made before the import, then import the file again. This is the cleanest route when the backup is recent and nothing else has changed since.
- Enter the transactions by hand when only a few are missing. For three or four lines, typing them is faster than any workaround.
- Edit the account ID in the file. Turn off online downloads for the account, download a new file covering only the dates you need, open it in a text editor and delete the last digit of the account number in
<ACCTID>. Then import it.
The Desktop download guide adds one more: ask your bank to reopen the transactions on its side, so they can be downloaded again.
When editing the Web Connect account ID is the wrong fix
The account ID edit is a workaround, and Intuit's article says you have to repeat it every time. It makes QuickBooks treat the file as a different account. That gets the transactions in, but it also removes the one check that stops you importing the same lines twice.
Skip the edit in these situations:
- When some of the lines are already in the register. The edited file brings in everything it holds, old and new alike. Cut the date range to just the missing days first, or you will spend longer removing duplicates than you saved.
- When a backup is available. A restore puts the file back exactly as it was. The edit leaves you managing an account that QuickBooks sees under two identities.
- When the real cause is the date range or an empty export. Changing the account ID cannot add transactions that aren't in the file.
- When only a handful of lines are missing. Type them in instead.
If what you're missing is a gap of days rather than lines you deleted, the approach is different again. The guide to importing missing bank transactions into QuickBooks Online shows how to find the exact gap and cut a file to cover it. The same habit of measuring the gap first works in Desktop.
When the bank no longer offers downloads for the months you need, a PDF statement may be all that's left. SimpleBankConvert is being built to turn statements like that into a QBO file for Desktop. It hasn't opened yet; the get started page keeps you posted.