Call Accounting and CDR Reports: How to Turn Phone Records Into Decisions

Call accounting is the least glamorous feature in a phone system and the one that gets an angry email when it is missing. It is also the one that finance, compliance, and operations all quietly depend on.

Definition: Call detail records (CDRs) are the per-call data your system logs — who called whom, when, for how long, on which trunk, and what the outcome was. Call accounting is the practice of turning those CDRs into usable reports: cost by department, cost by extension, billing for a client account, or evidence for a dispute.

What call accounting is actually for

Four jobs, and they are not equally common:

• Cost allocation. Putting a monthly phone bill against the department or cost centre that caused it, so the number means something.
• Client billing. Law firms, agencies, clinics, and MSPs bill clients for calls. They need per-account totals, itemised enough to survive a query.
• Compliance evidence. Regulated industries need to demonstrate that specific calls were placed or received, when, and on which line.
• Capacity and abuse detection. Which trunk overflows at 10am, which extension makes 300 calls a day, whether anyone is making international calls at 3am.

The CDR fields that matter

A phone system that logs calls but produces a report nobody can read is not doing call accounting. These are the fields worth confirming before you buy:

Two fields get missed and both matter: cost and disposition. A report that lists 400 calls with no cost column or no answered/busy distinction forces someone to reconstruct both by hand before it can be used.

How to build it so it survives contact with finance

Push cost onto the CDR, not into a spreadsheet later

If your platform can assign a cost to each call based on the trunk tariff, the report is ready the moment it runs. If cost has to be added manually later, the report is always slightly wrong and always a week behind.

Aggregate at a level finance recognises

Tag extensions with department, cost centre, or client account. Most systems support this through extension naming conventions or an account-code prompt at call setup. The prompt is more work per call but it is also the only way to attribute a call to a client that has no dedicated extension.

Export on a schedule

Manual export means the report only exists when someone remembers. Schedule a daily or monthly export to CSV or to your accounting system, and keep the destination somewhere the finance team controls rather than on a laptop.

Keep the raw data, not just the summary

Summaries lose the detail that matters when someone disputes a number. Retain the raw CDR set for the period your obligations require — commonly three to seven years depending on the regulation and the contract.

Things that trip people up

• Two systems, two sets of numbers. If trunks terminate at a carrier and calls also appear in a UC platform, reconcile them once a month or the two reports will disagree and you will lose trust in both.
• Cost allocation on shared lines. Reception lines and hotline numbers receive calls from many sources. Define an explicit rule — a default department, or an IVR prompt — before you need the number.
• CDR volume. A busy site generates tens of thousands of rows a month. A spreadsheet will not hold up; the export has to land somewhere designed for it.
• Retention and privacy. CDR metadata is personal data in most jurisdictions. Apply the same access controls and retention limits as you would to any customer record.

Reports worth having on day one

Newrock perspective

Newrock's OM-series IP-PBX produces detailed CDR records with duration, direction, trunk, and result on every call, and UMS provides the reporting layer on top — cost by extension, department, or trunk, with scheduled export. That matters because it removes the manual step where most call accounting systems quietly stop being accurate.

FAQ

Is call accounting only for large companies?

No. Even a fifteen-person firm has a phone bill it cannot currently explain, and one client account it eventually needs to bill for.

Do I need call accounting if I have a cloud phone system?

Cloud platforms have their own reporting, often strong but locked to their own storage. If you need to export to your own accounting or BI stack, that is a decision point, not a given.

How long should CDRs be kept?

Long enough to satisfy your contractual, tax, and regulatory obligations — commonly three to seven years. Check what your jurisdiction and your carrier contract actually require.

Can I get per-client billing for calls only?

Yes, using account codes or an IVR prompt at call setup. It adds a step for staff, so pilot it with one team before rolling it out.

Related reading on the Newrock site

• CDR Software for IP-PBX call record collection
• Unified Management System for OM series IP-PBX and MX series gateways
• What an IP-PBX Actually Costs: Line Items People Forget
• Managing Multiple PBX Sites: A Unified Management Approach

Conclusion

Call accounting is not an optional extra — it is the difference between a phone bill you accept and one you can defend. Confirm the CDR carries cost and disposition fields, tag your extensions properly, export on a schedule, and keep the raw data. Do that once and the reports write themselves for years.