Excel to QBO Converter: Convert Excel to QBO and XLSX to QBO

Of the four routes above, only conversion to .qbo avoids both the row cap and the mapping screen, and it is the only one that works in QuickBooks Desktop at all. Upload your .xls or .xlsx file in the converter above and download a .qbo Web Connect file in one pass. The tool reads the spreadsheet directly, finds the date, description, and amount columns, reformats them into the structure QuickBooks expects, and gives you back a .qbo you import as a standard bank feed.

No, QuickBooks Online cannot import a raw .xls or .xlsx file for bank transactions. It only accepts a strict CSV or a .qbo Web Connect file. To get Excel data in, you either reformat the sheet to QuickBooks' exact CSV rules or, more reliably, convert the Excel file to a .qbo first and upload that.

QuickBooks Online does not accept .xlsx for importing bank and credit card transactions; that upload path takes CSV or .qbo only. A few list imports such as customers and products allow Excel, but transaction feeds do not. Converting your .xlsx to a .qbo is the dependable way to bring spreadsheet transactions into the bank feed.

An Excel file is a flexible spreadsheet with any columns, formatting, and multiple sheets, so no two exports look alike. A .qbo file is a QuickBooks Web Connect file in OFX format with a fixed layout QuickBooks reads natively. Converting Excel to QBO turns an unpredictable workbook into the precise file QuickBooks was built to accept.

Convert the Excel file to a .qbo, then in QuickBooks Online open All apps, Accounting, Bank transactions, select the account, and choose Link account followed by Upload from file. Some accounts still land on that same screen through the older Transactions, Bank transactions menu. Pick the .qbo and QuickBooks imports every row into the review queue as a bank feed. This skips the column-mapping wizard that the CSV path forces you through.

QuickBooks rejects Excel imports because it does not read .xlsx for transactions, and a save-as-CSV often breaks on Excel's auto-formatting: dates flipped to serial numbers, dropped leading zeros, scientific notation on long account numbers, or amounts with currency symbols. Converting the workbook straight to .qbo applies QuickBooks' formatting rules and removes these failure points.

Drop the .xlsx into the converter above; it parses the sheet, detects the transaction columns, and builds a .qbo without you saving to CSV first. Dates are normalized to MM/DD/YYYY, currency symbols and thousands commas are stripped, and debits and credits are signed correctly before the .qbo downloads, ready to import.

Yes, but not as a spreadsheet. Convert it to a .qbo (or a QuickBooks-formatted CSV) first. A .qbo import works with a spreadsheet from any source because the converter reshapes the data into the exact OFX structure QuickBooks reads, so you are not limited to QuickBooks' narrow CSV column and date rules.

No. The converter opens .xls, .xlsx, and .xlsm files directly, so you skip the save-as-CSV step entirely. That step is where most Excel imports go wrong, because Excel rewrites dates, drops leading zeros, and adds scientific notation when it exports. Converting from the original workbook keeps your data intact.

At minimum your spreadsheet needs a date column, a description column, and an amount column, or separate credit and debit columns. The converter auto-detects these even when they are not in QuickBooks' required order or have extra columns around them, so you do not have to delete or rearrange anything before uploading.

Yes. Upload the workbook and the converter reads the transaction rows from it. Keep the bank or card activity together with clear date, description, and amount columns. If a workbook holds several different accounts, convert each account's data separately so every register gets its own .qbo and nothing is mixed across accounts.

Yes, and verifying that is the point. Before the .qbo downloads, the converter adds up every transaction it parsed and compares the sum to your spreadsheet total. If a row was missed or misread, you see it in the preview rather than during reconciliation weeks later. You export only once the parsed rows match your file.

Because Excel interprets what it thinks a date means before it writes the file. Two rules cause most of the damage. A two-digit year between 00 and 29 is read as 2000 through 2029, while 30 through 99 is read as 1930 through 1999, so a statement dated 1/5/30 silently becomes 1930. Separately, Excel for Windows defaults to the 1900 date system and Excel for Mac to the 1904 system, so a workbook passed between the two shifts every date by four years and a day. Converting the workbook directly sidesteps both, because the transaction dates are read from the cells rather than from whatever Excel decided to print into a text file.

Same converter, same result, because it runs in the browser rather than as an add-in. This matters more than it sounds. Most desktop conversion tools for QuickBooks are Windows Excel add-ins, so Mac users are pushed into saving as CSV and hand-fixing the output. The 1904 date system on Mac makes that worse, since a file that looked correct on the accountant's Windows machine can come back four years out. Uploading the workbook itself removes the whole class of problem.

Convert the spreadsheet to a .qbo and import it into the credit card account, not a bank account. The one extra thing to watch on card data is the sign. On a credit card the meaning flips: a charge increases what you owe and a payment reduces it, so a card export whose amounts are signed the same way as a checking export will post backwards. The converter reads the column layout and applies the card convention, and the reconciliation check catches a file whose total lands the wrong way around. If the card export is already a .csv rather than a workbook, the credit card CSV to QuickBooks page covers that path in full.

Not for transactions, in any version. QuickBooks Desktop has no transaction import for spreadsheets or for CSV. The Import Excel and CSV toolkit that ships with it handles exactly four list types, customers, vendors, items and the chart of accounts, and nothing else. The only supported route for bank and card activity is a .qbo Web Connect file through Bank Feeds, which is why converting the workbook is not a shortcut in Desktop, it is the path. IIF can also post transactions, but it writes straight to the ledger with no review queue and no undo, which is a poor trade for routine bank data.

Yes, and this is where converting beats the native upload by the widest margin. A QuickBooks Online CSV upload is capped at 1,000 rows and 350 KB per file, which a moderately busy checking account passes in a few months, so a year has to be split and remapped piece by piece. A .qbo has no such ceiling, so twelve months of a workbook converts to one file and imports in one pass. For very large histories, splitting by quarter still makes the review in the bank feed easier to work through.

Bank exports opened and edited in Excel usually pick these up, and they are read as values rather than as structure. Formulas resolve to whatever they currently evaluate to, which is fine. Subtotal and running-balance rows are the real risk, because a subtotal looks exactly like a transaction to any parser: it has a date next to it and a number in the amount column. Delete the subtotal, total and running-balance rows before uploading, keep one header row, and let the reconciliation check confirm the parsed total against the statement. A file that comes back over by a neat round amount usually still has a subtotal row in it.

Most failed imports start the moment you choose Save As CSV in Excel. Excel reformats data on the way out: a date can become a five-digit serial number, an account number loses its leading zeros, a long reference flips to scientific notation such as 1.23E+11, and negative amounts may export wrapped in parentheses QuickBooks reads as text. Each of these passes silently and then fails the upload one row at a time. Converting the original .xlsx straight to .qbo never routes through Excel's CSV export, so the values land in QuickBooks exactly as you see them in the sheet.

Bookkeepers and accountants handling catch-up and cleanup work convert Excel to QBO most, because clients deliver a year of activity as spreadsheets that never match QuickBooks formatting. Small business owners use it for accounts QuickBooks cannot connect by live bank feed, and for credit unions or niche cards that only offer an Excel download. Anyone who keeps a manual transaction log in Excel can turn it into a clean .qbo instead of retyping every line into QuickBooks.