VIRTUAL CONTROLLER · NOW IN BETA

A controller that always watches along.

No finance department of your own? The virtual controller looks at your figures with you every month, the way a good controller does. It knows your figures over time, only reports variances larger than the normal fluctuation, explains the why behind them and proposes concrete actions. You stay in control, without combing through every table each month.

Now in beta in Easyclose · you can also explore the flags and drill-down directly in the demo
Virtual controllerJUNE 2026 · beta
2 flags this month · the rest stayed within the band
Flags from your controller
!Staff costs+8% over budget · larger than the normal fluctuation+8%
Group intercompany checkIntercompany current accounts close across all entities€0.00
Watches over: profit & loss · balance sheet · budget · liquidity · per BV and consolidated

Flags, not noise

Every month, dozens of lines deviate at least a little. A good controller does not report everything: they know the normal pattern and only raise the alarm when something falls outside it. The virtual controller works the same way: it looks at your figures over the past twelve months and only reports what is larger than the normal fluctuation. The rest stays quiet.

Easyclose · Virtual controller · June 2026
!Contractor costsVariance larger than the normal fluctuation over 12 months · flagged+€21k
!Energy costsJump after contract renewal, larger than the normal fluctuation over 12 months · flagged+€8k
·Net revenueWithin the band, not flagged+1.2%
·Vehicle costsWithin the band, not flagged−€0.4k

Flags in colour, noise dimmed. The controller explains for every flag why it stands out, and for the rest why it does not. So you read two lines instead of two hundred.

The why behind it, not just the number

Spotting a variance is step one. Knowing where it comes from is the real work: which BV, which cost type, which entry. The virtual controller does that digging for you and puts the explanation underneath the number, with the contribution per cause.

Result June · consolidated
€289k
▼ 6% vs budget
Where does the difference come from?
Higher contractor costsTechniek B.V. · two projects overran+€21k
Energy contract renewednew rate since May, structural+€8k
One-off gain last yearsale of equipment June 2025 · distorts the year-on-year comparison−€12k

The controller points out the cost type and the BV, and marks what is one-off: last year's gain does not belong in the trend, so it does not count it as a real difference.

Concrete actions, not a loose observation

A controller who only observes leaves you with the work. The virtual controller proposes a concrete action with every flag. You decide: carry it out, adjust it or set it aside. The AI proposes, you stay in charge of your figures.

Proposals for the June flags
Discuss the contractor costs with the project leadbelongs to the flag "Contractor costs +€21k"done
Put the new energy contract into the forecastso your forecast uses the real rate from now onproposal
Mark the gain as one-off in the year-on-year comparisonso it no longer distorts the trendproposal

Every proposal stays a proposal until you tick it off or throw it away. Nothing ever changes in your figures without your say-so.

Ask away

Besides the monthly flags, you can simply ask the controller a question, in your own words. It finds the answer in your own entity and shows where it comes from: which report, which account, which entry.

Easyclose · Virtual controller
Why did the margin drop in May?
Virtual controller The gross margin dropped from 32.1% to 30.4% in May. The largest cause sits with Techniek B.V.: one purchase delivery came in €9,800 more expensive than usual, posted on 18 May under entry INK-0244. Without that delivery the margin would have been 31.8%. P&L Maypurchase analysisentry INK-0244
Is that one-off or will it come back?
Virtual controller

Every amount the controller mentions is clickable down to the entry beneath it, with the same drill-down as everywhere in Easyclose. No invented figures, but a source with every answer.

Under your own security

A controller who watches along must never see more than you do. That is why the virtual controller works under exactly the same isolation as your own account: it queries your data with your permissions, and secrets stay server-side.

Never sees more than you

The AI queries your figures with your permissions (Row Level Security per organisation). By definition it cannot see anything you are not allowed to see yourself, no exceptions.

Secrets stay server-side

API keys and other secrets are never in your browser and never in the code that reaches you. Everything sensitive stays on the server side.

No black box

Every figure the controller mentions stays traceable to the entry in your own entity. More about security →

How you will work with your virtual controller

No dashboards to build, no alerts to configure. The controller gets to know your figures and the work divides itself: it does the digging, you take the decisions.

STEP 1

The controller watches along every month

As soon as your figures are in, it walks through them: P&L, balance sheet, budget and liquidity, per BV and consolidated, set against the pattern of the past twelve months.

STEP 2

You get flags with the why

Only variances larger than the normal fluctuation reach you, with the explanation attached: which BV, which cost type, which entry.

STEP 3

You decide what happens with it

Every flag comes with a proposed action. Carry it out, adjust it or ignore it: the choice always stays with you, and nothing changes without your say-so.

The virtual controller is on its way

We are now building out the virtual controller as part of Easyclose. The building blocks it leans on, your figures, the drill-down to the entry and the flags in the reports, you can already try in the demo today, entirely in your browser with fictitious figures.

  • Only flags what is larger than the normal fluctuation
  • Explains the why: which BV, which cost type, which entry
  • Proposes concrete actions, you decide
  • Under your own security, every figure traceable
Want to be first to try it? Email hallo@easyclose.nl

Frequently asked questions

What does the AI see of my data?

Only your own figures, under exactly the same isolation as you (Row Level Security per organisation). The AI never sees more than you are allowed to see, and your data does not leave your protected EU environment. Secrets such as API keys stay server-side.

Does it invent figures?

No. Every amount the controller mentions comes from your own entity and stays clickable down to the underlying entry, with the same drill-down as everywhere in Easyclose. What does not come from your figures, it does not mention.

When will the virtual controller be available?

It is in there now, in beta. In the app you find it under Reports: the monthly flags with band and drill-down, the AI explanation with proposed actions and the chat on your own figures. The flags and drill-down (without AI) you can explore directly in the demo. If you run into anything, email hallo@easyclose.nl.

Does it cost extra?

That is not final yet. Honestly: the price follows once the feature is there, and we will announce it clearly in advance. Nothing about what you pay ever changes quietly.

Can I switch it off?

Yes. In Easyclose you set AI consent per feature: you decide which AI features are on and which are not. Switch the virtual controller off and nothing watches along, while the rest of Easyclose simply keeps working.

Does it work together with my own AI via MCP?

Yes. The virtual controller is the built-in variant; through the MCP connection you can also put your own AI, such as Claude or ChatGPT, safely on your own figures. Both work under the same isolation and never see more than you.