Azhar Khan · Utilities · Agentic AI Deployment
03 · UTILITIES · BILL PAY← HOME
700KInvoices a month, half of them stopped for a person.
THE TWIN
1 /100Reaches a person, at $0.20 per invoice, in a utility bill-pay operation.

A back office became a buying desk.

700 people

A 700-person back office paid $2.5B a year in utility bills on a 17-year-old system. Half the invoices stopped for a person, and 80 to 90% of quality flags were false alarms, because nobody could see whether a bill was already paid, in transit or used.

The check

I moved the check ahead of the exception. Each invoice is compared with its account first, paid, in transit and usage, so most exceptions never form. The template fills from the invoice and the master data.

The gate

The account template became the gate for every new client. Go-live starts at 75 to 80% readiness with change-of-address run in parallel, so onboarding fell from 90 days to 30.

290 keyers

All 290 keyers kept their jobs, and 65 became pattern-builders and exception analysts. Cost fell from $0.58 to $0.20 per invoice, and the same record now feeds procurement, tariff and forecasting, so the back office buys as well as pays.

{{ insHeadline }}
A rule check that runs after the exception only sorts the queue. Move it before, and it reads the account’s own state first.
{{ insState }}
{{ insPersonV }}
REACH A PERSON · PER 100
{{ insCostV }}
COST PER INVOICE
{{ insDeskV }}
THE DESK
CHECK RUNS AFTER THE EXCEPTIONCHECK READS STATE FIRST
2024 · HALF THE QUEUE, 290 PEOPLE{{ insHint }}

RUN · THE TWIN

1 invoice in 100 reaches a person.

Invoices a month
700Ktoward 1M

The volume grows toward 1M on the same record.

65% → 99%capture accuracy
8 → under 1minutes per invoice
$0.58 → $0.20cost per invoice
90 → 30 daysto onboard a client
Reaches a person
1in 100

Now 1 in 100 stops, with its evidence attached, before the due date.

The desk
65from 290

Keyers became pattern-builders and exception analysts.

Payments cleared a day
~1,900

Each one is audited against the record and sent on the day.

Payments a year
$2.5B

$1B of it runs on the twin.

Clients
180+
Vendors
20,000+

The 65 read only the exceptions, each with its evidence attached.

BUILD · THE TWIN

250,000 ACCOUNTS · 20,000+ VENDORS · EVERY BILL NORMALIZED

Buying runs on the same rows that pay the bill.

Bill audit, tariff, forecasting and emissions read the same rows.

Bill auditevery charge against the tariff and the meter1 IN 100
Anomaly detectionthe account’s own trend, inside its own bandBAND
Process intelligencecycle, touches and exceptions, read weeklyWEEKLY
Budgets · forecastspend by site, rates run as scenariosBY SITE
Tariff optimizationthe right rate for each meterPER METER
Energy procurementaggregate spend, contracts bought on the operation’s own numbers$2.5B
Incentivesthe programs each site qualifies forPER SITE
Scope 1 · 2emissions read off metered usageFILED
ReceiptAPI, portal, PO box
Splitat intake, by page
Entry · tier 1document intelligence
Entry · tier 2gone
Verificationconfidence threshold
Qualityreads the row first
Exception65 analysts · 1 in 100 · reviewed
Fund · payon the day, audited, sent
700KROWS A MONTH
250KACCOUNTS
65ANALYSTS · WERE 290 KEYERS
$0.20PER INVOICE · WAS $0.58

One digital twin carries $1B of the operation.

Every vendor, site and meter reconciles to one identity before a bill is read. A record that will not reconcile is held for a person.

$1B on the twin
$2.5Bthe whole payments operation, a year
700Kinvoices a month, reconciled before they are read
20,000+vendors on one identity
300+invoice layouts normalized
AGENTIC SYSTEMreads the bill, prices it against the record, pays it, and stops the one that will not reconcile
THE DIGITAL TWINthe modeled operation, 250,000 accounts on one identity
THE DATA LAYERone row per service, normalized across units, layouts and periods
THE CLIENT’S SYSTEM LAYERSportals, feeds, meters and the ledger

An extracted bill alone cannot feed forecasting, accruals or rate optimization.

The data layer Open the map →

BUILD · ONE ACCOUNT RECORD

250,000 ACCOUNTS · 14 FIELDS

The record could not say whether it was paid.

The bill says a balance is owed. Nothing on her screen says whether last month’s payment went out. Most of her flags will turn out to be nothing.

The record starts to answer.

Last bill, last payment and days since the check went out are written once, per account. A previous balance that matches a payment in transit now closes on the record.

The account record keeps its history.

The March bill stays in view. The 2026 record carries later payments, meter history and contract rates.

700,000 A MONTH · 1 IN 100 STOPS, WITH A REASON, BEFORE THE DUE DATE

ACCOUNT RECORD2024THE FIX2026
Vendor0382 · v7 · ES0382 · v7 · ES0382 · v7 · ES
ClientC-1147C-1147C-1147 · SFTP · Tue
Template—190 / 190190 / 190 · v3
Charge dictionary—DEMAND CHG → demand~36,000 · fully mapped
Last bill—$1,284.10 · Feb$1,296.40 · Aug
Last payment—$1,284.10 · 19 Mar$1,296.40 · cleared
In transit—yes · clears Thunone
Days since check—6 · under 300
Meter history——M-23 swapped Apr · ok
Intake source——portal · API
Remit-to——PO 8812 · verified Aug
Letter of authority——on file · 2026-01
Delivery day——Tue · no day missed
Contract rate——0.0900 · billed 0.1010
FIELDS KNOWN

GOVERN · THE GATE

ACCOUNT TEMPLATE FIRST

Onboarding became the gate.

The account template is created and validated before the first bill arrives, so the state row exists on day one.

12 to 16 weeks
15 to 20 days
Bill paythe pipeline runs end to end and the payment leaves90–95%
Prepaythe run stops at the AP file and the client paysAP FILE
Postpaythe run stops at quality and the client has already paidQA ONLY

THE DESK · 290 KEYERS

65PATTERN-BUILDERS AND EXCEPTION ANALYSTS
AZHAR KHAN {{ label }}
{{ headline }}
{{ sub }}
ELECTRIC · NJ · SUMMARY BILLP. 1 / 14
8 services · 9 meters · 48 charge lines
{{ s.id }}{{ s.meter }}{{ s.kwh }}{{ s.total }}
849,987 kWh$40,195.40
DUE 04/15 · BILL TYPE ACTUAL{{ dueText }}
DATA LAYER · ONE ROW PER SERVICE700K ROWS A MONTH
SERVICEMETERkWh×DELIVERYSTATUS
{{ s.id }}{{ s.meter }}{{ s.kwh }}{{ s.mult }}{{ s.delivery }}HELD
{{ d.name }}
{{ role }}
{{ f.label }} {{ f.src }}{{ f.value }}
CurrChg-Meter Diff · HARD BLOCK
{{ diff1 }}
CurrChg-Chg Unit Diff · HARD BLOCK
{{ diff2 }}
{{ tipLabel }} · {{ tipText }}
{{ s.v }}{{ s.k }}
UTILITY BILL PAY
MICROSOFT STUDY

GOVERN · THE DECISION

EXCEPTION DESK · 65 ANALYSTS

One charge name sends the bill to a person.

99 bills in 100 close on the account’s own state. This one carries a charge name the master has never seen. The guardrail will not price it or guess. It stops with its evidence, 6 days before the money is due.

Nothing posts below this line without a person.

The charge mapping is approved. The bill remains held: calculated usage is 63,600 kWh, but printed usage is 114,284. The mapping is saved for later bills. Payment waits for the meter discrepancy to be resolved.

Nothing posts. The bill is held for the morning team with its evidence attached, 6 days before the due date.

EXCEPTION · CHARGE LINEACCT AC-0449-0450
Service0449 96 · KZD700001191
Charge as printedDistribution Chrg (kW)
Charge master~36,000 entries · no exact match
Amount$41.87
Account staterate on contract · usage inside band
Charge balance$0.00 once priced; meter check still held
Payment due6 days
AWAITING A PERSON HELD · NOTHING POSTS BELOW THE LINE MAPPED · BILL HELD
{{ tkEyebrow }}

{{ tkH }}

{{ tkFacts }}

{{ tkOwn }}

{{ tkNext }} → Let's talk about a deployment leadership role.
PRESS . FOR THE NEXT PAGE