In freight audit and payment, margin rarely disappears in one dramatic event. It erodes through repeated rate discrepancies, unsupported accessorials, duplicate invoices, manual rekeying, approval queues, and delayed recovery claims.
A Value Stream Map (VSM) makes that erosion visible. It connects the flow of information, from carrier invoice receipt to approved settlement, with the time, effort, handoffs, queues, and controls required to complete the work.
This deep guide uses a worked case study: a mid-market manufacturer processing 12,400 carrier invoices per month against $9.8 million in annual freight spend. The objective is to redesign the process so that invoices are matched faster, exceptions are managed with discipline, and transportation spend becomes a more reliable source of financial intelligence.
The broader freight audit workflow typically includes invoice capture, rate verification, accessorial validation, duplicate detection, exception handling, approval, payment, and spend reporting. These stages form the financial control layer for transportation spend, as described in this freight audit and payment overview.
1. Select the Scope Before Drawing the Map
The fundamental purpose of scope selection is to prevent a VSM workshop from becoming an unfocused discussion about every transportation activity.
For this case, the scope is:
Start: Carrier invoice received through EDI, portal, PDF, or email
End: Correct amount approved, coded, and released for settlement
The map excludes carrier procurement, shipment planning, contract negotiation, and general ledger reconciliation after settlement. Those may become future projects, but they should not dilute the first improvement cycle.
Project baseline
- Monthly invoice volume: 12,400
- Annual freight spend: $9.8 million
- Audit clerks: 4.1 FTE
- First-pass invoice-to-PO match: 21%
- Average lead time: 11.4 days
- Discrepancy rate: 4.6%, or approximately 570 invoices per month
- Manual audit coverage: 18%, or approximately 2,232 invoices per month
- Process steps: 14
- Handoffs: 9
- Recovery claims last year: $310,000
The customer value definition is precise: pay the correct carrier, on time, with accurate documentation and usable spend data.
2. Current-State Map: Where Time and Margin Accumulate

The current-state map shows a classic transactional process: substantial activity, limited flow, and multiple ownership boundaries.
Invoice receipt
→ Format identification
→ Manual data entry or rekeying
→ Shipment and PO lookup
→ Contract/rate lookup
→ Invoice-to-PO match
→ Rate and surcharge audit
→ Exception classification
→ Supporting-document request
→ Carrier or internal query
→ Recalculation or dispute
→ Supervisor approval
→ Business approval
→ AP voucher and settlement release
The 14 steps create nine handoffs across transportation, audit, procurement, operations, finance, and Accounts Payable.
Worked lead-time calculation
A representative invoice experiences approximately:
| Current-state component | Average time |
|---|---|
| Value-adding verification and settlement work | 2.3 days |
| Waiting for data, documents, responses, or approvals | 9.1 days |
| Total invoice-to-approved-settlement lead time | 11.4 days |
The process is not slow because every invoice requires 11.4 days of effort. It is slow because work is placed into queues between steps.
At 12,400 invoices per month, the 21% first-pass match rate means approximately:
- 2,604 invoices match without additional intervention
- 9,796 invoices require rework, clarification, or exception routing
Even when the 4.6% discrepancy rate is applied conservatively to total invoice volume, approximately 570 invoices per month contain a detected discrepancy. The discrepancy categories should be stratified by carrier, mode, lane, accessorial, invoice format, and business unit during the Analyse Phase.
3. The Eight DOWNTIME Wastes in Freight Audit and Payment
A VSM is valuable because it translates general concerns into observable waste. In this case, all eight DOWNTIME categories are present.
-
Defects
Incorrect rates, duplicate invoices, unsupported accessorials, invalid fuel surcharges, and mismatched shipment references generate rework and recovery claims. -
Overproduction
Teams produce duplicate spreadsheets, repeated exception reports, and status updates before the underlying invoice record is corrected. -
Waiting
Invoices wait for carrier responses, missing proof-of-delivery documents, contract clarification, supervisor approval, or AP batch release. Waiting represents approximately 9.1 of the 11.4 lead-time days. -
Non-utilised talent
Four-point-one audit FTE are absorbed by searching, copying, reconciling, and chasing information. Their analytical capability is not fully used for root-cause analysis, carrier performance, or contract improvement. -
Transportation
In administrative work, transportation means unnecessary movement of information. PDF attachments, email chains, shared-drive exports, and system downloads move invoice data between disconnected locations. -
Inventory
Unprocessed invoices and unresolved exceptions become transactional inventory. A queue of invoices is work in process, not completed value. -
Motion
Auditors switch between the carrier portal, TMS, ERP, contract repository, email, spreadsheets, and approval tools. Repeated searching is motion waste in a digital process. -
Extra-processing
The same invoice may be checked by an audit clerk, supervisor, business approver, and AP analyst even when the variance is below an agreed risk threshold.
A useful workshop technique is to record each waste against a specific invoice category. For example, an LTL invoice with a reclassification charge may require four additional searches and two approval requests, while a clean parcel invoice may need only automated validation.
4. Future-State Design: Create Flow Around Risk

The future state should not attempt to automate every decision immediately. It should automate predictable work and reserve human judgment for material or ambiguous exceptions.
Future-state flow
- Single intake layer receives EDI, API, CSV, portal, and PDF invoices.
- Data normalisation creates consistent fields for carrier, shipment, lane, weight, service, fuel, accessorials, and invoice number.
- Automated three-way match compares invoice, shipment/PO, and contract or tariff data.
- Rules-based audit checks rates, surcharges, accessorials, duplicate invoices, and service-level conditions.
- Straight-through approval releases invoices within tolerance.
- Risk-based exception queue routes only material or unresolved differences.
- Named ownership and ageing alerts make every exception visible.
- Exception decision results in corrected invoice, short-pay, approved variance, or recovery claim.
- Digital approval checkpoint applies to defined thresholds rather than every transaction.
- AP settlement release uses validated amount, GL code, cost centre, and supporting evidence.
- Closed-loop analytics feeds carrier scorecards, contract updates, and the next improvement cycle.
This design applies the DMAIC logic directly. The Define Phase establishes the settlement problem. Measure confirms lead time, match rate, discrepancy rate, and recovery value. Analyse identifies root causes. Improve pilots the future-state workflow. Control monitors match performance, queue age, recovery, and approval adherence.
5. Current Versus Future Performance
The following table combines the supplied baseline with the target state. The 2.4% discrepancy rate and 100% rules-based audit coverage are design targets for the improvement wave and should be validated during the pilot.
| Metric | Current state | Future-state target | Improvement |
|---|---|---|---|
| Monthly invoice volume | 12,400 | 12,400 | Stable demand |
| Annual freight spend | $9.8M | $9.8M baseline | Better control of spend |
| First-pass automated match | 21% | 78% | +57 percentage points |
| Invoice-to-approved-settlement lead time | 11.4 days | 3.2 days | 71.9% reduction |
| Discrepancy rate | 4.6% | 2.4% design target | 47.8% reduction |
| Manual audit coverage | 18% | 100% rules-based screening | Full population control |
| Audit and payment steps | 14 | 8 core steps | 6 steps removed or combined |
| Handoffs | 9 | 4 controlled handoffs | 5 handoffs removed |
| Audit staffing | 4.1 FTE | 1.7 FTE run-rate | 2.4 FTE redeployed |
| Annual recovery claims | $310K | $540K | $230K increase |
The target is not simply “more automation.” It is better process capability: clean invoices should flow quickly, exceptions should become visible early, and recovered value should be converted into contract and carrier action.
6. The 90-Day Kaizen Wave

Days 1–30: Stabilise and make the work visible
Kaizen Event 1: Invoice Intake and Data Definition Sprint
Owner: Transportation Systems Manager
- Catalogue all invoice formats and intake channels.
- Establish one operational definition for match, discrepancy, exception, approval, and recovery.
- Remove duplicate intake logs.
- Create a daily ageing view for invoices and exceptions.
- Confirm the baseline of 12,400 invoices, 21% first-pass match, and 11.4-day lead time.
Deliverable: A validated current-state map and controlled data dictionary.
Days 31–60: Pilot straight-through matching
Kaizen Event 2: Three-Way Match and Exception Cell Pilot
Owner: Freight Audit Manager
- Pilot automated matching for the top five carriers by invoice volume.
- Load current contract rates, fuel tables, and accessorial rules.
- Introduce risk thresholds for automatic approval.
- Assign every exception a named owner and due date.
- Use visual ageing alerts for queues exceeding the service target.
Pilot measures: First-pass match, exception rate, average queue age, recovery value, and percentage of invoices requiring manual touch.
Days 61–90: Integrate approval and control
Kaizen Event 3: Approval-to-Settlement Flow and Control Plan
Owner: Accounts Payable Director
- Replace serial approvals with risk-based checkpoints.
- Integrate validated amounts with AP voucher creation.
- Create standard response paths for short-pay, corrected invoice, and recovery claim.
- Publish carrier scorecards by discrepancy type and financial impact.
- Review weekly control charts for match rate, lead time, and exception ageing.
90-day exit criteria:
- Automated match rate moving toward 78%
- Settlement lead time moving toward 3.2 days
- Recovery trajectory moving toward $540K annually
- 2.4 FTE redeployed to analytics, supplier performance, and improvement work
- Documented control plan with owners, thresholds, escalation rules, and review frequency
7. Build the Capability to Lead the Improvement
Freight audit and payment is an excellent Lean Six Sigma project because it combines flow, variation, defects, financial impact, approval governance, and customer-defined value.
A Yellow Belt can support process observation, data collection, and kaizen events. A Green Belt can lead the DMAIC project, validate root causes, and manage the pilot. A Black Belt can coordinate cross-functional change, apply advanced statistical analysis, and mentor improvement teams.
Lean 6 Sigma Hub offers CSSC-accredited, self-paced training with practical case studies, tools, templates, worked examples, and project-based learning. Explore the Lean Six Sigma online training pathway, or develop project leadership capability through the Lean Six Sigma Green Belt course.
Build the skills to map your value stream, quantify the opportunity, and lead a measurable improvement project, pursue Lean Six Sigma certification today.
Kaizen. Kai-Care. Kai-Done. Lean Six Sigma.








