CALSF

The Ampol Star Fleet interface (CALSF) imports non-fuel transactions (e.g. servicing, tyres etc).

The Interface Code reflects the previous name of Ampol, which was Caltex.

The interface files CALNP or CALNS include all transactions. However, the non-fuel transactions need to be excluded and imported using the CALSF interface in order to obtain enough detail of the work carried out.

These transactions are filtered out by excluding the specific product codes 'STARFLEET', 'S/FLEET' and 'S/FLEET P', 'FLEETCRDP' and 'FLEETCARD' when the data files are imported.
This means you need to run two imports to bring in all Star Fleet transactions into Catch-e: one for fuel and one for maintenance.

The product codes 'FLEETCRDP' and 'FLEETCARD' were introduced when Ampol changed it's name from Caltex.

Warning: Ampol often supplies this file as an .xls format. Ask Ampol to provide you with a .csv file instead.

Note: If the file is opened in excel and then saved, the program may convert the last digit of the card number to a zero due to the field length (this renders the field unreadable). If you want to review the file, we suggest you do this in Notepad or Wordpad.

File Columns and Mappings

No

Column Name

0

AMPOLREFNO

1

CARD_NO

2

AUTHORISATION_NO

3

CUSTOMER_NO

4

REGISTRATION_NO

5

SUPPLIER_NAME

6

TRANSACTION_DATE

7

ODO

8

MAINTENANCEGROUPCODE

9

MAINTENANCE_GROUP

10

MAINTENANCETYPECODE

11

MAINTENANCE_TYPE

12

MAINTENANCEACTIONCODE

13

MAINTENANCE_ACTION

14

MAINTENANCECAUSECODE

15

MAINTENANCE_CAUSE

16

SUPPLIERINVOICENO

17

PART_COST

18

LABOUR_COST

19

OTHER_COST

20

TOTAL_COST

21

GSTLINEITEM

The interface uses data in the first 22 columns of the file used to upload. If the file contains 24 columns the interface will ignore any data appearing after the 22 mentioned above e.g. GST is the last column used by the interface.

Should an attempt be made to import a file containing anything other than 22 or 24 columns the import process will fail with an on screen warning produced.

The interface ignores the header on import.

Troubleshooting

Error Message

Notes

"The Invoice Date is invalid! Please check you are importing the correct file!"

There may be a blank row at the end of the file. Please remove any blank rows and try to import the file again.

Custom Fleet

Custom Fleet transaction file interface is used for importing all Custom Fleet transactions.

Import Details

The required file is in .txt format. Only the transaction rows are imported (these are indicated by a '30' and '40' as the row type).

The file may be imported as either a zipped or text file.

Refer to the Customfleet User Manual for details on the Customfleet Standard Client Transaction File .

Below are the mappings used where row type = '30' and '40'.

File Columns and Mappings

  • A Row Type — Only imported where Row Type = '30' and '40' and relates to contract vehicle data e.g. 'rental' for product type in column 'K'

B Invoice Number

  • C Reference Number — For Column 'C' the Catch-e import process ignores the backslash and any value to the right of it from the reference number. The backslash and value to the right should be left in the import file. See the sample file below

E

  • F Transaction Date — Transaction date from column 'F' can be formatted as either dd/mm/yy or dd/mm/yyyy in the txt file.

K Product Type

  • L Product Description — Description field in fmfuel and fmmaintenance - use VMRS description followed by column 'L'.

Sample file

On the Fleet / Controls / Interfaces / Card Services/Interfaces screen it is recommended that the field "Description Import Type" is set to "Suffix" to allow the short VMRS code description to be set before the Custom Fleet description to give a meaningful description. Refer to the Catch-e demonstration system for examples of mappings.

Note: Custom Fleet sold the Fleet Card business in 2015/2016. Fleet Card issue an almost identical file to this one. If your file was generated by the Fleet Card entity please use the FLEETA Interface.

Fleet Card

Fleet Card offers two interfaces.

  1. This one is FLEETA and it imports all transactions.

  2. The other one, FLEETO, excludes Lease rental transactions.

Import Details

The required file is in .txt format.

The file may be imported as either a zipped or text file.

File Columns and Mappings Row Type 3

No

Name

Comments

A

Row Type

Row 3 records are used to identify the Card Number in use. It is a Card Header. See sample file illustration below.

B

Invoice Number

D

Reg No

F

Driver Name

M

Card Number

N

Card Type

P

Fuel Type

Q

Vehicle Make

S

Card Amount Net

T

Card Amount GST

V

Card Amount Total

X

Card Quantity Total

File Columns and Mappings Row Type 4

No

Name

Comments

A

Row Type

Only row type '4' records are imported. The Card Number is identified in row type '3'. See sample file illustration below.

B

Invoice Number

C

D

Reg No

E

F

Transaction Date

Transaction date from column 'F' can be formatted as either dd/mm/yy or dd/mm/yyyy in the txt file.

G

Product Class

H

Transaction Number

I

Merchant Name

J

K

Product Type

Ignored

L

Product Description

Description field in fmfuel and fmmaintenance - use VMRS description followed by column 'L' description (as indicated below).

M

Quantity

N

Odometer

O

P

Amount Net

Q

Amount GST

R

S

Amount Total

Sample file

On the Fleet / Controls / Interfaces / Card Services/Interfaces screen it is recommended that the field "Description Import Type" is set to "Ignore" to give a meaningful description.

Note: Custom Fleet sold the Fleet Card business in 2015/2016. Interface was formerly named CUSTA and has been renamed to better reflect the feature.