Search

EFI Autoload emails and reports

When a fuel module is set to autoload, Fleet360 collects your provider's files by SFTP on the schedule you set, loads each file, processes the transactions and emails the result. This page describes that email and the two reports it can attach. For the schedule and Run now, see Fuel - EFI Module Settings (new 26.11 page - link once published).

Autoload emails are available only when autoload is enabled for your company. The email described here is the 26.11 format; see EFIQ-003.

The completion email

One email is sent per file, to the user who set up the autoload.

Part	What it contains
Subject	\<Module> Load & Process Report — the fuel module's name, so you know which feed ran.
Opening line	"Your EFI autoload for \<Module> has completed."
Load totals	Rows in file · Transactions added · Total rejected · Total quantity accepted · Total cost accepted
Process totals	Transactions processed · Transactions not processed · Total quantity processed · Total cost processed
Attachment notice	"Detailed load and process reports are attached to this email." — shown only when at least one report is attached.
View Process	A link that opens Fuel > Process EFI for the module's facility.

Quantity and cost totals are summed from the transactions the file produced; a value that cannot be computed shows as 0.

Manual loads from Fuel > Load EFI are not covered by this email. They keep their own load notification.

The two reports

A report is attached only when it has something to list. A clean run — every row loaded, every transaction processed — arrives with no attachments.

Report	Attached when	Each row is
Load Report	The load rejected rows, or a loaded transaction carries an exception (error or warning)	A row the load rejected — duplicate, zero quantity, bad format — or a loaded transaction with an exception, with the reason
Process Report	One or more transactions did not process	A transaction that is still unprocessed after the run, with the reason it did not post

File names: <Module>_Load_Report_<YYYY-MM-DD>_<HH-mm>.csv and <Module>_Process_Report_<YYYY-MM-DD>_<HH-mm>.csv. Characters in the module name other than letters, digits, dot, underscore and hyphen are replaced with an underscore.

Report layout

Both files use the same layout. The first block repeats the email's totals for that phase as Metric, Value pairs. After a blank line, the detail rows follow with these columns:

Column	What it holds
Date	The transaction date from the file
Facility	The facility the transaction belongs to
Vehicle	The asset number the file carried, or the asset Fleet360 matched
Odometer	The meter reading from the file
Quantity	The fuel quantity from the file
Price	The unit price from the file
Pump number	The pump, when the file carries one
Fuel Type	The product or tank type
Driver card	The driver card number, when the file carries one
Warning/Error/Reject message	Why the row was rejected, flagged or not processed — the same text as the Rejected Transactions grid, the exception, or the Process Error column

Use the last column to fix the cause in bulk: add the missing cross references, correct the asset numbers, or clear the exceptions in Review Exceptions, then let the next run — or Run now — pick the transactions up.

A cell that begins with =, +, - or @ is prefixed with an apostrophe so that a spreadsheet treats it as text.

Runs and file limits

Each run takes at most 10 files from the SFTP folder, oldest first; the remainder wait for the next run. Each file gets its own email.

Related tasks

Fuel - EFI Review Exceptions — clearing the exceptions the Load Report lists
Fuel - Process EFI — the screen View Process opens, and the Process Error reasons