Cover Picture

Fuel - Process EFI

The process routine takes the loaded EFI data and updates the data in RTA—just as if the fuel tickets had been entered into the RTA system manually. The difference is that instead of taking a few hours, hundreds of transactions can be processed in only a few minutes! As long as there are no problems with the transactions processed, the vehicle meter reading, fuel usage, and fuel cost will be updated.

This is the last time that a user will be able to update or delete transactions from the load before they affect data in real time.

Open the screen

  1. Select Fuel > Process EFI from the side bar. The app bar reads Review/Process EFI. The screen also opens by itself after you load a file and review exceptions in one pass.

  2. The grid opens on Unprocessed transactions. Use the toggle above the grid to show Processed or All instead.

Processing and deleting need the EFI edit permission. With view-only EFI access you can filter, review and export, but Process and Delete unprocessed transactions are disabled.

Choose the date scope

The FILTER BY button above the grid sets the date scope. The line beside it, Showing:, tells you the current one.

OptionWhat it shows
Since Last ProcessedTransactions dated from the last processed date up to today. This is the default.
Date Range (Select Dates)Transactions between two dates you pick.
All TimeEvery transaction on file.

The date scope applies to the grid, to Process, and to Delete unprocessed transactions.

Find what needs attention

Two chips sit beside the toggle. They appear only when the grid has transactions of that kind:

  • Errors (n) — transactions with an error-level exception or a process error.

  • Warnings (n) — transactions with a warning-level exception.

Select a chip to show only those transactions; select it again to clear it. You can turn both on at once. The count on each chip is taken across the whole set, before the chips themselves narrow it, so it does not change when you select the other chip.

When the exception indicators are enabled for your company, a warning or error icon also appears beside the affected value in the row — the asset, the odometer or the quantity. Hover over it to read the exception.

Read the totals

The bar at the right of the controls shows Transactions, Qty and Cost for everything the grid is currently showing. The totals cover the full filtered set, not only the rows that have scrolled into view, and they update when you change the toggle, a chip, the date scope or any column filter.

Show the current fuel meter

The grid has a Current Fuel Meter column that is hidden by default. It shows the asset's fuel meter reading as it stands now, so you can compare it with the Odometer the fuel system sent before you process. Open the column chooser from the toolbar menu and switch the column on. It is read-only.

Export what you are looking at

Select the toolbar menu in the top right and choose Export To Spreadsheet or Export To PDF. The export contains the rows the grid is showing — the same toggle, chips, date scope and column filters apply. Export To Spreadsheet is available when spreadsheet exports are enabled for your company.

Process the transactions

  1. Select Process.

  2. Read the prompt. It names how many transactions will be posted:

  • With no warnings or errors in the set: "You are about to process n fuel transactions. This will post odometers, fuel costs, and quantities to the assets listed."

  • With warnings or errors in the set: "You are about to process n fuel transactions, including e with errors and w with warnings. This will post odometers, fuel costs, and quantities to the assets listed." Clear the exceptions first if you do not want them posted; see Fuel - EFI Review Exceptions.

  1. Optional: tick Include Assets Not Found to post transactions whose asset Fleet360 could not match. Use this when you track fuel for assets you do not maintain in Fleet360.

  2. Select Process to confirm. A progress bar runs while the transactions post. When it finishes, the prompt reports how many were processed, how many were processed with errors, and how many were not processed. Select Continue.

What Process includes. Process posts every unprocessed transaction inside the date scope and your column filters. It does not follow the Unprocessed/Processed/All toggle or the Errors/Warnings chips: narrowing the grid to errors does not narrow what is processed. The count in the prompt is the count that will be posted — check it before you confirm.

Delete unprocessed transactions

Use this to discard transactions that should never post, for example a file loaded twice or a batch of rows with the wrong asset numbers.

  1. Narrow the grid to the transactions you want to remove. Unlike Process, Delete does follow the Errors and Warnings chips as well as the date scope and column filters.

  2. Select Delete unprocessed transactions.

  3. The prompt reads "You are about to delete all unprocessed transactions based on your filters." Select Delete to confirm.

Only unprocessed transactions are deleted; processed rows are never touched. If nothing matches your filters, nothing is deleted. To remove a single transaction, use the Delete button in its row instead.

Once the EFI transactions are processed, be sure to review them for any process errors.

Read the chart below to view the errors

Message

What it means

What to do

Vehicle Not Found

The Vehicle Number or Card Number coming from the Fuel System Does not match an RTA Asset Number or Cross Reference Number

Three General Fixes:

  • Vehicle has not been Officially Added (Fix: simply add the new record)

  • There is no Cross Reference added to the Vehicle Record if using Cross Reference (Fix: Add the Cross reference in to the Asset file)

  • Vehicle has been Moved to another facility (Fix: move the Vehicle Back or Update the Cross Reference for New Facility)

Inconsistent Fuel Type

The Fuel Transaction Fuel Type Does not match the Primary Fuel Type set in the Asset Record

If you did not initially set the Fuel Type in the Asset File then set it. See Setting the Fuel Type from the Fluids Panel in the Asset File

Fuel quantity greater than tank capacity

The Fuel Transaction has a greater fuel quantity then the Vehicle can physically hold (Tank Size)

If the Asset did not have a tank capacity setup initially you will want to do this first. See Setting the Tank Capacity from the Fluids Panel in the Asset File

OR There may be truly be an issue with the Fuel Transaction

Meter exceeds allowable mileage limit

The Miles/Hours/Kilometers traveled for the Fuel Transaction Exceeds the “Maximum” Factor (Typically set behind the scenes to 3X) based on the Expected Average MPG Set in the Asset File

First if the Asset was not set with a suggested Average MPG then you will want to make sure you have a good number in each Asset Record. Setting the Average MPG from the Fluids Panel in the Asset File

This also may reflect an odometer issue in the Fuel Transaction itself or an Odometer issue in the Asset File

Mileage high for average mileage

The Miles/Hours/Kilometers traveled for the Fuel Transaction Exceeds the “High” Mileage Factor (Typically set behind the scenes to 1.5X) based on the Expected Average MPG Set in the Asset File

First if the Asset was not set with a suggested Average MPG then you will want to make sure you have a good number in each Asset Record. Setting the Average MPG from the Fluids Panel in the Asset File

This also may reflect an odometer issue in the Fuel Transaction itself

Mileage Low for average mileage

The Miles/Hours/Kilometers Odometer Reading coming in from the Fuel Transaction is less then the current Fuel Meter Reading in the Asset File.

This is usually indicative of a Fuel File loaded out of sequence. For Example Loading Wednesday Fuel file before loading Monday’s of the same week. The Wednesday readings have already updated. Thus pulling Mondays fuel at lower readings would throw these exceptions.

OR again is could be an Odometer issue either in the Asset File or the Fuel Transaction File