Free CSV to QBO Converter for QuickBooks
Convert bank or credit card transactions from CSV into a QuickBooks Web Connect (.QBO) file. Upload your CSV, map the transaction columns, review the output, and download the converted file.
No sales call required to use the converter. If you repeat this process every week, month, or across multiple locations, Autymate can help automate the workflow after your conversion.
Choose your file
Drop your bank CSV or Excel file here
Your file is never uploaded. We never receive it or store it.
Why QuickBooks Rejects a .QBO File
A .QBO file is not just its transactions. It opens with a Web Connect header, and one line in that header decides whether QuickBooks will read the rest of the file at all: the Intuit Bank ID, written as INTU.BID.
QuickBooks checks that number against its own list of Web Connect banks. If it is missing or does not match, the file is refused before a single transaction is read. Nothing about your dates, amounts or column mapping is the problem when that happens.
The converter will not let you download a file without one. It reports the missing Bank ID as an error rather than handing you a file QuickBooks will reject.
| <ORG> | FIRST NATIONAL | The bank's name |
|---|---|---|
| <FID> | 10898 | The bank's own id |
| <INTU.BID> | 2430 | Accept or reject |
| <BANKID> | 121000248 | Routing number |
| <ACCTID> | ••••4417 | The account |
| <CURDEF> | USD | Currency |
Without a valid INTU.BID, QuickBooks refuses the file before it reads a single transaction.
Where Your Bank ID Comes From
You do not invent this number. It is copied from a file your bank already sent.
From a .QBO Your Bank Sent
If you have ever downloaded a Web Connect file from your bank, it already contains the right Intuit Bank ID. Open it in any text editor and look for the INTU.BID line.
Or Let the Converter Read It
Drop that older .qbo into the Bank ID field and the converter lifts the number out of it for you, so there is nothing to type and nothing to mistype.
It Belongs to the Bank, Not the Account
The same Bank ID is correct for every account at that bank, so once you have it you can reuse it for each statement you convert.
What a QBO File Actually Is
A bank-feed file for QuickBooks, not a spreadsheet and not QuickBooks Online.
A QuickBooks Web Connect Converter
This is a QuickBooks Web Connect converter: the .QBO it writes is the Web Connect format QuickBooks Desktop reads to bring bank-feed transactions in.
QBO Is Not QuickBooks Online
The .QBO extension and the QuickBooks Online product share three letters and nothing else. A .QBO file is a bank download; QuickBooks Online is a product you log into.
When Direct CSV Is Simpler
If you use QuickBooks Online and your CSV already meets Intuit's current upload requirements, the native CSV path may be all you need and converting is unnecessary.
How to Convert CSV to QBO
Four steps from CSV bank transactions to QBO, and the file never leaves your computer.
Drop Your CSV or Workbook
A .csv, .tsv or Excel export from your bank. The file is read in your browser, so nothing is uploaded and there is no sign-up.
.csv · .tsv · .xlsx · .xlsm
Match Your Columns
Date, description and amount, or a separate debit and credit pair. Recognised headers are matched for you and you correct anything guessed wrong.
auto-matched first
Set the Account and Bank ID
Account type, currency and the Intuit Bank ID that decides whether QuickBooks accepts the file. The Bank ID can be lifted from an existing .qbo.
INTU.BID required
Review and Download
Transaction count, running balance and anything that will be rejected are listed before you download, not after.
issues shown before download
How to Prepare a CSV for QBO Conversion
Six things worth checking in the export before you generate the file.
Date
Use a consistent transaction date column.
Description
Keep payee, memo, or transaction description text in a dedicated column.
Amount
Use one Amount column or separate Debit and Credit columns, depending on the source file.
Remove Report Noise
Delete summary rows, repeated headers, page titles, and non-transaction notes.
Check Signs
Confirm how the source distinguishes withdrawals and deposits.
Review Duplicates
Check repeated-looking rows before generating the QBO output.
The Bank ID You Re-enter Every Month
One file needs no setup. Twelve of them need the same setup twelve times.
| Need | Free converter | Autymate |
|---|---|---|
| One statement your bank sent as CSV | Faster than anything we could set up | No workflow to design yet |
| Recurring monthly export | Still manual each period | Automate the repeatable workflow when feasible |
| Daily files | Manual effort compounds | Use defined mappings and processing rules |
| Multiple stores or entities | Repeat conversion per file | Standardize mappings and routing where supported |
| Exceptions | You investigate manually | Build validation, error context, and a support path |
After It Reaches Bank Feeds
The honest part: an accepted file is the start of a review, not the end of the job.
Nothing Posts On Its Own
Web Connect transactions arrive in Bank Feeds for review. They are matched or added by you, so an import does not change the books until you accept it.
Matching Against What Is There
QuickBooks tries to match each transaction to something already recorded. The closer your description and date columns are to reality, the more of that it gets right.
Re-importing the Same Period
Each transaction carries an id from the source file, which is what lets QuickBooks recognise one it has seen before. An overlapping date range is safer than a gap.
Converting Files for Multiple Locations?
The converter is built for a file. These are the parts that repeat once the same export arrives every period from every store, entity or QuickBooks company.
- Different CSV layouts, normalized into a controlled structure
- Different account mappings, kept as approved rules rather than rebuilt in spreadsheets
- Missing or late files, with completeness checks and exception ownership
- Multiple QuickBooks companies, with routing scoped where the environment supports it
- New locations, onboarded through a documented mapping process
- Historical catch-up, with duplicate-safe backfill and reconciliation
Common Questions
What people ask before they trust a converter with their accounting system.
It reads bank or credit card transactions from a CSV file and writes them into the QuickBooks Web Connect (.QBO) format, including the header QuickBooks checks before it will accept the file.
No. The .QBO extension is a Web Connect bank-feed file used by QuickBooks Desktop. QuickBooks Online is a separate product, and the two share an abbreviation rather than a format.
For bank transactions, often yes. QuickBooks Online provides its own CSV upload, and if your file already meets Intuit's current requirements, converting to QBO may be unnecessary.
Yes. Web Connect .QBO files are the format QuickBooks Desktop reads to bring bank-feed transactions into a company file.
A bank CSV to QBO conversion needs a date, a description and an amount. The amount can be one signed column or a separate debit and credit pair, and the converter will map either.
Yes, if the statement has been exported as transaction rows rather than a PDF or a screenshot. A CSV with one row per transaction converts; a report layout with subtotals and page headers needs cleaning first.
No converter should guarantee that. QuickBooks version, company-file setup, the account you import into and the quality of the source data all affect the result.
Most often the Intuit Bank ID. QuickBooks checks the INTU.BID value in the file header against its own list of Web Connect banks and refuses the file if it is missing or does not match, before reading any transactions.
If the CSV comes from a recurring source such as a POS, bank, payment platform or ERP, Autymate can scope a managed QuickBooks workflow when authorized source access and destination behavior are available.
That is the case it is built for. Controlled mapping, routing to the correct QuickBooks environment and exception handling across entities are the parts that do not scale by repeating a conversion per file.
Written and maintained by The Autymate integrations team. We build and run accounting integrations for multi-location franchises, ISVs and bookkeeping firms: QuickBooks Desktop and Online, POS, payroll and ERP. These converters exist because we kept writing the same ones for customers, and there was no reason to keep them to ourselves.
Last reviewed
Stop Rebuilding the Same File Every Period
The converter is the right tool when you need to fix one file. If the file comes from the same source every day, week, or month, tell us where it starts, which QuickBooks environment receives it, and what you have to fix before every import.
Exact source access, fields, permissions, QuickBooks behaviour and service scope are confirmed during discovery.