Home · Services · AI agents on Microsoft Teams · Digital CMR and POD
Scenario · Supply chain · Finance & accountingCMR data reaches the office on the day of unloading
Digital CMR and POD: from photo to settlement
The driver photographs the document at unloading. UiPath IXP reads it, including stamps and handwritten notes, a robot matches it to the order in the TMS, and the freight invoice goes out the same day.
Executive summary
Transport documents take weeks to reach the office; invoicing and settlements stall.
The driver takes a photo in the cab, IXP reads it, and a robot matches it to the TMS order and checks completeness.
Invoicing on the day of delivery, lower DSO, proof of delivery on demand.
The driver app, the TMS, the accounting system; UiPath IXP + robots.
A carrier and forwarder, 400 vehicles
9,000 CMR and POD documents a month. Drivers bring the paperwork in every week or two; the office retypes data, matches documents to TMS orders, scans and files.
A freight invoice cannot go out without proof of delivery, so receivables wait until the binder returns to the office. A client asking for delivery proof waits for a scan.
The current reality
- HumanThe driver carries CMRs in the cab for weeks
- WaitingNo invoice without the POD, so DSO climbs
- HumanThe office manually matches documents to TMS orders
- HumanRetyping, scanning, filing in binders
- Error riskA lost or illegible CMR means a dispute and no payment
- WaitingThe driver's settlement waits for complete paperwork
The hidden cost of the current process
The week between unloading and invoicing
- 600 office hours a month spent retyping and matching documents.
- Invoicing delayed by 1-2 weeks ties up working capital every month.
- "Delivered / not delivered" disputes drag on without quick proof.
The cost of doing nothing
You pay for the automation once; the manual process costs you again every month.
The process after automation
- AutomationThe driver photographs the CMR in the app at unloading
- AutomationIXP reads the document, including stamps and handwriting
- AutomationA robot matches it to the TMS order and checks completeness
- HumanGaps and mismatches: one dispatcher decision on Teams
- AutomationThe invoice goes out the same day; the POD is available to the client
What the automation handles
- Reading and validating documents 24/7 (IXP)
- Matching to orders and completeness checks in the TMS
- Preparing the invoice and driver-settlement pack
When a human decides
- Mismatches, damage and remarks on the document
- Disputes with clients and subcontracted carriers
- Exceptions beyond the completeness rules
Before
After
Value model: example assumptions
Business benefits
- Cash returns sooner because the invoice leaves on unloading day
- Driver settlements without waiting for paperwork, and with fewer disputes
- The full evidence set in a second for any claim
- The office absorbs a bigger fleet without headcount growth
Board-level KPIs affected
DSO · billing lag · cost per shipment · driver settlement time
What management gains
- A daily picture: delivered, invoiced, pending
- Fewer delivery disputes, because the proof is in the system right away
- Invoices go out daily, so cash flow is predictable
Estimate it for your organisation
An illustrative estimate based on your inputs. It models released capacity and is not a savings promise.
Systems in this scenario
Inputs
- Driver app (photo)
- Email from business partners
- Terminal scans
Mientha agentic layer
- UiPath Agent Builder
- UiPath robots
- Maestro™ · Action Center
Core systems
- TMS
- Finance system
- Customer portal
Human approval: Teams / Action Center
What we deliver
- A document-sample analysis: quality, languages, formats
- An IXP model trained on your CMRs and PODs
- Robots matching documents to orders in the TMS
- An exception route for dispatchers on Teams
- A pilot on one branch or lane
- Extraction-quality monitoring and a weekly report
What we need to start
- 50-100 sample CMRs/PODs (difficult ones too)
- TMS access in a test environment
- The completeness rules required for invoicing
- A process owner on the operations side
Implementation roadmap
Discovery
We map the process, data and exceptions with process owners.
Design
Target flow, business rules, approval thresholds.
Build
Agents, robots and integrations in your environment.
Validate
Tests on real cases, exception handling.
Go-live
Controlled rollout with human oversight.
Optimise
Monitoring, reporting and continuous improvement.
Duration depends on the number of systems and rules; a single process usually takes a few weeks.
Risk and controls
Autonomy under control
- Below the confidence threshold, a human always verifies
- The robot admits no invoice without your completeness rules met
- Originals archived, nothing is lost along the way
- A full decision trail on every shipment
Why now
- Every week of invoicing delay ties up working capital
- Rate pressure: a cost edge is easier built in the back office than on fuel
- It is the basis for faster driver settlement, our transport product
Why this matters to:
DSO falls; cash flow stops depending on driver returns.
Dispatchers handle the exceptions.
The fleet can grow without a swelling office.
Questions we usually hear
They do, because their prompt settlement depends on that photo. The app guides them step by step, and the paper original still reaches the archive.
That is why we train IXP on your documents. Below the confidence threshold a case goes to a human, and extraction quality improves week by week.
OCR reads characters. Here the document is also matched to the order, validated and closed in the TMS.
When this may not be the right solution
- A few hundred documents a month: scanning discipline will do
- Clients require paper originals only, without exception
- No TMS at all: operational basics first, then automation
A question for your next board meeting
How much of your company's receivables is waiting today for documents in drivers' cabs?
Solutions in the library
The same process as an implementation plan
The scenario shows the process with an AI agent on an example company. Library solutions describe the same or a neighbouring process with a value model and an implementation plan.
Freight is delivered, invoiced and disputed before anyone finds the signed document.
See the solution Supply chainFreight invoice audit against rate cards and shipmentsCarrier invoices are checked on a sample and paid in full; the overbilled lines are the ones nobody opened.
See the solution HR & peopleDriver settlementRoute, fuel and trip data collected by hand every month, and allowances calculated in a spreadsheet.
See the solutionWe deliver it through our service AI agents on Microsoft Teams.
The example company in this scenario works in Transport & logistics.
How many days pass between unloading and invoicing at your company?
Send 5 sample CMRs and we will show extraction on your own documents.
Send us 5 sample CMRs