An example of revenue assurance leakage recovery as a governed process: agents do the 8 steps, and a person signs the gate before anything irreversible happens. Download it, import it into your workspace, and adapt it to your systems.
The graph8 agent steps1 human gatesigns: Revenue-assurance (RA) lead / Director of Revenue Assurance
Revenue-leakage recovery autopilot
Carriers leak 1-10% of revenue because provisioning, network-usage, rating and billing run on disjoint systems that are only sample-reconciled, so un-billed and under-billed services go undetected for months. Recovery today is manual spreadsheet detective work, and any back-billing, write-off or rating change touches customers and the financial statements — so it cannot be left to an automated process. An agent reconciles 100% of records across all four domains continuously, quantifies the dollar impact of every discrepancy, and drafts a recovery or correction case with full evidence. Only genuine money-moves — back-billing a customer, writing off a leak, or changing a billing-config rule — reach the RA lead, who signs every irreversible action.
The governed flow · branches, parallel work & a human on the irreversible step
immaterial / no money-moveback-bill / write-off / config changeapprovedrework — insufficient evidence / wrong root cause
Start
agent · low risk
Ingest the full population of provisioning, network-usage (CDR/IPDR), rating and billing records from OSS, mediation and the billing stack
agent · medium risk
Reconcile 100% of records across all four domains to surface un-billed, under-billed and mis-rated services (no sampling)
parallel · fan-out / join
Quantify and classify each surfaced discrepancy concurrently
agent · medium risk
Quantify the dollar leakage per discrepancy and its billing-period exposure from rated vs billed deltas
agent · medium risk
Classify root cause (provisioning gap, rating error, mediation drop, billing-config defect) and attach the evidence trail
parallel · fan-out / join
Merge quantified impact and classified root cause into one case
decision
Discrepancy disposition?
agent · low risk
Immaterial / no money-move (timing artifact, already-billed, below materiality threshold): auto-close the case and log the disposition — fully reversible, no customer or ledger impact
agent · medium risk
Money-move required: assemble the back-bill / write-off / billing-config correction case with quantified impact, root cause and full evidence for sign-off
gate · human sign-off
The RA lead reviews the case and signs, or sends it back for rework, every back-bill, write-off and systemic billing-config change (customer-facing + financial-statement impact)signs: Revenue-assurance lead (Director, Revenue Assurance)
decision
Case approved?
agent · high riskirreversible
Post the approved billing adjustment, back-bill or rating-config correction to the billing system and ledger
agent · low risk
Track recovered dollars and leakage trend, and feed confirmed leak patterns back into the recon ruleset
Done
low riskmedium riskhigh riskbranch / reworkgate · human sign-off
Use this example
01
Download the file
A minctrl.process/v1 document: the graph and the hash of the process it becomes.
02
Import it in Processes
Import into Minctrl opens this example in your workspace; one click stores it as your first version. Import JSON does the same with the file, and a file changed after download is refused.
03
Connect your systems
Every connector starts in shadow: steps run, nothing leaves Minctrl until you configure a connector and switch it live.
04
Adapt it
Change signers, time limits and steps on the canvas. Each save is a new version; a running case stays on the version it started with.
Questions
How do I automate revenue assurance leakage recovery with Minctrl?+
Start from this example. Import the file in Processes, connect your own systems, and adapt the steps on the canvas. Agents run the reversible steps; every irreversible step waits at a gate for the role you choose. The example has 8 steps and 1 gate; you can change any of them.
Is revenue assurance leakage recovery in Minctrl auditable?+
Every run start, signature and change to the process is written to a hash-chained audit log your auditor can verify and export. A run is pinned to the exact graph it started on.
Does the AI decide everything?+
No. Minctrl will not make a process runnable while an irreversible step can be reached without a human gate, and one person cannot sign two gates of the same run.