Dispatch and Invoicing Automation for Freight Operators: What to Automate First

A freight operation runs on steps that repeat for every load: take the order, assign a driver, update the customer, collect the paperwork, send the invoice. When those steps run on phone calls, spreadsheets and paper, every new load adds more manual work, and the team needs more people just to keep up.

We build dispatch, tracking and invoicing automation for freight, fleet and 3PL operators in Switzerland through our logistics automation service. This guide explains which steps to automate first, the Swiss and European rules that shape the paperwork, and how to measure the result.

Where the hours go in a manual operation

In most operations we map, the manual work clusters in a few places:

• Dispatch by spreadsheet. Dispatchers juggle calls, texts and several tabs just to know where a load is.
• Status calls. Customers call for updates because nothing in the stack tells them automatically, and dispatchers call drivers to find out.
• Paperwork. Delivery notes and consignment notes are signed on paper, then scanned, retyped or lost.
• Invoicing lag. Invoices wait until someone has the paperwork and the time, so cash arrives days or weeks late.
• Month-end reconciliation. Orders, deliveries and invoices live in different systems and have to be matched by hand.

What to automate first

Rank each manual step by how often it happens and what a delay or error costs. For most operators, the order looks like this:

The first three come first because they happen on every load, they are mostly rule-based, and they connect directly to cash: a confirmed delivery with a proof of delivery is all an invoice needs.

Step 1: Status updates without phone calls

Most fleets already have the data to answer "where is my load?" It sits in the telematics system or the driver app. Automation turns those events into updates: arrival at pickup, loaded, departed, arrived at delivery, delivered. Each event updates the order and, if the customer wants it, sends them a message or updates a tracking page.

The result is fewer calls in both directions. Dispatchers stop chasing drivers, and customers stop chasing dispatchers.

Step 2: Proof of delivery and digital transport documents

Capturing the signature and photos at the stop, in an app, means the proof of delivery is attached to the order the moment the stop closes. No scanning, no lost paper and no waiting for the driver to come back to the depot.

The legal side is moving the same way. The CMR Convention, which governs international road freight contracts, now allows fully electronic consignment notes. According to IRU, 58 countries are CMR contracting parties, and 39 of them have ratified or acceded to eCMR. IRU lists real-time access to information and proof of pick-up and delivery among its benefits.

In the European Union, the eFTI Regulation applies in full from 9 July 2027. From that date, authorities in every member state must accept freight transport information that operators share electronically through certified eFTI platforms. Certified platforms and service providers could start preparing from January 2026. For operators whose trucks run into the EU, digital documents are becoming the normal way to work.

Step 3: Invoice on delivery

Once proof of delivery is captured digitally, the invoice can be created at the same moment. The system takes the agreed rate from the order, adds any extras recorded during the job, attaches the proof of delivery and sends the invoice, or queues it for a quick check first.

For Swiss operators, the invoice format has its own rules. The QR-bill fully replaced the old Swiss payment slips on 1 October 2022. Since 22 November 2025, version 2.3 of the QR-bill implementation guidelines has applied, and only structured addresses are permitted in the QR-bill, according to SIX. Any system that generates invoices needs to output structured addresses, or payments can be rejected.

For customers who pay through e-banking, eBill delivers invoices straight into their online banking. eBill reports 4 million registered users, and says 95% of Swiss financial institutions are connected to its infrastructure.

The payoff is speed. When the invoice goes out the day of delivery instead of days later, the payment clock starts earlier, and month-end reconciliation shrinks because orders, deliveries and invoices are linked from the start.

Step 4: Connect what you already run

None of this requires replacing your software. In most projects, we connect the systems an operator already uses:

Connecting instead of replacing is faster, cheaper and easier on the team, because nobody has to learn a new system to see the benefit.

Mistakes to avoid

• Automating a broken process. If the dispatch rules live only in one person's head, write them down first. Automation repeats whatever process it is given.
• Skipping the drivers. A driver app only works if drivers use it. Keep the steps at each stop short, and test the app with a few drivers before rolling it out to the fleet.
• Sending invoices with no check. Start with invoices queued for a quick review, then switch to automatic sending once the error rate is proven low.
• Changing everything at once. Roll out one step at a time, so the team learns each change and you can measure what each one saved.

What to leave for later

Route optimization, demand forecasting and AI assistants are tempting, but they depend on clean, connected data. Get the status, proof of delivery and invoicing flows running first, and the data for those projects builds up on its own. When you get there, our guide to where AI automation pays off explains how to pick the right AI tasks.

How to measure the result

Measure these before you start and again after each step goes live:

• Hours per week spent on status calls and status updates.
• Days from delivery to invoice sent.
• The share of invoices that need a correction.
• Calls and emails from customers asking where their load is.
• Time to close the month.

Time savings show up first. Cost savings follow: less overtime, fewer billing errors and more loads handled by the same team.

How we work with freight operators

Our logistics work is built for operations with 5 or more people where dispatch or tracking is still handled manually. It starts with a two-minute application and a 30-minute strategy call with a logistics specialist. On the call, we walk through how dispatch, tracking and invoicing run today and point to the manual steps that cost your team the most hours. You leave knowing what a rollout would involve, whether or not you work with us.

Every project is quoted after that call, because the scope depends on how many systems we connect. You can read more and apply on our logistics automation page. Operators who prefer German can use our German logistics page.

If you are ready to find out which steps to automate first in your operation, apply for a logistics strategy call.

Frequently Asked Questions

Do we need to replace our TMS to automate dispatch?

Usually not. Most of the gains come from connecting the TMS, telematics and accounting tools you already run, so data moves between them without retyping.

What should we automate first, dispatch or invoicing?

Start with status updates and proof of delivery, then invoicing. Invoicing on delivery depends on reliable delivery data, so the first two steps make the third one possible.

What changed for QR-bills in November 2025?

Since 22 November 2025, only structured addresses are permitted in the QR-bill, and the extended character set of the Swiss Payment Standards applies. Invoicing systems need to output both correctly.

How long does a logistics automation project take?

It depends on how many systems we connect and how manual the current process is. We give a real timeline on the strategy call, once we have mapped your operation.