# Import Checks into QuickBooks Desktop with Numbers

- Author: SimpleBankConvert (https://simplebankconvert.com)
- Published: 2026-10-17
- Category: QuickBooks Desktop imports
- Canonical: https://simplebankconvert.com/blog/import-checks-into-quickbooks-desktop

> How to import checks into QuickBooks Desktop so check numbers, payees and amounts carry over, by Web Connect file or batch entry from a spreadsheet.
You can import checks into QuickBooks Desktop two ways. A Web Connect file from the bank brings each cleared check with its number and amount, and Desktop matches it to a check you already wrote. Batch entry in the Accountant and Enterprise editions lets you paste a list of checks, payees included, from a spreadsheet.

## Do check numbers survive a Web Connect import into Desktop?

Check numbers usually survive a Web Connect import, as long as the bank put them in the file. A Web Connect (.qbo) file has a place for a check number on each line. Banks that fill it give Desktop the number, the amount and the clearing date. Banks that leave it empty send only a description such as "CHECK 1043".

The number matters because Desktop uses it to pair the bank line with your own entry. [Intuit's guide to adding and matching Bank Feed transactions in QuickBooks Desktop](https://quickbooks.intuit.com/learn-support/en-us/help-article/bank-connectivity/add-match-bank-feed-transactions-quickbooks/L3FoaeL3b_US_en_US) says that when QuickBooks makes a match, it looks at the check numbers, amount, date and who was paid. A check that arrives with its number therefore has the best chance of matching on the first pass.

### How to tell whether your bank sends the number

Import one month and open the review list. If the check lines show a number in their own field, the bank fills it. If the number only appears inside the description text, the bank does not, and Desktop has to rely on amount and date alone. That still works for most checks, but two checks for the same amount in one week can pair the wrong way round.

### When the file comes from a PDF statement

Many PDF statements print a checks section with a number, a date and an amount for each check. When that PDF is turned into a Web Connect file, the number has to be read off the page and placed in the file's check number field. A converter that drops it into the description instead gives you the weaker kind of match. SimpleBankConvert is being built to produce QBO files from PDF statements; you can [see what it will do on the homepage](/) while accounts are not open yet.

The full import route, from saving the file to linking the account, is in [importing bank transactions into QuickBooks Desktop with a Web Connect file](/blog/how-to-import-bank-transactions-into-quickbooks-desktop). This post stays on what happens to the checks.

## Matching imported checks to checks already written in Desktop

If you write checks in Desktop with Write Checks, the import should match each cleared check to that entry, not add a second one. Accepting the match marks your check as cleared and leaves the payee and expense account you chose in place. Adding it instead creates a duplicate expense.

Most businesses that write paper checks already record them in Desktop when they print or hand-write them. The bank file then only confirms which ones cleared and when. That is why matching is the main event for checks, and adding new ones is the exception.

### Worked example: five checks in one month

The table below is an example. The payees, numbers and amounts are made up.

| Check no. | Written in Desktop | Bank line in the file | What to do |
| --- | --- | --- | --- |
| 1041 | Mar 2, Harbor Rentals, 1,850.00 | Mar 4, check 1041, 1,850.00 | Accept the match |
| 1042 | Mar 5, Delta Signs, 312.40 | Mar 11, check 1042, 312.40 | Accept the match |
| 1043 | Not entered | Mar 12, check 1043, 96.00 | Add it, with the payee from the check stub |
| 1044 | Mar 18, Delta Signs, 312.40 | Not in this file | Leave it open; it clears later |
| 1045 | Mar 22, J. Ortiz, 420.00 | Mar 26, check 1045, 402.00 | Stop: amounts differ, check the stub and the bank |

Check 1043 is the common gap: a check someone wrote from the book and never entered. Check 1044 is not a problem at all, only a timing difference. Check 1045 needs a person. Either the check was entered wrong or the bank cleared a different amount, and only the paper or the bank's check image settles it.

### Watch the same-amount pair

Checks 1042 and 1044 in the example are both 312.40 to the same payee. If the bank did not send check numbers, Desktop could offer to match the March 11 bank line to check 1044 instead of 1042. Look at the number before accepting any match where the amount repeats.

### Matching deposits works the same way

Deposits are paired on similar details, but they bring their own problems, such as several customer checks bundled into one deposit. Those are covered in [importing deposits into QuickBooks Desktop](/blog/import-deposits-into-quickbooks-desktop).

## Why does an imported check arrive without a payee?

An imported check often arrives without a payee because banks do not know who you paid. The bank sees a check number and an amount; the payee name is written on the paper, not in the bank's records. So a Web Connect line for a check usually reads "CHECK 1043" or similar, with no name.

When the check matches one you wrote in Desktop, this does not matter. Your entry already has the payee, and the match keeps it. The problem only shows up for checks you never entered, such as check 1043 in the example above.

### Filling in the payee for an added check

For an unmatched check, add it and type the payee from the check stub, the carbon copy or the bank's image of the check. Then choose the expense account. Do not leave the payee as "CHECK 1043"; a vendor list full of check numbers makes every later report harder to read.

### Why renaming rules do not help here

Renaming rules turn a recurring bank description into a vendor name. Checks defeat them, because every check has a different number and the same description shape. A rule that renames all "CHECK" lines to one vendor would be wrong for every other payee. Fill check payees in by hand, or enter the checks in Desktop before the import so they match.

### Moving from Quicken

People moving from Quicken sometimes expect payees to come across with their checks, because Quicken stored them. A bank file will not bring them. If you are changing software rather than importing a statement, [switching from Quicken to QuickBooks Online](/blog/switch-from-quicken-to-quickbooks-online) explains what carries over in that move.

## Batch entering checks from a spreadsheet in Desktop Accountant or Enterprise

If you keep a check log in a spreadsheet, the Batch Enter Transactions screen lets you paste the whole list into Desktop with payees, numbers and accounts. [Intuit's article on batch entering transactions](https://quickbooks.intuit.com/learn-support/en-us/help-article/accountant-features/accountant-tools-batch-enter-transactions/L2dnHEij8_US_en_US) says the feature is available in QuickBooks Desktop Accountant or QuickBooks Desktop Enterprise, and lists checks as a transaction type.

This route suits a business that writes many checks and logs them as it goes. It brings in what the bank cannot: the payee and the expense account. The bank file then only has to confirm clearing.

### Laying out the spreadsheet

The Intuit article says to arrange the spreadsheet's columns to match the column order of the Batch Enter Transactions screen, then copy the rows and paste them by right-clicking the first date field. Open the screen first, choose Checks and the bank account, and copy the column order it shows into your sheet. A typical example layout is date, check number, payee, account, memo and amount, but follow what your screen shows, not this list.

### Payees that do not exist yet

A payee in the sheet that is not on any Desktop list will hold up the paste. Desktop will ask about it before it saves. Add new vendors first, or be ready to answer those prompts, so the batch saves in one pass.

### Older checks from past statements

For checks from months before you started in Desktop, the source is usually the old statements themselves. [Importing old bank statements into QuickBooks Desktop](/blog/import-old-bank-statements-into-quickbooks-desktop) covers getting that history in month by month, which is often simpler than rebuilding an old check log.

## Uncashed checks that clear on a later bank statement

A check written in one month and cashed in the next is normal, and it needs no special import. Leave it in the register as uncleared. When the next month's Web Connect file brings the cleared line, Desktop matches it to the open check, and the check is cleared at last.

The mistake is treating the gap as an error. At month end, the register balance and the bank's balance will differ by the total of checks still out. That difference is expected. Reconciliation lists those open checks so you can see that they explain the gap.

### Checks that never clear

Some checks are lost or never cashed. After a long wait, contact the payee, then void and reissue the check if needed, or void it if the debt is settled another way. Do not delete an old check just to make the register agree with the bank, because it removes the record that the payment was owed.

### Checks voided after the import

If a check matched to a bank line is later voided, the bank line still exists and the money still left the account. Voiding the check in Desktop would then make the register disagree with the bank. Void only checks the bank never paid, and record a stopped payment fee as its own line when the bank charges one.

## Duplicate checks from importing and batch entering the same list

Duplicate checks appear when the same checks reach Desktop by two routes and none of them get matched. A batch entry adds them, then the Web Connect file brings the same checks, and someone chooses Add instead of Match. The register then shows each check twice and the bank balance never agrees.

The fix is to choose one source of truth for each check before you import anything. Either the check is entered in Desktop first, by Write Checks or batch entry, and the bank file only matches it. Or the bank file adds it, and nobody enters it by hand. Mixing the two routes for the same check is what causes trouble.

### Finding the duplicates

Open the bank register and sort by number. Two entries with the same check number and amount, one cleared and one not, are the classic sign. Delete the uncleared copy, then check that the cleared one kept the right payee and account.

### Before a large batch, back up

[Intuit's guide to importing and exporting data in QuickBooks Desktop](https://quickbooks.intuit.com/learn-support/en-us/help-article/import-export-data-files/import-export-data-quickbooks-desktop/L9KS42UxP_US_en_US) states that you cannot undo an import and advises a backup before any import. Batch entry is not technically an import, but the same caution applies: cleaning up fifty pasted checks by hand takes far longer than restoring a backup.

### A rule for every month

Enter the month's checks before the month's bank file arrives. Then import the file, match every check that has a number, add the stragglers with their payees, and leave the rest open. Repeat each month and the duplicates stop appearing.