---
sourceDocument: Australia Telecom Service Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/telecom-service-ops

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecom Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Run Telecom Discrepancy audit

# Run Telecom Discrepancy audit {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.

## Before you begin

Role required: admin

## About this task

The Telecom Discrepancy Audit is part of the CMDB Compliance framework and supports phased auditing. It detects and addresses discrepancies in CI relationships and attributes discovered through ServiceNow Discovery or Service Graph Connectors (for example, Nokia Altiplano).

You can run the audit manually or set it to run at regular intervals. During manual execution, you can select from existing filters to limit the audit scope to specific CIs---helpful for testing or targeted reconciliation.  
The Telecom Discrepancy Audit works in two phases:

1. Initial compliance run: Validates CI relationships and selected CI tables using the following default criteria:
   * Supported CI classes: Slot, Subslot, Card, Interface, Network Gear (includes all extension tables).
   * Source: CI was discovered via Discovery (For example `discovery_source = SG-TSOM-Altiplano`).
   * Relationship type: `Contains::Contained By` (customizable via `sn_tsom_core.audit.relationship_types` property).
   {#run-audits__ul_ydk_qyn_xfc}
2. Subsequent compliance runs: In addition to initial checks, evaluates whether the Updated timestamp of the relationship or related CIs is more recent than the Last run date in the audit record.  
   Note:  
   Each failed audit creates a Follow-On Task for manual or automated remediation, confirming telecom CMDB data stays aligned with the network state.
{#run-audits__ol_cfk_yyn_xfc}

The following screenshot helps you understand the Telecom Discrepancy Audit.

## Procedure

1. Navigate to AllComplianceAudits
2. Open the Telecom Discrepancy Audit (cert_audit table) record.
3. **Optional:** Select a filter.  
   * If multiple audit filters have been defined during configuration, you can choose one before running the audit.
   * Filters enable you to restrict the audit scope based on criteria such as discovery source, CI class, or specific CI attributes.
   * This step is especially useful when troubleshooting a subset of records or validating specific discovery results.
   {#run-audits__ul_olp_mcn_zfc}
4. Do either of the following to run the audit.
   * Click Run Audit to trigger a manual execution.
   * Configure the audit to run on a scheduled basis by setting up a recurring job.

   {#run-audits__choices_tsn_vcn_zfc}  
   The audit uses CMDB Compliance to validate relationship and CI integrity across telecom inventory.
{#run-audits__steps_vzt_tbc_yfc}

## Result

Review audit results

* The audit identifies compliance failures such as missing relationships or misaligned attributes.
* For each failed audit record, a Follow-On Task is automatically generated.
* Tasks include recommended or automated remediation actions such as updating or decommissioning CIs.
{#run-audits__ul_l5z_zcn_zfc}

Example use case: The configured filters can be used for different discovery sources. For example, the Nokia Altiplano. When running the audit manually, you can select the appropriate filter to validate only those CIs
discovered by that specific source---confirming targeted and efficient auditing.
**Related tasks**   

* [Configure filter for audit](https://www.servicenow.com/docs/os6NsXZsFd0h~wDkegRWTg "Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.")
* [Example for Telecom Discrepancy Audit and Remediation](https://www.servicenow.com/docs/Qa1s_03bkhuTbBKYJRF36Q#example-for-telecom-discrepancy-and-reconciliation "The following example illustrates how the audit works in a scenario.")

## Example for Telecom Discrepancy Audit and Remediation {#ariaid-title2}

The following example illustrates how the audit works in a scenario.

### Before you begin

Role required: admin

### About this task

A card (Card04) was initially discovered in Slot04. Later, Card04 was replaced by Card05 in the physical network, but the CMDB still shows Card04 in Slot04. When a new discovery run executes, Card05 is discovered and added to
the same slot, creating a data conflict in CMDB.

Audit Behavior:

* The Telecom Discrepancy Audit detects this inconsistency and creates a failed audit record (e.g., `AUDR0001283`).
* A Follow-On Task is created automatically (e.g., `TASK0020215`) with a detailed description of the discrepancy.

{#example-for-telecom-discrepancy-and-reconciliation__ul_zls_d3c_yfc}

Task Description Example (Incorrect Number of Relationships):  
Card04 was last discovered more than 2.5 days ago.{#example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__2}

| CI | Model |
|-|-|
| Slot04 | DEMO 20532Tree |
| Card04 | Nokia 7360 FANT-F CARD MODULE |
| Card05 | \<model not identified\> |
[Table 1. Relationships between the following CIs]

{#example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc}

### Procedure

1. Navigate AllComplianceAuditsTelecom Discrepancy AuditRun Audits.  
   A Follow-on Task is automatically created for each failed audit record (for example, TASK0020215).
2. Select TASK0020215 and review the discrepancy description.  
   Note:  
   This is an example of the TASK0020215 description created for the "Incorrect number of relationships" scenario. Other scenarios and environments might have different descriptions.  
   The Follow-On Task contains a detailed description of the discrepancy. As you can see in the description, the Card04 CI is in discrepancy.
3. To remediate, perform the following steps:
   1. Navigate AllSystem DefinitionUI Actions.
   2. Select Remediate.  
      The Remediate button is a UI action that triggers the `TSOM CI Decommission` subflow. This subflow:
      * Retires the outdated Card04 CI.
      * Removes the incorrect Slot04 → Card04 relationship.
      * Synchronizes CMDB records with the network state.
      {#example-for-telecom-discrepancy-and-reconciliation__ul_hpd_3bd_yfc}

### Result

After remediation:

* The Follow-On Task (`TASK0020215`) updates with work notes summarizing the resolution steps.
* The Card04 CI is marked as retired, and incorrect relationships are removed.
* CMDB is now aligned with the latest discovered state from the network.

{#example-for-telecom-discrepancy-and-reconciliation__ul_gwy_mbd_yfc}  
Note:  
Customize Remediation - The Telecom Discrepancy Audit ships with example remediation subflows. You can create and attach custom subflows using Flow Designer to suit your operational requirements.
**Related concepts**   

* [Telecom Discrepancy Identification and Reconciliation](https://www.servicenow.com/docs/hxG0yC~ZaxhPiJaX2lYtzA "Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. This solution continuously audits and compares discovered data with inventory records. It helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.")
* [Discrepancy identification -- types of discrepancies](https://www.servicenow.com/docs/Dr2fJ5elTqsHjPZK7IcA6w "The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the discovered network state and inventory data stored in the CMDB or TNI.")
* [Telecom discrepancy identification and reconciliation](https://www.servicenow.com/docs/LTaiuK3iLT_Jtfe~9RYVZw "The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin enables the TSOM Visibility applications. It contains logic shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.")  
**Related tasks**   

* [Activate Telecom Discrepancy and Reconciliation](https://www.servicenow.com/docs/eKEWtA2thKOJ5oTFAFuKVg "Activate the Telecom Discrepancy Identification and Reconciliation feature to ensure consistency between telecom network resources and CMDB or Telecom Network Inventory (TNI) data. This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.")  
**Related topics**   

* [Defining UI actions](https://www.servicenow.com/docs/access?context=c_UIActions&version=australia&pubname=australia-platform-administration&ft:locale=en-US)

*[\>]: and then