By department · Controllership

Controllership needs to keep the train on the rails. Spreadsheets only show the derailment after it happens.

Abstra connects spend intent, budget, policy and ERP: it checks cost-center balance, routes approval tiers, records decisions and returns budget vs. actual and variances to managers and controllership, without waiting for month-end.

Book a controllership demo See controllership processes

The controllership pipeline

1
Capture
Requisition, internal purchase, travel, card spend, provision or consumption spreadsheet
2
Validate
Budget balance, cost center, project, policy and approval-tier rules
3
Control
Approve, block or request a change before the purchase order or posting
4
Report
Budget vs. actual, variances by area and alerts for whoever needs to act

Exceptions do not disappear in email: spend without budget, outside policy or above the approval tier becomes a task with an owner and a trail.

Workflow example · preventive control and budget vs. actual · 100% customized per customer

1 · Before the spend

Capture requestrequest, travel, card · spend intent

Validate budget and tierCC balance · policy · approval tier

Within rules → continues

If no balance / off ruleopens exception and returns

Authorized exceptionblock, adjust or approve with authority

with owner · audit trail

2 · Actuals follow-up

Read actuals in SAPpost-spend postings · already happened

Budget vs. actual and variancealert for the area and for controllership

Dashboard example · real time, connected and 100% customized

Balance, approval tiers and variances in one view

Illustrative data for demonstration.

within the rules

last 30 days

Requests this month

1.240

Within the rules

88%

No balance / off policy

Awaiting approval

Budget variance YTD

+4,2%

Cost centers

Month control

From capture to report

01
Captured
1.240
request and T&E · intent
02
Within the rules
88%
passed balance and policy · not automatic approval
03
With restriction
96
no balance or off policy · preventive alert
04
Awaiting approval
34
depend on an authorized owner
05
Actuals variances
41
budget × ERP · area and controllership

Mix

How requests closed

Within rules88%
No balance5%
Off policy3%
Awaiting tier4%

By cost center

Budget vs. actual YTD

BudgetActual

Marketing+12%
Ops+6%
Product+1%
Board+4%

Bars by variance magnitude · + = actuals above budget.

Live queue

Items that need attention

CT-220
CC-440 · Marketing
No balance
R$ 28k request · CC balance R$ 4k · preventive alert
CT-118
Travel · off policy
Policy
Business class · needs exceptional approval
CT-055
CC-055 Board · +4%
Variance
Budget vs. actual YTD · ask for an action plan

What controllership automation is

Controllership automation is the pipeline that captures spend intent, validates budget balance and policy, applies approval tiers before the purchase order or posting and publishes budget vs. actual with a trail. With Abstra, balance and tier control happen at spend intent — requisition, travel or card — not only at month-end close.

Proof in controllership

Numbers that matter to whoever controls spend.

Budget vs. actual and manager queries without spreadsheets

In the Medway case, budget versus actual tracking, approvals and expenses integrated with Omie, with managers checking their area’s financial health without relying on finance’s Excel.

Tax and management bases consolidated for analysis

At BeFly, spreadsheets and multi-entity data consolidated into dashboards for calculation, branch analysis and management exports used by the control team.

If your controllership looks like this, we fix it.

“Cost-center balance lives in a spreadsheet. The purchase order is already out when we see the overrun.”

“Budget vs. actual only closes after month-end. Leadership asks about the variance and we are still building the spreadsheet.”

“Every area spends at its own pace. Controllership finds out in the mid-year clawback, not at the moment of spend intent.”

“Reimbursement, travel and internal purchase policy depend on memory and email. Audit cannot find the evidence.”

Spend intent

Balance and tier control at spend intent — before the purchase order.

Requisition, travel, card or internal purchase go through the same rule: balance by cost center, project, policy and tier. What does not match becomes a task; what is approved proceeds with evidence for audit.

Real-time budget balance

Before releasing the requisition, the flow checks balance by cost center and project — spreadsheet, ERP or mixed base, per your operation.

See process

Tiers by amount, area and policy

Amount above limit, sensitive vendor or category outside policy routes to the right approver, with history and deadline.

See process

Block or adjust before the ERP

Without balance or approval, the purchase order or posting does not proceed. Documented exception, not a lost email.

See process

Manager sees consumption; controllership sees the trail

Budget vs. actual and variance by directorate fed by the approval flow — Medway and other customers query without relying on finance’s Excel.

See process

Where to automate first

How balance control at spend intent works

Budgeting, budget vs. actual, KPIs, approval tiers, expense policies and closing. Start with the process that blocks control the most.

Corporate budgeting

Budget base by area and cost center, with versioning and approval, so control has a trusted balance.

See process

Management reports

Budget vs. actual and open items published without hand-building Excel every month.

See process

KPI analysis

Variances and KPIs from validated sources, with alerts to the area and to controllership.

See process

Approval workflows

Approval tiers, cost centers and policy applied at spend intent, before posting.

See process

Reimbursements and expenses

Travel, reimbursement and card policy with evidence, review and an audit trail.

See process

Month-end close

Bases and cross-checks prepared for the close cycle, with traceable discrepancies.

See process

Abstra vs balance spreadsheet, ERP budget module and BI

What changes when control must act at spend intent — not only report variance at close.

Criterion	Abstra	Balance spreadsheet	Budget module (GKO…)	BI / dashboard
When control happens	At requisition, travel or card, before the PO	Manual update, always late	Blocks PO in ERP, if configured	After posting in the ERP
Balance by cost center	ERP + spreadsheet + rule in the same flow	Parallel source, conflict with ERP	Native in ERP, expensive license	Aggregation for visualization
Tiers and policy	Routing, evidence and approval trail	Email and manager memory	Limited to what the module exposes	Does not apply rules at the edge
Budget vs. actual	Fed by approval flow and ERP	Manual monthly build	Inside the ERP	Dashboard on closed data
Best for	Controllership without an expensive module, mixed stack and edge policy	Few cost centers, low volume	Single ERP with module already bought	Post-close management reporting only

Integrations

Connected to the ERP, expenses and spreadsheets controllership already uses.

Balance, tiers, cards and budget vs. actual. Native connector or spreadsheet read when there is no API.

200+ connectors and custom integrations

SAP

ERP

Microsoft Dynamics

ERP

Oracle

ERP

TOTVS

ERP

Google Sheets

Spreadsheets

NetSuite

ERP

SAP

ERP

Microsoft Dynamics

ERP

Oracle

ERP

TOTVS

ERP

Google Sheets

Spreadsheets

NetSuite

ERP

Microsoft Excel

Spreadsheets

Omie

ERP

Gmail

PostgreSQL

Data

BigQuery

Data

Snowflake

Data

Microsoft Excel

Spreadsheets

Omie

ERP

Gmail

PostgreSQL

Data

BigQuery

Data

Snowflake

Data

Slack

Alerts

Pipefy

Operations

Jira

Operations

Alerts

Slack

Alerts

Pipefy

Operations

Jira

Operations

Alerts

See all integrations

Beyond named cases

Real controllership patterns

Spend control by cost center

Before the purchase order, the flow checks budget balance, project and approval tier. No expensive ERP module, no parallel spreadsheet as the only source of truth.

Budget vs. actual for managers

ERP, accounts payable and spreadsheets feed a dashboard by directorate. The manager sees the variance; controllership sees the trail.

Policy at the edge (travel, reimbursement, cards)

Document read, rule applied, approval routed and ERP posting only after review, with history.

Multi-entity management view

P&L, KPIs and consolidations by entity/branch from synced bases, not a handmade close at month-end.

Controllership needs to validate balance at spend intent, apply tiers with evidence and publish budget vs. actual in time. A monthly report alone shows variance after spend is already off the rails.

Why not generic AI?

Frequently asked questions

Can you control balance before the purchase order?+

Yes. The flow checks balance by cost center and project at spend intent (requisition, travel, card). Without balance or tier approval, the PO or posting does not proceed — with a task and trail, as in the Medway case with Omie.

What is the difference between controllership and FP&A in Abstra?+

FP&A focuses on planning, forecasting and scenarios. Controllership focuses on spend control, approval tiers, policy, budget vs. actual and orchestrating what other areas do day to day. The pages overlap on budgeting and reporting, with a different focus.

Does Abstra replace the ERP budgeting module (like GKO)?+

Many companies never buy the module because it only blocks a purchase order without budget and costs a lot. Abstra orchestrates control at spend intent, in approvals and in reporting, connecting ERP, spreadsheets and teams, without depending on that module.

Can we start with our cost-center balance spreadsheets?+

Yes. The flow can start by reading Excel or Sheets and evolve into ERP checks, purchase requests and automatic alerts.

Does controllership also cover tax and accounting?+

They are neighboring scopes. In mid-size companies, controllership often owns part of management reporting and works with accounting and tax. On the site, tax and accounting have their own pages; here the focus is execution control, approval tiers and the management view.

Does AI decide whether a spend can go through?+

Automation applies the rule, flags the variance and routes the exception. The decision stays with the approval tier defined in the process, with approval and history.

Is it just a budget vs. actual dashboard?+

Viewing variance is one step. Controllership must block or approve at spend intent, record evidence and feed the report with a trail — as in BeFly’s management consolidation.

Where should we start?+

With the routine that most often busts balance or delays approval: purchase requisition, travel/reimbursement or budget vs. actual publishing. Use the processes below to go straight to the detail.

Execution capacity

Automate without building a technical team.

Abstra specialists map, implement and evolve finance automations with your team. Execution capacity without building an internal technical structure.

Abstra builds for you
Your team builds
Hybrid build

See implementation with specialists Talk to an expert

Bring a real approval flow. We’ll build control with you.

Balance by cost center, tier on requisition or budget vs. actual. A controllership demo with your operation’s rules.

Book a controllership demo Or explore the processes