REVENUE
Revenue can be filtered and grouped by order and customer
All revenue is reported, including revenue NOT linked to orders, ie: standalone invoices
Charges marked ‘Don’t invoice’ are NOT included in the calculations
Tables Include:
Revenue by collection date (all revenue)
Revenue not linked to orders
Costs not linked to orders (based purchase invoice date)
Profitability by order (based on collection date / inc. rev not linked to orders)
Delivered goods (spaces / metres)
Order details
Totals:
Amount invoice by order status
Top customers by revenue
Top customers by order volume
Inactive customers in last 60 days
💡PRO TIP: Use the filters to gain insight into specific customer revenue and/or order status, over a date range
Summary:
This revenue system tracks all income (order-linked and standalone invoices) except non-billable charges. Data can be filtered by order and customer. Key reports include revenue by collection date, costs, order profitability, delivery metrics, and summaries showing revenue by order status, top customers, and inactive accounts (60+ days). This supports both detailed analysis and strategic insights.
OPERATIONAL
Looks at trip execution, including collections / deliveries / on time reports / Customer volume
Data shown includes:
Number of collections
Number of deliveries
On-time performance (% of on-time vs late stops)
Customer order volume
Distance metrics (total miles by trip or resource)
Summary:
Operational dashboards aggregate and filter logistical activity data (trips, collections, deliveries, resource availability, incidents) for historical and trend analysis, using structured metrics and well-defined filters for detailed operational monitoring.
PROFITABILITY
Profitability is displayed at various levels, including trip, by driver, by resource and order
Calculated as the difference between revenue & cost
Only for revenue lines that have an associated cost
All values shown in base currency for consistency
Table columns with click-through or copy links to source data, including:
Order ID, Status
Customer
Total Revenue / Cost
Profit
Distance
Resources (Driver / Vehicle / Subcontractor)
Summary:
The profitability figure equals revenue minus cost, but only revenue with an associated cost is included in the calculation. This ensures that the margin shown reflects only fully costed revenue, and users should be aware of this when interpreting the reported figures.
DISTANCE
Mileage for trips can be broken down by resources (driver, vehicle, or subcontractor)
Includes Totals and segmented distances (ie: loaded, empty, deadhead miles)
The main source of distance data is the actual driven distance, which can be:
Pulled automatically from onboard computer/FMS integrations (e.g., Trimble, Transics)
Entered manually by users as a “Mileage” field on stops or trips
Estimated using route calculations via mapping providers like HERE Maps or PTV, if actual data is missing.
Distance can also be split per country for reporting, billing, or emissions calculations.
Actual driven distance (not just estimated/theoretical distance) is prioritised where available
Summary:
Distance data is calculated using the best available source: FMS/integrated mileage, manual entry, or mapping-based estimation. The result is used in dashboards at trip, driver, resource, and order level—with support for custom breakdowns, conversions, and accurate cost/emissions calculations.
OVERDUE INVOICES
Looks to the invoice associated to the Order. Broken down by amount, number, & by customer
Calculated by looking at the invoices associated with each order.
Past Due = Invoices that are past their due date (i.e., the current date is later than the invoice due date and the invoice is not yet marked as paid).
Data is broken down by both the number and monetary value of overdue invoices
Can be grouped or filtered by customer for analysis.
Click customer link to redirect to invoices tab filtered for that customer
Summary:
Overdue invoices calculation is primarily driven by comparing the invoice due date with the current date and the payment status, with flexible filtering and grouping to support business decision-making.
RESOURCE EXPIRATION
Looks at specific documents and certificates assigned to resources (especially vehicles & drivers), and reports on the expiration date, ie: end of license or permits.
Filter on 'expiration date' to see when critical docs are due to expire.
Tables available dedicated to specific resources, ie: Driver-related expirations.
RESOURCE VALIDATIES
Reports on the validity period for all resources, including start and end date / expiration and number of days to expire.
Includes currently unavailable resources due to expired validities.
Filter on 'End timestamp' or 'legal end date' to view resources with dynamic unavailability
System will automatically mark resource as unavailable due to expiration of document.
Why 2 options?
The split between Expiration and Validity dashboards is mainly due to:
Customer workflow: flexibility to see all validities vs just upcoming expirations.
Filtering: Resource Expiration typically uses an "is between" expiration date filter, while Resource Validity dashboards employ filters on the legal end date.
Summary:
Use Resource Expiration for a quick, focused list of items that are about to expire soon (with direct date-based filtering).
Use Resource Validity to see the full range of validity periods for resources (including those that have already expired or cause current unavailability).
HOLIDAYS
Based on 'Resource Unavailability' records (mostly driver) entered for holidays or time off
Export features let you retrieve exact dates for holidays per driver/resource
Uses Holiday start / end date to determine ‘Active’ status
Filtering based on END DATE; this may not directly return all holidays active on a specific date, ie: those still ongoing past the END DATE specified will not be included
Summary:
Holiday dashboards aggregate and display driver/resource time-off periods, with data based on start/end dates of holiday records. Use for planning, reporting, and filtering resource availability, so that staffing issues or driver shortages can be proactively managed.
INCIDENTS
Based on incident records linked to orders, stops, and goods (cargo).
All incident types included; both “stop-level” and “goods-level” incidents are counted and displayed together.
The main incidents dashboard offers:
A summary table grouping all orders by incident type (ie: Failed delivery) including a “No incident” or “Clean delivery” row for incident-free consignments.
Clicking on an incident type reveals all affected orders, with columns like Order ID, Customer, Service Level, Revenue, and Cost, and click-through to order details.
For each incident type, includes
orders
loading meters
pallet spaces
percentage of the total.
If a single consignment (order) suffers multiple incidents, each incident is counted / “No incident” means the order was executed without any logged incident.
On Time, In Full (OTIF) standards track the percentage of orders delivered without incidents, as well as categorising all types of failures, not just late or missing deliveries.
Summary:
Incidents are calculated based on structured records of failures/issues logged at stops or cargo. The dashboard aggregates this per incident type, customer, or time period, and allows detailed drill down for review and improvement actions.
ACCOUNTING
Accounting data based on sales and purchase invoices, credit notes, and accruals.
Mirrors what is sent or booked in your accounting package, supporting reconciliation and transparency
Tables based on individual invoice line items across:
Sales Invoices
Credit Notes
Purchase Invoices
Credit notes tables allow tracking reversals, corrections or cancellations
Purchase Invoice includes costs from suppliers or subcontractors
Breakdown by subcontractor vs owned fleet is available
Accounting dimensions = custom fields for analytical and financial reporting at the line item level, for accounting data entry.
Up to 3 accounting dimensions available - mapped to internal categories such as department, cost centre, project code, etc.
Description field available for each line
Exposed in both invoice detail page & exported data - customers can check & validate transaction classifications
Configured per customer so fields / descriptions show align with whats needed for group reporting / accounting exports
Summary:
The accounting data calculated by aggregating actual and accrued sales/purchase invoices and credit notes at the charge line level, split by operational type and filtered by invoice/accrual date. This makes it possible to verify what has been sent to accounting, what is still pending, and to perform period-end reconciliation and reporting.
ACCOUNTING ACCRUALS
Allows for accurate period-end cut-offs, supporting month-end closing, interim reporting, and reconciliation with accounting software.
Accruals account for revenue or cost that has occurred but not yet invoiced / booked
Calculated at charge level from executed orders, enables estimation on revenue earned but not yet realised on invoices
Revenue Accruals:
All charge lines (not the whole order total) are considered
Sums up charges where the service has been delivered/executed (using “collection date,” “delivery date,” or a configurable “charge date”) but has not yet been invoiced as of the selected accrual date
If part of an order is on an invoice and part is not, only the un-invoiced charges are counted in the accrual.
For cost accruals (purchase invoices):
The total value of executed services (trips/shipments) not yet booked in a purchase invoice as of the accrual date is included
This is calculated for each cost charge item, often grouped by own fleet vs. subcontractor, shipment, supplier, etc
The accrual is always based on a cut-off/accrual date (typically end of the accounting month).
Charges already locked for prior periods cannot be modified, ensuring data integrity for closed accounting periods
Summary:
Accounting accrual data is the sum of revenue and/or cost charges that have been completed but not yet invoiced (for revenue) or received/booked (for cost), as of a specific cut-off date. This calculation happens at the individual charge instance level for precision and auditing.