WEX fuel-card export to QuickBooks, without the cleanup
A WEX CSV has every fuel transaction you need — in a schema QuickBooks won't recognize. Here's how to get from that export to a clean, importable file without re-keying a single row.
To get a WEX fuel-card export into QuickBooks, you export the transaction CSV from the WEX portal, normalize its columns to a standard ledger, GL-code each row, and import the result into QuickBooks or Xero. Done by hand that means hours of column-matching and re-keying. Fuel Ledger does the normalizing for you: drop in the WEX CSV (or a Shell or Fuelman one — the format is auto-detected), and it returns a clean, GL-coded file ready to import, no manual cleanup required.
Why a WEX CSV won't import into QuickBooks cleanly
WEX gives you a perfectly good transaction export — it just doesn't speak QuickBooks. Drop it into a generic importer and you hit the same wall every month:
- The column schema is WEX's, not QuickBooks'. Names, order and date formats don't line up with what an accounting import expects, so the importer either rejects the file or maps fields wrong.
- Rows aren't GL-coded. Each fuel purchase needs an account/GL code before it's anything QuickBooks can post, and the raw export has none.
- Nothing's matched to a vehicle. If you track fuel per truck, you still have to tie every card number to a unit before the data is useful.
So most back offices end up hand-cleaning the file in a spreadsheet, then re-keying — and Shell and Fuelman exports each have their own different layout, so the work resets with every card.
The manual route, step by step
Without a normalizer, getting one WEX export into QuickBooks looks like this:
- Export the CSV from the WEX online account for the period you're reconciling.
- Rename and reorder columns to match your QuickBooks import template, and fix the date format.
- Match each row to a vehicle by card number, by hand.
- Assign a GL code to every transaction.
- Scan for bad rows — duplicate fills, over-tank-capacity amounts, after-hours buys — and correct them.
- Import the cleaned file, then fix whatever QuickBooks still rejects.
It works, but it's the line-by-line grind that eats days a month — and you repeat most of it for every other card you carry.
The Fuel Ledger route: drop, normalize, export
A provider-agnostic normalizer collapses that list into three steps that work the same for WEX, Shell or Fuelman:
- Drop in the export. Upload the raw CSV straight from the WEX portal — or a Shell or Fuelman one. Fuel Ledger auto-detects the schema, so there's no template to fill in and no fixed columns to match.
- Let it normalize and match. Every transaction is normalized to one standard ledger, GL-coded, matched to a vehicle, and screened for anomalies like over-tank-capacity fills and after-hours buys.
- Export the clean file. Out comes a QuickBooks- or Xero-ready file you import directly — no re-keying transaction by transaction.
By hand vs. with Fuel Ledger
| By hand | Fuel Ledger | |
|---|---|---|
| Map WEX columns | Manual per export | Auto-detected |
| Shell / Fuelman too | Different layout each time | Same flow, auto-detected |
| GL-code each row | By hand | Automatic |
| Match fuel to a vehicle | Look up by card number | Automatic |
| Catch bad rows | Hope you spot them | Anomalies flagged |
| QuickBooks / Xero import | Re-key & fix rejects | Clean file, imports directly |
Why no card or accounting tool builds this for you
It would be convenient if WEX exported a QuickBooks-ready file, or if QuickBooks read WEX's CSV natively — but neither is motivated to. Card issuers want you working inside their portal, and accounting tools expect data already in their shape. The neutral middle layer — a normalizer that reads any card's CSV and outputs to any accounting tool — is exactly the piece nobody on either side will build. That's the gap Fuel Ledger fills: no hardware, no lock-in, just whatever CSV you have turned into data QuickBooks or Xero will accept.
From WEX export to a clean QuickBooks file
Drop in a WEX, Shell or Fuelman CSV and get back a GL-coded, QuickBooks/Xero-ready file — vehicles matched, anomalies flagged, no re-keying. Free to try.
Enter your email to try the free CSV cleaner
Works with any fuel card and any accounting tool. No hardware required.
FAQ
Can I import a WEX fuel-card CSV into QuickBooks directly?
Not cleanly — WEX's column schema, date format and lack of GL codes mean a direct import gets rejected or mismapped. Fuel Ledger normalizes the WEX export into a GL-coded file that imports into QuickBooks or Xero without manual cleanup.
Does it work with Shell and Fuelman cards too?
Yes. Fuel Ledger auto-detects the CSV schema rather than relying on a fixed template, so WEX, Shell, Fuelman and other cards all run through the same flow and produce the same clean, accounting-ready output.
Will the export match my fuel to each vehicle?
Yes — each transaction is matched to a vehicle, GL-coded, and screened for anomalies like over-tank-capacity fills, so the file you import into QuickBooks or Xero is already reconciled per truck.