The trip already produced the invoice. Stop typing it again.
Most transport businesses bill from a spreadsheet assembled days after the work was done, which is why invoices go out late, surcharges get forgotten and margin leaks quietly. In GoFleexo the trip record is the billing record.
However you price the work, the system prices it the same way.
Per kilometre, per hour, per day, per trip, one-way or round trip, or a monthly contract — commercial transport uses all of them, often for different customers on the same fleet. Rate cards are configured once and applied automatically at trip closure.
Rate card configuration
Per km, per hour, per day, fixed per trip, one-way or round trip, and contract rates held per customer so the right price applies without anyone remembering it.
- Distance, time and fixed-rate methods
- Customer-specific rate cards
- One-way and round-trip pricing
Surcharges and pass-through
Fuel surcharge, tolls, permits, driver overtime, night charges and waiting time applied by rule rather than by negotiation after the fact.
- Fuel surcharge and tolls
- Overtime and night charges
- Waiting time by the hour
Trip-based billing
The invoice is generated from the closed trip — distance, duration, fuel, tolls and driver charges — with adjustments for cancellation, partial completion or rerouting.
- Generated at trip closure
- Shared trips split across customers
- Cancellation and partial adjustment
Contract billing
Recurring cycles for retainer and rental customers, invoiced automatically, with excess usage billed on top of the fixed component.
- Weekly, monthly, quarterly cycles
- Excess kilometre and trip charges
- Consolidated multi-vehicle billing
Round trip and multi-leg
Outbound and return billed jointly or separately as the agreement requires, with a different rate for a loaded return than an empty one.
- Separate or joint leg billing
- Loaded vs empty return rates
- Multi-leg shipment handling
Invoice delivery
Provisional and final invoices as PDF or Excel, delivered by email, through a customer portal, or printed with the trip documents.
- Provisional and final invoices
- Email, portal or printed
- Customer, contract, trip and vehicle references
Invoicing is half the job. Getting paid is the other half.
An invoice that leaves the building and is never chased is a cost, not revenue. GoFleexo tracks what is owed, what is overdue and what it is costing you to carry.
Payment recording
Payments captured manually or through bank integration, across cash, transfer, mobile banking and card, with advances and deposits adjusted automatically.
- Manual or bank-integrated entry
- Multiple payment modes
- Advance and deposit adjustment
Overdue management
Overdue invoices are flagged and reminders generated, so collection is a process rather than a memory.
- Overdue flagging
- Automatic reminders
- Per-customer outstanding view
Receivables ageing
Standard 30, 60 and 90-day ageing so the finance team can see exactly where cash is trapped.
- 30 / 60 / 90 day ageing
- Outstanding per customer
- Collection prioritisation
Margin per customer
Billing set against actual trip cost gives true profit per customer, not just revenue — the number that decides whether a contract is worth renewing.
- Billing vs actual cost
- Profit margin per customer
- Revenue by vehicle and route
Tax and compliance
Tax applied by rule and reported for the filing period, with invoice references retained for audit.
- Rule-based tax application
- Tax liability reporting
- Audit-ready invoice records
Accounting handover
Export to Excel or PDF, or hand the finance system a structured feed rather than a re-keyed summary.
- Excel and PDF export
- Accounting system integration
- Reconciliation reporting
One record, not a stack of systems.
This module shares the same data model as the rest of the platform, so a weighbridge reading, a job card and a customer invoice all belong to the same traceable chain rather than three disconnected tools.
See this running against your own fleet.
Tell us your fleet size, device types and the process costing you most. We will map the modules that address it and propose a phased rollout.