GOVERNED AGENTIC FINOPS · WASCO × CALIBRAX
← → to move · G for overview · F for full screen
W A S C O  ×  C A L I B R A X

Governed Agentic FinOps

Enterprise FinOps reimagined through Agentic Intelligence
Auditable Autonomous Operation
GOVERN ORCHESTRATE OPTIMIZE
THE PREVAILING STATE|TODAY

What The Modules Process And What FinOps Carries

The platform's scope is fixed at the point it is configured. The commercial book is not, so the boundary between what is processed and what is carried moves further out every period.
THE PLATFORM MODULES
What the components process
The billing, revenue recognition, receivables and allocation components each post correctly for the contract structures they were configured against. Their scope is set at configuration and holds only for the structures anticipated at that point.
▶
THE CHANGE LAG*
What the delivered capability does not cover
New contract structures, entities and disclosure requirements are onboarded continuously. Whether the platform can process them is set by the functionality the vendor has delivered and by the internal configuration cycle, neither of which follows the reporting calendar.
▶
FINOPS
What finance operations carries
Until that capability arrives, those contracts are processed outside the platform modules. The treatment is derived from the contract, applied at case level in the offline schedules, and reconciled back into the ledger before the period is closed.
* The change lag is the elapsed distance between the period in which finance settles a treatment and the point at which the platform is able to process it, whether that waits on delivered vendor functionality or on the internal configuration cycle. It is measured in delivery cycles rather than days, and it stays open in every close until the capability arrives.
WHAT CARRIES THE CHANGE LAG TODAY
Custom development
ABAP AND EQUIVALENT INSIDE THE PLATFORM
Programs written in the platform's own language against its tables and transactions. They compute what standard configuration cannot, for the specific contract structures they were commissioned to handle.
Robotic automation
RPA REPLAYING THE SCREEN STEPS
Bots that repeat the keystrokes an analyst would use to move balances between components. They carry the repetition, and they hold only while the screens, fields and transaction paths stay as they were.
Offline configuration and record
TREATMENT RULES, MAPPINGS AND CASE SCHEDULES
Treatment rules, mapping tables and calculation logic maintained in spreadsheets and local tools, together with the record of what was applied to each case. The platform configuration is extended offline here, outside change control, version control and maker-checker review.
WHY THESE EXIST
A rational answer to a fixed capability boundary
The platform delivers the functionality its vendor has built, on the vendor's roadmap. Finance operations adapts the process to fit that capability, and where a commercial structure cannot be made to fit, it is carried outside the platform. Custom development, robotic automation and offline configuration are not shortcuts taken in place of a better option. They are what the function built to hold the reporting calendar inside that boundary, and they are the reason the close still lands on time.
WHAT THIS PRODUCES
The balances are held.
The basis is not.
Each of the three carries movement, calculation or storage. None of them is a system of record for the basis of the position. The determination of which policy a contract attracts, the analysis that resolves each variance to a cause, and the rationale that supports the number at audit sit inside finance operations and are re-established case by case in every close. The platform can reproduce the balance on demand. It cannot reproduce the basis on which that balance was accepted.
The next page sets out the eight frictions this produces and what they cost the close.  →
GOVERNED AGENTIC FINOPS · WASCO × CALIBRAXPAGE 2
HOW THE FRICTION ARISES|TODAY

Eight Frictions And What They Cost The Close

These are not eight separate problems to be solved individually. They are one boundary expressed eight ways, which is why each initiative aimed at them returns less than the one before.†
Where configuration reaches its limit
01
Configuration is delivered on the release calendar
New contract structures and entities are onboarded continuously. Whether the platform can process them is set by delivered vendor functionality and by the internal configuration cycle, on a calendar the reporting timetable does not control.
02
Treatment is conditional and configuration is uniform
No two contracts carry identical terms. Configuration applies one rule to every record matching its selection, so the condition that decides which treatment applies is held by the team and applied at case level.
What was built to extend it
03
Determinative treatment is maintained outside the modules
The offline configuration became where the treatment is maintained. Under a reporting deadline that was the correct operational call, and it places determinative logic outside change control, version control and maker-checker review.
04
Custom development and automation coupled the estate
Each addition is bound to specific screens, tables and transaction paths, so a component upgrade or a support pack forces regression testing and rework in everything built above it.
What finance operations carries every close
05
Two supportable answers have to be held together
The structure permits two defensible positions on the same balance, so reconciliation exists to hold the two in agreement rather than because transaction volume demands it.
06
Extraction and substantiation consume the front of the close
Each balance is extracted from its component and substantiated against source before any variance analysis can begin.
07
A query on a closed period is answered by reassembly
Substantiation sits across the components, the offline configuration and the review trail. Bringing it back together draws senior time out of the current reporting cycle.
08
Each new structure adds a permanent increment
Every entity onboarded, every contract type added and every new disclosure requirement introduces a manual step that persists in every close that follows.
† Close here means the periodic reporting close, covering the monthly and quarterly cycle from component cut-off through reconciliation, variance analysis and sign-off. It does not mean daily transaction processing, which the modules handle without intervention.
THE OPERATIONAL IMPACT
TIMING
The close absorbs the variance
Cases the delivered capability cannot process are cleared inside the reporting window, so effort concentrates between cut-off and sign-off and the reporting timetable sets the pace of the work.
CONTROL
Consistency of treatment depends on continuity of people
The treatment applied to a case is held by the preparer who applied it, so consistency of treatment across periods depends on the same people being available at the next close and on the working papers being read the same way.
CAPACITY
Capacity is consumed before analysis begins
Extraction, substantiation and pack assembly consume the front of every close, and the variance analysis the signed position rests on is funded from whatever capacity remains.
THE COMPOUNDING EFFECT
Each close inherits the last
None of the eight is retired by process improvement and none of them clears on its own. Each entity onboarded, each contract type added and each new disclosure requirement introduces a permanent step to the close and a permanent line to the reconciliation. The consequence is a close whose run rate rises with the balance sheet while the establishment supporting it stays flat, so the buffer between cut-off and sign-off narrows every period and the exposure concentrates in the days when there is least room to absorb it. Two figures make that visible without a study: elapsed days from cut-off to sign-off set against the same measure a year ago, and the time it now takes to substantiate a balance from two closes back.
Next, where the close is actually spent  →
GOVERNED AGENTIC FINOPS · WASCO × CALIBRAXPAGE 3
WHERE THE EFFORT SITS|TODAY

The Close Divides Into Preparation And Judgment

Both halves are booked to the same cost centre and reported as one number, which is why the split between them stays invisible until the close runs late.
PREPARATION LOAD
Preparation work
Extracting the position from each component
Billing, revenue recognition and receivables each post their own part of the same contract on their own cut-off. Consolidating them into one supportable position is not a step any single component owns.
Substantiating against the source documents
Certificates, contract clauses and the client register determine whether the posted balances are supportable. Each is retrieved and matched to the case before the schedule can be signed off.
Applying the treatment the configuration cannot process
Where no delivered configuration covers the structure, the treatment is derived from the contract and applied in the offline schedules, case by case, until the platform can process it.
Assembling the position and its supporting pack
Balances, substantiation and rationale are assembled into a pack a reviewer and an auditor can follow. That assembly repeats per case and per close with no carry-forward into the next period.
SIGNED ACCOUNTABILITY
Financial judgment
Determining which financial treatment applies
Which policy the contract attracts, whether retention or recognition steps on completion, and whether the precedent set last period still holds. The contract governs the answer, not the configuration.
Resolving each variance to a named cause
A reconciled total is an outcome rather than an explanation. Each variance is decomposed to a cause that can be evidenced against a document or a posting.
Clearing exceptions and open items
Anything unsupported by a source is carried as an open item and escalated, rather than absorbed into a named cause so the reconciliation clears.
Reviewing, approving and standing behind the position
Sign-off is where the position becomes final and where personal accountability attaches to whoever defends it at audit.
THE STRUCTURAL CONSEQUENCE
Preparation variance lands
entirely on judgment
The two halves run in sequence rather than in parallel. Judgment cannot begin until preparation completes, so every hour preparation overruns is an hour removed from the window in which the position is interrogated and signed. Preparation absorbs none of its own variability. All of it transfers into the judgment window, which is precisely where the audit exposure sits and where the least capacity exists to absorb it. That is why adding people to preparation buys time in a straight line while taking preparation off the critical path buys it disproportionately, and it is why this reads as a control case before it reads as an efficiency case.
The next page defines agentic AI and maps it against the frictions it addresses.  →
GOVERNED AGENTIC FINOPS · WASCO × CALIBRAXPAGE 4
DEFINITION AND MAPPING|BOTH

What Agentic AI Is And What It Addresses

Capability is the easier half of this. What decides whether it belongs inside a financial close is the permission set around it rather than the intelligence within it.
THE CAPABILITY
Agentic AI
A system given a case and a required outcome rather than a fixed sequence of steps. It is told what the completed position has to satisfy and determines the route to it.
WHY IT IS NOT AUTOMATION
It selects which component holds each balance, which clause governs the treatment and which document substantiates it. It carries the case record across the close without losing state, checks its own output back against source, and escalates any case matching no released treatment. Robotic automation replays a fixed screen path and halts at the first case it was not written for.
THE CAPABILITY UNDER CONTROL
Governed Agentic FinOps
The same capability with the treatment taken out of its hands. It applies the treatment finance authored at the version finance released, and it settles nothing on its own authority.
HOW A CASE RUNS THROUGH IT
A coordinator agent opens the case when the underlying balances post and requests each one from the component* that produced it. A reader agent is spawned for a single document, returns the certified figure with its stated cause, and closes. The released treatment is applied at the version held for that contract condition. The case is handed to a reconciliation agent, where each variance resolves to a named source, and it reaches the responsible person complete with its rationale.‡
ARCHITECTURAL POSITION
Platform agnostic
Nothing here replaces, re-implements or migrates a component*. The governed layer sits above whichever system of record is in place, reads the treatment logic lifted out of it, and requests posted balances from it. The same design holds across a single-vendor estate, a mixed estate or a future platform change.
* Component means the platform module that already posts your figures, covering billing, revenue recognition, receivables and allocations, whichever platform they run on.   ‡ The agents do not post, compute or restate a balance. Every figure is requested from the component that produced it and returned exactly as posted. The capability to calculate exists and is withheld by design, because lineage is only supportable if it points at a system of record rather than at the agent's own arithmetic.
HOW EACH FRICTION IS ADDRESSED
FRICTIONS 01 AND 02
Treatment comes from a released definition rather than a release cycle
A change of treatment is authored and versioned by finance and takes effect in the period it is approved. The same contract condition attracts the same treatment across every entity, without waiting on delivered platform capability.
FRICTIONS 03 AND 05
One maintained definition replaces two supportable positions
The determinative logic moves out of the offline configuration into a governed layer under version control, change management and maker-checker review. There is one released treatment to apply rather than two defensible balances to reconcile.
FRICTIONS 04 AND 06
Balances are requested from the component rather than read off the screen
Each request runs against the component that posted the balance rather than a screen path, so an upgrade beneath the platform does not force rework above it, and extraction stops consuming the front of the close.
FRICTIONS 07 AND 08
Substantiation is written as the work runs
Each variance resolves to a named source, lineage and provenance are written as it goes, and only cases matching no released treatment are escalated. Close effort tracks exceptions rather than entity count.
THE ACCOUNTABILITY BOUNDARY
Execution moves,
approval does not
The agents execute against a required outcome, plan their own route across the components, apply the released treatment they read from the governed layer, and evidence every step. What they never do is settle the treatment or release the position. Proposed treatment, resolved variances and any open item unsupported by a source arrive together for the responsible person to evaluate, amend, approve or override, and sign-off remains the control point at which accountability attaches.
Next, what governed means and how a closed position stays answerable  →
GOVERNED AGENTIC FINOPS · WASCO × CALIBRAXPAGE 5
WHAT GOVERNED MEANS|PROPOSED

What Is Governed And Why It Differs From Today

An audit does not test the balance. It tests whether the basis for the balance can be produced, which turns on what was recorded at the time rather than on what can be rebuilt now.
Lineage
EVERY BALANCE CARRIES ITS ORIGIN
Lineage records which component posted a balance and which version of which treatment was applied to it. It is written at the moment the balance is requested, so the position and its substantiation are produced in one act rather than two.
The gate
EVERY ACTION IS CHECKED BEFORE IT RUNS
A gate is a control point every action passes before it executes, in the same sense as a posting block or a release strategy. It reads the register of approved actions and answers two questions: is this action defined and pre-approved for a case of this kind, and is this actor cleared to take it here. If either answer is no the action stops and is escalated. The answer is recorded either way.
Provenance
EVERY ACTION CARRIES ITS AUTHORITY
Provenance records who authorised each action and under what delegated authority. The step that writes to the record performs no reasoning and holds the only write authority, and it confirms an approval exists before it acts.
WHAT IS GOVERNEDHOW IT IS HELD TODAYUNDER GOVERNED AGENTIC FINOPS
The treatment applied to a contract
POLICY LAYER · WHAT THE PERIOD IS CLOSED AGAINST
 Maintained in the offline configuration alongside the components and amended by the responsible person who maintains it. Authored by finance, versioned as written, and returned from the governed layer to every case meeting the same contract condition.
The treatment stops travelling with an individual and starts travelling with the case.
The balance and its substantiation
DATA LINEAGE · WHAT THE POSITION RESTS ON
 Extracted from its component and carried forward, with its origin known to the person who extracted it. Requested from the component that posted it, never recalculated in transit, and carried with its source and the treatment version applied.
The balance and its substantiation are produced together rather than assembled afterwards.
The action, the approval and the audit record
CONTROL TRAIL · WHAT AUDIT IS SHOWN
 Approval sits in the review step, and a correction is applied to the position so the earlier state is superseded. Every action passes a gate that records the actor and the authority, and a correction is posted as a reversal so the record is never amended in place.
The prior state stays readable, which is what a control review asks to see.
PRIOR PERIOD ENQUIRY AND AUDIT SUPPORT
The position is
re-presented on request
An enquiry on a closed period today means reassembling four things: the balances posted across the components, the treatment held in the offline configuration, the review trail that moved the case, and the judgment applied at the time. The first three are recoverable with effort. The fourth is rarely documented, which is what turns an enquiry into an investigation. Under the proposed model nothing is traced back. The control plane still holds the case record, the membrane logged every read and every write against the components, and the governed layer holds the treatment version applied, so the position, its variance analysis, its lineage and the approval that released it are re-presented together on request.
Basis of this claim. The behaviour described is the target state of the proposed model rather than an observed result in this environment. Establishing it against your own closed periods sits within the discovery scope and forms part of the prototype acceptance criteria agreed at gate one.
Next, who carries each step under each model  →
GOVERNED AGENTIC FINOPS · WASCO × CALIBRAXPAGE 6
THE OPERATING MODEL|PROPOSED

Who Carries Each Step Under Each Model

Nothing in the sequence is wrong and no step is removed. What moves is the ownership of each one, and with it the elapsed distance between cut-off and sign-off.
Extract the position
Substantiate against source
Apply the treatment
Resolve the variances
Review and approve
TODAY
Today's operating model
RPA BOT · ABAP · ANALYST
A bot replays the screen steps across the components and a custom program computes what standard configuration cannot. The analyst checks both before the output is used.
▶
ANALYST
Each balance is substantiated against its certificate, its contract clause or the client register and matched to the case.
▶
SHADOW RECORD · ANALYST
The treatment is read from the offline configuration that holds it and applied outside the components for this contract.
▶
ANALYST
Each variance is decomposed to a cause using the source documents and the component detail.
▶
ANALYST · REVIEWER
The pack is routed for review. A query returned at review sends the case back through the earlier steps.
Basis of the upper lane. This is a high level workflow logic layer generalised against typical ERP module components rather than an observed process in this business. The assumptions behind it require validation, and that validation is part of discovery with the FinOps team.
PROPOSED
Governed Agentic FinOps
AGENT CONTROL PLANE
Where the agents run and where one hands the case to the next. It holds the case record, so a case waiting on a certificate or held at cut-off resumes from the same state instead of being worked again from the start.
COORDINATOR AGENT
Owns the case from open through to handover. It raises the case once the underlying balances have posted and requests each one from the component that produced it.
▶
READER AGENT · SPAWNED BY THE COORDINATOR
A second agent created for one document only. It returns the certified figure with its stated cause and then closes.
▶
COORDINATOR AGENT
The treatment is read from the governed layer at the version finance released for that contract condition.
▶
RECONCILIATION AGENT · CASE HANDED OVER
The case passes to a third agent. Each variance resolves to a named source and the proposed position is assembled with its rationale attached.
▶
YOU · REVIEW AND APPROVAL
The case reaches you complete. You evaluate the proposed treatment, amend it, approve it or override it.
ONE CONTROLLED INTERFACE
THE MEMBRANE
The single controlled interface between the agents and your platform components. Every read at steps one to three and every write at step five passes through it and is logged. No agent reaches a component by any other route, and no agent holds a write credential of its own.
WHAT THE AGENTS READ
GOVERNED
SEMANTIC LAYER
Holds the determinative treatment lifted out of the components, the custom programs and the offline configuration, together with the treatment know-how the team has carried. Authored and versioned by finance, and read by every agent above it.
THE OBJECTIVE
Collapse the offline estate
and the elapsed close
Removing the manual assembly is the visible part. The objective is the estate around it: the offline schedules, the custom extensions and the screen-driven automation built to hold the capability boundary, together with the effort they consume and the elapsed days they add between cut-off and sign-off. Treatment stops waiting on a delivery cycle, assembly stops running case by case, and the workaround layer stops needing maintenance of its own. What reaches the reviewer is a proposed position with its variance analysis and substantiation already attached.
Next, the mechanism against each friction  →
GOVERNED AGENTIC FINOPS · WASCO × CALIBRAXPAGE 7
MECHANISM AGAINST FRICTION|BOTH

The Mechanism Answering Each Friction

Eight frictions are answered by five mechanisms rather than by eight remediations, which is the difference between a programme of fixes and a change of operating model.
CLUSTER
THE FRICTION TODAY
WHAT CARRIES IT UNDER THE PROPOSED MODEL
WHAT CHANGES INSIDE A CLOSE
Where configuration reaches its limit
01 – 02
01Configuration is delivered on the release calendar
GOVERNED DEFINITIONThe treatment is authored and versioned by finance in the governed layer instead of waiting on delivered platform capability
A treatment change applies from the period it is approved rather than from the next delivery cycle
02Treatment is conditional and configuration is uniform
GOVERNED DEFINITIONThe coordinating agent reads the contract condition from the case and applies the released treatment version held for it, escalating anything matching none
The same contract condition attracts the same treatment across every entity and every period
What was built to extend it
03 – 04
03Determinative treatment is maintained outside the modules
GOVERNED DEFINITIONThe determinative logic moves out of the offline configuration into the governed layer, under version control, change management and maker-checker review
The treatment sits under change control rather than with the preparer maintaining it
04Custom development and automation coupled the estate
THE MEMBRANEEvery request passes the membrane to the component that posted the balance, so nothing is bound to a screen, a table or a transaction path
A component upgrade or support pack stops triggering regression testing and rework in the layers above
What finance operations carries every close
05 – 08
05Two supportable answers have to be held together
GOVERNED DEFINITIONOne released treatment is read from the governed layer and applied identically to every case meeting its contract condition
Reconciliation narrows to the balances that genuinely require a decision
06Extraction and substantiation consume the front of the close
AGENT CONTROL PLANEA reader agent is raised against one source only, returns the certified figure with its stated cause, and then closes
The close reaches variance analysis earlier in the reporting window
07A query on a closed period is answered by reassembly
LINEAGE AND PROVENANCELineage and provenance are written as each balance, treatment version and approval is used, so a closed position is re-presented rather than reconstructed
A prior period enquiry is answered without drawing capacity from the current close
08Each new structure adds a permanent increment
EXCEPTION HANDLINGOnly cases matching no released treatment are escalated to the responsible person, and the remainder clear against the treatment held
Close effort stops scaling with entity and contract count
THE PATTERN
Close effort stops scaling
with the balance sheet
Today the work in a close is set by how many entities and contract types the business carries, because each one introduces a manual step that persists. Under the proposed model the work is set by how many cases fall outside a released treatment and therefore require a decision. Onboarding an entity stops adding a permanent line to the close. For the first time the effort curve is flat against growth and rises only where genuine judgment is needed.
Next, the discovery engagement and the decision at gate one  →
GOVERNED AGENTIC FINOPS · WASCO × CALIBRAXPAGE 8
THE ENGAGEMENT|PROPOSED

Discovery And The Decision At Gate One

Gate one is a decision point rather than a commitment. Discovery is scoped so that either answer can be reached inside five working days, and the baseline it produces stays with the team either way.
STAGE ONE
Discovery
FIVE WORKING DAYS
GATE ONE OUTPUT
An agreed picture of how the close runs today, a validated view of which frictions are present and at what scale, and a defined scope for a prototype. Yours to keep whatever is decided at the gate.
▶
STAGE TWO
Prototype and parallel run
SCOPED AT GATE ONE
GATE TWO OUTPUT
Results from real cases run alongside the close, measured against criteria agreed in advance. Enough evidence to commission a build or to decline one.
▶
STAGE THREE
Design and build
SCOPED AT GATE TWO
GATE THREE OUTPUT
A tested process running in shadow against the live close. Moving from shadow to supervised operation is a separate decision at the gate.
▶
STAGE FOUR
Run and compound
ONGOING
WHAT IT BECOMES
Operated inside finance, with treatments corrected as cases expose them and the substantiation record accumulating close by close.
WHAT DISCOVERY IS
A joint discovery
with your FinOps team
Our deployment team works alongside your FinOps team to establish how the close actually runs, to test which of the eight frictions are present in this environment and at what scale, to confirm whether the proposed model is viable against the platform estate already in place, and to set the prototype acceptance criteria. The finding that matters most is the one that says no. If the frictions are not present at the scale assumed, that is established inside five working days rather than after a build, and the measured baseline produced remains yours either way.
WHAT DISCOVERY DRAWS ON
Team time against an agreed discovery scope
Six to eight hours across five working days, scheduled around the close rather than inside it. Read-only sight of an agreed contract set. An agreed scope boundary stating which process and entity are examined and which are not. An agreed delivery defining what discovery hands back at gate one. All three are fixed in writing before discovery begins.
WHAT DISCOVERY COVERS
One process and one entity
A single process and entity, examined alongside the live close without interrupting it. The output is a measured baseline of your own period, and it stays with you regardless of what is decided at gate one.
THE WORKED WALKTHROUGH
One contract, end to end
The follow-up session takes a single contract through the full sequence, showing the coordinator, the reader agent, the membrane, the governed layer and the approval point operating against the components already in place.
GOVERNED AGENTIC FINOPS · WASCO × CALIBRAXPAGE 9
01 / 09