What is the ABAX integration?

What is the ABAX integration?

The ABAX integration connects Telaris to ABAX's cloud-based driving log. Business trips are imported automatically and made available as order lines, so that mileage allowance and related expenses (parking, tolls, ferry) can be invoiced directly from the order. ABAX registers trips via GPS units in the vehicle. Telaris only retrieves data from ABAX – nothing is sent back, and private trips are not imported.

TABLE OF CONTENTS

• Purpose
• What the module solves
• Functional overview
• Data flow
• Typical workflow
• Interaction with other modules
• Key concepts

Purpose

The goal of the module is that business trips and related expenses come into Telaris automatically and can be added directly to an order for invoicing, without manual reporting. The module covers import of trips, assignment to order lines, and administration of drivers and vehicles.

What the module solves

Without the integration, these challenges typically arise:

• Employees must report trips and expenses manually – time-consuming and error-prone.
• Mileage allowance is invoiced late or forgotten because the data is not in the order system.
• Difficult to document business trips for tax and internal control.
• No systematic link between vehicle, driver and order.
  
  

The module solves this by:

• automatically importing business trips from ABAX with departure, arrival, distance and duration
• collecting related expenses (parking, tolls, ferry) per trip
• letting the order handler add trips directly as order lines with one click from the driving log tab
• linking vehicles (via tags) and drivers (via personnel) to trips and orders
• giving an overview of all available trips directly in the order editor

Functional overview

Data flow

Trips (business trips), expenses, driver overview and vehicle overview go from ABAX to Telaris. Telaris sends no data back to ABAX.

NOTE: Responsibility for privacy of GPS and driving data lies with the customer, not with Telaris. See the setup article for how consent is handled.

Typical workflow

1. ABAX registers trips automatically via the GPS unit in the vehicle.
2. Telaris imports business trips from ABAX (automatically every hour, or manually when the driving log tab is opened). Private trips are skipped.
3. The order handler opens an order and goes to the Driving log tab.
4. Available trips are shown with details (vehicle, driver, route, distance, expenses).
5. The order handler clicks «Add to the order» to create order lines.
6. The trip can then be marked as completed or removed from the list.

Interaction with other modules

• Order: the driving log tab is part of the order editor. Trips become order lines and follow the standard order flow and invoicing.
• Personnel: drivers in ABAX are linked to personnel in Telaris. Drivers without a link do not get trips imported.
• Tags: vehicles in ABAX are linked to tags in Telaris via registration number. The tag is linked automatically to the order when a trip is added.
• Products: two products are configured – one for mileage (price per km) and one for expenses.

Key concepts