Skip to content
ExtractorHub

CDR & Carrier Invoice Reconciler — Telecom Billing

Compare call detail records with a carrier rate deck and invoice. Find overcharges, undercharges, missing invoice lines, duplicates and unmatched calls with per-row arithmetic evidence.

CDR & Carrier Invoice Reconciler — Telecom Billing returns 5 documented output fields, including rate, minimum, connection, rows and summary. Every field carries a declared type, a written description and an example value. 2 runs are recorded on Apify.

Run it on ApifySee current pricing on Apify
5
Output fields
9
Inputs
2
Runs
2026-10-23
Last run

01 — output

What it returns

Every field the extractor writes to its dataset, with its type, a written description and an example value.

FieldTypeWhat it holdsExample
ratestringnullRate applied, in the unit the source states.
minimumstringnullMinimum as recorded for this row.
connectionstringnullConnection as recorded for this row.
rowsarraynullHow many rows this item contributed.120
summaryarraynullShort human-readable summary of this row.[]

02 — sample

One record

Assembled from the example values declared on the schema above, not invented at render time.

{
  "rate": "",
  "minimum": "",
  "connection": "",
  "rows": 120,
  "summary": []
}

03 — input

What you give it

InputTypeDescription
cdrDatasetIdstringoptionalOptional Apify dataset containing callId, destination and durationSeconds rows.
invoiceDatasetIdstringoptionalOptional Apify dataset containing callId and charge rows.
rateDatasetIdstringoptionalOptional Apify dataset containing prefix, ratePerMinute, billingIncrementSeconds, minimumSeconds and connectionFee rows.
cdrRowsarrayoptionalCall records. Each callId must identify one call; destination is an international number or prefix and durationSeconds is non-negative.
invoiceRowsarrayoptionalCarrier invoice line items with callId and decimal charge. Repeated call IDs are reported as duplicates.
rateRowsarrayoptionalLongest matching prefix wins. ratePerMinute and connectionFee are decimal amounts; increment and minimum are seconds.
currencystringoptionalThe currency shared by rate deck and invoice; the Actor does no FX conversion.
tolerancestringoptionalAbsolute difference at or below this decimal amount is treated as matched.
onlyExceptionsbooleanoptionalWhen true, omit matched calls from dataset output; the summary still counts them.

04 — run

Run CDR & Carrier Invoice Reconciler on your own input

It runs in the cloud on Apify. Check its current price and billing events on the Apify page before you run it.

Open on Apify ↗

05 — questions

Asked before running it

5 of 5 fields described

What does CDR & Carrier Invoice Reconciler — Telecom Billing return?
It returns 5 documented output fields: rate, minimum, connection, rows and summary. Each field declares its type, a description of what it holds, and an example value.
What input does CDR & Carrier Invoice Reconciler — Telecom Billing take?
The schema marks all 9 inputs optional. Check the field descriptions and credential requirements before running.
Does CDR & Carrier Invoice Reconciler — Telecom Billing need an API key or login?
No input field is marked secret. Check the Actor documentation for any source access requirements.
How do I run CDR & Carrier Invoice Reconciler — Telecom Billing?
It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.