Role
Operational controlling
Who knows what one production order really costs? Not the price of the material - the full cost, including changeovers, scrap and the time that went on rework. If it has to be calculated rather than read off, then pricing decisions are being made without that number.
Intro call
Four questions we would start with
Who sets the allocation keys for indirect costs?
If they were set once, when the system was implemented, they probably describe the company of a few years ago. Production has changed, the keys have not.
Whose desk does the question "why is this product unprofitable" end up on?
Usually yours - and it starts with checking whether the product is unprofitable or only looks that way because of how you spread the costs.
How many times a month do you explain to someone where the cost on their centre came from?
If it is often, the allocation is opaque to the people it affects - and then nobody believes it and nobody steers by it.
What do you not know about cost until the period closes?
If it is practically everything, the response to a variance comes a month late, when the cause is no longer on the floor.
We take over the calculating, you keep the agreeing
Assembling the unit cost, applying the keys and catching variances can be taken off the desk. Setting the allocation keys and defending them in front of the business stay with a person, because that is a conversation, not a calculation.
- An allocation key is a decision, not a formula. - The system calculates under the agreed key and shows how the result would change under a different one. Which is the right one is settled by you together with the business.
- The allocation can be taken apart. - For every cost on a centre you can see what it is made of and which key spread it. An opaque allocation is one nobody believes.
- The variance is calculated, the cause described by a person. - The system breaks the difference into components. Why it came out that way is said by someone who was on the floor.
Scope
What can be taken off operational controlling
Twenty example tasks. Each one has a human approval point. Below is a selection, and the scope we fit to your process.
Allocation keys and their justification
- A register of keys with the justification and the date they were set
- Pointing out keys based on data that has gone out of date
- Recalculating the result under an alternative key (choice: the controller and the business)
- Documenting who approved a given key
- A summary of costs not spread by any key
Product and order cost
- Assembling the full cost of an order from every component
- Pointing out orders whose cost departs from similar ones
- Breaking unit cost into material, labour and indirect
- Checking the completeness of cost inputs from production
- Comparing planned cost with actual
Cost variances
- Breaking a variance into price, usage and efficiency
- Pointing out events from the same period that might explain the difference (cause: the controller)
- A signal when a variance exceeds the threshold, during the period
- A summary of variances that repeat every month
- The variance history for a given centre
Profitability and conversations with the business
- Profitability by product, client and channel under the agreed method
- Pointing out lines sold below production cost
- Material for a conversation with the cost centre owner
- How the cost changed over time and what affected it
- A comparison of centres with a similar profile
A day's work
Today
- You assemble the cost of an order in a spreadsheet from several summaries
- When asked about a product's profitability you start by checking the keys
- You see variances after the close, when nobody remembers the cause
- Explaining the allocation to managers takes half the review
- Data from the floor arrives late or incomplete
- You remember the allocation keys but do not know who once approved them
With AI assistance
- The cost of an order is assembled, and you look at the outliers
- Profitability also shows how it would change under a different key
- A variance over the threshold reports itself during the period
- A manager sees the breakdown of their own cost without you explaining it
- Gaps in the data from the floor are marked before you calculate the result
- The keys have a justification, a date and the name of whoever approved them
- A unit cost you can rely on
pricing decisions rest on the full cost
the components are complete and visible rather than estimated
- The business accepting the keys
fewer arguments about whose cost it is
a key has a justification and a name, and the allocation can be taken apart
- Time to analyse a variance
the response comes during the period
a threshold breach is flagged rather than discovered after the close
- A transparent allocation
a manager understands their cost without an explanation
the breakdown is available where the cost owner looks
We start with one cost centre, not with the whole cost accounting.
- Step 1
We take one cost apart
We take one centre and break its cost into components and keys. That one table usually ends a years-long argument about why that department is so expensive.
- Step 2
The register of keys
Writing the keys down with their justification and approval. This is the moment when some of them turn out to be out of date - and that is valuable information in itself.
- Step 3
Order cost and variances
Assembling the full cost and signals when a threshold is exceeded. Only once the keys are agreed.
- Step 4
Profitability and material for the business
Breakdowns available to the cost owners. This stage changes controlling's relationship with the rest of the company the most.
Common questions
Questions that come up at the first meeting
Will controlling be smaller after the rollout?
Operational controlling is rarely overgrown, it is usually late. Cost data arrives once the decision has been made, because the summary takes two weeks. When it stops taking that, the controller starts being present in the conversations before the decision rather than after - and that is a change of position in the company, not a change in the number of people.
Does this fall under the AI Act?
Cost accounting is not a high-risk use. The line appears at performance data assigned to particular employees - that is an area with separate rules and one we do not touch in this scope.
Still have a question that is not here? Book a call
Next step
When did you last verify your cost allocation keys?
We will show you what cost accounting looks like when the allocation can be taken apart and a variance reports itself during the period.