To import a QBO file into QuickBooks Desktop for Mac, save the .qbo file from your bank, then go to Banking, open Downloaded Transactions and choose Import File. Pick the QuickBooks account the file belongs to, let the import finish, and add or match each line before it counts in your books.
Where is the QBO import on QuickBooks for Mac?
On QuickBooks Desktop for Mac, the QBO import sits under the Banking menu, not the File menu. Open Banking, choose Downloaded Transactions, then choose Import File and browse to the saved .qbo file. People who learned the Windows edition often look under File first and conclude the Mac version cannot import at all.
Intuit's guide to setting up online banking in QuickBooks Desktop for Mac describes the Web Connect route in that order: start from Banking, download and save the file from your bank's website, then select Downloaded Transactions and Import File. A QBO file is the Web Connect format, so "import a QBO file" and "import a Web Connect file" mean the same thing on a Mac.
Getting the file in the first place
The file comes from your bank's website, not from QuickBooks. Look on the bank's download or export page for an option labelled QuickBooks or Web Connect, and choose the dates you need. If the bank offers several formats, the one for QuickBooks is the .qbo file. A Quicken file with a .qfx ending is a different product's file and is not what these steps expect.
If the bank only gives you a PDF
A PDF statement cannot be imported at all; QuickBooks for Mac needs the lines as data. SimpleBankConvert is being built to turn a PDF statement into a QBO file, the file type QuickBooks Desktop opens, and you can join the early access list while accounts are not yet open.
Linking the QBO file to a Mac bank or card account
Every QBO file names one bank account, and QuickBooks for Mac stores its lines in one QuickBooks account that you choose. When the file holds more than one account, or the Mac asks, pick the matching account in the "Store in the QuickBooks Account" field and select Continue. That field decides where every line lands.
The Intuit setup guide mentions that field for files that cover several accounts. In practice, the safest habit is the same for every file: read the account name before you continue, even when it looks filled in already.
Steps from a saved file to the register
The list below is an example run for a checking account named "Business Checking 4417". Your account name will differ, and menu wording can shift slightly between releases.
- Back up the company file, since an import is hard to reverse once it has posted.
- Make sure "Business Checking 4417" already exists in the Chart of Accounts as a bank account.
- In QuickBooks, open the Banking menu and choose Downloaded Transactions.
- Choose Import File and select the .qbo file you saved from the bank.
- If asked, choose "Business Checking 4417" in the Store in the QuickBooks Account field, then Continue.
- Select OK when QuickBooks says the import has finished.
- Back in Downloaded Transactions, choose "Business Checking 4417" in the account list.
- Match or add each line, then compare the register balance with the bank's balance on the last date in the file.
Step 2 matters more than it looks. If the account does not exist yet, set it up first with the right type. A credit card file belongs in a credit card account, and a checking file belongs in a bank account. Putting one in the other flips the meaning of every amount.
One bank, several accounts
Many small businesses have a checking account and a savings account at the same bank. Download a separate file for each, or one combined file if the bank offers it, and confirm the account choice for each. A savings line that lands in checking leaves both registers wrong by the same amount in opposite directions, which is easy to miss on a quick glance.
Adding and matching QBO lines in Mac Downloaded Transactions
After the import, the lines wait in the Downloaded Transactions window until you deal with them. Each line is either matched to something already in the register or added as a new transaction. Nothing you skip reaches the register, so an untouched list means the import is only half done.
Intuit's article on adding and matching transactions in QuickBooks Desktop for Mac gives the working steps. Select the unmatched downloaded line and the register entry it belongs to, then choose Match. Matched lines show an orange circle. For a line with nothing to match, choose Add One, or Add Multiple for several, fill in the details and choose Record.
What a match needs
The same Intuit article says that for a match, the check number, amount, date and payee name must be similar to the entry in QuickBooks. That explains most "why didn't it match" moments. A check you typed as 412.80 that the bank cleared as 412.08 will never pair up, and neither will a payee you typed as "Flour Supply" when the download says "SQ *FLOUR SUPPLY CO".
Payee renaming saves the next import
Intuit's Mac guidance also suggests setting up payee renaming rules, so a messy bank description is renamed to one of your vendors. Set up a rule the first time a regular payee comes in with a long bank description. The next month's QBO file then lines up with your vendor list without retyping.
A short order of work
Handle the matches first, because they confirm work you already did. Then add the new lines one payee at a time. Finish with the balance check from step 8 above. If the register is off by the amount of one line, look for a line you skipped or one you added twice.
What changes between a Mac and a Windows QBO import?
The file is the same; the screens are not. A QBO file made for QuickBooks Desktop opens on both, but the menu path, the review window and some of the import tools differ. Instructions written for Windows will send you to menus and buttons the Mac edition does not have.
The differences that trip people up most often are these:
| Step | QuickBooks Desktop for Windows | QuickBooks Desktop for Mac |
|---|---|---|
| Where the import starts | File or Banking menu, depending on version | Banking, then Downloaded Transactions, then Import File |
| Where lines wait for review | Bank Feeds Center | Downloaded Transactions window |
| Adding several lines at once | Bank Feeds review screen | Add Multiple in Downloaded Transactions |
| Turning off downloads for an account | Bank Settings in Edit Account | Online Settings in the account's edit window |
The Windows route is covered step by step in importing bank transactions into QuickBooks Desktop on Windows. Use it only if you also work in a Windows copy, because its screenshots and button names will not match a Mac.
Spreadsheet and IIF imports
Windows guides often suggest other routes when a bank file is not available, such as an IIF file or pasting rows into a batch screen. Importing an IIF file into QuickBooks Desktop explains that format, and batch entering transactions in QuickBooks Desktop explains the paste-in screen. Both are written around Windows editions, so check that your Mac edition has the same menu before you build a file for it.
Release numbers
Mac releases are named by year, like Windows releases. Each year's release has its own support end date, and an unsupported copy can lose bank services. Check which release you run before you rely on any import route for the long term.
The Mac "Nothing imported" message after a QBO import
QuickBooks for Mac shows "Error: Nothing imported. Account up to date." when every line in the QBO file has been brought in before. It is not a damaged file. Each line in a Web Connect file carries a unique ID, and QuickBooks ignores any line whose ID it has already stored.
Intuit's article on the "nothing imported" Web Connect error gives that message for the Mac and explains the cause. It also lists fixes in order: restore a backup made before the earlier import, type a few missing lines by hand, or, with care, edit the account ID inside the file. The last option can create duplicates, so treat it as a final resort.
When you really did import it before
Usually the message is correct. Someone imported the same month last week, or the file overlaps a month already done. Open the register, filter to the file's dates and see whether the lines are there. If they are, you are finished.
When the lines are missing but the message still appears
If the lines are not in the register, they were probably added and then deleted. Deleting a downloaded line does not clear its ID, so a second import still skips it. For a handful of lines, typing them in is quicker than any repair. For a full month, restoring the backup from before the first import is cleaner than editing the file.
When the message points to the wrong account
Sometimes the lines did come in, but into another account. Check every account that the same bank feeds before you assume something is missing. A file that went into savings instead of checking will produce exactly this confusion on the second try.
When a QBO file is the wrong import for QuickBooks for Mac
A QBO file is the right tool for bank and card lines you want to review and match. It is the wrong tool for data that is not bank activity, for history the bank no longer offers, and for books kept in another program. Picking a different route early saves a month of cleanup.
Data that is not a bank statement
Invoices, bills, customer lists and journal entries do not belong in a QBO file. The format only carries dated amounts with a description and an ID. Forcing other data into it produces register lines with no customer, no item and no tax detail.
History you only have as a spreadsheet
If the bank no longer offers a download for an old period, you may have the lines as a CSV instead. QuickBooks Desktop does not read a CSV as a bank file. Importing a CSV of bank transactions into QuickBooks Desktop compares the ways around that, including turning the CSV into a QBO file first.
Books that live in Xero
Some readers searching for a Mac import actually keep their books in Xero, which takes a different bank file. Importing an OFX file into Xero covers that route. A QBO file is built for QuickBooks, so pick the format for the software you actually use.
A quick test before a big import
When you are unsure, import one month into a backup copy of the company file first. If the lines land in the right account, match cleanly and leave the register agreeing with the statement, the route works. Then import the rest one month at a time, oldest first, and write down which months are done.