The carrier Calder can't pay
What the user reports
Monday 21 December, month end is near. All four trucks have final charges, and accounts payable is settling them so the freight cost is in December's books. Last week Tallis Road Freight wrote that it had moved to a new legal entity with a new bank, and the master data specialist removed Tallis's supplier data in CP10 to re-create it from the new onboarding form, which is waiting for approval.
The error: Freight settlement for Tallis's truck (BWU-PO-5648) refused: carrier 20000006 has no supplier data in CP10.
What you'll do
- See the problem as the accounts payable accountant: On Freight settlement, create the settlement document for the freight order of Brennock's BWU-PO-5648 delivery, carried by Tallis Road Freight for 721.81.
- Find the cause: The truck has delivered and its charges are final. Why does settling the freight need Tallis's supplier data in the company code?
- Fix it as the master data specialist.
- Prove it: run the step that failed again.
The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.
Answer and explanation (open after the drill)
The fix: A carrier is a supplier: settlement accrues what Calder will owe it, and its invoice posts to payables in that company code.
Calder pays its carriers like any supplier: settlement accrues the freight cost against GR/IR clearing because a payable to that carrier will follow, and the carrier's invoice later posts to its account with its reconciliation account and payment terms in CP10. Without the supplier data, the lab won't accrue a cost it couldn't pay. The agreement and the final charges are on the freight order, and nothing in settlement touches a portal or decides punctuality.
Why it broke
Freight looks like logistics, but every carrier is a supplier in finance: its truck is accrued as a cost owed to it and its invoice is paid through payables. Removing the supplier data to re-create it left a gap in which nothing for that carrier can post, at month end, when the freight should reach the books.
How teams prevent it
Change a supplier's legal or bank details on the existing record through an approved change, with a second person confirming the bank data, instead of deleting and re-creating it. Before removing company code data, check for open freight orders, settlements and invoices. Time master data changes away from month end.
Across teams
Accounts payable can't close the freight for December, the controller misses 721.81 of freight cost in the month, and Tallis waits for its money. The supplier record belongs to the master data team; the bank change needs approval from finance, and the transportation planner is often the first to hear about a carrier's new entity.
Where AI fits
A rule that warns before company code data with open documents is removed is plain automation. A model can help with the change itself: reading the carrier's letter and the new onboarding form and listing what changed (extract), and flagging a bank change that arrives by email shortly before a payment, a common fraud pattern (predict). It should not change supplier or bank data on its own.
Learn more: Warehouse and transportation execution