User Guide
0 mins to read
Fuel Transaction Import Add-In User Guide
User Guide
0 mins to read
Learn more about the Fuel Transaction Import Add-In, which allows users to import Fill-up transactions extracted by the fuel provider’s application/service into MyGeotab. This document demonstrates how to import transactions using three different options: WEX, General Standard, and Import Fuel Provider.
For All 4.x.x Add-In Versions
May 2023
Revision history
Version | Date | Change |
1.0.0 | 2022-12-30 | First release for this version. |
1.0.1 | 2023-03-09 | Configuration file section improvements. Importing fuel transaction steps improvements. |
1.0.2 | 2023-04-27 | Added The Add-In and the How to access it sections Made some general improvements |
2.0 | 2023-05-05 | Updated the document style and updated content to adhere to the style guide. |
2.1 | 2023-09-22 | Made the version 4.1.0 updates like the menu image change and the import image changes. |
2.2 | 2024-02-27 | Added the FAQ section. |
The Fuel Transaction Import Add-In allows users to import fuel fill-up transactions supplied by a fuel card provider into a MyGeotab database.
To install the Fuel Transaction Import Add-In, go to MyGeotab, then follow the steps below:
{ "url": "https://app.geotab.com/addins/geotab/addin-fuel-transaction-import/manifest.json" }
To access the Add-In, select Engine & Maintenance > Fuel Transaction Import from the MyGeotab main menu.
The configuration file is the column mapping and configuration information required to execute a successful fuel transaction import operation.
See the GitHub configuration file repository to understand the configuration file structure, its properties, and how to correctly compile it in order to successfully import fuel transaction data into the MyGeotab database system.
The configuration file must contain the column mapping and configuration to be expected in the import process and describes the Excel import file.
An example configuration file and some formatting instructions can be found in the git repo, for example, source.json.
The data JSON object in the configuration file contains the Fuel Transaction entity property fields to be imported and their column references.
The Excel import file is an Excel spreadsheet (XLS, XLSX) file supplied by a fuel card provider (or a custom file produced through some other mechanism) containing the fuel fill-up transaction data to be imported.
Some context for the Excel import file includes:
✱ NOTE: The first row is skipped as it is assumed to be a header row.
✱ NOTE: The Maximum number of transactions that will be imported per import file is 5000, so truncate your import files where necessary to below this threshold in order to succeed.
Note |
|
There are some prerequisites for importing fuel transactions. These include:
✱ NOTE: If a device does not have any of the identification references, the record will still be imported, but it will be orphaned and will not have the possibility of matching an actual fill-up event.
Follow these steps to import the fuel transaction files (refer to the image that follows).
✱ NOTE: The imported transactions will not reflect in the fuel fill-ups page report immediately. There is a post-processing action required that performs the physical matching of these transactions to the fill-ups at a later stage. Generally, the matched transactions will display the following day.
Imported fuel transactions are processed at the end of each day, and are not reflected in the database immediately. A delay of up to 24 hours should be assumed.
The Reference Time Zone field allows you to select a time zone other than the current local time zone. In other words, you can import fuel transactions for other time zones or for different time periods, such as importing transactions that occurred during daylight savings time.