← THE PORTAL
FINANCIAL TRUTH & TRUST · CONTROLLERSHIP / CLOSE

From the close scramble to a continuous-readiness loop.

Today, the close is a checklist and an evidence scramble, every month. In Future Finance, reconciliations run continuously, evidence assembles as the work happens, and close readiness is a visible state days before the window opens.
LEARNING RETURN 01 SIGNAL exception forms · recon breaks 02 EXPOSURE close risk · readiness gap sized 03 CHOICE resolve {D} escalate 04 OWNER ACTION controller {D} accountant 05 OUTCOME was it ready early? EVIDENCE GATE 06 · VALUE PROOF certification evidence complete The governed loop, cast for this function – the same circuit as every Finance function, carrying close readiness risk instead of a report.
01 · THE TRANSFORMATION

From the close scramble to a continuous-readiness loop.

TODAY
The checklist. The evidence scramble. Every month.
Reconciliations run at period end.
Exceptions found late, without support.
Readiness unknown until the window opens.
IN FUTURE FINANCE
Reconciliations and tie-outs run continuously
Evidence assembles as the work happens
Exceptions arrive pre-supported, with lineage
Close readiness visible days before the window {D} by entity, by account
CLOSE READINESS → ACTION ROUTE
02 · WHERE TO START – THE WORKFLOWS, RANKED

Four workflows. One operating pattern.

Every workflow in this function becomes the same governed loop – cast differently. Below, each one in full: what it becomes, who does what, what it needs, and where the human boundary sits.
RANKED BY · ownership (who holds the lever) · value (from this domain’s sizing) · autonomy ceiling (Tier 1 = human-only → Tier 4 = highest permitted autonomy) · control sensitivity · scope (core vs conditional)   weighting leans value + ownership
AGENTS prepare DETERMINISTIC SYSTEMS calculate HUMANS approve OWNERS execute FINANCE validates
1Tier 4 of 4
Close management
Close management becomes a governed certification workflow {D} readiness visible by entity and account, exceptions pre-supported, and signoff kept human.
Who does what
Agentsassemble close status and pre-support exceptions
Systemsrun reconciliations and tie-outs continuously
Humanssignoff is human-owned
Financevalidates readiness by entity and account
ARCHETYPE close-to-certificationCADENCE monthly / quarterlyDATA close workflow · evidenceSENSITIVITY high
THE BOUNDARY · signoff is human-owned; the workflow assembles readiness, it does not certify the close.
OWNERSHIP Finance ownsVALUE High – feeds the sized poolAUTONOMY Tier 4 of 4CONTROL High sensitivitySCOPE Core
2Tier 2 of 4
Account reconciliations
Reconciliations become deterministic, with agent commentary {D} recons run continuously by registered logic, exceptions explained by agents, and resolution approved by a person.
Who does what
Agentsexplain reconciliation exceptions
Systemsreconcile deterministically – registered services
Humansreview and approve exception resolution
ARCHETYPE close-to-certificationCADENCE continuousDATA reconciliation servicesSENSITIVITY high
THE BOUNDARY · exceptions are human-reviewed; recon logic is deterministic and versioned, never agent math.
OWNERSHIP Finance ownsVALUE High – feeds the sized poolAUTONOMY Tier 2 of 4CONTROL High sensitivitySCOPE Core
3Tier 2 of 4
Journal entry and accrual review
Journal and accrual review becomes evidence-first {D} entries prepared with support attached, anomalies flagged, and approval kept human.
Who does what
Agentsprepare entries with support; flag anomalies
Systemscalculate accruals against policy
Humansapprove journals and accruals
ARCHETYPE close-to-certificationCADENCE monthlyDATA GL · subledgers · policySENSITIVITY high
THE BOUNDARY · journals and accruals are human-approved; agents prepare, they do not post to the ledger unreviewed.
OWNERSHIP Finance ownsVALUE Medium – close effortAUTONOMY Tier 2 of 4CONTROL High sensitivitySCOPE Core
4Tier 2 of 4
Consolidation and reporting package
Consolidation becomes assembled evidence {D} the reporting package built with tie-outs and lineage, and the package signed off by a person.
ranked last: deterministic assembly with human signoff.
Who does what
Agentsassemble the reporting package with tie-outs
Systemsconsolidate deterministically with lineage
Humanssign off the package
ARCHETYPE close-to-certificationCADENCE monthly / quarterlyDATA consolidation · lineageSENSITIVITY high
THE BOUNDARY · the package is human-signed-off; consolidation is deterministic, lineage-tracked.
OWNERSHIP Finance ownsVALUE Medium – close effortAUTONOMY Tier 2 of 4CONTROL High sensitivitySCOPE Core
03 · THE SIZING – FULL EVIDENCE TRAIL

The number, carried the way every claim is carried.

The figure on the front page arrives here as what it is – a governed packet. Range, basis, inputs, benchmarks, derivation, assumptions, and the strongest objection to it, all in one place.
CONTROLLERSHIP SIZING PACKET
CLOSE-SZ-09 · CLOSE-EFFORT POOL
OUTSIDE-IN
RANGE
$5–20M / yr · effort redeployment
BASIS
Hybrid · Confidence: Medium
WHAT IT IS
Continuous close readiness redeploys close and record-to-report effort {D} a shorter, calmer close, a team on judgment rather than assembly. Expressed as effort-cost redeployment, never headcount reduction. Supplemented by the close-days metric.
INPUTS
Total finance-function cost of a representative large-cap SaaS company (derived from an APQC cost-of-finance benchmark); effort-reduction applied as a share
BENCHMARKS
Finance-function cost as % revenue (APQC OSB; top-performers ~0.4%, laggards to 1.8%) · close-cycle day benchmarks (APQC)
DERIVATION
1 · close/record-to-report envelope derived from finance-function cost
2 · continuous readiness reduces 15–35% of that effort
3 · range → ~$5M/yr low · ~$20M/yr high · redeployed, not cut
ASSUMPTIONS
(1) close envelope derived from finance-cost benchmark · (2) 15–35% effort reduction (assumed) · (3) redeployment, never headcount reduction
SENSITIVITY
The effort-reduction share moves it most – halving to 7.5–17.5% gives ~$2.5M–10M/yrsanity bound: cannot exceed the benchmarked cost of the close/R2R function it draws from
THE ATTACK
“This is just a headcount-cut claim in disguise.” — No: it is effort-cost redeployment expressed in dollars, explicitly not a headcount-reduction figure; the team moves from assembly to judgment, and the close-days metric carries the operational proof.
OUTSIDE-IN · ILLUSTRATIVE · SUBJECT TO VALIDATION
Modeled on a Representative SaaS Company · outside-in, illustrative
A target-state vision · every value claim subject to validation