The month that was never run
What the user reports
Month-end at Calder, 2027-01-29. On 21 December the fixed asset accountant posted December's depreciation run. That afternoon the plant controller asked her to hold it while he checked whether the second test station should start depreciating in January instead, so she reversed the run. His answer came on the 23rd: December is right. Everyone was off until the new year, and nobody posted the run again. Today the accountant runs January's depreciation. December is still open for the year-end close.
The error: January's depreciation run is refused for every asset of CP10: the machines are depreciated through 2026-11 (the test station through no month yet), and "2026-12 comes first". Nothing posts for January, and December's books carry no depreciation at all.
What you'll do
- See the problem as the fixed asset accountant: On Depreciation run, read the proposal for 2027-01 (this month) and post the run.
- Find the cause: January's period is open and every machine has values left. Why does the run refuse every asset?
- Fix it as the fixed asset accountant.
- 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: December's run was reversed and never posted again: every asset is depreciated through November, and months are depreciated one after the other, so December comes first.
The proposal names the stop on each asset: depreciated through 2026-11, so 2026-12 comes first. The run in December was reversed, which makes the month owed again; the run won't skip it, because each month's charge is the net book value over the months left, and a skipped month would leave that month's profit too high and the next ones wrong. January's period is open (the run reached the proposal), the test station started in December when it was settled, and the reversal took back only December's depreciation, not the values taken over.
Why it broke
A posting was reversed to hold it, and holding is not a status a reversal can carry: the month was simply owed again. Nothing asked for it until the next run, and the run won't skip a month, so January found the gap.
How teams prevent it
Hold a run before it posts, not after: read the test run (the proposal) and post once the question is answered. If a posted run must come back, put the repost on the close checklist with an owner and a date, and check at every month-end that each month of the year has one run that stands.
Across teams
The fixed asset accountant's run stopped; December's profit looked 2,700.00 better than it was until the repost; Assembly's and the test area's cost center reports for December missed their depreciation; the year-end close and the asset history sheet for 2026 waited on it; and the plant controller's question, already answered, cost a month of follow-up.
Where AI fits
Plain automation: a rule that each month of the year has one run that stands, run on the close checklist, finds this gap with no model. An agent that saw the refusal and posted December on its own would be acting on a reversal someone made on purpose; whether the reason still holds is the accountant's call.
Learn more: Record to report, end to end