Orchestrate

The allocation run twice

Break-fix drill · Finance · about 6 minutes · starts after stage 11 of 11, "Pay and close the month", and the Who made the margin chapter through "Allocate it" (plant administration CP11-900 with its December cost of 2,600.00, allocated by plan hours to the assembly hall and the test bench on 640000)

What the user reports

Month-end at Calder, 2026-12-21. This morning the controller allocated plant administration's December cost (2,600.00) to the assembly hall and the test bench. The screen took a while, and a general ledger accountant who saw it spinning thought the run had failed, so she keyed the same split as a journal entry on the allocation account to be safe. In the afternoon payroll sent a correction for the office: 150.00 of overtime missed in December's run, posted to CP11-900. The controller opens Overhead allocation to pass the 150.00 on.

The error: The run for CP11-900 and 2026-12 is refused: a manual journal entry credits CP11-900 2,600.00 on the allocation account. Reports, Cost centers shows administration 2,450.00 below zero, and the assembly hall and the test bench each carrying administration twice (3,600.00 and 1,600.00), half of it as their own spending.

What you'll do

  1. See the problem as the cost controller: On Overhead allocation, pick sender CP11-900 and 2026-12 and allocate what is left: the 150.00 payroll correction.
  2. Find the cause: Administration's 2,600.00 left it twice: once by allocation 000001 and once by the manual entry. Which one goes, and why?
  3. Fix it as the cost controller.
  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: Reverse the manual entry: the run is the record the allocation screen and the reports read as allocated, and it is what a later run builds on; the hand-keyed copy looks like a credit on administration's own cost.

Both documents are in the journal and move the same amounts, but only the run is an allocation: it records its sender, month and key, the reports show its lines as allocated in and out, and the next run passes on only what arrived since. The manual entry's credit on CP11-900 looks like a reduction of administration's own cost, so the run sees nothing left and the receivers show the copy as their own spending. Reverse the copy. Keying allocations by hand (all of them, or the 150.00 on top) repeats the problem every month.

Why it broke

A run that looked stuck was repeated by hand on the same account. The run had posted; the manual copy moved the same cost again. A journal entry on the allocation account carries no sender, month or key, so the run can't tell it from administration's own cost, and the receivers can't tell it from their own spending.

How teams prevent it

Look for the run's document before repeating it: Overhead allocation lists every run with its journal entry. Keep the allocation account for the run (many companies block it for manual postings), and if a run truly fails, run it again, which passes on only what is left.

Across teams

The general ledger accountant meant to help; the assembly hall's and the test bench's managers saw administration twice in December, half of it as their own overspending; the controller's run for the payroll correction stopped; and until the copy is reversed, the cost center reports and any rate built on them read 2,600.00 too much on the production side.

Where AI fits

Plain automation: a rule that a run's account takes no manual postings, or that flags a manual entry with the same amounts as a run in the same month, finds this with no model. An assistant can explain which document is the copy and why, but the reversal is the controller's decision, with a reason in the books.

Learn more: Record to report, 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