Skip to main content
Telecom

Reconcile carrier invoices against a bill rebuilt from your own CDRs

ADAM reconciles call detail record (CDR) files, vendor rate decks and interconnect invoices. It rebuilds an independent bill from your own traffic, compares the vendor invoice against it per vendor and billing period, and runs a separate rate check that measures contracted against realised rates for each destination and route.

Call records from a company's own traffic rebuilt into an expected total of 17,880.40, set against a vendor invoice of 18,402.10, with the 521.70 difference marked as not a match

ChallengeSolution

Vendor invoices arrive with no practical way to check them
Rebuilds an independent bill from your own traffic
CDR files, rate decks and invoices land on different schedules
Compares the vendor invoice against it, per vendor and period
Contracted rates and billed rates drift apart per destination
Measures contracted against realised rates by destination and route
Disputes need evidence that is not to hand
Gives you the line-level evidence a dispute needs

How ADAM turns traffic into an invoice check

01Receive each evidence stream on its own schedule

Hourly CDR files arrive through a secure file drop, rate decks and vendor call records arrive in a shared cloud folder, and invoices arrive by email. ADAM brings those inputs into one reconciliation flow.

02Deduplicate calls before aggregating traffic

The same call can reappear across consecutive hourly files. ADAM streams the records and deduplicates them by call reference before any minutes or amounts are added together.

03Rebuild the expected bill from the traffic

ADAM groups the clean calls per vendor account and jurisdiction into a daily expected bill, calculated from the traffic rather than copied from the amount on the vendor invoice.

04Match invoices and test realised rates

The invoice is matched to that expected bill per vendor and billing period, on period overlap and amount. A separate rate check compares contracted and realised rates for each destination and route, so a local variance stays visible.

Call records rebuilt by ADAM AI into an expected bill of 17,880.40, compared with a vendor invoice of 18,402.10, leaving a flagged gap of 521.70 or 2.9 per cent

What a checked document looks like

Vendor invoice 4471-A · Route 9 · 08.20264 checks · 1 flagged
Calls billedAll routesMatched.
1,284,220
Billed minutesAll routesMatched.
42,108.5
Amount, CHFInvoice totalFlagged.Rebuilt from CDR 17,880.40 · +521.70 (+2.9%)
18,402.10
Contracted rateDE mobileMatched.
0.0142

A useful dispute needs two thresholds, not one

Two thresholds, not one
A discrepancy becomes a dispute only when a percentage threshold and an absolute monetary floor are both exceeded.
Material both ways
Four percent on a tiny account is noise, while 0.2 percent on a large account is real money.
One engine, on a rebuilt total
The same matcher that reconciles delivery notes against invoices, applied to a total rebuilt from your own traffic.

Carrier reconciliation FAQ

Why does ADAM deduplicate hourly CDR files by call reference?

The same call can appear again in consecutive hourly CDR files. ADAM streams those files and uses the call reference to remove the repeat before aggregating minutes and amounts, so the daily traffic figure is based on each call once.

How does ADAM know what the bill should have been?

ADAM builds its own daily expected bill for each vendor account and jurisdiction from the deduplicated traffic itself, rather than copying the amount from the vendor invoice. That gives the match an expected figure the vendor did not supply.

When does a carrier variance become a dispute?

Only when the configured percentage threshold and absolute monetary floor are both exceeded. Requiring both keeps a high percentage on a tiny amount and a tiny percentage on a large amount from being treated as the same kind of exception.

How can an invoice be paired when supplier names differ between systems?

ADAM first uses an exact document-number match when one exists. The second stage groups candidates by supplier-name tokens, currency and month, then requires the same currency, at least one shared name token and overlapping periods before a candidate can match.

What does the carrier team receive after reconciliation?

ADAM mirrors the result to Google Sheets, tints the variance red when the billed amount is too high and green when it is too low, and adds a plain-language note to each row. A scheduled digest summarises the resulting review work.

Can ADAM reconcile carrier invoices without processing raw CDR files?

Yes. Instead of rebuilding the expected bill from call records, ADAM can pull the expected amounts a carrier's own billing platform already holds, over a nightly API pull, and match the invoice against those. The comparison is the same, per vendor and billing period, and the same two thresholds decide whether a variance becomes a dispute.

Try ADAM on your own document

Send a photo or PDF and see the structured result in about a minute.

Try ADAM

Bring ADAM into your document flow.

Start with the channels you already use. We map the documents, define the modules and connect the outputs to your existing team.

Direct contact

ADAM AI

Michael Knobel, CEO

michael@adamai.ch

We reply within one business day.

Send a message