Month-end billing is one of the most persistent inefficiencies in the South African freight industry. Drivers complete loads throughout the month, paper delivery notes accumulate in a pile, and the finance team spends the last week of every month manually capturing trip data, checking rates, and generating invoices. By the time the invoice reaches the client, the delivery was completed three to four weeks ago.
This is not just an administrative problem. It is a cash flow problem, a dispute risk, and a competitive disadvantage. This guide explains how automated invoicing works, what it requires to implement, and what the financial impact looks like in practice.
The Problem with Manual Invoicing
Manual invoicing fails in predictable ways:
Delays - The gap between delivery completion and invoice generation is typically 2 to 4 weeks in a manual operation. Every day of delay is a day of working capital tied up in the debtor book.
Errors - Manual data capture introduces errors. Wrong rates, incorrect quantities, missing surcharges, and duplicate entries are all common. Each error either costs you money (if you undercharge) or creates a dispute (if you overcharge).
Disputes - When an invoice arrives 3 weeks after the delivery, the client's accounts payable team has no memory of the transaction. They query it. You have to find the paper delivery note, confirm the details, and resubmit. This process can add another 2 to 4 weeks to the payment cycle.
Reconciliation burden - At month-end, someone has to reconcile the trips completed against the invoices raised. In a busy operation, this is a full-time job for several days. Errors discovered during reconciliation require corrections, credit notes, and resubmissions.
How Trip-Based Invoicing Works
Automated invoicing is built on a simple principle: the invoice is generated from the trip data, not from a manual data entry process.
When a freight order is created, the agreed rate is captured in the system. When the driver completes the delivery and captures digital proof of delivery, the system has everything it needs to generate an invoice:
- The customer's billing details (from the customer account)
- The agreed rate (from the freight order)
- The delivery confirmation (from the digital POD)
- The trip details (vehicle, driver, collection point, delivery point, quantity)
The invoice is generated automatically, attached to the POD, and sent to the customer. The transaction posts to the general ledger. All of this happens within seconds of the POD being captured - not at month-end.
Setting Up Pricing Rules
The foundation of automated invoicing is a correctly configured pricing structure. T-ERP supports a range of pricing models:
Per-trip pricing - A fixed rate per trip, regardless of distance or quantity. Simple to configure and easy for customers to understand.
Per-tonne pricing - Rate based on the weight of the load. Requires weight capture at loading or delivery.
Per-kilometre pricing - Rate based on the distance of the trip. Calculated automatically from the route distance.
Zone-based pricing - Different rates for different origin-destination combinations. Useful for operations with complex rate schedules.
Customer-specific pricing - Each customer can have their own rate schedule, with different rates for different routes, commodities, or vehicle types.
Surcharges - Fuel surcharges, toll surcharges, hazardous goods surcharges, and other additional charges can be configured as rules that apply automatically when the relevant conditions are met.
Once the pricing rules are configured, the system applies them automatically. There is no manual rate lookup, no spreadsheet, and no risk of applying the wrong rate.
Automated Invoice Generation
When a trip is completed and the POD is captured, the invoice generation process is:
- System validates the trip against the freight order (quantity, route, vehicle)
- Applicable rate is retrieved from the pricing rules
- Any surcharges are calculated and applied
- Invoice is generated with all required details
- POD is attached to the invoice
- Invoice is emailed to the customer's billing contact
- Transaction posts to the accounts receivable ledger
The entire process takes seconds. No human intervention is required unless an exception is flagged (e.g., the captured quantity differs significantly from the ordered quantity).
Customer Notifications and POD Attachment
Automated invoicing is most effective when it is paired with automatic customer notification. When an invoice is generated, the customer receives:
- The invoice in PDF format
- The signed digital POD attached
- A reference number linking the invoice to the original freight order
This transparency reduces disputes significantly. The customer can see exactly what was delivered, when, and by whom. The signed POD is irrefutable evidence of delivery.
For customers who prefer to receive invoices in a specific format (e.g., EDI, CSV, or a specific PDF template), T-ERP can be configured to generate invoices in the required format automatically.
Reconciliation and Finance Integration
In a fully automated invoicing environment, the month-end reconciliation exercise is largely eliminated. Because every trip generates an invoice in real time, the accounts receivable ledger is always current.
Finance teams can see:
- Total revenue invoiced to date (not just at month-end)
- Outstanding debtors by customer and age
- Invoices awaiting payment vs invoices in dispute
- Cash flow forecast based on expected payment dates
When the month ends, there is no pile of paper delivery notes to capture. The books are already up to date.
Automated Invoicing in T-ERP
T-ERP's Operations module includes a fully automated invoicing engine that generates invoices from completed trips without manual intervention.
Pricing rules are configured once and applied automatically. Digital POD from the mobile app triggers invoice generation immediately. Invoices are emailed to customers automatically with the POD attached. All transactions post to the general ledger in real time.
The result is a billing cycle measured in hours, not weeks - and a debtor book that reflects the current state of your business, not what it looked like three weeks ago.
Frequently Asked Questions
What happens if the driver captures the wrong quantity on the POD?
T-ERP includes validation rules that flag significant variances between the ordered quantity and the captured quantity. When a variance is flagged, the invoice is held for review rather than sent automatically. A supervisor can approve the variance or correct the quantity before the invoice is released.
Can automated invoicing handle credit notes and adjustments?
Yes. When a customer disputes an invoice or a correction is required, a credit note can be generated against the original invoice. The credit note is linked to the original transaction and the adjustment posts to the general ledger automatically.
How does automated invoicing handle fuel surcharges?
Fuel surcharges can be configured as a percentage of the base rate or as a fixed amount per trip. When the surcharge rule is active, it is applied automatically to every invoice. When fuel prices change, the surcharge percentage is updated once in the system and applies to all subsequent invoices.
Can we send invoices in bulk at the end of the week rather than immediately?
Yes. T-ERP can be configured to batch invoices by customer and send them on a defined schedule (daily, weekly, or at trip completion). Some customers prefer to receive a single weekly invoice rather than individual invoices per trip.
What accounting systems does T-ERP integrate with?
T-ERP includes a built-in accounting module that handles the complete GL posting automatically. For operators using external accounting software, T-ERP can export invoices in standard formats for import into most major accounting platforms.