revenuelytics.aiAI-centric revenue assurance

AI-centric revenue assurance

What the state is owed, rebuilt from records the operator does not control.

AI agents rebuild each operator's revenue base from counterparties, settlement systems and regulators, then reconcile it with what was declared and paid. A practitioner reports every difference as a factual finding under ISRS 4400.

Built for Auditors-General Revenue authorities Sector regulators Ministries of finance Universal service funds

Working paper C-4 · Operator 03 · FY2024/25

One finding, traced from source to signature
Illustrative
  1. Agent 1 · Ingest1.9bn usage records from 4 counterparties and 312 settlement invoices, profiled and matched.
  2. Agent 2 · Read the lawExcise at 17% of service revenue. Gazette notice p.14, in force all year.
  3. Agent 3 · ReconcileRebuilt base 2,540.6m. Declared 2,427.1m across 12 monthly returns.
  4. Agent 4 · Build the evidenceDifference of 19.3m in excise. Every figure linked to its source rows and hash-sealed.
  5. PractitionerReviewed and signed as a factual finding under ISRS 4400. No opinion, no estimate.Reviewed · working paper C-4
Currency mSealed 7f3a…c91eFigures are illustrative

Why declared figures cannot check themselves

The systems that verify operator revenue are fed by the operators.

Electronic returns, licence-fee filings and revenue assurance platforms all start from the licensee's own numbers. They can show that a return disagrees with itself. They cannot show that it is too low.

2 of 24

Operator-years that one revenue authority had tax-audited in its telecom sector over four years.

Performance audit published by a national audit office, 2020
99%

The gap between one operator's declared sales and the authority's own reconciliation, in the audits that were done.

Same report
1 year

Sector VAT and excise paid and never verified, because the monitoring system was offline.

Same report

How the agents work

Four agents read every record. One practitioner signs every finding.

A five-year sector review means billions of usage records, thousands of settlement invoices and every gazette notice that changed a rate. Audit teams sample that volume because they have to. The agents work through all of it, so practitioners spend their time on the differences.

  1. Agent 1

    Ingest

    Takes traffic, billing, settlement and ledger data in each source's own format. Profiles it, normalises it and flags gaps before matching starts.

  2. Agent 2

    Read the law

    Turns licences, tariff filings, gazette notices and tax schedules into dated, machine-readable rules. Each rule cites the page it came from.

  3. Agent 3

    Reconcile

    Matches every record to its counterparty, applies the rule in force on that date and ranks the differences by value.

  4. Agent 4

    Build the evidence

    Drafts the working paper, links every figure to its source rows and hash-seals each stage before review.

  5. Practitioner

    Sign

    Reviews each difference against the source, decides what is a finding and signs the working paper. Nothing is reported that a person has not checked.

The agents do

  • Test the full population. Every record for every month, instead of a sample chosen by hand.
  • Apply the rate in force on each date. A gazette change in the middle of the year is caught.
  • Re-run in hours. When new data arrives or a base definition is agreed, the whole reconciliation runs again.

The agents never

  • Decide a finding. A practitioner does, and every reported figure traces back to a source row.
  • Raise an assessment. The revenue authority remains the only body that can.
  • Leave the country. Models and data run on infrastructure the government owns or nominates. Nothing trains on your records.

What you receive

Two reports, never merged.

An agreed-upon procedures report must not carry opinions. A government still needs estimates to act on. They arrive as separate documents, so the factual findings hold when an operator challenges them.

Report 1 · ISRS 4400 (Revised)

Agreed-upon procedures

  • Factual findings: what was compared, with what, and the difference
  • The engaging party confirms in writing that the procedures fit the purpose
  • Named intended users and restricted distribution
  • No opinion, no conclusion, no assurance

Report 2 · Advisory

Analytics and exposure

  • Inferred obligations as ranges, with the assumptions stated
  • Operator risk tiers and where to look next
  • Recommendations on systems, data sharing and enforcement
  • Marked as not assurance and not part of Report 1

Standards, method and terms in full

Sectors

Where declared revenue is hard to see from outside.

Each sector has obligations tied to a base the state cannot observe directly, and counterparties who hold the other side of every transaction.

Telecommunications

Independent anchorsInterconnect counterparties, international traffic monitoring, foreign carrier settlements, parent-company filings

Obligations testedExcise, VAT, licence royalty, spectrum fees, universal service levy, inbound floor price, numbering

Mobile money and payments

Independent anchorsCentral bank settlement and trust-account data, switch records, related-party network charges

Obligations testedTransaction levies, VAT on fees, withholding, trust-account interest

Gaming and betting

Independent anchorsWallet flows into and out of licensed operators, payment gateway data, board registers

Obligations testedGaming tax on gross gaming revenue, winnings withholding, licence fees, unlicensed operators

Gateways and satellite

Independent anchorsLanding-station and capacity contracts, customs imports, spectrum and landing-rights registers

Obligations testedLanding rights, capacity revenue, import duty, non-resident withholding tax

How an engagement runs

Four stages, each with an exit.

Every stage ends with a deliverable and a decision. The government can stop at any gate and keep everything produced so far.

  1. Stage 1

    Feasibility

    A short, paid study before any large award. Data inventory, a legal opinion on how each dataset can be obtained, and procedures agreed with the engaging party. About 8 weeks.

    Exit with a data inventory, the legal route to each dataset and agreed procedures
  2. Stage 2

    Pilot

    One operator, one year, every procedure. The pilot shows what the full review will produce before the larger commitment.

    Exit with pilot findings and revised procedures
  3. Stage 3

    Full reconciliation

    All licensees across the statutory look-back window. The review period matches the reassessment window, because a finding outside it cannot be assessed.

    Exit with the ISRS 4400 report and the advisory report, issued separately
  4. Stage 4

    Revenue Ops

    Monthly cycles on new filings, run jointly and then by your team. AI Revenue Ops is also offered on its own.

    Exit with your staff running a full cycle without us

Request a confidential briefing.

Tell us the sector and the institution. A senior practitioner replies within two working days.

Request a briefing

DubaiDIFC, Dubai, UAE · GMT+4 Hong KongCentral District, Hong Kong SAR · Asia-Pacific headquarters · GMT+8 briefings@revenuelytics.ai