Convert CSV to QBO on a Mac for QuickBooks

To convert CSV to QBO on a Mac, check the bank CSV in TextEdit, fix it in Numbers or Excel without letting either rewrite the dates, then run it through a Mac or browser-based converter. Import the QBO through Downloaded Transactions in QuickBooks Desktop for Mac, or upload it in QuickBooks Online.

Can a Mac convert CSV to QBO without Windows?

A Mac can convert CSV to QBO without Windows. Some converters ship as Mac apps and others run in a web browser, so neither Boot Camp nor a virtual machine is needed. The harder part on a Mac is keeping the CSV intact on its way to the converter.

A QBO file is a Web Connect file: a text statement in the OFX family that QuickBooks reads as if it came from your bank. Nothing about it is tied to Windows. What matters is that the converter reads the CSV columns correctly and writes a valid bank header. What is inside a QBO file lists those parts if you want to check the output by eye.

When you compare tools, look for these on a Mac:

• It runs on your macOS version. An older app may not open on a recent Mac. A browser tool avoids the question.
• It shows a preview. You should see the first rows parsed into date, payee and amount before you save.
• It lets you set the date order. Month first or day first, chosen by you, not guessed.
• It asks for the account type. Checking, savings or credit card, so the signs come out right.

The same tools often write QFX too, for Quicken. If that is what you need, choose QFX at the save step. The CSV preparation below is identical.

Keeping Numbers and Excel for Mac from rewriting CSV dates

Numbers and Excel for Mac can rewrite CSV dates the moment they open the file. They read date-like text using your Mac's region settings, then save it back in whatever format the cell displays. A day-first bank file opened on a US Mac can turn 03/04 into March 4 silently.

The safest rule is to avoid opening the bank CSV in a spreadsheet at all if it is already clean. Many bank CSVs need nothing more than a look in TextEdit and a straight trip to the converter.

When you do need to edit it, for example to delete a summary row, protect the dates:

1. Look first. Open the file in TextEdit and note how dates are written, such as 2026-03-04 or 04/03/2026.
2. Edit, then check the same rows. After editing in Numbers or Excel, export to CSV and open the new file in TextEdit. Compare three dates with what you noted in step 1.
3. Prefer year-first dates. If the spreadsheet changed them, format the date column as year, month, day before you export. That style cannot be misread.
4. Watch amounts too. A cell showing (64.18) or $64.18 may be exported that way. Format amounts as plain numbers with a minus sign.

In Numbers, the export lives under File, then Export To, then CSV. In Excel for Mac, use Save As and choose CSV UTF-8. Both write a text file the converter can read. The trap is not the export itself but what the app changed when it first opened the file.

Checking the CSV in TextEdit before the QBO conversion

TextEdit shows a CSV exactly as the converter will read it: plain text, commas and all. Open it there, make sure it is in plain text mode, and read the header row and the first three lines. You will spot reordered dates, stray quote marks and summary rows in seconds.

TextEdit opens .csv files as plain text by default. If you see fonts and formatting, choose Format, then Make Plain Text. Do not save from TextEdit unless you meant to change something.

Here is an example of what a clean file looks like. The values are made up:

Date,Description,Amount
2026-03-02,LAKESIDE PRINT SHOP,-48.20
2026-03-04,DEPOSIT INV 3307,975.00
2026-03-06,MONTHLY ACCOUNT FEE,-15.00

Read it against this list:

• One header row. No bank name, account line or blank lines above it.
• One kind of date. Every date in the same style.
• Signed amounts. Money out has a minus sign. If the file has separate debit and credit columns, that is fine too, as long as the converter can map both.
• No totals at the bottom. A row like Total,,1234.56 becomes a fake transaction.
• Commas inside descriptions are quoted. A description such as "SMITH, J" must sit in quotes, or it splits into two columns.

If the file passes, send it straight to the converter. Every trip through a spreadsheet is another chance for a change.

Making the QBO file on a Mac, step by step

Making the QBO file on a Mac takes about eight steps: download the CSV, check it in TextEdit, open the converter, map the columns, set the date order, enter the account details, save as .qbo, and read the new file once in TextEdit. Most of the time goes into the checks, not the conversion.

1. Download the CSV from your bank for one account and one date range. Note the date range.
2. Check it in TextEdit, as in the previous section.
3. Open the converter and load the CSV.
4. Map the columns. Date to date, description to payee or name, amount to amount. Map a memo or reference column if you have one.
5. Set the date order to match what you saw in TextEdit.
6. Enter the account details. Account type, the last digits of the account number and the bank, if the converter asks.
7. Save as .qbo. Give it a name that says the account and dates, such as checking-2026-03.qbo.
8. Open the QBO in TextEdit and find the first <DTPOSTED> and <TRNAMT> values. 20260302 and -48.20 would match the example above.

The QBO header may start with plain lines such as OFXHEADER:100, or with an XML declaration. Both are valid OFX styles. The difference between OFX SGML and XML files explains when that matters. If you ever need to look inside a Quicken download in the same way, how to open a QFX file shows the same TextEdit approach.

Opening a Mac-made QBO file in QuickBooks Desktop for Mac

QuickBooks Desktop for Mac imports a QBO file from the Banking menu. Intuit's guide to downloading bank transactions in QuickBooks Desktop for Mac says to choose Banking, then Downloaded Transactions, then Import File, and select the file. It also confirms Web Connect transactions open from a .qbo file.

Before importing, back up the company file. A QBO import adds transactions you cannot undo with one click.

During the import, QuickBooks asks which account the file belongs to. Pick the existing bank account if it is the right one. Create a new account only if you mean to. Picking the wrong account is the most annoying mistake to fix later, because the transactions then have to be moved or deleted one by one.

After the import, compare the number of downloaded transactions with the number of rows in the CSV. Then match or add them as you would a normal bank download.

A QBO file only holds bank lines. If what you have in the CSV is really an accountant's adjustments, with accounts and debits and credits, it is a journal entry list, not a bank file. Importing journal entries into QuickBooks Online covers that route instead.

Does QuickBooks Online on a Mac need a QBO file at all?

QuickBooks Online on a Mac often does not need a QBO file. It runs in the browser and its bank upload takes a CSV directly, so you can skip the conversion. A QBO file saves the column-mapping step, but mapping a three-column CSV is short work.

Choose QBO for QuickBooks Online when:

• You upload often for the same account and want no mapping screen.
• The bank's CSV has odd columns that you would rather fix once in a converter.
• You also use QuickBooks Desktop for Mac and want one file for both.

Choose CSV when you upload once in a while, or when you want to read and fix the file in a spreadsheet first. Either way, apply the date checks above.

If your bank only gives you PDF statements, not CSV, the CSV step can come from the PDF instead. SimpleBankConvert, which is in early access, is being built to turn PDF statements into CSV or QBO files for QuickBooks Online. Get started to be told when accounts open.

Why does a Mac QBO import say nothing imported?

A Mac QBO import says nothing imported when every transaction ID in the file has been imported before. Intuit's article on the "Nothing imported" Web Connect error says QuickBooks for Mac shows "Error: Nothing imported. Account up to date" and skips transactions with repeated IDs.

With a converted file, this usually happens in one of two ways. You imported the same file twice. Or the converter builds IDs from the date and a counter, and you converted an overlapping CSV that produced the same IDs for the same days. The second case is useful when it stops real duplicates, and confusing when the lines were new.

Intuit's article lists three fixes, in order: restore a backup made before the earlier import and import again; enter a few missing lines by hand; or edit the account number in the file's ACCTID field, which Intuit's steps do by deleting its last digit. Its steps for that last fix use TextEdit on a Mac.

To avoid it in the first place, keep each CSV to a date range that does not overlap the last one, and name files by date range so you can see at a glance what has already gone in.