Partial invoicing of orders based on completed loads and other new features

In this article, you will learn about the following improvements and new features in the fireTMS system:

Partial invoicing of orders based on completed shipments

We have added the ability to partially invoice orders that are still in progress. Previously, if a single order comprised several shipments, an invoice could only be issued once the entire order had been completed.

Following this change, the system can automatically mark an individual load as completed once all its route points – both loading and unloading – have been assigned the status Completed (either manually by the freight forwarder, via the fireTMS Driver app, or via GBox Assist). Once the load has been completed, the system automatically generates a draft invoice.

If it is necessary to re-mark the load as ‘in progress’, simply change the status of one of its route points to ‘uncompleted’. The system will automatically reverse the completion of the load and delete the previously generated draft invoice.

This option is available under Configuration >> System configuration >> Order handling >> field Automatic completion of a loading after all loading and unloading operations have been completed. By default, the system operates as before, and the feature can be enabled manually in the configuration.

This allows the user to start invoicing a completed load without having to wait for the remaining loads in the same order to be processed, which speeds up settlement and streamlines work with consolidated orders.

Detection of missing current GPS positions and entries in the odometer log

With the new version of the system, we have added a mechanism that automatically detects gaps in vehicle data. This feature allows you to monitor situations where the GPS provider has stopped transmitting the current location of a given vehicle or where no new entries have appeared in the odometer log within a specified time period.

The configuration is available at Configuration >> System configuration >> the Transport configuration tab, in the Detection of vehicle position irregularities. The user can separately enable the detection of missing telematics data and missing entries in the mileage log, specify the number of days without data after which a notification is to be sent, and select the type of notifications: immediate or grouped once a day.

Information on detected irregularities is presented in the fireTMS system in the form of notifications (alerts – sent to users with administrator roles) and corresponding markers on the vehicle list. In the new column on the vehicle list Vehicle position, the user can check the data status, the date of the last position, the vehicle’s location, the address and the odometer reading retrieved from the telematics system (provided that the telematics system returns this information). A preview of the vehicle’s position details on the map is also available from this level.

The solution helps to detect problems with GPS integrations and gaps in vehicle mileage records more quickly, increasing control over the fleet and the accuracy of the data used for transport planning and billing.

Documents from sub-loads visible in the main load

With the new version of the system, we have improved the display of documents for split loads. Previously, scans of documents sent from the fireTMS Driver app were assigned exclusively to the specific sub-load being carried out, i.e. the part of the load resulting from its division. As a result, documents relating to the transport operation were not visible in the main load, even though they concerned the entire order.

Following the change, documents assigned to sub-loads are also accessible from the main load in the sub-load documents section. This makes it easier for the user to locate the complete set of transport-related documentation without having to view each sub-load separately.

This change improves the transparency of working with split loads and facilitates subsequent processes related to the settlement and invoicing of transports, where access to full documentation is crucial.

fireTMS API: adding costs

We have expanded the fireTMS API (documentation) with a new endpoint enabling the addition of costs to a vehicle, driver or trailer. The endpoint supports both standard operating costs and fuel costs, and the scope of the data transferred corresponds to the fields available in the cost registration form within the system.

This enables external systems to automatically transfer information about incurred costs without the need to manually enter data into fireTMS. This change enhances the system’s integration capabilities and supports the automation of processes related to transport cost settlement.

Corrections to corrections calculated based on the most recent correction

We have streamlined the way correction documents issued for previous corrections are calculated. From now on, when creating a correction to a correction, the system uses data from the most recently issued correction, rather than the values from the original invoice.

As a result, subsequent corrections reflect the current status of the document and are calculated in a more intuitive way, which reduces the risk of errors during multi-stage invoice corrections.

GPS Fleet Monitor Integration

We have expanded the list of supported telematics systems to include integration with GPS Fleet Monitor. Thanks to this new integration, fireTMS can automatically retrieve vehicle location data, enabling real-time fleet monitoring directly within the system.

This integration reduces the need to manually check data in external GPS systems, provides faster access to vehicle location information, and supports more efficient transport planning and execution.

Would you like to find out more about these new system features? Please contact us.

* Some of the features described are available only in selected plans.