---
title: "CDR009 - Usage record requires a terminating number"
slug: "cdr009-usage-record-requires-a-terminating-number"
updated: 2026-08-10T20:19:32Z
published: 2026-08-10T20:19:32Z
canonical: "help.idibilling.com/cdr009-usage-record-requires-a-terminating-number"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.idibilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CDR009 - Usage record requires a terminating number

Override is allowed

| Name | Usage record requires a terminating number. |
| --- | --- |
| Common Cause | This was a voice call or a mobile message and the originating number could not be determined. |
| Common Resolution(s) | Actions you can take to resolve the problem: - If this rarely occurs, the CDR may be bad or malformed. If so, it can be left alone (it will eventually age and no longer be visible) - or it can be purged immediately if desired. - If this occurs regularly, contact IDI BCT. It’s possible that a software (parser) update is required. - If the usage record should be billed anyway, choose Override Rule on the usage record. If this is done frequently, consider a change to Unbillable Rules for this Unbillable Code. Note that ignoring validation failures can have undesirable downstream repercussions including rating and discounting failures and poor invoice presentation. |
| Details | Voice calls and messages require an originating number. In this case the originating number could not be determined from the information in the CDR. |