CSV to QBO Converter for Construction: Import Contractor Bank and Card CSV Files into QuickBooks

No. Enterprise Contractor Edition has the deepest job costing reporting Intuit ships, including job profitability and Costs to Complete by Job Summary, but it inherits the same banking limitation as every other Desktop edition. It cannot read a bank or credit card CSV. The only import it accepts for banking activity is a .qbo Web Connect file, which is exactly what this converter produces.

Export the card activity as CSV from the card issuer, convert it to .qbo, and import it into the credit card account you already set up in QuickBooks. The transactions land in the register unclassified. You then assign each one to a customer or job, and on Desktop tick the billable box if the cost is being passed through. Tagging happens after the import, never inside the file.

Yes, once they are in the register. On QuickBooks Desktop you assign a Customer:Job to each line and optionally a class for the division or crew. On QuickBooks Online you assign the transaction to a Project. Neither the bank feed nor an imported .qbo can do the tagging for you, because a bank file carries no job information. The import gets the money in accurately; the coding is the accounting work that follows.

Yes, through Projects, and it starts at QuickBooks Online Plus. Essentials and Simple Start cannot track project profitability, so a contractor on those tiers has cost data with nowhere to put it. Plus and Advanced both include Projects, and Advanced adds cost estimates. Importing transactions works identically on every tier, so the subscription decision is about reporting rather than about getting data in.

Download the transaction export from the fuel card portal as CSV, convert it to a .qbo, and import it into a QuickBooks account that represents that card. Fuel networks issue cards outside the normal banking rails, so there is usually no feed to connect. Once imported, code each purchase to the truck or job. Contractors running twenty vehicles usually convert one file per month rather than chasing individual receipts.

Set up each project as a job under the customer, then make sure every cost carries that Customer:Job. Bank and card imports supply the raw spending, bills supply supply house purchases on terms, and payroll supplies labor. Run Job Profitability Detail to see where a job stands. The reporting is only as complete as the cost data, which is why the unconnected card and supply accounts matter so much.

You can, but decide first what the record should be. If you buy on 30 day terms, those purchases belong in accounts payable as bills so the job sees the cost on the purchase date and the vendor balance stays right. Convert and import the account activity only when you are treating it like a card, meaning you want a register to reconcile against the statement. Do not do both for the same purchases.

All of them, one file at a time. A .qbo Web Connect file maps to exactly one account, the same rule QuickBooks applies to files downloaded straight from a bank, so a builder with two operating accounts, three cards and a fuel card converts six files. There is no cap on how many accounts a company file can hold. The discipline that matters is importing and reconciling each one in the same order every month.

Direct Connect stops for everyone on October 30, 2026, and Direct Connect bill pay ends with it. Per version bank feed sunsets continue on their own schedule, with 2024 supported through September 30, 2027. Web Connect .qbo imports are not affected by either deadline. Practically, a contractor staying on Desktop or Enterprise moves to downloading a file each period and importing it, converting from CSV wherever the bank offers no .qbo.

On Desktop, yes. File imports carry no date limit, so a January to December export goes in as one .qbo, which is how contractors catch up a neglected job file before a WIP schedule or a tax deadline. On QuickBooks Online, manual uploads are capped at 350 KB and 1,000 rows, so split a busy year by quarter. Bank feeds usually pull only about 90 days on first connect, which is the whole argument for a file based backfill.

Not if your date ranges do not overlap. Every transaction in a converted .qbo carries a stable unique ID, the field QuickBooks checks against activity it has already seen, so a repeated import of the same file is normally recognized and skipped. The safer habit is still to import clean, non overlapping periods and reconcile each account before importing the next one.

No. Amounts, dates and descriptions pass through exactly as the bank or card portal wrote them, and the converted totals reconcile to the source file. That matters more in construction than in most industries, because a job cost report feeds change orders, draw requests and WIP schedules that other people rely on. If a number in QuickBooks does not match the statement, the reconciliation is where you want to find it, not the conversion.