Import Missing Bank Transactions into QuickBooks Online

To import missing bank transactions into QuickBooks Online, find the first and last date the feed skipped, take your bank's statement or download for those days, cut the file down to only those dates, and upload it to the same account. Keep one day of overlap on each side to confirm nothing doubles.

Finding the exact gap in missing bank transactions

The gap is the run of dates with no transactions in QuickBooks even though your bank shows activity. You find it by comparing the QuickBooks account register against the bank's statement, then writing down the first missing day and the last. Everything else in this process depends on those two dates being right.

Compare the register to the statement

Open the account register in QuickBooks and sort by date. Open the bank's statement or online history beside it. Walk down both lists until they stop agreeing. Three signals narrow it quickly:

• The balance. Pick any date and compare the bank's ending balance for that day with the QuickBooks balance. The last date where they agree sits just before the gap.
• A run of empty days. Several consecutive business days with no entries is a stronger clue than one quiet day.
• The first line after the gap. The next transaction that does appear in QuickBooks marks the gap's far edge.

Check where the transactions went first

Before you call anything missing, rule out the usual hiding places. Intuit's article on finding missing downloaded transactions says new downloads land in For review, transactions you mark personal or duplicate move to Excluded, and lines without an account go to the Uncategorized Income or Expense accounts. A line in any of those places is not missing and does not need importing.

Write the gap down

Record two dates and the reason you believe them. For example, "Feed has nothing from 3 March to 9 March. Last good line: 2 March, $1,204.50 balance. Next good line: 10 March." These dates are examples. They anchor every step that follows, including the file you cut and the check you run afterwards.

Worked example: a feed that skipped 3 to 9 March

Here is the example this guide uses throughout. All values are made up.

The feed has 2 March and 10 March but nothing in between. The gap is 3 to 9 March, four missing lines. Those four lines are the only ones that need to go in. If the gap is much bigger, say a month or more, importing older bank transactions into QuickBooks Online covers history that the feed cannot reach.

Trimming the import file to the missing dates only

Trimming means keeping only the statement rows whose dates fall inside the gap, and deleting the rest, before you upload. It is the step that prevents duplicates. QuickBooks imports the rows you select, so a file that covers the whole month invites back transactions you already have.

Get a file that covers the gap

You need your bank's transactions as a file QuickBooks Online accepts. Banks usually offer a CSV or QBO download from their transaction history, and you can usually pick a date range. If all you have is a PDF statement, convert it first. How to upload bank statements to QuickBooks Online covers the PDF case.

SimpleBankConvert is being built for that conversion. It turns a PDF statement into a CSV or QBO file QuickBooks Online can upload, and the early-access list is open at Get started. Accounts are not open yet.

Cut a CSV in a spreadsheet

For a CSV, open the file in a spreadsheet and work in this order:

1. Keep the header row.
2. Sort the rows by date, oldest first.
3. Delete every row dated before the first missing day.
4. Delete every row dated after the last missing day.
5. Check that the first and last dates left are inside the gap.
6. Save as CSV again, under a new file name so the original stays untouched.

In the worked example, the rows for 3, 5, 7 and 9 March stay. The rows for 2 and 10 March go, because QuickBooks already holds them. That leaves four lines.

Keep the file format intact

Intuit's page on uploading transactions from a file lists what a CSV needs. Each file needs either three columns (Date, Description, Amount) or four (Date, Description, Credit and Debit). Use one date format throughout. Leave zero-value cells blank in the Amount, Credit or Debit columns. Remove numbers from the Description column. After trimming, check that you did not delete the header or break a column.

The same page says a file must be 350 KB or less and can hold up to 1,000 lines per upload. A gap of a few days is far below either limit.

Cut a QBO file

A QBO file is harder to cut by hand because it is not a spreadsheet. Download a new QBO from the bank with a date range that matches the gap, if the bank allows one. That is safer than editing the file. If the bank gives you no date choice, ask for a CSV instead, or convert the statement to a file whose rows you can trim.

Upload it

Follow the steps in the upload guide. In short, go to Bank transactions, open the account's tile, open the Link account list and choose Upload from file, select your trimmed file, choose the QuickBooks account, match the columns, then select the transactions to import. Walking through the QuickBooks Online upload screens step by step shows each screen.

Will QuickBooks flag missing transactions it already has?

Do not rely on it. Intuit's upload page does not describe how QuickBooks detects duplicates when you upload a file, and it advises setting the date range carefully to avoid them. Your defence against doubling is a file that holds only the missing days, not a hope that QuickBooks will catch repeats.

Why a CSV is risky

A CSV row has a date, a description and an amount, and nothing that identifies the transaction itself. Two rows with the same date, text and amount look identical, whether they are one payment counted twice or two real payments. QuickBooks cannot tell them apart from the data alone, which is one more reason to cut the file to the gap.

Run the overlap check

The overlap check is a way to prove your trim was right before you import. Look at the dates on either side of the gap. In the worked example, 2 March and 10 March are the boundary days, and QuickBooks already has them.

1. Open your trimmed file and confirm the earliest date is 3 March and the latest is 9 March.
2. Confirm no row dated 2 March or 10 March remains.
3. After importing, search the register for 2 March and 10 March and confirm each line appears once.
4. Compare the QuickBooks balance on 10 March with the bank's balance for that day.

If a 2 March or 10 March line now appears twice, your file included a boundary day. Delete the duplicate, and fix the file before any later import.

Reviewing what the upload brings in

Uploaded rows go through the same review step as feed transactions. After you select the rows to import, they appear for review, where you match, add or exclude them. If you entered some of these payments by hand while the feed was down, match them rather than adding them again. Adding a payment you already typed in is the commonest cause of a double.

One payment entered by hand

If only one or two transactions are missing, a file is overkill. Manually adding a transaction in QuickBooks Online is quicker for a single payment, and it avoids any chance of a repeat.

Missing transactions that sit across two statements

A gap that spans a month end sits on two statements, so you need a file or a statement for each month, or one download that covers both. The principle does not change: keep only the dates inside the gap, and make sure each day appears once across the files you upload.

Which dates fall in which file

Suppose the feed skipped 28 February to 4 March. The 28 February lines are on the February statement, and the 1 to 4 March lines are on the March statement. A single bank download with a custom date range covering 28 February to 4 March is simplest, if your bank allows it. If it does not, make two trimmed files.

Keep the order and the dates clean

Upload the earlier file first. After each upload, check the register. Then upload the second file. Each file should end and start on its own side of the month end, with no shared days. A line from the last day of February should not appear in both files.

Watch statement cut-off days

Statements do not always end on the last calendar day. A statement period may run from the 15th to the 14th. A month-end gap then sits inside one statement period, or crosses two. Rely on the transaction dates in each row, not the statement label. Read the dates, trim by date, and ignore the file's title.

Check the balance at the seam

After both uploads, compare the QuickBooks balance at the last day of the gap with the bank's. If the figure differs by one transaction amount, a row is missing or doubled at the seam. Find the row by looking at the boundary day first.

Should you disconnect the feed before importing missing days?

No, you usually do not need to. Intuit's upload steps start from the account's tile and the Link account list, and they do not ask you to disconnect anything first. Disconnecting is a bigger step than the job needs, and it forces you to choose a start date again when you reconnect.

Why leave the feed alone

The feed fetches new transactions from today forward. Your gap is in the past. A file upload fills the past without touching the feed's job. As long as your file holds only the gap dates, the two do not collide.

The one case to wait

There is no pause switch to reach for: Intuit's page on updating recent bank transactions says automatic updates cannot be turned on and off. Hold the upload instead if the feed is currently delivering the very days you are about to upload, for example when it has recovered and is now back-filling the same stretch. Check For review first. If the missing days have started to arrive on their own, you do not need the file at all. If only some arrive, trim your file to the days that did not.

After the import

Once the file is in and the overlap check passes, leave the feed running and keep an eye on it for a week. If it skips again, QuickBooks not downloading bank transactions walks through the causes in order, and the account setup guide how to import a bank account into QuickBooks is worth a read if the account itself was set up in a way that makes gaps more likely.