---
title: "SVC027 - A usage record cannot guide by service number to an ambiguous service"
slug: "svc027-a-usage-record-cannot-guide-by-service-number-to-an-ambiguous-service"
updated: 2026-08-10T20:18:56Z
published: 2026-08-10T20:18:56Z
canonical: "help.idibilling.com/svc027-a-usage-record-cannot-guide-by-service-number-to-an-ambiguous-service"
---

> ## 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.

# SVC027 - A usage record cannot guide by service number to an ambiguous service

Override **NOT** allowed

| Name | A usage record cannot guide by service number to an ambiguous service. |
| --- | --- |
| Common Cause | This service number (a.k.a. MDN, MSISDN) is assigned to multiple services in CostGuard and the active dates of these services overlap, so it isn’t possible to determine which of these to guide this usage to. |
| Common Resolution(s) | Action you can take to resolve the problem: - Fix the service number overlap by correcting the effective and/or disconnect dates of the incorrect occurrence of the service. |
| Details | A service number may be assigned to services in CostGuard multiple times, but each occurrence must have an effective/disconnect date range that doesn’t overlap with any other. In this case, a service number is present at least twice in the system, and the date ranges of these instances overlap. It is likely that some conversion or migration error caused this, because the system prevents users from making this mistake. |