Orchestrate

The billing plan that stops at 80%

Break-fix drill · Sales · about 5 minutes · starts after stage 11 of 11, "Pay and close the month", and the Run a project chapter up to "Plan the milestones" (project CP-26-ENG01 released for Brennock's EP-900, with its engineering hours, engineered parts and build charged to it)

What the user reports

Calder, 2026-12-21. Last week the project manager typed the billing plan of CP-26-ENG01 from Brennock's contract for the EP-900: 30% when Brennock approves the design, 50% when its engineer has witnessed the factory acceptance test. This morning Brennock's engineer signed the revised drawings, and the project manager recorded milestone 1 as reached. Billing opens Milestone billing to send Brennock its 30%.

The error: Billing milestone 1 of CP-26-ENG01 is refused: the billing plan covers 80% of the order, and nothing can be billed until the rest is planned. The milestone is reached and its evidence is recorded.

What you'll do

  1. See the problem as the billing specialist: On Milestone billing, Bill milestone 1 of CP-26-ENG01.
  2. Find the cause: The milestone is reached with its evidence, the project is released and Brennock has no overdue bills. Why is the bill refused?
  3. Fix it as the project manager.
  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 billing plan covers only 80% of the order: the delivery milestone (20%) was never entered, and a plan that doesn't cover the whole order can't bill, because its bills would never add up to it.

The rule sits on the plan, not the milestone: the bills of a billing plan must add up to the order to the cent, and the last milestone takes what is left. A plan of 30% and 50% would leave 37,200.00 of Brennock's order that no bill ever claims. The planned date is a forecast, not a condition; a milestone bill doesn't check stock; and a credit limit holds deliveries and orders, not a bill for work Brennock has already accepted.

Why it broke

The billing plan was typed from part of the contract. Each milestone was right and each was accepted, so nothing looked wrong until the first bill: the check that a plan covers the whole order runs when a bill is released, because a plan may be built up over days.

How teams prevent it

Enter the billing plan from the whole contract and read the coverage on Milestone billing before the first milestone is reached: anything under 100% is money no bill will ever claim. Have someone who didn't type it, sales or the controller, compare the plan with the contract's payment schedule when the project is released.

Across teams

The project manager owns the plan; billing found the gap when the first bill was refused; Brennock's cash for the design approval (59,287.50 with tax) waited while it was fixed; and had the plan been allowed to bill, 37,200.00 of the order would have stayed unbilled after the pump shipped, found only when the controller compared billed with the order at the project's close.

Where AI fits

Extract and compare: a model can read the contract's payment schedule and propose the milestones with their shares and events, citing the clause for each. The project manager checks and saves them; the 100% rule stays in the system. It is the same pattern as the chapter's milestone stop: the model finds the evidence, a person confirms, the bill follows by rule.

Learn more: Quality, projects and service: the processes between the big four

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