Fuel Ledger

For owner-operators & small-carrier back offices

Any fuel-card CSV in, an IFTA-ready ledger out.

Drag in a CSV from WEX, Shell, Fuelman or any other card. Fuel Ledger auto-detects the format, normalizes it to one clean ledger, matches each transaction to a vehicle and IFTA jurisdiction, flags the odd ones, and exports a QuickBooks/Xero file plus an IFTA-formatted summary.

No telematics hardware. No platform. Just a smart CSV transformer.

Every month, the same line-by-line spreadsheet grind

  • Each card provider exports a different CSV schema, so generic importers choke and you end up matching transactions by hand.
  • You match every fuel transaction to a vehicle, driver, odometer, GL code and IFTA jurisdiction before anything can be keyed into QuickBooks or the IFTA return.
  • One finance manager reported spending 3 days a month reconciling 4,200 transactions across 65 vehicles.
  • The 2024 IFTA rules now require distance records in CSV/XLS — no PDFs — raising the bar on clean, structured data.

How it works

Messy CSV in, clean data out

1

Drop in any fuel-card CSV

Upload an export from WEX, Shell, Fuelman or any other card. Fuel Ledger auto-detects the provider's schema — no template-wrangling, no fixed columns.

2

Normalize, match, flag

Every transaction is normalized to one standard ledger, matched to a vehicle and IFTA jurisdiction, and screened for anomalies — over-tank-capacity fills, after-hours buys, wrong-jurisdiction entries.

3

Export ready to file

Out comes a QuickBooks- or Xero-ready file and an IFTA-formatted quarterly summary — structured the way the 2024 rules expect, ready to import or file.

Why no card issuer or platform will build this

Fuel-card issuers want you locked inside their portal, and fleet platforms only ingest fuel data if you're already paying for telematics. A neutral, provider-agnostic normalizer that works with any card and any accounting tool is exactly what none of them is motivated to build. Fuel Ledger has no hardware and no lock-in — it just turns whatever CSV you have into data you can actually file.

Questions carriers ask

Which fuel cards does it work with?

Any of them. Fuel Ledger auto-detects the CSV schema from WEX, Shell, Fuelman and others rather than relying on a fixed template, so a card we haven't seen before still normalizes cleanly. Tell us about an odd format and we'll tune the detector.

Does it handle IFTA jurisdictions?

Yes. Transactions are matched to IFTA jurisdictions and rolled up into an IFTA-formatted summary covering the 48 US states and 10 Canadian provinces — exported as CSV/XLS, the format the 2024 rules require.

Can it match fuel to my mileage?

Yes — optionally cross-reference a GPS or distance export so each fill lines up with the right vehicle and jurisdiction, and anomalies like over-tank-capacity fills get flagged.

Does it work with QuickBooks and Xero?

It exports a clean, GL-coded file ready to import into QuickBooks or Xero — no manual re-keying transaction by transaction.

What does it cost?

The CSV cleaner is free to try. The IFTA-ready export and accounting sync are a low-cost upgrade. Enter your email to start and see current pricing.