CDR & Carrier Invoice Reconciler

Find incorrect carrier charges from your own exports. The Actor compares each call detail record (CDR) to the longest matching destination prefix in your rate deck, applies the minimum duration and billing increment, then compares the expected charge to the invoice line. It never logs in to a carrier or places calls.

Inputs

Supply cdrRows, invoiceRows, and rateRows as JSON arrays, or supply their corresponding Apify dataset IDs. Dataset IDs take precedence over inline arrays. The included sample prefill is a safe local demo.

Array	Required fields	Optional fields
cdrRows	callId, destination, durationSeconds	—
invoiceRows	callId, charge	—
rateRows	prefix, ratePerMinute	billingIncrementSeconds (default 60), minimumSeconds (default 0), connectionFee (default 0)

All monetary inputs are non-negative decimal strings with up to six places, in one currency. tolerance is an absolute charge difference. One canonical CDR per call ID is required. Repeated invoice call IDs are reported as exceptions, not silently merged. Prefixes and destinations contain international digits; +, spaces, parentheses, periods and hyphens are accepted in phone numbers.

Results

Each dataset row includes the selected rate prefix, billed seconds, expected and invoiced charges, difference (invoice - expected), status and reason. Statuses: matched, overcharged, undercharged, missing_rate, missing_invoice, duplicate_invoice, unmatched_invoice, duplicate_unmatched_invoice. SUMMARY contains counts and totals. knownPairDifference excludes calls without both a rate and invoice; invoiceChargeAllLines includes all invoice lines. No currency conversion is performed.

The Actor rounds the computed usage charge to six decimal places, then adds the connection fee. A zero-second CDR has zero expected charge. Verify those policies against your carrier contract before relying on the report for a dispute.

Run locally

npm install
npm test
apify run

For a quick local run, place input JSON in storage/key_value_stores/default/INPUT.json. The Actor handles up to 100,000 rows per input dataset. It writes a full dataset unless onlyExceptions is true.

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• CDR & Carrier Invoice Reconciler declares all 5 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of CDR & Carrier Invoice Reconciler include rate, minimum, connection, rows and summary.
• CDR & Carrier Invoice Reconciler needs no API key, login or account of any kind before its first run.
• Every one of CDR & Carrier Invoice Reconciler's 9 inputs is optional, so it runs with no configuration at all.
• CDR & Carrier Invoice Reconciler documents rate as: Rate applied, in the unit the source states.
• Every number published about CDR & Carrier Invoice Reconciler is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• CDR & Carrier Invoice Reconciler is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.

Limitations

• CDR & Carrier Invoice Reconciler reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.

FAQ

What does CDR & Carrier Invoice Reconciler return?

It returns 5 documented output fields — rate, minimum, connection, rows and summary — each with a declared type and a written description. The full schema is below.

What does CDR & Carrier Invoice Reconciler require to run?

Nothing. All 9 inputs are optional and ship with working defaults.

Does CDR & Carrier Invoice Reconciler need an API key?

No. It reads only public data and asks for no account.

How is CDR & Carrier Invoice Reconciler billed?

Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.