← THE PORTAL
ECONOMIC VALUE CONTROL · FINANCE OPERATIONS · AR / AP / BILLING

From queue triage to an exception-to-owner loop.

Today, operations is queue triage and blockers age until someone notices. In Future Finance, exceptions are detected, sized, and routed the day they occur, billing blockers arrive with exposure and evidence attached, and root causes are surfaced, not just symptoms.
LEARNING RETURN 01 SIGNAL exception occurs · blocker {D} dispute 02 EXPOSURE cash at risk · exposure sized 03 CHOICE resolve {D} escalate {D} credit 04 OWNER ACTION billing {D} account owner 05 OUTCOME did it clear faster? EVIDENCE GATE 06 · VALUE PROOF recovery validated The governed loop, cast for this function – the same circuit as every Finance function, carrying billing blocker risk instead of a report.
01 · THE TRANSFORMATION

From queue triage to an exception-to-owner loop.

TODAY
Queue triage and manual escalation.
Blockers age until someone notices.
Disputes worked in arrival order, not by exposure.
Root causes lost in the volume.
IN FUTURE FINANCE
Exceptions detected, sized, and routed the day they occur
Billing blockers arrive with exposure and evidence attached
Aging visible to everyone {D} nothing buried in a queue
Root causes surfaced, not just symptoms
BILLING BLOCKER → ACTION ROUTE
02 · WHERE TO START – THE WORKFLOWS, RANKED

Five 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
Billings / DSO / collections / disputes
Aging follow-up becomes a closed-loop dispute and collections workflow {D} cases prepared with DSO and cash impact, sensitive actions approved by a person, and owners resolving the blocker.
Who does what
Agentsprepare dispute and collections cases with cash impact
Systemscalculate DSO, aging, and overdue exposure
Humansapprove sensitive escalation, credits, write-offs
Ownersaccount and billing owners resolve issues
Financevalidates cash collected and aging improvement
ARCHETYPE signal-to-actionCADENCE daily / weeklyDATA AR · billing · CRM · contractsSENSITIVITY medium-high
THE BOUNDARY · credits, write-offs, and escalations are human-approved; owners resolve, Finance validates the recovery.
OWNERSHIP Finance ownsVALUE High – feeds the sized poolAUTONOMY Tier 4 of 4CONTROL Med-high sensitivitySCOPE Core
2Tier 4 of 4
AP exception handling
AP queue triage becomes routed exception packets {D} invoice/PO mismatches summarized, matched deterministically, and exceptions approved with SLA tracking.
Who does what
Agentssummarize AP exceptions with context
Systemsmatch invoice to PO and receipt
Humansapprove exceptions
ARCHETYPE signal-to-actionCADENCE daily / weeklyDATA AP · PO · vendorSENSITIVITY medium
THE BOUNDARY · exceptions are human-approved; matching is deterministic, payment stays controlled.
OWNERSHIP Finance ownsVALUE Medium – cycle efficiencyAUTONOMY Tier 4 of 4CONTROL Medium sensitivitySCOPE Core
3Tier 3 of 4
Credit, adjustments, and write-off routing
Manual approval chains become a governed approval workflow {D} evidence assembled, impact calculated, and every credit or write-off human-approved against delegation-of-authority.
Who does what
Agentsassemble the evidence for the adjustment
Systemscalculate the credit/write-off impact
Humanshuman approval required against DOA
ARCHETYPE policy-to-complianceCADENCE event-drivenDATA customer · invoice · policy · DOASENSITIVITY high
THE BOUNDARY · credits and write-offs are human-approved against DOA; the workflow assembles evidence, it does not adjust.
OWNERSHIP Finance ownsVALUE Control + leakageAUTONOMY Tier 3 of 4CONTROL High sensitivitySCOPE Core
4Tier 4 of 4
Order-to-cash finance operations
Fragmented handoffs become a monitored O2C workflow {D} order, billing, revenue, and cash handoffs monitored end to end, with process owners remediating.
Who does what
Agentsmonitor handoffs and surface breaks
Systemsreconcile across order, billing, revenue, cash
Ownersprocess owners remediate the breaks
ARCHETYPE signal-to-actionCADENCE daily / monthlyDATA CRM · CPQ · billing · ARSENSITIVITY medium
THE BOUNDARY · process owners remediate; Finance stewards the flow, it does not own every upstream system.
OWNERSHIP Finance stewardVALUE Medium – cleaner booksAUTONOMY Tier 4 of 4CONTROL Medium sensitivitySCOPE Core
5Tier 4 of 4
Process SLA and queue management
Manual status chasing becomes workflow status, reminders, and escalation {D} SLAs monitored, queues tracked, and low-risk reminders automated.
ranked last: lowest-risk, reminder-level automation.
Who does what
Agentsmonitor SLAs and send low-risk reminders
Systemstrack queue status
Humanshandle the exceptions
ARCHETYPE signal-to-actionCADENCE dailyDATA queue / SLA toolingSENSITIVITY low
THE BOUNDARY · only low-risk reminders are automated; exceptions route to a person.
OWNERSHIP Finance ownsVALUE EfficiencyAUTONOMY Tier 4 of 4CONTROL Low 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.
FINANCE OPERATIONS SIZING PACKET
FOPS-SZ-07 · BILLING-LEAKAGE POOL
OUTSIDE-IN
RANGE
$8–35M / yr · annual recurring
BASIS
Hybrid · Confidence: Medium
WHAT IT IS
Governed order-to-cash loops recover billing errors and invalid deductions and shorten dispute cycles. This is P&L / process value {D} distinct from Treasury’s one-time cash release. Conditioned on billing and collections owners acting.
INPUTS
Total revenue and accounts receivable of a representative large-cap SaaS company; leakage applied as a share of revenue
BENCHMARKS
Revenue leakage 3–5% typical, <1% top-quartile (MGI / EY / academic) · billing errors ~38% of leakage causes · revenue-assurance recovery (TM Forum) · invalid-deduction write-offs (Serrala)
DERIVATION
1 · top-quartile-leaning leakage rate 0.5–1.5% of revenue (reject the 3–5% headline)
2 · billing/collections/deduction share ~40% of causes
3 · addressable recovery 30–60% → ~$8M/yr low · ~$35M/yr high
ASSUMPTIONS
(1) leakage 0.5–1.5% of revenue (haircut for maturity) · (2) billing/collection share ~40% · (3) recovery 30–60% · (4) dunning minimal given B2B/channel model
SENSITIVITY
The leakage rate moves it most – halving to 0.25–0.75% gives ~$4M–18M/yrsanity bound: high end ($35M) is 0.38% of revenue – well under even vendor-inflated 1–2% figures, recovery share under best-in-class
THE ATTACK
“Leakage studies are vendor pitches.” — The packet uses a top-quartile leakage rate (not the 3–5% typical), splits it by documented cause weight, applies a partial recovery share, and separates cleanly from the Treasury cash release.
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