Orchestrate

The declaration without a value

Break-fix drill · Logistics · about 5 minutes · starts after stage 11 of 11, "Pay and close the month", and the Global trade chapter up to "Give the declaration a value" in *Declare the export* (customs settings for CP10, Lakemoor on FCA Rockford, ES-200 weighed, the two pumps for LWC-PO-0418 picked and packed on one pallet)

What the user reports

Monday 21 December at Rockford. Lakemoor's carrier collects the two pumps for LWC-PO-0418 at three. The shipping clerk drafted the export declaration this morning and left it for the billing run, which posts every evening, as it does for every order in the United States. At two the pallet is wrapped, the declaration is still a draft and the goods issue is refused.

The error: Release refused on Export declarations: the declaration for LWC-PO-0418 has no value, because there is no invoice for the delivery yet; and the goods issue is refused while the declaration is a draft.

What you'll do

  1. See the problem as the trade compliance officer: On Export declarations, Release the declaration for the delivery of LWC-PO-0418; then on Deliveries and shipping post its goods issue.
  2. Find the cause: The order is priced, the pumps are classified and packed. Why does the declaration have no value?
  3. Fix it as the billing specialist.
  4. Prove it: run the step that failed again.

Start the drill

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: The value comes from an invoice, and the bill can only be created after the goods issue: before the goods leave, only a pro forma invoice can give it one.

A declaration reads its value from the delivery's invoice: the billing document, or before it a pro forma invoice. Calder bills after goods issue, and the goods issue waits for the released declaration, so waiting for the night's bill is a loop that never ends. A pro forma invoice carries the order's prices for this delivery, posts nothing and asks Lakemoor for nothing. Tax and the control class don't make a value, and customs never fills one in: the exporter states it.

Why it broke

Calder's routine was built for the United States: ship today, bill tonight. A delivery to another country needs its value before it leaves, because customs is told what goods are worth before they cross. The declaration waited for a bill that waits for the goods issue, which waits for the declaration.

How teams prevent it

Make the pro forma invoice part of packing for every delivery abroad: when the pallet is packed, billing creates it, and the declaration is released before the carrier arrives. A morning list of deliveries abroad with a draft declaration and no invoice catches the rest.

Across teams

Shipping drafted, billing owns the invoice, trade compliance releases, and Lakemoor's carrier waits at the dock. The gap sat between two teams who each did their own part right.

Where AI fits

Plain automation is enough: create the pro forma invoice when a delivery abroad is packed, and list drafts without a value. A model would add a guess where the order already holds the exact prices.

Learn more: Order to cash end to end

All drills · Back to the lab

Sign in to track your progress

We'll email you a one-time sign-in link. No password needed.

or

Tell us a little about you

Optional, every field. It helps us pitch answers to your questions at the right level and decide which topics to write next. It is never shown publicly, and you can change or clear it anytime from the account menu.

SAP areas you work in