Workshop & operations

Fuel card import

Read the file, check the matching, commit. Hundreds of statement rows become refuellings on the right vehicle — without copy-and-paste from PDF annexes.

Formats Provider parsers · generic CSV
Matching By card number
Safety Dry run before commit
Result Refuellings in fuel management

Nobody retypes the fuel card statement any more

The module ships parsers for common fuel card providers and additionally reads generic CSV files. Cards are mapped to vehicles once; after that the import matches automatically. Anything ambiguous stays open and is resolved by hand — nothing is silently guessed.

What it does

What the module actually does

Provider parsers and generic CSV

Shipped parsers for widespread fuel card providers, plus a generic CSV import for everything else.

Card mapping

Card numbers are mapped to vehicles once; every later import reuses that mapping.

Dry run before commit

The import first shows the result: recognized, matched and open rows — commit happens only on confirmation.

Resolve open rows manually

Unmatched rows can be assigned to a vehicle individually instead of discarding the whole import.

Normalize fuel types

Provider labels such as 'Diesel B7', 'E10' or 'electric' are mapped onto your fuel types.

Import history

Every import run stays traceable with file, timestamp and result.

Workflow

Import run

  1. 01 Read file
  2. 02 Dry run
  3. 03 Resolve open rows
  4. 04 Commit

Frequently asked questions

Then you use the generic CSV import. Because the software runs on your infrastructure, additional provider-specific parsers can be added as part of a customization project.

The import runs in two stages: first a dry run that only analyses, then a deliberate commit. Rows without an unambiguous match are not guessed — they are reported as open.

Committed rows become refuellings in fuel management — with vehicle, volume, price and fuel type. From there they feed consumption analytics and the Fleet Cost Cockpit.

See this module with your own data

30 minutes, no sales pressure: we show the module in the context of your fleet — self-hosted in your data centre, GDPR-compliant, made in Germany.