Convert trucking bank, factoring settlement and fuel card CSV exports into .qbo Web Connect files for QuickBooks. Get gross revenue, fees and fuel by state.
No account needed for your first conversions. We never store your bank login.
Short answer: most of a trucking company's money never touches a rail QuickBooks can read. Factoring advances, fuel card accounts and TMS settlements all arrive as CSV or Excel files, not as bank feed lines. Export each one, convert it with the tool at the top of this page, and import the resulting .qbo Web Connect file into QuickBooks Online or QuickBooks Desktop. You end up with gross revenue, factoring fees and fuel purchases as separate, dated, categorizable lines instead of one lump deposit you cannot break apart. Last updated July 2026.
Ask an owner operator what they made last month and they will usually quote what hit the bank. That number is wrong, and the bank feed is the reason. A factoring company does not deposit the invoice. It advances most of it, keeps a fee, sometimes nets out a fuel advance or an insurance installment, and wires whatever is left for several loads at once. The feed sees one deposit from a company name. The books need the gross revenue on those loads, the factoring fee as an expense, and each load tied to the truck that ran it. None of that can be recovered from a single deposit line, no matter how good the categorization rules are.
The factor knows all of it. Every factoring company publishes a settlement or purchase report, and every one of them will export it to CSV or Excel. Same story with the fuel card. Comdata, EFS, WEX and TCH accounts are issued by fleet card networks rather than banks, so QuickBooks has nothing to connect to, but each one exports a transaction file with the location, the state, the gallons and the price. That is where a trucking company's real cost detail lives, and converting those files is how it gets into the register.
Fuel by state is the other reason this matters. A quarterly IFTA return needs gallons purchased in each jurisdiction against miles run in each jurisdiction. A bank feed gives you one line reading COMDATA and a total. The fuel card CSV gives you every stop with the state on it. Convert that file and the detail is in QuickBooks, sitting next to the revenue it paid for, instead of in a spreadsheet you rebuild every quarter.
The converter reads .csv, .txt, .xls, .xlsx and .xlsm in any column order. It handles mixed date formats, strips dollar signs and thousands separators, reads either one signed amount column or separate debit and credit columns, and writes a valid .qbo with a unique ID on every transaction so QuickBooks can tell a re-import from genuinely new activity. It also exports the same data to XLSX or CSV when a settlement has to go to a tax preparer or a factoring dispute needs a clean workpaper.
| Where the money moves | Bank feed available | What the feed shows | What the CSV export shows | Why it matters |
|---|---|---|---|---|
| Factoring company settlements | No, a factor is not a bank | One net deposit, several loads | Every load, advance rate, fee, reserve | Gross revenue and factoring fee expense |
| Fleet fuel cards (Comdata, EFS, WEX, TCH) | No, card network not a bank | One lump draft, if anything | Stop, state, gallons, price per gallon | IFTA gallons by jurisdiction, cost per mile |
| Business checking account | Usually yes | Deposits, insurance, payments | Same lines, full history, no gaps | Backfills and QuickBooks Desktop |
| TMS or ELD app exports | No | Nothing | Per load revenue, miles, accessorials | Revenue per mile by truck |
| Broker direct pay and quick pay | Only the deposit | Net after the quick pay discount | Invoice amount and the discount taken | Real yield on quick pay loads |
Built for the CSV and Excel exports US banks and cards actually send, checked before it exports.
The converter adds up the transactions it parsed and matches that to your file total before you export, so nothing is silently dropped.
Valid OFX 1.02 with QuickBooks Web Connect headers. Online and Desktop import it as a standard bank feed.
Date, description, and amount are detected for you, so you skip QuickBooks' strict 3-column and 4-column CSV layout.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Mixed date formats, currency symbols, and stray commas that break a raw CSV import are cleaned up before the .qbo is built.
One conversion, three files: the .qbo for QuickBooks, an XLSX to review, and a CSV for everything else.
Three steps. No column-mapping wizard.
Drag in a CSV, XLS, or XLSX export from your bank, credit card, or accounting tool. Any column order is fine.
Every transaction is parsed and checked against your file total. You see the rows before exporting.
Download the .qbo and import it as a Web Connect bank feed. Excel and CSV are in the same download.
The specifics that decide whether the import is clean. If your case is not here, message us in chat.
Invoice the broker for the full load amount so gross revenue is correct, then record the factor's deposit against that invoice rather than as new income. The gap between the invoice and the deposit is the factoring fee, posted to an expense account. If the factor holds a reserve and releases it later, that release is a second payment against the same invoice, not additional revenue.
Because the deposit is net. The factor advances a percentage of the invoice, deducts its fee, and often nets out fuel advances, insurance installments or prior chargebacks before wiring the balance. One deposit also frequently covers several loads. The settlement report is the only document that breaks it back apart, which is why importing that file matters more than categorizing the deposit.
No. Fleet fuel cards from Comdata, EFS, WEX and TCH are issued through card networks rather than through a bank, so there is nothing for QuickBooks bank feeds to connect to. The supported route is to download the card's transaction export as CSV or Excel and import it. Converting that export to .qbo brings every fuel stop in as its own dated line.
Import the fuel card CSV rather than the bank line, because the card export carries the purchase state and the gallons on every stop. Once those lines are in QuickBooks you can tag them by state using classes or locations, then total gallons per jurisdiction for the quarterly IFTA return. The bank feed shows one combined draft with no state detail at all.
No. QuickBooks Desktop cannot import a bank or credit card CSV in any version or year, including Pro, Premier and Enterprise. Its only banking import is a .qbo Web Connect file, loaded through Banking, then Bank Feeds, then Import Web Connect File. That single limitation is why converting is the standard route for trucking companies still running Desktop.
Keep one business checking account, one fuel card, and a factoring relationship if you use one, then import all three into QuickBooks as separate registers rather than reconstructing them from the bank. Track each truck as a class so you can see revenue and cost per unit. The goal is that every dollar of revenue and every gallon of fuel has its own line, not a monthly summary.
You need complete cost detail and a mileage figure from the same period. Import the fuel card, maintenance, insurance and settlement files so the expense side is real, then divide total operating cost by the miles from your ELD or TMS export for that period. The number is only as honest as the import: a missing fuel card file understates cost per mile immediately.
Yes. File imports have no ninety day limit, so a January to December export goes in as a single .qbo on QuickBooks Desktop. On QuickBooks Online, manual uploads are capped at 350 KB and 1,000 rows, so a busy fleet year usually needs splitting by quarter. Bank feeds only pull about ninety days on a first connect, which is why a backfill has to be a file import.
Not if the date ranges do not overlap. Every transaction in a converted .qbo carries a unique ID, the field QuickBooks checks against activity it has already seen, so a repeated import is normally recognized and skipped. The habit that prevents trouble is importing clean, non overlapping periods per account and reconciling each month before you load the next one.
Direct Connect stops on that date, and Direct Connect bill pay ends with it. Any QuickBooks Desktop account that pulled transactions automatically over Direct Connect goes quiet. Web Connect .qbo imports are not affected and keep working. In practice trucking companies on Desktop move to downloading a file each month, either as .qbo if the bank offers one or by converting the CSV the bank does offer.
Yes. Conversion changes the file format, it does not open a connection, so you never hand over online banking or fuel card credentials and no login token is stored. The tool reads the file you already downloaded and writes a .qbo carrying the same dates, amounts and descriptions. For accounts that have no feed in the first place, that is the only route in.
Not necessarily. Dedicated trucking software adds dispatch, settlements and IFTA reporting, which is worth it once you run several trucks. A single owner operator or a small fleet usually gets there with QuickBooks plus classes per truck, as long as the underlying data is complete. The failure mode is not the software, it is books built from one net deposit a week.
Upload a CSV or Excel export, get a QuickBooks-ready .qbo back in seconds. No card to try it.
Where to go next: fleets that also run supply and equipment accounts should read the CSV to QBO converter for construction page, bookkeepers handling several carriers should start with the CSV to QBO converter for accountants and bookkeepers page, and high volume months are covered on the bulk CSV to QBO converter page. The two edition specific guides are CSV to QuickBooks Online and CSV to QuickBooks Desktop. If the business account sits at a small institution with no QuickBooks feed, see the credit union CSV to QBO converter page. For the Direct Connect deadline see the Direct Connect alternative page, for step by step conversion see how to convert CSV to QBO, for column layout see the QuickBooks CSV import template, and for a full backfill see importing older transactions into QuickBooks.
For the solo bookkeeper running a monthly close in QuickBooks.
USD / month
billed $288 yearly
For a firm or finance team converting across many clients and currencies.
USD / month
billed $888 yearly
For multi-bookkeeper firms managing many client books at scale.
USD / month
billed $2,988 yearly
