CSV to QBO Converter for Multiple QuickBooks Company Files

Yes, and there is no limit on how many company files you can feed. What there is no such thing as is a single import that fans out to several companies at once. QuickBooks treats every company file as its own closed book, so each file gets its own upload, chosen and confirmed by you. Plan the work as one pass per company rather than one pass for the month.

That is less painful than it sounds once the naming is fixed. The slow part of a multi file close is almost never the upload itself, which takes seconds. It is hunting for which download belongs to which entity, and re-checking a file you are not certain about.

Yes. Every QuickBooks Online company requires its own paid plan, and Intuit does not bundle them on the standard consumer facing plans. Team access does not carry across either, so a staff member added to one company still has to be invited to the next. For firms, the exception worth knowing is QuickBooks Ledger, which is billed per company file and sold only through QuickBooks Online Accountant.

Desktop works differently again. A company file there is a file on disk rather than a subscription, so the cost question is licensing rather than per company billing, but the isolation between files is the same or stronger.

Name the file before you convert it, not after. A download called Export.csv in your downloads folder is the single most common cause of a misrouted import, because every bank names its export the same forgettable thing and you end up with six of them. Rename on arrival to something that carries the entity, the account and the period, then convert.

A pattern that survives a busy month looks like Northgate-Operating-1234-2026-08.csv: entity first so the files sort by client, then the last four of the account, then the period. When the converted QBO file inherits that name, the confirmation screen in QuickBooks becomes a real check rather than a formality, because the file name and the company you have open either match or they obviously do not.

Convert one entity at a time and finish it before opening the next. Our converter takes one file per run by design, and on a multi file close that is a feature rather than a limit: it forces a clean boundary between clients instead of a queue you can lose your place in.

You can, and occasionally you should, but be deliberate about it. A shared card or a management company account sometimes genuinely belongs in two sets of books. The converted QBO file is just a file, so nothing stops you uploading it twice into two different companies, and QuickBooks will not object because the duplicate check is per account inside one company file.

The risk is that you end up double counting real expense. If both entities post the same charges, one side needs to be a due to or due from entry rather than a second copy of the expense. Decide which entity owns the account before you import, not while you are reconciling.

The transactions land in the review queue of the wrong file, and you have to remove them there before they are accepted into the register. If you catch it in the queue it is a quick cleanup. If the batch was already accepted and categorized, you are undoing real ledger activity, and in QuickBooks Online that means working through the imported batch rather than pressing a single undo.

There is a sharper trap on the second attempt. Every transaction in a QBO file carries a FITID, an identifier that is unique within the account, and QuickBooks remembers the FITIDs it has already seen in that account even after you delete the transactions. Clean up a mistaken import and re-upload the same file to the same account, and rows can be silently skipped as duplicates. That is the reason to check the company name before uploading rather than to rely on being able to reverse it.

No, and this catches firms that run a mixed client base. No version of QuickBooks Desktop, including Enterprise, imports a bank CSV into the register. Bank data goes in as a QBO Web Connect file, or as IIF, which posts straight to the ledger with no review queue and no undo. The Import Excel and CSV Toolkit that people find first does not help here, because it imports four list types only: customers, vendors, items and the chart of accounts.

So for any Desktop client the CSV has to become a QBO file before it can go anywhere. That is the whole job, and it is why a firm with even two or three Desktop files ends up needing a converter as a standing part of the close rather than a one off.

QuickBooks Online accepts up to 1,000 transactions and 350 KB per upload, and the 350 KB ceiling applies to QBO, QFX and OFX files as well as to CSV. A busy operating account can pass 1,000 transactions inside a single quarter, and a full year of catch up almost always does.

Split by period rather than by row count when you hit it. Month by month or quarter by quarter files keep the boundaries meaningful, so if one upload has a problem you know exactly which period to redo. Cutting a year at row 1,000 leaves you with a seam in the middle of a month that nobody can reconcile later.

No. QuickBooks Online will not import bank transactions into a subaccount, which surprises firms that build tidy parent and child structures for multi entity clients. Import to the parent account and reclassify from there.

Worth checking before you design the chart of accounts for a new client rather than after the first import fails, because rebuilding an account structure once transactions are posted is far more work than getting it right at setup.

No. Duplicate protection lives inside one account in one company file, through the FITID carried by each transaction in a QBO file. QuickBooks skips FITIDs it has already seen in that account, and it holds that memory even after the transactions are deleted. Nothing compares one company file against another.

A plain CSV has no transaction identifier at all, which is the practical argument for converting to QBO on a multi file workload. Converted files carry unique transaction IDs, so re-uploading the same month into the same account is caught by QuickBooks rather than by you noticing the register looks wrong three weeks later. On our Plus plan and above those IDs come as standard, along with a conversion history you can check when you cannot remember whether August was already done.

It appears in both banks, so it arrives in both imports, and if you categorize both sides as ordinary income and expense you overstate both entities. Post one side against a due to or due from account, or a clearing account for the entity pair, so the transfer nets out and the intercompany balance stays visible.

QuickBooks Desktop Enterprise 2023 and later can create a matching entry in the other company file automatically, but only on the Accountant, Diamond and Platinum tiers. Everywhere else, including all of QuickBooks Online, the second side is yours to post.

For write up, tax only and year end clients, QuickBooks Ledger is the option built for the job and it is billed per company file, though it is sold only to firms with a QuickBooks Online Accountant subscription. It drops invoicing, receipt capture, bill pay, inventory and sales tax tracking, so it fits clients whose work arrives as history rather than as live operations.

Check sales tax before you put a client there. Ledger has no sales tax tracking, so any client with post Wayfair nexus obligations belongs on a plan that does. The QuickBooks Ledger bank import workflow covers what the Ledger bank feed will and will not reach on a year end file.

Count accounts, not clients. A client with a checking account and two cards is three downloads a month, not one, and each one is a separate conversion. Ten clients averaging two and a half accounts is roughly 25 conversions in a normal month, and two or three times that in January when prior year catch up lands on top of the current month.

That shape is why the plans are sized the way they are. Starter covers 100 conversions a month, which carries a solo bookkeeper through a normal close comfortably. Plus moves you to 500 and adds the unique transaction IDs and the conversion history that matter once you can no longer keep the month in your head. Pro removes the cap entirely and adds API access for firms that want the conversion step scripted into an existing workflow.

Run three conversions with no account and no card to see the output against a real client file first. A free signup gives unlimited conversions capped at 100 transactions per file with a watermark, which is enough to prove the column mapping on your banks before any money changes hands.

Paid plans start at $49 a month for Starter, or $24 a month billed yearly, and include automatic column mapping, opening and closing balances and split debit and credit handling. Plus is $149 a month, or $74 billed yearly, for 500 conversions, multi currency, the unique transaction IDs and conversion history. Pro is $499 a month, or $249 billed yearly, for unlimited conversions and retention plus API access. Firms needing SSO, a named contact or custom bank layout onboarding are on Enterprise, which is quoted directly.