By Sharon Watkins, Founder and CEO, RadiusPoint
Voice wireline and data circuits move through the same telecom expense management lifecycle, but they cannot share one inventory key. Voice keys on telephone numbers under a billing account number. Data keys on circuit IDs, bandwidth, and location pairs. Run both on one platform with category-correct keys, and finance gets a single audit trail while telecom keeps accurate inventory.
The confusion rarely surfaces until month-end. A controller pulls one telecom accrual, ties the voice invoices to a phone-number list, then runs the same match against the data invoices and finds that nothing lines up. Circuit invoices do not carry phone numbers. They carry circuit identifiers, bandwidth tiers, and the two addresses each circuit connects. The two spend types belong to one discipline, yet they are keyed, contracted, and audited differently, and treating them as a single list is exactly where reconciliation breaks.
Key Takeaways
- Voice keys on telephone numbers under a BAN; data keys on circuit IDs, bandwidth, and location pairs.
- Voice uses seat or line rates; data uses port, loop, and committed bandwidth terms.
- Voice audits features and usage; data audits installed versus billed service and MRC variance.
- RadiusPoint runs both categories in ExpenseLogic with category correct keys and shared GL output.
One lifecycle, two inventory keys: where voice and data split
Both voice wireline and data circuits run the same four stages of order, inventory, invoice audit, and pay, but voice keys on telephone numbers while data keys on circuit identifiers and endpoints. The lifecycle is what makes them one discipline. The inventory key is what makes them two problems inside it. A voice line is identified by its number, grouped under a billing account number (BAN), and described by its feature set. A data circuit is identified by a circuit ID, sized by committed bandwidth, and defined by the two locations it joins, the A end and the Z end.
That single difference cascades through every later stage. It changes what the order confirms, what the inventory of record stores, what the audit tests, and what accounts payable is being asked to approve. Deciding whether that lifecycle belongs in-house or with a provider is a separate question, covered in our guide on when you need TEM. The keying difference below applies either way.
| Dimension | Voice wireline | Data circuit |
|---|---|---|
| Primary inventory key | Telephone number under a BAN | Circuit ID |
| Supporting identifiers | BAN, feature and USOC codes, site | Bandwidth tier, location pair (A end and Z end), site |
| Contract unit | Seat or line rate | Port, loop, and committed-bandwidth terms |
| Characteristic audit test | Feature and usage anomalies against the contracted rate | Installed versus billed, plus mileage or MRC variance |
| Common leakage | Legacy features, unused lines, rate reversion at renewal | Disconnected circuits still billing, bandwidth mismatch, closed-location circuits |
A voice audit asks whether the number should still exist. A data audit asks whether the circuit was ever installed at the bandwidth you are paying for.
Voice wireline expense management: auditing numbers under a BAN
Voice wireline expense management tracks numbers, features, and usage against contract rates under each billing account number before accounts payable releases the invoice. The unit of work is the telephone number. Every number rolls up to a BAN, every BAN rolls up to a carrier contract, and the audit tests each number against the rate and feature set that contract actually specifies.
The errors cluster in predictable places. Features billed per line and applied estate-wide long after anyone used them. Lines that survive a role change or an office move because nobody cancelled them. Long-distance and usage charges that drift above the contracted rate. Rates that revert to list pricing at renewal because the amendment was never loaded into the rate table. None of these are exotic. They persist because a manual reviewer cannot test hundreds of numbers against contract terms every cycle, so the invoice gets approved on its total rather than its lines. A line-item audit reverses that default, testing each number before payment rather than sampling after it. The mechanics of that recurring test are set out in our telecom audit services overview.
Data circuit expense management: auditing IDs, bandwidth, and endpoints
Data circuit expense management validates circuit IDs, bandwidth, locations, and monthly recurring charges against the inventory of record and the contract. Here the unit of work is the circuit, and the reference data is harder to hold. A circuit does not announce itself with a phone number. It appears on the invoice as an identifier, a bandwidth level, a pair of addresses, and a monthly recurring charge, and every one of those has to match a maintained inventory record for the charge to be legitimate.
Data circuits also fail in a way voice lines rarely do: they keep billing after they are gone. A disconnected MPLS or SD-WAN circuit that was ordered off but never confirmed off will bill for months, because the carrier’s billing system and the client’s inventory are not the same record. Bandwidth is a second recurring problem, where a circuit contracted at one tier bills at another, or a port charge outlives the loop it supported. Closed and relocated sites produce a third, with circuits still charging monthly recurring cost at addresses the business has vacated. Catching these means testing installed against billed, checking mileage or MRC variance, and matching every circuit ID on the invoice to a circuit in inventory. The full validation sequence sits in our invoice auditing services.
Align five fields, and one close covers both categories
Controllers and telecom teams can keep category-correct keys and still close as one, provided five fields are identical across voice and data. The keys diverge on purpose: a number is not a circuit ID and should not be forced into the same field. What has to match is the connective tissue that lets both categories feed a single accrual and a single general ledger interface. Align these five, and the difference between a number and a circuit ID stops mattering to finance. The comparison logic that separates wireless keying from wireline keying is developed further in our note on wireless versus telecom expense management.
The Shared-Close Rule. Five fields controllers require identical across both categories, even when the inventory keys differ:
- Billing account number (BAN). The account each service rolls up to, so voice and data on the same account reconcile to the same payable.
- Service ID type. A single field that flags whether the record is keyed by number or by circuit ID, so both resolve through one logic rather than two spreadsheets.
- Site or location code. The shared address key that lets a closed location surface every voice line and every circuit billing against it at once.
- Cost center. The allocation target, identical in structure across categories, so chargeback and GL coding do not fork by spend type.
- Contract rate reference. The pointer to the contracted rate or bandwidth term, so every line is testable against what was actually agreed.
Why RadiusPoint runs voice and data on one ExpenseLogic estate
RadiusPoint manages wireline voice and data circuits in one estate on ExpenseLogic, so finance gets one audit trail while telecom keeps category-correct inventory keying rules. ExpenseLogic holds the rate table, the inventory of record, and the invoice history for both categories in a single system, keying voice on telephone numbers under each BAN and data on circuit IDs, bandwidth, and location pairs. ExpenseLogic validates every invoice line against the contracted rate, the provisioned service, and the applicable tax treatment each billing cycle. RadiusPoint analysts file disputes directly with carriers under a letter of agency, pursue each case until the credit posts, and update the inventory of record as moves, adds, changes, and disconnects occur. ExpenseLogic then feeds allocated, coded charges into the client’s ERP and accounts payable systems from one close.
The cost of not doing this compounds monthly. Every cycle a data estate goes unaudited, disconnected circuits keep billing at full monthly recurring charge and closed-location circuits keep posting to live cost centers. Every cycle a voice estate goes unaudited, reverted rates and orphaned features bill again at the same amount they billed last month. A one-time sweep converts that history into a refund. A continuous audit converts the same analytical work into error that never reaches an invoice, which is money kept rather than money recovered.
Ask RadiusPoint to audit one month of your wireline voice and data invoices on ExpenseLogic, and see how many circuit IDs and telephone numbers on your current bill no longer match your inventory of record.
FAQ
Voice and data should share one TEM platform while retaining category specific inventory keys.
Should voice and data have separate TEM tools?
Separate tools multiply GL and inventory reconciliation. Prefer one ExpenseLogic platform with different keys for each product family.
Where does wireless fit in this comparison?
Wireless is a third keying model based on device and Employee ID. It should not be forced into voice or circuit inventory.
What breaks first when keys are mixed?
Data circuits billed like phone lines, or voice features lost inside circuit summaries, create false inventory and unreliable reconciliation.
Do MACD workflows differ?
Yes. Voice MACD often means feature or number changes. Data MACD means bandwidth, demarcs, and install verification.
Can one LOA cover both?
Scope carefully by product family. Ordering rights for circuits are not the same as ordering rights for voice lines.