Skip to content
Management & reportingFor every industry

Explain plan-versus-actual variances for finance

Every variance from plan with the postings, orders and events behind it, and a warning before a budget is exceeded.

Today

Controllers spend days working out why a cost center or product line is off plan. The answer sits in postings, purchase orders and production data spread across systems. Budget overruns surface at month end, when nothing can be steered any more.

An example

At Talwerk Antriebstechnik cost center 4200, maintenance in plant 2, is well above plan in October. The agent traces most of it to two records: the unplanned replacement of the main gearbox on gear-cutting machine VZ-07 and external service order 45-1182 for the hardening shop. It also warns the cost-center owner that at this rate the quarterly budget runs out in week 48.
Fictional company, typical workflow.

Your data, wherever it lives

Today postings, purchase orders and cost centers sit in the ERP, the plan in finance spreadsheets, downtime and machine hours in the MES, and explanations get chased by e-mail from the people responsible. demi reads, understands and links them per cost center, order and event, with your rights. The AI explains a variance in minutes instead of days of searching, every statement backed by its posting, and the cost-center owners decide how to respond.

Where the data lives today

  • ERP
  • Office files
  • MES
  • E-mails
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: the ERP, planning spreadsheets and production data. demi replaces nothing and links every posting to its cost center, its order and the event it came from, such as downtime.

  2. 2 · PermitPermission Layer

    Cost-center owners see their budgets and postings, finance sees everything, and personnel costs of individuals stay with the roles that see them today. Finance reviews every explanation and approves the commentary, and this is recorded.

  3. 3 · ActIntelligence Layer

    The agent drills from the variance to the postings behind it and computes each one's share exactly from the postings, not estimated. It writes the explanation with the records and warns owners before a budget is exceeded.

How it runs

  1. 1

    Clarify the data sources: ERP, planning spreadsheets and production data

  2. 2

    The agent compares plan and actual per cost center and product line

  3. 3

    It traces every significant variance to its postings and events

  4. 4

    Finance reviews the explanation and releases the commentary

  5. 5

    Owners get warnings before their budget runs out

What changes

  • Every variance traced to its postings

  • Budget overruns caught early

  • More time in finance for decisions

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+144 hfreed per year

Assumptions and calculation

demi shows the postings, orders and events behind each variance; you correct course.

60 min → 36 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

30 budget variances × 60 min × 40% × 1.0 (manual) × 12 months = 8,640 min = 144 h

Value per year, before demi costs

Freed per year+144 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$9,360

gained per year

144 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

How deep does the analysis go?

Down to the individual posting, purchase order or invoice and, where connected, to the event in production, such as a machine stoppage. The agent shows which share of the variance comes from which record. You can open every level and check the original.

Can cost-center owners receive budget warnings?

Yes. You decide when a warning fires and how it arrives, for example by e-mail or in chat. The warning names the postings driving the budget and the expected trend. That leaves time to act.

Does it work with our cost-center structure?

Yes. demi works with cost centers, cost types and cost objects exactly as you have set them up. Nothing is rebuilt. When the structure changes, demi works with the new state. How the data gets from the ERP to demi, we clarify in a conversation.

Does the agent repost anything?

No, it posts nothing on its own. If it finds a misposting, say on the wrong cost center, it proposes the correction. The posting happens only after finance approves it, and the step is recorded.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases