Customer freight billing: jobs and delivery documents

Two jobs, one delivery document

Suppose a transport operator is preparing a monthly statement for a customer. It includes two separate, completed jobs. The customer and operator agreed that the statement would include proof of delivery for the listed jobs. A signed document is linked to the first job. The second has no matching document yet.

The employee preparing the package needs to see both lines: the first with its attachment and the second with a missing delivery document. They can ask operations for the proof relating to the second job, using its specific reference.

In the proposed application, the employee opens the document beside the statement line and checks the association. They see the customer's order reference alongside the internal transport-job reference. The internal reference helps them speak with operations; the customer reference identifies the service in the customer's records. The statement remains understandable to both sides.

When operations supplies the missing file, it joins the second line. The employee can review the complete package before handing it over. The first job's document stays with the first job: a matching customer name or date is insufficient to use it for the other delivery too.

What staff need beyond another spreadsheet

Preparing the statement starts with identifying the jobs it covers and the documents agreed with the customer. If those terms are stored separately, the employee needs a link to them. They can then explain why a line is waiting for an attachment without keeping the reason in a personal spreadsheet.

A useful view connects each statement line to the job, its documents, and the person following up on a missing file. A colleague taking over can see what operations has already been asked. When the response arrives, they return to the same record without searching the correspondence again. The responsible employee reviews the statement and attachments before sending them to the customer. The existing accounting system remains the authoritative place for the billing record.

Also preserve the identity of documents already received. If a driver later sends another photo of the same proof of delivery, it belongs with the existing job. The extra file may add to its documentation; it does not create another completed service on the statement.

Check what your current system can prepare

The jobs, terms, and documents may already be in your transport management system (TMS) or ERP. Start by finding out whether billing staff can open them from one statement view. Sometimes the missing piece is access to an existing screen or a connection between a folder and the job. Preparing the documents may not require a separate application.

Odoo 18 documents calculating delivery costs on sales orders and adding delivery as an order line (Odoo delivery methods). That can cover part of the commercial data. Check separately how your system associates delivery documents with a customer's statement.

An integration makes sense when jobs are well managed in the TMS but files arrive in another system. It can connect those locations and show missing documents in the billing view. Before commissioning it, establish which job references and attachments the tools make available.

Consider a custom view when customers have different agreements about supporting documents and staff repeatedly assemble packages from several sources. An initial scope could cover one team and a recurring statement format. The project prepares material for review while retaining the existing accounting application.

If your team also checks surcharges on invoices received from carriers, our separate article covers comparing freight charges with the agreed transport order.

Open jobs after the application goes live

When changing tools, preserve jobs waiting for documents, including customer references and existing attachments. Moving only a list of jobs would leave staff associating files again. Older packages can remain in an accessible archive, and exports from the new application should retain the links between statements and documents.

Your company needs someone to maintain customer agreements and resolve uncertain document matches. Agree with the provider who investigates a file that reached the source system but still does not appear beside the job. Include integration maintenance, code and data ownership, and access for a replacement provider when comparing proposals.

Connect the statement to its delivery documents

Through its custom application service, Syntalith can build a view connecting transport jobs, proof of delivery, and the customer's agreed requirements. Billing staff review the package there and direct questions about missing documents to the right person. Your team identifies where terms are recorded and how jobs are referenced in customer documents and internal systems.

Tell us about the last statement that required a manual search for attachments. Explain where the job records were and how the delivery documents eventually arrived. That conversation will help determine whether an existing module is enough or whether you need an integration and a dedicated preparation view. Service pricing is available on the Syntalith pricing page.