Skip to content
Company vehicle in Cyprus.

Fuel monitoring for Cyprus fleets

Know which fuel numbers come from transactions, which are estimates and which need a person to review them.

Start with the source of each litre

A fuel purchase has a date, litres, spend and an assigned vehicle or driver. Fleet can import fuel-card CSV statements with column mapping and a preview of duplicates and errors. Managers can review entries and correct or reject them. That creates an auditable transaction record, but it is not a live tank gauge. The FTC164 does not report a fuel level. A report saying “fuel monitoring” should tell the reader whether a figure came from a card statement, an entered transaction, a calculated rate or a physical sensor. Those sources answer different questions.

Begin by checking your card provider’s export. Are plate numbers consistent? Does the file contain litres and total spend? How are refunds and duplicate rows represented? Import a small file and resolve unmatched vehicles before importing a full period. A wrong plate can distort consumption for two vehicles at once. Keep the original statement available for review and do not silently correct an unusual total. Fleet surfaces import errors and duplicate candidates so a person can decide what the source record means.

Use trips as context, not as a substitute for receipts

The vehicle page can place fuel purchases beside kilometres, trips and idling hours for a selected period. A difference from a vehicle’s usual pattern may be worth checking, but it is not by itself evidence of misuse. A delivery van with a week of city stops will have a different pattern from the same van on a long open-road trip. Vehicle maintenance, load, route and incomplete transaction data also matter. Ask the reviewer to inspect the original entry, the vehicle and the period before changing a record or raising a concern.

Fleet can estimate fuel used while idling when an idle-burn rate in litres per hour is set for the vehicle. The estimate is a multiplication of a configured rate by measured idling hours, not fuel drawn from the tank. Label it as an estimate and revisit the rate when the vehicle changes. If there is no defensible rate, leave the estimate unset rather than inventing a number. The same discipline applies to cost per kilometre and consumption: they are meaningful only when the transactions and distance cover the same period and vehicle.

  1. 07:52Clocked inDepot, Latsia
  2. 08:06Trip startedKXA 482 · linked driver
  3. 09:01ArrivedSite, Limassol
  4. 09:03Attendance recordStaff hours recorded separately
  5. 11:40Fuel record41.60 L · EUR 59.49 · website
  6. 16:40Clocked outDepot, Latsia
Staff hours
8 h 48
Driven
162 km
Fuel
EUR 59.49
Alerts
0

Build a review routine

Decide who imports statements, who resolves unmatched vehicles and who approves corrections. Keep the source file and note the reason for each change. Review high fills against tank capacity as a prompt to inspect, not an automatic fraud decision. A vehicle may have a wrong configured tank size or a record may have a data-entry error. The Fleet dashboard flags unusual totals and fill patterns for this reason. Record the outcome so the same issue is not rediscovered at each monthly review.

When comparing providers, ask to see a real import with a malformed row, a duplicate and a plate that does not match. A polished chart fed by perfect sample data says little about the work finance must actually perform. Ask whether fuel cards, driver-paid purchases and receipts are all in the delivered workflow or only in a roadmap. Fleet supports the web import and review flow; a driver phone fuel screen is not part of the current release and is not promised here.

Prepare a card statement before the first import

Ask the card provider for a sample export that includes the fields the finance team actually receives. List the date and time format, plate reference, litres, unit price, total and station identifier if available. Identify which columns are essential and which can be blank. Then map a small sample into Fleet, preview the rows and inspect the duplicate and error list. A good import process refuses to guess a vehicle from a partly matching plate. Resolve that mismatch with the source file or a documented correction, then repeat the import. Keep the original file so the team can trace a number later.

Period boundaries deserve special care. A card transaction dated at the end of a month may be posted in the next statement. A comparison against kilometres should state which period each side covers. Do not silently move a transaction date merely to make a chart look plausible. If a card can serve more than one vehicle, document the actual vehicle for the fill and flag uncertain rows for a person. The aim is a reliable ledger, not a perfect-looking graph.

Investigate flags in a consistent sequence

Fleet can flag a total that does not add up, a fill above configured tank capacity and a vehicle that was not near a station. These are review prompts. First inspect the raw transaction and its vehicle assignment. Next check whether the vehicle catalogue contains the right tank capacity and whether the route period has complete reports. Then ask the driver or card administrator for an explanation if needed. A high fill may be a mistaken tank setting, a unit conversion problem or an incorrect card assignment. Correct only what can be tied to evidence, and retain the original source.

The outcome should be recorded: accepted, corrected with a reason, rejected as duplicate or still unresolved. A manager who sees a flagged item next month should know what was decided before. Avoid labelling a flagged item as theft or misconduct without separate evidence. This is particularly important when fuel data and driver identity meet; a usual-driver assignment is not proof of who bought fuel on a shared vehicle.

Explain the idle-fuel estimate in plain units

The vehicle fuel view uses idling hours for the chosen period. If an idle-burn value in litres per hour is set, the service estimates litres consumed while idling. The arithmetic is straightforward, but the rate is an input chosen for the vehicle, not a measurement from the FTC164. A difference in engine size, load or auxiliary equipment can make a generic rate misleading. Document the source of any chosen rate and leave the field empty when no defensible value exists. A manager should be able to see the hours, the rate and the resulting estimate separately.

Use the estimate to ask a practical question, such as whether extended idle at a depot is worth discussing with the team. Do not convert it to a precise saving promise without measured fuel data. Pair it with trip and stop context, since idling during a service task may have a different explanation from idling in a queue. If the data cannot distinguish those situations, say so in the review.

Ask for the delivered fuel workflow

A purchasing discussion should walk through the actual flow: a statement arrives, a person maps its columns, unmatched rows are resolved, entries are reviewed, and a period report is exported. Ask who can import, edit, approve and export. Ask what a rejected row looks like and whether the original source remains available. If a vendor describes receipt recognition or driver phone entry, ask to see that feature in the version being sold. Fleet has web import and review, while a driver phone fuel screen is not part of the current release.

Request a quote with the card sources and number of vehicles stated. The cost of preparing and reviewing data can matter as much as the tracker price. A system that creates reliable, traceable numbers is more useful than one that silently fills gaps with guesses. Agree how the team will handle missing statements, changed plates and a vehicle sold mid-period before the first monthly close.

A sample month-end review

Start with the card statement and count rows, errors, duplicate candidates and vehicles that could not be matched. Resolve those before looking at a consumption chart. Open one high-spend vehicle and compare transactions with the same period’s distance and idling hours. If the import covers only part of the period, mark the figure incomplete. A month-end close should be able to say which numbers are source transactions, which were corrected by a person and which are estimates.

Next, inspect a flagged fill. Check the source row, plate, configured tank size and any route context. If the total does not add up, preserve the original amount and record why a correction was made. If a fill appears too large, confirm the catalogue data before treating the transaction as suspect. If the vehicle was not near the station, check report gaps and whether another driver used the card. A flag should direct attention; it should never silently overwrite the customer’s record.

End by assigning actions. Finance can correct a mapping, the fleet manager can update vehicle details, and the installer can check reporting gaps. A driver may be asked for context only after the underlying records are inspected. Keep the result with the period so next month does not repeat the same investigation. Request a quote for the actual import and review workflow, including support for the card files you use.

Trace a fuel number back to its source

A driver can enter a purchase and attach a receipt; where the workspace has receipt reading enabled, the server proposes fields from the photo for a person to check. Finance can import fuel-card statements, map columns and review duplicates or unmatched plates. Fleet compares approved purchases with distance and idling for the selected vehicle and period. An idle-fuel figure is an estimate from hours and a configured litres-per-hour rate. None of these numbers is a tank-sensor reading from the FTC164.

The FTC164 has no CAN or OBD fuel feed. Its analog inputs could in principle be wired to a separate sender, but Fleet does not interpret that sender today. A sudden fall in a calculated consumption chart must be checked against missing receipts, a partly imported period, wrong plate matching and gaps in trip data before anyone calls it theft. Preserve the original transaction and mark uncertainty for review.

Sources

  1. Teltonika FTC164 datasheet
  2. Teltonika FTC164 features

Frequently asked questions

Is the fuel figure read from the tank?

No. Fleet uses fuel transactions and card imports; the FTC164 does not report fuel level.

What does an idle-fuel number mean?

It is an estimate from idling hours and the vehicle’s configured idle-burn rate, not a direct measurement.

Should every unusual fill be rejected?

No. Review the source transaction, plate, tank configuration and period before correcting or rejecting it.

Discuss your fleet requirements

Ask for a quote based on your vehicles and operational needs.