Utility Bill Management: How Multi-Site Teams Run the Monthly Cycle

UEM0

Multi-site teams run utility bill management as one monthly cycle: confirm every expected bill arrived, check it against tariff and usage, and pay on time. The month closes once exceptions like estimated reads, closed sites still billing and late fees are cleared and coded data reaches finance. RadiusPoint runs that cycle for clients in ExpenseLogic.

Key Takeaways

  • Utility bill management is the monthly routine for every account and meter in the portfolio, which is different from auditing one bill in depth.
  • An expected-bill calendar built from each account’s billing history turns a missing bill into a dated exception instead of a surprise late notice.
  • Check every bill against the meter roster, the tariff and the same month last year, and flag estimated reads before anyone approves payment.
  • Closed sites, open deposits and late fees need a standing exception list, because one closed store cost a RadiusPoint client more than $1,500 a month.
  • The month isn’t done until finance has general ledger (GL) coded charges, accruals for missing bills and usage by site.

What Is Utility Bill Management?

Utility bill management is the monthly process of receiving, checking, paying and recording every utility bill across an organization’s accounts, meters and sites. It covers electricity, natural gas, water, sewer and waste. The aim is that no bill goes missing, no charge goes unchecked, no due date slips and finance gets clean data each month.

It works at the portfolio level. A single-bill review asks whether one invoice is right, and our guide on how to audit a utility bill covers that line by line. Utility bill management asks a wider question every month. Did every account bill, did each bill match what the site should cost, and is anything still billing that shouldn’t be?

That last question carries the money. A national eyewear manufacturer and retailer with 3 labs and 170 retail locations kept paying electricity, gas and water bills for a South Carolina store after it closed. RadiusPoint identified the closed site, had the services disconnected and stopped more than $1,500 a month in charges. The published case on utilities at closed locations estimates that a proactive process would have avoided more than $18,000 for services nobody used.

What Does the Monthly Utility Bill Cycle Look Like for a Multi-Site Team?

A multi-site team’s monthly utility bill cycle runs through six checkpoints, from confirming the account roster to handing coded data to finance. Each checkpoint leaves a record, and each one exists to catch a specific failure: a missing bill, an estimated read, a rate change, a closed site still billing or a late fee.

The roster is the base record. It lists every account number, meter number, service address, vendor, rate class, billing cycle and site status, plus the cost center each meter charges. A current utility meter inventory is what lets the team tell a missing bill from a closed account. Rate class matters too. New York’s Department of Public Service notes that rates differ by service classification, so a meter in the wrong class bills at the wrong rate every month.

Point in the month Task Record it leaves Failure it catches
Start of the month Confirm the account and meter roster against site openings and closings Roster with site status, rate class and cost center Closed site still billing; new site with no account
As bills arrive Match each arrival to the expected-bill calendar Received and missing list by account Missing bill
On review Compare each bill with the tariff, usage history and roster Review note with read type and variance Estimated read; rate change; usage spike
Before each due date Release approved bills and track payment status Payment status by account and due date Late fee; disconnection notice
Throughout the month Work open exceptions with an owner and a date Exception list for closed sites, deposits and disputes Closed site still billing; deposit never returned
Month-end Send coded charges, accruals and usage to finance GL file, accrual list, kWh and therms by site Missing bill left unaccrued; cost booked to the wrong site

How Do You Catch a Missing Utility Bill Before the Due Date Passes?

You catch a missing utility bill by predicting when each account should bill, then checking arrivals against that date every week of the month. Utilities bill on recurring read cycles, so a year of bill dates tells you when the next one should land. A bill that misses its expected date becomes an exception with an owner.

To build the expected-bill calendar for each account:

  1. Pull the last 12 bill dates and service periods from the account history.
  2. Note the usual gap between bills, and mark accounts that bill every two months or quarterly instead of monthly.
  3. Set an expected bill date and a short grace window for each account, then record the due date the vendor normally gives.
  4. Each week, compare bills received with bills expected and list every account past its grace window.

When a bill doesn’t arrive, check the vendor portal first, since bills can post online before the paper copy arrives. Then confirm the mailing address on file, because moves and acquisitions leave bills going to old addresses. If the vendor shows no bill, ask whether the meter was read and whether the account was closed or transferred. Finance should accrue the missing bill from the same month last year so the close isn’t understated.

A missing bill isn’t free money. New York’s rules let a utility backbill a nonresidential customer for up to two years. The limit drops to 12 months when the delay came from the utility’s own deficiency. Either way, the charge lands later and larger.

Estimated Reads and Rate Changes Hide in the Gap Between Two Bills

Most month-to-month surprises on a utility bill come from three sources: an estimated read, a rate change or a real shift in site usage. The review compares each bill with the prior bill and the same month last year. It also checks the read type before anyone approves payment, since an estimate can hide either problem.

Estimated reads

Every bill should show how each read was taken. New York’s nonresidential billing rule, 16 NYCRR 13.11, requires bills to state whether each reading came from the meter, a remote register, the customer or an estimate, and the reason for any estimate. Under 16 NYCRR 13.8, a utility that doubts a reading may estimate for that reason no more than twice in a row before further steps apply. Flag any meter with two estimated reads in a row and request a read. The risk is the catch-up bill, which New York defines as a bill on a real read after estimates that comes in at least 50% higher than the utility’s standard billing would have been.

Rate and tariff changes

Prices move even when usage doesn’t. Preliminary data from the US Energy Information Administration (EIA) put the average US commercial electricity price at 14.47 cents per kilowatthour in August 2026, up from 13.87 cents in August 2025, a rise of about 4.3%. When the cost per kWh on a bill moves while kWh stays flat, look for a new tariff, a rider, a supplier change or a rate class switch. Confirm the change against the published tariff before you approve the bill.

Usage shifts

Compare kWh and therms with the same month last year, not only last month, because weather drives heating and cooling. A jump with no change in operating hours can point to equipment left running or a meter assigned to the wrong site.

Closed Sites, Deposits and Late Fees Belong on One Exception List

Closed sites, deposits and late fees don’t clear themselves, so they belong on a standing exception list the team works every month. Each entry needs an account, an amount, an owner and a target date. These items can stay open for months while every other bill flows through the cycle normally.

Closed sites still billing

A closed site keeps billing until someone disconnects or transfers each account. EIA’s 2018 Commercial Buildings Energy Consumption Survey (CBECS) counted about 124,000 vacant commercial buildings that still used electricity, roughly 5 billion kWh in a year. Match every closure date against the roster, request disconnects or transfers, and check each final bill’s usage dates against the disconnect date.

Deposits

A utility may require a deposit when a site opens, and it seldom comes back without a request. Track the amount, the date paid and the refund condition for each account. New York’s rules let a utility ask an existing nonresidential customer for a deposit after two or more late payments in 12 months. They also let the customer pay a required deposit in three installments.

Late fees

Late fees usually mean a bill reached accounts payable (AP) late or went to the wrong address. In New York, a utility may add a late payment charge to a nonresidential bill unpaid 20 calendar days after its due date, at the rate in its tariff. Log each fee, ask for a waiver, and fix the delivery path behind it. Waived fees, refunded deposits and billing credits all belong in utility expense recovery until the money posts.

How Does Utility Bill Data Reach Finance at Month-End?

Utility bill data reaches finance as three month-end outputs: GL coded charges by cost center, accruals for bills not yet received and usage by site. Without all three, the close either misses a month of cost or books it to the wrong place. Nobody can then explain a site’s variance with confidence.

Coding follows the roster. Each meter maps to a site, a cost center and a GL account, so the charges land where the site’s budget sits. Shared meters need an allocation rule, such as square footage, written down once and applied every month. Accruals cover the bills the calendar flags as missing, estimated from the same month last year and reversed when the real bill arrives.

Usage in kWh and therms by site shows whether a cost change came from price or consumption. Scale makes this harder: EIA’s 2018 survey estimated that 5.9 million US commercial buildings spent $141 billion on energy that year.

How RadiusPoint Runs the Utility Bill Cycle in ExpenseLogic

RadiusPoint can own the utility bill cycle for a client in ExpenseLogic, from invoice intake and line item audit to client-funded payment and finance data. When one team owns intake, audit, payment and the data, the cycle runs in one place. Exceptions don’t sit unclaimed while a due date passes.

RadiusPoint, founded in 1992, delivers Utility Expense Management (UEM) alongside telecom expense management (TEM). In ExpenseLogic, that covers utility and telecom invoice intake, line item audit against contracted rates and inventory, and closed location billing exception reports. It also includes real estate system integration for service setup and disconnect, cost allocation in the client’s chart of accounts, accrual and GL interface files, and dispute and refund recovery. RadiusPoint can pay vendor invoices for clients once the client funds the account.

The approach scales. An optometry and eyewear chain grew from 170 to 1,200 locations through acquisitions and openings while RadiusPoint managed its electric, gas, water and waste bills. The published case describes missing invoices tracked in ExpenseLogic, deposits managed to their release dates and kWh and therms reported by location. If AP capacity is the pressure point, the signs it’s time to outsource utility bill pay are a useful check, and the full scope sits under RadiusPoint’s Utility Expense Management services.

At $1,500 a month, one closed store came to $18,000 a year, and every unmanaged month adds to that. Request a free demonstration or a complimentary TEM consultation to see your own portfolio in ExpenseLogic.

Frequently Asked Questions

Is utility bill management the same as Utility Expense Management?

They overlap, but the scope differs. Utility bill management is the monthly cycle of receiving, checking, paying and recording bills. Utility Expense Management usually adds recovery audits, rate and contract work and longer-range cost reduction on top of that cycle. Every later saving depends on the complete, accurate bill data that the monthly cycle produces.

Should we pay a utility bill that’s based on an estimated read?

Usually yes, if the amount is close to the same month last year, because a late payment can bring a fee. Flag the account at the same time and request a real read. If the estimate looks far off, call the utility before the due date. Ask for a corrected bill or a read, and note the dispute on the exception list.

Which utilities should a multi-site program include?

Include every service that bills a site on a recurring basis: electricity, natural gas, water, sewer and waste. Leaving one out creates a blind spot, since closed sites can keep paying for water and trash pickup long after the power is off. Put each service on the roster with its own account, meter or container record and billing cycle.

How far back can a utility bill us for usage it missed?

It depends on the state. In New York, backbills to nonresidential customers are limited to two years, and to 12 months when the utility’s own deficiency caused the underbilling. Other states set their own limits. Check your state public utility commission’s rules for nonresidential service before you accept a large catch-up bill.

What does a team need to start running this cycle?

Start with a complete roster of accounts and meters, twelve months of bill history and the current site list from real estate. Those three records let you build the expected-bill calendar, spot closed sites and set a usage baseline for each meter. Add the GL coding rules for each site, and the cycle has what it needs.

References

  1. RadiusPoint, “Utilities Mismanagement Costs $18K in Unnecessary Expenses,” case study, October 10, 2022. https://radiuspoint-expenselogic.com/open-closed-location-utilities-management-uem-case-study/
  2. RadiusPoint, case study on a retail optometry and eyewear chain’s growth from 170 to 1,200+ locations, October 10, 2022. https://radiuspoint-expenselogic.com/growth-without-the-growing-pains-170-to-1200-locations/
  3. U.S. Energy Information Administration, Electric Power Monthly, Table 5.6.A, “Average Price of Electricity to Ultimate Customers by End-Use Sector, by State, August 2026 and 2025,” released October 23, 2026. Electric Power Monthly, Table 5.6.A
  4. U.S. Energy Information Administration, “2018 Commercial Buildings Energy Consumption Survey final results,” December 2022. 2018 Commercial Buildings Energy Consumption Survey final results
  5. U.S. Energy Information Administration, 2018 CBECS Table C22, “Electricity consumption totals and conditional intensities by building activity subcategories, 2018,” December 2022. 2018 CBECS Table C22
  6. New York State Department of Public Service, “Your Rights as a Non-Residential Gas, Electric or Steam Customer,” accessed November 2026. Your Rights as a Non-Residential Gas, Electric or Steam Customer
  7. New York Codes, Rules and Regulations, Title 16, Part 13, sections 13.1 (definitions), 13.8 (meter reading and estimated bills), 13.9 (backbilling) and 13.11 (contents of bills), rules for nonresidential gas, electric and steam service. 16 NYCRR Part 13

This article is general information for finance, facilities and AP teams that manage utility bills across multiple sites. It isn’t legal, accounting or tax advice. New York rules are cited as one state’s example, and your utility’s tariff and state commission rules govern your accounts. RadiusPoint results come from specific client engagements and aren’t a guarantee of results for your organization.

Telecom and Utility Expense Management System: What to Check

TEM0

An expense management system is software that captures, approves and records business spending, and the term usually means employee travel and expense (T&E) software. Telecom and utility bills need a different kind of system, one that holds the service inventory and contracted rates, audits every line item against them and gets each bill coded and paid.

Nobody on staff submits these bills. A carrier or utility issues them to the company every month, and every charge ties back to a service ID, circuit, line, meter, contract and location. When you evaluate a system, the question that decides the rest is who owns each bill from intake to ledger.

Key Takeaways

  • “Expense management system” usually means T&E software for employee receipts and reimbursements.
  • Telecom and utility bills are issued by vendors, recur every month and tie to service IDs, meters, contracts and locations, so they need inventory, contracted rates and a line item audit that T&E tools don’t hold.
  • Accounts payable (AP) automation can capture, route and pay a carrier bill, but it isn’t built to check each line against the contract and the service inventory.
  • Test any system on 12 points, from inventory and contract rates to accrual files, closed-site exceptions, human resources (HR) roster checks and payment.
  • Settle who owns each bill from intake to ledger before you choose between software, a managed service or both.

What Is an Expense Management System?

An expense management system is software that captures, approves and records business spending, and most are built for employee expense claims. Their design centers on a person, proof of the expense and a business purpose. A carrier or utility bill has no claimant: the vendor sends it straight to the company, every month.

So a T&E system is organized around a person and a claim: who spent the money, on what, for which business purpose, and whether the receipt backs it up. Two other kinds of system also get called expense management. AP automation captures, routes and pays supplier invoices of every kind. A telecom and utility expense management system manages recurring service bills against an inventory of lines, circuits, accounts and meters. Only the third is built for the bills a carrier or utility sends, and it covers telecom expense management (TEM) and Utility Expense Management (UEM).

Employee Expense Tools vs AP Automation vs Telecom and Utility Expense Systems

The three system classes start from different documents: an employee’s receipt, a supplier’s invoice or a carrier and utility bill tied to inventory. That starting document decides what each system checks a charge against, how it codes the cost and who pays the bill. The table compares them on six points.

Point of comparison Employee T&E expense system AP automation Telecom and utility expense management system
Input document Receipts, mileage logs and corporate card charges an employee submits Supplier invoices of every kind, received by mail, email or electronic feed Recurring carrier and utility invoices, with charges by account, service ID, circuit, line or meter
Reference data Expense policy, per diem rates and the card feed Purchase orders (POs), receiving records and the vendor master Service inventory, contracted rates tied to service IDs, tariffs, site open and close dates and the HR roster
Audit method Policy checks on each claim: spending limits, missing receipts, duplicate claims Matching the invoice to the PO and receiving record, plus approval routing Line item audit of every charge against contracted rates and inventory, with exceptions for closed sites and unused services
Coding The employee’s cost center and an expense category The general ledger (GL) account from the PO or the vendor’s default GL coding and allocation by location, department, service ID or meter, plus accruals for service not yet billed
Who pays The company reimburses the employee or pays the card issuer AP pays the supplier AP pays the carrier or utility, or a provider pays from funds the company supplies
Best fit Travel, meals, mileage and other spending an employee chooses One-off and recurring supplier spending, with or without a PO Telecom, wireless and utility service across sites, lines and meters

AP automation gets further than a T&E tool: it can capture the bill, route it for approval and pay it. What it can’t do on its own is say whether each charge matches the contract and whether the service should still exist.

That’s why AP automation and a telecom and utility system usually work side by side rather than compete. The split between them, and where the two hand off at the ledger, is covered in TEM and accounts payable automation.

Why Can’t a T&E System Handle Carrier and Utility Invoices?

A T&E system checks a claim against policy and a receipt, but a carrier or utility bill can only be checked against inventory and contracts. No employee submits the bill, the invoice is its own receipt, and a wrong charge can look perfectly normal. Five differences make the mismatch practical rather than theoretical.

Nobody submits it. A T&E workflow starts when an employee files a claim and states its business purpose. A carrier or utility bill arrives at the company, at a site or in a vendor portal, and nobody attests to anything. Capturing every bill has to be a system job, or some bills get paid without review and others don’t get paid at all.

The unit is the service, not the transaction. One carrier invoice can carry charges for every line, circuit and toll-free number on an account, and one utility bill can cover several meters. Each of those charges needs its own rate check and its own cost center.

The invoice is the receipt. A T&E check confirms that the receipt matches the claim. On a carrier bill, the charge always matches the invoice, because the invoice is the only document. The real test is whether the charge matches the contracted rate and whether the service should still be there.

Errors repeat. A wrong hotel charge happens once. A wrong or unneeded recurring charge bills every month until someone stops it at the source. One RadiusPoint client was paying $1,500 a month for utilities at locations it had already closed.

Services outlive the people and places they serve. Wireless lines stay active after employees leave, and meters keep billing after stores close. Catching them takes the HR roster and the site list, and a T&E tool connects to neither.

Inventory work is where this kind of money turns up. RadiusPoint’s inventory management work recovered $174K in re-credits, the kind of recovery that starts from a list of services, not from a stack of receipts.

What Should a Telecom and Utility Expense Management System Do?

A telecom and utility expense management system should hold the inventory and contracts, audit every line, code and accrue the cost, and get bills paid. Each job depends on the one before it. An audit is only as good as the inventory and rates behind it, and a GL file is only as good as the audit.

Filing the dispute with the carrier and chasing the credit is people work, and it’s the core of telecom invoice management services.

12 Questions to Ask Before You Choose an Expense Management System

Ask each vendor to show how one carrier or utility charge moves from inventory and contract through audit, coding, accrual and payment. A demo built on sample data rarely fails. These twelve questions make the system prove each step on records shaped like yours, so you can compare answers side by side.

Questions 1 to 6: Inventory, Contracts and Audit

Question to ask What a strong answer shows
1. Can you list every line, circuit, account and meter we pay for, by location and cost center? A searchable inventory where each service carries its location, cost center, vendor account and service ID or meter number
2. Where is the contracted rate for one service ID stored, and when does that contract expire? The rate attached to the service ID, with term dates and an alert before an expiration or termination fee date
3. How does every telecom and utility bill get into the system, whatever format it arrives in? One intake path for paper, PDF, portal and electronic bills, each matched to an account in the inventory
4. Does the audit check every line on every invoice, or a sample? Every line checked against contracted rates and inventory, with each exception naming the service ID or meter
5. What happens after the audit finds an error? A dispute record tracked until the credit appears on a bill or a refund arrives
6. Can one bill be coded to our chart of accounts and split across cost centers? Allocation by location, department, service ID or meter into your own GL accounts, not a generic category

Questions 7 to 12: Ledger, Service Changes and Payment

Question to ask What a strong answer shows
7. What file does our GL receive at month-end, and does it accrue service not yet billed? An accrual file and a GL interface file in a format your enterprise resource planning (ERP) system imports
8. When a location closes, what flags a bill that keeps arriving for it? An exception report listing closed sites that still bill, and disconnects tied to your site records
9. How do you find lines still assigned to people who’ve left? Employee IDs checked against the current HR roster, with mismatches listed for action
10. How are moves, adds, changes and disconnects requested and approved? Tickets that follow approval rules you set, linked to the inventory and to the next bill
11. Who pays the audited bill, and from whose funds? A written payment model, such as a provider paying from an account you fund, with each payment tied to the audited invoice
12. Do telecom and utility bills sit in the same inventory, audit and reports? One record of services, sites and costs across carriers and utilities, so a closed site shows up on both sides

Score each answer by whether the vendor shows it on screen with data like yours, not by whether it appears on a feature list. In any telecom expense management software evaluation, questions 1, 2 and 4 carry the most weight, because every later answer depends on the inventory, the rates and the audit. A vendor that can’t show a single service ID with its contracted rate attached won’t produce a reliable accrual file either.

Question 12 matters most where IT holds the carrier bills and facilities holds the utility bills. The case for one platform for TEM and UEM comes down to seeing a closed site’s telecom and utility charges in the same place, instead of in two systems that never compare notes.

How RadiusPoint and ExpenseLogic Own the Bill From Intake to Ledger

RadiusPoint, founded in 1992, can own utility and telecom bills from intake to ledger, running audit, payment and finance data from one ExpenseLogic record. That answers the question that should decide the choice: who owns each bill between the day it arrives and the day it reaches the GL?

A system finds the error, but someone still has to dispute it, order the disconnect and chase the credit. The full comparison, including which tasks stay with your team under each model, is in TEM software vs managed TEM services. RadiusPoint offers both together: ExpenseLogic plus a team that works the account. Its expense management services page lays out how scope and pricing are set.

Measured against the twelve questions, RadiusPoint and ExpenseLogic provide:

  • Records: utility and telecom invoice intake, vendor contract management with expiration dates and rates tied to service IDs, and contract obligation alerts.
  • Audit: line item audit against contracted rates and inventory, closed location billing exception reports and employee ID validation against the HR roster.
  • Changes: moves, adds, changes and disconnects (MACD) ticketing with client-defined approval workflows, and real estate system integration for service setup and disconnect.
  • Finance outputs: accrual and GL interface files, and cost allocation in the client’s chart of accounts.
  • Payment and recovery: dispute and refund recovery. RadiusPoint can pay vendor invoices for clients once the client funds the account.

Both bill types run on the same platform. ExpenseLogic telecom expense management covers wireline, wireless and data circuits, and Utility Expense Management with ExpenseLogic covers electricity, gas, water, sewer and waste.

Published results show what that looks like in practice. For a Fortune 100 manufacturer, RadiusPoint obtained more than $450,000 in telecom refunds in the first year of service, with $850,000 in ongoing savings. ExpenseLogic is rated 4.8 from 31 reviews on Capterra, and Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 TEM Vendor SmartList. It’s also a women-owned business.

To see how ExpenseLogic and the RadiusPoint team would handle your own telecom and utility bills, request a complimentary TEM consultation or demonstration.

Frequently Asked Questions

Who should own a telecom and utility expense system inside our company?

Give each team the part it already controls, and name one owner for the whole bill. IT or the telecom manager usually owns the carrier inventory and MACD approvals, facilities or real estate owns site openings and closings, and finance or AP owns coding, accruals and payment. The system should hold one shared record, so every team sees the same services, sites and costs.

What’s the difference between TEM and Utility Expense Management?

Both manage recurring bills from intake to ledger, but they check different things. TEM audits carrier charges against contracted rates and an inventory of lines, circuits and service IDs. Utility Expense Management audits utility charges at the meter, against tariff or contract rates and usage history. RadiusPoint covers both in ExpenseLogic, so a site’s telecom and utility costs sit in one record.

Will a telecom and utility expense system replace our ERP or AP software?

No. It sits in front of them. The telecom and utility system audits and codes each bill, then sends GL and accrual files your ERP imports and an approved amount AP can pay. Your ERP stays the book of record.

Are employee phone stipends a T&E expense or a telecom expense?

It depends on who holds the account. A stipend or reimbursement for an employee’s own phone plan runs through T&E or payroll, because the employee pays the carrier. A line on a company carrier account is a telecom expense: it belongs in the inventory, gets audited against the contract and should be checked against the HR roster when someone leaves.

References

  1. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  2. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews. capterra.com
  3. RadiusPoint, “Utilities Mismanagement Costs $18K in Unnecessary Expenses.”
  4. RadiusPoint, “Inventory Management Helps Recovering $174K in Credits,” October 12, 2022.
  5. RadiusPoint, “$1.3M in Telecom Refunds and Cost Savings: Case Study,” June 10, 2023.

This article is general information for finance, accounts payable, IT and facilities teams comparing expense management systems. It isn’t legal or accounting advice. RadiusPoint results cited here come from specific client engagements and aren’t a guarantee of results for any organization.

Utility Contract Management: Tracking Supply Terms, Renewals and Rates

UEM0

Utility contract management means tracking signed electricity, gas and utility service contracts so each renewal is decided on time and each bill matches the contract. Miss a notice window and accounts can roll onto holdover, month-to-month or default service pricing. RadiusPoint ties contract end dates and rates to each account in ExpenseLogic, so audits catch off-contract bills.

Key Takeaways

  • Keep one contract register that lists every account and meter a supply contract covers, with its end date, notice window, price structure and pass-through charges.
  • The contract or a state rule decides what happens at expiry: holdover or month-to-month pricing, a new term, or a return to the utility’s default service.
  • Pennsylvania and Texas notice rules protect small business accounts below set demand limits, so larger accounts depend on their own contract terms.
  • Check each bill’s supply rate, service dates, usage and pass-through lines against the contract, and handle tariff and rate class questions separately.
  • RadiusPoint’s published results include $120,000 a year from contract rate optimization, and one client was paying $18,000 a year for utilities at closed locations.

What Is Utility Contract Management?

Utility contract management is what a business does after signing energy contracts: record the terms, track the dates and hold each bill to the contract. It covers electricity and natural gas supply contracts in states that allow retail choice, plus the service agreements a site signs with its local utility. Contract software vendors use the same phrase for contracts that utility companies hold, which is a different job.

Some teams call it energy contract management when the scope stops at electricity and gas supply. Either way, the contract matters because supply and delivery are billed on different terms. The U.S. Energy Information Administration (EIA) notes that the distribution utility delivers contracted electricity to the customer’s meter and charges for that service, whichever supplier the customer picks. In EIA’s 2019 count, 19 states and the District of Columbia let some commercial and industrial customers choose a competitive supplier, and 15 of those states plus the District allowed it in all sectors.

Choosing the supplier is utility procurement. Contract management starts once the signature is on the page, and in states with deregulated utilities a multi-site company can hold different suppliers, terms and end dates at once.

What Happens When a Utility Supply Contract Expires?

At expiry, the end-of-term clause or a state rule decides the price: a holdover or month-to-month rate, a renewal term or the utility’s default service. None of those carries the negotiated price automatically. If nobody acts on the supplier’s notices, the account moves to whichever option the contract names, and the bill changes with it.

Texas, for example, requires a retail electric provider to serve a small commercial customer who takes no action under a month-to-month default renewal product, and that product’s price may vary between billing cycles. Pennsylvania’s Public Utility Commission (PUC) warns that a fixed rate may change to a monthly variable rate when a customer ignores the renewal notices. Your company’s counsel should read the end-of-term, renewal and termination language before anyone relies on it.

What a Holdover Rate Can Cost: An Illustrative Example

This is an illustration, not a market quote. Take a site that uses 40,000 kilowatt-hours (kWh) a month. EIA’s average revenue per kWh for commercial customers, its proxy for retail price, was 14.47 cents in August 2026, up 4.3% from August 2025. At that all-in average, which includes delivery, the site’s monthly bill would be about $5,788.

Each 1 cent per kWh between the contract price and the price after expiry changes that bill by $400 a month, or $4,800 over 12 months. Natural gas moves too: EIA’s U.S. average commercial price was $10.98 per thousand cubic feet in 2025, against $10.07 in 2024.

What to Record in a Utility Contract Register

A utility contract register records each term that changes a bill or a deadline, beside where it appears in the contract and on the bill. Build the register by account and meter, not by contract, so each bill can be matched to its terms.

Term to record Why it matters Where to find it
Supplier and contract ID Ties each bill and notice to the right agreement Signature page; supplier name on the bill
Accounts and meters covered Only listed accounts get the contract price Account schedule; account and meter numbers on the bill
Start and end dates Service periods inside the term carry the contract price Term clause; service period dates on the bill
Notice window Missing it can renew the contract or start holdover pricing Renewal or termination clause; supplier expiry notices
Pricing after expiry Sets the holdover, month-to-month, renewal or default outcome End-of-term clause; supplier’s expiry notice
Price structure Fixed and index pricing need different bill checks Pricing exhibit; supply rate line on the bill
Pass-through charges Shows which costs can appear on top of the contract price Pricing exhibit; separate charge lines on the bill
Usage limits Usage outside an agreed band may be billed at another price Volume clause; billed kWh or therms
Site changes and early termination Sets how sites are added or removed and what leaving early costs Site change and termination clauses; not on the bill

Keep the register in the same system that receives the bills. That way an expired term, a missing meter or a new pass-through line gets noticed in the month it first appears.

Renewal Notice Rules Protect Small Accounts, Not Large Ones

In Pennsylvania and Texas, supplier notice rules protect residential and small business accounts, so a larger commercial account relies on its own contract. The cutoffs are set by demand, so one company can have sites on both sides of the line. Track which accounts qualify, because the notices you can expect differ by site.

Pennsylvania defines a small business electric customer as one whose maximum registered peak load was under 25 kilowatts (kW) in the last 12 months. For those accounts, the PUC explains that the supplier sends an initial notice 45 to 60 days before a contract expires and an options notice 30 days before. The natural gas rule moves the dates earlier, with an initial notice 60 to 75 days out and an options notice at least 45 days out. A gas customer who answers neither notice is converted to a month-to-month or fixed-duration contract, and neither can carry cancellation fees.

Texas draws its line at a peak demand under 50 kW during any 12-month period. A retail electric provider must send a small commercial customer at least three written expiration notices during the last third of a fixed-rate term, with the final one at least 14 days before expiry. If the provider skips the required notice, it must keep serving the customer under the fixed-rate terms until it gives notice. Larger Texas customers may agree in writing to higher or lower protections than the rules set.

How Do You Check a Utility Bill Against the Contract Price?

Match the bill’s supply lines to the register: supplier and account, service dates inside the term, contract rate times usage, and only allowed pass-throughs. A failed line means the bill wasn’t priced on the contract, whether the cause is a lapsed term, a meter missing from the schedule or a billing error.

These bill lines show whether the contract price was applied:

  • Supplier name and account number match the register, whether they appear on the utility’s consolidated bill or a separate supplier invoice.
  • Service period dates fall inside the contract term. Texas lets a provider bill a small commercial account the term price through the first meter read on or after a calendar end date, so expect one transition bill.
  • The supply rate per kWh or per therm matches the contract price, or the contract’s index formula for that month.
  • Billed usage times the contract rate equals the supply charge, within rounding.
  • Each pass-through line appears in the pricing exhibit, and no new one shows up mid-term.
  • Every meter billed by the supplier is on the contract’s account schedule.

These are the same lines you’d read to audit a utility bill for any error, with the register supplying the expected values. Delivery charges follow the utility’s published tariff rather than the supply contract, so a wrong rate class is a rate reclassification question, not a contract one.

RadiusPoint runs this check as part of its line item audit against contracted rates and inventory. Because ExpenseLogic holds each contract’s expiration date and rates against the account, a bill priced after a lapsed term gets flagged by the audit. RadiusPoint also handles dispute and refund recovery. Its published results include $120,000 a year from contract rate optimization in a telecom engagement, where services were moved onto the client’s corporate contract rates.

Adding and Removing Sites Under a Supply Contract

Run each site change through the contract’s site clause, naming the account and meter, and update the register, or the bill and contract drift apart. A new store billed at the utility’s default price, or a closed store still billed under the contract, costs money every month it goes unnoticed.

Openings are the quieter miss. A site that isn’t added to the account schedule never gets the contract price, and nothing on its bill says so. Closings run the other way, because the account keeps billing until someone stops it. One RadiusPoint multi-location client was paying $1,500 a month, $18,000 a year, for utilities at closed locations.

For Texas small commercial accounts, a contract covers only the location it names, and a customer who moves out owes no early termination fee once it gives a forwarding address and any evidence of the move the provider requires. Volume raises the stakes: RadiusPoint supported one client’s growth from 170 to 1,200 locations through acquisitions and openings, and each new location added utility accounts to track.

Who Should Own Utility Contracts After Signature?

One owner should hold the contract register, the bill and the ledger entry, because renewals, audits and accruals all depend on the same account data. Split the work across procurement, facilities and accounts payable, and each team sees only its own piece of an expiring contract.

RadiusPoint can own the utility and telecom bill lifecycle for a client, from invoice intake and line item audit to the data finance uses afterward. Its vendor contract management ties expiration dates and rates to service IDs, and contract obligation alerts cover termination dates and fees. The same ExpenseLogic record feeds accrual and general ledger interface files, cost allocation in the client’s chart of accounts and closed location billing exception reports. Real estate system integration supports service setup and disconnect when sites open or close. RadiusPoint can pay vendor invoices for clients once the client funds the account.

RadiusPoint delivers this work through its Utility Expense Management services on the ExpenseLogic platform. Capterra reviewers rate ExpenseLogic 4.8 out of 5 across 31 reviews, and Amalgam Insights listed RadiusPoint among its 2024 Distinguished Vendors for telecom expense management. Each month a lapsed contract or a closed site goes unnoticed, the same off-contract charge posts again. To see how RadiusPoint and ExpenseLogic would track your supply contracts and check each bill against them, request a free demonstration.

Frequently Asked Questions

Can we switch suppliers while an account is on a holdover rate?

It depends on the holdover terms, though state rules help small accounts. In Texas, a month-to-month contract can’t contain a termination fee or penalty. Pennsylvania’s natural gas rule bars cancellation fees in a contract converted after the customer ignores both expiry notices. Larger accounts outside those rules should check the holdover clause for its own exit terms before signing with a new supplier.

Does our energy broker track renewal dates for us?

Only if your agreement with the broker says so. The supply contract is between your company and the supplier, so the notice deadlines are yours to meet either way. Keep your own register with each end date and notice window, and treat a broker’s reminder as a second alert rather than the only one.

How early should we start on a supply contract renewal?

Start from the earliest notice deadline in the contract, not the end date. Some contracts require written notice well before expiry, and missing it can renew or roll the account automatically. For small Pennsylvania electric accounts, the first supplier notice arrives 45 to 60 days out, so set your register alert ahead of that date to leave time for offers and approval.

Is a utility bill audit the same as utility contract management?

No, but each depends on the other. A bill audit checks charges against contract prices, tariffs and usage. Contract management keeps the register that tells the audit which price, term and account list apply, and it handles renewals and site changes. Without current contract data, an audit can’t tell that a bill was priced after the term ended.

References

  1. U.S. Energy Information Administration, “Electricity Monthly Update, End Use: August 2026,” released October 23, 2026. Electricity Monthly Update, End Use: August 2026
  2. U.S. Energy Information Administration, “U.S. Price of Natural Gas Sold to Commercial Consumers,” annual series, released October 30, 2026. U.S. Price of Natural Gas Sold to Commercial Consumers
  3. U.S. Energy Information Administration, “Can customers choose their electricity supplier?” Frequently Asked Questions. Can customers choose their electricity supplier?
  4. U.S. Energy Information Administration, “Participation in electricity customer choice programs has remained unchanged since 2013,” Today in Energy, November 1, 2019. Participation in electricity customer choice programs has remained unchanged since 2013
  5. 52 Pa. Code § 54.2, “Definitions,” via Cornell Legal Information Institute. 52 Pa. Code § 54.2
  6. Pennsylvania Public Utility Commission, “Understanding Contracts,” PAPowerSwitch (on 52 Pa. Code § 54.10 notices). Understanding Contracts
  7. 52 Pa. Code § 62.81, “Notice of contract expiration or change in terms for residential and small business customers,” via Cornell Legal Information Institute. 52 Pa. Code § 62.81
  8. 16 Tex. Admin. Code § 25.471, “General Provisions of Customer Protection Rules,” via Cornell Legal Information Institute. 16 Tex. Admin. Code § 25.471
  9. 16 Tex. Admin. Code § 25.475, “General Retail Electric Provider Requirements and Information Disclosures to Residential and Small Commercial Customers,” via Cornell Legal Information Institute. 16 Tex. Admin. Code § 25.475
  10. Capterra, “ExpenseLogic,” 4.8 from 31 reviews, page updated September 29, 2026. ExpenseLogic
  11. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions
  12. RadiusPoint, “Telecom Expense Management Solution.”
  13. RadiusPoint, “Utilities Mismanagement Costs $18K in Unnecessary Expenses.”
  14. RadiusPoint, “Normalizing Invoice Processing and Payment in Hyper-Growth Phase.”

General information only, not legal, tax or energy procurement advice. State rules are summarized rather than reproduced in full, apply only to the customer classes they name and can change, so check the current text before relying on them. RadiusPoint results cited come from specific client engagements and aren’t a guarantee of results for any organization.

Capex vs Opex for Telecom and Utility Spend

Financial0

One carrier invoice can carry a router the company will use for years, the charge to install it and a month of internet service that’s used up before the books close. Capex vs opex is the split between spending that buys a lasting asset and spending that runs the business this period. Capital expenditure (capex) pays for assets that serve the business for more than a year, so it goes on the balance sheet and is depreciated over the asset’s useful life. Operating expenditure (opex) is the cost of running the business in the current period, and it’s expensed when it’s incurred.

For telecom and utility spend, most of the bill is opex. Monthly carrier service, wireless plans, usage, the taxes on that service, and utility usage and demand charges are operating expenses. The capital items are narrower: equipment the company buys and owns, the installation and sales tax that come with it, company-owned network build-outs and certain software implementation costs. Leased equipment and device installment plans sit in between and need their own review. Because one invoice can hold all of these, the classification is decided line by line, not invoice by invoice, and it follows your company’s own capitalization policy and your auditor’s view.

That’s where invoice handling and accounting meet. RadiusPoint, founded in 1992, runs telecom expense management (TEM) and Utility Expense Management (UEM) for clients through ExpenseLogic, its expense management platform, with a team that audits each invoice line against contracted rates and inventory. Line-level review catches more than misfiled equipment. One multi-location RadiusPoint client was paying $1,500 a month, $18,000 a year, for utilities at closed locations, an operating expense that shouldn’t have existed, and RadiusPoint’s inventory management work recovered $174K in re-credits. Charges like these look like ordinary opex when a bill is coded as one monthly total.

Key Takeaways

  • Capex buys an asset that serves the business for more than a year; opex is the cost of running it this period. Most telecom and utility charges are opex.
  • Equipment the company buys and owns, plus its installation and sales tax, can be capitalized when it clears the company’s capitalization threshold.
  • Utility usage, delivery and demand charges are operating expenses, and refundable deposits aren’t expenses at all.
  • Equipment rentals may be leases that belong on the balance sheet, and device installments repay a purchase rather than pay for a month of service.
  • One carrier invoice can mix every one of these, so classification belongs at the line level, on an audited and coded invoice record.

Short version: Code recurring telecom and utility charges as opex, then pull owned equipment (with its installation and sales tax), rentals and device installments out line by line for your capitalization policy and auditor to settle.

What Is the Difference Between Capex and Opex?

Capex buys or improves an asset the business will use for more than a year; opex pays for what it uses up this period. The difference is timing. Capex lands on the balance sheet and reaches the income statement a piece at a time through depreciation. Opex hits the income statement in full in the period it’s incurred.

For federal tax, Internal Revenue Service (IRS) Publication 946 sets out the tests for depreciable property. It must be property you own, used in your business or income-producing activity, with a determinable useful life, and expected to last more than 1 year. Financial reporting follows the company’s own capitalization policy, which commonly adds a dollar threshold below which even durable items are expensed when bought.

Typical capex includes a phone system, the cabling in a new office, a building or a major improvement to one. Typical opex includes rent, payroll, carrier service and electricity. The label matters to finance for three reasons:

  • Budgets. Capital spending usually goes through a separate approval cycle from the operating budget, so a misfiled item can sit in the wrong budget all year.
  • Earnings measures. Depreciation sits outside earnings before interest, taxes, depreciation and amortization (EBITDA), so moving a cost between capex and opex changes EBITDA.
  • Tax timing. A cost that’s expensed and a cost that’s depreciated can reach the tax return in different years, and tax depreciation rules don’t always match the books.

How Telecom and Utility Invoice Lines Are Usually Classified

Recurring service, usage, utility consumption and demand charges are opex, while owned equipment and the costs to install it are capital candidates. Rentals, device installments and deposits each need their own treatment. The table maps each common line type to its usual treatment, the rule behind it and what to check on the invoice before anyone codes it.

Invoice line type Usual treatment Rule or test behind it What to check on the invoice
Monthly recurring service (circuits, internet, voice, wireless plans) Opex IRS Publication 946: depreciable property must be property you own and expected to last more than 1 year. The carrier owns the network, and the service is used up each month. Service ID matches inventory and the contracted rate; billing period dates
Usage and overage (minutes, data, roaming) Opex Consumed in the billing period; nothing is owned afterward Usage ties to an active line or circuit; spikes in roaming or overage
Taxes, surcharges and regulatory fees Follow the line they’re charged on: opex on service, part of the equipment’s cost on a purchase IRS Publication 551 lists sales tax in the cost basis of property you buy Which line each tax applies to; exemption status where the company holds it
Installation and other non-recurring charges Opex when they set up a carrier’s service; part of the equipment’s cost when they install equipment the company buys IRS Publication 551 lists “Installation and testing” in cost basis; Publication 946 requires ownership Whether the work was on carrier-owned or company-owned equipment; the matching order
Equipment purchase (routers, phone systems, handsets bought outright) Capital candidate if it lasts more than a year and clears the capitalization threshold; otherwise expensed when bought IRS Publication 946 ownership and useful life tests; the company’s capitalization policy; for tax, the de minimis safe harbor in Treasury Regulation 1.263(a)-1(f) Serial numbers, quantity, unit price and proof of receipt
Device installment (monthly payment on a financed phone or tablet) Not a monthly service cost: the device is recorded when acquired, and installments repay the balance Ownership under the installment agreement; the company’s capitalization policy Installment number, remaining balance and whether the device’s user is still employed
Leased or rented equipment Possible lease, with a right-of-use asset and lease liability, unless a short-term election applies Accounting Standards Codification (ASC) 842, Leases; IFRS 16 for companies reporting under International Financial Reporting Standards (IFRS) Rental line separate from service; term; whether specific equipment is identified
Utility usage and delivery (kilowatt-hours, therms, gallons) Opex Consumed in the billing period Meter number, read dates and the tariff or contract rate
Utility demand charges Opex Billed on peak demand within the billing period; no asset is acquired Peak kilowatts, demand multiplier and rate schedule
Deposits Not an expense: a refundable deposit stays on the balance sheet until it’s refunded or applied Refund terms in the utility’s tariff or the carrier agreement Deposit amount, refund terms and status when an account closes
Late fees and finance charges Opex Charged for paying after the due date; nothing is acquired Payment date against due date; repeat fees on the same account

Usual treatment isn’t final treatment. Most telecom capex vs opex questions come down to the middle rows: installation, equipment, installments and rentals. Those lines are where the same word on an invoice can mean an operating cost on one bill and part of an asset’s cost on the next, which is why the “what to check” column matters as much as the treatment column.

Which Telecom Costs Can Be Capitalized?

Telecom costs can be capitalized when they buy or build a lasting company asset: owned equipment, the cabling behind it or qualifying software implementation work. The carrier’s service itself isn’t an asset the company owns, so the monthly charges for it stay opex however long the contract runs.

Equipment the company buys. Phone systems, routers, switches, wireless access points and handsets bought outright are capital candidates. IRS Publication 551 says the cost of property you buy “also includes” amounts paid for items such as sales tax, freight, and installation and testing. So when a carrier bills a router, its shipping, its sales tax and the technician who set it up, those lines belong together under the company’s capitalization policy, even if they arrive on different invoices.

Small items and the tax safe harbor. For federal tax, the de minimis safe harbor in Treasury Regulation 1.263(a)-1(f) lets a business that elects it deduct tangible property up to $5,000 per invoice or item if it has an applicable financial statement. Without one, the regulation sets $500, which IRS Notice 2015-82 raised to $2,500 for costs incurred in taxable years beginning on or after January 1, 2016. The election is made each year with the tax return and works alongside the company’s accounting procedures. It isn’t a book capitalization threshold, so confirm both with your tax adviser.

Network build-outs. Structured cabling, equipment rooms and fiber the company owns can be capitalized with the project they serve. Construction charges are different: when a carrier bills to extend its own network to your building, the carrier usually keeps what it builds, so the charge doesn’t create property the company owns. In a leased office, check how your policy treats improvements the company pays for but can’t take with it.

How Should Finance Treat Cloud Software Implementation Costs?

Implementation costs for a cloud service can be capitalized like internal-use software and expensed over the hosting term, while subscription fees stay opex. A 2025 standards update, effective for annual reporting periods beginning after December 15, 2027, changes when capitalization starts. For a carrier portal or a TEM or UEM platform, the answer depends on the contract and the work performed.

Software implementation. A cloud subscription is a service, so its fees are opex. Implementation work is another matter. Under Accounting Standards Update (ASU) 2018-15, issued by the Financial Accounting Standards Board (FASB) in August 2018, a customer capitalizes implementation costs of a cloud service contract under the same requirements as internal-use software. It then expenses them over the term of the hosting arrangement in the same income statement line as the hosting fees.

FASB’s ASU 2025-06 (September 2025) removes the project stages from that guidance for annual reporting periods beginning after December 15, 2027, with early adoption permitted. Under it, capitalization starts when management has authorized and committed to funding the project and it’s probable the project will be completed and the software used as intended. The same questions come up when a company connects a carrier portal or a TEM or UEM platform to its enterprise resource planning (ERP) system, and the answer depends on the contract and the work performed.

Are Utility Bills Ever Capital Expenses?

Utility bills are operating expenses in almost every case, because electricity, gas, water and demand charges pay for service used in the billing period. The exceptions are narrow: equipment the company buys, one-time charges tied to a construction project, and deposits, which aren’t expenses at all. Treat them as review items, not as reasons to reclassify the utility account.

Demand charges cause the most confusion. They’re billed on the highest demand recorded during the billing period, so they can feel like a capacity investment, but they buy nothing the company keeps after the period ends. They stay opex, coded with the meter’s usage charges.

The lines worth a second look are these:

  • Equipment the company buys: submeters, building controls or on-site generation. These usually come from vendors rather than the utility and follow the same equipment rules as telecom hardware.
  • Construction-related charges: a one-time charge to connect or extend service to a new facility, or utilities used while a building is under construction and not yet in service. Either may belong with the project’s cost under the company’s policy, so route it to whoever owns the project accounting.
  • Rental lines: equipment the utility rents to the site, such as outdoor lighting, belongs in the same lease review as telecom rentals.
  • Deposits: a refundable deposit is money the company expects back. Track it by account so it’s recovered when the account closes.

For manufacturers, plant utilities may also flow into inventory cost as production overhead, which is a cost accounting question rather than a capex one.

The bigger utility risk isn’t misclassification. It’s opex that shouldn’t be paid at all. The multi-location client paying $1,500 a month for utilities at closed locations was paying an operating expense for sites it no longer used. A utility bill audit checks each meter’s charges against the tariff and the site list, and vacant utility cost recovery goes after charges at units that should have moved to a tenant.

Why Does Line-Level Coding Decide the Classification?

Line-level coding decides the classification because one carrier invoice can hold service, equipment, installation and rentals, and each follows a different rule. Coding the invoice total to one telecom expense account overstates the period’s opex, keeps equipment off the fixed-asset register and hides rentals from the lease review.

Take the first invoice a carrier sends for a new branch office. The figures in this example are illustrative, not a client bill.

Invoice line (example) Amount Coding Why
Dedicated internet access, monthly $650 Opex, telecom service Carrier-owned service, used up this month
Hosted voice, 20 seats, monthly $400 Opex, telecom service Service, not property
Installation, new internet circuit (one-time) $500 Opex, unless policy says otherwise Sets up the carrier’s service on equipment the carrier owns
Router, purchased $2,000 Capital candidate Owned equipment that lasts more than a year
Router installation and configuration $300 With the router Installation and testing are part of cost (IRS Publication 551)
Sales tax on router $140 With the router Sales tax is part of cost (IRS Publication 551)
Taxes and regulatory surcharges on service $95 Opex, with the service Follows the service lines
Firewall equipment rental, monthly $75 Lease review Rental of specific equipment; ASC 842 test
Late fee, prior invoice $25 Opex Nothing acquired
Invoice total $4,185

Coded line by line, this invoice splits into $1,670 of opex, $2,440 of capital candidates (if the router clears the capitalization threshold) and a $75 rental for lease review. Coded as one total, all $4,185 lands in telecom expense. That overstates this month’s opex by more than half, leaves the router off the fixed-asset register and skips the rental entirely. The late fee also deserves its own flag: it’s a process failure, not a cost of service.

The same split has to survive month-end. Coded lines reach the general ledger (GL) through a GL interface file at month-end close, and a telecom accrual file estimates service used but not yet billed. Neither works if the coding happens at the invoice total. In ExpenseLogic, RadiusPoint applies cost allocation across departments in the client’s own chart of accounts, so the opex lines reach the right cost centers.

How Leases and Device Installment Plans Change the Answer

Equipment rentals may be leases that belong on the balance sheet, and device installments repay a purchase instead of paying for monthly service. Neither fits a simple capex or opex label. Flag both at the line level so the lease and fixed-asset owners see them before the period closes.

Leases. FASB’s ASU 2016-02 created Topic 842. Under Topic 842, “a contract, or part of a contract, that conveys the right to control the use of identified property, plant, or equipment (an identified asset) for a period of time in exchange for consideration” is a lease. When a contract meets that test, the lessee recognizes a lease liability and a right-of-use asset. For leases with a term of 12 months or less, a lessee can elect, by class of underlying asset, not to recognize lease assets and liabilities. For companies reporting under IFRS, the IFRS Foundation describes IFRS 16 as a single lessee model that requires a lessee to recognize assets and liabilities for all leases with a term of more than 12 months, unless the underlying asset is of low value.

On a telecom invoice, the test turns on control of specific equipment. A standard internet or voice service often fails it, because the carrier decides which equipment and fiber carry the traffic. A rental of named equipment at your site, or a long-term right to specific fiber, can pass it. That’s a judgment for the lease accounting team, and the invoice’s job is to get the line in front of them.

Device installments. A wireless bill can show a monthly service plan and a monthly device payment side by side. Under a typical installment agreement, the business buys the device and pays for it over a set number of months, so read the agreement to confirm who owns it.

If the business owns it, the device’s cost belongs to the month it was acquired. Above the capitalization threshold it’s equipment; below it, it’s expensed when acquired, not spread across the installment months. Each installment then reduces the balance owed. Coding installments as wireless service mixes equipment into service spend, which inflates the per-line cost used to compare rate plans. It also hides the balance that may come due when an employee leaves and the line is canceled.

How RadiusPoint and ExpenseLogic Keep Telecom and Utility Spend Coded Correctly

RadiusPoint can own the telecom and utility bill lifecycle, from invoice intake and line item audit to payment and the coded data finance uses. Opex lines arrive coded to the client’s chart of accounts. ExpenseLogic and RadiusPoint’s team cover each part of that record:

  • Intake and audit: utility and telecom invoice intake, and line item audit against contracted rates and inventory.
  • Payment: RadiusPoint can pay vendor invoices for clients once the client funds the account.
  • Data for finance: accrual and GL interface files, and cost allocation in the client’s chart of accounts.
  • Orders and changes: moves, adds, changes and disconnects (MACD) run through ticketing with client-defined approval workflows.
  • Contracts: vendor contract management with expiration dates and rates tied to service IDs, plus contract obligation alerts.
  • Sites and people: closed location billing exception reports, real estate system integration for service setup and disconnect, and employee ID validation against the HR roster.
  • Recovery: dispute and refund recovery when an audited line doesn’t match the contract.

That record scales with the business. RadiusPoint supported one client’s growth from 170 to 1,200 locations through acquisitions and openings, and each new site brings new carrier and utility accounts to code. The same coded history is what lets a telecom team prove TEM savings to finance line by line instead of by estimate. For the platform behind it, see ExpenseLogic telecom expense management and Utility Expense Management with ExpenseLogic.

RadiusPoint is a women-owned business. Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 TEM Vendor SmartList, and ExpenseLogic is rated 4.8 from 31 reviews on Capterra.

Every month an invoice is coded as one total, equipment stays off the asset register and charges that shouldn’t be paid keep looking like routine opex. To see your own telecom and utility invoices coded line by line, request a free demonstration of ExpenseLogic.

Frequently Asked Questions

Is a company phone a capex or opex purchase?

It depends on what the phone cost and on your capitalization policy. A phone bought outright that lasts more than a year and clears your threshold is capitalized; one below the threshold is expensed when it’s acquired. The monthly plan is opex either way. Paying for the phone in installments doesn’t change when its cost is recognized; it only changes when the cash goes out.

Is a cloud expense management subscription capex or opex?

The subscription fee is opex, because it pays for a hosted service. Implementation costs can be different. Under ASU 2018-15, a customer capitalizes qualifying implementation costs for a cloud service contract and expenses them over the term of the hosting arrangement, in the same income statement line as the subscription fees. Which costs qualify is a judgment for your accounting team and auditor.

What goes wrong if equipment gets coded as telecom expense?

The month’s opex is overstated, the asset never reaches the fixed-asset register, and later periods miss the depreciation that should have spread its cost. Budget owners see a spike they can’t explain, and per-line service costs look higher than the contract allows, which skews rate plan reviews. The reverse error, capitalizing service charges, overstates assets and flatters the current period’s earnings.

Should utility deposits be coded to the utilities expense account?

No. A refundable deposit is money the utility holds and should return, so it belongs on the balance sheet until it’s refunded or applied to a final bill. Coding it to utilities expense overstates that month’s cost and makes the deposit easy to forget. Track deposits by account and site, and check for them every time a location closes or service moves to a new account.

Who should decide whether a telecom charge gets capitalized?

Your company’s accounting policy decides, applied by whoever owns that policy, usually the controller, with your auditor reviewing the result. Accounts payable (AP) and the telecom team supply what the decision needs: the invoice line, the order behind it, serial numbers and the contract terms. A charge gets classified correctly only when that line-level detail reaches the person applying the policy.

References

  1. Financial Accounting Standards Board, “Accounting Standards Update No. 2016-02, Leases (Topic 842),” February 2016. storage.fasb.org
  2. Financial Accounting Standards Board, “Accounting Standards Update No. 2018-15, Intangibles, Goodwill and Other, Internal-Use Software (Subtopic 350-40): Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract,” August 2018. storage.fasb.org
  3. Financial Accounting Standards Board, “Accounting Standards Update 2025-06, Intangibles, Goodwill and Other, Internal-Use Software (Subtopic 350-40): Targeted Improvements to the Accounting for Internal-Use Software,” September 2025. storage.fasb.org
  4. IFRS Foundation, “IFRS 16 Leases,” issued January 2016. ifrs.org
  5. Internal Revenue Service, “Publication 946 (2025), How To Depreciate Property.” irs.gov
  6. Internal Revenue Service, “Publication 551 (12/2025), Basis of Assets,” revised December 2025. irs.gov
  7. Internal Revenue Service, “Tangible property final regulations.” irs.gov
  8. Code of Federal Regulations, Title 26, Section 1.263(a)-1, “Capital expenditures; in general,” Legal Information Institute, Cornell Law School. law.cornell.edu
  9. Internal Revenue Service, Notice 2015-82, Internal Revenue Bulletin 2015-50, December 14, 2015. irs.gov
  10. RadiusPoint, “Utilities Mismanagement Costs $18K in Unnecessary Expenses.”
  11. RadiusPoint, “Inventory Management Helps Recovering $174K in Credits,” October 12, 2022.
  12. RadiusPoint, “Normalizing Invoice Processing and Payment in Hyper-Growth Phase.”
  13. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  14. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews. capterra.com

This article is general information for finance, accounts payable and telecom teams. It isn’t accounting, tax, legal or audit advice. How any charge is classified follows your company’s capitalization policy, your auditor’s review and, for tax, your tax adviser. The FASB, IFRS Foundation and IRS materials cited are summarized, not reproduced in full, and the invoice example uses illustrative figures. RadiusPoint results cited come from specific client engagements and aren’t a guarantee of results for any organization.

Telecom M&A Integration Savings: How to Size, Capture and Prove Them

TEM0

Trace a lost telecom saving backward from the twelve-month integration review. The deal model shows it as captured. The integration tracker marks the duplicate circuits closed in month three. The disconnect orders went in during month four, but no carrier confirmation came back and nobody checked the next invoice. Meanwhile accounts payable (AP) kept paying the acquired company’s old accounts, because once the two AP teams merged, those invoices went into the payment run without a line-item review. The saving was booked. It was never realized.

Telecom M&A integration savings are the recurring costs a buyer removes from the combined company’s telecom and related bills after a deal closes: duplicate circuits and accounts, rates the larger company can now improve, numbers billing on the wrong account, services that were never part of the deal and sites that closed but still bill.

The short answer is that an integration saving counts only when three records agree: an invoice baseline, a dated action (a disconnect, a move or a new rate) and a later invoice showing the charge gone or lower. Size each category from both companies’ invoices rather than from a percentage. Take the savings that need no contract change first, time contract consolidation to notice windows, and report run-rate savings apart from one-time credits so finance can tie the number to the general ledger (GL).

RadiusPoint, founded in 1992, does this work for clients through ExpenseLogic, its expense management platform, and a telecom expense management (TEM) team that audits every invoice line against contracted rates and inventory. This guide is for the finance, corporate development and telecom leads who have to stand behind the savings number after the deal team moves on.

Key Takeaways

  • Telecom M&A integration savings come from six places: duplicate circuits and accounts, contract consolidation, numbers on the wrong account, services outside the deal, closed sites still billing and utilities at closed locations.
  • Size each category from twelve months of both companies’ invoices, then subtract the one-time costs of capturing it, such as early termination fees, overlap months and transition services fees.
  • Savings that need no contract change can come first. Duplicate circuits wait for cutover, and contract consolidation waits for notice windows.
  • A saving is proven when the baseline invoice, the action record and a later invoice agree, with run-rate savings reported apart from one-time credits.
  • Put utilities at closed and consolidated sites in the same savings plan as telecom, with the same baseline, action record and invoice proof.

Short version: Don’t report a telecom integration saving until a later invoice shows the charge gone or lower, and size every category from both companies’ invoices before you trust the number in the deal model.

Where Do Telecom M&A Integration Savings Come From?

Telecom M&A integration savings come from overlap and leftovers: services both companies pay for, and services the combined company no longer needs. Overlap savings usually sit inside contracts, so they take longer. Leftovers are faster to remove: numbers on the wrong account, services that came across without being part of the deal, and sites that closed but still bill.

Overlap shows up in three ways. The two companies may run duplicate circuits and accounts at shared sites or between the same locations. They may run two networks or two sets of voice services that now do one job. And they usually hold separate contracts for the same services, where the combined volume can support a better rate once the terms allow a change.

Leftovers take four forms. Long distance and toll-free numbers stay on the acquired company’s account at its old rates, or keep billing after nobody needs them. Lines and services transfer to the buyer even though they serve the seller’s retained business or a site outside the purchase agreement. Circuits and lines keep billing at sites the integration closed or merged. And electric, gas, water and waste accounts keep billing at those same closed sites, usually outside the telecom plan entirely.

RadiusPoint’s published client results show what single categories can be worth. In those results, eliminating unneeded toll-free numbers saved $18,000 a year, and contract rate optimization saved $120,000 a year. Inventory management work recovered $174K in re-credits for a client whose vendors kept billing lines after disconnects were requested. A multi-location client was paying $1,500 a month, $18,000 a year, for utilities at closed locations. Each is one client’s result, not a forecast for your deal.

The split between overlap and leftovers shapes any post-acquisition telecom cost reduction plan. Leftovers can usually be cut in the first months, while overlap often waits for a cutover or a contract date.

Savings Category Table: Where Each Shows Up and How to Size It

Each integration savings category leaves its own trace on the invoices, and that trace sets both the sizing method and the proof finance will accept. Use the table as a worksheet, one row per category, filled in for every billing account both companies hold. Size from the invoice rather than the contract, because the invoice is what the combined company pays.

Savings category Where it shows up on invoices How to size it Proof finance accepts
1. Duplicate circuits and accounts Two billing account numbers (BANs) for one site, two internet or data circuits at one address, two networks linking the same locations Monthly charge of the service you’ll retire, times the months left after the disconnect date, minus overlap months and install charges for the survivor Disconnect ticket, carrier confirmation and the first invoice without the charge
2. Contract consolidation and rate leverage The same service billed at different rates on each company’s contract Billed rate minus the new contracted rate, times current volume, from the new rate’s effective date, minus termination fees and any minimum commitment shortfall Signed amendment or new contract, its rate exhibit and invoices billing at the new rate
3. Long distance and toll-free numbers on the wrong account Per-number and per-minute charges on the acquired company’s account at its old rates, or numbers no one routes or answers For numbers you keep: the rate gap times usage. For numbers no one needs: the full monthly charge Number list with routing and usage, the move or disconnect order and the next invoice
4. Lines and services transferred that weren’t part of the deal Services billed to the buyer that serve the seller’s retained business, another owner or a site outside the purchase agreement Full monthly charge from the closing date, plus any amount billed in error that can still be disputed The purchase agreement’s site or asset list, the transfer or disconnect order and any credit memo
5. Closed or consolidated sites still billing Circuits, lines and equipment charges at addresses the integration plan closed Full monthly charges from the site’s closing date Closing date from facilities or real estate, disconnect confirmation and an invoice without the charge
6. Utilities at closed locations Electric, gas, water, sewer and waste accounts at sites that closed Full monthly charges from the closing date, using twelve months of bills for seasonal accounts Closing date, the utility’s final bill and no later bills on that account
7. Back-billed errors and re-credits (one-time) Charges paid after a disconnect was requested, or billed above the contracted rate Sum of overbilled amounts still inside the dispute window Dispute record and the credit as it posts on a later invoice

Rows one through six are run-rate savings: once captured, they recur every month. Row seven is a one-time recovery. Keep it out of any annualized figure, because a credit for past overbilling won’t repeat next year, and counting it as run-rate makes the rest of the number harder to defend.

How Do You Size Integration Savings Against the Deal Model?

Size integration savings from twelve months of both companies’ invoices, category by category, then net out the one-time costs of capturing each saving. Compare that bottom-up figure with the telecom line in the deal model. Where the model’s number is higher, the gap is an assumption that still needs a source, and it’s better to find that out before the first quarterly review.

Twelve months matters because some charges bill quarterly or annually, and some services sit idle for months before anyone notices. Pull every invoice for every billing account of both companies, the contracts with their rate exhibits and term dates, and the list of sites the integration will close. If the deal team built a due diligence telecom inventory before close, start there: it’s the first draft of the baseline, and every service on it should match a current invoice line.

Public companies that show merger savings in pro forma financial statements follow a rule worth borrowing. Rule 11-02 of Regulation S-X, as the U.S. Securities and Exchange Commission (SEC) amended it in 2020, lets a public company present “Management’s Adjustments” for synergies only when there’s a reasonable basis for each one. An expense reduction can’t exceed the expense historically incurred in the period, related dis-synergies must be shown alongside, and the notes must disclose each adjustment’s basis, limitations and estimated time frame, plus its method of calculation where material. The rule governs public filings, not your internal tracker, but its tests translate directly to telecom:

  1. A reasonable basis. Every saving ties to a service ID, a billing account and an invoice amount, not to a percentage of total spend.
  2. No more than you paid. A category can’t save more than both companies were billed for it. When two services overlap, only the one you retire goes away, so size the saving at that service’s cost, not both.
  3. Costs shown alongside. Net out early termination fees, months of running old and new circuits in parallel, installation and migration charges, fees under a transition services agreement (TSA) while the seller still provides service, and shortfall charges if moving volume leaves a contract below its minimum commitment.
  4. A time frame. Date each saving to the action that captures it, which separates the Year 1 figure from the run-rate.

Run-rate and in-year savings are different numbers, and it’s easy to blur them. Take the closed-location utility result above: $1,500 a month. If that billing stopped after month four of the first year (an illustrative date, not the client’s), Year 1 would capture eight months, or $12,000, while the run-rate saving stays $18,000 a year. Any model that books the full run-rate in Year 1 overstates it whenever the action lands after day one.

Which Savings Arrive First, and Which Take a Contract Cycle?

Savings that need no contract change, such as services outside the deal and closed-site billing, can arrive first; contract consolidation waits for notice windows. Duplicate circuits fall in between, because the surviving circuit has to be installed and tested before the other one goes. Plan the first year around those gates, not around the order the savings appear in the deal model.

Phase Savings that can land What has to be true first
Before close None yet. This phase produces the inputs: the pre-close inventory, a contract list with term and notice dates, and the sites the plan will close. Access to the target’s invoices and contracts during diligence
Months 1 to 3 Services outside the deal, telecom and utilities at sites already closed, toll-free and long distance numbers to cut or move, and wireless lines for people who have left Authority to act on the acquired accounts with each carrier and utility, and someone reviewing the acquired company’s invoices line by line
Months 3 to 6 Duplicate circuits retired after cutover, and disputes for past overbilling filed with credits starting to post Surviving circuits installed and tested, and dispute windows still open
Months 6 to 12 Contract consolidation, co-terming and new rates, plus services that end with the TSA Notice dates reached, termination fees and minimum commitments checked, and TSA exit dates set
Month 12 No new category. The realized total is reconciled to the deal model. A run-rate report by category, tied to the GL

Treat the months as a planning guide, not a rule. A single-site acquisition compresses the plan, while several acquisitions in one year stretch it. Contract savings depend on dates written into each agreement, and the guide to telecom contract notice windows covers finding them before they pass. Every row also assumes the underlying work is under way (finding services, confirming owners and placing disconnects), which the guide to acquisition telecom cleanup after a merger walks through.

One gate matters more than the calendar: who reviews the acquired company’s invoices once accounts payable consolidates. Invoices that go straight into the payment run keep every leftover alive, however good the plan is.

Utilities and Closed Sites: The Integration Savings Telecom Plans Miss

Utility accounts at closed or consolidated sites keep billing until someone closes them, and telecom integration plans often leave out electric, gas, water and waste. One multi-location RadiusPoint client was paying $1,500 a month, $18,000 a year, for utilities at closed locations. Stopping that kind of cost takes no new contract, only an owner.

Utilities fall through for organizational reasons. Telecom sits with IT, utilities sit with facilities or real estate, and the integration plan can be written before the site plan is final. Closings can also come later than telecom cutovers, as leases end and teams move, so the accounts at those addresses can sit unreviewed for months.

Add a site list to the savings plan: every location the integration will close or consolidate, its closing date, and every telecom and utility account at that address. Some closed sites need minimum service until the lease ends, for alarms, fire protection or a final walkthrough, so confirm with facilities before closing an account rather than after. Then size each account from its last twelve months of bills, the same way as the telecom rows.

RadiusPoint covers this side through Utility Expense Management with ExpenseLogic, which spans electricity, gas, water, sewer and waste. ExpenseLogic’s closed-location billing exception reports flag sites marked closed that still bill, and its real estate system integration supports service setup and disconnect when a location opens or closes. Growth by acquisition multiplies the work: RadiusPoint has supported a client’s growth from 170 to 1,200 locations through acquisitions and openings.

How Should You Prove Realized Integration Savings to Finance?

Prove each realized saving with three matching records: the baseline invoice line, the dated action that removed or repriced it, and a later invoice. If the later invoice still shows the charge, the saving isn’t realized, whatever the tracker says. Finance can then trace every dollar from the deal model to a service, a document and a GL account.

Keep an evidence file for each saving with:

  • The service ID, billing account and site, with the baseline amount and the invoice it came from
  • The action record: the ticket or order, who approved it, the carrier’s or utility’s confirmation and the effective date
  • The first invoice that shows the charge removed or billed at the new rate
  • The one-time costs netted against it, such as termination fees, overlap months or install charges
  • The GL account and cost center where the saving lands

Then report three kinds of money separately, because finance treats them differently:

Type Example How to report it
Run-rate savings A duplicate circuit retired, a number moved to the contracted rate, a closed site’s accounts closed Monthly, by category, against the deal model; annualize only after a later invoice confirms it
One-time recoveries Credits and refunds for past overbilling In the month the credit posts on an invoice, and never annualized
Cost avoidance New orders placed at contract rates instead of the acquired company’s old rates As a separate line with the method stated, since it doesn’t reduce last year’s spend

The $174K in re-credits mentioned above belongs in the second row. Recovering past overbilling is its own workstream, covered in the guide to telecom refund recovery, and a credit counts only once it posts on an invoice. Finally, re-check later invoices for every closed item. A charge that comes back three months after a disconnect undoes a saving finance has already counted.

How RadiusPoint and ExpenseLogic Help Capture and Prove Integration Savings

RadiusPoint supports integration savings through ExpenseLogic, auditing every invoice line against contracted rates and inventory so each saving traces to a service and an invoice. RadiusPoint’s team works the invoices inside the platform. The client keeps the decisions: which services to disconnect, which contracts to consolidate and when to act.

In one engagement under RadiusPoint’s M&A support services, the team investigated Accounts Payable post-acquisition for an OEM automotive client that completed 5 acquisitions in the same year, normalized the situation and helped the client achieve savings of $1.3M in Year 1 of their acquisitions.

Each part of the savings plan maps to an ExpenseLogic capability:

  • Duplicates and services outside the deal: line-item audit of every invoice line against contracted rates and inventory, across wireline, wireless and data circuits.
  • Contract consolidation: vendor contract management ties expiration dates and rates to service IDs, and contract obligation alerts cover termination fees and dates.
  • Disconnects and moves: moves, adds, changes and disconnects (MACD) run through ticketing with client-defined approval workflows.
  • People who left during the integration: Employee ID validation against the HR roster surfaces lines still assigned to former staff.
  • Closed sites: closed-location billing exception reports and real estate system integration, described above.
  • Proof for finance: monthly accrual files and GL interface files for the accounting system.

RadiusPoint can pay vendor invoices for clients once the client funds the account. RadiusPoint was founded in 1992 and is a women-owned business. Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 TEM Vendor SmartList, and ExpenseLogic is rated 4.8 from 31 reviews on Capterra.

Every month an acquired account goes unreviewed, its leftovers bill again and the gap between booked and realized savings grows. To see your combined invoices sorted this way, request a complimentary TEM consultation through the ExpenseLogic telecom expense management page.

Frequently Asked Questions

Is there a typical percentage for telecommunication M&A integration savings?

No percentage applies reliably across deals, and this guide doesn’t offer one. Savings depend on how much the two companies overlap, how many sites close, what each contract allows and how soon someone reviews the acquired invoices. Build the figure from both companies’ invoices instead, and treat any published result, including RadiusPoint’s $1.3M Year 1 example, as one client’s outcome rather than a forecast for your deal.

Should we cancel the acquired company’s telecom contracts right after close?

Usually not on day one. Read each contract first for early termination fees, notice dates, automatic renewal terms and minimum commitments, because one fee or shortfall charge can erase a year of savings in that category. Keep services the business still runs on until replacements are installed and tested. Services outside the deal and services at closed sites are different: they rarely need a replacement, so cancel those quickly.

What happens if we disconnect a toll-free number customers still dial?

Under Federal Communications Commission (FCC) rules, a disconnected toll-free number stays in disconnect status, or disconnect and transitional status, for at least 45 days and no more than four months. No extension is granted, and the number then goes to the spare or unavailable category. Before cutting a number, check where it’s published and whether calls still arrive. If it’s still in use, move it to the right account instead.

Who should own the integration savings number, finance or IT?

Finance should own the number, because finance reports it against the deal model and ties it to the general ledger. Telecom or IT owns the actions: cutovers, disconnects, number moves and contract work. Accounts payable owns the invoice evidence. Keep all three in one tracker by category, and let finance decide when a saving counts as realized, based on the evidence file rather than a status flag.

Can a transition services agreement delay telecom savings?

Yes. Under a TSA, the seller may keep providing network, phone or IT services to the acquired business for a set period, often for a fee. Savings on those services can’t start until the TSA ends for them, and the fee itself is a cost to net against the plan. Put each TSA end date on the same calendar as contract notice dates so replacements are ready in time.

How long should we keep checking invoices after the integration ends?

Keep checking every invoice, well past the first year. Charges can return after a disconnect, rates can drift at renewal and new sites bring new accounts. At a minimum, repeat the full category review at the first renewal of each consolidated contract and after every site closing, and keep each saving’s evidence file with the month-end records finance already retains.

References

  1. U.S. Securities and Exchange Commission, “Amendments to Financial Disclosures about Acquired and Disposed Businesses,” Release No. 33-10786, May 2020. sec.gov
  2. Code of Federal Regulations, Title 17, Section 210.11-02, “Preparation requirements” (Regulation S-X, Rule 11-02), Legal Information Institute, Cornell Law School. law.cornell.edu
  3. Code of Federal Regulations, Title 47, Section 52.103, “Lag times,” Electronic Code of Federal Regulations, current as of October 15, 2026. ecfr.gov
  4. RadiusPoint, “M&A Support Services: A New Way to Think About Their Role.”
  5. RadiusPoint, “Telecom Expense Management Solution.”
  6. RadiusPoint, “Inventory Management Helps Recovering $174K in Credits,” October 12, 2022.
  7. RadiusPoint, “Utilities Mismanagement Costs $18K in Unnecessary Expenses.”
  8. RadiusPoint, “Normalizing Invoice Processing and Payment in Hyper-Growth Phase.”
  9. RadiusPoint, “About RadiusPoint.”
  10. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  11. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews. capterra.com

This article is general information for finance, corporate development and telecom teams working through an acquisition. It isn’t legal, accounting, tax or financial advice, and your purchase agreement, carrier and utility contracts and accounting policies govern how savings are captured and reported. The SEC and FCC rules cited are summarized, not reproduced in full. RadiusPoint results cited come from specific client engagements and aren’t a guarantee of results for any deal.

Government Telecom Expense Management: How Agencies Control Telecom Spend

TEM0

How many phone lines, mobile devices and data circuits is your agency paying for this month? Who approved the last one that was added? The first answer is usually spread across carrier invoices. The second may not be written down anywhere, and it’s the one an auditor will ask for.

Government telecom expense management (TEM) means running the kind of telecom expense management government auditors expect: every line, device and circuit an agency pays for is tied to an inventory of record, an approved order and an audited invoice. In an agency, that record matters more than the rate. Procurement rules decide who may order a service and under which contract, budget cycles decide which year’s money pays for it, and public accountability means any charge can end up in an inspector general’s report. The same few controls answer all three: a current inventory, approved moves, adds, changes and disconnects (MACD), a usage review that closes idle lines and an audit trail that outlasts staff turnover.

When those controls slip, the cost ends up on the public record. In December 2025, California’s State Auditor reported that the state’s Employment Development Department (EDD) paid $4,623,352 in monthly service fees for 6,285 mobile devices that went unused for four or more consecutive months between November 2020 and April 2025. An EDD official told the auditor the department had been receiving its carrier’s nonusage reports since 2017, yet the branch using the devices said its staff didn’t evaluate whether they were being used.

RadiusPoint, founded in 1992, does this work for clients through ExpenseLogic, its expense management platform, and a team that audits every invoice line, runs MACD ticketing with client-defined approval workflows and keeps inventory, cost allocation and reporting current. Government is one of the industries RadiusPoint serves.

Key Takeaways

  • Government TEM ties every telecom line, device and circuit to an inventory of record, an approved order and an audited invoice.
  • Procurement rules, fiscal year budgets and public accountability shift the priority from rates to records: who ordered, under which contract, from which budget and with whose approval.
  • Public audits from 2010 to 2025 keep finding the same gaps: incomplete inventories, no regular usage review and lines that keep billing after the need ends.
  • Set a written threshold for idle lines, review every carrier account’s usage each billing cycle and close lines through an approved disconnect ticket.
  • Keep approval rules and decisions inside the agency, even when a provider does the audit, inventory and ticket work.

Short version: If your agency can’t show the approved order, the current user and the audited invoice behind any telecom line, fix the inventory of record and the approval trail before you negotiate a single rate.

What Is Government Telecom Expense Management?

Government telecom expense management controls an agency’s telecom inventory, orders, invoices and payments so every charge traces back to an approved, documented decision. The mechanics match commercial TEM. The difference is who checks the work: inspectors general, state auditors, legislative staff and the public, sometimes years after payment.

The core tasks, covered in what telecom expense management is and how it works, don’t change in government: inventory, ordering, invoice audit, dispute recovery, cost allocation and payment. What changes is the scrutiny.

Public sector telecom spend is large enough to draw that scrutiny. A 2015 report from the U.S. Government Accountability Office (GAO) cited the most recent estimate from the Office of Management and Budget (OMB): about $1.2 billion a year on about 1.5 million federal mobile devices and associated services. At the state level, Texas Legislative Budget Board staff reported in 2019 that state agencies spent about $474.4 million on telecommunications-related services across fiscal years 2016 and 2017.

Agency Audits Keep Finding the Same Three Gaps

Agency audits keep finding three gaps: no complete inventory of record, no regular review of usage, and no proof that approved disconnects stopped the billing. The reports below cover federal, state and city governments from 2010 to 2025, and none of the findings shown here turned on a carrier’s rate.

Audit (office, year) What it found Control that was missing
New Jersey Office of the State Comptroller, 2010 The state paid for more than 19,000 unused phone lines, nearly one in six state lines. Disconnecting them was expected to save more than $3.2 million a year. A current inventory and a regular disconnect review
U.S. Government Accountability Office, GAO-15-431, 2015 Only 5 of 15 federal agencies reviewed had complete service and device inventories, and only 1 of 15 had documented procedures for reviewing devices for overuse, underuse or zero use. An inventory of record and a documented usage review
Florida Department of Environmental Protection, Office of Inspector General, 2019 Monthly usage certifications weren’t completed or provided for 210 of 726 department cell phones in the month reviewed. A monthly usage sign-off by the user or supervisor
U.S. Securities and Exchange Commission, Office of Inspector General, Report No. 562, 2020 The agency spent almost $732,000 on 1,567 devices with zero usage between October 2018 and December 2019. A periodic review of carrier usage reports
City of Baltimore, Office of the Inspector General, 2020 City agencies paid about $108,451.80 from September 2017 through February 2020 for 204 Voice over Internet Protocol (VoIP) lines they reported they weren’t using. Disconnect tracking through to the invoice
California State Auditor, Report I2025-1, 2025 EDD paid $4,623,352 in monthly fees for 6,285 mobile devices unused for four or more consecutive months, from November 2020 through April 2025. Assigned review of carrier nonusage reports and a written cancellation threshold

Read together, the reports show what an agency telecom audit checks first: whether the agency knows what it’s paying for, whether anyone reviews usage and whether a disconnect actually ends the charge. In New Jersey and Baltimore, lines that were disconnected or believed inactive kept showing up on bills.

Why Do Procurement Rules and Budget Cycles Change TEM?

Procurement rules and budget cycles change TEM because they decide who may order a service, under which contract and from which year’s budget. Public accountability adds a third test: the record behind every charge has to hold up in an audit, a records request or a legislative hearing.

Government constraint What it means for telecom TEM control that addresses it
Procurement rules Services should be ordered under a contract the agency is allowed to use, by staff with authority to order MACD tickets with an approval step on every order, and contract rates tied to each service ID
Contracted rates An invoice is only correct if each line bills at the rate in that contract Line-item audit of every invoice line against contracted rates and the inventory
Budget cycles Money is planned and committed by fiscal year, fund and program Cost allocation by cost center or program, accrual and general ledger (GL) files, and a yearly line review timed before the budget request
Public accountability Auditors, inspectors general and the public can ask for the record behind any charge An inventory of record plus ticket, audit and dispute history kept for the agency’s retention period
Segregation of duties No one person should request, approve, receive and pay for the same service Separate requester, approver and invoice review roles built into the workflow
Staff turnover and reorganization Lines outlast the people, offices and programs they were ordered for User checks against the current staff roster, zero use reviews and closed-site billing reports
Decentralized ordering Field offices order locally while a central office pays One inventory across every billing account, with missing-invoice tracking and costs split to the offices that use them
Carrier authorization Carriers share records and accept changes only from authorized people A letter of agency (LOA) that names who may act for the agency and what it covers

Budget timing differs by level of government. The federal fiscal year begins on October 1 under 31 U.S.C. 1102. According to the National Conference of State Legislatures (NCSL), 46 states began fiscal year 2026 on July 1, 2025, while New York starts its fiscal year on April 1, Texas on September 1, and Alabama and Michigan on October 1. Schedule the yearly line review to finish before your next budget request is built, so the request funds lines you’ll keep rather than lines nobody uses.

Procurement rules matter for a quieter reason. A contract sets the rate, and an invoice is only right if each line bills under that contract. When a field office calls a carrier directly, the new service can land on a separate account at standard rates, outside any contract the agency competed. An approval step on every order, followed by an audit of every invoice line against contracted rates, keeps purchases and prices inside the rules.

An Inventory of Record Comes Before Any Zero Use Cleanup

An inventory of record lists every line, device and circuit an agency pays for, with its location, user, cost center and contract attached. Zero use reviews depend on it, because a carrier’s usage report shows idle numbers but not who holds them or whether a program still needs them.

Most of the federal agencies GAO reviewed in 2015 didn’t have one. Only 5 of 15 had complete service and device inventories, and GAO wrote that “the remaining agencies either did not have inventories or those inventories did not account for all devices and services.” In a 2020 report on five agencies’ plans to move telecom services to new contracts, GAO noted that officials at three of them said they weren’t responsible for tracking all the telecom services in use, so they couldn’t provide complete inventories. Texas Legislative Budget Board staff reached the same conclusion for state agencies in 2019, noting that without a central inventory, agencies “have a limited ability to improve efficiencies, such as verifying proper device usage.”

Build the inventory from the carriers’ records, not from memory. Customer service records (CSRs) show what each carrier believes is on each account, and a telecom inventory of record built from CSRs gives you a list to reconcile against invoices, locations and the current staff roster. Every service that bills but has no owner, location or cost center goes on a review list.

Then set the rule for idle lines in writing. California’s State Auditor recommended that EDD terminate service for mobile devices not used for 90 consecutive days, and EDD put a departmentwide policy along those lines into effect on September 3, 2025. In the Texas survey, three agencies said they eliminate lines with no usage over a set period, with review frequency ranging from one month to six months. Once the threshold is set, the review runs the same way every cycle:

  1. Pull usage reports for every carrier account each billing cycle. California’s findings came from one of EDD’s 22 accounts with its carrier, and the auditor said the total was likely understated.
  2. Flag zero use mobile lines, idle landlines and circuits with no traffic, and match each one to its user, location and cost center in the inventory.
  3. Ask the assigned user’s supervisor or the program owner to confirm whether each flagged line is still needed, with a response deadline.
  4. Close confirmed lines through an approved disconnect ticket, recover the device and check the next invoice to confirm the charge stopped.
  5. Record the outcome either way, including who decided to keep a low-use line and why.

RadiusPoint builds this check into ExpenseLogic by pairing zero use device identification with Employee ID validation against a monthly HR roster, so lines assigned to former staff surface alongside lines nobody uses.

How Do MACD Approvals and Audit Trails Answer Public Accountability?

MACD approvals answer public accountability by recording who requested each move, add, change or disconnect, who approved it, what it costs and when billing changed. Kept together, those tickets become the audit trail an inspector general or state auditor asks to see, long after the staff who handled them have moved on.

Federal internal control standards point the same way. GAO’s Standards for Internal Control in the Federal Government, revised in 2025 and effective beginning with fiscal year 2026, says segregation of duties “helps prevent fraud, waste, and abuse” by “considering the need to separate authority, custody, and accounting.” For telecom, that means the person who requests a line shouldn’t be the one who approves it, and neither should be the person who confirms the invoice is right.

The telecom MACD process works the same way in an agency as anywhere else, but government tickets need two extra fields: the fund, program or cost center that pays, and the contract the order falls under. A workable role split looks like this:

  • Requester: program staff or a manager, who states the business need.
  • Approver: the budget holder for the cost center that will pay.
  • Fulfillment: the telecom or IT office, which places the order under the right contract.
  • Invoice review: finance, accounts payable or an audit provider, which confirms the charge matches the approved order and the contracted rate.

When an outside provider will deal with carriers for the agency, carriers usually want written authorization first. Decide who signs the telecom letter of agency, what it authorizes and when it ends before any work starts, and file a copy with the audit trail.

Use this audit trail checklist for each line, device or circuit. If the record can’t answer a question, that’s the gap to close first.

  • What is it (service ID, phone number or circuit ID), where is it, and which cost center, fund or program pays for it?
  • Which contract does it bill under, and at what rate?
  • Who is it assigned to today, and does that person still appear on the staff roster?
  • Who requested it, who approved it, when and for what business reason?
  • What has changed since, and who approved each change?
  • Did the carrier confirm each order, and did the next invoice reflect it?
  • What did each month’s invoice audit find: matched, disputed or corrected?
  • For every dispute, when was it filed and when did the credit post?
  • When was usage last reviewed, and who confirmed the line is still needed?
  • If it was disconnected, where are the ticket, the carrier confirmation and the first invoice without the charge?
  • Which LOA, if any, authorized an outside party to act on it?

What Should an Agency Ask a TEM Provider?

An agency should ask a TEM provider how invoices are audited, who approves changes, how disputes are tracked and who keeps the records. Those answers decide whether the agency can still explain its telecom spend after the people who set up the program have moved on, and whether an auditor can follow the trail without the provider in the room.

  • Does the audit check every invoice line against contracted rates and the inventory, or only a sample?
  • Can approval rules follow the agency’s own structure (by cost center, program or role), and does each ticket record the requester, approver and dates?
  • How are disputes tracked until the credit posts, and how are credits reported back to the program that paid?
  • How does the provider confirm that a disconnect stopped the billing?
  • Can costs be allocated by fund, program or cost center, and can accrual and GL files match the agency’s chart of accounts?
  • How are idle lines and lines assigned to former staff identified each cycle?
  • Who in the agency signs the LOA, and what exactly will it authorize?
  • If invoices will be paid through the provider, how is the account funded and how are payments reconciled?
  • Will the agency own its inventory, ticket history and audit results, and can it export them in a usable format at any time, including when the contract ends?

Whatever the answers, keep the decisions in house. A provider can maintain the inventory, audit invoices, file disputes and process tickets, while the agency sets the approval rules, decides what to order or disconnect, owns contract decisions and signs.

How RadiusPoint Supports Public Sector Telecom Control With ExpenseLogic

RadiusPoint supports public sector telecom control with ExpenseLogic, keeping inventory, MACD approvals, invoice audit, cost allocation and reporting in one record its team works monthly. The agency sets the approval rules and makes the decisions, and RadiusPoint’s team does the audit and administrative work against those rules.

Each gap from the audit reports maps to an ExpenseLogic telecom expense management capability:

  • Inventory and idle lines: ExpenseLogic tracks devices by serial number and Employee ID, validates Employee IDs against a monthly HR roster and identifies zero use devices. Closed-location billing exception reports flag services still billing at sites that have closed.
  • Approvals and contracts: MACD ticketing runs on client-defined approval workflows. Vendor contract management ties expiration dates and rates to service IDs, and contract obligation alerts cover termination fees and dates.
  • Invoice audit: RadiusPoint’s line-item audit checks every invoice line against contracted rates and the inventory across wireline, wireless and data circuits. Daily missing-bill reporting shows when an expected invoice hasn’t arrived.
  • Budgets and accounting: Costs are allocated to cost centers, including split billing a circuit across several, and ExpenseLogic produces monthly accrual files and GL interface files for the accounting system.
  • Records: Reporting includes budget reports, scheduled email delivery and export to Excel, CSV and PDF. Contract management stores contract images and terms, and document management recalls stored images by permission.

RadiusPoint can pay vendor invoices for clients once the client funds the account.

One non-government example shows the inventory work in practice. For a healthcare provider, RadiusPoint identified and deactivated dormant business lines, which led to a 26% reduction in the client’s annual telecom spend. It’s a single client’s result, not a forecast for an agency.

RadiusPoint was founded in 1992 and is a women-owned business. Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 TEM Vendor SmartList, and ExpenseLogic is rated 4.8 from 31 reviews on Capterra.

Every billing cycle an idle line stays on an account, the agency pays for it again, and the record of why gets harder to rebuild. To see how the inventory, approval workflows and audit trail work together, request an ExpenseLogic demonstration.

Frequently Asked Questions

Do state and local agencies need different TEM controls than federal agencies?

No, the controls are the same: an inventory of record, approved MACD tickets, a usage review, an invoice audit and an audit trail. What differs is the rulebook. Federal agencies apply GAO’s internal control standards, while state and local agencies follow their own statutes, procurement codes, internal control rules and records schedules. Match approval levels, fiscal year timing and record retention to the rules your agency answers to.

How long should a line go unused before an agency cancels it?

Pick a threshold, write it into policy and apply it every billing cycle. California’s State Auditor recommended 90 consecutive days for EDD, and agencies in the 2019 Texas survey reported review periods from one month to six months. Before canceling, confirm the need with the assigned user or program owner, and check the contract for early termination fees or minimum commitments that change the math.

Does handing TEM to a provider mean giving up control of telecom decisions?

It shouldn’t. A provider can audit invoices, maintain the inventory, track disputes and process MACD tickets, while the agency keeps the approval rules, every decision to order or disconnect, contract decisions and the final signature. Put that split in writing, limit the LOA to the work the provider is doing and make sure the agency can export its own data at any time.

Who should own telecom spend inside an agency, IT or finance?

Usually both, with one named owner for the inventory of record. The telecom or IT office places orders and manages services, finance allocates and pays, and program managers approve what their budgets fund. In the 2019 Texas survey, seven of 12 responding agencies said they delegated phone usage monitoring mostly to individual departments, which is how lines slip between offices without anyone seeing the whole account.

How can an agency estimate what a TEM program might save?

Build the estimate from your own records, not a published percentage. Count lines with no usage past your threshold and multiply by their monthly charges, then add billed rates that exceed contracted rates and services still billing at closed sites. That gives a range you can defend in a budget request. Treat any case study figure, including RadiusPoint’s, as an example rather than a forecast.

What should happen to carrier credits and refunds once they’re recovered?

Record each one against the service ID, cost center and fund that paid the original charge, then apply it the way your agency’s accounting rules require. Log the dispute amount, filing date and posting date, and confirm the credit on a later invoice before closing the dispute. Without that trail, credits on a consolidated account are hard to trace back to the program that overpaid.

References

  1. California State Auditor, “Investigations of Improper Activities by State Agencies and Employees,” Report I2025-1, December 12, 2025. auditor.ca.gov
  2. U.S. Government Accountability Office, “Telecommunications: Agencies Need Better Controls to Achieve Significant Savings on Mobile Devices and Services,” GAO-15-431, May 21, 2015. gao.gov
  3. U.S. Government Accountability Office, “Telecommunications: Agencies Should Fully Implement Established Transition Planning Practices to Help Reduce Risk of Costly Delays,” GAO-20-155, April 7, 2020. gao.gov
  4. U.S. Government Accountability Office, “Standards for Internal Control in the Federal Government,” GAO-25-107721, May 15, 2025. gao.gov
  5. U.S. Securities and Exchange Commission, Office of Inspector General, “Opportunities Exist To Improve the SEC’s Management of Mobile Devices and Services,” Report No. 562, September 30, 2020. oversight.gov
  6. City of Baltimore, Office of the Inspector General, “Investigative Report Synopsis,” OIG Case No. 20-0019-I, May 13, 2020. baltimorecity.gov
  7. Florida Department of Environmental Protection, Office of Inspector General, “Review of Wireless Services Usage Certifications for Department Issued Cell Phones,” Report A-1819DEP-013, March 25, 2019. floridadep.gov
  8. New Jersey Office of the State Comptroller, “Comptroller audit finds state government wastes millions annually due to unused phone lines,” press release, July 7, 2010. nj.gov
  9. Texas Legislative Budget Board staff, “Improve Telecommunications Management Practices to Reduce State Agency Costs,” April 2019. lbb.texas.gov
  10. United States Code, Title 31, Section 1102, “Fiscal year,” Legal Information Institute, Cornell Law School. law.cornell.edu
  11. National Conference of State Legislatures, “FY 2026 State Budget Status,” 2025. ncsl.org
  12. RadiusPoint, “Healthcare Case Study: Telecom Expenses Down by 26% in Healthcare,” December 28, 2023.
  13. RadiusPoint, “About RadiusPoint.”
  14. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  15. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews. capterra.com

This article is general information for finance, IT, procurement and telecom staff in public agencies. It isn’t legal, procurement, audit or financial advice, and your agency’s statutes, procurement rules, internal control standards and records schedules govern how these controls apply. Audit findings cited here describe the agencies and periods named in each report. The RadiusPoint result cited comes from a single non-government client engagement and isn’t a guarantee of results for any agency.

Telecom Contract Rate Benchmarking: When to Bring In Outside Help Before Renewal

TEM0

Your carrier contract sets one rate. Your invoices can show another. When a renewal proposal arrives, its discount is measured against what you pay today, so if lines have drifted above their contracted rates, part of that discount is just the carrier billing what it already agreed to.

Telecom contract rate benchmarking checks your telecom expense management contract rates three ways before a renewal: against what the carrier bills, against what you use and against what other carriers will quote. Do it in that order. Billed versus contracted comes first because it corrects the baseline, plan and feature fit comes second because it shrinks what you’re buying, and market quotes come last. Start about 12 months before the term ends, bring in outside help when the work won’t fit before the notice date, and keep negotiation strategy approval and the final signature with your team.

RadiusPoint, a telecom expense management (TEM) provider, does this work in ExpenseLogic, where contract expiration dates and rates are tied to service IDs and every invoice line is audited against the contracted rate. When a client asks, RadiusPoint’s team also negotiates with the carrier on the client’s behalf. For a global glass manufacturer, RadiusPoint gathered all its service contracts, validated the expiration dates and negotiated at the corporate level, so the carrier folded those contracts together. In year one the client saved more than $100,000 in telecom expenses, including refunds, with a 200% return on investment (ROI).

Key Takeaways

  • Benchmark in order: billed versus contracted rates, then plan and feature fit against usage, then competing quotes. A quote measured against an overbilled baseline overstates the savings.
  • Build the comparison from 12 months of invoices for every billing account, each contract with its amendments and rate exhibits, and an inventory tied to service IDs.
  • Start about 12 months before the term ends, so corrections, disconnects and any request for proposal (RFP) finish before the notice date.
  • Bring in outside help when carriers, contracts and locations outgrow the hours you have before that date, and keep strategy approval and the final signature in house.
  • Published RadiusPoint results: $120,000 a year from moving 400 phone numbers to corporate contract rates, and more than $100,000 saved in year one, with a 200% ROI, for a glass manufacturer whose contracts were consolidated.

Short version: Before you compare any carrier quote, correct what you’re billed to what your contract says, start about 12 months before the term ends and use outside help only for work your team can’t finish before the notice date, while your team keeps strategy approval and the signature.

What Is Telecom Contract Rate Benchmarking?

Telecom contract rate benchmarking compares each contracted rate with three things: what the carrier bills, what your organization uses and what competing carriers will quote. Each comparison answers a different question. The first finds money the carrier owes you, the second finds services you no longer need and the third tests whether the price itself is competitive.

Much of the advice on telecom expense benchmarking starts with the market rate, and that’s the weakest place to start. A competing quote is only as useful as the baseline it’s measured against, and the baseline is your invoices. If some lines bill above their contracted rates, a quote that simply matches the contract looks like savings it isn’t. If you pay for lines nobody uses, every quote prices services you’re about to cancel.

Rate benchmarking is one task inside telecom contract management, the wider job of tracking each carrier agreement’s terms, dates, obligations and rates. RadiusPoint’s guide to vendor contract management covers matching invoices to contracts month by month. The sections below cover the renewal: what to compare, where the numbers come from, when to start and who should do the work.

The Benchmarking Worksheet to Fill Before Any Carrier Call

A benchmarking worksheet lists each billed item, the record behind its contracted and billed amounts and what a gap between them looks like. Build one row per item for each carrier and billing account number (BAN). The rows below apply to wireline, wireless and data contracts alike.

Item to benchmark Where the data comes from What a gap looks like
Monthly recurring rate per line or circuit Invoice line items, matched by service ID to the contract’s rate exhibit or pricing attachment A billed rate above the contracted rate, or a line billing at standard rates because it was never added to the contract account
Plan, bundle or bandwidth tier The inventory, usage reports and the plan named on each invoice line Lines on plans larger than their usage, or circuits with more bandwidth than the site uses
Features and add-ons Feature charges on the invoice, compared with the inventory and the features the contract includes Features nobody ordered or uses, or included features billed as extras
Usage rates (long distance, minutes, data overage) Usage detail on the invoice, compared with the contracted per-unit rates Per-unit charges above contract, or overage every month that points to the wrong plan
Discounts and credits Contract amendments and promotional terms, compared with the credit lines on the invoice A contracted discount or recurring credit missing from the invoice, or one that stopped before its end date
Commitments and term Contract terms (minimum spend or volume, term length), compared with 12 months of billed spend Billed spend well below the commitment, which is a shortfall risk, or well above it, which is volume to bargain with
Services billed versus services in use The inventory tied to locations and service IDs, compared with every billed service Billed services with no inventory record, or services at closed sites, that would renew along with the contract
Dates and exit costs The contract: term end, notice date, auto-renewal clause and early termination fees Any date or fee nobody can find, which can remove your option to leave

Leave taxes, regulatory surcharges and government fees out of the worksheet. They follow law and jurisdiction rather than your negotiated rate, so they belong in a separate telecom tax and surcharge audit, not in a rate comparison.

Fill the worksheet from your own records before you ask anyone for a price. Gaps in the rate, feature, usage and credit rows become disputes or corrections. Gaps in the plan, commitment, inventory and date rows become decisions to make before the contract renews.

Start With Billed vs Contracted Rates, Not Market Quotes

Start with billed versus contracted rates, because every line billed above its contract rate inflates the baseline that a carrier’s renewal discount is measured against. A corrected baseline shows what the contract really costs, and the disputes it produces can return money for past months that are still inside the dispute window.

A nationwide automotive salvage company shows how far billing can drift from a contract. It made five acquisitions within a year, its accounts payable was consolidated in one business unit, and invoices were paid without review. After RadiusPoint’s line-item inventory and audit, 400 phone numbers moved to the corporate long-distance account’s contract rates, saving $120,000 a year. The published case also lists benchmarking of costs and detailed cost identification among the work.

The match itself is mechanical, which is exactly why it gets skipped. For each billing account:

  1. Pull the contract, every amendment and the rate exhibit or pricing attachment that lists each service and its rate.
  2. Match each recurring invoice line to a contract item by service ID, circuit ID or phone number.
  3. Flag three kinds of line: billed above the contracted rate, billed at standard rates because the service was never added to the contract account, and billed with no contract item at all.
  4. Dispute past overcharges inside the window your contract and the carrier’s terms allow, and correct the rate going forward.
  5. Rebuild the monthly total at contracted rates. That corrected figure is the baseline every renewal offer gets measured against.

Organizations running TEM across multiple carrier accounts should repeat the match for every BAN, because one carrier can hold several contracts with different rate exhibits. RadiusPoint runs this match on every invoice in ExpenseLogic. Done by hand, it’s still worth doing once before any renewal.

Normalize Every Rate Before You Compare It

A fair benchmark compares the same unit, term, commitment and service level, drawn from 12 months of invoices and a current inventory. Without that, a carrier’s quote and your contract describe different products, and the cheaper-looking number may simply buy less. Normalize first, then compare.

Twelve months matters because annual charges, seasonal usage and mid-year credits don’t show up in a single bill. Then put every rate on the same footing:

  • Same unit. Per line per month for wireless, per circuit per month at a stated bandwidth for data, and per minute or per call for usage.
  • Same term and commitment. A 36-month rate with a minimum spend isn’t comparable with a 12-month rate that has none. Record both on every quote.
  • Recurring kept apart from one-time. Spread installation charges, waived fees and signing credits over the term instead of mixing them into the monthly rate.
  • Same service level. Repair times, uptime commitments and support tiers change what a rate buys.
  • Same inventory. Ask every carrier to price the inventory you’ll keep after disconnects, not the one on today’s invoice.

Treat any market rate quoted without a source with caution. Business telecom pricing depends on volume, term, locations and service mix, so the market benchmark that fits your contract is a quote priced against your own normalized inventory, gathered through an RFP or direct quotes from competing carriers. Those quotes do two jobs: they test the price, and they give the incumbent a reason to improve it.

How Many Months Before Renewal Should You Start?

Start benchmarking about 12 months before the term ends, so audit corrections, disconnects and any competitive quotes are finished before the contract’s notice date arrives. Work backward from the notice date, not the term end, because a missed notice date can renew a contract that has an auto-renewal clause.

Months before the term ends What to finish
12 Confirm the term end, notice date, auto-renewal terms and early termination fees. Collect invoices, contracts, amendments and the inventory.
9 Fill the worksheet. File disputes for billed versus contracted gaps and disconnect services nobody uses.
6 Check plan and feature fit, write requirements (locations, services, service levels), decide whether to bring in outside help and request competing quotes or issue an RFP.
3 Negotiate with the incumbent and any finalists. Approve the strategy first, then review terms, commitments and rate exhibits.
Before the notice date Decide whether to renew, renegotiate or switch, and send any written notice the contract requires.
After signature Load the new rates and dates against service IDs and check the first invoices against them.

Treat the months as a planning guide, not a rule. Compress the plan for a single service at one site, and stretch it when acquisitions, many locations or several carriers are involved. If the notice date falls earlier than the plan assumes, move every step up. The guide to telecom contract notice windows covers finding and calendaring that date.

When Is Outside Help Worth It Before a Renewal?

Outside help is worth it when the audit, data work and carrier conversations won’t fit into your team’s available hours before the notice date. It’s a capacity question as much as an expertise one: the steps are learnable, but the hours have to fit before the deadline.

Keep it in house when Bring in help when
You have one carrier and one contract You have several carriers, several BANs or several contracts with the same carrier
The inventory is current and tied to service IDs The inventory is out of date or lives in spreadsheets
Someone has matched invoices to rate exhibits in the past year Nobody has compared billed rates with contracted rates
Contracts were signed centrally Locations signed their own contracts, or contracts came with acquisitions
The notice date leaves time for the full plan above The notice date is closer than the plan allows
Staff have time to run quotes or an RFP Nobody is free to run quotes, compare responses and talk to carriers

Both published cases sit in the right-hand column. The salvage company inherited services through acquisitions and paid invoices without review, and the glass manufacturer’s locations ordered services on their own with no corporate contracts.

Ask any outside party the same questions before you bring them in:

  • Will the benchmark start from your invoices and contracts, or only from a market rate sheet?
  • How will billing errors found during benchmarking be disputed and tracked until the credit posts?
  • Who talks to the carriers, and will you see every proposal and redline?
  • Who approves the negotiation strategy, and who signs? Both answers should be your team.
  • Will you get the worksheet, inventory and contract data back in a format you can use?

Carriers usually require your written authorization, often a letter of agency (LOA), before they’ll share account records with a third party, so name who signs it early.

What Should Stay With Your Team in a Telecom Contract Negotiation?

Your team should keep strategy approval, business requirements, commitment decisions and the final signature, even when an outside party prepares data or talks to carriers. Delegating the work isn’t the same as delegating the decision. Agree the split in writing before the first carrier call.

Can be delegated Stays with your team
Collecting invoices, contracts and carrier records Business requirements: locations, services and service levels
Filling the worksheet and auditing billed versus contracted rates Approval of the negotiation strategy, targets and walk-away position
Filing and tracking disputes Decisions on term length and minimum commitments
Requesting quotes, comparing responses and modeling options The choice to renew, renegotiate or switch carriers
Talking to carriers and drafting proposed terms, when you ask The final signature
Loading new rates and dates and auditing invoices after signature Ownership of the contract data and the right to take it with you

The published glass manufacturer telecom case study shows what that delegated work can look like. The client, a global glass manufacturer with large U.S. retail operations and more than 200 retail locations, had locations that called vendors to order whatever services they needed. It had no corporate contracts, so locations bought from the same vendor under different contracts. RadiusPoint gathered all the service contracts, validated their expiration dates and then negotiated at the corporate level, so the carrier folded those contracts into one corporate contract. In year one the client saved more than $100,000 in telecom expenses, including refunds, and reached a 200% ROI.

The consolidation only holds if new orders follow it. In the case, ordering moved to RadiusPoint’s MACD (moves, adds, changes and disconnects) portal, so future orders are placed under the appropriate contract at the appropriate rates. That’s the telecom expense contract negotiation step that’s easiest to skip: making sure the rates you won are the rates you’re billed.

How RadiusPoint and ExpenseLogic Support Renewal Decisions

RadiusPoint supports renewal decisions in ExpenseLogic by tying contract rates and expiration dates to service IDs and auditing every invoice line against those contracted rates. That record turns a renewal from a carrier’s proposal into a comparison your team can check line by line.

In ExpenseLogic, vendor contract management keeps each contract’s expiration date and rates tied to service IDs, and contract obligation alerts cover termination fees and dates, so renewal dates and exit costs are on record before planning starts. The Contract Management module stores contract images and retains terms, so the rate exhibit is on file when the worksheet needs it.

RadiusPoint’s line-item audit checks every invoice line against contracted rates and the inventory across wireline, wireless and data circuits, which keeps the billed versus contracted rows current every month rather than once per renewal. For wireless lines, bill audit and rate plan optimization address plan fit. Moves, adds, changes and disconnects run through MACD ticketing with client-defined approval workflows, so new orders after a renewal follow the new contract.

When a client asks, RadiusPoint’s team can negotiate with carriers on the client’s behalf, as it did for the glass manufacturer. The client approves the negotiation strategy and signs the final contract.

RadiusPoint was founded in 1992 and is a women-owned business. Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 TEM Vendor SmartList.

Every month a line bills above its contracted rate, the carrier’s next renewal offer is measured against the wrong number. Book a complimentary TEM consultation through the ExpenseLogic telecom expense management page, and bring your term end date, notice date and current rate exhibits.

Frequently Asked Questions

What if our carrier contract doesn’t include a rate exhibit?

Ask the carrier’s account team for the pricing schedule, rate attachment or order forms the agreement refers to, and collect every amendment signed since. Rates may sit in those documents rather than in the master agreement. Until you have them, treat each billed rate as unverified, mark those rows in the worksheet and make getting the pricing documents an early step in the renewal plan.

Should taxes and regulatory fees be part of a rate comparison?

No. Compare service charges before taxes, surcharges and government fees, because those follow law and jurisdiction rather than your negotiated rate. Check them in a separate tax and surcharge review instead. The exception is a fee the carrier sets itself rather than one the law requires. Carrier-imposed charges like that can go on the negotiation list alongside the rates.

How often should we benchmark between renewals?

Check billed against contracted rates every invoice cycle, because an error repeats every month until someone catches it. Review plan and feature fit at least once a year and whenever headcount, locations or services change. Save the market comparison for the run-up to a renewal, or for a major change such as an acquisition, when the carrier has a reason to reprice.

Can we renegotiate a telecom contract before it expires?

Sometimes. A carrier may agree to amend a contract mid-term when you add services, consolidate several contracts or extend the term. Check early termination fees and minimum commitments first, because they set the cost of any change. Get every amended rate in writing, then check the next invoices against it before you count the savings.

What’s a realistic savings target for a carrier renewal?

Build the target from your own worksheet rather than a published percentage. Add up the billed versus contracted gaps, the cost of services you’ll disconnect and the difference between your corrected baseline and the best qualified quote. RadiusPoint’s published results, such as $120,000 a year from moving 400 numbers to contract rates, are individual client results, not a forecast for your contract.

References

  1. RadiusPoint, “Glass Manufacturer Saves $100K On Telecom Expenses,” May 22, 2023.
  2. RadiusPoint, “Telecom Expense Management Solution,” automotive salvage case study (Acquisition and TEM), accessed November 2026.
  3. RadiusPoint, “About RadiusPoint,” accessed October 2026.
  4. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com

This article is general information for finance, IT, procurement and telecom teams preparing for a carrier contract renewal. It isn’t legal, procurement or financial advice, and the terms of your own contracts govern notice dates, fees and dispute rights. RadiusPoint results cited here come from specific client engagements described on the pages listed in References and aren’t a guarantee of results for your organization.

How to Build a Business Case for Telecom Expense Management

TEM0

Only 5 of 15 federal agencies had complete inventories of their mobile devices and services when the US Government Accountability Office (GAO) reviewed them for a May 2015 report. Only 1 had documented procedures for reviewing devices and service plans for overuse, underuse or zero use. Any organization in that position has the same problem: without an inventory and a usage check, nobody can say which services to cancel, so nobody can say what an audit would save.

Telecom audit savings are the money a line-item audit of telecom invoices brings back or stops: one-time refunds and credits for errors you’ve already paid, and recurring reductions from disconnecting unused services and correcting rates. A business case for telecom expense management (TEM) turns those savings into a decision finance can approve. Build it in order: a verified baseline of current spend, savings inputs you can trace to invoices and contracts, the full cost of the program, and a payback period shown with and without refunds.

RadiusPoint delivers TEM in ExpenseLogic, its platform for telecom, wireless and utility expenses, with line-item audit, refund and credit recovery, inventory reconciliation and reporting. The outline, savings inputs and payback formula below work with any provider’s proposal, and the RadiusPoint client results quoted here are individual results, not a forecast for your organization.

Key Takeaways

  • Start with a 12-month baseline: every carrier invoice, the service inventory, current contracts and the hours your team spends on telecom today.
  • Keep one-time refunds and credits (R) apart from recurring savings (S). Count a refund when the credit posts, and never in the monthly savings line.
  • Payback in months = (C minus R) / (S minus F), where C is the one-time program cost and F the monthly program cost. Show it with R and with R set to zero.
  • Individual RadiusPoint client results: a global glass manufacturer saved more than $100,000 in year one with a 200% ROI, a Fortune 100 manufacturer recovered more than $450,000 in telecom refunds in year one, and a healthcare provider cut its telecom expenses 26%.
  • Name the risks before finance does: refunds that don’t post, savings that don’t recur, internal time and services that get added back.

Short version: Ask finance to approve a TEM program only when the business case starts from your own 12-month invoice baseline, keeps one-time refunds apart from recurring savings, counts every program cost including your team’s time and shows payback in months with and without refunds.

What Goes Into a Telecom Expense Management Business Case?

A telecom expense management business case needs a spend baseline, savings inputs, the program’s cost, a payback calculation, named risks and a clear decision request. Finance approves arithmetic it can re-check, so every section should name where its number comes from. The table maps each section to its source, and its letters match the payback formula further down.

Section What goes in it Where the number comes from
Decision requested The program, its scope (carriers, service types, locations), the contract term and the budget line you’re asking finance to approve The provider proposal and your own scope list
Current spend baseline Monthly telecom spend by carrier, service type and cost center; invoice and billing account counts; the inventory of lines, circuits and devices 12 months of carrier invoices, the service inventory and the accounts payable (AP) ledger
Current cost of managing telecom Hours AP, IT and telecom staff spend on invoices, disputes and orders each month; late fees paid Time estimates from each team; late fee lines on the invoices
One-time recoveries (R) Refunds and credits for past billing errors that are still inside the dispute window A sample of invoices checked against contract rates and the inventory; dispute terms in your contracts and the carriers’ terms
Recurring savings (S) Monthly reductions from disconnecting unused services, correcting rates to contract and signed renegotiations The inventory compared with invoices and usage; contract rate exhibits; signed amendments
Program cost (C and F) One-time setup cost (C) and monthly cost (F), each including your team’s time Provider quotes and your own staffing estimate
Payback and multi-year view Months to recover the one-time cost, with and without R; net benefit over the contract term Payback months = (C minus R) / (S minus F), worked through below
Risks and assumptions Every input labeled verified or estimated, with what happens if it’s wrong Your notes against each row above
How results will be measured The baseline figures realized savings will be reported against after approval, and who signs off on them The baseline section of this case

Two rules keep the table honest. Every dollar sits in exactly one row, so a refund can’t also show up as a monthly saving. And every number carries a label, verified or estimated, so the approver knows which ones to test first.

Build the Baseline Before You Estimate a Dollar of Savings

Build the baseline from 12 months of carrier invoices, your service inventory, current contracts and the hours your staff spend on telecom today. Every savings estimate is a share or a count of something in that baseline, so an error there carries into every number built on top of it.

A full year of invoices matters because annual charges and seasonal changes don’t show up in a single month. Pull every carrier and every billing account number (BAN), then split the spend four ways: recurring service charges, usage, one-time charges, and taxes, surcharges and fees. The split shows finance which part of the bill each savings estimate comes from.

The inventory is the harder half. List every line, circuit, device and service with its location and cost center, then compare the list with the invoices in both directions: services you’re billed for that aren’t in the inventory, and inventory items nobody can match to a bill. GAO found those gaps in a federal government that, by the Office of Management and Budget’s (OMB) 2012 estimate, spent about $1.2 billion a year on mobile devices and services across about 1.5 million devices. Without an inventory and usage procedures, GAO concluded, agencies “have a limited ability to monitor device usage and determine if a device should be canceled or moved to a more cost-effective service plan.”

Add three more records finance will ask about. First, contracts: rates, terms, expiration dates, minimum commitments and early termination fees. Second, open disputes and pending credits, so the case doesn’t count money that’s already being claimed. Third, the current cost of managing telecom: monthly hours from AP, IT and telecom staff on invoices, disputes and orders, plus any late fees on the invoices.

Struggling to assemble the baseline is evidence too. It’s one of the clearest signs of when you need TEM, so note how long it took and what you couldn’t find, and put both in the problem statement.

Which Savings Inputs Will Finance Accept?

Finance accepts savings inputs it can trace to an invoice line, an inventory record or a signed contract, and treats everything else as an estimate. Split the inputs by type, because one-time recoveries and recurring savings do different jobs in the payback math. The table shows how to estimate each one before you buy.

Savings input How to estimate it before you buy Evidence finance will ask for Where it goes in the formula
Refunds and credits for past billing errors Check a sample of invoices against contract rates and the inventory, and count only errors still inside the dispute window The invoice line, the contract rate and, later, the credit on a billed invoice One-time (R)
Unused services disconnected Count lines, circuits and features with zero use or no owner, and multiply by their monthly charge The inventory record, a usage report and the disconnect order Recurring (S)
Rates corrected to contract Take the gap between the billed rate and the contracted rate, per month The contract rate exhibit next to the invoice line Recurring (S), plus a one-time credit for past months (R)
Renegotiated rates and consolidated contracts Leave out of the base case until signed, or show as a separate upside case The signed amendment or new contract Recurring (S), once signed
Late fees avoided Add up the late fee lines across the baseline year The late fee lines on the invoices Recurring (S)
Staff time freed Price the hours at your loaded labor cost Time estimates, plus a staffing or contractor change if spend actually drops Separate line, outside payback
Cost avoided Estimate the charges an approval step would have blocked Approved and declined orders Separate line, outside payback

The telecom savings metrics finance trusts are the ones it can re-check: dollars tied to a specific service and invoice, with the evidence attached. That’s why the last two rows sit outside payback. They’re real, but nobody can re-perform them from an invoice.

Refunds need one more rule. A filed dispute isn’t money, and an agreed credit isn’t either until it appears on a billed invoice. Telecom refund recovery tracks each claim to that point, and your case should count R the same way.

RadiusPoint’s published results show each input type at work. They’re individual client results from real implementations, not a forecast for your organization. A Fortune 100 manufacturer whose wireless invoices RadiusPoint audited in ExpenseLogic recovered more than $450,000 in telecom refunds in its first year of service, which is R-type money. A healthcare provider cut its annual telecom spend 26% after dormant business lines were disconnected and removed from its invoices, which is S-type money. A global glass manufacturer saved more than $100,000 in its first year, including refunds and credits, and reached a 200% ROI on its TEM services.

Published year-one figures don’t always separate one-time from recurring money, and ROI can be defined more than one way. Use them to show finance what an audit can find, build R and S from your own invoices, and ask any provider how its ROI figures are calculated before you quote one.

What Will the Program Cost, and When Does It Pay Back?

The program costs its one-time setup, its monthly fees and your team’s time, and it pays back once savings have covered all three. Write the payback formula with placeholders first and agree it with finance. Then the approval debate is about inputs, which you can evidence, rather than about arithmetic.

One-time cost (C) covers implementation and data loading, building or validating the inventory, connecting output files to your AP or accounting system, letters of agency for carrier records, and your own project time. Add early termination fees only if the plan changes carriers before a contract ends. Monthly cost (F) is the provider’s fee plus the internal time that stays with you for approvals, exception review and program ownership.

Provider quotes arrive in different shapes, so convert each one to a one-time figure and a monthly figure before you compare them. RadiusPoint’s guide to how TEM pricing works explains the common models. Then run the same math for every option on the table: the status quo, an in-house program with added staff or software, and outsourced telecom expense management.

Define the placeholders:

  • C: one-time program cost, internal implementation time included
  • F: monthly program cost, provider fees plus internal time
  • S: monthly recurring savings from disconnects, rate corrections and signed renegotiations
  • R: one-time refunds and credits you expect to post within the payback period

Payback (months) = (C minus R) / (S minus F)

The formula only works when S is larger than F. If monthly savings don’t beat the monthly cost, the program never pays back on recurring savings, and the case has to rest on recoveries and on the separate lines for staff time and cost avoidance. Show the result twice: once with R, and once with R set to zero. The second result is the conservative case, because refunds depend on dispute windows and carrier responses you don’t control. If R is larger than C, the formula returns a negative number, which means the credits alone cover the one-time cost once they post.

Finance will usually ask for three refinements. If recurring savings start only after a ramp of M months, add M to the result and add the program cost paid during the ramp (F × M) to C. Run the formula backwards as a break-even test: if T is the longest payback your finance team accepts, the monthly savings the program must reach are F + (C minus R) / T. And for the multi-year view, net benefit over a contract of N months is N × (S minus F) + R minus C, less S × M if there’s a ramp. If your estimate of S clears the break-even bar only with renegotiations that aren’t signed yet, say so in the memo.

Risks Finance Will Raise, and the Answers to Put in Writing

Finance will ask whether the savings recur, whether refunds will actually post, what your team’s time costs and what stops waste from returning. Answer each question in the business case itself. A risk you name in the memo reads as diligence, while the same risk raised by the approver reads as a gap.

  • Savings that don’t recur. Refunds stop once past errors are cleared. Keep R out of the monthly line and lead with the payback that excludes it.
  • Refunds that never post. Your contracts and each carrier’s terms set the window for disputing a charge, and errors older than that window can’t be claimed. Count R only for errors inside it, and treat it as cash only when the credit appears on a billed invoice.
  • Waste that comes back. Disconnected lines can be reordered and rates can drift at renewal. Name the controls that stop it: an approval step for every move, add, change or disconnect (MACD), and a check of every new invoice against the contract and the inventory.
  • Internal time left out. Even a fully managed program needs an owner on your side for approvals and decisions. Put those hours in F.
  • Estimates that came from a sales deck. Mark any provider-supplied savings figure as an estimate, and replace it with math from your own baseline before the memo goes out.
  • Access to carrier records. A provider needs your written authorization, usually a letter of agency (LOA), before carriers will share account records or work disputes with it. Name who signs it.
  • Exit terms. Ask what comes back if you leave: invoice images, line items, the inventory and dispute history, in a format you can use.

What Belongs in the One-Page Approval Memo?

The approval memo puts the decision first, then the baseline, savings split by type, full cost, payback with and without refunds, risks and measurement. Keep the memo itself to one page and move the evidence to appendices, so an approver can follow the logic quickly and still find the source behind any number.

  1. Decision requested: the program, its scope, the contract term, the budget line and the approver.
  2. Problem: one paragraph, anchored on one baseline figure, such as monthly telecom spend that nobody audits line by line today.
  3. Baseline: monthly spend by carrier and service type, invoice and account counts, the inventory count and current staff hours.
  4. Savings estimate: one-time recoveries (R) and recurring savings (S) on separate lines, each labeled verified or estimated.
  5. Program cost: one-time (C) and monthly (F), internal time included.
  6. Payback: months with R and with R set to zero, plus the break-even monthly savings.
  7. Options considered: the status quo, an in-house program and an outsourced one, with the same math for each.
  8. Risks and controls: each named risk next to the control that addresses it.
  9. Measurement: the baseline the program will be reported against, the report finance will receive and who signs off on realized savings.
  10. Appendices: the invoice sample, inventory extract, contract exhibits and provider quotes behind every number.

The same outline works as a telecom cost reduction report template after go-live: keep the baseline from item 3, replace each estimate in item 4 with the realized figure and report it the way item 9 defined. That’s the core of proving TEM savings to finance against a baseline both sides already signed.

How RadiusPoint Supports the Business Case With ExpenseLogic Data

Each input in a TEM business case maps to work RadiusPoint does in ExpenseLogic: line-item audit, refund and credit recovery, inventory reconciliation and reporting. ExpenseLogic is the platform, and RadiusPoint’s team works the invoices, carrier disputes and inventory inside it. Each capability lines up with a row of the savings inputs table above.

The line-item audit checks every invoice line against contracted rates and the inventory, across wireline, wireless and data services. That’s the evidence behind rate corrections (S) and behind the past billing errors that become refunds (R). Refund and credit recovery files and pursues carrier disputes until the credits post, which is the point at which R becomes money.

Inventory reconciliation compares what you’re billed for with what you have, which is how unused lines and services are found and disconnected (S). Reporting in ExpenseLogic covers audit analysis and budget reporting, with exports to Excel, CSV and PDF, and costs are allocated to your cost centers. If the business case also covers the payment run, RadiusPoint can pay vendor invoices for clients once the client funds the account.

RadiusPoint’s published individual client results include more than $450,000 in first-year telecom refunds for a Fortune 100 manufacturer, a 26% cut in telecom expenses for a healthcare provider, and more than $100,000 saved in year one with a 200% ROI for a global glass manufacturer. RadiusPoint was founded in 1992, is a women-owned business and has been ISO 9001 certified since 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 TEM Vendor SmartList, and ExpenseLogic holds a 4.8 rating on Capterra from 31 reviews.

Every month the case waits, the same unaudited charges bill again at the same rate. Book a complimentary TEM consultation through the ExpenseLogic telecom expense management page, and bring your baseline and the memo outline above.

Frequently Asked Questions

What telecom audit savings should we expect?

Expect a number only after you’ve built your own baseline. Telecom audit savings depend on how many unused services you pay for, how far billed rates have drifted from contract and how many past errors are still inside the dispute window. RadiusPoint’s published results, such as a 26% cut in telecom expenses for one healthcare provider, are individual client results. They show what an audit can find, not what yours will.

Should staff time count as savings in a TEM business case?

Count it on its own line, outside payback, unless spending actually changes. Hours freed in AP, IT or telecom are real capacity, but finance books them as savings only when a contractor, an overtime budget or an open position goes away. Price the hours at your loaded labor cost and let the approver decide how much weight they carry.

What if we can’t get a full year of telecom invoices?

Use the months you have and label the gap. Request missing invoices through each carrier’s online portal or your account team, or authorize a provider to request account records with a letter of agency. If the baseline covers less than a year, flag that annual and seasonal charges may be missing, so finance reads every figure built on it as an estimate.

Who should sign off on a TEM business case?

Get three sign-offs: the IT or telecom owner who presents the case, the controller or CFO who approves the numbers, and an AP lead who confirms invoice counts and current process costs. Add procurement if the plan changes carrier contracts. When AP and finance sign the baseline before anyone discusses savings, the approval meeting argues about inputs, not about whose spreadsheet is right.

Does the same approach work for IT expense management cost savings?

Yes. The structure carries over to IT expense management cost savings: a baseline, savings split into one-time and recurring, full program cost and payback. The inputs change. Software and cloud baselines count licenses, subscriptions and usage instead of lines and circuits, and the evidence is a license record or a cloud bill rather than a carrier invoice. Keep each category in its own baseline so savings in one can’t hide costs in another.

References

  1. US Government Accountability Office, “Telecommunications: Agencies Need Better Controls to Achieve Significant Savings on Mobile Devices and Services,” GAO-15-431, May 21, 2015. gao.gov
  2. RadiusPoint, “$1.3M in Telecom Refunds and Cost Savings: Case Study,” June 10, 2023.
  3. RadiusPoint, “Healthcare Case Study: Telecom Expenses Down by 26% in Healthcare,” December 28, 2023.
  4. RadiusPoint, “Glass Manufacturer Saves $100K On Telecom Expenses,” May 22, 2023.
  5. RadiusPoint, “Telecom Expense Management Solution,” accessed October 2026.
  6. RadiusPoint, “How Companies Recover Telecom Refunds and Credits From Carriers,” accessed October 2026.
  7. RadiusPoint, “About RadiusPoint,” accessed October 2026.
  8. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  9. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews, accessed October 2026. capterra.com

This article is general information for finance, IT and telecom teams preparing a business case for telecom expense management. It isn’t financial, accounting or legal advice, and your own finance policies on payback, discounting and capital approval apply. The GAO findings describe 15 federal agencies in a 2015 report. RadiusPoint results cited here come from specific client engagements described on the pages listed in References and aren’t a guarantee of results for your organization.

Utility Bill Audit Services: What a Provider Checks and How Fees Work

UEM0

In April 2009, Connecticut’s Office of Policy and Management asked for proposals on a job most finance teams will recognize. Roughly 3,000 electric accounts and 550 natural gas accounts across 29 executive branch agencies needed someone to review three to five years of energy bills, find the errors and recover the overpayments. The compensation clause ran one sentence: the contractor would be paid “an agreed upon contingency fee based on moneys recovered.”

Hire a utility bill audit service today and you’ll likely be offered that deal or its opposite, a recurring fee to audit every bill from here on. The choice decides what the audit can find and what it costs.

Utility invoice auditing services are outsourced reviews of electricity, gas, water, sewer and waste bills in which a provider checks each meter’s charges against its tariff or contract rate, its usage history and the sites you actually operate, then works with the utility to correct what it finds. Hire a one-off recovery audit to reach back into bills you’ve already paid, and an ongoing audit to stop the same errors from billing again. Before you sign either, get three terms in writing: how deep the audit goes, how far back it reaches, and what the fee is charged on and for how long.

RadiusPoint audits utility bills as part of its Utility Expense Management (UEM) service in ExpenseLogic, its platform for telecom, wireless and utility expenses, with meter-level audit, tariff analysis and closed-location billing exception reports. One multi-location RadiusPoint client was paying $1,500 a month, $18,000 a year, for utilities at locations it had already closed.

Key Takeaways

  • A utility bill audit service should test each meter, not account totals: meter setup, tariff and rate class, demand charges, consumption against history, and closed sites.
  • A one-off recovery audit reaches back into paid bills. Connecticut’s 2009 recovery audit request asked for at least three and no more than five years of history.
  • An ongoing audit checks each new bill, so it catches sites that close and meters that spike after a one-off audit ends.
  • Contingency fees come out of recoveries, and some contracts add a share of future savings for a set term. Get the savings definition, the baseline and the end date in writing.
  • One RadiusPoint client was paying $18,000 a year for utilities at closed locations, the kind of charge a closed-site check is built to find.

Short version: Hire a one-off recovery audit when past bills have never been checked, keep an ongoing meter-level audit running so the same errors don’t bill again, and sign neither until the contract defines the lookback window, the savings baseline and the date the fees end.

What Does a Utility Bill Audit Service Actually Check?

A utility bill audit service checks each meter’s charges against its tariff or contract rate, its usage history and your list of open sites. Those checks catch different errors, and they pay off at different times. The table shows what each audit type compares, what it typically catches, and whether a one-off or an ongoing audit is the better way to run it.

Audit type What the provider compares What it typically catches One-off or ongoing?
Meter-level check Meter numbers, multipliers and read types on the bill against the meter list for each site A wrong multiplier, estimated reads that were never trued up, a meter billed to the wrong account or billed twice Both. A recovery audit claims the back months; an ongoing audit stops the next bill.
Tariff and rate class check Each charge against the utility’s published rate schedule and riders, and the supply charge against your contract price in a deregulated market Charges that don’t match the schedule, a supply rate that drifted from the contract, a meter on a rate class the site no longer fits Both for billing errors. A rate class change is a forward fix.
Demand charge review Billed kW, demand multipliers and ratchets against metered peak demand Demand billed above the metered peak, or a ratchet still charging for a peak the site set months ago Mostly ongoing, because demand is billed again every cycle.
Consumption anomaly check Each meter’s usage against its own history, its season and thresholds you set A spike, a zero read on a site that’s open, or usage that doesn’t fit the building Ongoing. An anomaly costs least the month it first appears.
Closed site check Meters still billing against site close dates and vacancy records Bills for locations you’ve closed, or for units left vacant with the account in your name Ongoing. Sites keep closing after a one-off audit ends.

A provider can list all five checks and still run only some of them on every bill, so ask which run against your meter list each cycle and which happen once during setup. A comparison of this month’s total with last month’s is a variance check: it shows that a bill changed, not whether it was right.

To run the checks in-house instead, the guide on how to audit a utility bill walks through them meter by meter. The rest of this page is about hiring someone to do it.

One-Off Recovery Audit or Ongoing Audit?

A one-off recovery audit reviews past bills to claim refunds, while an ongoing audit checks every new bill as it arrives, cycle after cycle. The first brings money back. The second stops the same errors from billing again. If your utility bills have never been audited, you may need both, in that order, and the table compares them side by side.

Factor One-off recovery audit Ongoing audit
What it looks at Bills you’ve already paid, over a set lookback window Each new bill, every billing cycle
Time window Set in the contract. Connecticut’s 2009 request asked for at least three and no more than five years. Open-ended, for as long as the contract runs
Main output Claims for refunds and credits, plus a findings report Exceptions held or disputed, plus a corrected record of meters and rate classes
Common fee basis A contingency fee from money recovered, sometimes with a share of future savings A recurring fee, such as a flat monthly amount or a rate per invoice or per meter
When it ends When the lookback window has been worked and the claims close When the contract ends
What it misses Errors that start after it closes, such as a site that shuts next quarter Money lost before the service started
Best fit Bills that have never been audited, or a portfolio you’ve just acquired Portfolios where sites open, close and change rate class

Energy cost recovery services are usually the one-off kind. The provider reviews past electric and gas bills, files claims with the utility and gets paid from what comes back. Connecticut’s 2009 request fits that pattern: it covered only electric and natural gas invoices, and its scope was limited to identifying and recovering billing and payment errors.

How far back a claim can reach isn’t the auditor’s call. The utility’s tariff and state rules set the limits, and they differ from one state and utility to the next, which is why utility expense recovery is its own job once the error has been found.

The two approaches fail in opposite ways. A recovery audit is finished when its lookback window is, so an error that starts the following month lands on bills nobody checks. An ongoing audit catches that error, but it can’t reach money lost before it began. The same split holds for invoice auditing services in other spend categories: recovery work looks backward, and continuous audit looks forward.

Meter, Tariff and Rate Class Checks Find What a Total Hides

Meter, tariff and rate class checks test whether each meter is billed on the right schedule, at the right price, with the right multiplier. An account total can look normal while one meter on it carries an error. Ask every provider for a sample exception, and check that it names the meter, not only the account.

A tariff check compares each charge with the utility’s published rate schedule for that meter’s rate class, riders included. Where you buy supply in a deregulated market, a contract check compares the supply charge with the price you signed. Both answer one question: was this bill calculated correctly?

Rate class asks a different one: is this meter on the right schedule at all? A bill can be calculated perfectly on a rate class the site no longer fits, and no tariff check will flag it. Moving the meter takes a filed request with the utility, which is why utility rate reclassification usually lowers future bills rather than producing a refund. Connecticut’s answers to bidders allowed for the exception: where the utility applied a rate change retroactively, the auditor would be paid on the savings actually recouped.

Meter checks sit underneath both. A wrong multiplier inflates every kWh and kW on the bill, and because it doesn’t change, the bill looks normal month after month. Ask whether the provider checks multipliers, read types (actual or estimated) and which site each meter belongs to.

Demand charges need their own review. Billed kW should match metered peak demand, and a ratchet can keep charging for a peak the site set months earlier. Ask whether the provider recalculates demand, multiplier included, or only reads the demand line off the bill.

Why Do Consumption Anomalies and Closed Sites Need Checking Every Month?

Consumption anomalies and closed-site charges need checking every month because they start without warning and repeat on every bill until someone stops them. A one-off audit sees the ones already sitting on past bills. It can’t see the site that closes next quarter or the meter that spikes next summer.

Consumption checks compare each meter’s usage with its own history and season, and with thresholds you set. They flag a spike, a zero read on a site that’s open, or usage that doesn’t fit the building. Not every anomaly is a billing error. Some are a leak or equipment left running, so the finding should reach facilities as well as accounts payable (AP).

Closed sites make the clearest case for an ongoing check. A location closes, the lease ends, and the utility account can keep billing long after the keys are handed back. One multi-location RadiusPoint client was paying $1,500 a month, $18,000 a year, for utilities at locations it had already closed. ExpenseLogic produces closed-location billing exception reports for that pattern: a site marked closed, a meter still billing.

Property managers see the same problem at the unit level, when a tenant moves out without transferring the account and the bills land back on the owner. RadiusPoint has published a 12% decrease in utility expenses from vacancy cost recovery.

A one-off audit finds the closed sites already on past bills. It can’t find the ones you close after it ends, so ask every provider how it learns that a site has closed: from a feed of your site records, or from someone remembering to send an email.

How Do Utility Audit Fees Work?

Utility audit fees come in three basic forms: a contingency share of what’s recovered, a share of future savings, or a fixed recurring fee. Some contracts combine them. What you actually pay depends less on the label than on three definitions: what counts as savings, the baseline it’s measured from, and when the fee stops.

Fee model What the fee is charged on Public example or typical use Get this in writing
Contingency on recoveries A share of refunds and credits the utility pays back Connecticut’s 2009 request paid “an agreed upon contingency fee based on moneys recovered.” Which recoveries count, and whether credits on future bills count the same as refund checks
Share of future savings A share of lower bills after a change the auditor identified, for a set term Some contracts add a share of future savings for a set term. The baseline, the term, and whether the fee applies to changes you make yourself
Fixed recurring fee A flat monthly amount, or a rate per invoice, account or meter Ongoing audit services, where the same work repeats every billing cycle What’s in scope, what counts as extra, and how the fee changes as sites open and close

Connecticut drew a line worth copying. Its answers to bidders said the winning auditor “would not be eligible for any share of future savings” from a rate change it pursued.

RadiusPoint has published its own case against contingency pricing. Its article on the contingency fee pricing model argues that billing errors are “inconsistent and unpredictable,” so a fee tied to them is hard to budget for, and that clients expect a price proportional to the value they receive, which a percentage of one large error may not be. Whichever model you choose, ask the provider to estimate its fees across the full contract term, including the years after the first large recoveries.

Questions to Ask Before You Hire a Utility Audit Provider

Before you hire a utility audit provider, ask how deep the audit goes, how far back it reaches and what the fee is charged on. Get every answer in the contract, not just the proposal. The list below covers scope, authority, savings definitions and what happens when an audit turns up an undercharge.

  1. Do you audit every meter on every bill, or a sample of accounts?
  2. Which commodities are in scope: electricity, gas, water, sewer, waste?
  3. Which checks run every cycle, and which run once during setup?
  4. How far back will a recovery audit go, and how do you decide what’s claimable?
  5. Who files claims and talks to the utility, and what written authorization do you need from us?
  6. What counts as savings, what baseline is it measured from, and when does the fee on it end?
  7. If we make a change ourselves, do you still charge on the savings?
  8. What happens if you find an undercharge that the utility could bill us for?
  9. What do we receive: findings by meter, with invoice copies and the status of every claim?
  10. Who keeps the meter list, rate data and findings if we end the contract?

Questions 6 and 7 decide the final cost more than any percentage on the proposal. A provider that answers them in a sentence or two, and puts that sentence in the contract, is easier to budget for than one that answers with an estimate of how much it expects to find.

How RadiusPoint Audits Utility Bills in ExpenseLogic

RadiusPoint audits utility bills in ExpenseLogic at the meter level, checking tariffs, rate classes, demand charges, consumption and closed-location billing on an ongoing basis. RadiusPoint’s Utility Expense Management covers electricity, gas, water, sewer and waste, and each check maps to a row in the audit types table near the top of this page.

In ExpenseLogic, the meter-level audit covers contract and tariff rate audit, consumption-based audit and threshold-based audit. RadiusPoint adds tariff analysis and rate reclassification, demand charge review with demand multiplier calculations for kilowatt analysis, closed-location billing exception reports, and consumption reporting in kWh and therms by site.

RadiusPoint’s published utility results include a 12% decrease in utility expenses from vacancy cost recovery, and the multi-location client that was paying $18,000 a year for utilities at closed locations. If you also want the payment run handled, RadiusPoint can pay vendor invoices for clients once the client funds the account.

RadiusPoint was founded in 1992, is a women-owned business and has been ISO 9001 certified since 2002. ExpenseLogic holds a 4.8 rating on Capterra from 31 reviews.

Every billing cycle without a meter-level check is another cycle for a wrong multiplier or a closed site to bill again. Request a free ExpenseLogic demonstration through the Utility Expense Management with ExpenseLogic page, and bring the hiring questions above.

Frequently Asked Questions

What kinds of companies perform utility invoice auditing services?

Four kinds of firms commonly offer them: utility expense management providers, which audit as part of processing every bill; cost recovery firms, which review past bills for a share of what they recover; energy consultants and brokers, which may add audits to supply procurement; and outsourcing firms that process utility invoices for AP. Ask each one whether auditing is its core service or an add-on to something else.

Is utility audit management software enough on its own?

It’s enough if someone on your team has time to work the exceptions. Utility audit management software can flag a wrong rate class, a demand spike or a closed site that’s still billing, but a person still has to confirm the error, contact the utility and track the credit. Check the product, too: some tools sold under that name are internal audit platforms for utility companies, not bill audit tools.

What does UEM audit mean?

A UEM audit is the bill-checking step inside Utility Expense Management: each utility invoice is compared with the meter list, the tariff or contract rate and the meter’s usage history. It’s ongoing by design. A standalone utility bill audit can be a one-off project, while a UEM audit repeats every billing cycle as part of the wider program of receiving, allocating and reporting on utility bills.

Can an audit find money if our bills look the same every month?

Yes, because a steady bill can be steadily wrong. A meter on the wrong rate class, a wrong multiplier or a closed site billing a fixed charge produces the same error every month, so it never shows up as a variance. Only a check against the tariff, the meter record and your list of open sites will find it, which is why month-over-month comparisons aren’t enough.

Is a utility bill audit the same as an energy audit?

No. An energy audit looks at the building: equipment, controls and operating hours, to find ways to use less energy. A utility bill audit looks at the bill: whether you were charged the right rate, on the right meter, for a site you still operate. The two work well together, because audited bill data shows an energy auditor which sites and meters to visit first.

References

  1. State of Connecticut, Office of Policy and Management, “Cost Recovery Audit of Energy Utility Bills,” Request for Proposals, April 15, 2009, and Amendment #1 (questions and answers), May 5, 2009. portal.ct.gov
  2. RadiusPoint, “Contingency Fee Pricing Model: Beware,” November 8, 2022.
  3. RadiusPoint, “Utility Expense Recovery: How Multi-Site Teams Reclaim Overcharges and Credits,” accessed October 2026.
  4. RadiusPoint, “How to Audit a Utility Bill for Errors,” accessed October 2026.
  5. RadiusPoint, “Utility Rate Reclassification and How It Lowers Bills,” August 28, 2026.
  6. RadiusPoint, “Invoice Auditing Services: What They Cover and How to Choose a Provider,” August 24, 2026.
  7. RadiusPoint, “Utility Expense Management,” accessed October 2026.
  8. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews, accessed October 2026. capterra.com

This article is general information for finance, facilities and property teams deciding whether to hire a utility bill audit service. It isn’t legal, accounting or procurement advice, and audit and fee terms should be reviewed by your own counsel. The Connecticut documents are public examples from 2009 that show how fee terms can be written, not current market rates. RadiusPoint results cited here come from specific client engagements described on the pages listed in References and aren’t a guarantee of results for your organization.

Telecom Invoice Management Services: What’s Included and What to Ask

TEM0

A paid telecom invoice proves one thing: the money left. It doesn’t prove the circuit on page four still exists, that the rate matches the contract, or that the credit a carrier agreed to last quarter ever reached a bill. The gap between a paid invoice and a correct one is the work you’re hiring a provider to close.

Telecom invoice management services are an outsourced, recurring service in which a provider receives every carrier invoice, audits each line against your contracted rates and service inventory, works disputes until credits post, and sends accounts payable (AP) allocated, accrual and general ledger (GL) files for month end. To scope one, list the outputs AP needs each month and the decisions your team keeps, then hold every provider to both in writing.

RadiusPoint delivers telecom invoice management as part of its telecom expense management (TEM) service, run in ExpenseLogic, its platform for telecom, wireless and utility expenses. On RadiusPoint’s published record, inventory management work recovered $174,000 in re-credits. That money came from checking the bills against the inventory, not from paying them on time.

Key Takeaways

  • The core scope runs from invoice receipt and missing invoice tracking through line-item audit, disputes, cost allocation, and accrual and GL files. Bill payment is optional.
  • A line-item audit checks every charge against the contracted rate and the service inventory. RadiusPoint’s published inventory management work recovered $174,000 in re-credits.
  • A dispute is closed when the credit posts on a later invoice, not when the carrier agrees to it.
  • AP keeps payment approval, GL mapping and accrual sign-off. RadiusPoint can pay vendor invoices for clients once the client funds the account; approval stays with the client.
  • Name every output in the contract, with its format, and ask for a sample of each on the first call.

Short version: Sign a telecom invoice management service only when the contract names every monthly output AP will receive, from the missing invoice report to the GL interface file, and leaves payment approval with your team.

What Do Telecom Invoice Management Services Include?

Telecom invoice management services include invoice receipt, missing invoice tracking, line-item audit, disputes through to posted credits, cost allocation, and accrual and GL files. Order tickets and bill payment can sit in the same contract. The table shows what each component produces for AP and for the telecom team, and who should own the decision behind it.

Service component What AP gets What the telecom team gets Who owns the decision
Invoice receipt and capture Every carrier invoice logged once, with its image, before anyone codes or pays it Every billing account number (BAN) in one list The provider runs intake. You decide which carriers and accounts are in scope.
Missing invoice tracking A report of expected invoices that haven’t arrived, before they turn into late fees or a short accrual A flag on accounts that stopped billing, which can mean a disconnect, an address change or a lost bill The provider chases the carrier. AP decides whether to accrue the missing amount.
Line-item audit Each invoice marked clean or held as an exception before payment Every charge compared with the contracted rate and the inventory of circuits and lines The provider flags. Telecom decides whether a flagged service should exist.
Disputes and credit tracking A log of amounts disputed, credited and still open, by carrier Carrier tickets worked until the credit posts The provider files and follows up. You set the limit above which a dispute needs your sign-off.
MACD ticketing (moves, adds, changes and disconnects) An approval on record behind every new recurring charge Orders and disconnects tracked to completion, with the inventory updated Telecom approves, under a workflow you define.
Cost allocation Charges coded to cost centers and GL accounts Cost by location, department or service Finance sets the allocation rules. The provider applies them every cycle.
Accrual file An estimate for service used this period but not yet billed The service IDs behind each accrued amount The controller approves the accrual method.
GL interface file Audited, coded charges in a file the accounting system can load Nothing extra; it draws on the same inventory AP owns the GL mapping and the posting.
Bill payment (optional) Carriers paid on approved invoices Accounts kept current with each carrier Your team approves every payment. A provider that pays should pay only from funds you provide.

The last column matters most when you scope. A provider can run every row, but it can’t decide whether a circuit should exist or how your controller books an accrual. Those calls stay with your team, and the contract should say so.

The middle columns show why the work is shared. AP measures the service by its files at close, while the telecom team measures it by whether the inventory and the bills agree. If you’re comparing TEM services and software, ask which rows the software runs by itself and which need a person every month.

Receipt, Capture and Missing Invoice Tracking Start the Cycle

A telecom invoice management service should log every invoice the carriers send and flag every expected invoice that didn’t arrive this cycle. Receipt alone counts what showed up. The missing invoice report counts what should have, and it has to be built from your account list rather than from last month’s arrivals.

Carrier invoices reach AP as paper, PDFs, portal downloads and electronic files, often on different dates for the same carrier. Intake means getting each one into a single record with its image, billing account number and service period, so nobody keys the same bill twice or misses one that went to a former employee’s inbox.

Missing invoice tracking is the control AP can’t run from the invoice pile, because you can’t see a bill that never came. A bill that doesn’t arrive can still cause a late fee, a disconnect notice on an account nobody knew was overdue, or a short month-end number. A missing bill on a live service still belongs in the period, which is why a telecom accrual file treats it as an accrual row.

When you scope intake, ask how the provider builds its list of expected invoices. It should come from the service inventory and the billing account list, so an account that goes quiet shows up as an exception instead of quietly dropping out of view.

How Does a Line-Item Audit Check Contracts and Inventory?

A line-item audit compares every charge on every invoice with two records: the rate in your contract and the inventory of services you have. The contract check catches the wrong price. The inventory check catches the wrong service, meaning lines, circuits and numbers you’re paying for but don’t have or no longer need.

Ask every provider whether its telecom invoice audit covers all invoices or a sample. Billing errors sit on individual lines, so a sample can pass an invoice that repeats the same wrong charge every month. RadiusPoint’s analysts validate every invoice line, wireline, wireless and data, against contracted rates and a maintained inventory of circuits and lines. The audit should also reach taxes, surcharges and fees, which follow their own rules rather than your contract.

Two published RadiusPoint results came from the inventory side. In one engagement, RadiusPoint identified 25 toll-free numbers that didn’t belong to the client, and eliminating them saved $18,000 a year. In a healthcare case, an assisted living and nursing home organization cut its annual telecom spend 26% after more than 700 dormant business lines were disconnected and removed from its invoices.

Keep the two kinds of audit work apart when you scope. A one-time engagement from telecom audit services clears the backlog of past errors. An invoice management service audits each new invoice before it’s paid, so a fixed error doesn’t come back on next month’s bill.

Disputes Aren’t Finished Until the Credit Posts

A dispute is finished only when the credit appears on a later invoice and posts to the cost center that carried the original charge. A filed ticket isn’t a recovery, and an agreed credit isn’t a posted one. Your service should track every dispute through all three stages and report each stage to AP.

Ask to see the dispute log a provider will send you. For each dispute it should show the carrier and billing account, the amount, the date filed, the carrier’s ticket number, the current status and the invoice where the credit landed. A log that stops at “submitted” leaves AP guessing whether the money ever came back.

Timing matters because dispute windows are finite and set by your contract or the carrier’s terms. Disputes start from a confirmed flag, such as a rate that drifted from the contract or a service billed after its disconnect date, so ask how the provider triages telecom invoice red flags before it files. Then agree who can file without asking. One workable split: the provider files routine billing errors on its own, and anything that could change service or contract terms waits for your telecom manager.

RadiusPoint files and pursues carrier disputes until credits post, and ExpenseLogic tracks each pending credit until it’s received. That follow-through is what turns a finding, such as the $174,000 in re-credits from inventory management work, into money on a statement rather than a promise in an email.

What Does AP Get for Month-End Close?

For month-end close, AP should get charges allocated to cost centers, an accrual for unbilled service and a GL interface file it can load. Those three outputs turn audited invoices into journal-ready data. Without them, someone in AP keys coding from PDFs and books last month’s total as the accrual.

Allocation decides where each charge lands. Finance owns the rules, by location, department, service or employee, and the provider applies them every cycle. Shared circuits need a split rule too, and expense cost allocation at the service level is what keeps that split consistent every cycle.

The GL interface file for month end close carries the coded, audited charges into your accounting system in one batch. Scope three things about it: the format your system imports, the mapping to your chart of accounts, and how exceptions are handled, so a disputed charge goes to an accrual or a hold instead of stalling the whole file.

Ask, too, when in your close calendar each file arrives and who on your team signs it off. A file that lands after the books close only moves the manual work to next month.

What Stays With Your AP Team?

Your AP team keeps the decisions that carry financial authority: payment approval, GL mapping, accrual sign-off and limits on what the provider disputes alone. The provider does the volume work. Your team keeps the approvals, so outsourcing the invoices doesn’t mean handing over control of the spend.

  • Payment approval. Every payment run still passes through your approval, whoever releases the funds.
  • Vendor setup. New carriers and billing accounts enter your vendor master through AP, not through the provider.
  • GL mapping and allocation rules. Finance decides where costs land, and the provider applies the rules.
  • Accrual method and sign-off. The controller approves how unbilled service is estimated.
  • Dispute and disconnect limits. Your telecom manager approves anything that could change service or contract terms.

Bill payment is the part to scope most carefully. RadiusPoint can pay vendor invoices for clients once the client funds the account; approval stays with the client. If you’d rather keep the payment run, AP can pay carriers from the audited invoice detail and the GL interface file, and the service still covers every step before payment.

Questions to Settle on the First Call With a Provider

On the first call, settle scope, audit depth, dispute ownership, file formats and payment funding, and ask the provider to put each answer in writing. Vague answers at this stage turn into contract disputes later. Ask for a sample of each output rather than a description of it.

Bring someone from AP and someone from telecom, and work through this list:

  1. Which carriers, billing accounts and service types are in scope: wireline, wireless, data circuits or all three?
  2. Do you audit every invoice line or a sample, and what do you check each charge against?
  3. Where does the inventory come from, and who keeps it current after each move, add, change or disconnect?
  4. How do you build the list of expected invoices, and what happens when one doesn’t arrive?
  5. Which disputes can you file without our approval, and where’s the limit?
  6. Can we see a sample dispute log that follows credits through to the invoice they posted on?
  7. What format do the allocation, accrual and GL interface files come in, and can they match our chart of accounts?
  8. When in our close calendar does each file arrive?
  9. Who pays the carriers, from whose funds, and who approves each payment?
  10. If we leave, what do we get back (invoice images, line items, inventory and dispute history), and in what format?

Questions 2, 6 and 9 separate an invoice management service from a payment processor. If a provider can’t show a dispute closing on a posted credit, or can’t say whose money pays the carrier, keep looking.

How RadiusPoint Delivers Telecom Invoice Management in ExpenseLogic

RadiusPoint delivers telecom invoice management in ExpenseLogic, with RadiusPoint analysts working the invoices from receipt through audit, disputes, allocation, and accrual and GL files. ExpenseLogic is the platform, and RadiusPoint’s team chases the carriers, files the disputes and closes the tickets inside it. Each part maps to a row in the scope table.

In practice, that covers automated invoice receipt and processing; line-item audit across wireline, wireless and data circuits against contracted rates and inventory; MACD ticketing with approval workflows you define; daily missing-bill reporting; cost allocation; and monthly accrual and GL interface files for your accounting system.

The published results come from that work: $174,000 in re-credits from inventory management, $18,000 a year from 25 toll-free numbers that didn’t belong to the client, and a 26% cut in annual telecom spend for a healthcare organization. Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 TEM Vendor SmartList. RadiusPoint was founded in 1992, is a women-owned business and has been ISO 9001 certified since 2002.

Every invoice paid without a line-item audit leaves the same charges set to bill again next cycle. Book a complimentary TEM consultation through the ExpenseLogic telecom expense management page and bring the first-call questions above.

Frequently Asked Questions

Which TEM provider offers automatic invoice auditing and credits recovery?

Look for a provider that pairs automated invoice receipt with a line-item audit of every invoice and tracks each dispute until the credit posts. RadiusPoint does this in ExpenseLogic: analysts validate every line against contracted rates and inventory, then file and pursue carrier disputes until credits post. With any provider, ask which checks the software runs on its own and which a person reviews.

Is telecom invoice management software enough, or do we need a service?

Software is enough if someone on your team has the hours to work its exceptions every month. Telecom invoice management software can flag a wrong rate or a missing bill, but a person still has to dispute the charge, chase the carrier and confirm the credit. If those queues grow every month, the gap is labor, not software, and a managed service fits better.

How is telecom invoice management different from AP automation?

AP automation moves an invoice through coding, approval and payment. It checks that the invoice is coded and approved, not that the circuit still exists or the rate matches the contract. Telecom invoice management comes first: it audits the telecom charges, works the disputes and sends AP coded files. The two work together, and neither replaces the other.

Do we have to sign a letter of agency?

Usually, if you want the provider to deal with carriers for you. A letter of agency (LOA) is your written authorization for a third party to request account records and work disputes on your behalf. Each carrier sets its own requirements, so ask the provider which accounts need one and exactly what the LOA lets it do.

What should we send a provider before the scoping call?

Send a list of carriers and billing account numbers, current contracts and rate amendments, any service inventory you keep, your cost center list and chart of accounts, and a note on how carriers get paid today. With that in hand, a provider can answer the first-call questions against your accounts instead of a demo account.

References

  1. RadiusPoint, “Telecom Expense Management Solution,” accessed October 2026.
  2. RadiusPoint, “Red Flags on a Telecom Carrier Invoice: Checklist for AP and Telecom Managers,” accessed October 2026.
  3. RadiusPoint, “Healthcare Case Study: Telecom Expenses Down by 26% in Healthcare,” December 28, 2023.
  4. RadiusPoint, “What a Telecom Accrual File Is, and How Finance Teams Build One,” accessed October 2026.
  5. RadiusPoint, “How Controllers Use a TEM GL Interface File in Month-End Close,” accessed October 2026.
  6. RadiusPoint, “Allocating Telecom and Utility Costs Across Departments,” accessed October 2026.
  7. RadiusPoint, “ExpenseLogic,” platform modules page, accessed October 2026.
  8. RadiusPoint, “About RadiusPoint,” accessed October 2026.
  9. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com

This article is general information for AP, finance and telecom teams scoping an outsourced telecom invoice service. It isn’t legal, accounting or procurement advice, and contract terms should be reviewed by your own counsel. RadiusPoint results cited here come from specific client engagements described on the pages listed in References and aren’t a guarantee of results for your organization.

Questions to Ask a Utility Expense Management Provider Before You Sign

UEM0

Ask a utility expense management provider what happened to the electric, gas and water accounts at the last location you closed. That one answer tells you more than an hour of demo. Some providers can name the meter, the final bill and the date service stopped. Others can tell you only that an invoice arrived and got paid.

A utility expense management solution is the software and managed service that receives, audits, allocates and reports on an organization’s electricity, gas, water, sewer and waste invoices across every site. Before you sign, test each provider on six points: meter-level audit depth, tariff and rate checks, site openings and closings, vacant unit costs, data ownership and reporting. A strong provider answers each one with a named control, an owner and an example, not a promise.

RadiusPoint delivers Utility Expense Management (UEM) on its ExpenseLogic platform, with meter-level audit, tariff analysis and closed-location billing exception reports. One multi-location RadiusPoint client was paying $1,500 a month, $18,000 a year, for utilities at locations it had already closed, and RadiusPoint has published a 12% decrease in utility expenses from vacancy cost recovery.

Key Takeaways

  • Ask where the audit happens. A meter-level audit checks each meter against its tariff or contract rate and its usage history, while an account-level review can miss one meter billed on the wrong rate class.
  • Ask who sets up and stops service when a site opens, closes or goes vacant. One RadiusPoint client was paying $18,000 a year for utilities at closed locations.
  • Write data ownership into the contract: invoice images, line-item history and the meter list, exported in a format another system can load.
  • Ask for consumption reports in kWh and therms by site and meter, so you can tell a price change from a usage change.
  • Walk away from sample-based audits, savings fees with no written definition and exit terms nobody will put on paper.

Short version: Choose the utility expense management provider that can show you a meter-level tariff check, a closed or vacant site caught on an exception report, and a written data export you keep if you leave, because those three answers cover the places utility money leaks after you sign.

What Should You Ask a Utility Expense Management Provider First?

Start with questions in six areas that expose how the work gets done: audit depth, tariff checks, site changes, vacant units, data ownership and reporting. Pricing and contract length matter too, but these six areas decide whether a provider finds errors or simply pays invoices. Use the table to score every answer in the same terms.

Question to ask Why it matters What a strong answer includes
Do you audit every invoice at the meter level, or a sample at the account level? An account total can look normal while one meter is billed on the wrong rate class or multiplier. Every invoice and every meter, with the meter number printed on each exception.
What do you check each meter’s charges against? A month-over-month variance check shows that a bill changed, not whether it was right. The published tariff or contract rate, the meter’s usage history and thresholds you set, named as separate checks.
How do you find a meter on the wrong rate class? A bill can be calculated correctly on a schedule the site no longer fits. Tariff analysis that compares the meter’s load with the classes available, and a named owner for the reclassification request.
Who sets up utility service when we open a location? Service started outside the program arrives as an unknown account, often paid before anyone audits it. A trigger from your site or real estate records, so the new account is in the platform before its first bill.
Who stops service when we close a location, and who checks the final bill? Closed sites keep billing until someone stops them. One RadiusPoint client was paying $1,500 a month, $18,000 a year, for utilities at closed locations. A named owner for the disconnect, a confirmed final bill and an exception report for any closed site that bills again.
How do you find vacant units that are still billing to us? When a tenant moves out without transferring the account, the cost can land back on the owner. RadiusPoint has published a 12% decrease in utility expenses from vacancy cost recovery. Move-out dates matched to utility bills by unit, with the charges flagged by period so they can be recovered or stopped.
Who owns the invoice images, line-item data and meter list? If the contract is silent, your utility history may stay with the provider when you leave. Ownership stated in the contract, with any export fee named up front.
What do we get back at exit, and in what format? A folder of PDFs can’t be loaded into a new system. Invoices, line items, meters, rate classes and sites in CSV or Excel, plus invoice images, on a stated timeline.
Do reports show consumption in kWh and therms by site and meter? Dollars alone can’t separate a rate increase from a usage increase. Physical units, cost and cost per unit by site, meter and period, with site and date comparisons.
Who pays the utility, and from whose funds? Payment timing drives late fees and disconnection notices. A written funding model: either the provider pays from funds you transfer, or it sends a validated payment file your AP team releases.

Score each answer on three things: does it name a control, an owner and an output you can see? “We keep an eye on that” names none of them. Whichever utility expense management company you shortlist, ask for an example of each output, such as an exception that shows a meter number or a sample exit file, rather than a description of one.

If you’ve bought telecom expense management (TEM) before, the pattern will feel familiar, and the questions to ask a TEM provider cover the telecom side of the same decision. Utilities add two problems of their own: rate classes that decide what each kWh costs, and accounts tied to buildings that open, close and sit empty.

Meter-Level and Tariff Questions Show How Deep the Audit Goes

A meter-level audit checks every meter’s charges against its tariff or contract rate, its usage history and set thresholds, every billing cycle. Ask each provider to show a sample exception with the meter number on it. If the exception names only an account, the review stopped at the account total, where one mispriced meter can hide.

The steps for how to audit a utility bill start at the meter number, because that’s the device the tariff and the kWh attach to. Ask what the provider compares every meter against, and listen for four separate checks:

  • Tariff check: charges compared with the utility’s published rate schedule for that meter’s rate class.
  • Contract check: supply charges compared with the rate you signed, where you buy energy in a deregulated market.
  • Consumption check: usage compared with the same meter’s history, so a spike or a reading of zero stands out.
  • Threshold check: any charge or usage past a limit you set, flagged before the invoice is paid.

A provider that calls all four “auditing” without separating them may be running a month-over-month variance test, which tells you a bill changed but not whether it was right. Ask too whether the audit checks meter multipliers and demand charges, since a wrong multiplier inflates every kWh and kW on the bill.

The rate class gets its own question because the rate schedule decides what each kWh costs. In some states, public utility commissions fully regulate electricity prices, and some utilities offer time-of-day pricing, according to the U.S. Energy Information Administration (EIA). EIA’s latest monthly data put the average U.S. commercial electricity price at 14.47 cents per kWh in August 2026, up 4.3% from a year earlier. A meter on a schedule the site no longer fits pays the wrong price on every one of those kWh, even when the bill is calculated perfectly.

That’s why utility rate reclassification is a separate question from a bill audit. The audit asks whether the bill matches the schedule, and reclassification asks whether the schedule fits the meter. Ask how the provider spots a better-fitting rate class, what load history it needs and who files the request with the utility.

What Happens to the Bills When a Site Opens, Closes or Goes Vacant?

When a site opens, closes or goes vacant, new accounts can bill outside the program and closed accounts keep billing until someone stops them. Ask each provider who triggers the change, who contacts the utility and who checks the next invoice. A strong answer names a feed from your site records and a report, not an email chain.

Openings. Ask how a new location gets into the platform before its first bill arrives. If the answer depends on someone in facilities remembering to email the provider, the first invoices show up as unknown accounts and may be paid without an audit. In ExpenseLogic, real estate system integration supports service setup and disconnect when a location opens or closes.

Closings. Ask who requests the disconnect or transfer, who confirms the final bill and what flags a closed site that bills again. A closed-location billing exception report is built for that last job: a site marked closed, a meter still billing.

Vacant units. For property managers, ask how the provider finds units where a tenant moved out and the utility account landed back in the owner’s name. A strong answer matches move-out dates to utility bills by unit and flags the charges by period. The guide to vacant utility cost recovery explains how those bills arise and who owes them after a tenant leaves.

Growth. Ask how the process holds up as the portfolio grows. RadiusPoint has supported a client’s growth from 170 to 1,200 locations, and a process that relies on email hand-offs struggles long before a portfolio reaches that size.

Who Owns the Data, and Can You Take It With You?

You should own your invoice images, line-item history, meter list and site records, and the contract should say how you get them back. A provider can hold years of your utility history by the time you renegotiate. If the export terms are vague, that history becomes a reason to stay rather than a record you control.

Ask four things and get the answers in the contract: who owns the data during the term, what the exit export contains, what format it arrives in, and whether a fee or waiting period applies. A complete export covers invoice images, every line item, meters with their rate classes, sites with open and close dates, and the audit exceptions and credits. CSV or Excel files load into another system. A folder of PDFs doesn’t.

Ask about exports during the contract, too. A provider that treats every extract as a support ticket is showing you how the exit will go. ExpenseLogic reports export to Excel, CSV and PDF, and it’s still worth putting the exit terms in writing with RadiusPoint, as you would with any other provider.

Some of the raw data starts with the utility. Green Button, an industry-led initiative described by the U.S. Department of Energy, lets utility customers download their own energy usage data, and its Connect My Data option automates that transfer with the customer’s consent where the utility offers it. A provider adds the audited, structured history across every utility and site, and that’s the part to protect in the contract.

Reporting Should Show kWh and Therms by Site, Not Just Dollars

Good utility reporting shows consumption in kWh, therms and gallons by site and meter, beside cost, so you can separate rate changes from usage changes. A dollar-only report can’t tell you whether a site used more or paid more. Ask to see one site’s twelve-month report in the demo and check whether both answers are on the page.

Ask about interval data next. EIA defines advanced meters as meters that record electricity use at least hourly and provide the data to both the utility and the customer at least once a day. In 2025, 17.5 million of the 20.7 million commercial electric meters in the U.S., about 85%, were advanced meters, according to EIA. A provider that uses interval data where your utilities offer it can show when a site peaks, not only how much it used in a month.

Then ask whether invoice and sustainability reports draw on the same audited data, so the kWh in an emissions report match the kWh you paid for.

Which Answers Should Make You Walk Away?

Walk away when a provider audits only a sample, can’t say who stops service at closed sites, or won’t put data export terms in writing. Each of those answers leaves a known leak open after you sign. The other warning signs below are worth flagging in any proposal review, especially when two of them show up together.

  • “We review a sample of invoices.” Utility errors sit on single meters, and a sample skips most of them.
  • Exceptions that name an account but never a meter number.
  • A “tariff check” that turns out to be a comparison with last month’s bill.
  • No named owner for disconnects at closed sites, or a plan that boils down to “you call the utility.”
  • A savings fee with no written definition of savings, no baseline and no end date.
  • Exit exports “available on request,” with no contents, format, fee or timeline in the contract.
  • Reports in dollars only, with no kWh or therms.
  • A payment arrangement where nobody can tell you whose funds pay the utility, or when.
  • A guaranteed savings percentage quoted before anyone has seen your invoices.

One weak answer isn’t always a deal breaker. Two or more in the audit or site-change rows usually mean you’re buying invoice processing with an audit label on it.

How RadiusPoint Answers These Questions With ExpenseLogic

RadiusPoint answers these questions with ExpenseLogic: meter-level audit, tariff analysis, rate reclassification, closed-location billing exception reports and consumption reporting in kWh and therms. RadiusPoint’s Utility Expense Management covers electricity, gas, water, sewer and waste, and each capability maps to a row in the question table.

Two published results match the site questions. One multi-location RadiusPoint client was paying $1,500 a month, $18,000 a year, for utilities at closed locations, and RadiusPoint has published a 12% decrease in utility expenses from vacancy cost recovery.

On payment, RadiusPoint can pay vendor invoices for clients once the client funds the account. Whether to hand over the payment run is a separate decision, and the guide on when to outsource utility bill pay covers the signs that multi-site AP is past capacity.

RadiusPoint was founded in 1992 and is a women-owned business, and ExpenseLogic holds a 4.8 rating on Capterra from 31 reviews, with reviews through December 2025. For the full scope of RadiusPoint’s utility expense management solution, see the Utility Expense Management with ExpenseLogic page.

Every billing cycle a closed site stays open is another bill for a building you’ve already handed back. Request a free ExpenseLogic demonstration and bring this question list with you.

Frequently Asked Questions

How do utility expense management companies usually charge?

Pricing models vary, so ask each provider to name its model in writing. Common structures include a fee per invoice or per account, a platform or subscription fee, and a share of recovered savings, sometimes combined. For any savings-based fee, get the definition of savings, the baseline and the duration in the contract, because those three terms decide what you actually pay.

Is a utility bill audit the same thing as utility expense management?

No. A utility bill audit checks invoices for errors, either once or every cycle. Utility expense management is the ongoing program around it: receiving every invoice, auditing it, allocating the cost to the right site and cost center, reporting consumption and, where the provider offers it, paying the utility. An audit can be one part of a UEM contract, but it isn’t the whole contract.

Do we need utility expense management software or a managed service?

It depends on who will work the exceptions each month. Utility expense management software can flag a wrong rate class or a closed site that’s still billing, but someone still has to dispute the charge, contact the utility and close the account. If your team has those hours, software may be enough. If it doesn’t, a managed service, where the provider’s staff do that work in the platform, fits better.

What should we gather before talking to UEM providers?

Pull a list of sites with open and close dates, the utility accounts and meters you know about, and twelve months of invoices for a few representative sites. Add a short note on how utility bills get paid today and any reporting you owe finance or sustainability teams. With that in hand, each provider can answer the questions above against your real portfolio instead of a demo account.

Does utility expense management cover water, sewer and waste too?

It should, so ask each provider directly. Water, sewer and waste invoices follow different billing rules from electricity and gas, and they often come from municipal utilities and haulers with their own formats. RadiusPoint’s Utility Expense Management covers electricity, gas, water, sewer and waste. Ask every provider which commodities it audits at the meter level and which it only processes for payment.

References

  1. RadiusPoint, “Vacant Cost Recovery: The Utility Bills Nobody Is Watching,” accessed October 2026. https://radiuspoint-expenselogic.com/vacant-utility-cost-recovery/
  2. RadiusPoint, “When to Outsource Utility Bill Pay: Signs Multi-Site AP Is Past Capacity,” accessed October 2026. https://radiuspoint-expenselogic.com/when-to-outsource-utility-bill-pay/
  3. RadiusPoint, “How to Audit a Utility Bill for Errors,” accessed October 2026. https://radiuspoint-expenselogic.com/utility-bill-audit/
  4. RadiusPoint, “Utility Rate Reclassification and How It Lowers Bills,” accessed October 2026. https://radiuspoint-expenselogic.com/utility-rate-reclassification/
  5. RadiusPoint, “Utility Expense Management,” accessed October 2026. https://radiuspoint-expenselogic.com/expense-logic/utility-expense-management/
  6. RadiusPoint, “About RadiusPoint,” accessed October 2026. https://radiuspoint-expenselogic.com/about/
  7. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews, accessed October 2026. capterra.com
  8. U.S. Energy Information Administration, “Electricity Monthly Update,” end-use data for August 2026, released October 23, 2026. eia.gov
  9. U.S. Energy Information Administration, Electric Power Annual, Table 10.05, “Advanced Metering Count by Technology Type, 2016 through 2025,” accessed October 2026. eia.gov
  10. U.S. Energy Information Administration, “How many smart meters are installed in the United States, and who has them?” Frequently Asked Questions, October 20, 2023. eia.gov
  11. U.S. Energy Information Administration, “Electricity explained: Prices and factors affecting prices,” accessed October 2026. eia.gov
  12. U.S. Department of Energy, “Green Button,” accessed October 2026. energy.gov

This article is general information for finance, facilities and property teams comparing Utility Expense Management providers. It isn’t legal, accounting or procurement advice, and contract terms should be reviewed by your own counsel. RadiusPoint results cited here come from specific client engagements described on the pages listed in References and aren’t a guarantee of results for your organization. Electricity prices and meter counts are national figures from EIA and won’t match any single site or utility.

How to Choose an MMS Platform That Works for Telecom and Finance

TEM0

Your telecom manager and your controller can open the same wireless invoice and need different things from it. The telecom manager wants to know which device sits behind each line, who carries it and whether it should still be live. The controller wants each charge coded to a cost center and a general ledger (GL) account, accrued before close and tied to someone who still works there.

An MMS platform optimized for telecom and finance is a managed mobility services system that keeps one record for every mobile line, by phone number and Employee ID, and turns that record into what both teams need: device inventory and change tickets for telecom, and allocations, accruals and GL files for finance. If a platform serves only one side, the other team rebuilds the data in a spreadsheet.

So when someone asks which MMS platform is optimized for telecom and finance, the useful answer is a set of tests rather than a brand name. (MMS here means managed mobility services, not the multimedia messaging platforms that also show up in searches for the term.)

RadiusPoint runs managed mobility services on its ExpenseLogic platform, where invoice processing is allocated down to the phone number and Employee ID. After RadiusPoint audited more than 600 lines for a food service company and set a wireless policy, the company cut costs 22%, saving more than $400,000 in year one.

Key Takeaways

  • An MMS platform built for both teams keeps one record per mobile line, tied to a phone number, a device, an Employee ID and a cost center.
  • Telecom needs a device and line inventory, change tickets with approval workflows and a way to find zero-use lines.
  • Finance needs charges allocated to phone number and Employee ID, a monthly accrual file and a GL interface file it can load at close.
  • The HR roster connects both sides: Employee IDs checked against it each month expose lines still billing for people who’ve left.
  • In RadiusPoint engagements, a food service company cut costs 22% (more than $400,000 in year one), and a Fortune 100 company saved $830,000 annually through wireless discovery and optimization.

Short version: Pick the MMS platform that can trace any wireless charge from the carrier invoice to a phone number, an Employee ID, a cost center and a GL account, because that one record is what lets telecom and finance stop keeping separate spreadsheets.

What Should an MMS Platform Do for Telecom and Finance at the Same Time?

An MMS platform should keep one record for every mobile line and turn that record into telecom’s inventory and finance’s month-end files. Each line needs a device, a user, an Employee ID, a cost center and a contract rate attached. When telecom changes a line, finance’s numbers should change with it, without anyone retyping a row.

Telecom works the line record, and finance posts from it. The table pairs each team’s need with the ExpenseLogic capability that covers it.

Platform area What the telecom team needs What finance needs ExpenseLogic capability
Line and device record Every smartphone, tablet and wearable by serial number, with its line and user attached Every line tied to an Employee ID and a cost center, so each charge has an owner Device and inventory management by serial number and Employee ID
Invoice processing Charges matched to the right line and device Each charge allocated to the person and cost center that used the service Monthly invoice processing allocated down to the phone number and Employee ID
Changes (MACD) Moves, adds, changes and disconnects ordered and tracked in one place An approval on record for every new line or upgrade that adds cost MACD ticketing with client-defined approval workflows
Unused service Lines with no usage flagged for disconnect or reassignment Spend on idle lines stopped instead of paid again next month Zero-use device identification
Departed employees Lines and devices from people who’ve left found and recovered No charges allocated to people who are no longer on payroll Employee ID validation against the HR roster, with ex-employee line detection
Invoice accuracy Billed rates checked against the contract and the rate plan Errors disputed with the carrier, not booked as expense Line-item audit, bill audit and rate plan optimization
Month-end close Missing carrier bills identified and chased An estimate booked for service used but not yet billed Monthly accrual files and daily missing-bill reporting
Posting to the ledger One audited invoice record per billing account Coded charges in a file the accounting system can load GL interface files for the accounting system

Read the table across, not down: a shortlisted platform should answer the telecom column and the finance column in every row. A tool built around devices can track hardware and still stop at the invoice, which leaves the controller keeping an allocation spreadsheet. A tool built around billing can code the invoice and still not know who carries the device behind a line, which leaves telecom keeping its own inventory. Month-end then becomes the place where someone reconciles the two by hand.

Wireless is also one slice of your telecom expense management (TEM) program, and this comparison of wireless expense management vs TEM shows where the two meet. Whether you’re buying MMS software for mobile expense management or a managed service, the same table applies.

The Telecom Side Needs an Inventory It Can Act On

For the telecom team, the platform has to hold an accurate device and line inventory and let staff change it through tracked, approved tickets. An inventory that changes outside tickets goes stale. A ticket that never updates the inventory creates a second record. The platform should handle both in one place.

In ExpenseLogic, devices and lines are tracked by serial number and Employee ID, covering smartphones, tablets and wearables. MACD (move, add, change, disconnect) tickets run through approval workflows the client defines, and annual line registration keeps user records clean and current.

The second telecom test is unused service. A zero-use line has no voice, data or text use in the window you choose, and it keeps billing until someone stops it. This guide to finding zero-use mobile lines covers the checks to run before a disconnect. Bill audit and rate plan optimization belong here too, because a plan that doesn’t match usage is a telecom fix with a finance payoff.

What Does Finance Need Before It Trusts the Wireless Number?

Finance needs every wireless charge allocated to a phone number and Employee ID, an accrual for unbilled service, and a GL file it can load. Without those three outputs, the controller books last month’s total, codes the invoice to one department and explains the variance later. With them, wireless cost lands where it was incurred, in the period it was incurred.

Allocation comes first. ExpenseLogic processes each monthly invoice and allocates it down to the phone number and Employee ID, so a charge follows the person and their cost center instead of sitting on one billing account.

Timing comes second. A telecom accrual file estimates service used this period but not yet invoiced, so the expense posts in the right month even when a carrier bill arrives late. ExpenseLogic produces monthly accrual files, and daily missing-bill reporting flags invoices that haven’t arrived.

Posting comes third. A GL interface file lists audited charges with their GL accounts and cost centers in a format the accounting system can load, which replaces journal entries keyed by hand from a PDF invoice. ExpenseLogic’s line-item audit checks invoice lines against contracted rates and inventory, so a billing error can be disputed rather than coded and paid.

The Employee ID Is Where Telecom and Finance Meet

The Employee ID connects both sides, because a line tied to a valid, current employee is both a known device and a chargeable cost. When that ID stops matching the HR roster, telecom has a device to recover and finance has a charge with no owner. A monthly check against the roster catches the mismatch before it repeats for months.

Turnover makes this a monthly job. U.S. employers recorded 62.8 million total separations in 2025, and the total separations rate averaged 3.3% a month, according to the Bureau of Labor Statistics. Applied to a 5,000-person workforce, that rate works out to about 165 departures in an average month, and each departing employee with a company phone leaves a line to stop or reassign.

ExpenseLogic validates Employee IDs against a monthly HR roster and flags lines still assigned to former employees. HR’s part is a current employee list, and ExpenseLogic’s asset management module interfaces with the HR Employee ID.

Which Questions Separate a Platform From a Spreadsheet With a Login?

Ask the vendor to trace one line from invoice to ledger in the demo; a platform shows it live, while a spreadsheet needs an export. Bring someone from telecom and someone from finance, and have each ask their own questions. Write down which answers needed a follow-up file.

  1. Pick one phone number from our last invoice. Can you show its device, user, Employee ID, cost center and GL account on one screen?
  2. That user left last month. Where does the platform flag the line, and who sees the flag?
  3. Which of our lines had no usage last cycle, and what’s the next step for each one?
  4. Who approves a new line or an upgrade, and where is that approval stored?
  5. When a change ticket closes, does the inventory update from the ticket, or does someone retype it?
  6. Is every invoice line checked against the contract rate and the inventory, or only a sample?
  7. A carrier bill is late at close. What does the accrual file show for that account?
  8. Can the GL interface file come out in our chart of accounts and our import format?
  9. Each month, who works the exceptions: our staff or yours?

Questions 1, 2 and 8 matter most to a joint buying team, because they test whether telecom’s record and finance’s file come from the same data. If an answer needs an export, a lookup table or a promise to build a report later, you’re looking at a spreadsheet with a login.

When Does Managed MMS Fit Better Than Software Alone?

Managed MMS fits better when nobody on staff has the hours to work the platform each month, because software records problems but people resolve them. Flagged zero-use lines still need disconnect tickets. Billing errors still need carrier disputes. Missing bills still need chasing. If those queues grow every month, the gap is labor, not software.

That’s the case for managed mobile expense services, where the provider’s team works the platform for you. RadiusPoint runs it that way: ExpenseLogic is the platform, and RadiusPoint’s staff work the invoices, chase the carriers, file the disputes and close the tickets. For MMS clients, the RadiusPoint help desk also handles line suspension, call forwarding, troubleshooting and unauthorized purchase management.

The results reach both teams. A Fortune 100 company saved $830,000 annually through wireless discovery and optimization with RadiusPoint, and the food service company in the managed mobility case study cut costs 22% once its lines were audited and a wireless policy was in place. Software alone still fits a team with a dedicated telecom analyst, a finance owner for the GL mapping and the hours each month to clear exceptions.

How RadiusPoint and ExpenseLogic Serve Both Teams

RadiusPoint’s ExpenseLogic platform holds the line inventory telecom works from and produces the accrual and GL files finance closes the month with. Wireless invoices sit on the same platform as telecom and Utility Expense Management (UEM), so finance works with one system across all three. RadiusPoint’s team does the monthly work inside it.

The ExpenseLogic managed mobility services page lists the full scope, from device procurement and deployment through recovery, recycling and retirement.

Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 Vendor SmartList for Telecom Expense Management, and ExpenseLogic holds a 4.8 rating from 31 reviews on Capterra. RadiusPoint was founded in 1992 and is a women-owned business.

Every month a former employee’s line stays live, it bills again and lands on a cost center nobody is watching. Request a free demonstration of ExpenseLogic and bring the nine questions above.

Frequently Asked Questions

Is an MMS platform the same as an MMS messaging platform?

No. In expense management, MMS stands for managed mobility services: running a company’s mobile devices, lines and the wireless spend behind them. MMS is also the abbreviation for multimedia messaging service, the standard for sending pictures and video by text, and messaging platforms for banks and lenders use that meaning. Searches for an MMS platform for finance return both, so check which one a vendor sells.

Do we still need MDM software if we buy an MMS platform?

Probably, because the two solve different problems. Mobile device management (MDM) software configures and secures the device itself, with settings such as passcodes, app controls and remote lock. The platform criteria in this article cover lines, invoices, users and cost. Ask each vendor which of the two it provides, and how device records and Employee IDs pass between the systems if you run both.

Who should own the MMS platform, telecom or finance?

Both should, with separate jobs. Telecom typically owns the inventory, the carrier relationships and the MACD approvals. Finance owns the cost center mapping, the GL accounts and the accrual review at close. HR supplies the employee list. The platform is the shared record, so a change one team makes shows up for the others without a hand-off file.

What HR data does an MMS platform need from us?

At minimum, a current employee list with Employee IDs, sent on a regular schedule, plus whatever cost center detail your allocation rules depend on. ExpenseLogic validates Employee IDs against a monthly HR roster. Without that feed, a platform can’t reliably tell a departed user’s line from an active one until someone reports it, and the line keeps billing in the meantime.

Can the platform provider pay the carriers too?

It depends on the provider. RadiusPoint can pay vendor invoices for clients once the client funds the account. If your AP team would rather keep the payment run, it can pay carriers from the audited invoice detail and the GL interface file. Either way, agree up front on who approves each payment and how disputed charges are handled before money goes out.

References

  1. RadiusPoint, “How Managed Mobility Services Cut Costs 22% ($400K in Year 1),” food service case study, accessed October 2026.
  2. RadiusPoint, “Managed Mobility Solution & Service,” accessed October 2026.
  3. RadiusPoint, “ExpenseLogic,” platform modules page, accessed October 2026.
  4. RadiusPoint, “How Controllers Use a TEM GL Interface File in Month-End Close,” accessed October 2026.
  5. RadiusPoint, “What a Telecom Accrual File Is, and How Finance Teams Build One,” accessed October 2026.
  6. RadiusPoint, “Finding and Killing Zero-Use Mobile Lines,” accessed October 2026.
  7. RadiusPoint, “Wireless Expense Management vs Telecom Expense Management,” accessed October 2026.
  8. U.S. Bureau of Labor Statistics, “Job Openings and Labor Turnover Survey News Release, January 2026,” USDL-26-0439, March 13, 2026 (annual 2025 figures). bls.gov
  9. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  10. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews, accessed October 2026. capterra.com
  11. RadiusPoint, “About RadiusPoint,” accessed October 2026.

This article is general information for telecom and finance teams comparing managed mobility services platforms. It isn’t accounting, legal or procurement advice. Client results describe specific RadiusPoint engagements on the pages listed in References and aren’t a guarantee of results for your organization. The turnover example applies a national average rate and won’t match any single employer.

ExpenseLogic Named a Top Pick for Utility and Telecom Invoice Auditing in Capterra’s 2026 Telecom Expense Management Software Report

News0

ExpenseLogic Named a Top Pick for Utility and Telecom Invoice Auditing in Capterra’s 2026 Telecom Expense Management Software Report

We’re proud to share that ExpenseLogic has been named the top pick in Capterra’s latest report, “My 7 Best Telecom Expense Management Software Picks in 2026, Based on 644 Capterra Reviews,” which analyzed 644 verified reviews of telecom expense management software and ranked seven platforms by overall Capterra rating, with review count used as a tiebreaker.

ExpenseLogic is featured as the Best pick for utility and telecom invoice auditing.

ExpenseLogic is a utility and telecom expense management platform built for accounts payable and facilities teams auditing invoices across many locations and vendors at once. From utility and telecom invoice processing to ACH payment collection and multi-location lease tracking, we built our platform to replace a patchwork of spreadsheets with one audit trail, and this recognition reflects how our ExpenseLogic community puts that to work every day.

This comes as no surprise, since ExpenseLogic has earned an overall rating of 4.8 out of 5 across the 31 verified reviews Capterra analyzed for this report, with the score of the seven platforms ranked, with a 4.7 out of 5 for both ease of use and customer service across its full Capterra review history.

One Dashboard for Every Utility, Telecom, and Lease Invoice

ExpenseLogic was featured in this report because reviewers consistently describe reporting depth as the reason they stay: one dashboard that replaces several spreadsheets for teams auditing utility, telecom, and lease costs together across many sites. What sets ExpenseLogic apart in this report is how far its auditing reaches past phone bills alone, into utility and lease invoices too, which matters for facilities and accounts payable teams who would otherwise be piecing that picture together by hand.

Payment Processing That Takes the Pressure Off Your AP Team

Being named Capterra’s top pick in this category tells about the auditing depth and payment processing we’ve prioritized, which are genuinely making a difference for the accounts payable and facilities teams who run their utility and telecom spend through ExpenseLogic every day, and it’s a milestone we’re sharing with every analyst, support specialist, and engineer who helped make it possible.

Here’s a further look at what our users have to say about their experience with us:

“We really liked the dynamic reporting capabilities of the software along with the easy of use that was reported across our team. The payment processing aspect of their services totally takes the pressure off of our AP team.”
— Karla C., Manager, Hospital and Health Care [Source: Capterra]

“Expense Logic makes it easy for me to compile reports on my various location’s leases. It does a great job of summarizing monthly, quarterly, and yearly data.”
— Shawn O., North America Facilities Manager, Facilities Services [Source: Capterra]

“It was easy to navigate and find my way around different sections of the site, and value for money” — Ben S., Procurement Specialist, Machinery [Source: Capterra]

About ExpenseLogic: ExpenseLogic is a utility and telecom expense management platform that brings invoice auditing, ACH payment processing, and multi-location lease and usage tracking into one system, built for accounts payable and facilities teams managing utility, telecom, and wireless costs across many sites. 

Disclaimer: Capterra’s independent and objective insights help software buyers evaluate which systems are most appropriate for their needs. Learn more.

Acquisition Telecom Cleanup: Inventorying Circuits After a Merger

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

Acquisition telecom cleanup starts by inventorying every BAN and circuit from both companies, then clearing duplicates before you renegotiate carriers or redesign networks. Day-one rate bake-offs feel productive. Without a census, they lock in blind spots from both estates.

Post-merger telecom cleanup is a BAN and circuit census first, then duplicate clearing, disconnect decisions, credit pursuit, and GL merge. RadiusPoint loads acquired inventories into ExpenseLogic so the combined company runs one multi-carrier audit estate instead of two competing spreadsheets.

Key Takeaways

  • Day-one priority is a complete BAN and circuit census, not an early rate bake-off.
  • Merged estates hide duplicate circuits, dual BANs at one site, and contracts mid-notice-window.
  • Cleanup savings are only credible when disconnects and credits map to inventory IDs finance can audit.
  • MACD freezes and LOA scope updates prevent ordering chaos during integration.
  • RadiusPoint consolidates acquired telecom inventories into ExpenseLogic for one multi-carrier audit estate.

The Short Version

  1. Census BANs and circuits from both entities (CSRs, BAN lists, contracts).
  2. Flag duplicates and dual BANs per site.
  3. Decide retain or disconnect with an owner.
  4. Pursue credits for erroneous charges.
  5. Merge GL coding into one model on ExpenseLogic.

That Merger Telecom Cleanup Sequence is the playbook Controllers will fund because each step leaves an inventory ID they can sample.

Day-one census before any carrier meeting

Before carrier meetings, pull CSRs and BAN lists from both entities so ExpenseLogic starts with a full circuit census rather than a partial rumor inventory. Renegotiation without inventory truth recreates the acquiree’s blind spots under a new logo.

Start the census in diligence when possible. Otherwise start in week one of integration. Capture carrier, BAN, service ID, site, contract end, notice window, and interim owner for every row. RadiusPoint treats that file as the first onboarding artifact for the combined estate, aligned with the same discipline as TEM onboarding data.

Wireless devices of acquired employees need a parallel pass: HR roster reconciliation and line inventory beside wireline circuits. Wireline cleanup alone leaves mobility spend billing for badges that already closed.

After close, expect dual BANs at shared sites and overlapping circuits that both entities ordered for the same building or backup path. Legal day one does not delete either company’s last three years of MACD habits.

Use a Dual-BAN Site Card per location during integration:

Field What integration captures
Site / building Canonical location name and code
BANs present Every Billing Account Number still billing the site
Circuits / service IDs Active paths, including backup and temporary builds
Contract ends / notice windows Dates that can silently renew during integration
Owner Named telecom and business owner post-close
Retain / disconnect draft Decision pending evidence, not a hallway guess

Duplicate discovery is an audit job with inventory keys, not a network redesign slide. Telecom audit services should flag dual billing and dead paths before anyone promises synergy dollars.

Contract notice windows inside the integration calendar

Put acquired contract notice windows on the integration calendar immediately so silent renewals do not lock rates while teams are busy on network redesign. Integration calendars already track HR, real estate, and systems. Telecom notice windows belong there too.

A contract mid-window during a merger is a finance risk disguised as an IT backlog item. Miss the window and you inherit term length you did not choose while duplicate circuits still bill. Demand and capacity planning for the combined estate should include those dates; RadiusPoint’s material on demand planning and forecasting is adjacent to that calendar discipline even when the immediate job is cleanup, not growth.

LOAs usually need re-papering for acquired BANs. Scope ordering rights carefully so integration vendors cannot place blanket orders while MACD should be frozen or tightly approved.

Cleanup sequence that finance will fund

Sequence cleanup as inventory validate, duplicate flag, disconnect or retain decision, dispute credits, then GL coding merge so Controllers see controlled savings. Skipping to carrier consolidation without that sequence recreates blind spots faster than it removes them.

Cleanup savings are credible only when disconnects and credits map to inventory IDs. Inventory management on RadiusPoint’s published record recovered $174,000 in re-credits when inventory truth drove pursuit. A client growth path from 170 to 1,200 locations on the published record shows why a single estate matters after scale events; a merger is a scale event with worse starting data quality.

Telecom refund recovery belongs after the retain or disconnect decision, not before. Filing disputes on circuits you still have not classified wastes carrier windows and Controllers patience.

How RadiusPoint stabilizes post-merger TEM on ExpenseLogic

RadiusPoint loads both estates into ExpenseLogic, reconciles multi-carrier BANs, and runs MACD under client approvals until one telecom inventory of record remains. Software plus people is the stabilizer: the platform holds one schema; analysts work dual BANs, regional carriers, and credit pursuit while integration teams redesign networks.

Practical controls during the transition:

  • MACD freeze or heightened approval on acquired BANs until owners are named.
  • One exception queue across both legacy estates.
  • Scoped LOAs for acquired accounts.
  • GL coding map that Controllers approve before the first combined close.

Preserve inventory deliberately when tools change mid-integration. Losing service IDs while switching platforms is how mergers pay for the same circuit twice under a new vendor login. Treat the move like a controlled inventory handoff, not a cutover party.

Cleanup is done when one inventory of record, one exception queue, and one GL coding model cover the combined estate. Until then, you still have two companies’ telecom problems sharing a letterhead.

Integration leads often ask for a single carrier meeting in week two to “show progress.” Bring the Dual-BAN Site Cards instead. Carriers will optimise what you still cannot name. RadiusPoint’s posture in ExpenseLogic is to refuse a bake-off narrative until the census rows are complete enough for Controllers to sample.

Closed-location billing on the utility side is a useful analogy only: inventory status should stop charges AP would otherwise pay. On telecom, the parallel is dead circuits and dual BANs after legal day one. Do not import utility dollar figures into a telecom synergy slide. Import the control idea: status before remittance.

Post-Close Controls That Keep the Cleanup From Slipping

The weeks right after close are when discipline pays off, because that’s when accountability is easiest to lose. Roles are shifting, two teams are learning each other’s systems, and the acquired estate has no clear owner yet. So the first control we put in place is a single named owner for the combined inventory, with a short weekly checkpoint where every open disconnect, credit and contract action gets a status. It’s low effort, and it stops work from stalling in the handoff between two organizations that don’t yet share a process.

Evidence is the second control. Every entry in the combined inventory needs to trace back to a source: a carrier record for the service, a signed agreement for the rate, and a work order for anything that changed. When an entry can’t be sourced, it gets flagged rather than assumed, because an unverified line is exactly where a duplicate or a phantom charge hides. Holding to that standard turns the inventory from a best guess into something finance and the carriers will both accept when a dispute comes up.

Carrier coordination is where the two estates actually merge in the outside world. Each carrier has its own process for consolidating accounts, transferring responsibility to the surviving entity, and closing services, and those processes move at different speeds. We sequence the requests so dependent actions don’t collide, confirm each one in writing, and hold a service active until its replacement is verified live. That last rule matters most at shared sites, where cutting the wrong connection takes people offline.

None of this holds without an audit trail. Every disconnect order, credit filing and account change carries a date, a reference number and a confirmation, kept together so the history is reconstructable months later. That record is what protects the recoverable dollars: a credit filed inside the carrier’s dispute window only stays recoverable if you can show when it was raised and what it was raised against. The audit trail is also what an acquirer’s finance team leans on when they need to prove the cleanup actually happened.

Credits and the general ledger handoff close the loop. As disputes resolve, the credits post against the accounts they came from, so the savings show up where the spend lives rather than as a lump nobody can trace. In parallel, the two companies’ coding gets reconciled into one scheme, so combined reporting reads cleanly from the first full month it runs. In ExpenseLogic, that unified coding is what lets RadiusPoint hand finance a combined view instead of two files they have to stitch together.

  • Name one owner for the combined inventory and hold a short weekly status on open actions.
  • Require a carrier record, a contract and a work order behind every inventory line, and flag anything unsourced.
  • Confirm every carrier action in writing and keep a service live until its replacement is verified.
  • Post credits against their originating accounts and merge GL coding before the first combined report.

Frequently Asked Questions

How soon after close should TEM cleanup start?

Start the census in diligence if possible. Otherwise start in week one of integration. Carrier meetings can wait until BANs and circuits from both entities sit in one list.

Should we pick one carrier immediately?

Not before inventory truth. Early consolidation without a census locks in duplicate paths and orphan BANs under a preferred logo.

What about wireless devices of acquired employees?

Run HR roster reconciliation and line inventory in parallel with wireline circuit cleanup. Ex-employee and duplicate lines are merger leakage with a different invoice layout.

Do LOAs need re-papering?

Usually yes for acquired BANs. Update Letter of Agency scope so ordering rights stay limited during integration and MACD stays under named approvals.

When is cleanup done?

When one inventory of record, one exception queue, and one GL coding model cover the combined estate in ExpenseLogic, and Controllers can sample disconnects and credits by service ID.

Census First, Synergy Second

Acquisition telecom cleanup rewards teams that inventory before they renegotiate. RadiusPoint consolidates both estates in ExpenseLogic so duplicate circuits, dual BANs, and notice windows become managed work instead of integration folklore.

Request a post-merger BAN census load into ExpenseLogic and ask to walk five Dual-BAN Site Cards from discovery to retain or disconnect to credit to GL impact.

This article is educational. RadiusPoint does not guarantee synergy percentages, cleanup timelines, or carrier outcomes. Published figures cited are specific client outcomes and were current as of 15 September 2026.

Facility Utility Bill Pay vs Utility Expense Management: Where Audit Starts

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

Utility bill pay clears invoices by their due date. Utility Expense Management, UEM after this first use, starts earlier. It audits the meter inventory, the tariff, and each site’s open or closed status before any funds move. Bill pay answers “did we pay on time.” UEM answers “should we have paid this at all, and at this rate.”

Here’s the tension that quietly drains a facilities budget. An accounts payable team can hit every due date, dodge every late fee, and still remit thousands of dollars a month for electricity, gas, and water at buildings nobody occupies. The invoices were paid correctly. They should never have reached payment. At RadiusPoint, one multi-location client was paying roughly $1,500 a month, about $18,000 a year, in utilities at closed locations that bill pay alone had no reason to question.

If you’re a Facilities Manager, Real Estate leader, Controller, or CFO deciding what to buy or build, the distinction below decides whether spend gets validated or just settled.

Key Takeaways

The core takeaway: bill pay clears invoices by due date, while UEM validates meter inventory, tariff, and site status before any funds move.

  • Bill pay optimizes for timeliness. UEM optimizes for meter and tariff correctness. Paying on time is not the same as paying the right amount.
  • A UEM audit starts with meter inventory and site status, not with remittance. The first question is what should be billed, not what is due.
  • Vacant and closed sites leak cash under bill pay alone, because a paid-on-time invoice for an empty building still clears.
  • RadiusPoint runs UEM on ExpenseLogic across electricity, gas, water, sewer, and waste, with meter-level controls and vacant cost recovery built in.

Utility Bill Pay Goals vs UEM Goals: Timeliness vs Correctness

Bill pay aims to avoid late fees and keep service running, while UEM aims to pay only validated, meter-level charges billed at the correct tariff.

Bill pay is measured on cycle time and clean remittance: received, coded, approved, and paid before the disconnect date. Every one of those steps assumes the charge is legitimate. Bill pay has no mechanism to ask whether the meter behind the account still serves an active site, or whether the rate matches what the account qualifies for.

UEM inverts the order. Before it clears anything, it validates the charge against a record of what should exist: which meters, at which sites, on which tariff, within which consumption range. When a building goes dark, UEM flags the still-arriving invoice and triggers vacant utility cost recovery rather than routing it to payment like any other bill.

Question it answers Utility bill pay Utility Expense Management
Is this invoice due soon? Yes, this is the core job Yes, but only after validation
Does this meter serve an active site? No visibility Checked against site status
Is this the correct tariff class? No visibility Audited against rate rules
Is consumption within a normal range? No visibility Threshold-tested per meter
Primary risk it removes Late fees, service interruption Overpayment, phantom spend, wrong rate

Where the Audit Starts in a UEM Program

A UEM audit starts before payment with a meter inventory, a tariff class check, consumption thresholds, and each site’s open or closed status.

Remittance is the last step, not the first. Bill pay begins at the invoice and ends at the payment. UEM begins several steps upstream, at the reference data that tells you whether the invoice deserves to be paid. That reference data is a meter-level inventory, not an account list, because a single account can span multiple meters and a single site can carry meters that were never decommissioned. Auditing at account level is how closed-site charges survive. Auditing at meter level is how they get caught.

Step Question asked Bill pay does this?
1. Due date When must this be paid to avoid a fee or disconnect? Yes, first and only
2. Meter inventory Which meters exist, at which sites, tied to which accounts? No
3. Tariff validation Is the account on the correct rate class for its usage and location? No
4. Site status Is this location open, vacant, or closed as of this billing period? No

A bill pay process runs step one and skips to payment. A UEM process runs steps two through four first. Tariff validation is where a surprising share of recoverable money sits, because a wrong rate class bills quietly and consistently for years. When usage or site type no longer matches the assigned rate, that’s a utility rate reclassification finding, and it belongs to the audit, not to accounts payable.

Utility Bill Pay vs UEM: The Operating Model Side by Side

Side by side, bill pay and UEM differ in who owns them, what data keys they use, which exceptions they raise, and what they report.

Bill pay and UEM look identical at the moment of payment, because the invoice gets paid either way. The divergence lives in everything before and after that payment, which the table below lays out.

Dimension Utility bill pay Utility Expense Management
Owner Accounts payable, treasury Facilities, real estate, and finance, coordinated
Data key Vendor account number Meter number tied to site and cost center
Trigger Invoice arrives Invoice arrives and inventory is checked
Exception type Payment failed or is overdue Wrong tariff, off-threshold usage, charge at a closed site
Action on exception Chase the payment Dispute the charge, file for a credit, correct the rate
Reporting output Paid versus outstanding Cost by site and meter, recovery filed versus credited, tariff variance

The data key row drives everything else. Bill pay is organized around the vendor account. UEM is organized around the meter, mapped to a site and a cost center. That single choice is what lets UEM allocate spend accurately, benchmark one location against another, and detect a charge at a site that closed last quarter. Fixing exceptions rather than settling invoices is why UEM sits closer to the discipline described in our overview of invoice auditing services than to a payment queue.

Vacant and Closed Sites: The Proving Ground for UEM

Vacant and closed sites prove whether you manage expenses or only pay bills, because site status should stop charges accounts payable would otherwise remit.

When a location closes or a tenant moves out, the meters rarely stop with them. The account stays open, the utility keeps billing, and unless someone has connected site status to the payment process, the invoices keep clearing. They arrive on schedule, for a plausible amount, against a real account, and they pay on time for a building that’s empty.

This is exactly where the RadiusPoint closed-location figure comes from: roughly $1,500 a month, about $18,000 a year, for one multi-location client, paid out on utilities at sites no longer in use. Under bill pay alone, that spend is invisible. Under UEM, the vacant or closed status flags the meter, the charge routes to an exception instead of to payment, and recovery begins. Across a property portfolio, chasing exactly this pattern is how vacant cost recovery has decreased utility expenses by 12 percent.

A late invoice gets noticed within days. A perfectly paid invoice for an empty building can bill for years. Only UEM is looking for the second one.

How RadiusPoint Runs UEM on ExpenseLogic

RadiusPoint validates utility invoices at meter level inside ExpenseLogic, allocates each cost to the right site, and recovers spend that tenant transitions leave behind.

The platform holds the inventory and people work the exceptions. ExpenseLogic is the record of what should be billed: the meters, the sites, the tariffs, and the consumption thresholds each account is measured against. Every incoming utility invoice for electricity, gas, water, sewer, and waste is validated line by line against that record, then allocated down to location, department, and meter number. When a charge fails the tariff check, breaks a threshold, or hits a meter at a closed site, ExpenseLogic raises the exception.

The other half is the part most platforms leave to the client. A RadiusPoint analyst takes the exception, files the dispute with the provider, pursues the credit, and, in the vacant case, works the account back to closure so the leak stops rather than just gets reported. Software plus people is the model.

Verdict: if your first question is the due date, you’re buying bill pay. If your first question is the meter inventory and the tariff, you’re buying UEM. Both keep the lights on. Only one keeps you from paying for lights in a building that’s dark.

The practical move for most portfolios isn’t to abandon bill pay. It’s to put a UEM audit layer in front of it, so validation happens before funds move. If you also manage telecom or wireless spend and want the same allocation and close pattern across categories, the case for a managed provider is laid out in our guide to when you need TEM. RadiusPoint delivers that layer on ExpenseLogic, and it starts at the meter, not the due date.

Frequently Asked Questions

These answers clarify what UEM means here, whether AP automation suffices, how deregulation and rate reclassification apply, and whether TEM and UEM belong together.

Is UEM Unified Endpoint Management?

No. In this article UEM means Utility Expense Management. Unified Endpoint Management is an unrelated IT term for managing devices. Here, UEM is the discipline of auditing, allocating, and controlling utility spend across electricity, gas, water, sewer, and waste.

Can AP automation alone deliver UEM?

It can pay, but it can’t audit. Accounts payable automation processes and remits invoices efficiently, which is bill pay done well. Meter and tariff audit still need UEM inventory and rules, because AP automation has no record of which meters should exist or what rate each account qualifies for.

Do we need deregulated procurement to start UEM?

No. Audit and allocation create value in regulated markets too. Procurement and rate shopping depend on deregulation, but validating meters, catching wrong tariff classes, allocating cost by site, and recovering charges at closed locations work regardless of market structure.

How does rate reclassification fit?

Wrong tariff classes are a UEM audit finding, not a bill pay task. When an account’s assigned rate no longer matches its usage or site type, the charge bills quietly and correctly from the provider’s side. Only a meter-level audit that validates tariff against the account catches it and files for the correction.

Should TEM and UEM share a platform?

Sharing ExpenseLogic gives Controllers one allocation and close pattern across categories. Telecom, wireless, and utility spend then validate, allocate, and report the same way, on one meter-and-account-keyed record, instead of living in separate tools with separate exception handling and separate month-end routines.

How to Prove TEM Savings to Finance Without Inflating Avoidance Dollars

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

Prove TEM savings with hard refunds, documented rate cuts on live services, and eliminated inventory, while labeling avoidance separately so finance never sees inflated totals. The reason this matters is simple. A Controller has sat through too many savings decks that fall apart on the second question. A headline number lands, someone asks how it was calculated, and half of it turns out to be avoidance annualized on optimistic assumptions. Once that happens, every future number your telecom expense management program reports gets quietly discounted.

Key Takeaways

This is the entire method in one place: separate the three buckets, evidence every line, label avoidance honestly, and hand audit a re-performable ledger.

  • Hard savings are cash refunds and permanent bill reductions tied to a BAN and an invoice period.
  • Avoidance is real but different, because it’s spend prevented, not cash hitting the ledger.
  • Inflated avoidance, the habit of counting every hypothetical, destroys credibility with Controllers faster than a missed number ever will.
  • Evidence packs need before and after rates, inventory IDs, carrier credit memos, and GL impact.
  • RadiusPoint structures savings reporting from ExpenseLogic audit work so finance can re-perform the logic without a meeting.

Hard savings versus avoidance versus soft claims

Hard savings change cash or recurring bills, avoidance prevents spend, and soft claims without BAN-level evidence do not belong in a finance packet.

The difference isn’t academic. It decides which line a Controller will defend to an auditor and which line gets struck before the report leaves the building. Sort every claimed saving into one of three buckets. We call it the Three-Bucket Savings Model, and it’s the first thing that goes on any RadiusPoint savings report.

Bucket What it is Evidence it needs How it hits finance
Hard savings Cash refunds and credits, plus a bill you were paying that permanently drops, such as a disconnected service that stops billing Carrier credit memo, or the before and after invoice on the same BAN and service ID Real money: cash returned, or a lower recurring invoice from now on
Negotiated recurring savings A contracted or optimized rate that lowers a live, still-billed service every cycle Signed rate exhibit tied to the service ID, showing the old rate and the new rate Lower recurring cost for as long as the service stays active at the new rate
Avoidance Spend you prevented that never reached an invoice, such as an order you stopped or a plan you right-sized before it billed A dated decision with the quantified basis behind it Budget protected, but no cash moves and no invoice drops

Soft claims are everything else: productivity, hours saved, general efficiency. They can be true and still not belong in the savings total, because finance can’t reconcile them to a BAN. Put them in the narrative, not the number. The cleanest hard-savings line is a recovered credit, which is the core of telecom refund recovery, and it’s also the line auditors accept most easily, because a credit memo is a document a carrier issued, not a calculation you performed.

Where programs inflate numbers and how to stop

Inflation happens when one-time credits are annualized forever, baseline rates are fictional, or disconnected services get double-counted as both a refund and ongoing avoidance.

None of these require dishonesty. They usually come from a spreadsheet that was built to look impressive rather than to survive review. Each has a fix, and the fix is always the same shape: anchor the number to evidence and count it once.

Anti-pattern Why it inflates The fix
Annualizing a one-time credit forever A large refund is year-one cash, not a recurring saving. Carrying it into year two and three invents money that never returns Book one-time credits once, in the period they post. Only recurring rate and inventory changes carry forward
Fictional baselines Claiming a percentage saved against a list price you never actually paid Baseline against the contracted or previously billed rate on the same service ID
Double-counting a disconnect Claiming the refund for past overbilling and also claiming ongoing avoidance on the same dead service Count the credit as hard savings once, then count the stopped recurring charge as a recurring reduction, never both, and never a third time as avoidance
Counting every hypothetical Treating every plan you could theoretically change as avoidance already banked Only count avoidance tied to a real, dated decision that actually happened

The common root is missing evidence. A disciplined line-item telecom audit is what produces the credit memos, rate exhibits, and disconnect confirmations that keep each number anchored to something a carrier or a contract can confirm. Without that evidence, a program is left estimating, and estimates drift upward until the first hard question exposes them.

Evidence Controllers accept

Controllers accept credit memos, rate exhibits tied to service IDs, disconnect confirmations, and GL postings that reconcile cleanly to the savings story you are telling.

Everything else is a claim awaiting proof, and a Controller will treat it that way. The evidence pack behind a defensible savings report is short and specific:

  • Carrier credit memos with case numbers, matched to the BAN and to the invoice that carried the credit.
  • Before and after invoices on the same service ID, comparing like periods, so a rate change is visible rather than asserted.
  • Signed rate exhibits or contract amendments showing the old rate and the new rate.
  • Disconnect confirmations from the carrier, not just the internal disconnect order, since an order raised is not a service removed.
  • GL postings that show the credit or the reduced charge landing in the correct cost center and period.
  • The inventory of record, dated, showing the service removed from what you own.

This is why credible savings reporting is a byproduct of a real invoice auditing service, not a quarter-end spreadsheet exercise. The audit generates the documents. The report only has to organize them and point each one at the line it supports.

A savings ledger finance can re-perform

Keep a ledger carrying BAN, service ID, savings type, monthly impact, start date, and owner, so audit can re-perform each line without a slide deck.

Internal Audit should pick any row, pull evidence, redo the arithmetic, and reach the same number. The Re-Performable Ledger uses these fields:

Field What it holds Why audit needs it
BAN The billing account number the saving sits under Ties the line to a real, billable account
Service ID The specific circuit, line, or service affected Prevents double-counting across overlapping claims
Savings type Hard, negotiated recurring, or avoidance Keeps the three buckets from blending into one total
Monthly and one-time impact Recurring dollars per month, and any one-time credit held separately Stops a one-time refund from being annualized
Baseline reference The contracted or previously billed rate used Kills fictional baselines
Start date and end condition When it began, and what stops it counting A rate reduction stops when the service disconnects or the contract changes
Evidence link and owner The credit memo or exhibit, and the named person accountable Makes the line re-performable and someone answerable for it

How RadiusPoint reports savings from ExpenseLogic work

RadiusPoint ties refund recovery and optimization outcomes to inventory and invoices inside ExpenseLogic, so every reported saving stays traceable when finance reviews it.

ExpenseLogic holds inventory, rate tables, and invoice history together, while RadiusPoint analysts pursue carrier disputes, track credits, and update moves, adds, changes, and disconnects. That combination lets a Controller trace each saving to a BAN and period.

Published client outcomes illustrate the rule, not a guarantee. One Fortune 100 manufacturer recovered $450,000 in first-year telecom refunds and moved to $850,000 in ongoing annual savings. The refund is one-time hard savings; the $850,000 carries forward only while rates remain lower. A client also achieved $120,000 a year through contract rate optimization, a negotiated recurring line. Other reported outcomes include a healthcare provider’s 26% telecom expense reduction and a food service company’s 22% wireless reduction after mobility auditing. Each must be labeled by bucket.

Frequently Asked Questions

These are the questions finance and Internal Audit ask most about a TEM savings report, answered the way a Controller would want them answered.

Should avoidance appear in the same total as hard savings?

No. Show both, labeled separately, and never blend them into one headline number without a footnote that says which part is cash and which part is prevented spend. The moment they merge, the whole figure inherits the credibility of its weakest line.

How long can a rate reduction count?

Count a rate reduction for as long as the service stays active at the new rate. Stop counting it the moment the service disconnects or the contract changes again. A saving on a service that no longer exists is not a saving.

What baseline should we use?

Use the contracted or previously billed rate on the same service ID. Don’t baseline against a market rate or a list price you never actually paid, because that manufactures savings no invoice ever reflected.

Do category benchmarks like typical year-one TEM reductions help?

Only as context, and only with attribution. Organizations implementing telecom expense management often see 15% to 30% first-year reductions, but that’s a Gartner figure about the category in general, not a RadiusPoint guarantee. Present it as background, never as your own projected result.

Who signs the savings report?

Telecom, or the TEM program owner, prepares it. Finance validates the material lines against the evidence. Internal Audit may sample. Shared ownership across those three roles is what makes the number credible, because no single party both produces and blesses it.

The short version for finance

Report hard and negotiated recurring savings as your headline, keep avoidance labeled and footnoted, and hand audit a ledger it can re-perform without you.

That discipline is the difference between a number finance defends and one it discounts. Re-sort last quarter’s report into three buckets. Anything without a BAN, service ID, and carrier evidence belongs in a footnote until supported. That is the work RadiusPoint does through ExpenseLogic.

What ExpenseLogic Tracks That Spreadsheet TEM Cannot

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

A spreadsheet can track what you spent on telecom, but it can’t hold the evidence that proves each charge, records every change, and survives an audit. ExpenseLogic tracks the things a file structurally cannot: MACD ticket history, contract and invoice images, customer service record extracts, dispute packets, and versioned general ledger files, all tied to the billing account number they belong to. That difference is invisible at small scale and decisive the moment a telecom estate grows.

If you’re running telecom expense management in a spreadsheet, you built the right tool for the size you started at. A single owner, a few accounts, one carrier, and a monthly check against last month’s totals is a reasonable system, and for a while it works. The gap doesn’t appear because anyone did the job badly. It appears because the estate outgrew what any file was designed to hold, and the first place it shows up is the evidence you can’t retrieve when someone asks for it.

Key Takeaways

  • A spreadsheet tracks totals well and evidence poorly. It records what you paid, not the proof, history, and documents that justify each charge at audit.
  • Growth breaks the file through concurrency and evidence before it breaks the arithmetic: multiple editors, MACD volume, contract images, dispute packets, and versioned GL files that one spreadsheet can’t hold together.
  • ExpenseLogic keeps inventory, contract, MACD ticket, invoice line, and GL code linked as one record, so every change traces from the asset to the invoice to the general ledger.
  • RadiusPoint isn’t handing you a file to maintain. Its staff work the invoices, disputes, and MACD tickets inside ExpenseLogic on your behalf.

What spreadsheet TEM actually tracks well

Spreadsheets work for small BAN counts and single owners until concurrency and audit evidence outgrow the file. A billing account number (BAN) or two, one carrier, and one person who knows where everything lives is a system a spreadsheet handles cleanly. It records totals, compares this month to last, and splits a handful of cost centers without much friction. The useful question is when you need TEM, tied to change and evidence.

Tracking gaps after first growth spurt

After growth, spreadsheets lose MACD history, contract images, dispute packets, and versioned GL files needed at month-end close. Each gap is a different kind of missing evidence. MACD history, the record of moves, adds, changes, and disconnects, tells you what changed and who approved it, and a spreadsheet overwrites that with every edit. Contract images, including the letter of agency and negotiated terms, live in someone’s inbox rather than beside the charge they govern. A dispute packet, the bundle of invoice image, customer service record, and notes you send a carrier to win a credit, has nowhere to sit. And the general ledger file that finance needs at month-end close exists in five slightly different saved versions, none of them clearly the current one.

The breaking point is usually concurrency, not size. When more than one person needs the record, the single file stops being a source of truth and becomes a set of conflicting copies. Here’s a short checklist for spotting the breaking point:

  • More than one person needs to edit the record in the same week.
  • You manage more than a small handful of BANs, or more than one carrier.
  • MACD activity happens faster than you can log it.
  • Finance asks for the same GL allocation two different ways at close.
  • An auditor, or your own CFO, asks for the invoice image or dispute proof behind a line.
  • You can’t answer “what changed since last month, and who approved it” from the file itself.

If two or more of those are already true, the spreadsheet has passed its concurrency breaking point, and the cost is no longer convenience. It’s the evidence you can’t produce on demand.

Inventory, contract, and ticket history in one record

ExpenseLogic ties inventory to contracts and MACD tickets so every change leaves a trail spreadsheets cannot guarantee. In ExpenseLogic, RadiusPoint’s platform, a service isn’t a row. It’s a linked record that runs from the inventory of the asset, to the contract that sets its rate, to the MACD ticket that last changed it, to the invoice line that bills it, to the GL code that allocates it. That chain is the whole point, because it lets you trace a single charge backward to the change that created it and forward to the budget it lands in.

Link in the record What it answers What a spreadsheet holds instead
Inventory (asset or service) What exists, where, and under whose Employee ID A row that may already be out of date
Contract The rate this asset should bill at A document in someone’s inbox
MACD ticket What changed, when, and who approved it Usually nothing at all
Invoice line What the carrier actually billed The number you keyed by hand
GL code Where the cost is allocated A formula that breaks on edit

Because every link is stored together, ExpenseLogic can answer a question a spreadsheet can only guess at: is this charge valid, given the contract, the inventory, and the last approved change? RadiusPoint uses that same chain to catch a rate that reverted at renewal, a circuit that kept billing after a disconnect ticket, and a line still assigned to an employee who left, because each of those shows up as a break between two links that should agree.

Audit evidence and document recall

Line-item audit needs invoice images, CSR extracts, and dispute notes retrievable by BAN and period. A real audit doesn’t compare totals. It compares each line to the contracted rate and to the customer service record (CSR) extract that shows what the carrier has on file, and when it finds a discrepancy, it assembles the invoice image and the dispute note into a packet the carrier will act on. All of that has to be recallable by billing account number and billing period, months later, when the credit is still working its way through. A spreadsheet stores the number and throws away the proof. ExpenseLogic stores the proof, which is what makes line-item invoice auditing repeatable rather than heroic.

One RadiusPoint client had been paying roughly $18,000 a year for toll-free numbers that no longer routed anywhere. The charge repeated on the invoice for years, so a month-to-month spreadsheet never questioned it. Recovering it took retrieving the invoice image and the inventory record together and asking whether those numbers still did anything. They didn’t, and the only reason anyone could prove it was that the documents were still there to pull.

How RadiusPoint uses ExpenseLogic beyond a tool licence

RadiusPoint staff work invoices, disputes, and tickets inside ExpenseLogic. That’s the difference between buying a platform and buying an outcome. RadiusPoint does that work for you inside ExpenseLogic: validating every line against the contract, filing and tracking disputes until the credit posts, processing MACD tickets, and reconciling wireless serial numbers and Employee IDs against the HR roster so departed employees stop billing.

The results come from the work, not the file. A Fortune 100 manufacturer recovered $450,000 in telecom refunds in its first year with RadiusPoint and roughly $850,000 in ongoing annual savings while managing more than 10,000 wireless devices, and inventory reconciliation on another engagement recovered $174,000 in re-credits. The same record structure carries into utility expense management (UEM, meaning Utility Expense Management), where one multi-location client recovered about $18,000 a year from utilities still billing at closed locations. Whether you’re standing up a new program or moving off a file, the starting point is the same: getting the onboarding data into a record that finally links the pieces.

Frequently Asked Questions

ExpenseLogic answers the tracking questions spreadsheet teams face when history, evidence, and concurrent ownership outgrow one file.

Can I just export from ExpenseLogic to Excel?

Yes. ExpenseLogic exports to Excel, CSV, and PDF whenever you need it, so nobody is trapping your data. The distinction is that an export is a snapshot, while the live record keeps the history, the images, and the links between inventory, contract, MACD ticket, invoice line, and GL code. You can take the numbers to a spreadsheet anytime. What you can’t take is the evidence chain that made those numbers defensible.

When is a spreadsheet actually sufficient?

When the estate is small, stable, and owned by one person: a few BANs, one or two carriers, and little monthly MACD activity. If you can answer what changed and who approved it straight from the file, and no one is asking for invoice images or dispute proof, you’re below the concurrency breaking point and a spreadsheet is a fair tool. The moment two or more of the checklist signals above are true, that stops being the case.

Does this cover utilities and UEM meters?

Yes. ExpenseLogic tracks utility expense management alongside telecom and wireless, including meter-level detail, tariff and rate data, and billing at closed or vacant locations. Because utilities sit in the same record structure as telecom, one reconciliation and one general ledger process cover voice, data, wireless, and facility invoices instead of three separate spreadsheets that never quite agree.

Can it track wireless serial numbers and Employee ID?

Yes. ExpenseLogic stores device detail at the serial-number level and reconciles each line to an Employee ID and the HR roster. That link is exactly where ex-employee lines and zero-use devices surface, because the platform can compare who a line is assigned to against who still works there. A spreadsheet has no reliable connection to HR, which is why those lines keep billing.

If we switch, do we lose our inventory history?

No. Preserving the inventory of record is the whole objective of onboarding, and RadiusPoint rebuilds it from carrier orders, CSRs, and your existing file rather than starting from a blank sheet. If you’re weighing a move, the mechanics of switching TEM without losing your inventory are worth reading before you commit, because a clean transfer is what protects the history you already paid to build.

See what your spreadsheet can’t show you

Every month the evidence stays uncaptured, a dispute window closes on a credit you could have won and a change goes into the estate with no record of who made it. The fix isn’t a better template. It’s a record that links inventory to contract to MACD to invoice line to GL, and a team that works that record for you. Ask RadiusPoint to audit one month of your invoices in ExpenseLogic, and see in specific dollars, with the images to prove it, what your spreadsheet has been unable to track.

Multi-Carrier TEM: Reconciling AT&T, Verizon, and Regional BANs in One Estate

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

Multi-carrier TEM works when AT&T, Verizon, and regional carrier BANs share one inventory schema, one audit ruleset, and one GL coding model inside a single estate. The moment each carrier keeps its own spreadsheet language, reconciliation stops being analysis and turns into translation, and the errors that matter start hiding in the gaps between files.

Picture a mid-market company that just acquired a competitor with three sites in another state. Overnight it inherited a regional carrier it had never billed against, a fresh set of billing account numbers, and an accounts payable team now approving invoices in two formats it only half understands. Nothing breaks on day one. The break comes a quarter later, when a disconnected circuit keeps billing and nobody catches it, because that carrier’s invoice lives in its own file and answers to no one. The multi-carrier problem is a data problem before it is a cost problem, and RadiusPoint treats it as one by starting with the billing account number rather than the invoice total.

Key Takeaways

  • National and regional carriers differ in customer service record formats and charge codes, so your inventory schema has to normalize them before any spend comparison means anything.
  • BAN-level ownership prevents orphan regional accounts from surviving quietly after an acquisition or a local site build.
  • One estate means one exception queue and one close file, not three carrier-specific closes that never agree with each other.
  • RadiusPoint loads multi-carrier BANs into ExpenseLogic so analysts audit different invoice languages against one inventory of record.

Why Multi-Carrier Estates Break First at the BAN Layer

Multi-carrier programs break when each carrier’s BAN set lives in a separate file with no shared owner, status, or cost-center map. A BAN, the billing account number a carrier uses to group services under one bill, is the unit everything else hangs from, and once you hold BANs from several carriers, the weakest link is never the biggest bill. It is the small account no analyst was assigned to watch.

The failure mode is predictable. National carriers get attention because their invoices are large and their portals are familiar. Regional carriers arrive through acquisitions, local builds, or a single site only one provider serves, and they slot into a spreadsheet as an afterthought. That spreadsheet has no concept of status, so a circuit that should have been disconnected keeps paying. It has no owner, so no one is accountable when a charge drifts, and no cost-center default, so finance codes it to a catch-all where the variance disappears into overhead.

This is the complexity threshold where a managed telecom expense management program earns its keep. A single carrier can be run out of a well-kept spreadsheet by a diligent person. Three to seven carriers, each with its own billing format and dispute path, cannot, because the human effort scales faster than the savings. The estate does not need more spreadsheets. It needs one schema every carrier’s data is forced to enter.

Normalize National and Regional Invoice Languages

Normalize product codes, tax lines, and service ID formats from AT&T, Verizon, and regional carriers into one ExpenseLogic schema before you compare spend. Carriers do not describe the same service the same way. One labels a charge as network access, another buries it in a bundled feature code, a third splits it across two line items with a surcharge attached. Compare those raw invoices and you are comparing vocabularies, not costs.

Normalization is a ladder, and each rung turns raw billing into something you can audit. No charge reaches your general ledger, the finance system’s chart of accounts, until it has passed every rung.

Rung Layer What happens Output you can trust
1 Raw invoice Charges arrive in the carrier’s own product codes, tax labels, and service IDs by EDI, portal, or paper Source data only, nothing comparable yet
2 Charge taxonomy Each carrier’s line items map to a shared set of categories: access, usage, features, taxes, surcharges, and one-time charges Like-for-like charge types across every carrier
3 Inventory key Every recurring charge ties to a specific circuit, line, or service in the inventory of record Charges with no matching asset surface immediately
4 GL code The normalized, inventoried charge carries a default cost center and a general ledger code One close file that posts cleanly

Only after the ladder is climbed does a line-item telecom audit become possible across carriers, because the audit ruleset now reads one taxonomy instead of five. A rate reversion on a Verizon circuit and one on a regional carrier’s circuit look identical to the ruleset, which is the point. Regional carriers are not worse billers than the nationals. They simply speak a different dialect, and normalization translates it rather than penalizing it.

An Ownership Model for Every BAN in the Estate

Assign a business owner, a telecom owner, and a cost-center default to every BAN so regional accounts cannot bill without an accountable party. Ownership is the control spreadsheets never enforce and the one that quietly saves the most, because an owned account gets questioned and an orphan account gets paid.

The grid below is the artifact that makes this real. Every BAN gets a row, and every row names the same five facts. When a new carrier arrives through an acquisition, it does not go live in ExpenseLogic until its rows are complete.

BAN Carrier Business owner Telecom owner Default cost center Status
8017-XXXX AT&T Regional Ops Director Analyst A 6120 East Active
2245-XXXX Verizon Facilities Manager Analyst A 6120 West Active
5590-XXXX Windstream Site Lead, Plant 3 Analyst B 6135 Plant Under review
3302-XXXX TDS Telecom Unassigned Unassigned Default Orphan, flag

That last row is why the grid exists. An orphan BAN is not a rare event in a multi-carrier estate; it is the default outcome of acquisition-driven growth unless something forces assignment. Building this census is the first onboarding artifact any serious TEM program should demand, and it should be complete across all carriers before a single invoice is loaded.

A BAN is owned when three roles are named: a business owner accountable for the spend, a telecom owner accountable for the service, and a default cost center for coding. A BAN missing any of the three is an orphan account, and orphan accounts are where regional overbilling lives longest.

One Exception Queue Across Carriers

Run one exception queue ranked by dollars and age so a small regional BAN error does not hide behind national carrier noise. The instinct in a multi-carrier estate is to work each carrier separately, because each has its own portal and dispute process. That instinct is what lets the expensive errors slip, because it ranks work by carrier rather than by impact.

A single queue changes the ordering. Every exception the audit ruleset raises, whatever carrier produced it, lands in the same list, sorted by dollars at stake and how long it has been open. Age matters as much as size, because carrier dispute windows are finite and a correct finding raised too late is unrecoverable no matter how correct it is.

The design has three practical effects. It surfaces a large regional error above a trivial national one, because it ranks money rather than brand. It keeps aging disputes visible so nothing ages past its recovery window. And it gives one analyst a single place to work, so the estate closes from one queue rather than three carrier-specific lists that never agree.

How RadiusPoint Reconciles Multi-Carrier BANs in ExpenseLogic

RadiusPoint consolidates carrier feeds into ExpenseLogic, reconciles BANs to inventory, and produces one audited path to payment and GL posting. The platform holds the schema, the ownership grid, and the exception queue described above, and named people work them. That combination of software and a human on the account is the part a spreadsheet cannot copy.

In practice, ExpenseLogic ingests each carrier’s billing, applies the normalization ladder so AT&T, Verizon, and every regional carrier land in one taxonomy, and matches recurring charges against the inventory of record. Charges that do not match an owned asset become exceptions. A RadiusPoint analyst works that one queue, files disputes through the correct carrier path, tracks each to a credit, and only then releases charges to payment and general ledger posting. The estate closes once, in one file, with one set of cost centers.

This model matters most during change, when multi-carrier estates are most fragile. Acquisitions add carriers and BANs faster than internal teams can absorb them, and a provider transition can quietly lose the inventory that took years to build. The safe path is consolidating carriers without losing your inventory of record, so the BAN census, the ownership grid, and the audit history survive the move. One estate, one schema, one audited path to payment, no matter how many carriers the business collects.

Frequently Asked Questions

Do we need a separate TEM instance per carrier?

No. A separate instance per carrier recreates the spreadsheet problem inside software, because you end up with several systems of record that still have to be reconciled by hand. The value of TEM comes from one estate holding every carrier’s BANs against one inventory, one taxonomy, and one queue. Separate instances just give you separate closes.

How should regional carriers be prioritized?

By spend, site criticality, and invoice complexity, not brand familiarity alone. It is tempting to prioritize the nationals because their names are familiar and their bills are large, but a regional carrier serving a critical plant, or one with a genuinely tangled invoice, often carries more recoverable error per dollar. Rank carriers the way you rank exceptions: by impact.

What about wireless sub-accounts under national carriers?

Treat wireless master accounts and their sub-accounts with the same BAN discipline you apply to fixed services. A master account often hides dozens of sub-accounts, each capable of billing for lines assigned to people who left months ago. Give the master and its sub-accounts owners, statuses, and cost-center defaults like any other BAN. Wireless and fixed spend have their own differences, but the ownership rule does not change.

Can carriers be compared on unit cost easily?

Only after normalization. Raw invoice PDFs are documents, not comparable analytics, so any unit-cost comparison drawn straight from them compares two vocabularies and calls the result a number. Once every carrier’s charges pass the ladder into a shared taxonomy tied to inventory, unit cost becomes a fair comparison. Before that, it is a guess wearing a decimal point.

How TEM and Accounts Payable Automation Should Split the Work

Uncategorized0

Sharon Watkins, Founder and CEO, RadiusPoint

A finance team automates accounts payable, watches invoice processing get faster and cleaner, and assumes telecom spend is now under control. Then an audit finds a circuit still billing for a site that closed two years ago, a rate that reverted at renewal, and a mobile line for someone who left last spring. The AP system did nothing wrong. It processed, coded, and paid exactly what it was designed to process, code, and pay. It just had no way to ask whether those charges should have been on the invoice at all.

Here’s the verdict up front. Keep accounts payable automation for invoice logistics, keep telecom expense management for telecom truth and audit, and integrate the two at the general ledger handoff. AP automation owns capture, routing, coding, and payment. Telecom expense management owns the service inventory, the contract rate audit, line-item validation, and carrier disputes. They aren’t rivals. They’re two halves of one workflow. RadiusPoint runs the telecom expense management half through ExpenseLogic, its proprietary cloud platform, and hands your AP system a coded, audited file it can post without rework.

Key Takeaways

  • AP automation is a logistics engine for invoices you’ve already decided to pay. It doesn’t decide whether a charge is correct.
  • Telecom expense management supplies the two things AP automation lacks: an inventory of what should exist, and a contract rate to check each line against.
  • Three-way match can’t guard telecom spend, because recurring services generate no purchase order and no receipt to match the invoice against.
  • A clean RACI keeps ownership from blurring, so the TEM provider audits, telecom owns service truth, AP pays, and finance stays informed.
  • RadiusPoint and ExpenseLogic don’t replace your AP stack. They feed it a validated file through a fixed handoff contract.

What AP Automation Does Well for Telecom Invoices

AP automation does the logistics well: it captures telecom invoices, extracts the data, routes them for approval, posts the coding, and pays the carrier. That’s real work, and doing it by hand is slow, error-prone, and expensive. A modern AP platform reads a bill, suggests a general ledger code from vendor history, moves it to the right approver, and releases payment before a late fee lands. For a category with hundreds of monthly invoices from dozens of carriers, that automation is genuinely worth having.

The important thing is to be honest about the boundary of that value. AP automation makes a decided invoice move faster. It doesn’t decide whether the invoice was right. It has no inventory of your circuits, no copy of your carrier contracts, and no mechanism to file a dispute. It trusts the bill and processes it. For most vendor categories that trust is reasonable, because a purchase order and a receipt already vouched for the charge. Telecom is the category where that vouching never happened, which is where the second half of the workflow has to begin.

What Only TEM Can Do

Only telecom expense management builds the service inventory, audits each line against the contracted rate, and disputes wrong charges with the carrier until credits post. This is a different discipline with different reference data. Instead of a purchase order and a receipt, it validates every charge against what services should exist and what those services should cost.

Building and holding that reference data is the hard part, and it’s the reason TEM is a standing function rather than a one-time cleanup. Somebody has to pull carrier service records, reconcile them against invoices and site lists, and then keep the inventory current through every move, add, change, and disconnect. Somebody has to keep the rate table matched to signed contracts as they renew. Somebody has to open a dispute when a charge fails, follow it through the carrier’s process, and confirm the credit actually arrives. None of that is an AP task, and none of it happens by itself. Our guide to when you need TEM walks through the signals that this work has outgrown a spreadsheet and a diligent analyst.

Why Three-Way Match Is Not Enough for TEM

Three-way match needs a purchase order and a receipt to compare against, and recurring telecom services produce neither, so the check has nothing to verify. A monthly carrier bill has no discrete order event and nothing to receive at a dock. The control was built for procured goods, and telecom isn’t procured goods.

Organizations work around this in ways that all leak. A blanket purchase order for annual spend only catches invoices above the blanket, which means it misses almost everything, since nearly every error lives inside the blanket. Two-way match compares a total to an order value and never sees a rate that reverted to list price. Variance monitoring flags a sudden jump, but a ghost charge that has billed steadily for a year reads as the baseline, and nobody questions the baseline. A wrong charge that repeats every month looks identical to a right one under any matching rule. The deeper explanation of invoice audit against three-way match covers why the reference data, not the matching logic, is the thing that fails.

Three-way match asks whether the invoice agrees with the paperwork. A line-item audit asks whether the paperwork was ever right.

A Clean RACI for AP, Telecom, and the TEM Provider

A clean RACI assigns the work so nobody double-owns it: the TEM provider audits, telecom approves service truth, AP processes payment, and finance stays informed. When ownership blurs, charges fall between IT, procurement, and finance, and the reconciliation nobody owns is exactly where the leakage lives. Naming a single accountable role for each task closes that gap.

Task TEM provider (RadiusPoint) Telecom / IT Accounts payable Finance / Controller
Maintain the service inventory R A I I
Audit each line against contract R C I A
File and pursue carrier disputes R / A C I I
Code and allocate to the GL R C C A
Route the invoice for approval I C R A
Execute payment or bill pay C I R A
Own the vendor master data C C R A

Read down the first column and the pattern is clear. The TEM provider is responsible for everything upstream of payment, which is truth, audit, and disputes. AP is responsible for everything from approval onward, which is logistics. Finance stays accountable for the numbers landing correctly, and telecom stays accountable for whether a service should exist in the first place. No task has two owners.

How RadiusPoint Hands Work to AP Through ExpenseLogic

RadiusPoint runs the audit inside ExpenseLogic, its proprietary cloud platform, then hands accounts payable a coded file your AP system can post without rework. ExpenseLogic holds the inventory of record and the contract rate table, tests every invoice line against both, and routes failures to RadiusPoint analysts who file disputes with carriers and utility providers. Charges that pass are allocated to cost center, location, and general ledger account, then delivered into your ERP and AP systems. This is additive, not a rip and replace. Your AP automation keeps capturing, routing, and paying, and our invoice auditing services make sure what reaches it is already correct.

The Handoff Contract

The handoff works because both sides agree on a fixed data contract for every line that crosses it. Four fields carry the meaning, and the AP system only ever sees charges that have already cleared the audit.

Field What it carries
BAN The billing account number that ties the charge back to the carrier account and to the matching inventory record.
Coded amount The audited, approved figure with its full general ledger and cost-center allocation already applied, ready to post.
Exception flag A marker showing whether the line passed clean or is being held pending a dispute, so AP never pays a contested charge.
Period The service month the charge belongs to, so it posts to the correct accrual and lands in the right close.

Agreeing on those four fields is usually the first integration worth building, and the cleaner your TEM onboarding data is, the faster the file starts flowing. Once the contract holds, the verdict takes care of itself: AP automation runs the logistics, telecom expense management runs the truth and the audit, and the two meet at one coded handoff into the ledger.

Frequently Asked Questions

What is accounts payable automation?

Accounts payable automation is software that handles the manual steps of paying supplier invoices: capturing each bill, extracting its data, routing it for approval, coding it to the general ledger and scheduling payment. Telecom and utility bills are an obvious fit, since they arrive every month from each carrier and utility in its own format. The catch is that the software moves an invoice through your process. It doesn’t decide whether the charges are right.

What can’t AP automation check on a telecom or utility invoice?

AP automation can’t check a telecom or utility charge against anything outside the invoice and your approval rules, because it holds no service inventory, contract rates or tariffs. It’ll flag a duplicate invoice or missing approval but won’t spot a meter on the wrong tariff, repeated estimated reads, a line billing at a closed site or a rate above contract. So it can’t replace telecom expense management: skip the line-item audit and AP just pays wrong bills faster.

How do you automate the accounts payable process for utility bills?

You automate accounts payable for utility bills by centralizing intake, auditing each meter’s charges against its tariff and usage history, and sending AP a coded file to post, so automation isn’t limited to faster approvals. It’s the same split as telecom, since utility bills also arrive with no purchase order or receipt to check against. In Utility Expense Management (UEM), RadiusPoint handles invoice receipt and validation, meter-level audit and cost allocation in ExpenseLogic, with line-item detail on every charge.

Who owns disputes and vendor master data?

Disputes live with the TEM provider, while accounts payable owns the vendor master as the system of record for who gets paid. RadiusPoint opens each dispute, works it through the carrier’s process and confirms the credit posts, and the exception flag keeps the disputed line out of the payment run until it resolves. The TEM provider consults on the vendor master, mapping carrier billing accounts to the right vendor records, which stops duplicate vendors and misrouted payments.

Should TEM pay carriers directly?

It doesn’t have to, because either payment model works as long as the RACI names one owner for payment. RadiusPoint can pay vendor invoices for clients once the client funds the account. Many clients keep payment in their own AP system and use RadiusPoint only for audit, coding, and disputes.

What is the first integration to build?

Build the coded handoff file first, agreed on the four fields above: BAN, coded amount, exception flag, and period. It’s the smallest change that delivers the whole benefit, because it lets audited charges flow straight into AP. Deeper ERP feeds and inventory syncs can follow once that file is reliable.

Utility Meter Inventory: The UEM Parallel to a Telecom Service ID File

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

A utility meter inventory is the UEM parallel to a telecom service ID file because both are the authoritative list of every billable identifier an organization pays for, and both are the level where a real audit actually happens. In Telecom Expense Management (TEM), an auditor works from the service ID, the unique number tied to a single line, circuit, or trunk. In Utility Expense Management (UEM), the equivalent unit is the meter. Audit the meters and you’re doing expense management. Pay the account totals and you’re only doing bill pay.

Here’s the thesis in one line: UEM audits at the meter level the way TEM audits at the service ID level, and without a meter inventory of record, utility bill pay is payment, not expense management. That gap has a price. When a site closes or a unit goes vacant and its meter never leaves your inventory, the invoice keeps arriving and finance keeps paying it. At RadiusPoint we run UEM on ExpenseLogic right beside TEM, on one platform, so the same discipline that catches a ghost phone line also catches a meter that should have gone dark months ago.

Key takeaways

  • A utility meter is the UEM equivalent of a telecom service ID, the smallest unit a real audit can work from.
  • Bill pay without a meter inventory is payment only. Meter-level auditing is what turns it into expense management.
  • A meter inventory of record needs six fields at minimum: meter ID, commodity, site, tariff class, status, and cost centre.
  • Closed and vacant sites are where a missing meter costs the most, because nobody’s watching an invoice for a location nobody visits.

UEM versus paying the utility bill

Utility Expense Management is the practice of validating utility charges at the meter level, and it’s a fundamentally different job from paying the utility bill. Bill pay is a three-step loop: receive the invoice, code it, remit the payment. It answers one question, whether the bill got paid on time. UEM answers a harder set. Is this meter on the correct tariff class? Does the consumption make sense for this site? Did a charge cross a threshold that signals an error? Is the cost landing in the right cost centre?

Those questions map to three kinds of audit that only exist once you work at the meter level: a contract and tariff rate audit, a consumption-based audit, and a threshold-based audit. None of them are possible from an account total, because a total hides the meter that’s wrong behind the meters that are right. It’s the same reason a telecom invoice total tells you nothing useful until you break it down by service ID. A program that stops at bill pay is paying accurately and auditing nothing. Knowing when a managed expense program earns its keep starts with recognizing that the audit, not the payment, is where the money is.

Why the meter is the service ID of utilities

The meter is the service ID of utilities because it’s the one identifier that ties a physical point of consumption to a rate, an account, and a cost centre, which is exactly what a telecom service ID does for a line or circuit. Every discipline TEM applies to a service ID has a clean counterpart in UEM at the meter. The unit of consumption changes from minutes and data to kilowatt-hours, therms, CCF, and gallons, but the structure is identical: an identifier, a rate applied to it, a volume measured against it, and a cost centre it belongs to.

Service ID Parallel table
Dimension Telecom (TEM) Utility (UEM)
Core identifier Service ID (line, circuit, or trunk) Meter ID (meter number)
What it identifies A single billable telecom service A single physical point of consumption
Account grouping Billing account number (BAN) Utility account number
Unit of consumption Minutes, data, ports, circuits kWh, therms, CCF, gallons
Rate structure Tariff, rate plan, USOC Tariff class, rate schedule
What the audit checks Contract rate versus billed, zero-use lines, cramming Tariff class fit, consumption anomalies, threshold breaches
Change events Moves, adds, changes, disconnects (MACD) Service start, transfer, close, vacancy
Cost allocation key Cost centre by service ID Cost centre by meter ID
Failure mode when missing Ghost line keeps billing Meter at a dead site keeps billing

The tariff class row is where a lot of recoverable money hides. A meter left on the wrong rate schedule after a site’s usage profile changed can overbill for years without ever triggering a late payment. That’s a meter-level finding, and it’s the utility version of a telecom line stuck on an outdated contract rate. RadiusPoint treats it exactly that way through utility rate reclassification, which is only possible when every meter carries its tariff class in the inventory. You cannot reclassify what you have never recorded.

Building a meter inventory of record

Building a meter inventory of record means creating one authoritative list of every meter, reconciled against actual invoices, so no billable point of consumption exists off the books. The build follows the same path as a telecom inventory. You extract every identifier from the invoices, cross-check it against a physical site list, and resolve the two into a single source of truth. In telecom that source is the service ID file. In utilities it’s the meter inventory. The onboarding work that produces a clean TEM data foundation is the direct model for how a meter inventory gets stood up.

At minimum, every meter record in ExpenseLogic captures these six fields.

Meter Inventory Minimum Spec
Field What it records Why the audit needs it
Meter ID The unique meter or account number the utility bills The primary key every charge and audit ties back to
Commodity Electricity, gas, water, sewer, or waste Sets which consumption logic and units apply
Site The physical location the meter serves Links the meter to a real, verifiable building
Tariff class The rate schedule the meter is billed on Enables the rate and reclassification audit
Status Active, closed, or vacant Flags meters that should no longer be billing
Cost centre The department or entity the cost belongs to Drives accurate allocation and chargeback

Closed and vacant sites where meter inventory pays off

Closed and vacant sites are where a meter inventory pays for itself, because a meter that stays active after a location goes dark keeps billing every month with nobody left to review the invoice. This is the utility twin of the ex-employee wireless line no one disconnects. The location is empty, the service is still on, and the charge flows straight through bill pay because it looks exactly like every legitimate invoice. The status field in the inventory is the only thing that catches it, which is why a meter inventory without a status column simply cannot do this work.

Property management feels this most sharply during tenant transitions. A tenant moves out, never transfers the account, and the utility keeps billing the property owner for a unit generating zero revenue. Recovering those charges is the core of vacant utility cost recovery, and it only works when you can prove which meters map to which vacant units. One multi-location RadiusPoint client recovered about $1,500 a month, roughly $18,000 a year, from utilities that were still billing at locations the company had already closed. That money was recoverable for one reason: the meters were in the inventory, flagged by status, and audited against the site list. Without the inventory, those invoices would still be quietly paid.

One ExpenseLogic estate for TEM and UEM keys

Running TEM and UEM on one ExpenseLogic estate means telecom service IDs and utility meters live in the same system of record, audited by the same team against the same rules. Most vendors split these into separate products, which forces you to maintain two inventories, two audit workflows, and two exception queues that never talk to each other. On ExpenseLogic, the service ID file and the meter inventory are two expressions of one idea, a complete list of every billable identifier, each carrying its rate, its status, and its cost centre.

The verdict

The verdict is simple. If you can’t produce a current list of your meters with their commodity, tariff class, status, and cost centre, you don’t have Utility Expense Management, you have utility bill pay. The meter is the service ID of the utility world, the meter inventory is your service ID file, and the audit that recovers real money can only happen at that level. Build the inventory of record first. Everything else in UEM, from rate reclassification to vacant cost recovery, depends on it.

Frequently asked questions

Does UEM mean Unified Endpoint Management here?

No. In this article UEM means Utility Expense Management, the practice of auditing electricity, gas, water, sewer, and waste charges at the meter level. Unified Endpoint Management is a separate discipline in device and IT security that happens to share the acronym. When RadiusPoint says UEM, it always means the utility spend side of ExpenseLogic.

What is a meter inventory of record?

A meter inventory of record is one authoritative, invoice-reconciled list of every utility meter an organization pays for, with each meter carrying its meter ID, commodity, site, tariff class, status, and cost centre. It’s the utility equivalent of a telecom service ID file.

How does a utility meter compare to a telecom service ID?

A utility meter is the direct counterpart of a telecom service ID, since both are the smallest billable unit and the level at which a genuine audit takes place. A service ID ties a rate and a cost centre to a single line or circuit. A meter ties a tariff class and a cost centre to a single point of consumption.

Why do closed or vacant sites cost so much in utilities?

Closed or vacant sites cost so much because their meters often stay active and keep billing long after anyone stops reviewing the invoice. The charge looks legitimate, so bill pay processes it without question. Only a meter inventory with a status field catches it, which is what makes vacant cost recovery possible

Can TEM and UEM run on the same platform?

Yes. RadiusPoint runs both Telecom Expense Management and Utility Expense Management on ExpenseLogic, so service IDs and meters share one system of record, one audit workflow, and one exceptions queue.

Telecom Contract Notice Windows: Catching Silent Renewals Before They Lock

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

To catch a telecom contract before it silently renews, tie three facts together well ahead of the deadline: the term end date, the notice-by date, and the billing accounts and service IDs the contract actually covers. Auto-renewal clauses roll you into another term, often at reverted rates, unless written non-renewal notice lands inside a window that commonly runs 30 to 90 days before expiration. A renewal alert only prevents the lock-in if it reaches a named owner while there’s still time to act.

Most teams treat a contract renewal as a date on a calendar. It’s more accurate to treat it as the last day you had a choice. Up to that day you can renegotiate, switch carriers, or walk away. One day past the notice-by deadline, the same contract becomes a fact you now pay for, usually for another one to three years, and often at a rate nobody agreed to in a meeting. The clause did exactly what it was written to do. The failure was upstream, in whether anyone was watching the date.

Key Takeaways

  • Notice deadlines commonly fall 30 to 90 days before the term ends, and some carriers push that to 120 or 180 days. The exact number is buried in the clause, not on the pricing page.
  • Contracts kept in email and inventory kept in a spreadsheet are the combination that produces silent renewals. Neither one alerts anybody.
  • Link every notice-by date to the billing account numbers and service IDs it covers, so an alert can say what it protects, not just that something expires.
  • RadiusPoint’s ExpenseLogic holds contract images, expiration dates and obligation alerts against the same inventory it audits every billing cycle.

How Notice Windows and Auto-Renew Clauses Work

A notice window is the fixed period before your term ends when you must tell the carrier, in writing, that you won’t renew. Miss it, and the auto-renewal clause (sometimes called an evergreen clause) does the rest. The contract rolls into a fresh term automatically, and your right to renegotiate closes with the window.

Four parts of the clause decide how much a missed window costs, and they’re worth reading together.

Part of the clause What to check Why it bites
Initial term 12, 36, 60 or 84 months Sets how long you’re committed and when the renewal clock starts ticking
Renewal term Same length, shorter, or a month-to-month rollover Decides how long a missed window locks you in, another year or another three
Notice window Commonly 30 to 90 days before term end The single deadline that actually triggers the lock-in
Renewal pricing Fixed, capped, or “then-current list price” Whether the new term quietly costs more than the one you negotiated

Two of these bite after the fact. If a renewal reverts pricing to list, your monthly recurring charge climbs the moment the new term starts. And if you try to leave once you’re locked in, the early termination fee usually equals the remaining months of the term multiplied by the monthly charge, plus repayment of any promotional credits, waived installation or discounted hardware from the original deal. The window matters more than the exit: leaving is expensive on purpose, not renewing is free if you act in time.

Why Silent Renewals Still Happen in Mature Estates

Large estates miss deadlines not from carelessness but because the people, records and systems that hold the dates keep drifting apart over time. The bigger and older the estate, the more places a renewal date can hide. Four failure modes account for most of it.

  • Owner attrition. The person who signed the contract has left, and the carrier’s renewal reminder still routes to a mailbox nobody reads. The date exists; the reader doesn’t.
  • BAN sprawl. Billing account numbers multiply across carriers, regions and acquisitions until no single list maps contracts to what’s actually billing. You can’t defend a deadline you can’t find.
  • PDF-only storage. The contract lives as a scanned PDF in a shared drive, with the notice-by date trapped inside a clause no system can read, sort or alert on.
  • Missing ETF awareness. Nobody knows what leaving would cost, so even a renewal that’s caught in time gets rubber-stamped rather than challenged.

Every one of these is a records failure, not a judgment failure. The managers involved are perfectly capable of making the call. They just never got a prompt they could act on, attached to information they could trust. That crossover, where manual tracking stops scaling, is when telecom expense management starts to pay for itself.

A Practical Notice-Window Calendar for Telecom and Procurement

A working renewal calendar counts backward from the term end and assigns a named owner an action at each staged deadline before notice closes. The moment you sign, record the term end date and count back from there. Staged alerts turn a single terrifying deadline into a sequence of small tasks. Recording the dates this early also feeds renewals into demand planning and forecasting, so each decision lands inside the budget cycle.

  • 120 days out. Pull the contract, confirm the notice window and the exact delivery method, and start a vendor performance review.
  • 90 days out. Decide: renew, renegotiate or exit. If you’re renegotiating or leaving, get competing quotes now, while the carrier still has a reason to compete.
  • 60 days out. If you’re not renewing, draft and send written notice by the method the clause requires. Don’t wait for the last legal day.
  • 30 days out. Confirm the carrier acknowledged the notice in writing. If it’s silent, escalate before the window shuts.

The calendar only works if each contract carries the same small set of fields. At a minimum, every tracked contract needs five.

  • Term end date. The day the current term expires.
  • Notice-by date. The last day written non-renewal notice can land, counted back from the term end.
  • Owner. One named person accountable for the decision, not a shared inbox.
  • BAN list. The billing account numbers and service IDs the contract covers.
  • Delivery method. Exactly how notice must be sent, whether that’s certified mail, a carrier portal, or a registered address named in the clause.

Inventory Linkage That Makes Alerts Actionable

An alert only helps if it names the billing accounts and service IDs it covers, so you know exactly what a renewal locks in. A reminder that reads “Carrier X master agreement expires” is nearly useless across a real estate. It doesn’t tell you which circuits, sites or lines it governs, so you can’t price the decision. Tie the notice-by date to the BANs and service IDs, and the same alert now shows what’s at stake and what walking away would actually mean.

Inventory linkage also catches the failure that a calendar alone never will. When a negotiated rate expires and the account quietly returns to list price, the renewal date can pass on time and the overbilling still starts. The only thing that catches rate reversion is a line-item comparison of each invoice against the contracted rate table, which is the discipline of a continuous invoice audit rather than a diary entry. That verified inventory is also the difference between switching TEM without losing inventory and starting over blind.

How RadiusPoint Surfaces Obligation Alerts

RadiusPoint stores each contract, its expiration and its notice-by date inside ExpenseLogic, tied to the same inventory its analysts audit every billing cycle. The contract management module holds the contract image, the expiration date and the negotiated rates against service IDs, and it raises obligation alerts covering both termination fees and dates. Those alerts route to a named owner rather than into the void.

Because the platform audits every invoice line against the contracted rate table each cycle, a rate that reverts at renewal gets caught as a billing exception, not just as a date that passed. Software surfaces the alert; a named RadiusPoint analyst works it, files disputes when a rate slips, and pursues credits until they post. In one case, a client recovered $120,000 a year once contract rates were tied to service IDs and audited every cycle, a figure specific to that estate rather than a number to expect. This is what continuous telecom expense management does that a spreadsheet cannot. The questions worth asking any TEM provider start with how they tie contract terms to inventory and who works the alert.

The Verdict

Catching silent renewals is a records problem, not a negotiation problem, and it’s solved before the notice window opens, not after it closes. Every term that renews unwatched is another one to three years at a rate you never tested against the market, plus an early termination fee if you try to leave. The fix costs far less than a single missed window: put every contract’s term end, notice-by date, owner and BAN list in one place, and alert the owner while there’s still room to act. Ask RadiusPoint to inventory your contracts and set the alerts against the services they cover.

Frequently Asked Questions

These are the questions procurement and telecom managers ask most often when they start tracking telecom contract notice windows and non-renewal deadlines seriously.

How do I find the notice window in a telecom contract?

Read the clause, not the pricing page. Look in the general terms and conditions for language like “automatic renewal,” “renewal term” or “automatic extension,” then confirm the exact number of days and the required delivery method.

How should I send a non-renewal notice?

Send it exactly the way the clause specifies, which is often certified mail or a named carrier portal, and treat the send as a task rather than a memory. Record the tracking number, the date, and the carrier’s written acknowledgment. If the clause requires certified mail and you email it instead, the carrier can treat the notice as never given.

Who should own catching renewals, finance or procurement?

Finance sees the spend, but procurement or the telecom team executes the notice, so the owner has to be whoever can actually send it and run the negotiation. A dashboard that finance watches and procurement acts on works only if one named person is accountable for the decision on each contract.

When should I start renegotiating?

Before the notice-by date, not the term end. Once the window closes, you’ve renewed, and your negotiating position is gone for another full term. Starting at 90 to 120 days out gives you time to gather competing quotes while the carrier still competes for your business.

Do wireless contracts need the same notice discipline?

Yes. Wireless agreements carry the same auto-renewal and notice mechanics as wireline, and they change faster because lines and devices turn over constantly. Applying the same term-end, notice-by and owner tracking to managed mobility keeps mobile contracts from renewing on stale line counts nobody reconciled.

Wireline vs Data Circuit Expense Management: Same Platform, Different Keys

Uncategorized0

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:

  1. Billing account number (BAN). The account each service rolls up to, so voice and data on the same account reconcile to the same payable.
  2. 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.
  3. 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.
  4. Cost center. The allocation target, identical in structure across categories, so chargeback and GL coding do not fork by spend type.
  5. 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.

What a Customer Service Record (CSR) Reveals That Your Invoice Hides

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

A Customer Service Record (CSR) is the carrier’s record of what it has provisioned on your account, every service and feature, line by line. A telecom invoice is narrower: the carrier’s demand for payment this period, with that detail compressed into totals. So a real audit starts from the CSR, not the bill, which is why RadiusPoint pulls CSRs into ExpenseLogic and tests each invoice line against what is actually provisioned.

Here’s how it usually surfaces. Someone in finance questions a charge on a telecom bill, a feature that’s been riding the same account for years, and the invoice can’t answer because it never itemized the feature. It rolled the cost into a monthly total and moved on. Pull the CSR, and the feature is right there: provisioned on a specific line, tagged with the order code that put it there and the date it went live. The bill wasn’t hiding it out of malice. It was never built to show you what you’re paying for. The CSR was.

Key Takeaways

  • The CSR is the carrier’s view of what’s provisioned. The invoice is the carrier’s view of what to collect this period. They are not the same document, and they don’t carry the same detail.
  • Features, USOC order codes, hunting arrangements, and directory listings routinely appear on a CSR while the invoice shows only rolled totals.
  • Inactive and pending-disconnect services can sit on a CSR for months and keep generating charges the invoice never flags.
  • RadiusPoint loads CSR detail into ExpenseLogic so analysts can match every invoice line to true provisioned inventory.

Payment document versus provisioning document: what each one is really for

Invoices exist to collect payment for a period. CSRs exist to document how the carrier has provisioned your services and features. That single difference in purpose explains almost everything a CSR reveals.

An invoice is a billing artifact. It’s built to state a balance due and get it paid, so it favors a total over transparency. It summarizes, groups, and reprints last month’s recurring charges without re-explaining them. That isn’t deceptive. It’s just what a payment document does.

A CSR is a provisioning artifact. It records exactly what the carrier has turned on: which lines exist, which features sit on each one, how calls hunt between them, which listings are published, and what status each service is in. It’s written in carrier code, which is why it’s rarely read, but it’s the closest thing to ground truth a carrier will hand you.

Question The invoice answers The CSR answers
What do I owe this period? Yes, that’s its whole purpose No, it isn’t a billing statement
What is actually provisioned on my account? Only in summary, if at all Yes, line by line with order codes
Which features sit on which line? Rarely; usually rolled into a total Yes, feature by feature
Is this service active, pending, or disconnecting? No status detail Yes, through service status flags
Where is the service located? Sometimes a billing address only Service address, listings, and jurisdiction

The invoice tells you what to pay. The CSR tells you what you’re paying for. Auditing the first without the second is checking arithmetic you can’t actually see.

This is why a line-item audit can’t run on invoices alone, and why our overview of invoice auditing services treats the provisioning record, not the bill, as the reference data every charge gets tested against.

The CSR hidden five: detail your invoice quietly compresses into a total

CSRs commonly reveal feature codes, hunting configurations, directory listings, and service status flags that monthly invoices compress into opaque totals. Five categories account for most of what goes unnoticed.

  1. Features and USOC codes. Each feature is provisioned with a Universal Service Order Code (USOC) and billed per line. Voicemail, call forwarding, caller ID, and legacy add-ons can persist for years. The invoice shows a feature total; the CSR shows which features, on which lines, at what rate.
  2. Hunting arrangements. Hunting defines how an unanswered call rolls to the next line in a group. It carries its own charges and routinely outlives the phone system it was built for. Invoices don’t describe hunt groups. CSRs do.
  3. Directory listings. Published, non-published, and additional listings each carry a recurring charge. A company can pay for listings tied to departments or locations that closed long ago, and never see them itemized on a bill.
  4. Service status flags. A CSR records whether a service is active, pending, or disconnecting. That status is the difference between a charge you should pay and one you shouldn’t, and the invoice carries none of it.
  5. Pending and stranded disconnects. A service ordered off but never confirmed off can sit on the CSR in a limbo state, billing every cycle. The bill looks unchanged, which is exactly the problem.

Reading these categories against the bill is the core of what a real audit does, and it’s the reason our telecom audit services reconstruct the CSR before testing a single invoice line.

How a hidden CSR line turns into paid waste

When CSR lines stay active after a site closes or an employee leaves, the invoice keeps charging while accounts payable has no inventory flag telling it to stop. The waste is quiet, and it compounds.

Consider the mechanics. A location shuts down. The lease ends, the staff move, the lights go off. The telephone lines and features provisioned to that address, though, don’t disconnect themselves. Unless someone issues a disconnect order and confirms it posted, those services stay on the CSR, and every charge tied to them keeps flowing onto an invoice that gets approved on its total. Accounts payable pays it because nothing on the bill says the site is gone. Nothing on the bill ever could.

The same pattern hits individual services: a feature nobody uses, a line assigned to a role that no longer exists, a listing for a merged division. Each one is small. Each one recurs. And because the invoice reprints the total rather than re-justifying the line, the charge renews month after month with no natural moment of review. A CSR-driven audit creates that moment on purpose, and when it finds a service that should have stopped billing, the next step is recovering what was already paid. That recovery work is described in our note on telecom refunds and cost avoidance.

How finance and telecom should read a CSR together

Finance should learn which CSR fields drive cost, while telecom owns service status and change activity, so both teams share one interpretation of the same record inside ExpenseLogic.

The two teams read a CSR for different reasons, and both readings matter. Finance cares about the fields that map to money: the billing account number a service rolls up to, the cost center it should be allocated to, the rate each feature carries, and the tax jurisdiction that applies. Telecom cares about the fields that describe reality: which services are active, what’s pending a move, add, change, or disconnect (MACD), and whether the provisioned configuration still matches how the business actually operates.

Neither reading is complete alone. Finance can flag a charge that looks wrong but can’t say whether the underlying service should exist. Telecom knows the service should be gone but doesn’t see it hitting a live cost center every month. Put both readings on the same record, and a stranded line becomes visible from two directions at once. Turning that shared reading into a maintained system, rather than a one-time exercise, is the subject of our guide to building a telecom inventory of record from carrier CSRs.

The short version

If you remember one thing, make it this: the bill is not the inventory. A telecom invoice tells you what a carrier wants paid. A CSR tells you what the carrier has actually provisioned, and the gap between the two is where overcharges live. Start every audit from the CSR, reconcile the invoice to it, and the questions your bill can’t answer suddenly have answers.

How RadiusPoint turns CSR insight into audit action

RadiusPoint compares CSR extracts to invoices and contracts inside ExpenseLogic, then opens disputes or disconnect tickets on anything that shouldn’t be billing. Software finds the mismatch; people resolve it.

RadiusPoint requests CSRs from each carrier under a letter of agency and loads the extracted detail into ExpenseLogic alongside the rate table, the inventory of record, and the invoice history. ExpenseLogic validates every invoice line against the provisioned service, the contracted rate, and the applicable tax treatment each billing cycle. When a charge has no matching CSR line, or a CSR line carries a status it shouldn’t, ExpenseLogic flags the exception and RadiusPoint analysts take it from there, filing disputes with the carrier, pursuing each case until the credit posts, and issuing disconnect orders on services that should have stopped. RadiusPoint updates the inventory of record as moves, adds, changes, and disconnects occur, so the next cycle starts from an accurate baseline rather than repeating the same finding.

The result is one audit trail for finance and one accurate provisioning record for telecom, drawn from the same source. RadiusPoint runs this as a continuous managed service rather than a one-time sweep, which converts the analytical work from money recovered after the fact into error that never reaches an invoice.

Ask RadiusPoint to pull one month of CSRs against your current telecom invoices in ExpenseLogic, and see how many provisioned lines and features on your bill no longer match anything your business still uses.

FAQ

A CSR is the carrier’s provisioning record, and it belongs at the start of any telecom audit, not the invoice alone.

Is a Customer Service Record a free document?

It depends on the carrier. Some deliver a CSR electronically at no charge, others treat it as a special request. Access is a right you can scope through a letter of agency (LOA), so build CSR retrieval into the LOA rather than negotiating it case by case.

How is a CSR different from a bill of materials?

A CSR is the carrier’s record of provisioned telecom services and features. A bill of materials is a manufacturing and project term for the components that make up a product. The language overlaps in equipment or installation contexts, but for recurring telecom service the document you want is the CSR.

Can electronic bills replace CSRs?

No. E-bills improve how the invoice is delivered and formatted, which helps processing, but they don’t add provisioning detail. An e-bill is still a payment document. It won’t show you feature-level configuration or service status the way a CSR does.

How often does a CSR change?

Any move, add, change, or disconnect can change it. Treat a CSR as a snapshot, not a permanent truth: re-pull it after major changes and on a scheduled refresh, so your inventory of record keeps pace with what the carrier has actually provisioned.

Does wireless have a CSR equivalent?

Not by that name. Wireless carriers provide account and line-level detail extracts that serve a similar purpose, with different field names and structure. Treat them as inventory sources for the wireless estate and reconcile them the same way, invoice line against provisioned record.

How Controllers Use a TEM GL Interface File in Month-End Close

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

Controllers use a TEM GL interface file to turn a month of audited telecom charges into one pre-coded batch the ERP can post in minutes, instead of a stack of invoices someone keys by hand. The file is the finished output of telecom expense management (TEM): every charge has already been checked line by line, mapped to a general ledger account, and tagged to a cost centre. By the time it reaches your close, the coding decisions are done and the disputes are flagged. What lands in the ERP is a reviewed subledger feed, not a pile of PDFs.

Key takeaways

  • The GL interface file is the audited product of TEM, not an invoice dump. Each line carries the billing account number, service period, amount, GL account, and cost centre.
  • It belongs early in the close, after the audit finishes and before journals lock, so telecom posts alongside every other subledger.
  • Clean lines flow straight through; exception lines route to an accrual or a hold, so one disputed charge can’t stall the close.
  • RadiusPoint generates the file from ExpenseLogic after line-item audit, so your team posts a reviewed file rather than coding carrier bills.

The short version: an audited, pre-coded GL file lets you post telecom like any other subledger. Clean lines flow through, exceptions get handled on the side, and the work that makes the file trustworthy (the audit and the coding) happens before it ever reaches your ERP.

What’s Actually Inside a TEM GL Interface File

A TEM GL interface file lists every audited telecom charge with its billing account number, service period, amount, GL account, and cost centre for posting.

Start with the fields, because they’re what make the file postable. Each row typically carries the billing account number (BAN), which is the carrier’s account identifier and the anchor for tracing a line back to its source invoice. Alongside it sit the service period the charge covers, the audited amount, the GL account it maps to, and the cost centre or allocation string your organization uses to push spend to the right department, location, or entity.

The file separates into two kinds of rows, and controllers should treat them differently. Clean lines are charges that passed audit and matched contract, plan, and inventory. They’re ready to post with no human touch. Exception lines are charges that failed a check: a rate that doesn’t match the agreement, a service billed after disconnection, a new line nobody ordered, a credit still pending. These don’t get suppressed. They get marked so finance can decide whether to accrue, hold, or post with a note.

Where the GL File Lands in Your Close Calendar

Controllers load the GL file early in the close, after the audit finishes but before journals lock, so telecom posts with other subledgers on time.

Timing is where a good file earns its keep. Telecom is a recurring, high-volume expense that arrives on the vendor’s schedule, not yours, so it has a habit of showing up late and forcing a last-minute manual journal. Placing the feed deliberately fixes that. Below is a Close-Calendar Placement Map most finance teams can adapt to their own cycle.

Close stage What happens with the TEM feed
Before close opens Audit completes on the prior month’s invoices; the GL file is generated and delivered to finance.
Early close Clean lines import and post to the telecom accounts and cost centres; the file is balanced to source invoices.
Mid close Exception lines are reviewed; late or disputed charges are accrued or held with a documented reason.
Before journals lock Telecom subledger ties out; any adjusting entries are booked and the version is archived.
Post close Resolved exceptions and vendor credits carry into the next period’s file.

Handling Accruals and Exception Lines Without a Pile of Manual Journals

Clean lines post straight to the general ledger; exception lines route to an accrual or hold, so the close isn’t blocked by one disputed charge.

This is where the interface and the accrual do different jobs, and it’s worth being precise. The interface file is the posting mechanism for real, audited spend in the period. An accrual is your estimate for spend that belongs to the period but isn’t cleanly billable yet, usually because an invoice is late or a charge is under dispute.

A well-built feed supports both. Clean lines give you the confirmed base. Exception lines give you the accrual candidates, already itemized, so your accrual isn’t a round-number guess. Instead of accruing “telecom, roughly the usual,” you accrue the specific held lines with their amounts and reasons attached. When the dispute resolves or the credit posts, it flows through a later file and the accrual reverses against something concrete.

Balancing matters here too. Before anything posts, the file should tie to the source invoices it was built from, so the total you book reconciles to what carriers actually billed, net of audited adjustments. That reconciliation is what lets you sign the close knowing the telecom line is defensible, not approximated. RadiusPoint’s invoice auditing services are what produce that audited base in the first place, which is why the exception lines are trustworthy rather than arbitrary.

The Controls That Keep the TEM Feed Trustworthy

Feed controls cover versioning, balancing to source invoices, restricted access, and a named coding owner, so the file you post is the file you audited.

A GL feed is only as good as the controls around it, because it writes directly into your books. Use a TEM Feed Control Checklist and run it every period:

  1. Versioning. Every generated file is versioned and archived. If a correction is needed, you produce a new version rather than editing the posted one, and you can always show which file backed which journal.
  2. Balancing. The file totals reconcile to source invoices and to the amounts audited before import. No line posts that can’t be traced to a BAN and a service period.
  3. Access. Only named roles can generate, approve, and import the file. The person who audits isn’t automatically the person who posts.
  4. Coding owner. One owner is accountable for the GL account and cost-centre mapping. When the mapping changes, that owner signs off before the next file uses it.

The mapping itself is set up once and maintained deliberately, not reinvented monthly. Most of that structure gets defined during onboarding, when your chart of accounts and cost-centre logic are captured. If you want to see what that setup involves, RadiusPoint documents the inputs in its TEM onboarding data requirements, and the sequence in its TEM implementation timeline.

How RadiusPoint Produces a GL-Ready File from ExpenseLogic

RadiusPoint produces the file inside ExpenseLogic after line-item audit, mapping each charge to your chart of accounts, so your team posts instead of coding.

Here’s the part that separates a real GL feed from a spreadsheet export. RadiusPoint audits every invoice line first: rate against contract, service against inventory, plan against usage. Only then does ExpenseLogic assemble the audited charges into a file coded to your GL accounts and cost centres. The output is GL-ready because the review and the coding are already finished by the time it’s generated.

ExpenseLogic covers telecom, wireless, and utility expense management (UEM) on one platform, so the same audited-then-coded logic applies across all three categories and lands in a consistent file rather than three different formats. That single unified feed is easier to control and easier to reconcile.

And it’s software plus people, not software alone. The platform builds and balances the file, but a RadiusPoint analyst works the account, resolves disputes with carriers, and confirms the exception lines make sense before the file reaches finance. Automation handles the volume; a named human handles the judgment. That combination is what lets your controller treat telecom as a clean subledger instead of a monthly investigation.

Frequently Asked Questions

Is the GL interface file the same as an accrual?

No. The interface file posts confirmed, audited spend for the period. An accrual estimates spend that belongs to the period but isn’t cleanly billable yet. The file’s exception lines feed the accrual, so your estimate is itemized rather than a round number.

Doesn’t AP automation already do this?

AP automation routes and pays invoices, but it approves recurring telecom charges by default because there’s usually no purchase order or goods receipt to match against. It doesn’t audit the line against contract, plan, or inventory. The TEM feed adds that audit and the GL coding before anything posts.

What happens when our GL structure or cost centres change?

The coding owner updates the mapping and signs off before the next file uses it. Because the mapping lives in ExpenseLogic and is versioned, the change is applied once and carries through every future file, rather than being re-keyed each month.

Who signs off on the cost-centre coding?

A single named coding owner on the finance side is accountable for the GL account and cost-centre mapping. RadiusPoint proposes the mapping from your chart of accounts during onboarding, and your owner approves it, so accountability stays in-house.

How far before close should the file arrive?

Ideally before the close opens, so clean lines post early and exceptions get worked mid-close rather than at the deadline. The earlier the audited file lands, the less telecom shows up as a last-minute manual journal.

The Verdict

A TEM GL interface file is what lets a controller stop treating telecom as a monthly fire drill and start treating it as a subledger. Audited lines, pre-coded to your accounts and cost centres, post like everything else. Exceptions get accrued or held with specifics attached. The file balances to source and stays versioned, so the close is defensible. RadiusPoint builds that file from ExpenseLogic after a real line-item audit, which is the difference between posting numbers you trust and coding invoices you hope are right. If you’re evaluating whether a provider can deliver a genuinely GL-ready feed, the questions to ask a TEM provider are a good place to start.

Telecom Tax and Surcharge Audit: What Belongs on the Bill

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint

Open a telecom invoice and almost every line below the plan rate wears the same official costume: a tax, a fee, or a surcharge with a government-sounding name. The quiet assumption in most accounts payable departments is that all of it is mandatory and none of it can be questioned. That assumption is where the money leaks.

Here is the direct answer. A telecom tax and surcharge audit checks each bill line against statute, tariff, and contract so finance pays only the charges that truly belong. Not every line labeled “tax” or “surcharge” is a statutory obligation. A real audit separates three things carriers print in one indistinguishable block: statutory taxes set by law, carrier surcharges permitted by a tariff or your contract, and discretionary fees a carrier chose to pass through. RadiusPoint runs that separation as a line-item audit inside ExpenseLogic, flagging what does not belong before the payment goes out, not months later in a recovery sweep.

This is audit guidance, not legal or tax advice. Jurisdiction rules differ and change, so the method below is about classification and proof, not a ruling on any specific statute.

Key takeaways

These points sum up how a telecom tax and surcharge audit separates mandatory charges from questionable ones and turns exceptions into recoverable credits for finance.

  • Statutory taxes, permitted surcharges, and discretionary fees are three different classes. Treating them as one “tax” bucket is what hides recoverable errors.
  • Contract language and jurisdiction rules decide what belongs. The label a carrier prints on the line is not proof.
  • A line-item audit in ExpenseLogic lets RadiusPoint analysts challenge miscoded surcharges before the charge posts to the general ledger.
  • Every dispute needs the account number, service ID, charge code, and billing period documented, so a credit can be proven to finance later.

The three charge classes hiding on every telecom invoice

Telecom invoices mix statutory taxes, carrier surcharges allowed by tariff or contract, and discretionary fees, and each class deserves its own audit test. Bundle them into a single “taxes and fees” total and you lose the ability to challenge the one class that is actually challengeable.

Statutory taxes are levied by federal, state, or local government. Federal excise tax, state and local telecom taxes, and E911 or 988 charges that fund emergency systems all sit here. They are set by law, they vary widely by jurisdiction, and a carrier cannot waive them.

Permitted carrier surcharges are cost-recovery line items a tariff or your signed contract authorizes. Some, like the Federal Universal Service Fund pass-through, are tied to a government program yet still applied at the carrier’s discretion in how much they recover and how. That discretion is exactly what makes them auditable.

Discretionary fees are the carrier’s own pricing decisions dressed in regulatory language. “Regulatory cost recovery,” “administrative fee,” and “cost assessment” lines usually fall here. They are not government taxes even though they share the block, and they are the first place a line-item invoice audit earns its keep.

Charge class What it IS What it ISN’T
Statutory tax A levy set by federal, state, or local law and remitted to a government body Not negotiable and not waivable by the carrier
Permitted carrier surcharge A cost-recovery charge a tariff or contract allows for a defined service Not a government tax, even when the name is built to look like one
Discretionary fee A carrier pricing decision passed through to the customer Not mandated and not automatically owed just because it prints on the bill

What “belongs on the bill” actually means

A charge belongs when law or the signed contract authorizes it for that service, jurisdiction, and period, and everything else is an exception worth challenging. “Belongs” is not a feeling about whether a fee looks official. It is a test with a yes or no answer for each line.

The failure mode is treating the invoice label as the authority. A line reading “state regulatory fee” is a claim by the carrier, not evidence the fee applies to your service type in your jurisdiction for the month billed. The proof lives in the statute, the carrier’s filed tariff, and your contract, not in the description field. RadiusPoint validates each line against the inventory of record and the contract inside ExpenseLogic, which turns a vague “that looks high” into a specific, defensible exception during a line-item telecom audit.

The Belongs Test: four questions before you pay

Run every questioned line through four questions. A “no” on any one of them makes the charge an exception to hold and document.

  1. Law: Does a federal, state, or local statute require this charge for this service? If it is a tax, you should be able to name the authority.
  2. Tariff: Is the surcharge in the carrier’s filed tariff at the rate and basis billed?
  3. Contract: Does your signed agreement permit this charge, or does it cap or exclude it?
  4. Service type: Does the charge match the actual service? Wireless, wireline, and data carry different rules, so a fee valid on one can be wrong on another.

How to run a surcharge audit without stalling accounts payable

Sample the high-variance charge codes first, hold only the disputed lines, and keep undisputed taxes moving so month-end close still finishes on time. An audit that freezes the whole invoice to argue over one surcharge creates more damage than the surcharge did.

The workable split is simple. Undisputed statutory taxes and clearly authorized surcharges flow through to payment on schedule. Only the questioned lines get held, ticketed, and worked. That keeps the AP cycle intact while the audit runs in parallel instead of in the critical path.

This is also where automation gets oversold. Three-way match confirms that an invoice ties to a purchase order and a receipt, but telecom tax and surcharge codes rarely map to a PO line, so the match passes them straight through. That gap is the whole reason invoice audit and three-way match are not interchangeable. Pair the PO-level control with a line-item audit that actually reads the tax and surcharge block.

The evidence pack that wins carrier disputes

Winning disputes cite the account number, service ID, invoice period, charge code, and the contract or tariff clause showing the surcharge does not apply. A carrier credits a documented exception far faster than an email that just says a fee looks wrong.

The pattern that wins is boring and repeatable: one exception, one packet, every field a carrier’s billing team needs to verify without a phone call. RadiusPoint files these directly with carriers under a letter of agency and tracks each pending credit in ExpenseLogic until it posts, the same discipline behind documented telecom refund recovery on client accounts.

Evidence Pack Template: the fields finance will accept

  • Billing account number (BAN): the specific account, not just the carrier name.
  • Service ID: the phone number, circuit ID, or meter tied to the charge.
  • Invoice period: the exact billing month and invoice number.
  • Charge code and label: the carrier’s own code plus the line description as printed.
  • Amount and basis: what was billed and how it was calculated, per line or per rate.
  • Authority tested: the statute, tariff section, or contract clause the Belongs Test failed on.
  • Requested correction: the credit sought and the go-forward fix so the error does not reappear next cycle.

Where RadiusPoint fits in the tax and surcharge workflow

RadiusPoint audits every line in ExpenseLogic against inventory and contract so surcharge exceptions surface before payment, not after the books close. The point of a managed telecom tax and surcharge audit is not a one-time refund sweep. It is a monthly control that catches the same miscoded fee the first time it appears.

ExpenseLogic holds the rate table, the inventory of record, and the invoice history in one system, and validates invoice line items against contracted rates, provisioned services, and applicable tax treatment each billing cycle. RadiusPoint analysts work the exceptions, file the disputes, and update the inventory as moves, adds, changes, and disconnects happen, so a corrected surcharge stays corrected. It is the same line-item discipline RadiusPoint applies across telecom, wireless, and Utility Expense Management (UEM), which gives finance one reconciliation process instead of three.

The short version

Not every charge printed as a tax or surcharge is mandatory, so a telecom tax and surcharge audit exists to prove which lines truly belong. A telecom tax and surcharge audit sorts each line into statutory tax, permitted surcharge, or discretionary fee, tests it with four questions, and documents the exceptions so finance pays only what belongs. RadiusPoint runs that audit continuously inside ExpenseLogic, which is how a miscoded fee gets caught before payment instead of after the close.

Frequently asked questions

These are the questions finance and telecom teams ask most often when they start auditing telecom taxes and surcharges against contract and jurisdiction rules.

Are Universal Service and similar fees always legitimate?

Many are statutory or tariff-based, but the amount and whether they apply to your service type still need a line-level check. A fee funding a real government program can still be miscalculated or applied to the wrong service.

Should tax lines go through three-way match?

Three-way match alone rarely validates telecom tax codes, because those lines seldom tie to a purchase order or receipt. Pair it with a TEM line-item audit that reads the tax and surcharge block directly.

Who should approve surcharge write-offs?

Finance owns materiality and the write-off decision, telecom owns the carrier negotiation, and both should be recorded in the dispute ticket so the trail is clear later.

Do wireless and wireline follow the same surcharge rules?

They overlap in name only. Audit wireless and wireline under their own product and contract rules, because a surcharge that is valid on one can be wrong on the other.

Can spreadsheet filters catch bad surcharges?

Filters help you triage a single invoice, but sustained auditing needs charge-code history tied to inventory in a platform like ExpenseLogic. Otherwise the same miscode returns the next month and no one remembers the last dispute.

How to Build a Telecom Inventory of Record From Carrier CSRs

Uncategorized0

By Sharon R. Watkins, Founder and CEO, RadiusPoint

To build a telecom inventory of record, pull the Customer Service Records (CSRs) from each carrier, normalize the service IDs, map every line to a location and a cost center, then load a validated, versioned file into a system that can audit invoices against it. A CSR states what the carrier believes you subscribe to. Your inventory of record is the version your company trusts after that record has been validated, de-duplicated, and reconciled. At RadiusPoint we build that inventory inside ExpenseLogic first, so invoice audit finally has something true to match against.

Most teams build inventory in the wrong direction. They start from the invoice, because the invoice is the thing that shows up every month and demands payment. But an invoice is a summary. It rolls features into bundles, hides disconnected services that never stopped billing, and says nothing about the account that quietly vanished from the file. Reconcile a summary against itself and you confirm the summary. You don’t find the money. The carrier’s own record is where the truth lives, and building from it changes what the whole program can see.

Key Takeaways

  • A Customer Service Record states what the carrier thinks you subscribe to. Your inventory of record is the version your company trusts after validation, de-duplication, and cost-center mapping.
  • Build the inventory from CSRs first, then reconcile invoices to that file. Doing it the other way around just confirms the bill.
  • Every inventory row needs a BAN, a service ID, a location, a cost center, and a contract rate before any audit can run against it.
  • Duplicate and orphaned CSR lines are usually where disconnect savings and refund recovery start.
  • RadiusPoint uses ExpenseLogic plus analyst review so CSR extracts become a maintained inventory, not a one-time spreadsheet dump.

Why Carrier CSRs Beat Invoices as Your Inventory Source

CSRs list the provisioned services and features that the invoice often summarizes away, so inventory should start from the carrier record, not the bill. An invoice is built to be paid, not to be audited. It groups charges, applies bundle pricing, and presents a total that clears accounts payable without ever exposing the line-level detail underneath.

A CSR is drawn from the carrier’s provisioning database. It shows the individual working telephone numbers, circuit IDs, features, and service order codes attached to a billing account number, including the ones the invoice has folded into a package or, worse, kept billing after the service was supposed to end.

Question What the invoice tells you What the CSR tells you
What am I paying? A bundled total per account Every line item, feature, and surcharge separately
What do I actually have? Only what is currently billed Every service provisioned, including recently changed ones
Where is it installed? A billing address, often a headquarters The service location for each line or circuit
Is anything still billing that should be gone? Nothing, the charge just looks normal The service order codes that reveal a disconnect never completed

This is why the inventory you assemble at the start of a program matters more than any dashboard you buy. The data gathered during onboarding becomes the reference every later audit depends on, and if it’s sourced from bills alone, every audit inherits the bill’s blind spots. Start from the carrier record and those blind spots have nowhere to hide.

If your inventory was built from invoices, you have a list of what you’re paying for. You still don’t have a list of what you have.

How to Turn CSRs Into an Inventory of Record: Five Steps

Pull the CSRs by BAN, normalize the service IDs, map locations and cost centers, then freeze a versioned inventory of record for audit. The build follows five steps in order, and the order is the point. Skip normalization and your map is unreliable. Skip validation and you version a file full of the carrier’s own errors.

  1. Pull. Request the full CSR for every billing account number, under a letter of agency, from each carrier in scope. Ask for the official service record, not a billing summary, because carriers will send the shorter document if you let them. A partial pull that covers some BANs but not others produces an inventory with holes you can’t see.
  2. Normalize. Carriers describe the same service in different formats, with different service order codes and different naming. Translate each carrier’s raw record into one consistent schema so a circuit from one carrier and a circuit from another sit in the same column with the same meaning.
  3. Map. Attach every line and circuit to a physical location and an owning cost center. This is where a raw carrier extract becomes something finance can use, because a service with no site and no cost center is a service nobody is accountable for.
  4. Validate. Reconcile the normalized, mapped records against invoices and against whatever internal inventory already exists. Flag every disagreement. Disagreements aren’t noise to be smoothed over, they’re the findings.
  5. Version. Freeze the reconciled file as a dated inventory of record and give it an owner. Every future change gets recorded against this version, so you always know what the inventory looked like when a given audit ran.

How long this takes depends mostly on how scattered the source data is, which is usually the real variable in a first build. Centralized billing shortens it. Invoices spread across accounts payable, IT, and individual site managers lengthen it. Either way, the five steps don’t change, only the effort at step one.

The Seven Fields Every Inventory Row Must Carry

Each inventory row needs a BAN, a service ID, a product code, a site, a cost center, a contract rate, and a status before ExpenseLogic can audit invoices line by line. A row missing any one of these can’t be fully audited, because each field answers a question the audit has to ask.

Field What it answers Why the audit needs it
Billing account number (BAN) Which account is this billed under? Ties the row back to the invoice it should appear on
Service ID Which specific line or circuit is this? The unique key that matches invoice detail to inventory
Product code What kind of service is it? Determines which rate and tax treatment should apply
Site or location Where is it installed? Reveals services at closed or unowned locations
Cost center Who owns the cost? Allocates the charge and gives someone accountability
Contract rate What should it cost? The benchmark every billed charge is tested against
Status Is it active, pending, or disconnected? Catches services still billing after they were meant to end

The contract rate field is the one most inventories omit, and it’s the one that turns a list into an audit. Without a rate to test against, you can confirm that a charge exists, but you can’t say whether it’s correct. It’s also the field that carries forward when you change providers, which is why an inventory built this way stays portable rather than trapped inside one vendor’s tool.

Where CSR-Based Inventory Builds Break Down

CSR builds fail when partial BAN pulls, stale feature codes, or unowned locations leave orphans that keep billing long after the site closed. The failure modes are consistent, and knowing them in advance is most of the defense.

  • Partial BAN pulls. The team requests CSRs for the accounts it knows about and never discovers the accounts it doesn’t. A billing account nobody remembers is exactly the account most likely to be paying for something dead.
  • Stale feature and service order codes. A CSR can carry codes for features and configurations that were changed years ago and never cleaned up. Loaded without interpretation, they inflate the inventory with services that don’t really exist in their billed form.
  • Unowned locations. A line mapped to a site that closed, or to a site no cost center will claim, is an orphan. Orphans are where the money hides, because a charge nobody owns is a charge nobody questions.
  • Format drift between carriers. Two carriers rarely format CSRs the same way. A build that assumes one layout will silently mis-parse the other, dropping or mislabeling rows.

Orphaned and duplicate lines aren’t only a data-quality problem. They’re usually the first dollars a program recovers, and finding them is the front end of telecom refund recovery. In one inventory clean-up, eliminating toll-free numbers that no longer routed anywhere returned $18,000 a year. In another, reconciling the inventory against the carrier’s records recovered $174,000 in re-credits. Those numbers don’t come from renegotiating anything. They come from having a true inventory to compare the bill against.

An orphan is a charge nobody owns. And a charge nobody owns is a charge nobody cancels.

How RadiusPoint Keeps the Inventory True After the First Load

RadiusPoint refreshes the inventory through MACD tickets and recurring CSR pulls inside ExpenseLogic, so the file stays current between audits instead of decaying the moment it’s built. An inventory of record is only true on the day you freeze it. Every move, add, change, and disconnect (the MACD activity that runs constantly in any live estate) starts pulling the file out of alignment with reality.

A one-time build ignores this and is stale within a quarter. RadiusPoint treats the inventory as a living file instead. Every MACD request is ticketed and written back to the inventory as it happens, and periodic CSR pulls re-confirm the carrier’s record against the file we maintain. Because ExpenseLogic holds the inventory, the rate table, and the invoice history in one place, each month’s audit runs against a current inventory rather than a snapshot from onboarding.

That continuity is what separates a managed program from a project. The same inventory that makes the first audit possible is the thing that keeps every later telecom audit honest, because the file the audit tests against was updated the day the service changed, not the day someone remembered to update a spreadsheet.

The Short Version

Build from the carrier’s record, not the bill. Pull every CSR, normalize the service IDs into one schema, map each line to a site and a cost center, validate against invoices, and freeze a versioned inventory with an owner. Give every row a BAN, service ID, product code, site, cost center, contract rate, and status. Then keep it alive with ticketed MACD and recurring CSR pulls. Do that, and the invoice finally has something true to be audited against. Skip it, and you’re auditing the bill against itself.

Frequently Asked Questions

Can we build a telecom inventory from invoices alone?

No, and it’s the most common mistake. Invoices show what you’re being charged, not what you have. They bundle line items, omit disconnected services that are still billing, and carry a billing address rather than a service location. An invoice-only inventory confirms the bill instead of testing it. Use the carrier’s Customer Service Records as the source, then reconcile the invoices to them.

How often should CSRs be refreshed?

Refresh on two triggers. First, on change: any move, add, change, or disconnect should update the inventory as it happens, through a ticket rather than from memory. Second, on a schedule: a periodic full CSR pull, commonly annual or semi-annual, re-confirms the carrier’s record against the file you maintain and catches anything that slipped between tickets. Estates with high turnover or frequent site changes need the scheduled pull more often.

What if two carriers format their CSRs differently?

They will, and that’s what the normalization step is for. Each carrier’s raw record gets translated into one consistent schema, so a circuit from one carrier and a circuit from another land in the same fields with the same meaning. This is exactly where builds that assume a single format break, because a parser tuned to one carrier’s layout will quietly mislabel another’s. Normalizing first is what makes a multi-carrier inventory trustworthy.

Who approves inventory changes?

A named owner, working from a defined approval workflow. Because every row carries a cost center, a change to that row has an accountable owner attached, and MACD activity flows through a ticket that records who requested the change and who approved it. The point of versioning the inventory is that no change is silent. You can always see what changed, when, and on whose authority.

How does this relate to switching TEM providers?

Directly. A properly built inventory of record is portable, which means it’s yours to carry to a new provider rather than something locked inside one vendor’s platform. The BAN, service ID, product code, site, cost center, contract rate, and status fields are provider-neutral. If you’re weighing a change, our guide to switching TEM providers without losing inventory covers how to move the file without losing the accuracy you paid to

What Is a Telecom BAN, and Why Finance Needs It on Every Invoice

Uncategorized0

By Sharon R. Watkins, Founder and CEO of RadiusPoint. Sharon founded the company in 1992 after a career in bank internal audit, and has spent more than three decades building the ExpenseLogic platform and reconciling carrier invoices against the accounts that generate them.

A billing account number, or BAN, is not a reference code you type into a carrier portal. It is the account identity a carrier bills under, and in telecom expense management the BAN is the one key that has to reconcile to three separate records at once: the invoice header, the customer service record from the carrier, and the inventory of services you actually run. When the BAN agrees across all three, your payables are auditable. When it does not, you get ghost payables, which is real money leaving the building against accounts nobody can tie back to a service.

Most finance and telecom teams never look at the BAN directly. They approve an invoice total, code it to a cost center, and pay it. The BAN sits quietly on the invoice header doing the one job nobody audits: deciding which account, and therefore which inventory, a charge belongs to. That works until a carrier migration, a merger, or an acquisition changes the BAN underneath a stream of charges that keeps arriving on the old schedule. Deciding whether to reconcile that yourself or hand it to a provider is a large part of knowing when you need a TEM program.

Key Takeaways

  • The BAN is the account identity a carrier bills under. It sits above service IDs and should reconcile to the invoice header, the customer service record, and the inventory of record.
  • A BAN is not a phone number, a circuit ID, an invoice number, or a remittance ID. Confusing the BAN with any of these is the root of most reconciliation errors.
  • Ghost payables appear when a BAN is truncated on import, remapped after a merger, split across accounts payable vendors, inherited in an acquisition, or paid under a remittance ID that does not match the BAN.
  • One location can hold several active BANs after adds, migrations, and acquisitions, so the inventory has to list every one.
  • Loading each BAN as a controlled key, so every invoice, dispute, and general ledger file points to one account identity, is what keeps payables audit-ready.

How BANs relate to CSRs, invoices, and inventory

The BAN sits at the top of a hierarchy, and every other telecom identifier hangs beneath it. On the customer service record, the CSR the carrier maintains for your account, the BAN is the parent. Under it sit the service IDs: circuit IDs, billing telephone numbers, and mobile numbers, each one a service the carrier has provisioned. Undder each service ID sit the charge lines: the monthly recurring charge, usage, features, taxes, and surcharges. That chain, BAN to service ID to charge line, is the structure a real reconciliation follows.

The invoice header carries the BAN. The inventory of record carries the service IDs. Reconciling the header to the CSR and to the inventory, line by line rather than by sampling, is the core of invoice auditing services, and it is where the account identity has to hold. If the BAN on the invoice does not match a BAN in your inventory, the charge has nowhere to land and the audit stops before it starts.

BAN, service ID, invoice number, remittance ID: four identifiers people conflate

Four numbers travel together on a telecom account, and treating any two of them as interchangeable is how reconciliations break. Each names a different thing and changes on a different schedule.

Identifier What it names Where it appears How often it changes
Billing account number (BAN) The account a carrier bills under Invoice header, customer service record, contract Rarely, until a migration, merger, or acquisition
Service ID (circuit ID, billing telephone number, mobile number) One provisioned service under a BAN Charge lines, inventory of record, CSR detail Whenever a service is added, moved, or disconnected
Invoice number One monthly bill document for a BAN Invoice header only Every billing cycle
Remittance ID The payee identity accounts payable pays to Vendor master, check or ACH file Rarely, and set separately from the BAN

One BAN groups multiple service IDs, so counting BANs tells you how many accounts you have, not how many services. The invoice number is disposable, new every cycle, and useless as a reconciliation key. The remittance ID is the one most likely to drift away from the BAN, because accounts payable sets it up for payment routing without reference to the carrier’s account structure. That gap is where the next section lives.

Common BAN failures that create ghost payables

A ghost payable is a charge that clears every month against an account you can no longer connect to a service. The money is real and the payment posts cleanly, which is exactly why nobody catches it: nothing bounces, nothing errors, the general ledger balances. The BAN is what failed, quietly, upstream. Five failure modes account for most of them, and a line-item telecom audit is built to surface all five.

Failure mode How it happens Why it creates a ghost payable
BAN truncation Leading zeros are dropped or account segments are cut when a BAN is keyed or imported into accounts payable or a spreadsheet Charges post to a malformed account that reconciles to nothing in inventory
Post-merger remapping A carrier merger or platform migration reissues BANs, and for a period both the retired and the new BAN bill The old BAN keeps billing while inventory points only at the new one, so the old stream goes unwatched
Split across accounts payable vendors The same carrier account is set up under two or more vendor records in accounts payable One BAN pays through two remittance identities, so no single view ever reconciles the whole account
Acquisition split BANs inherited through an acquisition are never folded into the inventory of record Inherited accounts bill against an owner nobody tracks, often for years
Remittance versus BAN mismatch The remittance ID accounts payable pays to is set separately from the BAN on the customer service record Payment clears but never ties back to a service, so the charge cannot be audited or disputed

The last two are the most expensive because they hide the longest. After an acquisition, the inherited estate arrives without a clean inventory, and the BANs that came with it bill against no clear owner until someone reconciles them deliberately. A remittance versus BAN mismatch is worse still: the payment side looks healthy, so the mismatch never raises an exception. Both need the same fix, which is a single inventory owner who holds the authoritative list of active BANs and reconciles every remittance back to it.

A ghost payable never bounces. It clears, it balances, and it bills again next month. That is why it survives.

How RadiusPoint and ExpenseLogic keep BANs audit-ready

RadiusPoint loads every BAN into ExpenseLogic as a controlled key, so each invoice, each dispute, and each general ledger file points to one account identity rather than to whatever string happened to be typed that month. Once the BAN is controlled, the hierarchy underneath it becomes testable: every service ID maps to a BAN, every charge line maps to a service ID, and every payment maps back to the BAN it settled. When a carrier reissues a BAN in a migration, the old and new identities are linked in the platform rather than left to drift, so the retired account cannot keep billing unnoticed.

This is where the software-plus-people model matters. The platform holds the controlled keys and the rate table; RadiusPoint analysts do the reconciling work that keeps them true, validating every invoice line item against the inventory of record each billing cycle instead of sampling a few. RadiusPoint captures and validates every BAN, alias, and account number during onboarding and data collection, which is the step that decides whether the rest of the program reconciles or guesses. In one client estate, correcting the inventory of record recovered $174,000 in re-credits that had been sitting behind mismatched accounts.

Every month a BAN stays uncontrolled is another cycle of the same charges posting against an account nobody can audit. Ask RadiusPoint to reconcile one carrier’s BANs against your inventory of record, and you will see how many of your payables point at a service and how many point at a ghost.

Frequently Asked Questions

Is a BAN the same as a phone number or circuit ID?

No. A phone number, a billing telephone number, and a circuit ID are service identifiers that sit under a BAN, and one BAN can hold multiple of them. The BAN names the account; the service IDs name the individual services the carrier has provisioned on that account.

Who owns BAN accuracy, accounts payable or telecom?

Both, on different sides of the same number. Telecom owns inventory truth, meaning which services exist under which BAN. Accounts payable owns payment posting, meaning which BAN a payment settles against. They need the same BAN to agree, which is why a single inventory owner and a shared account list matter more than which department holds them.

What if a carrier uses an account number instead of a BAN?

Treat the account number as the BAN equivalent. Some carriers, particularly wireless and utility providers, label the field differently. Document the alias against the account in ExpenseLogic so the account number, the BAN, and any legacy identifier all resolve to one controlled key rather than three that look unrelated.

Can one location have multiple BANs?

Yes, and it is common. Adds, carrier migrations, and acquisitions all create new BANs for a site that already had one, so a single location can carry several active BANs at once. The inventory of record has to list every active BAN for the location, or charges under the unlisted ones become ghost payables.

Does wireless use BANs too?

Yes. Wireless bills roll up to a master account number that functions as the BAN, with individual mobile numbers as the service IDs beneath it. Map wireless the same way you map wireline: master account number as the controlled key, mobile numbers reconciled against an employee or cost center directory underneath it.

2026 Gartner Press Release

News, Press Release1

RadiusPoint Included as a Representative Vendor in the 2026 Gartner® Market Guide for Telecom Expense Management Services, Global

OVIEDO, FL — September 09, 2026 — RadiusPoint, a provider of telecom and utility expense management services and the proprietary ExpenseLogic platform, has been included as a Representative Vendor in the April 2026 Gartner® Market Guide for Telecom Expense Management Services, Global

The Gartner Market Guide examines the evolving Telecom Expense Management (TEM) market as organizations seek greater visibility and control over recurring technology expenses. The 2026 research highlights continued movement toward automation, AI-driven capabilities, cost optimization, and the management of expenses extending beyond traditional telecom into areas such as cloud, SaaS, and utilities.

RadiusPoint is profiled in the report as a privately owned provider serving organizations across North America and Europe through its ExpenseLogic platform. Gartner notes RadiusPoint’s focus on automation and optimization designed to proactively surface business insights, along with continued development of its AI chatbot and improvements to EDI and OCR capabilities for data capture and reporting.

Through ExpenseLogic, RadiusPoint supports organizations with expense and invoice management processes including invoice processing, inventory management, dispute resolution, payment handling, reporting, and other managed telecom services. The report also identifies healthcare, retail, and logistics among the primary industries RadiusPoint serves

“Being included again as a Representative Vendor in the Gartner Market Guide is meaningful to us because the market continues to move toward greater automation, visibility, and control over complex expenses. We remain focused on helping organizations simplify the way they manage telecom and utility expenses while providing the data and insights they need to make better business decisions.”

RadiusPoint continues to develop ExpenseLogic to help Finance, IT, and Operations teams gain greater visibility into their recurring expenses while reducing manual processes and improving the accuracy of invoice and expense management.

Gartner Reference
Market Guide for Telecom Expense Management Services, Global, Matt Baldino and Katja Ruud, 1 April 2026

Disclaimer: Gartner does not endorse any company, vendor, product, or service depicted in its publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner publications consist of the opinions of Gartner’s business and technology insights organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this publication, including any warranties of merchantability or fitness for a particular purpose.

About RadiusPoint
Established in 1992, RadiusPoint is a prominent provider of services encompassing Telecom Expense Management (TEM), Utility Expense Management (UEM), Wireless Expense Management (WEM), and Mobile Device Management (MDM). Located at its corporate headquarters in Orlando, Florida, RadiusPoint offers a comprehensive range of business and technology solutions, all aimed at enhancing the global business performance of its clients.

What Do You Lose When You Switch TEM Providers?

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 31 August 2026 · 12 min read

When you switch telecom expense management providers you can lose the inventory of record, open disputes, unposted credits, letters of agency, and current customer service records, unless you export them before access ends. A TEM contract ending is not a software logout. RadiusPoint rebuilds a working inventory in ExpenseLogic from those five files plus fresh carrier records, not from a portal you can no longer open.

This page is the switch process.

Key Takeaways

  • The five things that walk out with the old provider are inventory, open disputes, the credit pipeline, letters of agency, and carrier customer service records (CSRs).
  • Inventory work at RadiusPoint has recovered $174,000 in re-credits when the record of services did not match the bill. That file is what you are trying not to lose.
  • A Fortune 100 manufacturer working with RadiusPoint recovered $450,000 in telecom refunds in year one. Unposted disputes of that kind die if nobody owns them during the gap.
  • The Switch-Safe Handoff is four moves: export first, re-request CSRs, reissue letters of agency, then park open credits.
  • Notify the incoming provider and start the export before you tell the outgoing provider the access date.

The Short Version

Export the inventory of record, the dispute register, and the credit log while you still have login rights, then re-request CSRs and reissue letters of agency, before anyone cuts the old portal.

In this article

The five things that walk out with the old provider

The five things that walk out with the old TEM provider are inventory, open disputes, credits, letters of agency, and CSRs. RadiusPoint asks for those five before ExpenseLogic is treated as live. A TEM platform can hold years of tickets you never copied. When the login dies, the tickets die with it.

Recovery is only as durable as the register you carry across the gap. A glass manufacturer working with RadiusPoint saved $100,000-plus in year one. Those dollars started as line items someone could still see.

This is a process page. It does not rank providers. If you need a commercial starting point after the handoff, the telecom expense management service is that page.

What happens to open disputes and credits during a TEM switch?

Open disputes stall, and unposted credits expire, unless a named owner keeps the evidence pack and the carrier ticket number alive through the gap. RadiusPoint parks that register in ExpenseLogic and will not call a credit “saved” until it appears on a later invoice. Identified dollars are not banked dollars. A switch that reports “$400,000 identified” and then drops the follow-up has converted recovery into a story.

A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one, with $850,000 in ongoing annual savings and a $1.3 million year-one impact. That pipeline had an owner. Invoice auditing services find the error. Telecom audit services keep the audit moving. Neither page replaces a dispute register you forgot to export.

Ask the outgoing provider for a list of every open ticket, the amount, the carrier reference, and the last follow-up date. If they cannot produce it, assume the pipeline is already at risk.

How do you keep the inventory of record when you change providers?

You keep the inventory of record by exporting it while you still have rights, then reconciling that file to a fresh CSR. RadiusPoint treats the outgoing export as a hypothesis in ExpenseLogic. The CSR is the carrier’s current picture. The next invoices are the proof. Inventory management at RadiusPoint has recovered $174,000 in re-credits when those pictures disagreed.

An inventory export that lacks service ID, BAN, carrier, contract, location, cost centre, monthly rate, status, last invoice date, and open-ticket reference is a contact list. It is not an inventory of record. RadiusPoint will say which fields are missing rather than load a false baseline.

Multi-vendor support is the live reminder that each carrier is a separate export and a separate CSR request. One “download all” button is rare.

Letters of agency and customer service records have to be reissued

Letters of agency have to be revoked and reissued, and customer service records have to be requested again from each carrier. Customer service records have to be requested again from each carrier. RadiusPoint will not reuse an outgoing provider’s letter, and ExpenseLogic will not treat a six-month-old CSR as current. The grant is personal to the agent. Copying a PDF does not transfer authority.

This is not a second letter-of-agency explainer. It is the switch step: revoke the old grant so two agents are not writing the same carrier, then issue a scoped grant to the incoming team. CSR timing sits on the carrier, not on your preferred go-live date.

If utilities are in scope, Utility Expense Management (UEM, not Unified Endpoint Management) needs the same revoke-and-reissue pattern on utility accounts. RadiusPoint can hold those grants on the same ExpenseLogic instance. They are still different vendors.

The Switch-Safe Handoff

The Switch-Safe Handoff is RadiusPoint’s four-move sequence: export first, re-request CSRs, reissue letters of agency, then park open credits with a named owner. ExpenseLogic is where those four outputs land. Exit blogs in this category say “collect invoices and tell your vendors.” They do not teach a four-move order that delays notice to the outgoing provider until the export is in motion.

Move What you take What fails if you skip it
1 Export first Inventory, dispute register, credit log, contract images The portal closes and the history goes with it
2 Re-request CSRs A current carrier record per vendor You import a stale extract as truth
3 Reissue LOAs Revoke old grant, issue scoped new grant Two agents, or no agent, talk to the carrier
4 Park open credits Owner, amount, ticket ID, last follow-up Identified dollars never post

When should you notify the old provider versus the new one?

Notify the incoming provider first, start the export, then give the outgoing provider a dated access-end notice that still leaves time to pull files. RadiusPoint would rather see a complete pack than an early announcement. A provider who loses the account can still behave professionally. Do not test that by cutting access the same day you send the email.

Read the current contract for notice periods and auto-renewal. That is a calendar fact, not a vendor review. RadiusPoint will work to your notice date. ExpenseLogic still needs the four Switch-Safe outputs inside that window.

If the outgoing team offers a “transition file,” take it, then still re-request CSRs. Their file is their picture. The carrier’s CSR is the picture the next invoice will be billed from.

How RadiusPoint rebuilds a working inventory instead of importing a stale one

RadiusPoint rebuilds the inventory in ExpenseLogic by matching your export to new CSRs and to the next invoices, then opening exceptions where the three disagree. Importing a stale file and calling it go-live is how ghost circuits survive a switch. Analysts file new disputes under the new letter of agency. Old tickets stay in the parked register until they post or are written off with a reason.

The glass manufacturer case is a savings story after the record was usable. HumanGood’s published 315% ROI is a running-program figure. Neither number appears during a messy cutover.

RadiusPoint has done this since January 1992. ISO 9001 certification has been in place since September 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. Sharon Watkins founded the firm after internal-audit work at a bank. A TEM switch is an audit handoff with a cancellation email attached.

FAQ

Can we run two TEM providers at once during the gap?

You can, if letters of agency are scoped so only one agent can order, and both can read bills. RadiusPoint will say which rights it needs. Two agents filing the same dispute is how credits get lost.

What if the old provider will not export inventory?

Start with carrier CSRs and the last 12 months of invoices. RadiusPoint will rebuild from those in ExpenseLogic. The $174,000 re-credit case is what a rebuild can still find. You will spend more calendar time.

Do we need to re-sign every letter of agency?

Yes, or execute a revoke-and-replace that the carrier will accept. A forwarded PDF of the old letter is not a grant to the new agent.

Is this the same as the Day-Zero pack for a first-time TEM buyer?

No. First-time onboarding gathers your internal files. A switch also has to extract files that live inside the outgoing platform and keep the credit pipeline alive. Overlap exists. The risk is different.

What if we are only switching the software and keeping the same people?

You still need the export and the CSR refresh. People remember tickets. Portals do not migrate memory. RadiusPoint will still reconcile the file to the next invoice.

What to do before you give notice

List the five files. Pull the ones you can download today. Call RadiusPoint with that list and the notice date on the current contract. ExpenseLogic can start on a partial export. It cannot start after the portal is already dark.

References

  1. Telecom Expense Management Services | RadiusPoint
  2. Telecom Refunds, Cost Avoidance, Savings | RadiusPoint
  3. Invoice Auditing Services | RadiusPoint
  4. Telecom Audit Services | RadiusPoint
  5. Multi-Vendor Support | RadiusPoint
  6. Glass Manufacturer Saves $100K on Telecom Expenses | RadiusPoint
  7. HumanGood Achieved 315% ROI with RadiusPoint | RadiusPoint
  8. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
  9. ExpenseLogic reviews | Capterra
  10. Sharon R. Watkins | RadiusPoint
  11. ExpenseLogic | RadiusPoint

Disclaimer

This article is general information for teams changing TEM providers. It is not legal advice on contracts, notice periods, or letters of agency. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results or of a cutover duration.

The Data a TEM Provider Needs Before Day One

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 30 August 2026 · 12 min read

A telecom expense management provider needs invoices, contracts, a starter inventory, allocation rules, an employee roster, and site open-and-close dates before the first cycle, and a letter of agency is only one file in that pack. Accounts payable emails three PDFs and calls it kickoff. RadiusPoint cannot build an inventory of record in ExpenseLogic from three PDFs. Day one is the day the pack is complete enough to load, not the day the contract is countersigned.

This page is onboarding-readiness.

Key Takeaways

  • The Day-Zero Data Pack is eight files: scoped letters of agency, invoice history, contracts, starter inventory, GL and allocation rules, HR roster, site dates, and named owners.
  • A letter of agency authorizes carrier conversations. It does not create invoices, rate tables, or an employee list.
  • A food service onboarding at RadiusPoint needed two months for users to register 600-plus lines. Fifty-six of those users were already gone.
  • HumanGood, a named RadiusPoint client, has a published 315% ROI once the program is running. That figure is not a substitute for a complete kickoff pack.
  • Kickoff stalls when IT is asked for every file. AP, procurement, finance, HR, and real estate each own a slice.

The Short Version

Before RadiusPoint can run ExpenseLogic on your accounts, you need a Day-Zero Data Pack: invoices, contracts, a starter inventory, allocation rules, an HR roster, site dates, named owners, and a scoped letter of agency, not the letter alone.

In this article

What a TEM provider can start without, and what it cannot

A TEM provider can start a RadiusPoint kickoff call without a perfect inventory, but it cannot validate invoices without bills. RadiusPoint still needs a rate source and a way to reach the carrier. RadiusPoint will load what you have into ExpenseLogic and mark the gaps. A missing contract exhibit delays rate matching. A missing letter of agency delays portal access. A missing site list delays allocation. Those are different delays.

The telecom expense management service names monthly accrual files and GL interface files as outputs. Outputs require inputs. This page is the input list. The TEM FAQ answers how the platform behaves after load. Do not treat the FAQ as the pack.

You can begin without 36 months of history. You should not begin without at least one full recent cycle per major carrier and the current contract that is supposed to govern it.

Why is a letter of agency not the onboarding file?

A letter of agency authorizes a TEM provider to speak to a named carrier on a scoped set of rights only. It is not the onboarding file. RadiusPoint still needs invoices, contracts, and owners after the letter is signed, and ExpenseLogic will not invent those records from the authorization. Scope the letter. A read-only billing grant is not ordering rights. A blanket grant is a governance problem, which the live TEM pillars already warn against.

This section names the letter so you do not confuse it with the pack. It is not a second letter-of-agency article. If you want the legal mechanics of the grant, that is a different page. If you want to know what to gather this week, stay here.

RadiusPoint will tell you which carrier the letter must name and which rights it must include. You still have to produce the other seven files.

Which invoice, contract, and inventory files should be ready first?

Ready first means 12 months of invoices or portal access, current contracts, and the best inventory you already have on file. RadiusPoint loads those three into ExpenseLogic before it asks for a polished spreadsheet. Invoice audit work cannot start on a carrier you have not shown. Contract images are the rate table. The starter inventory is a hypothesis the bills will test.

A food service client had no wireless procurement policy and no structure for adding users. RadiusPoint stood up a Register Your Line portal and spent two months collecting registrations on 600-plus lines. That timeline is published on the managed mobility case study. The pack was incomplete on purpose. The invoices and the portal still had to exist on day one.

Telecom lifecycle management is the live companion for how services move after kickoff. This question is only about the files that have to exist before that lifecycle has a baseline.

What finance and HR have to contribute before kickoff

Finance has to contribute the chart of accounts, cost-centre list, and allocation rules before RadiusPoint can code ExpenseLogic files. HR has to contribute a current employee roster for wireless matching. RadiusPoint cannot code a GL interface file in ExpenseLogic without the map finance already uses, and it cannot flag a departed user without a roster dated in the same month as the wireless bill. Those two files are why kickoff is not an IT-only request.

The food service case found 56 identified users who were no longer employed. That finding required a roster, not only a carrier extract. HumanGood’s published 315% ROI is a running-program figure. It does not appear until allocation and inventory have something to post against.

If finance plans to copy last month’s bill for the accrual, say so. RadiusPoint will then know the accrual file is part of the pack, not a later enhancement.

The Day-Zero Data Pack

The Day-Zero Data Pack is RadiusPoint’s eight-file list of what has to be present, even if incomplete, before ExpenseLogic can run a first cycle. Implementation guides in this category say “send us your invoices and an LOA.” They do not name an eight-file pack with an owner for each file.

Code File Minimum that unblocks day one
A Scoped letters of agency One per carrier, rights named, revoke path named
B Invoice history or portal access Latest 12 months, or a live feed, for each major vendor
C Contracts and amendments Current rate exhibits, not only the cover page
D Starter inventory Circuits, lines, BANs, and locations you already know
E Finance map Chart of accounts, cost centres, allocation rules
F HR roster Active employees for wireless matching
G Site list Open and closed locations with dates
H Named owners AP, IT, procurement, and an approver

Who inside your company owns each file?

IT or telecom owns the inventory, BANs, circuit IDs, and portal logins that RadiusPoint will load into ExpenseLogic. Accounts payable owns invoice PDFs and the vendor master. Procurement owns contracts. Finance owns the GL map. HR owns the roster. Real estate or facilities owns site dates and, if utilities are in scope, the utility account list. RadiusPoint will send one request list. Your internal owners still have to move the files.

That environment makes file H (named owners) non-negotiable. A single inbox labeled “TEM kickoff” will sit.

Utility Expense Management (UEM, not Unified Endpoint Management) adds meter IDs and tariff sheets to files B, C, and G. RadiusPoint can load those on the same ExpenseLogic instance. They are still different owners inside your company.

How RadiusPoint uses ExpenseLogic once the pack arrives

RadiusPoint loads the pack into ExpenseLogic, builds a baseline inventory from bills plus your starter file, and opens exceptions where the two disagree. Analysts then validate lines, file disputes where authorized, and return an allocation file that matches the finance map you sent. You do not receive a portal with empty tables and a note to “upload more later” as if that were go-live.

RadiusPoint has done this since January 1992. ISO 9001 certification has been in place since September 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. Credentials do not shrink the pack. They tell you the load process is repeatable.

Sharon Watkins founded RadiusPoint after internal-audit work at a bank. Day-zero data is an audit binder. ExpenseLogic is where that binder becomes the inventory of record.

FAQ

Can we start if our inventory spreadsheet is two years old?

Yes, if invoices and contracts are current. RadiusPoint will treat the spreadsheet as a hypothesis in ExpenseLogic and rebuild against the bills. Mark file D as stale so nobody pretends it is the inventory of record.

Do we need portal passwords or only PDFs?

PDFs can start a historical load. Portal or EDI access is what keeps the next cycle arriving without a mailbox chase. RadiusPoint will say which carriers still require a human upload.

What if HR will not release a roster?

Wireless matching will be incomplete. RadiusPoint can still process wireline invoices. File F stays red on the pack until HR sends a dated active list, even if names are limited to employee ID.

Is this the same as the data we send when we switch providers?

No. Switching is a handoff out: export, open disputes, reissued letters, carrier CSRs. This page is a handoff in: the first pack a new provider needs. Overlap exists. The jobs are different.

How complete does file G need to be on day one?

Every location you know is still open or that closed in the last 12 months, with a date. RadiusPoint will catch more from the bills. A blank site list makes every invoice a mystery BAN.

What to do before kickoff

Assign an owner to each of the eight codes this week. Send RadiusPoint the files you have, and label the files you do not. ExpenseLogic can start on a partial pack. It cannot start on a letter of agency and a promise.

References

  1. Telecom Expense Management Services | RadiusPoint
  2. Telecom Expense Management FAQ | RadiusPoint
  3. Invoice Audit | RadiusPoint
  4. Telecom Lifecycle Management | RadiusPoint
  5. Multi-Vendor Support | RadiusPoint
  6. How Managed Mobility Services Cut Costs 22% ($400K in Year 1) | RadiusPoint
  7. HumanGood Achieved 315% ROI with RadiusPoint | RadiusPoint
  8. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
  9. ExpenseLogic reviews | Capterra
  10. Sharon R. Watkins | RadiusPoint
  11. ExpenseLogic | RadiusPoint

Disclaimer

This article is general information for teams preparing a TEM kickoff. It is not legal advice on letters of agency or data-sharing. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results or of a kickoff duration.

Signs Your Company Has Outgrown Managing Telecom In-House

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 29 August 2026 · 12 min read

You need a telecom expense management provider when your team can no longer produce a complete inventory this week, invoices are approved without a line-item check, and contracts renew without a rate review. How many mobile lines does your company pay for right now? Not approximately. Exactly. Most in-house owners cannot answer inside five business days. That gap is the sign. RadiusPoint takes the operational load on ExpenseLogic while you keep the budget.

This page is a readiness self-assessment.

Key Takeaways

  • The first sign you have outgrown in-house TEM is an inventory you cannot finish this week, with a location, a cost centre, and a contract rate on each service.
  • A food service company working with RadiusPoint had 600-plus lines, one overloaded owner, and 56 departed users still billing. Monthly cost fell 22%, more than $400,000 in year one.
  • Amalgam Insights’ IT Rule of 30 states that the average unmanaged IT expense category is wasting 30% in spend, a category claim, not a RadiusPoint promise (EIN Presswire, 2024).
  • Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. Treat that as a category range, not a guarantee.
  • The Outgrown-In-House Scorecard is six operational signs. Three or more yes answers is a staffing problem.

The Short Version

If your team cannot name every circuit, mobile line, and data service this week, you have already outgrown in-house telecom expense management, whether or not you still have a “telecom person.”

In this article

The inventory question your team should answer this week

The inventory question is exact headcount of circuits, mobile lines, and data services, each with a location, a cost centre, and a contract rate. RadiusPoint treats that file as the inventory of record inside ExpenseLogic. A spreadsheet that is 90 days old is a memory. It is not an inventory. The telecom expense management FAQ is where buyers ask how the platform holds that file. This page asks whether you can produce it at all.

A food service company came to RadiusPoint with hundreds of wireless devices and no identification of the employees using them. The managed mobility case study records 600-plus phones billed monthly, 56 users no longer employed, and a 22% monthly-cost cut that the video transcript states as more than $400,000 a year. That is what “we are handling it in-house” looked like with one person who also had other duties.

If you cannot answer the inventory question this week, the rest of the scorecard is already in motion.

What happens when invoices get approved without a line-item check?

Invoices approved without a line-item check become paid vendor claims, including charges for services that no longer exist at all. RadiusPoint audits invoice lines against contracted rates and inventory in ExpenseLogic before the payment run. Rubber-stamp approval is the quiet version of in-house failure. The due date is real. The GL coding is complete. The circuit may have been dead for a year.

RadiusPoint published $18,000 a year recovered by eliminating unneeded toll-free numbers. Inventory work has recovered $174,000 in re-credits when the record of services did not match the bill. A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one. Those dollars sat on invoices someone had already been allowed to pay. Facing five TEM challenges names the operational pressure. This page names the sign: approval without a line check.

Carrier dispute windows are finite. An invoice reviewed 60 days late is often a permanent write-off. That is an in-house capacity problem, not a software preference.

How carrier and location count turns a spreadsheet into a leak

Complexity, not a round spend number, is usually what outgrows a part-time telecom owner that RadiusPoint still sees monthly. RadiusPoint sees the break when a second and third carrier land, then when sites open and close faster than MACD tickets close. One carrier and one site can still fit a careful analyst. Three carriers plus wireless plus utilities will not, if that analyst also owns help desk and hardware refresh.

RadiusPoint published a client that grew from 170 to 1,200 locations. At that scale, a missed disconnect on a thin percentage of sites is not a rounding error. ExpenseLogic holds telecom, wireless, and utility invoices together so the same owner problem does not hide in three spreadsheets. Cutting telecom expenses with TEM is the commercial companion. This section is the complexity test.

An automotive-salvage engagement on the live TEM page generated $1.3 million from inventory and audit after acquisitions consolidated invoices. That is what a location-count jump looks like when nobody rebuilds the record.

What happens when telecom contracts renew without a review?

A telecom contract that auto-renews at the old rate is an unowned calendar RadiusPoint sees every month, not a market decision. RadiusPoint tracks expiration dates and rates against service IDs in ExpenseLogic and raises the date before the notice window closes. In-house teams lose that date because the person who signed the deal left, or because the file lives in a procurement inbox no one opens.

Silent renewal is one of the six scorecard signs. It pairs with departed employees who still have live mobile lines, which is the wireless face of the same ownership gap. The food service case had both: no wireless policy, and users who had been gone more than two years while billing continued. RadiusPoint wrote the policy after the inventory, not before.

What Is Telecom Expense Management? explains the discipline. This page asks whether anyone on your payroll still practices it every month.

The Outgrown-In-House Scorecard

The Outgrown-In-House Scorecard is RadiusPoint’s six-sign test of whether one internal owner can still finish the work each month. ExpenseLogic is where RadiusPoint would take those six jobs if the score is already failed.

Sign Yes looks like What RadiusPoint loads into ExpenseLogic
1 Incomplete inventory No exact service count this week Circuits, lines, BANs, locations, rates
2 Unread approvals AP pays on due date and coding only Line-item match to contract and inventory
3 Carrier and site sprawl Three-plus carriers or a rising site count Multi-vendor invoices on one record
4 Silent renewals A term date nobody calendared Contract IDs and notice windows
5 Ghost mobility Departed staff still have live lines Employee roster versus wireless inventory
6 Accrual from last month’s bill Finance copies the prior invoice Missing-bill and accrual support files

Three or more yes answers is a staffing problem. Buying a dashboard without moving the work does not clear a yes.

Does a dedicated telecom person still mean you can stay in-house?

A dedicated person can keep TEM in-house if they still finish inventory, line checks, and renewals without dropping the accrual. RadiusPoint does not treat a job title as proof of capacity. The food service owner was dedicated to phones and still had other telecom duties. The lines outran the person.

Stay in-house when the scorecard is mostly no, the carrier mix is simple, and finance already trusts the accrual. Move the operational work when three or more signs are yes. This question only tests whether the person you already have can still see the file.

A healthcare provider working with RadiusPoint reduced telecom expenses 26%. A glass manufacturer saved $100,000-plus in year one. Those are program outcomes after the work moved. They are not a rule that every titled telecom manager must outsource.

How RadiusPoint and ExpenseLogic take the operational load

RadiusPoint takes invoice collection, line-item audit, dispute filing, and inventory maintenance onto ExpenseLogic, and leaves budget approval and carrier strategy with you. The telecom expense management service is that model. You still own the yes or no on a disconnect. RadiusPoint owns proving the charge is gone.

Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The same 2024 release cycle is where Amalgam published the IT Rule of 30: the average unmanaged IT expense category is wasting 30% in spend. Use that as a category warning. Do not write it as a RadiusPoint guarantee. Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one, again a category range.

RadiusPoint has done this since January 1992. ISO 9001 certification has been in place since September 2002. The Capterra listing sat at 4.8 from 31 reviews through December 2025. Sharon Watkins founded the firm after internal-audit work at a bank. The outgrown-in-house problem is an audit problem with a headcount attached.

FAQ

Is there a spend number that means we must outsource?

No honest operator can name one number that fits every carrier mix. RadiusPoint starts with the six signs. A simple single-carrier environment can stay in-house at a higher spend than a messy multi-carrier one at a lower spend.

Does a TEM platform without managed service fix a failed scorecard?

Only if you staff the work the platform reports. RadiusPoint’s model is software plus people. A license that leaves disputes and inventory with a team that already failed the scorecard is a reporting layer over the same leak.

What if we only failed the mobility signs?

Start with wireless inventory and the HR roster. The food service case was a mobility failure that sat next to a TEM failure. RadiusPoint can take one expense category first. The scorecard still applies to that category.

Can we run the scorecard on utilities too?

Yes, with Utility Expense Management (UEM, not Unified Endpoint Management) substituted for TEM on the invoice type. RadiusPoint holds both on ExpenseLogic. A closed-site electric bill is the utility face of sign 1 and sign 3.

What to do before the next invoice cycle

Score the six signs this week. If you cannot name the inventory, stop there and call that a yes. Every cycle you skip is another unread approval.

References

  1. Outsourced Telecom Expense Management | RadiusPoint
  2. What Is Telecom Expense Management? | RadiusPoint
  3. Telecom Expense Management Services | RadiusPoint
  4. Telecom Expense Management FAQ | RadiusPoint
  5. How Managed Mobility Services Cut Costs 22% ($400K in Year 1) | RadiusPoint
  6. Facing Five TEM Challenges | RadiusPoint
  7. Cutting Telecom Expenses with TEM | RadiusPoint
  8. Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management | EIN Presswire
  9. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
  10. ExpenseLogic reviews | Capterra
  11. Sharon R. Watkins | RadiusPoint

Disclaimer

This article is general information for finance and IT leaders deciding whether in-house TEM still fits. It is not a staffing or legal recommendation. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies. Category-level ranges, including Amalgam’s IT Rule of 30 and the 15 to 30 percent TEM range, are not RadiusPoint guarantees.

Questions to Ask a TEM Provider Before You Sign

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 28 August 2026 · 12 min read

The questions that belong in a telecom expense management contract are the ones that name a person, a percentage, and a file you will receive if you leave. Most buyers treat the TEM demo as the evaluation. RadiusPoint treats the statement of work as the evaluation. A platform can show you a variance. A managed service has to say who files the dispute, who updates the inventory, and who hands you the export on the last day.

This page is the pre-sign question list.

Key Takeaways

  • Ask who files the carrier dispute and who confirms the credit on a later invoice. A report is not a recovery.
  • Ask what share of invoice lines is audited against the contracted rate table, not what share is loaded into the tool.
  • Ask how the inventory of record is built, and in what format you receive it if the engagement ends.
  • A food service client working with RadiusPoint on 600-plus lines cut mobility cost 22% and more than $400,000 in year one after 56 departed users were still being billed.
  • Seven questions to ask on signing day is RadiusPoint’s list of questions that have to survive into the contract, not only into the sales deck.

The Short Version

Before you sign a TEM agreement, write seven answers into the statement of work: who files, what share of lines is audited, how inventory is exported, what the letter of agency covers, which pricing model you are buying, who the named analyst is after go-live, and what files you receive on the last day.

In this article

The questions that belong in the contract, not the demo

The questions that belong in a TEM contract are the ones a RadiusPoint demo, or any demo, can dodge with a screenshot. RadiusPoint writes those questions into ExpenseLogic’s operating model so a buyer can test the answer after month three, not only on the sales call. “We audit invoices” is demo language. “What percentage of lines, against which rate table” is contract language. The vendor evaluation page on the RadiusPoint site is the commercial companion. This page is the script you take into the room.

This page assumes you already know what TEM is and you are about to sign.

A letter of agency, an inventory export, and a dispute register are three different documents. RadiusPoint will ask you for the first at kickoff. You should ask RadiusPoint, or any other provider, for the other two in writing before you sign.

Who files the dispute when an invoice is wrong?

The provider should file the dispute, age it, and confirm the credit on a later invoice, unless you have staffed that work internally on purpose. RadiusPoint files carrier disputes on the client’s behalf and tracks them in ExpenseLogic until the credit posts. A flag-only model hands you an exception list. A draft-only model writes the letter and leaves the follow-up with you. Ask which box you are buying.

A Fortune 100 manufacturer working with RadiusPoint recovered $450,000 in telecom refunds in year one, with $850,000 in ongoing annual savings and a $1.3 million year-one impact. That figure is a recovery story. It is only useful in a pre-sign meeting if the provider can say who filed, who chased, and how the credit was proven. Invoice auditing services find the error. Filing is the next job.

If the answer is “we send you a report,” write that into the statement of work as your labor, not as their managed service.

What percentage of invoice lines will you actually audit?

Ask for the invoice-line coverage percentage in writing, and ask RadiusPoint or any bidder what happens below a dollar threshold. RadiusPoint audits invoice line items against contracted rates and against inventory, rather than sampling, and records that work in ExpenseLogic. Loading an invoice is not auditing it. Anomaly flags are not a rate-table match.

Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category-level observation, not a RadiusPoint guarantee, and it only holds if someone actually checks the lines. A glass manufacturer working with RadiusPoint saved $100,000-plus in year one. A healthcare provider reduced telecom expenses 26%. Ask each bidder to show a comparable finding, then ask whether those dollars were identified, disputed, or credited.

Telecom expense management pricing explains how providers charge. This question is about what you receive for that charge.

How will we get our inventory of record if we leave?

You should receive a documented export of services, BANs, locations, rates, disputes, and credits that the next operator can load. RadiusPoint treats the inventory of record as a client-owned file inside ExpenseLogic, not as a vendor hostage. Ask for the export format, the field list, and the number of business days after notice.

A food service client had 600-plus phones billed monthly with no employee identification, and 56 identified users who were no longer employed. That inventory work is published on the RadiusPoint managed mobility case study. If you cannot leave with that file, you will rebuild it from carrier bills. That rebuild is the cost people forget to price into the contract.

Inventory management at RadiusPoint has also recovered $174,000 in re-credits when the record of services did not match the bill. Ask the bidder how that kind of mismatch is found, and whether you keep the evidence pack.

Seven questions to ask on signing day

These seven signing-day questions are RadiusPoint’s list of seven questions that have to be answered in the statement of work before a TEM signature is safe. ExpenseLogic is built so those answers can be tested after go-live. Buyer guides in this category list features. They do not lock a seven-question contract script that separates demo language from operating language.

# Question Weak answer Strong answer
1 Who files the dispute, and who chases the credit until it posts? “We flag exceptions.” Named team files, ages, and confirms the credit
2 What share of invoice lines is audited, not just loaded? “We run analytics.” A written coverage percentage against a rate table
3 How is the inventory built, and how is it exported if we leave? “You can see it in the portal.” Documented export, field list, and delivery days
4 What does the letter of agency authorize, and how is it revoked? “Standard LOA.” Scoped rights, logging, and a revoke path
5 Which pricing model are we buying, and what does it reward? “Flexible commercial terms.” Recovery share, per-invoice, per-line, or hybrid, with the incentive named
6 Who is the named analyst after go-live? “A dedicated team.” A named person plus a backup
7 What files do we receive on the last day? “We’ll work with you.” Inventory, dispute register, credit log, contract images

Which pricing model are you buying, and what does it reward?

You are buying a recovery share, a per-invoice or per-line fee, a platform license, or a hybrid, and each model pays a different behavior. RadiusPoint is a managed service on ExpenseLogic, not a one-time contingency audit. A recovery-only fee pays someone to find refunds. It does not, by itself, pay them to stop the next invoice from repeating the error. Read that incentive before you read the case study.

This section only asks you to match the model to the work you just scoped. If you want disputes filed and inventory kept current, a license that leaves those tasks with you is the wrong purchase.

HumanGood, a named RadiusPoint client, has a published 315% ROI case. Use named cases as proof that a program can pay. Use the seven signing-day questions to test whether this contract will produce that kind of program.

How RadiusPoint answers these questions in a managed TEM engagement

RadiusPoint delivers managed telecom expense management on ExpenseLogic: analysts audit lines, file disputes, and keep inventory, while you keep budget approval. The telecom expense management service is the commercial page for that model. This article is the question list you should still ask RadiusPoint, in writing, before you sign.

RadiusPoint has been in this work since January 1992. ISO 9001 certification has been in place since September 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. Credentials tell you the firm is real. The seven signing-day questions tell you the contract is real.

Sharon Watkins founded RadiusPoint after internal-audit work at a bank. The pre-sign problem is an audit problem with a sales deck attached. ExpenseLogic is the working paper after you sign. The seven questions are the working paper before you sign.

FAQ

Is this the same as a TEM RFP scorecard?

A scorecard ranks vendors. The seven signing-day questions write operating duties into one contract. RadiusPoint can sit on a scorecard and still fail this list if the statement of work is vague. Ask both.

Should we ask for a sample audit before we sign?

Yes, if you can provide a slice of invoices and contracts. RadiusPoint will treat a sample as evidence, not as a promise of year-one dollars. A sample that only loads PDFs and never files a dispute is a warning.

What if the provider will not name an analyst?

Write a named analyst plus a backup into the statement of work, or treat the gap as a staffing risk. RadiusPoint’s model is a named human on the account. A ticket queue with no name is a different purchase.

Do we still need a letter of agency if we only want reporting?

If the provider must pull invoices or talk to a carrier, yes. Scope it. A read-only billing grant is not the same as ordering rights. RadiusPoint will tell you which grant it is asking for.

What to do before you sign

Print the seven signing-day questions. Put the bidder’s answers in the left column and the contract clause in the right. If a cell is empty, you are buying a demo. RadiusPoint will fill those cells for a managed ExpenseLogic engagement. Every week you sign without them is a week you cannot test the work.

References

  1. How to Choose a Telecom Expense Management Company | RadiusPoint
  2. What Is Telecom Expense Management? | RadiusPoint
  3. Telecom Expense Management Services | RadiusPoint
  4. Telecom Expense Management Pricing | RadiusPoint
  5. Invoice Auditing Services | RadiusPoint
  6. Vendor Evaluation | RadiusPoint
  7. How Managed Mobility Services Cut Costs 22% ($400K in Year 1) | RadiusPoint
  8. HumanGood Achieved 315% ROI with RadiusPoint | RadiusPoint
  9. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
  10. ExpenseLogic reviews | Capterra
  11. Sharon R. Watkins | RadiusPoint

Disclaimer

This article is general information for finance, IT, and procurement teams evaluating a TEM contract. It is not legal advice. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results. Category-level ranges are hedged and are not RadiusPoint promises.

Utility Rate Reclassification and How It Lowers Bills

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 28 August 2026 · 12 min read

Utility rate reclassification is the filed request that moves a meter onto a different published rate class so the same kilowatt-hours and peak kilowatts are priced under a schedule the load actually qualifies for. A plant that added a night shift two years ago can still be billed as a daytime general-service account. Rate reclassification is a Utility Expense Management (UEM, not Unified Endpoint Management) tariff action. RadiusPoint runs it on ExpenseLogic as a schedule change, not as a vacant-cost recovery and not as a line-item bill audit.

The live utility rate optimization page covers the wider program, including demand management and power-factor work.

Key Takeaways

  • Utility rate reclassification changes the published class on an account. It does not change the meter read, the tenant name, or the occupancy date.
  • The U.S. commercial average was 14.19 cents per kWh in June 2026, up 4.8% from June 2025, per the EIA Electricity Monthly Update.
  • RadiusPoint published vacant cost recovery that decreased utility expenses by 12%, and a multi-location client paid $1,500 a month ($18,000 a year) for utilities at closed locations. Those are payer problems. Reclassification is a schedule problem.
  • An elevator-company engagement cut monthly waste expenditure 28% through vendor and contract work. RadiusPoint keeps that credit type separate from a rate-class move.
  • How to check rate-class fit uses four gates: load factor, voltage or service level, demand threshold, and operating hours.

The Short Version

If the invoice math is correct and the account is still on a class the load no longer fits, RadiusPoint should file a rate reclassification in ExpenseLogic, not open a billing-error dispute.

In this article

What utility rate reclassification actually changes

Utility rate reclassification changes the published tariff class the utility uses to price an account, while consumption and peak demand stay on the same meter. RadiusPoint treats that class change as a Utility Expense Management (UEM) action inside ExpenseLogic. The invoice still lists energy charges, demand charges, customer charges, and riders. The class decides which published prices attach to those lines.

A reclassification is a customer-initiated filing in most territories. The utility will keep billing the class it assigned at turn-on until someone applies, qualifies, and is moved. RadiusPoint stores the current schedule, the interval history, and the candidate class in ExpenseLogic so finance can see the before-and-after on the same account.

Vacant cost recovery asks who should be the customer of record. Rate reclassification asks which published class that customer should sit in. RadiusPoint keeps both on the utility expense management service so a facilities lead can open two exception types without mixing the workstreams.

How is rate reclassification different from a utility bill audit?

A utility bill audit at RadiusPoint tests whether this invoice matches the meter, the tariff, and the signed contract. Rate reclassification tests whether that tariff is still the class the site qualifies for. RadiusPoint runs both inside ExpenseLogic and posts them as different exception types. A bill audit recovers a wrong multiplier, a duplicated demand line, or a tax that does not belong. A reclassification leaves those lines intact and changes the schedule they are priced on.

Invoice auditing services catch category errors on telecom and related invoices. On the utility side, the same discipline still stops at “is this charge correct for the class we are on.” Reclassification starts after that question is answered yes.

Vacant cost recovery is a third job. RadiusPoint’s vacant cost recovery work is the owner-name and occupancy match. Do not send a rate-class application to fix a tenant who never transferred service.

Why a correctly calculated bill can still be the wrong bill

A correctly calculated bill can still be the wrong bill when the published class no longer matches how the site draws power. RadiusPoint sees this in ExpenseLogic after a shift change, an automation project, a square-footage change, or a voltage upgrade. The utility did the arithmetic. The class was assigned years earlier. Finance kept paying because the due date was real.

The U.S. commercial average sat at 14.19 cents per kWh in June 2026, 4.8% above June 2025, according to the EIA Electricity Monthly Update (U.S. retail sector, June 2026). At that all-in level, a class that prices the same kilowatt-hour and the same peak kilowatt on a different published schedule changes the invoice without touching the meter. RadiusPoint does not publish a house percentage for reclassification savings. The dollar outcome is the difference between two filed tariffs on one load.

RadiusPoint has published other utility outcomes that are easy to confuse with a class change. Vacant cost recovery decreased utility expenses by 12%. A multi-location client paid $1,500 a month, $18,000 a year, for utilities at closed locations. An elevator-company engagement cut monthly waste expenditure 28%. Those credits stay in their own buckets in ExpenseLogic.

What load data do you need before you apply for a new rate class?

You need interval history, the current tariff sheet, billed demand, and a dated note on how the site now operates, before anyone files. RadiusPoint loads those four inputs into ExpenseLogic so the rate-class fit check has evidence. Twelve to 24 months of interval data is the usual ask from utilities and from analysts, because one summer peak can hide a winter load factor. The current tariff sheet tells you which classes exist and what kW floor, voltage, or hours each one requires.

A class application without operating-hours context fails in two directions. You can apply for a time-of-use class a 9-to-5 office cannot use. You can also stay on a high-demand general-service class after production moved off-peak. RadiusPoint will not file from a single monthly kWh total. ExpenseLogic needs the peak interval and the hours that created it.

Site status still matters. A closed location is a vacant-cost or disconnect job first. RadiusPoint will not reclassify a dark meter to “save” an account that should be ended.

How to check rate-class fit

Rate-class fit is checked as RadiusPoint’s four-gate method for load factor, service voltage, demand threshold, and operating hours on one account. ExpenseLogic is where RadiusPoint stores the four inputs so the test can run when a site changes, not only when a consultant is hired. Ranking tariff pages in 2026 walk demand charges. They do not teach this four-gate sequence as a named finance test.

Gate What RadiusPoint loads into ExpenseLogic Pass condition
Load factor Interval kWh versus billed kW The class matches a steady or peaky profile
Voltage / service Account service level on the tariff Secondary, primary, or transmission eligibility is met
Demand threshold Peak kW against the class floor The site is over or under the published kW gate
Operating hours Shift calendar and known process loads Time-of-use or interruptible classes are usable

A fail on gate 4 with a pass on gate 3 is a time-of-use candidate. A fail on gate 2 is a service-level application, which can require utility construction, not only a paper filing. RadiusPoint writes the fail type onto the ExpenseLogic exception so facilities is not guessing. Vacant cost is the wrong payer. Bill audit is the wrong charge. Rate class is the wrong schedule. RadiusPoint will not treat those three as one “utility savings” line.

Who files a rate reclassification, and who has to approve it?

The customer of record files, and the utility (or the commission rules behind that utility) approves if the account qualifies. RadiusPoint prepares the analysis in ExpenseLogic and can submit on the client’s authority where a letter of agency or similar grant allows it. The utility is not obligated to shop you into a cheaper class. That is why a paid invoice can stay expensive for years.

Approval is a qualification test, not a negotiation. If the site is below a demand floor, the industrial class is closed. If the site cannot shed load, an interruptible rider is closed. RadiusPoint will show the failed gate rather than promise a move. Utility service options on the RadiusPoint site is the procurement companion for deregulated supply. Reclassification of the delivery class is a different filing.

Sharon Watkins founded RadiusPoint in January 1992. The class-change problem is an audit problem with a tariff book attached. ExpenseLogic is the working paper. RadiusPoint is the team that files.

How RadiusPoint and ExpenseLogic keep tariff analysis in the monthly cycle

RadiusPoint runs tariff analysis as managed Utility Expense Management, and ExpenseLogic watches for a load that has left its class. The utility expense management service already stores tariff schedules, demand readings, and site comparisons. Reclassification is the exception that says “apply,” not “dispute.”

A one-time consulting study goes stale when the next shift change lands. RadiusPoint keeps the rate-class fit check on the same monthly feed that catches a vacant name and a closed-site bill. ISO 9001 certification, in place at RadiusPoint since September 2002, is how that exception process stays repeatable when the location count moves. RadiusPoint published a client that grew from 170 to 1,200 locations. At that scale, a missed class on a handful of sites is not a rounding error.

RadiusPoint’s Capterra listing sat at 4.8 from 31 reviews through December 2025. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. Those credentials sit on the firm. They are not a savings percentage for a class change.

FAQ

Does rate reclassification work on gas, water, and waste, or only on electric?

Electric is where published commercial classes and demand gates show up most often. RadiusPoint still reviews gas, water, sewer, and waste schedules in ExpenseLogic when a territory publishes more than one class. The elevator-company 28% waste reduction was contract and vendor work, which RadiusPoint keeps separate from a class filing.

Can you recover prior months after the class is changed?

Only if the utility’s tariff or the commission rules allow a back-effective date, and only with interval evidence RadiusPoint can attach in ExpenseLogic. The operational job is to show the qualification date. Counsel and the utility decide whether that date is retroactive. RadiusPoint does not write tariff language.

Is a time-of-use enrollment the same as a rate reclassification?

Time-of-use is one kind of class or rider change. It still has to pass the operating-hours gate. RadiusPoint will not enroll a site that cannot move load off-peak and then call the higher on-peak rate a win.

How is this different from shopping a retail energy supplier?

Shopping a supplier changes the energy commodity in a deregulated market. Reclassification changes the utility’s published delivery or bundled class. RadiusPoint can support both. They are different filings and different lines on the invoice.

Do you need interval meters to do this?

You need enough history to prove load factor and peak timing. Interval data is the clean path. A monthly kWh and kW pair is a start, not a filing pack. RadiusPoint will say so in ExpenseLogic rather than file blind.

What to do before the next utility cycle

If you cannot name the published class on last month’s five largest electric accounts, start there. RadiusPoint will load those invoices into ExpenseLogic and check rate-class fit with you. Every cycle you skip is another month priced on a class the load may have already left.

References

  1. Electricity Monthly Update, End Use: June 2026 | U.S. Energy Information Administration
  2. ExpenseLogic | RadiusPoint
  3. Utility Expense Management | RadiusPoint
  4. Vacant Expense Recovery Solution | RadiusPoint
  5. Utility Rate Optimization | RadiusPoint
  6. Invoice Auditing Services: What They Cover and How to Choose a Provider | RadiusPoint
  7. Utility Service Options | RadiusPoint
  8. Sharon R. Watkins | RadiusPoint
  9. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
  10. ExpenseLogic reviews | Capterra

Disclaimer

This article is general information for finance and facilities teams. It is not legal advice on tariffs, commission rules, or back-effective dates. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies, or from named public sources, and are not a guarantee of future results.

How Companies Recover Telecom Refunds and Credits From Carriers

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 27 August 2026

Companies recover telecom refunds by filing a documented dispute, keeping a carrier case number open, and confirming the credit posted on a later invoice. A finding in a spreadsheet is not a refund. It is a claim that dies if nobody pursues it through the carrier’s window.

Refund recovery is the work that turns an audit exception into cash on a bill you can show finance. RadiusPoint’s live FAQ says credits pending are tracked in ExpenseLogic until the credit is received. That sentence is the job.

Key Takeaways

  • Filed is not recovered. Recovery is the posted credit, allocated in the next GL file.
  • A Fortune 100 manufacturer on RadiusPoint’s published record recovered $450,000 in telecom refunds in year one.
  • Inventory management on that same published record recovered $174,000 in re-credits.
  • Unneeded toll-free numbers produced $18,000 a year. Contract rate optimization produced $120,000 a year.
  • 47 CFR 64.2401 requires a toll-free dispute contact on the bill and forbids unauthorized charges (Cornell LII).

The Short Version

Keep a register: case number, service ID, months open, dollars claimed, window, status. Close a row only when the credit hits an invoice.

Stage Evidence Failure mode
Find Exception vs rate or inventory Slide deck, no claim
File Carrier case number Email with no ticket
Pursue Escalation log Finder leaves, case dies
Post Credit on a billed invoice “Agreed” but never appears
Allocate GL / cost center file Cash lands in a dump account

In This Article

Finding an Error Is Not Recovering a Credit

Finding an error is the audit, and recovering the credit is a second job with a case number and a posted invoice. Recovering the credit is a second job with a case number, a window, and a posted invoice.

ExpenseLogic’s expense-audit module lists dispute tracking next to line-item detail. The capability statement names credit recovery and prevention of recurring error through maintained reference data. Prevention matters because a recovered credit that repeats next month was a refund, not a fix.

Sharon Watkins’s published line is that the telecom industry “can’t keep up with the ubiquitous challenges and doesn’t have the time to identify savings.” Identification is cheap compared with pursuit. The people who find the error are rarely the people the carrier will still take a call from six months later.

A glass manufacturer on the published record saved more than $100,000 in year one at 200% ROI. The number is useful here only if you ask whether those dollars were credits received or costs avoided. RadiusPoint’s live capability language groups “telecom refunds and cost savings” together on a $1.3 million program.

How does a carrier credit actually post?

A carrier credit posts as a later invoice line, bill adjustment, or remittance you can show finance once the carrier issues it. RadiusPoint tracks the pending credit inside ExpenseLogic until that moment.

Typical post paths:

  1. Credit memo on the next BAN invoice.
  2. Adjustment inside a tax or surcharge bucket, easy to miss.
  3. Check or wire, rare on large estates.
  4. “Account credit” that sits until someone asks AP to apply it.

If the credit is buried in a tax bucket, allocation has to follow it or the department that overpaid never sees the cash. That is why the last step of Credit-to-Cash is the GL file, not the carrier email.

Managed mobility services recover a different flavor of credit: zero-use and ex-employee lines that should stop billing. A food service client cut 22% ($400,000) in year one across more than 600 lines. Some of that is avoidance going forward. Ask which dollars were back-credits.

Two-day invoice processing, a live FAQ claim, helps you see the credit when it lands. It does not file the dispute.

What do Truth-in-Billing rules actually give you?

Truth-in-Billing rules give you a dispute contact and a clear bill, not a deposited refund you still must pursue. RadiusPoint’s job is to file inside the window and keep the case alive.

47 CFR 64.2401 requires a clear description of each charge, a named provider, a distinct section for third-party charges, a toll-free inquiry number, and a ban on unauthorized charges (e-CFR via Cornell). The FCC’s Truth-in-Billing page restates those duties and was updated 22 April 2025 (FCC).

Those rules give you a contact and a right to contest. They do not deposit the money. Cramming (unauthorized third-party charges) is the consumer-facing cousin of a problem enterprises still see on BAN invoices. Recovery is still a case file.

Gartner forecast $1.354 trillion in communications services spend for 2026 (Gartner, 27 July 2026). A small error rate on a number that large is why pursuit, not discovery, is the scarce skill.

What belongs on the refund register?

Finance should demand a six-field refund register: case number, service ID, months open, dollars claimed, window, and posted status. RadiusPoint’s pending-credit tracking is that register inside ExpenseLogic.

A register without a case number is a wish list. A register that closes on “carrier agreed” is a wish list with a date. Close only on a posted invoice image.

Unapplied credits are a named finding type in RadiusPoint’s audit language: a credit agreed but never posted. Inventory of record plus the register is how you stop paying for the same error after you “won.”

Utility expense management (UEM means Utility Expense Management, not Unified Endpoint Management) produces the same register for meters. Do not mix those rows into a telecom BAN without a service-ID key.

Which refund figures are published?

RadiusPoint’s usable refund proof is the published library of published named client outcomes, and never a guarantee of future cash.

published figures that name refund, re-credit, or a cash-like recovery:

  • Fortune 100 manufacturer: $450,000 telecom refunds, year one.
  • Inventory management: $174,000 in re-credits.
  • Unneeded toll-free numbers: $18,000 a year.
  • Contract rate optimization: $120,000 a year.
  • $250,000-plus in unrealized cost savings uncovered (published language; treat as uncovered value, not as posted cash, unless the case file says posted).

Industry range, hedged: organizations implementing TEM typically see 15% to 30% cost reduction in year one. That is category language, not a RadiusPoint refund promise. Average ROI of 370% to 580% is an industry-range statement and is an average of self-published figures. Prefer a named case.

Has managed more than $550 million in annual client spend is an industry-range statement and from 2019. Skip it when you are proving a refund.

Capterra 4.8 from 31 reviews through December 2025 (Capterra), ISO 9001 since 2002, and Amalgam Insights Distinguished Vendor 2024 are process credentials. They support the claim that someone will still be on the case next quarter.

How RadiusPoint Pursues the Case

RadiusPoint analysts file with the carrier under a scoped letter of agency, then keep the case in ExpenseLogic until the credit posts. Telecom expense management is the service wrapper. Sharon Watkins is the founder who still treats pending credits as unfinished work.

The about RadiusPoint page is the company story. The operating rule is here: a dedicated internal audit team reports daily statistics on invoice processing and support-ticket accuracy, per the live capability statement. Daily is the cadence a register needs.

An automotive salvage client published $1.3 million on the TEM page. The capability page also cites a $1.3 million telecom refunds-and-savings program. Use the figure as published scale. Ask, in diligence, how much of it was posted credits versus avoided spend.

Ask to see five closed rows: case number, invoice image of the credit, and the GL line. If a provider can find errors but cannot show those three, you have an audit. You do not have recovery.

Frequently Asked Questions

If the auditor found $200,000, do we have $200,000?

No. You have a claim. You have the money when the credit posts and the GL file reflects it. Ask for the register, not the slide.

What is the difference between a refund and cost avoidance?

A refund or re-credit is cash or a billed credit for a past error. Avoidance is the same error not repeating. Both matter. Only the first belongs on a refund page.

Do Truth-in-Billing rules force the carrier to pay?

They force a clear bill, a dispute contact, and no unauthorized charges. They do not set your enterprise window or wire the money. You still file and pursue.

Can we recover credits on wireless lines?

Yes, when the line should not have billed (zero-use, ex-employee, wrong plan). RadiusPoint’s MMS work is the usual path. The register fields do not change.

Close the Row When the Invoice Shows the Credit

A dispute without a posted invoice is still open, and the register should keep that row live until the credit image exists. Build the register. Staff the pursuit. Allocate the cash.

Request a demo of ExpenseLogic and ask to walk five pending credits to posted. Every month a case sits without a number is another month the carrier keeps the money.

References

  1. 47 CFR § 64.2401: Truth-in-Billing Requirements | Cornell LII / e-CFR
  2. Truth-In-Billing Policy | Federal Communications Commission, updated 22 April 2025
  3. Gartner Forecasts Worldwide IT Spending to Grow 14.2% in 2026, Totaling $6.37 Trillion | Gartner newsroom
  4. ExpenseLogic | Capterra
  5. Telecom Expense Management | RadiusPoint
  6. ExpenseLogic | RadiusPoint
  7. Managed Mobility Services | RadiusPoint
  8. About | RadiusPoint
  9. RadiusPoint Capability Statement | RadiusPoint
  10. Sharon Watkins | RadiusPoint

This article is educational. RadiusPoint does not guarantee refund amounts, credit posting dates, or carrier outcomes. Figures were current as of 28 August 2026.

businessman analyzing financial data with tablet

Critical Need for Demand Planning and Forecasting in Utility Management

UEM0

The CFO of a multinational manufacturing firm stares at the latest utility bill, a sprawling document detailing energy consumption across dozens of facilities. The numbers are higher than anticipated, yet again. There is no clear understanding of why, nor a reliable method to predict future costs or identify potential savings. 

This scenario, unfortunately, is a common reality for many enterprise organizations: a reactive approach to utility expenses, driven by a lack of insight into consumption patterns and market fluctuations. The result is often budget overruns, missed opportunities for efficiency, and a significant drain on financial resources.

For large organizations, managing utility expenses is far more complex than simply paying bills. It involves navigating volatile markets, understanding intricate rate structures, and reconciling usage across a vast, distributed infrastructure. 

Without robust demand planning and forecasting, businesses are left vulnerable to unpredictable costs, undermining financial stability and strategic initiatives. 

This article explores how advanced utility expense management, powered by sophisticated demand planning and forecasting, can transform this challenge into a substantial competitive advantage.

Need for Demand Planning and Forecasting

Traditional utility expense management often relies on historical data and basic trend analysis, which are insufficient in today’s dynamic energy landscape. 

Factors such as weather variability, economic shifts, regulatory changes, and evolving operational demands all impact utility consumption and pricing. Without a proactive approach, organizations are perpetually playing catch-up, reacting to invoices rather than shaping their utility spend.

Demand planning and forecasting, when applied to utility management, involves predicting future consumption patterns and associated costs with a high degree of accuracy. This is not merely about estimating; it is about building a comprehensive model that incorporates historical usage, operational data, market intelligence, and predictive analytics. 

The benefits are profound: enhanced budgeting accuracy, identification of cost-saving opportunities, improved energy procurement strategies, and a stronger foundation for sustainability initiatives.

From Scattered Data to Strategic Savings

Many organizations grapple with decentralized utility data, often spread across various departments, spreadsheets, and vendor portals. This fragmented view makes comprehensive analysis and effective forecasting nearly impossible. RadiusPoint addresses this core pain point by providing a centralized platform, ExpenseLogic, which consolidates all utility data into a single, accessible repository.

This consolidation is the first crucial step in enabling effective demand planning. 

Once data is unified, our hybrid model, combining the ExpenseLogic SaaS platform with a dedicated managed services team, can begin to extract meaningful insights.

Our experts leverage this data to perform a line-item audit on every bill, identifying discrepancies, errors, and opportunities for optimization that would otherwise go unnoticed. This granular level of analysis is critical for building accurate forecasts and uncovering hidden savings.

Consider the challenge of allocating utility costs across various departments or even down to individual cost centers or profit/loss units. For a large enterprise, this can be an administrative nightmare. RadiusPoint offers granular allocation down to the meter number, providing unparalleled transparency and accountability. This precision not only simplifies internal chargebacks but also provides a more accurate basis for forecasting, as specific consumption drivers can be isolated and analyzed.

Transforming Expense Management from a Chore into a Strategic Advantage

For most organizations, utility expense management is seen as a burdensome, non-core activity. It consumes valuable internal resources, from finance teams painstakingly reconciling invoices to operations personnel chasing down usage data.

RadiusPoint redefines this perception, Transforming Expense Management from a Chore into a Strategic Advantage.

Our approach moves beyond simple bill payment. We integrate demand planning and forecasting into a comprehensive utility expense management strategy, enabling organizations to:

  1. Optimize Budgets: Accurate forecasts allow for more precise budgeting, reducing the risk of unexpected expenses and freeing up capital for strategic investments.
  2. Identify Cost Reduction Opportunities: By understanding future consumption and market trends, businesses can proactively implement energy efficiency measures, negotiate better rates, and avoid peak demand charges. Our typical clients see cost savings of 15-30% in the first year alone, demonstrating the tangible financial impact.
  3. Enhance Procurement Strategies: With clear demand projections, organizations can engage in more informed energy procurement, locking in favorable rates and mitigating price volatility.
  4. Support Sustainability Goals: Accurate consumption data and forecasts are foundational for developing and tracking environmental sustainability initiatives, helping organizations meet their ESG (Environmental, Social, and Governance) targets.

The RadiusPoint Difference: Unmatched Expertise and Proven Results

What sets RadiusPoint apart is our unique blend of technology and human expertise. The ExpenseLogic platform provides the robust data aggregation, analytics, and reporting capabilities needed for sophisticated demand planning. 

Our managed services team, composed of industry veterans, then applies their deep knowledge to interpret this data, identify trends, and develop actionable recommendations.

Our commitment to client success is reflected in our impressive metrics:

  • 370-580% average ROI for clients: This exceptional return on investment highlights the significant financial benefits our services provide.
  • Vacant Cost Recovery (VCR) for UEM: This specialized service proactively identifies and recovers costs associated with unoccupied or underutilized facilities, a common source of financial leakage for large enterprises.

Our services provide actionable business intelligence, giving CFOs, Operations Managers, Procurement Managers, and IT Directors the insights they need to make informed decisions. Instead of merely processing invoices, we empower them to understand the underlying drivers of their utility expenses and proactively manage them.

The Cost of Inaction

The complexities of utility expense management are only increasing. Regulatory shifts, climate concerns, and volatile energy markets demand a proactive, data-driven approach. Continuing with manual processes and reactive budgeting is no longer a viable strategy for mid-market and enterprise organizations. The financial leakage from undetected billing errors, the resource drain from manual invoice processing, and the lack of centralized spending visibility are quantifiable costs that directly impact profitability.

Consider the compounding effect of even small errors or inefficiencies across hundreds or thousands of utility accounts over several years. The cumulative loss can be staggering, dwarfing the investment in a comprehensive solution.

You have a choice: remain reactive, allowing rising utility costs and inefficiencies to erode your bottom line, or embrace a strategic, data-driven approach that transforms a significant expense into a source of competitive advantage.

Choose to gain control, achieve unparalleled visibility, and unlock substantial savings. Explore Utility expense management by RadiusPoint today to schedule a consultation and begin your journey toward optimized utility spend.

How Long a Telecom Expense Management Rollout Actually Takes

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 26 August 2026

A telecom expense management rollout takes as long as it takes to build a defensible inventory, collect letters of agency, gather scattered invoices, and agree the ERP file spec. RadiusPoint does not publish a week count, and any provider who gives you one before seeing those four inputs is selling a Gantt, not a close date.

TEM implementation time is gated by inventory completeness, not by software provisioning. You bought the program because invoices were already late and incomplete. That mess is the clock.

Key Takeaways

  • RadiusPoint’s published proof is stated in year-one outcomes, not in a published week range.
  • Organisations implementing TEM typically see 15% to 30% cost reduction in year one. That is an industry-range statement, not a RadiusPoint guarantee.
  • A Fortune 100 manufacturer on RadiusPoint’s published record recovered $450,000 in telecom refunds in year one, plus $850,000 in ongoing annual savings.
  • A food service client cut 22% ($400,000) in year one across more than 600 lines.
  • Two-day invoice processing is a live RadiusPoint operating claim after a bill exists. It is not a rollout clock.

The Short Version

Do not accept a week count as the answer. Ask which work unit is open: agency letters, invoice scatter, inventory build, or the ERP spec. Published RadiusPoint proof lands in year one.

Work unit Why it sets the clock What “done” looks like
Letters of agency Carriers will not release records without them Signed, scoped LOAs with each carrier
Invoice scatter AP, IT, and sites hold different years Agreed BAN list and a first complete cycle
Inventory build No audit or allocation without it Service IDs reconciled to CSRs
ERP file spec Close cannot use a dashboard Accrual and GL formats accepted by AP
First validated cycle Software live is not operational live One month of exceptions worked to a register

In This Article

Why RadiusPoint Will Not Quote a Week Count

RadiusPoint will not quote a TEM week count because none of RadiusPoint’s published case studies states one. Sharon Watkins has run this company since January 1992. The honest answer after three decades is that the inventory is the clock.

Vendor blogs publish 90 to 120 days, 90 to 180 days, or 4 to 8 weeks. Those are their marketing ranges, not RadiusPoint’s, and they are not adopted here. The capability statement says setup is completed by the RadiusPoint team and that configuration follows the client. It does not attach a week number to that sentence.

ISO 9001 since September 2002 and a 2024 Amalgam Insights Distinguished Vendor listing are process signals. They are not a Gantt. Capterra lists ExpenseLogic at 4.8 from 31 reviews through December 2025 (Capterra). Reviews describe the work.

Gartner named RadiusPoint a Representative Vendor in the 2023 Market Guide for TEM Services. Always keep the year. That recognition is not a delivery calendar.

What actually consumes the calendar?

Four client-side inputs consume the calendar: letters of agency, invoice scatter, inventory quality, and ERP specs RadiusPoint cannot skip. RadiusPoint’s telecom expense management service cannot audit a circuit the carrier has not confirmed.

Here they matter as a gate: no LOA, no customer service records, no inventory of record. Invoice scatter is the second gate. Twelve to thirty-six months of bills usually sit in AP, IT, and site inboxes. That gathering is not software.

Inventory build is the longest honest work. ExpenseLogic can store the result. It cannot invent a CSR the carrier has not sent. The ERP spec is the fourth gate: accrual files and GL coding have to match the client’s close, which is why RadiusPoint collects file specifications during setup.

A glass manufacturer on the published record saved more than $100,000 in year one at 200% ROI. That number is a year-one outcome. It is not evidence the project finished in a quoted week.

Why is year one the honest published window?

Year one is the only time window RadiusPoint’s published proof consistently uses for outcomes rather than a week count. If a proposal talks in weeks and the proof talks in years, believe the proof.

Published year-one marks:

  • Fortune 100 manufacturer: $450,000 telecom refunds, $850,000 ongoing annual savings, $1.3 million total year-one impact, more than 10,000 wireless devices.
  • Food service: 22% reduction, $400,000, more than 600 lines.
  • Global glass manufacturer: more than $100,000, 200% ROI.
  • Healthcare provider: 26% reduction in telecom expenses (period stated as the engagement result, not as a week count).

Industry range, hedged: organisations implementing TEM typically see 15% to 30% cost reduction in year one. Attribute that to the TEM category, not to a RadiusPoint promise.

Has managed more than $550 million in annual client spend is an industry-range statement and dates to 2019. Use it as historical scale only. Client growth from 170 to 1,200 locations is published scalability proof, which tells you the platform can absorb a larger estate. It still does not give you a week count.

What must you bring before day one?

You must bring carrier and BAN lists, signed letters of agency, trusted inventory, and the ERP layout AP will accept. RadiusPoint’s managed mobility services add employee IDs and device serials to that pack.

This section only names the items that move the clock. If any of them are missing, the honest range stays “year one to first validated outcomes,” not a week you picked because a competitor printed one.

About RadiusPoint states the firm has been serving businesses since 1992. Longevity is relevant because carrier processes have not gotten faster. The telecom industry, in Sharon Watkins’s published line, “can’t keep up with the ubiquitous challenges and doesn’t have the time to identify savings.” That is why the rollout is a records project.

Utility expense management (UEM means Utility Expense Management, not Unified Endpoint Management) adds meter lists and tariffs to the same pack when utilities are in scope. Do not pretend a TEM-only Gantt covers meters.

What Live Means, and What It Does Not

Live means one complete invoice cycle has been received, validated, exceptioned, and exported into AP, not merely a portal login. RadiusPoint’s two-day processing claim starts after that cycle exists. A portal login is not live.

Dispute credits still in flight are not a reason to call the rollout unfinished, and they are not a reason to call it finished. They are a register. Healthcare 448% ROI and HumanGood 315% ROI are published outcomes of running the process, not of flipping a switch.

Ask every provider a single question: what work is complete on the day they say they are live? If the answer is “the software is provisioned,” you still do not have TEM. If the answer is “the inventory of record and the first coded file,” you are in the honest window.

Frequently Asked Questions

How long does a TEM implementation take at RadiusPoint?

RadiusPoint does not publish a week count. Time follows letters of agency, invoice scatter, inventory build, and the ERP file spec. Published proof is year-one outcomes.

Why do other vendors quote 90 days or 8 weeks?

Those are their marketing ranges. They are not in RadiusPoint’s published case studies, so they are not repeated here as a promise or as our range.

Is two-day invoice processing the rollout time?

No. Two-day processing is how fast a received invoice is worked after go-live. It is not how long it takes to build the inventory that invoice is tested against.

When should we expect savings?

Published RadiusPoint cases that state a period use year one. Category-level industry language is 15% to 30% in year one for organisations that implement TEM. Neither is a guarantee.

What is the fastest way to stall a rollout?

Leave letters of agency unsigned, or keep invoices in site inboxes. Software cannot request a CSR the carrier has not been authorised to send.

Ask for Work Units, Not a Gantt

If a proposal’s first number is a week count and its proof is year-one, the week count is decoration. Score the four gates. Then look at year-one cases.

Request a demo of ExpenseLogic and ask what RadiusPoint considers live. Every month spent arguing about a fictional week is a month the same inventory errors keep billing.

References

  1. ExpenseLogic | Capterra
  2. Gartner Forecasts Worldwide IT Spending to Grow 14.2% in 2026, Totaling $6.37 Trillion | Gartner newsroom (market context only)
  3. Telecom Expense Management | RadiusPoint
  4. ExpenseLogic | RadiusPoint
  5. Managed Mobility Services | RadiusPoint
  6. About | RadiusPoint
  7. RadiusPoint Capability Statement | RadiusPoint
  8. Sharon Watkins | RadiusPoint

This article is educational. RadiusPoint does not guarantee a rollout date, a week count, or a savings percentage. Figures were current as of 28 August 2026.

professionals present financial charts meeting 1

Telecom Expense Management Companies: How to Choose the Right Partner

TEM0

Telecom expense management companies fall into three business models: software platforms you operate yourself, managed service providers who run the process on your behalf, and audit firms who recover refunds once and leave. The right choice depends less on features than on whether your team has the staffing to work the platform every month.

That single distinction explains most failed TEM programs. Buyers evaluate telecom expense management companies on dashboards and integrations, sign a software contract, and then discover that nobody internally owns invoice validation, dispute filing, or inventory reconciliation. The platform reports the variance. It does not resolve it. Twelve months later the savings case has not materialized and the tool gets blamed for a resourcing decision.

Key Takeaways

  • Vendor business model predicts outcomes better than feature comparison. Software-only, managed service, and contingency audit are three different purchases.
  • Ask what percentage of invoices the vendor validates line by line, not what percentage they load.
  • Recovery is a one-time event. Avoidance is recurring. Contracts priced purely on recovery share incentivize the wrong behavior.
  • Inventory accuracy is the leading indicator. A vendor who cannot reconcile services to assets cannot validate anything downstream.
  • Implementation length is a proxy for how much work the vendor is actually absorbing.

The Three Business Models Behind Every TEM Vendor

Every telecom expense management provider you will shortlist sits in one of three categories. Vendors rarely describe themselves this way, because each model has a weakness the sales conversation is built to avoid. Categorizing them first makes the shortlist honest.

Model What you buy Who does the work Fails when
Software platform (SaaS) A licensed system for invoice loading, inventory records, and reporting Your internal telecom or finance analysts You have fewer than one full-time analyst per 2,000 lines or 300 circuits
Managed service An outcome: validated invoices, filed disputes, maintained inventory, allocated cost The vendor’s analysts, using their platform Governance is loose and nobody on your side reviews the vendor’s output
Contingency audit A one-time historical review, paid as a share of refunds found The audit firm, for a fixed engagement window You treat a single recovery event as an ongoing cost control program

Hybrids exist. Several platform vendors attach a professional services team, and several audit firms have built software front ends. The test is not what the vendor sells alongside the core product. The test is what happens on the fifteenth of the month when a carrier invoice arrives with 400 unexpected line items. Someone has to open it, compare it to contracted rates, compare it to the inventory of record, and file the dispute inside the carrier’s window. Ask the vendor to name that person.

A platform tells you the invoice grew nine percent. A managed service tells you which four circuits caused it, whether the charge is contractually valid, and that the credit request was filed on the eleventh.

Where RadiusPoint Sits in the Market

RadiusPoint delivers telecom expense management as a fully managed service built on ExpenseLogic, its proprietary cloud-based platform. ExpenseLogic centralizes invoice processing, inventory tracking and contract management in a single configurable dashboard. The platform automates invoice validation, reconciliation and cost allocation, which drives efficiencies, reduces expenditure and improves visibility for finance and IT leaders. Organizations using ExpenseLogic gain end-to-end control over telecom assets, workflows and spend, and integrate validated charges seamlessly into their ERP and accounts payable systems.

RadiusPoint audits one hundred percent of invoice line items rather than sampling, files disputes directly with carriers on the client’s behalf, and maintains the inventory of record as moves, adds and changes occur. The company also manages utility and mobility spend on the same telecom expense management platform, so a single reconciliation process covers telecom, wireless and facility invoices. That scope matters for organizations whose real problem is fragmented ownership across IT, finance and facilities rather than a shortage of reporting.

How to Compare Telecom Expense Management Software

When buyers search for the best telecom expense management software, they usually receive feature grids. Feature grids are easy to win and hard to verify. A more useful comparison walks the invoice lifecycle and asks, at each stage, whether the vendor performs the step, reports on the step, or leaves it to you.

Lifecycle stage The question that matters Weak answer Strong answer
1. Invoice capture How do invoices arrive, and what happens to the ones that do not parse? “We support EDI and PDF.” “Exceptions route to a named analyst within one business day.”
2. Validation What share of line items is checked against contracted rates? “We flag anomalies.” “One hundred percent, against the rate table we maintain from your contracts.”
3. Inventory reconciliation How is the inventory of record kept current? “Customer uploads a spreadsheet.” “We update from carrier orders and MAC activity, and audit against invoices monthly.”
4. Dispute management Who files the credit request, and who follows it? “We generate a report you can send.” “We file, track and escalate until the credit appears on an invoice.”
5. Cost allocation Can charges split to cost center, location and GL account without manual work? “Export to Excel.” “Rules-based allocation feeding your ERP in your chart of accounts.”
6. Payment and accrual Does the system support approval workflow and accrual entries? “We show what is due.” “Approved, coded, and posted through an AP integration.”

Score each stage as performed, reported, or unaddressed. A platform that reports on all six and performs none of them is a legitimate purchase for an organization with a staffed telecom team. For everyone else it is a reporting layer over an unsolved problem.

Evaluation Criteria That Actually Predict Outcomes

Audit depth, not audit language

Nearly every vendor uses the word audit. The meaningful variable is coverage. Sampling catches systemic errors and misses one-off charges, which is where a meaningful share of telecom billing error lives: a disconnected circuit that keeps billing, a mobile line assigned to a departed employee, a rate that reverted to list price when a contract renewed. Ask for the coverage percentage in writing and ask what happens to line items below a dollar threshold.

Inventory as the leading indicator

Invoice validation is only as good as the inventory it validates against. If the vendor cannot tell you what services exist, at which locations, under which contract, at which rate, then every downstream number is an estimate. Ask how the inventory is built during implementation, and ask what the vendor does when the carrier’s records and the client’s records disagree, because they will.

Recovery versus avoidance

Recovery is money returned for past billing errors. Avoidance is error prevented going forward. Recovery is visible, satisfying and finite. Avoidance is the reason the program pays for itself in year three. A vendor compensated only as a share of recovery has a structural reason to find refunds and no structural reason to stop the errors from recurring. Read the pricing model for that incentive before you read the case studies.

Contract and rate management

Telecom contracts carry commitments, tiers, term dates and negotiated rates that expire quietly. Ask whether the vendor loads contract terms into the rate engine or simply stores the PDF. Ask who notifies you ninety days before a term expires. Ask whether the vendor supports the negotiation itself or hands you a benchmark and wishes you luck.

Regulatory and tax handling

Telecom invoices carry a layer of surcharges, including Universal Service Fund contributions, state and local utility taxes, and carrier-imposed cost recovery fees. Some are mandated, some are discretionary, and the discretionary ones are frequently misapplied. A vendor who treats the tax block as unauditable is leaving a recurring percentage of every invoice unchecked.

Reporting your CFO will actually open

Dashboards demo well. The question is whether the output reconciles to the general ledger. If finance cannot tie the TEM report to the accrual, the report becomes a second version of the truth and gets ignored within two quarters.

What Telecom Expense Management Companies Charge, and Why the Model Matters

Pricing in this category is not standardized, which makes proposals difficult to compare on a single page. There are four common structures, and each one shapes vendor behavior in a predictable direction.

Pricing model How it works Behavior it encourages Best suited to
Per line or per invoice A unit fee applied to lines, circuits or invoices processed Neutral. Cost is predictable and scales with estate size. Stable estates with a known volume
Percentage of spend under management A share of the telecom spend flowing through the platform Rewards the vendor when your spend rises, which is the wrong direction Rarely the buyer’s friend. Negotiate a cap.
Contingency on recovery A share of credits recovered, often thirty to fifty percent Rewards finding past errors, not preventing future ones One-time historical audits
Fixed managed service fee A monthly fee for a defined scope and service level Rewards operational efficiency and clean invoices Ongoing programs where avoidance is the goal

Many contracts blend a base fee with a recovery share, which is reasonable. What is not reasonable is a structure where the vendor earns nothing in a year when your telecom spend is flat and your invoices are clean. That is the year the program is working, and it should not be the year the vendor stops paying attention.

Ask every shortlisted vendor to model three years of fees under one assumption: no recoveries after year one. The answers separate the management programs from the audit engagements faster than any feature demonstration.

Mobility, Cloud and the Expanding Scope of Expense Management

The category no longer stops at fixed-line telecom. Most enterprise estates now include a large wireless fleet, a growing SaaS and cloud subscription base, and in asset-heavy industries a utility bill volume that dwarfs telecom. Vendors have expanded into these adjacencies at different speeds and with different depth, and the labels they use are inconsistent.

  • Mobility management. Device procurement, activation, usage optimization, employee self-service, MDM or UEM integration, and end-of-life recovery. Ask whether the vendor performs device logistics or only reports on plan usage.
  • Unified communications and collaboration. Seat-based licensing for platforms billed monthly per user, where the failure mode is licenses assigned to departed employees rather than rate error.
  • Cloud and SaaS expense. Increasingly folded into technology expense management. The mechanics of validation are similar, but the contracts and consumption models are not, so depth varies widely.
  • Utility expense. Electricity, gas, water and waste invoices. Relevant to retail, healthcare, manufacturing and multi-site operators, and handled by a much smaller subset of vendors.

Scope creep in a proposal is not automatically a good thing. A vendor covering four categories shallowly is worse than one covering two categories properly. The useful question is which categories carry your largest invoice volume and your worst current visibility, then buy depth there.

The Vendor Landscape: Who Serves Which Segment

The market is not a single ranked list. Vendors cluster by the segment they were built for, and a provider that is excellent for a fifty-thousand-line global enterprise is often a poor fit for a two-thousand-line regional business, and the reverse.

Segment Typical profile What this buyer needs
Global enterprise Multi-country, multi-currency, tens of thousands of lines and circuits Local invoice formats, tax logic by jurisdiction, regional support hours, deep carrier relationships
Mid-market and upper mid-market Single country, distributed sites, a lean IT and finance team Managed execution rather than tooling, because there is no analyst to spare
Mobility-first organizations Large device fleets, modest fixed-line footprint Device lifecycle, usage optimization, MDM integration, employee self-service
Multi-site asset-heavy operations Retail, healthcare, manufacturing, utilities in scope alongside telecom One provider covering telecom, wireless and utility invoices on a single platform

Established names in the category include Tangoe, Calero, Sakon, Upland Cimpl, Brightfin, Cass Information Systems, Valicom and RadiusPoint. They are not interchangeable. Some are software-led with services attached, some are services-led with proprietary software, and some sit inside a broader payment or ITSM platform. Independent review sources such as Gartner Peer Insights and industry bodies such as AOTMP are more useful for segment fit than for ranking, because ranking depends entirely on the buyer profile.

Nine Questions to Ask Before You Sign

  1. What percentage of invoice line items do you validate against contracted rates, and will that number appear in the contract?
  2. Who on your team files disputes with carriers, and what is your average days-to-credit?
  3. How is the inventory of record established during implementation, and who maintains it afterward?
  4. What does your fee structure look like if we find no recoverable errors in year two?
  5. Which of our carriers do you already process invoices from today?
  6. What is your implementation timeline, and what does our team have to produce during it?
  7. How does validated cost data reach our ERP, and in whose chart of accounts?
  8. What happens to our data, rate tables and inventory if we leave?
  9. Can we speak to a reference of similar size, in a similar industry, who has been live for more than two years?

The ninth question does more work than the other eight. A two-year reference has been through a contract renewal, a carrier billing system migration, and at least one staffing change on the vendor side. Year-one references are still inside the honeymoon.

Red Flags in a Telecom Expense Management Contract

  • Savings guarantees with undefined baselines. A guaranteed percentage is meaningless until the baseline calculation is written down and agreed.
  • Auto-renewing multi-year terms with no performance exit. If the vendor misses agreed service levels for two consecutive quarters, you should be able to leave.
  • Data portability left unspecified. Your inventory, rate tables and dispute history are your asset. Name the export format in the contract.
  • Fees indexed to total spend under management. This quietly rewards the vendor when your spend rises.
  • Implementation scoped in weeks for a complex estate. Fast implementations usually mean the vendor loaded invoices and skipped inventory build.

If a vendor cannot explain how they will be paid in a year where your telecom spend is flat and clean, they are selling you an audit, not a management program.

Making the Decision

Reduce the choice to two variables before you look at any vendor material. First, count the internal hours per month currently spent on telecom invoice work, honestly, including the finance time spent chasing allocations. Second, count the hours the work actually requires given your line and circuit volume. If the second number is materially larger than the first, a software platform will not close the gap, because the gap is labor and not visibility.

Organizations with a staffed telecom function and a mature process buy software and get leverage. Organizations without one buy managed service and get the process. Organizations that buy software while hoping the process appears on its own are the reason telecom expense management has a reputation for underdelivering.

For a broader grounding in how the discipline works before you shortlist, start with our overview of telecom expense management, and see how a managed model handles telecom refunds and cost avoidance in practice.

Frequently Asked Questions

What do telecom expense management companies actually do?

They collect carrier invoices, validate charges against contracts and inventory, dispute errors, allocate costs to the right cost centers, and report on spend. Providers differ in how much of that work they perform versus report on.

What is the difference between TEM software and a TEM managed service?

TEM software gives your team a system to do the work. A TEM managed service assigns the vendor’s analysts to do the work for you using their platform. Software suits teams with dedicated telecom analysts. Managed service suits teams without them.

How much do telecom expense management companies charge?

Pricing typically follows one of three structures: a per-line or per-invoice subscription, a percentage of spend under management, or a contingency share of recovered credits. Many contracts blend a base fee with a recovery share. Ask how the fee behaves in a year with no recoveries, because that reveals what the vendor is really committing to.

How long does a TEM implementation take?

Typical enterprise implementations run three to six months, driven mostly by inventory build and carrier account setup rather than software configuration. A proposed timeline shorter than that usually means inventory reconciliation has been deferred rather than removed.

Can one provider handle telecom, mobility and utility expenses?

Yes. Some providers process fixed-line telecom, wireless, and utility invoices on a single platform, which removes duplicate reconciliation work when IT, finance and facilities each hold part of the spend. RadiusPoint manages all three through ExpenseLogic.

Do we still need internal staff after hiring a TEM provider?

You need an owner, not an operator. One person should review vendor output, approve disputes above a threshold, and hold the quarterly business review. Programs without a named internal owner drift regardless of how capable the provider is.

How do we measure whether a TEM program is working?

Track four numbers: invoice line items validated as a percentage of total, disputed dollars filed versus credited, inventory accuracy rate, and cost avoided against a documented baseline. Recovery alone overstates early performance and understates later performance.

What a Telecom Accrual File Is, and How Finance Teams Build One

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 24 August 2026

A telecom accrual file is a structured estimate of circuits, lines, and meters that were consumed this period but not yet invoiced, coded so the close can post. If you cannot name the unbilled service IDs at month-end, you are not accruing telecom. You are hoping last month repeats.

A telecom accrual file is the finance extract of live inventory that still lacks an invoice, not a copy of the AP pay file. RadiusPoint can provide a monthly accrual file based on the client’s accounting specifications, delivered on the client’s timing.

Key Takeaways

  • Accrued expenses are costs incurred with no invoice in hand by close. Accounts payable starts when the invoice arrives (FinQuery, 29 May 2026).
  • RadiusPoint works a missing-bill report daily and can deliver a monthly accrual file specified during setup.
  • ExpenseLogic lists accrual files next to allocation in the accounts payable module.
  • RadiusPoint processes invoices within a two-day window after receipt, which shrinks late-fee risk once the bill exists.
  • Gartner forecast $1.354 trillion in worldwide communications services spend for 2026 (Gartner, 27 July 2026).

The Short Version

Build the file from inventory and rates, not from last month’s paid total. Reverse it when the invoice lands so you do not expense the same circuit twice.

Artifact Trigger Posts to Certainty
Accrual file Service consumed, invoice missing Accrued expense Estimate
Invoice / AP file Invoice received Accounts payable Billed amount
Allocation file Either of the above, split Cost centers / GL Rule-based

In This Article

The Accrual File, Defined

A telecom accrual file is a row-level list of unbilled service IDs with amount, period, GL, and reversal flag. RadiusPoint treats it as an AP-module output, sitting beside allocation, not as a slide in a QBR.

FinQuery’s May 2026 explainer is the accounting backbone: accrued expenses exist because the benefit was consumed and the invoice was not. Utilities and usage-based services are named in that category. Telecom circuits and wireless lines behave the same way. The file is how a TEM program makes that journal auditable.

The capability statement lists accounts payable feeds, accrual files, and general ledger coding in the client’s own chart of accounts.

How do finance teams calculate the rows?

Finance calculates each accrual row from a live inventory record, a rate, and the number of unbilled days in the period. RadiusPoint’s telecom expense management stack already holds the inventory, the contract rate, and the invoice history, which is why the file can be more than a guess.

Three honest methods, in descending quality:

  1. Contract or tariff rate times the open days for that service ID.
  2. Last billed amount for the same service ID, adjusted for known MACDs.
  3. Account-level average, used only when the inventory row is still being built.

Method 3 is a placeholder. It is how most closes work today, and it is why a late $80,000 circuit makes the next month look like a miracle. Healthcare AP and ordering automation on RadiusPoint’s published record showed a 448% ROI. HumanGood, a named client, showed 315% ROI. Those figures are published process outcomes. They are not a promise that your accrual variance disappears.

Reverse the row when the invoice posts. FinQuery is blunt: accruals that are not reversed double-count. ExpenseLogic’s job is to know which invoice killed which accrual row.

Why is a missing bill an accrual row?

A missing bill on a live service is an accrual row because the inventory says you consumed it this period. RadiusPoint works the missing-bill report daily, tracks vendor conversations, and sets reminders if the invoice is still out.

Utility expense management produces the same artifact for meters. Electric, gas, water, sewer, and waste invoices arrive on their own calendars. A retail chain that closes on day six cannot wait for every utility.

Client growth from 170 to 1,200 locations is published RadiusPoint scalability proof. At 1,200 sites the missing-bill report is the close. Daily missing-bill work is also how RadiusPoint says it avoids disconnects and late fees.

Two-day invoice processing after receipt does not replace the accrual. It shortens the gap between “invoice exists” and “AP can post,” so the reversal happens inside the next cycle instead of the next quarter.

Why is last month’s total a weak accrual?

Last month’s paid total ignores new circuits, dead circuits, late credits, and every BAN that did not bill on time. RadiusPoint still sees organizations close on that number because it is available.

Gartner’s July 2026 communications services line is $1.354 trillion, growing 4.4% (Gartner newsroom). A category that large, moving 4.4%, will not land every invoice before your close calendar. The file exists because the market is late, not because finance is fussy.

Capterra lists ExpenseLogic at 4.8 from 31 reviews through December 2025 (Capterra). ISO 9001 has been in place since September 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor in 2024. Those are process credentials for a file an auditor will sample.

Organizations implementing TEM typically see 15% to 30% cost reduction in year one. That range is an industry-range statement, not a RadiusPoint guarantee. Do not put it in the accrual file as a plug.

What RadiusPoint Delivers at Close

RadiusPoint delivers the monthly accrual file on the specification collected during setup, then keeps delivering it on the client’s close calendar. Sharon Watkins has been adjacent to this problem since 1992: invoices that arrive after the period they describe.

The about RadiusPoint page is the company narrative. The operating pieces are here: inventory of record, daily missing-bill report, two-day process once the bill exists, coded GL and accrual extracts.

Ask to see last month’s accrual file and the reversals that cleared this month. If a provider cannot show both, they are sending you a spend report.

Frequently Asked Questions

What is accrual accounting, in plain terms?

Accrual accounting records revenue when you earn it and expenses when you incur them, not when cash changes hands. If your offices used power, water and phone service in March, March carries that cost even when the bills don’t show up until April. Where no invoice exists yet, finance books an estimate, called an accrual, so each month shows what the business actually used.

How is accrual accounting different from cash accounting for telecom and utility bills?

Cash accounting records a telecom or utility bill when you pay it, while accrual accounting records it in the period you used the service. IRS Publication 538, Accounting Periods and Methods (2022), says that under an accrual method you “deduct expenses in the tax year you incur them, regardless of when payment is made.” Utility bills widen the gap, because billing cycles rarely match your close calendar and each invoice arrives after the meter read.

Is the accrual file the same as the invoice upload?

No, the invoice upload is accounts payable for bills that already exist, while the accrual file estimates service IDs the vendor hasn’t billed yet. RadiusPoint produces both on the client’s file spec. Two-day invoice processing doesn’t replace the accrual either, because processing starts once the invoice exists and the accrual covers the days before it does. You need both.

What if we just accrue a flat percentage of last year?

You’ll be close in a quiet month and wrong in any month with installs, disconnects or a missing bill. A percentage of last year can’t see which services have gone live or died since then. Rows built from inventory can, because each one carries a service ID, its rate and the unbilled days in the period, so the estimate moves when the estate does.

When do you reverse the accrual?

Reverse the accrual when the matching invoice posts, or as soon as you learn the service died. FinQuery’s control point is the same: reverse in the period you expect the invoice, so the expense hits once. A row left open after its invoice posts books the same cost twice, and a row for a dead service overstates expense for a bill that won’t arrive.

Who should own utility accruals when a provider manages the bills?

Your controller should own the accrual method and sign-off, while the provider owns the bill data behind it. In Utility Expense Management (UEM), RadiusPoint runs invoice receipt and validation, meter-level audit and cost allocation in ExpenseLogic, which supplies meter-grain accrual rows for the telecom close package, often as a second file or sheet. RadiusPoint can pay vendor invoices for clients once the client funds the account. Your team still decides how to estimate unbilled usage and when to post.

Close on Inventory, Not on Hope

If the file cannot name the unbilled circuit, you do not have a telecom accrual, only a plug for the close.

Request a demo of ExpenseLogic and ask for the monthly accrual file layout plus the missing-bill report. Every close that skips those rows is another variance you will explain in the next meeting.

References

  1. Accrued Expenses vs. Accounts Payable Explained | FinQuery, 29 May 2026
  2. Gartner Forecasts Worldwide IT Spending to Grow 14.2% in 2026, Totaling $6.37 Trillion | Gartner newsroom
  3. ExpenseLogic | Capterra
  4. ExpenseLogic | RadiusPoint
  5. Telecom Expense Management | RadiusPoint
  6. Utility Expense Management | RadiusPoint
  7. About | RadiusPoint
  8. RadiusPoint Capability Statement | RadiusPoint
  9. Sharon Watkins | RadiusPoint

This article is educational. RadiusPoint does not guarantee close accuracy or a specific accrual variance.

Meter, tariff, and consumption triad for a utility bill audit

How to Audit a Utility Bill for Errors

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 22 August 2026

You audit a utility bill by testing each meter for the right multiplier, the right tariff, and billed consumption that matches interval or register data. A facilities manager who only compares this month’s account total to last month’s will miss a current-transformer ratio that has been wrong since the last meter swap.

A utility bill audit is a meter-level reconciliation of tariff, consumption, and inventory, not an account-level variance check. RadiusPoint’s utility expense management (UEM here means Utility Expense Management, not Unified Endpoint Management) is built on that grain. This page is not a telecom invoice audit and it is not vacant cost recovery.

Key Takeaways

  • Audit three things on every meter: configuration (including the multiplier), tariff or rate class, and consumption or demand.
  • EIA counted 140,491,981 U.S. AMI installations in 2024, including 16,529,599 commercial meters (EIA Table 10.05).
  • EIA’s 2022 FAQ put AMI at about 119 million installations, 72% of U.S. electric meters (EIA FAQ, updated 20 Oct 2023).
  • RadiusPoint has published $1,500 a month ($18,000 a year) recovered from utilities at closed locations, a published facilities proof point.
  • An elevator-industry client cut monthly waste expenditure 28% on RadiusPoint’s published record, which is a contract-and-tariff finding, not a tenant-transfer finding.

The Short Version

  1. List every meter behind the account, not just the account number.
  2. Confirm the meter is live and the multiplier or CT ratio matches the field tag.
  3. Test the rate class against the load profile and the signed contract.
  4. Recompute kWh, kW, and any ratchet from interval or register data.
  5. File the exception with the utility and keep it open until the credit posts.
Check Account review Meter audit
Unit of work Vendor account Meter number
Catches Duplicate bills, late fees Multiplier, tariff, demand
Misses Wrong rate class Almost none of the above
Output Pay or hold Dispute plus rate correction

In This Article

Meter Level Is the Unit of Work

A utility audit starts at the meter number because that is the device the tariff and the kWh attach to. RadiusPoint’s live UEM copy says the audit happens at meter level, not account level, which is the technical detail that separates real UEM from generic AP processing.

ExpenseLogic audits each invoice by account number, then by service ID (phone, circuit, or meter number), then by each charge on that service ID. For utilities, the service ID is the meter. If you stop at the account, a four-meter site looks like one clean bill.

EIA does not publish natural gas or water meter counts in the electric AMI FAQ, which is a useful limit: electric interval data is the richest feed, and gas, water, sewer, and waste still need a register-level check. RadiusPoint’s UEM scope is electricity, gas, water, sewer, and waste.

Sharon Watkins founded RadiusPoint in 1992 to manage telecom, technology, and utility expenses together. The meter grain is not a 2026 slogan. It is why the platform stores a site and utility equipment database.

What does a tariff check actually test?

A tariff check tests whether this meter’s rate class, riders, and contract price match the signed agreement and the load the site actually runs. RadiusPoint’s UEM audit types are contract and tariff rate audit, consumption-based audit, and threshold-based audit.

Wrong rate class is the expensive miss. A general-service schedule on a site that qualifies for a time-of-use or industrial class will look consistent every month, so a variance control never fires. Demand multipliers for kilowatt analysis matter in retail and hospitality, which is why RadiusPoint already names those verticals on the UEM page.

The capability statement lists tariff and rate class review next to meter-level invoice audit. Rate reclassification is a later article. This section only asks whether the class on the bill is the class the meter earned.

Energy Star participation is named on the live capability page as a reporting support point, not as a savings claim. Line-item invoice detail is what makes Scope 2 reporting possible. An unaudited tariff makes the carbon number as fictional as the dollar number.

How do you test demand and a ratchet?

You test demand by recomputing billed kW from interval data, then checking any ratchet or contract minimum that changed the dollars. RadiusPoint’s threshold-based audit is the sibling control: a spike that is real still has to be billed under the right rule.

A ratchet can bill this month on a peak that happened last August. Tariform’s demand-extraction note is the practical warning: the billed kW may not appear on this invoice at all. If your AP file only stores the dollar total, you cannot test the ratchet.

EIA’s 2024 commercial AMI count (16,529,599) is the pool of sites where interval data should make this test cheaper than it was on a monthly register. Estimated reads that are never trued up remain the analog failure, especially on hard-to-access meters.

A multi-location RadiusPoint client published $1,500 per month from utilities at closed locations. That is a consumption-of-zero test the account-level review will not run, because the account still looks open.

Which utility errors show up at meter level?

Meter-level utility errors cluster into eight types because utilities bill from configuration, not from intent, and the list repeats. RadiusPoint analysts research each exception with the vendor and track the credit until it posts, the same pending-credit discipline ExpenseLogic uses on telecom.

  1. Incorrect meter multiplier or CT ratio after a swap.
  2. Wrong rate class or outdated tariff.
  3. Demand ratchet or contract minimum applied after a one-off spike.
  4. Estimated read never replaced with an actual.
  5. Sales tax on an exempt manufacturing or nonprofit account.
  6. Rider billed after the site no longer qualifies.
  7. Zombie meter at a closed, sold, or demolished site.
  8. Contract price that does not match the signed agreement.

Vacancy cost recovery decreasing utility expenses by 12% is a published RadiusPoint published figure. It belongs to the vacant-cost-recovery page. It is listed here only so you do not treat a tenant-transfer miss as a tariff win.

An elevator company on RadiusPoint’s published record reduced monthly waste expenditure 28%. Waste is in the UEM scope. It is a contract-and-container audit, still at service-ID grain.

How RadiusPoint Runs Utility Expense Management

RadiusPoint runs utility expense management on ExpenseLogic as invoice receipt, meter validation, site allocation, and open-close help desk work. The about RadiusPoint page is the company story. This section is the operating loop.

ESG reporting that eliminated 800 man-hours of data gathering is a published proof point. That number is about line-item utility detail, which is the same extract a meter audit produces. It is not a promise that your next audit saves 800 hours.

Capterra rates ExpenseLogic 4.8 from 31 reviews through December 2025 (Capterra). Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. ISO 9001 has been in place since September 2002. Use those as process signals, not as a utility refund forecast.

This audit covers electric, gas, water, sewer, and waste. Telecom expense management is the sibling discipline, not this checklist.

Frequently Asked Questions

Is a year-over-year account variance an audit?

No. Variance against last month only catches jumps. A wrong CT ratio that has been stable for three years looks like the baseline. Test the meter.

Do smart meters remove the need to audit?

No. EIA’s 2024 AMI count shows how common interval data is. The data still has to be read against the tariff and the multiplier. A smart meter can bill a ratchet with more precision, not less.

What about gas, water, sewer, and waste?

The same grain applies: service ID, contract, and consumption. EIA’s electric AMI FAQ does not cover those meters, so you will lean on registers, haul tickets, and signed rates. RadiusPoint’s UEM scope includes all five.

How is this different from vacant cost recovery?

Vacant cost recovery asks who owes the bill after a tenant leaves. A utility bill audit asks whether the bill is correct for the meter that is still there. Different question, different page.

How is this different from a telecom invoice audit?

Telecom audits reconcile invoice, contract, and circuit or line inventory. Utility audits reconcile invoice, tariff, and meter inventory. RadiusPoint runs both on ExpenseLogic. Do not copy a CSR checklist onto an electric bill.

Pull Twelve Months of One Meter

Start with the messiest site you have, and write down the meter number, multiplier, rate class, and billed kW before you pay. Write down the meter number, the multiplier, the rate class, and the billed kW. If any of those four is missing, you do not have an audit file yet.

Request a demo of ExpenseLogic and ask to see a meter-level exception. Every month this goes unread is another month the same configuration bills at the same wrong rate.

References

  1. Table 10.05. Advanced Metering Count by Technology Type, 2015 through 2024 | U.S. Energy Information Administration
  2. How many smart meters are installed in the United States, and who has them? | EIA FAQ, updated 20 October 2023
  3. ExpenseLogic | Capterra
  4. Utility Expense Management | RadiusPoint
  5. ExpenseLogic | RadiusPoint
  6. Telecom Expense Management | RadiusPoint
  7. About | RadiusPoint
  8. RadiusPoint Capability Statement | RadiusPoint
  9. Sharon Watkins | RadiusPoint

This article is educational. RadiusPoint does not guarantee refunds, tariff changes, or consumption reductions. Figures were current as of 28 August 2026.

Four-step Service-ID Allocation Stack from BAN to service ID to cost centre to GL code

Allocating Telecom and Utility Costs Across Departments

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 20 August 2026

Finance teams allocate telecom and utility spend by mapping each service ID to a cost centre, then writing a coded general ledger file. A controller who dumps one billing account number into a catch-all account is coding, not allocating, and the departments will spend the next close arguing about a number nobody can defend.

Cost allocation is the rule that splits a live service across the people and sites that use it, then lands that split in the chart of accounts. GL coding is the last step, not the method. RadiusPoint builds the map inside ExpenseLogic so the file AP posts is already split.

Key Takeaways

  • Allocation starts at the service ID (circuit, wireless line, or meter), not at the invoice header or the BAN.
  • RadiusPoint can split any charge across multiple cost centres or locations, a live ExpenseLogic FAQ claim.
  • ExpenseLogic accounts payable and allocation lists allocation and accrual files as a core AP module, comparable to PeopleSoft and Great Plains interfaces.
  • A Fortune 100 manufacturer on RadiusPoint’s published record has more than 10,000 wireless devices managed globally, which is an allocation problem before it is an audit problem.
  • Gartner forecast worldwide communications services spend at $1.354 trillion for 2026, up 4.4% from 2025 (Gartner newsroom, 27 July 2026).

The Short Version

Map every circuit, line, and meter to an owner, apply a written split rule, then export a coded GL file. Do not guess a header percentage after the invoice arrives.

Step Unit What finance gets
1. BAN Carrier account The invoice envelope
2. Service ID Circuit, line, or meter The thing being paid for
3. Cost centre Department, site, project Who consumes it
4. GL code Chart of accounts Where the file posts

In This Article

The Service-ID Allocation Stack

Finance allocates recurring spend by stacking four records: billing account, service ID, cost centre, and GL code, in that order. RadiusPoint treats the service ID as the unit because that is what the carrier bills and what the inventory can prove.

ExpenseLogic stores vendors, invoice detail, payment detail, and asset inventory in one portal so the stack does not live in four spreadsheets. The RadiusPoint capability statement names cost allocation and accounting integration as a core competency: rules-based allocation to cost centre, location, and general ledger account, with coded output into the client’s ERP.

A header split (“put 30% of this BAN on marketing”) fails the first time a circuit moves or a store closes. The stack fails later, and it fails with a ticket, because the owner sits on the inventory row.

Education and higher learning are the vertical RadiusPoint already flags for chargeback complexity and manager authorisation workflows. That is the same stack with more cost centres, not a different product.

How do you split one circuit across many cost centres?

You split a shared circuit by writing a percentage rule on the service ID and applying it every cycle until owners change. RadiusPoint’s live TEM FAQ states that any charge can be split between multiple cost centres or locations.

A worked example, invented only as arithmetic on a published capability (circuit split-billing), not as a client result: a $4,800 MPLS circuit used by Finance (25%), Operations (40%), Sales (20%), and an IT backbone share (15%) becomes $1,200 / $1,920 / $960 / $720. The next month uses the same rule unless a MACD ticket changes the owners.

That is chargeback. Chargeback is the conversation with the department. Allocation is the rule that makes the conversation short. RadiusPoint’s telecom expense management lifecycle already lists cost allocation next to invoice audit and payment.

Client growth from 170 to 1,200 locations is a published RadiusPoint scalability proof. At that span, a shared circuit without a written split becomes a monthly argument, not a file.

Why does a header split fail at month-end?

A header split fails at month-end because the BAN no longer matches who used each circuit or meter this period. RadiusPoint will create an upload file that interfaces with the client’s current accounting software for proper allocation, which is the live FAQ answer to “will our AP team key this.”

Coding without a split dumps the BAN into one account and leaves finance to journal the rest. That is the pain the AP director already has: volume, exceptions, manual GL coding, late fees. ExpenseLogic’s AP module is built to remove the keying, not to invent a new chart of accounts.

Gartner’s July 2026 forecast puts worldwide IT spend at $6.37 trillion and communications services at $1.354 trillion (Gartner, 27 July 2026). A 4.4% rise in communications spend is a budget variance problem if last year’s dump account is this year’s “actual.”

Three-way match asks whether the invoice agrees with a purchase order. Allocation asks which cost centre owns a service that never had a purchase order.

How do you allocate a wireless line after someone leaves?

You allocate a departed employee’s wireless line to that person’s last cost centre, then stop the billing and recover leftover months. RadiusPoint’s managed mobility services invoice processing is allocated down to phone number and Employee ID for that reason.

ExpenseLogic can validate a monthly HR roster of valid employee IDs against devices and lines in the repository. That is an allocation control, not a mobility slogan. A food service client on RadiusPoint’s published record had more than 600 lines audited and a 22% cost reduction ($400,000 year one). Those lines had to land somewhere after the audit.

A Fortune 100 wireless discovery story on the same published record shows $830,000 in annual savings. Discovery without allocation just moves the leak into a different GL bucket.

Capterra lists ExpenseLogic at 4.8 from 31 reviews through December 2025 (Capterra, ExpenseLogic). Reviewers who care about AP files care about this grain, not about a dashboard colour.

Utility Meters Need a Different Grain

Utility allocation belongs on the meter number and the site, because one vendor account can hide five meters and a vacant wing. RadiusPoint’s utility expense management (UEM here means Utility Expense Management, not Unified Endpoint Management) allocates cost to location, department, and meter number.

A multi-location RadiusPoint client published $1,500 a month, $18,000 a year, from utilities at closed locations. That finding is an allocation failure first: the meter was still mapped to an open cost centre. This page only needs the grain: meter, not account.

EIA counted 16,529,599 commercial AMI meters in 2024, inside 140,491,981 total AMI installations (EIA Electric Power Annual, Table 10.05). More interval data does not allocate itself. Someone still has to own the meter in the file.

RadiusPoint also houses deposit information by meter and service type, which is another allocation-adjacent record AP rarely sees until a site closes and the deposit never returns.

What RadiusPoint Puts in the Interface File

RadiusPoint delivers a coded upload file on the client’s own chart of accounts, ready for AP to load without re-keying lines. ExpenseLogic writes the spec file to the client’s ERP (PeopleSoft, Great Plains, JD Edwards, and others named on the certifications page) so AP does not re-key.

Sharon Watkins founded RadiusPoint in January 1992 and still treats ExpenseLogic as the place the allocation rule lives. The company’s published posture is software plus people: analysts maintain the inventory so the file stays true after a move.

ISO 9001 certification since September 2002 is the process claim behind a file you can hand an auditor. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. Neither fact is a savings guarantee. Both are reasons the interface file is a product, not a favour.

Ask for one month of invoices allocated at service-ID grain. If the file cannot name the circuit, the line, or the meter, it is a journal entry dressed as TEM.

Frequently Asked Questions

Is GL coding the same as cost allocation?

No. GL coding is the account the journal hits. Allocation is the rule that decides how much of a circuit, line, or meter belongs to each cost centre before that account is chosen. RadiusPoint runs the rule, then writes the code.

Can one circuit hit more than one department?

Yes. RadiusPoint’s live FAQ says any charge can be split across multiple cost centres or locations. The split sits on the service ID so it repeats every cycle until a ticket changes the owners.

Where do wireless lines get charged?

To the phone number and the employee ID, then to that person’s cost centre. Pooled BAN totals cannot survive an offboarding month. ExpenseLogic can test a monthly HR roster against the inventory.

How should utility invoices be allocated?

At meter number and site, not at the vendor account. Utility expense management (not Unified Endpoint Management) is the RadiusPoint name for that grain. Closed-location bills are an allocation miss before they are a recovery project.

What does AP actually receive from RadiusPoint?

An upload file specified during setup, coded to the client’s chart of accounts, so the team does not key invoice lines.

If the File Cannot Name the Circuit, Stop

Allocation that starts at the BAN will be re-litigated every close, because no service ID owns the dollars on that file. Start at the service ID, write the split, export the file.

Request a demo of ExpenseLogic and ask to see one circuit split and one meter coded. Sharon Watkins has been building that file since 1992. The cost of another guessed header is another month of the same argument.

References

  1. Gartner Forecasts Worldwide IT Spending to Grow 14.2% in 2026, Totaling $6.37 Trillion | Gartner newsroom, 27 July 2026
  2. Table 10.05. Advanced Metering Count by Technology Type, 2015 through 2024 | U.S. Energy Information Administration
  3. ExpenseLogic | Capterra
  4. ExpenseLogic | RadiusPoint
  5. Telecom Expense Management | RadiusPoint
  6. Utility Expense Management | RadiusPoint
  7. Managed Mobility Services | RadiusPoint
  8. RadiusPoint Capability Statement | RadiusPoint
  9. Sharon Watkins | RadiusPoint

This article is educational. RadiusPoint does not guarantee savings, allocations, or close dates. Figures were current as of 28 August 2026.

Wireless Expense Management vs Telecom Expense Management (WEM vs TEM): Which Scope Do You Need?

Uncategorized0

Two published RadiusPoint cases cut costs by more than 20%, and they came from opposite sides of the telecom bill. A food service company saved 22% in monthly costs, over $400,000 a year, on a wireless estate where services for 56 users no longer employed were still paid monthly. A healthcare organization cut its annual spend 26% by deactivating over 700 dormant regular business lines.

Wireless expense management vs telecom expense management comes down to scope: wireless expense management (WEM) is the part of telecom expense management (TEM) that covers wireless services and mobile devices, while TEM covers wireless, wireline and data circuits together. Managed mobility services (MMS) sit beside both and manage the devices themselves.

RadiusPoint covers all three on ExpenseLogic, a single cloud platform for telecom, wireless and utility expenses. Wireless invoices are allocated down to phone number and Employee ID, and contracts and rates are tied to service IDs.

Key Takeaways

  • The Enterprise Technology Management Association (ETMA) calls WEM programs a special category of TEM programs focused on wireless services and mobile devices, with goals similar to TEM’s.
  • WEM tracks lines by phone number and Employee ID; TEM adds service IDs, contract terms, accrual files and general ledger (GL) interface files across wireline, wireless and data circuits.
  • RadiusPoint’s Fortune 100 wireless case, with some 10,000 devices, identified and reconciled over $450K in refunds and saves $830K+ a year from exception reporting alone.
  • The healthcare 26% came from over 700 dormant regular business lines, which makes it wireline TEM proof, not a wireless result.

Short version: scope wireless expense management first when the unexplained charges sit on mobile lines, buy full TEM when circuits, contracts and month-end files are also in play, and add managed mobility services when the devices themselves need managing.

WEM vs TEM: How Do Wireless and Telecom Expense Management Compare?

Wireless expense management covers mobile plans, usage and the employee behind each line, while telecom expense management covers every wireless, wireline and data circuit invoice. Managed mobility services add the device itself. Each keys its records differently: by phone number, by service ID or by device serial number.

Compared on Wireless expense management (WEM) Telecom expense management (TEM) Managed mobility services (MMS)
What it covers Wireless services and mobile devices Wireline, wireless and data circuit invoices, from order placement to payment The device lifecycle, from procurement to retirement, plus the wireless billing that follows
Inventory key Phone number and Employee ID Service ID, with contract rates tied to it Device serial number and Employee ID
What it checks Plan fit against usage, voice and data pooling, roaming, call tagging, unused lines from HR feeds and carrier usage Every invoice line against contracted rates and inventory, contract expiration dates, missing bills, closed-location billing Zero-use devices, ex-employee lines against the HR roster, annual line registration, wireless policy
Output finance gets Costs by line and employee, with personal calls tagged for payroll deduction or reimbursement Monthly accrual files, GL interface files, circuit split-billing across cost centers Wireless invoices allocated down to phone number and Employee ID
Published RadiusPoint case that fits Fortune 100 manufacturer: some 10,000 wireless devices, over $450K in refunds, $830K+ a year from exception reporting alone Healthcare: over 700 dormant regular business lines, 26% of annual spend. Glass manufacturer: $100K+ in year one Food service: 600+ phones, 22% in monthly costs, over $400,000 a year

Is Wireless Expense Management Part of TEM?

Yes, wireless expense management is part of TEM: the same invoice discipline applied to wireless services and mobile devices, sometimes bought under its own name. ETMA describes WEM programs as “a special category of Telecom Expense Management (TEM) programs with a focus on wireless services and mobile devices.”

RadiusPoint’s guide to what telecom expense management is puts it the same way: wireless expense management is the mobile subset of TEM, and adding device procurement, staging, support and recovery turns it into MMS.

The published cases bear this out. The Fortune 100 client’s video case study says the work began as a one-time audit that obtained refunds on its wireless expenses, then continued as monthly telecom expense management and mobility expense management. In the food service case, the video transcript says RadiusPoint took over both the client’s telecom expense management and its managed mobility services. The healthcare 26% sits on the other side: the case page credits over 700 dormant regular business lines, a TEM result from wireline service.

Wireless Expense Management Adds Checks Built Around Each Employee

Wireless expense management adds checks that follow the employee: plan fit, pooled data, roaming, personal calls and lines still billing after someone leaves. ETMA calls matching the monthly service plan to employee usage critical, notes that carriers may offer pooling for voice and data, and warns that roaming charges outside the home network can lead to bill shock.

ETMA also describes WEM programs that use HR feeds and carrier usage to identify unused lines, notifying managers of devices assigned to former employees with no use at 60 or 90 day increments. ExpenseLogic validates Employee IDs against a monthly HR roster, and RadiusPoint’s mobility capabilities include zero-use device identification and annual line registration (see how to find zero-use mobile lines).

Both wireless cases show these checks at work. In the Fortune 100 wireless case, a Register Your Line cloud database tied each device to a cost center and a verified employee ID, and monthly wireless activity reports with rate plan information and call records gave the client a basis to ask for reimbursement of personal calls. The food service case used a Register Your Line portal with a 60-day register-or-cancel notice; owing to the number of employees and missing data, the process took two months.

Full TEM Covers the Circuits, Contracts and Month-End Files

Full TEM goes past the wireless bill to wireline service, data circuits, carrier contracts and the accrual and GL files behind month-end close. Contracts and rates tie to service IDs, so each invoice line can be checked against what was agreed, whether it bills a handset or a circuit.

RadiusPoint’s telecom expense management service covers line-item audit across wireline, wireless and data circuits against contracted rates and inventory; MACD (move, add, change, disconnect) ticketing with client-defined approval workflows; vendor contract management with contract obligation alerts; circuit split-billing across cost centers; closed-location billing exception reports; daily missing-bill reporting; deposit tracking; and monthly accrual and GL interface files. RadiusPoint can pay vendor invoices for clients once the client funds the account.

Two published wireline cases show what that scope finds. A global glass manufacturer with 200+ retail locations had been ordering services location by location with no corporate contracts. RadiusPoint found six call-forward lines from a location closed for years, at about $67 per call-forward service, and ordering moved to the MACD portal. The client saved $100K+ in year one, and its return on investment (ROI) has been over 200%. In the healthcare case, the 26% (or $475k once the lines were disconnected and removed from the invoices) came from over 700 dormant regular business lines.

When Do Wireless Expense Management Services Make Sense on Their Own?

Wireless expense management services make sense on their own when a statement of work (SOW) describes problems on mobile lines, not circuits or utility meters. The verbs in a SOW or request for proposal (RFP) point to the scope, and each scope maps to a capability.

Wording in the SOW or RFP Scope it points to Capability it calls on
Audit the wireless carrier invoices, match lines to the HR roster, cancel zero-use lines Wireless-focused scope Employee ID validation against a monthly HR roster; zero-use device identification; rate plan optimization
Process every billing account number (BAN), allocate to cost centers, produce an accrual file Full TEM Line-item audit across wireline, wireless and data circuits; monthly accrual and GL interface files
Track carrier contracts, expiration dates and termination fees Full TEM Vendor contract management; contract obligation alerts
Procure, stage, kit, repair, recover and recycle devices MMS Device and inventory management by serial number and Employee ID; help desk
Audit electricity, gas, water, sewer and waste bills Utility Expense Management (UEM) UEM on the same ExpenseLogic platform

Where Do Managed Mobility Services Fit Beside WEM and TEM?

Managed mobility services sit beside WEM and TEM, covering the device’s life from procurement to retirement along with the wireless billing that follows it. Buy MMS when the device, not only the bill, needs managing, because staging, kitting, repair and recovery are hands-on work that no invoice audit performs.

RadiusPoint’s managed mobility services add device and inventory records by serial number and Employee ID across smartphones, tablets and wearables. The food service case shows why the two meet: lost devices and in-stock devices were still billed monthly, a device problem and a billing problem at once. Mobile device management (MDM) is a separate purchase: it controls and secures the device, while WEM governs the bill.

How RadiusPoint Covers WEM, TEM and MMS on One Platform

RadiusPoint covers WEM, TEM and MMS on ExpenseLogic, a single cloud platform for telecom, wireless and utility expenses, with RadiusPoint staff working the invoices. The Wireless Management module stores device detail and audits line contracts, and the Accounts Payable module handles allocation and accrual files for finance.

The same staff chase the carriers, file the disputes and close the tickets in the ExpenseLogic platform. RadiusPoint was founded in 1992 by Sharon R. Watkins, who works directly with the software development team, and it’s a women-owned business. ExpenseLogic holds a 4.8 rating on Capterra from 31 reviews, with reviews through December 2025, and Amalgam Insights named RadiusPoint a Distinguished Vendor on its 2024 TEM Vendor SmartList.

Every billing cycle a departed employee’s line or a closed site’s circuit stays active adds another charge nobody approved. Request a free demonstration to see the Wireless Management and Accounts Payable modules in ExpenseLogic.

Frequently Asked Questions

Is mobility expense management the same as wireless expense management?

Yes, in practice mobility expense management, mobile expense management, wireless telecom expense management and wireless expense management describe the same work on mobile lines and devices. In managed mobile expense management, the work is delivered as a service, with staff, not only software, working the invoices and carrier disputes.

Does wireless expense management include buying and repairing phones?

Wireless expense management doesn’t include buying or repairing phones on its own: WEM governs the bill, the plan and the user record, while procurement, staging, kitting and repair belong to managed mobility services. ETMA notes that some WEM programs manage device retirement through recycling, so the two overlap at the end of a device’s life.

Can one platform handle wireless and wireline invoices together?

Yes, one platform can handle both: ExpenseLogic runs line-item audit across wireline, wireless and data circuits against contracted rates and inventory. Wireless invoices are allocated down to phone number and Employee ID, contracts and rates tie to service IDs, and the platform produces monthly accrual and GL interface files for the accounting system.

Where do utility bills belong if they aren’t telecom or wireless?

Utility bills belong in UEM, not WEM or TEM. UEM covers electricity, gas, water, sewer and waste, and its audit happens at the meter level rather than the line or circuit. RadiusPoint runs UEM on the same ExpenseLogic platform as telecom and wireless, so a company can keep all three expense categories in one system instead of three.

References

  1. Enterprise Technology Management Association (ETMA), “What is Wireless Expense Management (WEM)?,” April 1, 2021. etma.org
  2. RadiusPoint, “Wireless Discovery and Optimization Saves $830K Annually,” March 4, 2023.
  3. RadiusPoint, “$1.3M in Telecom Refunds and Cost Savings: Case Study,” June 10, 2023.
  4. RadiusPoint, “How Managed Mobility Services Cut Costs 22% ($400K in Year 1),” May 15, 2023.
  5. RadiusPoint, “Healthcare Case Study: Telecom Expenses Down by 26% in Healthcare,” December 28, 2023.
  6. RadiusPoint, “Glass Manufacturer Saves $100K On Telecom Expenses,” May 22, 2023.
  7. RadiusPoint, “What Is Telecom Expense Management (TEM)? How It Works and What It Saves,” accessed October 2026.
  8. RadiusPoint, “About RadiusPoint,” accessed October 2026.
  9. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews, accessed October 2026. capterra.com
  10. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com

This article is general information for finance, IT and telecom buyers, not legal or contract advice. RadiusPoint outcomes cited here come from specific published client engagements on the case pages listed in References, and results vary by organization.

Editorial grid of handset tiles with three dark zero-use lines

Zero-Use Mobile Lines: How to Find Ex-Employee and Ghost Lines Still Billing

Uncategorized0

California’s unemployment agency had the warning in hand. Its wireless carrier sent monthly reports of devices with no use for three consecutive months, yet the branch holding them said its staff didn’t check usage. Over 54 months, the Employment Development Department (EDD) paid $4,623,352 in service fees for 6,285 devices unused four or more consecutive months, according to California’s State Auditor.

Zero-use mobile lines are corporate wireless numbers that keep billing with no calls, texts or data in a review period your policy sets, because the person or device behind them is gone or the line was never meant to be busy. Finding them takes a match, not a report: each billed line checked against a current employee, a device and recent usage.

RadiusPoint handles this through the managed mobility capabilities in ExpenseLogic, including zero-use device identification, ex-employee line detection through HR roster reconciliation and annual line registration. In one published RadiusPoint case, a food service company cut monthly costs 22%, more than $400,000 a year.

Key Takeaways

  • A quiet line can belong to someone who left, to no one (a ghost line), or to an alarm or backup system meant to sit idle; each needs its own next step.
  • California’s State Auditor found EDD paid $4,623,352 for 6,285 devices unused four or more consecutive months, and recommended ending service on devices unused more than 90 days.
  • In RadiusPoint’s food service case, an audit of more than 600 lines found 56 identified users no longer employed by the company, and monthly costs fell 22%, more than $400,000 a year.
  • A Fortune 100 company that tied about 10,000 wireless devices to verified employee IDs recovered more than $450,000 in refunds and saves more than $830,000 a year.

Short version: match every billed mobile line to a current employee, a device and recent usage each month, cancel the ex-employee and ghost lines your policy allows, check quiet lines that may serve alarms or backup paths first, and confirm on later invoices that the charges stopped.

How Do You Match Every Mobile Line to the HR Roster?

Match each billed phone number to an Employee ID on the current HR roster, a device on record and its usage in your review period. A line that fails any check goes on an exception list. Usage says a line is quiet; the roster and the device record say why.

Field Where it comes from What a miss looks like
Phone number Carrier invoice for each billing account number (BAN) Bills on the invoice but is missing from your line inventory
Employee ID This month’s HR roster Assigned to a terminated ID, or to none
Device serial number Device inventory or carrier device detail No device on record, or the device is listed as lost or in storage
Usage in the review period Carrier usage detail or nonusage report No calls, texts or data in the period your policy sets
Cost center HR roster or finance chart of accounts Charged to a closed department or one that doesn’t employ the user

Match on Employee ID, not name: names change and repeat, while an ID stays with one person. The Fortune 100 company in RadiusPoint’s wireless discovery case registered about 10,000 devices in a cloud database that assigned each one to the correct cost center and tied it to a verified employee ID. ExpenseLogic validates Employee IDs against a monthly HR roster and allocates invoices down to the phone number and Employee ID, the field that drives cost allocation.

Ex-Employee, Ghost and Quiet System Lines Each Need a Different Next Step

Sort each flagged line by why it’s quiet, since ex-employee lines, ghost lines and quiet system lines call for different next steps. A ghost line has no current user and no device behind it. Treating them alike either leaves charges running or takes an alarm or backup connection offline.

Line type What to check Typical next step under your own policy
Ex-employee line HR shows the person left, yet the number still bills Recover the device, keep the number only if the business needs it, then suspend or cancel
Ghost line (no user or no device) No roster match, no device on record and usually no usage Send a registration notice with a deadline; cancel what nobody claims
Quiet system or backup line Little or no use, but tied to an alarm, elevator, payment terminal or failover connection Name the system owner and site first; keep it and recheck at your next review

RadiusPoint’s food service case shows how the first two types pile up. Auditing more than 600 lines, RadiusPoint identified 56 users no longer employed by the company, some gone more than two years, plus a separate set of more than 50 lines no longer associated with the company that should have been canceled. Lost wireless and paging devices were still billed monthly, and numerous in-stock devices were billed monthly with no assigned user. Some older phones couldn’t be recovered, so the company let them go and canceled those services anyway.

Why Didn’t a Monthly Nonusage Report Stop California’s Bills?

California’s EDD received a carrier report flagging devices unused for three consecutive months, but the branch holding them didn’t check usage, so fees kept running. A usage report finds quiet lines. It can’t say who should have them, so it can’t cancel anything by itself.

One EDD official told the State Auditor the department began receiving the carrier’s nonusage reports in 2017. More than half the devices its unemployment insurance branch acquired went unused for at least two years, and 99 were never used. As of April 2025, that branch had 1,787 call representatives while EDD still paid for 5,097 of the devices.

That month, EDD ended service for 2,825 devices and had its IT branch start ending any line unused for 90 consecutive days, a process it made departmentwide policy on September 3, 2025. Federal agencies showed the same gap in 2015, when the U.S. Government Accountability Office (GAO) found only 1 of 15 federal agencies it reviewed had documented procedures for reviewing devices and plans for “overuse, underuse, or zero use.”

Which Quiet Lines Need a Second Check Before You Cancel?

Check any quiet line that might serve an alarm panel, elevator phone, payment terminal or backup internet connection before canceling it. These lines can sit idle for months by design, so zero use doesn’t prove they’re unneeded. A wrong cancellation shows up during an emergency or an outage.

Four clues point to a system line:

  • The device is a modem, router or alarm communicator, not a handset.
  • The plan is data-only, with small, regular data sessions and no calls.
  • It’s charged to a site or facilities cost center, not a person.
  • No one on the HR roster claims it, but a site manager knows the number.

Record the system, site and owner in the line inventory, keep the line until that owner signs off, and recheck it at each review.

What Proves a Canceled Line Actually Stopped Billing?

A canceled line is only finished when the invoices that follow no longer show its monthly recurring charge (MRC) or any new usage. A closed ticket or carrier confirmation proves a request was made; only the next bill proves the charge stopped.

On the next invoice, look for three things: the MRC is gone, any partial-month credit matches the cancellation date, and no unexpected early termination fee or device payment appears. If the MRC is still there, the disconnect didn’t take. ExpenseLogic’s MACD (move, add, change, disconnect) ticketing with client-defined approval workflows keeps each request on record, and a monthly invoice audit catches cancellations that never reached the bill.

Past months are separate. In the food service case, some former employees had been gone more than two years, so their lines had billed more than two years of monthly charges. Canceling stops the next charge, not the earlier ones. Recovery depends on the carrier’s dispute terms, and a third party filing disputes typically works under a letter of agency (LOA) that names the accounts it covers.

Annual Line Registration Keeps the Line Count From Growing Back

Annual line registration asks every user to claim their line and device each year, so unclaimed numbers surface on a deadline, not years later. A one-time cleanup fixes today’s list. A yearly registration, backed by a written wireless policy, keeps it from drifting as people join, move and leave.

RadiusPoint includes annual line registration in its managed mobility services, along with wireless policy creation and enforcement and ExpenseLogic device inventory by serial number and Employee ID. In the food service case, employees registered their lines and devices through a Register Your Line portal and were told unregistered lines would be canceled after 60 days. Owing to the number of employees and missing data, the process took two months.

The audit also found phones employees had bought and expensed at non-contract rates about 30% higher, and moving them onto the corporate contract saved about 30% on those lines. The client had one person who managed the phones at their site, distributed them and ordered the services, and RadiusPoint helped write a wireless policy covering procurement and terms.

Pull the Invoices and the Roster Before the Next Wireless Bill Closes

Pull last month’s wireless invoices for every billing account and this month’s HR roster, then match each line to a current employee and a device. The lines that don’t match, minus quiet system lines, become your first cancellation list. If the records you have can’t support that match, fix the inventory first.

RadiusPoint was founded in 1992 by Sharon Watkins. The ExpenseLogic platform holds a 4.8 rating from 31 reviews on Capterra, and Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 Vendor SmartList for Telecom Expense Management.

Every month an ex-employee’s line stays active adds another charge for a phone nobody answers. Request a free demonstration to see zero-use device identification and HR roster reconciliation in ExpenseLogic.

Frequently Asked Questions

How long should a line sit unused before you cancel it?

There’s no universal rule; write the window into your wireless policy. California’s State Auditor recommended EDD end service for devices unused more than 90 days, and its carrier flagged devices after three consecutive months. Seasonal roles, spare devices and system lines may justify a longer window, as long as each exception has a named owner.

Should you suspend a line or cancel it right away?

Suspend when the business may still need the number, such as a customer-facing line, a device you expect back or a legal hold. Cancel when nobody needs it. Suspension rules and any charges vary by carrier, so check your agreement. The RadiusPoint help desk handles line suspensions, and MACD tickets in ExpenseLogic record each request.

Do tablets, wearables and pagers count as zero-use lines?

Yes, if they carry a monthly plan, because they bill like a phone line and go quiet the same way. ExpenseLogic’s device inventory covers smartphones, tablets and wearables, and RadiusPoint’s food service case found pagers unaccounted for in the wireless program. California’s State Auditor counted wireless hotspots among the 7,224 devices EDD procured by December 2020.

Will mobile device management software find zero-use lines?

Not on its own. Mobile device management (MDM) software secures and controls enrolled devices, while the charge comes from the carrier invoice. A line with no enrolled device may never appear in an MDM console. Finding those takes the invoice, the HR roster and the device inventory side by side.

References

  1. RadiusPoint, “How Managed Mobility Services Cut Costs 22% ($400K in Year 1),” May 15, 2023.
  2. RadiusPoint, “Wireless Discovery and Optimization Saves $830K Annually,” March 4, 2023.
  3. RadiusPoint, “Managed Mobility Solution & Service,” accessed October 2026.
  4. California State Auditor, “Investigations of Improper Activities by State Agencies and Employees,” Report I2025-1, December 12, 2025 (Case I2025-1099, Employment Development Department). auditor.ca.gov
  5. U.S. Government Accountability Office, “Telecommunications: Agencies Need Better Controls to Achieve Significant Savings on Mobile Devices and Services,” GAO-15-431, May 21, 2015. gao.gov
  6. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews, accessed October 2026. capterra.com
  7. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  8. RadiusPoint, “About RadiusPoint,” accessed October 2026.
  9. RadiusPoint, “Sharon R. Watkins,” author page, accessed October 2026.

General information for finance, HR and mobility teams, not legal or contract advice. Carrier terms for suspension, cancellation and disputes vary by agreement. RadiusPoint outcomes cited here come from specific published client engagements on the case pages listed in References, and results vary by organization.

Editorial still of a letter of agency document with scoped fields, no people

Telecom Letter of Agency: What It Authorizes, and How to Scope It Safely

Uncategorized0

By Sharon R Watkins · Updated 2 September 2026 · 5 min read

A telecom letter of agency (LOA) is a signed document that authorizes a third party to act on your behalf with your carriers, most often to obtain customer service records and file billing disputes. Under FCC rules a carrier must act on a valid LOA within 60 days, and the document controls exactly how much power you hand over. Scoped narrowly, it lets an auditor read your records and dispute wrong charges. Scoped loosely, it can also let someone order, change, and disconnect your services, which is far more authority than a records review needs.

The name is the first thing people get wrong, and it matters. Many vendors call this a Letter of Authorization, but the FCC’s official term in federal statute is Letter of Agency. They describe the same document, and the confusion is harmless right up until a carrier rejects a form for not matching the exact wording or record on file.

Key Takeaways

  • An LOA authorizes a third party to obtain your carrier records and act on your account. Its scope is a choice, not a fixed template.
  • For an audit or expense program, scope it to record access and dispute filing only, never to ordering or disconnecting services.
  • The details on the LOA must match the carrier’s account record exactly, or the request gets rejected.
  • The records it unlocks, customer service records, are the ground truth an audit reconciles against.
  • Number-porting LOAs and audit LOAs look similar but grant different powers. Read which one you are signing.

Short Version

The letter of agency is the key that lets a provider pull your carrier records and dispute charges without you sitting on every call. The only real decision is scope. Grant enough to read records and file disputes, and no more. A well-written LOA is narrow, specific, and time-bound; a risky one authorizes actions you never intended.

What a Letter of Agency Authorizes

A letter of agency appoints a named third party as your agent with your carriers for a defined set of actions over a defined period. At minimum, an audit-focused LOA authorizes release of your customer proprietary network information, defined in federal law as 47 U.S.C. section 222, which includes billing records, service records, and account details. That release is what lets an auditor see what you are actually being charged for, line by line.

The reason scope matters is that some LOAs go much further. Broad templates authorize the agent to order, change, and maintain services across every carrier, which is convenient for a provider and dangerous for a client who only wanted a records review. The safe default is explicit: read the records, file the disputes, touch nothing else.

The Two LOAs People Confuse

A porting LOA and an audit LOA share a format but grant different authority, and signing the wrong one causes different problems. Knowing which you are handing over is the whole point.

Porting LOA Audit / expense LOA
Purpose Move phone numbers to a new carrier Obtain records and dispute charges
Grants Authority to initiate a carrier change Authority to read records and file disputes
Main risk Data mismatch rejects the port Over-broad scope grants ordering rights
Should it allow disconnects? Only the numbers being ported No

What the LOA Unlocks: Customer Service Records

The document is administrative, but what it unlocks is the most valuable data in a telecom audit. A customer service record, or CSR, is the carrier’s own account of the services provisioned on an account, and it regularly disagrees with both the invoice and your internal records. Reconciling those disagreements is where audit findings come from, and none of it is possible until the LOA authorizes the carrier to release the CSR. This is why record access is the first real step of any telecom refund recovery effort.

How to Fill and Scope One Correctly

A clean LOA process avoids the two failure modes, rejection and over-authorization, by getting the details right and the scope tight. Work through it in order.

  1. Copy details from a recent invoice. Use the exact account holder name, service address, and account number as the carrier has them, not your everyday business name.
  2. Name the agent precisely. State who is authorized and for which accounts or number ranges.
  3. Limit the actions. For an audit, authorize record access and dispute filing. Strike ordering, changing, and disconnecting.
  4. Set a validity window. Give the authorization explicit start and end dates rather than leaving it open-ended.
  5. Sign with authority. The signer must be the person authorized to obligate the account, or the carrier can reject it.

Getting the details right is not busywork. When the information on the LOA does not match the carrier’s record, the losing or holding carrier rejects it and returns a reason code, and the entire timeline slips while you correct a mismatched address or a missing account number.

Approval workflows that replace blanket ordering rights

Keep every add, move, change, and disconnect inside an ExpenseLogic ticket routed to your named approvers, so the Letter of Agency never becomes the only control on ordering.

The objection behind most broad grants is fair: if we do not authorize ordering, how does anything get done? Ordering still happens. It happens through a control you own rather than a permission you signed away. The LOA gives the carrier a reason to accept an order. Your approval workflow decides whether that order should be placed at all.

So every move, add, change, or disconnect (MACD) runs as a ticket. Someone requests the change, the request carries its cost and justification, and it routes to the approver you have designated for that cost center or site before anything reaches the carrier. Nothing is ordered on standing authority. RadiusPoint runs this inside ExpenseLogic, so the approval trail and the resulting inventory change live in the same system as the audit.

Under a scoped LOA, RadiusPoint pulls Customer Service Records, validates invoice lines against what is provisioned, and files disputes when a charge is wrong. That work runs on inquiry and dispute rights. When a change does need to happen, RadiusPoint opens a MACD ticket in ExpenseLogic, attaches the cost and the reason, and routes it to the approver you named, so the order reaches the carrier only after your approval posts.

Where the LOA Fits in a Telecom Program

The letter of agency is the authorization layer underneath most telecom expense work, which is why it usually gets signed early in onboarding. It enables the record pulls that feed inventory, it authorizes the disputes that recover money, and its scope should be coordinated with your MACD process so that ordering and disconnecting stay under internal control while records and disputes are delegated. When RadiusPoint begins a telecom engagement, the LOA is scoped to exactly that: authority to obtain customer service records and file disputes, gathered as part of the standard onboarding data set, with service-ordering authority deliberately left with the client.

Frequently Asked Questions

Is a Letter of Agency the same as a Letter of Authorization?

Yes, in practice. Letter of Agency is the FCC’s official term in federal regulation, and Letter of Authorization is a widely used synonym for the same document. Use whichever term your carrier’s form uses to avoid a wording mismatch.

How long is an LOA valid?

For as long as the document states, which is why you should set explicit start and end dates. Open-ended authorizations are harder to control and should be avoided for anything beyond a specific, time-boxed engagement.

Does an LOA let a provider disconnect our services?

Only if the LOA says so. A well-scoped audit LOA does not grant disconnect authority. If a template includes ordering, changing, or disconnecting language and you only want a records review, remove it before signing.

How fast must a carrier act on an LOA?

Federal rules require a carrier to submit a preferred carrier change order within 60 days of receiving a valid letter of agency. Most carriers act within days, but 60 days is the outer regulatory limit for carrier-change requests.

What information does an LOA require?

The account holder name as the carrier has it, the service address, the account number, the numbers or services in scope, a validity period, and an authorized signature. Pulling these from a recent invoice is the reliable way to match the carrier record.

References

  • FCC, Letter of Agency terminology and preferred carrier change rules.
  • 47 U.S.C. section 222, Customer Proprietary Network Information.
  • Carrier LOA forms (Telnyx, FTS) illustrating CPNI release and broad-scope authorization language.

This article is general information and not legal advice. A letter of agency is a legal authorization; have counsel or a qualified advisor review scope and wording before signing anything that grants a third party authority over your accounts.

Four MACD tiles labeled Move, Add, Change, and Disconnect

The MACD Process in Telecom Expense Management, Explained

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 6 August 2026 · 12 min read

The MACD process in telecom expense management is the ticketed path for moves, adds, changes, and disconnects, and it fails most often on disconnects. The dispute was filed in April, resolved in September, and the overbilling had already run for 34 months on a circuit someone thought was dead. MACD is the change-control layer of telecom expense management: RadiusPoint records the request in ExpenseLogic, the carrier works the order, and finance doesn’t close the ticket until later invoices prove the charge is gone.

Key Takeaways

  • MACD means moves, adds, changes, and disconnects. A disconnect that’s requested but never proven on a later invoice is still an open financial risk.
  • RadiusPoint published $18,000 a year recovered by eliminating unneeded toll-free numbers, a classic failed-disconnect cousin.
  • Inventory work at RadiusPoint has recovered $174,000 in re-credits when the record of services did not match the bill.
  • The Disconnect Closeout Ladder has five rungs: request, firm order confirmation, final-bill sighting, invoice 2 and 3 proof, inventory retire.
  • A Fortune 100 manufacturer working with RadiusPoint recovered $450,000 in telecom refunds in year one, with $850,000 in ongoing annual savings and a $1.3 million year-one impact.

The Short Version

A MACD ticket is finished when ExpenseLogic shows the service ID gone from the next invoices, not when someone clicked submit on the carrier portal.

In this article

What MACD means in telecom expense management

MACD in telecom expense management is the four-type order set that changes the live inventory RadiusPoint bills against inside ExpenseLogic. A move relocates a service. An add provisions a new one. A change alters a feature, rate plan, or configuration. A disconnect is supposed to end the recurring charge. Outsourced telecom expense management is often bought because that four-type queue has outgrown the person who also runs the help desk.

MACD isn’t an ITSM label with a telecom accent. It’s the financial event that creates or kills a line on next month’s invoice. RadiusPoint keeps the ticket, the service ID, the BAN, and the promised due date in ExpenseLogic so the later invoice has something to match.

Organizations that implement TEM typically see 15% to 30% cost reduction in year one, a category range rather than a RadiusPoint promise. A large share of that range is inventory work, and inventory work is MACD that finally closed.

Why do disconnects fail so often?

Disconnects fail because carriers treat a submitted order as progress, while finance needs a stopped recurring charge on a later bill. RadiusPoint sees the same five breaks in ExpenseLogic: wrong service ID, wrong BAN, too little notice, the order sat in the wrong carrier queue, or provisioning stopped and billing did not.

Nothing on the invoice says “this charge is a ghost.” It looks like last month. RadiusPoint’s job is to hold the disconnect ticket open in ExpenseLogic until the charge is absent, then file for credit on the tail. Telecom audit services find disconnected-but-still-billing services as a first-audit staple. MACD is how you stop manufacturing the next crop.

RadiusPoint published $120,000 a year from contract rate optimization. That’s a rate problem. A failed disconnect is an inventory problem wearing a rate costume. ExpenseLogic has to test both.

The Disconnect Closeout Ladder

The Disconnect Closeout Ladder is RadiusPoint’s five-rung rule that a MACD disconnect is open until invoice three is clean of that service. ExpenseLogic is the ladder: each rung is a dated artifact, not a status emoji. Ranking MACD pages stop at “confirm billing stopped.” They don’t name a five-rung closeout that finance can audit. That’s the first.

Rung What RadiusPoint records in ExpenseLogic Fail if
1 Request Written disconnect with service ID and BAN Verbal only, or the ID is guessed
2 Confirmation Carrier FOC or equivalent “Submitted” with no order number
3 Final-bill sighting Invoice language that this is a closing bill Recurring MRC still present
4 Invoice 2 and 3 Two later cycles with zero recurring for that ID The charge returns under a new USOC
5 Inventory retire Service removed from the ExpenseLogic inventory of record Ticket closed, inventory still live

Rung 4 is where most in-house programs quit. RadiusPoint doesn’t. A healthcare provider working with RadiusPoint cut telecom expenses 26%. Programs that skip rungs 4 and 5 give that money back.

How do moves and adds create duplicate billing?

Moves and adds create duplicate billing when the replacement service starts before the original service is proven dead on a later invoice. RadiusPoint treats every add that replaces a live circuit as a paired MACD in ExpenseLogic: one add ticket, one disconnect ticket, one shared due date. Site upgrades and SD-WAN overlays are the usual scene. The new circuit looks like progress. The old MPLS charge keeps hitting AP.

A glass manufacturer working with RadiusPoint saved more than $100,000 in year one at a 200% ROI, a published case. Duplicate services after a move are a standard way that kind of money hides. ExpenseLogic’s inventory of record is how RadiusPoint sees two service IDs on one address.

An automotive salvage client of RadiusPoint has a published $1.3 million outcome. Large estates don’t leak through one circuit. They leak through a hundred half-closed moves.

What finance sees when a MACD ticket never closes

Finance sees a variance it can’t explain, an accrual that’s wrong, and a late fee on a service nobody asked to keep. RadiusPoint writes those finance symptoms back onto the MACD ticket in ExpenseLogic so the telecom queue and the close calendar tell the same story.

Finance symptom MACD failure underneath What ExpenseLogic should show
Unexplained MRC Disconnect never completed Open disconnect, service ID still billed
Accrual miss Add installed, invoice late Open add, no invoice match
Duplicate GL load Move billed at old and new site Two live IDs, one occupancy
Late fee Dispute held, bill unpaid Exception aging past the due date

RadiusPoint’s TEM FAQ has long claimed a two-day invoice processing turnaround. That claim only helps if the MACD record is already in ExpenseLogic when the invoice lands. Otherwise the two-day cycle just pays the ghost faster.

Who should own MACD: IT, telecom, or accounts payable?

IT should request the change, telecom should run the carrier order, and accounts payable should wait on the ExpenseLogic result. RadiusPoint sits in the middle of that triangle as the managed operator. If any one group “owns MACD” alone, you get a completed ticket and a living charge.

A CIO wants the circuit moved. A telecom manager wants the FOC. A controller wants the MRC gone. All three are correct. RadiusPoint’s about story is software plus people for that exact split: ExpenseLogic holds the record, RadiusPoint chases the carrier.

Don’t hand a blanket letter of agency to whoever owns the ticket queue. Here the rule is simpler: the person who can click disconnect isn’t the person who can declare the invoice clean.

How RadiusPoint tickets MACD inside ExpenseLogic

RadiusPoint tickets MACD inside ExpenseLogic with client-defined approvals, carrier due dates, and a close rule that waits on later invoices. The MAC ticket system is a named ExpenseLogic module. Real-estate feeds can open and close services when a location opens or closes, which is how a vacant store and a dead circuit get the same treatment. RadiusPoint analysts work the exceptions. The client sees the ticket, not a portal full of homework.

A Fortune 100 manufacturer in RadiusPoint’s published case studies managed more than 10,000 wireless devices globally. Wireless MACD is the same ladder with an Employee ID on it. Wireline MACD is the same ladder with a circuit ID. ExpenseLogic holds both.

Sharon Watkins has said the telecom industry can’t keep up with the challenges and doesn’t have time to identify savings. MACD is where that sentence becomes a queue. RadiusPoint works the queue.

FAQ

What does FOC mean on a disconnect order?

FOC is the carrier’s firm order confirmation: a dated promise that the disconnect is accepted. RadiusPoint stores the FOC on the ExpenseLogic ticket as rung 2. It isn’t proof that billing stopped. It’s proof the carrier acknowledged the request.

How long should you keep a disconnect ticket open?

Keep it open through two later invoice cycles after the promised stop date. RadiusPoint’s ladder doesn’t retire the inventory in ExpenseLogic before that. A shorter window is how ghosts return under a new code.

Can you recover charges after a failed disconnect?

Often yes, inside the carrier’s dispute window, if RadiusPoint can show the request date, the FOC, and the invoices that kept billing. Recovery is a credit. Closeout is the control that stops the next 12 months.

Is MACD the same as a change request in ITSM?

No. An ITSM change request may move a configuration item. MACD is the carrier order and the invoice result. RadiusPoint will take an ITSM feed into ExpenseLogic. The ticket isn’t done when ITSM says done.

Do wireless line disconnects follow the same MACD path as circuits?

Yes on the ladder, no on the artifacts. Wireless uses a phone number and Employee ID. Circuits use a service ID and a site. ExpenseLogic holds both. The close rule is still later invoices.

What to do before the next invoice cycle

Pull every disconnect requested in the last 90 days. Ask RadiusPoint to load them into ExpenseLogic and run rungs 3 through 5. If you can’t produce that list in a day, you don’t have a MACD process. You’ve hope.

References

  1. Telecom Expense Management | RadiusPoint
  2. What Is Telecom Expense Management? | RadiusPoint
  3. Outsourced Telecom Expense Management | RadiusPoint
  4. Telecom Audit Services: What a Line-Item Telecom Audit Actually Finds | RadiusPoint
  5. Glass manufacturer saves $100K on telecom expenses | RadiusPoint
  6. About RadiusPoint | RadiusPoint
  7. Sharon R. Watkins | RadiusPoint
  • What Is Telecom Expense Management?
  • Telecom Audit Services
  • Telecom Expense Management

Disclaimer

This article is general information for finance and telecom operations teams. It is not a promise of recovery timing or savings. Outcomes cited are from specific RadiusPoint client engagements in RadiusPoint’s published case studies.

Stacked owner-name utility bills for a vacant unit, editorial still with no people

Vacant Cost Recovery: The Utility Bills Nobody Is Watching

Uncategorized0

By Sharon Watkins, Founder and CEO, RadiusPoint · 3 August 2026 · 12 min read

Vacant cost recovery is the process that finds utility bills still sitting in the owner’s name after a tenant leaves, then assigns the rightful payer. A facilities lead opens the March electric bill for a store that closed in November and the amount has not moved. Vacant cost recovery is a Utility Expense Management (UEM, not Unified Endpoint Management) control that reconciles occupancy, account name, and meter consumption so finance stops paying someone else’s kilowatts. RadiusPoint runs that control on ExpenseLogic, the platform that holds telecom, wireless, and utility invoices in one place.

Key Takeaways

  • Vacant cost recovery is a Utility Expense Management (UEM) job: it matches occupancy to the name on the utility account, then recaptures charges the owner should not keep.
  • RadiusPoint has published vacant cost recovery work that decreased utility expenses by 12%.
  • A RadiusPoint multi-location client paid $1,500 a month, $18,000 a year, for utilities at closed locations.
  • How to check owner-name continuity uses four checks: occupancy status, account name, meter use, and the lease rule on who owes after move-out.
  • RadiusPoint’s Capterra listing sat at 4.8 from 31 reviews through December 2025, and Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList.

The Short Version

Vacant cost recovery belongs to finance and facilities together: if the account name still says owner after the unit or site is no longer yours to occupy, RadiusPoint should treat that bill as an exception in ExpenseLogic, not as rent.

In this article

What vacant cost recovery covers

Vacant cost recovery covers utility charges that stay on the owner’s account after occupancy has changed, across electric, gas, water, sewer, and waste. RadiusPoint treats vacant cost recovery as a named Utility Expense Management (UEM) control inside ExpenseLogic, not as a one-time AP write-off. The live RadiusPoint utility expense management service runs meter-level invoice receipt, tariff checks, and site open-and-close workflows. Vacant cost recovery sits on top of that feed: it asks who should be the billed party for this meter in this period.

Vacant cost recovery is the transfer problem. A utility bill audit is the tariff and consumption problem. They share invoices. They don’t share the question. RadiusPoint keeps both in ExpenseLogic so a facilities lead can see a vacant flag and a rate-class flag on the same meter without mixing the two workstreams.

RadiusPoint has been in expense management since January 1992, and the about page still frames the founding job as telecom, technology, and utility control. Vacant cost recovery is the property-management face of that same job.

Who actually owes the utility bill after a tenant leaves?

The party named on the lease and on the utility account owes the bill after move-out, and those two names often disagree for weeks. RadiusPoint starts vacant cost recovery in ExpenseLogic by putting the rent roll or site-status file next to the utility account header, then asking which name the tariff and the lease actually support. If the lease says the resident places service in their name, a bill that stays in the owner’s name after move-in is the resident’s consumption on the owner’s BAN. If the lease says the owner keeps house service during vacancy, the owner owes the vacant-period usage and should stop paying the day a new resident’s account starts.

Who owes is a document question, not a vibe. RadiusPoint doesn’t invent a payer. ExpenseLogic holds the invoice image, the meter ID, and the occupancy dates so the exception can be posted to a tenant ledger, billed back, or left as owner house cost with a reason code.

State and local utility rules differ on back-billing and on how long a landlord may leave service in the house name. This article is operations, not counsel. RadiusPoint’s job is to show the mismatch with dates attached.

How to check owner-name continuity

Owner-name continuity is checked as RadiusPoint’s four-check method that asks whether occupancy, account name, meter use, and lease still describe one payer. ExpenseLogic is where RadiusPoint stores the four inputs so the test can run every billing cycle, not once a year. No ranking multifamily VCR page we reviewed teaches this four-check sequence as a named finance test. That’s the first.

Check Source RadiusPoint loads into ExpenseLogic Pass condition
Occupancy Rent roll, PMS export, or real-estate open/close file Unit or site status is dated
Account name Utility invoice header and BAN Name matches the party who should hold service
Meter use Meter-level consumption on the same invoice Usage is plausible for vacant or occupied
Lease rule Lease clause or house-service policy Recovery path is allowed or owner cost is coded

A fail on check 2 with a pass on check 1 is classic tenant-transfer leakage. A fail on check 1 with continuing use on check 3 is a closed-site or holdover problem. RadiusPoint writes the fail type onto the ExpenseLogic exception so AP isn’t guessing.

Why do vacant-unit bills keep arriving after move-out?

Vacant-unit bills keep arriving because the utility’s customer of record doesn’t update when the lockbox does, and nobody reconciles the two files. RadiusPoint sees the same three break points in ExpenseLogic: the departing resident closed service early, the incoming resident never opened service, or the utility processed a transfer against the wrong meter.

Continuous-service agreements make the leak quieter. The lights stay on. The invoice stays in the house name. Finance pays it because the due date is real. ExpenseLogic flags the name mismatch before the payment run, which is the difference between a recovery and a donation.

RadiusPoint published a 12% decrease in utility expenses from vacancy cost recovery. That figure is the only vacant-cost percentage in RadiusPoint’s published case studies, and it’s the headline number for this page. Pair it with the closed-location case below when the estate is commercial, not garden-style.

Commercial closed-location leakage versus multifamily VCR

Commercial closed-location leakage is the same owner-name failure as multifamily VCR, except the “tenant” is your own store, plant, or branch. RadiusPoint keeps both patterns in ExpenseLogic because a retailer and a property manager hit the same meter-to-occupancy break. Ranking VCR pages in 2026 are written for apartments. RadiusPoint’s published commercial proof is different.

Pattern Who should hold the account RadiusPoint published proof
Multifamily tenant transfer Resident, per lease, after move-in Vacancy cost recovery decreasing utility expenses by 12%
Commercial closed site Nobody, once the site is dark $1,500 a month, $18,000 a year, on utilities at closed locations
Waste and refuse at closed sites Owner only while the container is still there An elevator-company engagement cut monthly waste expenditure 28%

RadiusPoint also published a client that grew from 170 to 1,200 locations. At that scale, a missed close on 1% of sites isn’t a rounding error. ExpenseLogic’s closed-location billing exception report exists for that reason. ISO 9001 certification, in place at RadiusPoint since September 2002, is how the exception process stays repeatable when the location count moves.

How should finance treat a recovered vacant cost?

Finance should post a recovered vacant cost as a dated credit or tenant charge, never as a silent cut to the utility line. RadiusPoint pushes that posting file out of ExpenseLogic so the general ledger can show recovery, house cost, and in-period usage as three different things. If you net the credit into “utilities” with no reason code, next quarter’s budget looks lucky and the control disappears.

A recovered vacant cost isn’t a tariff win. It’s a payer win. RadiusPoint keeps the two credits separate in ExpenseLogic because a rate reclass and a tenant transfer answer different audit questions. HumanGood, a named RadiusPoint client, has a published 315% ROI case. Use named cases for the program story. Use the 12% and the $18,000 figures for vacant cost recovery itself.

RadiusPoint’s capability statement lists vacant cost recovery under Utility Expense Management. That’s the correct bucket when a controller asks whether this is a TEM project.

How RadiusPoint and ExpenseLogic execute vacant cost recovery

RadiusPoint runs vacant cost recovery as managed Utility Expense Management: ExpenseLogic ingests each utility invoice and analysts work the owner-name exceptions. The platform already collects line-item utility detail and allocates to location, department, and meter number. Vacant cost recovery adds the occupancy match and the recovery path. RadiusPoint can pay the vendor after the exception is cleared so late fees don’t accrue on a bill you’re still arguing.

Invoice auditing services catch category errors. Vacant cost recovery catches the wrong payer on a correct tariff. You want both. You don’t want one page pretending they’re the same.

Sharon Watkins founded RadiusPoint in 1992 after internal-audit work at a bank. The vacant-cost problem is an audit problem with a lockbox attached. ExpenseLogic is the working paper. RadiusPoint is the person who calls the utility.

FAQ

Does vacant cost recovery apply to a master-metered building?

Yes, but the recovery path changes. On a master meter RadiusPoint still runs ExpenseLogic against occupancy and consumption, yet the “account name” check often stays in the owner’s name by design. Recovery then becomes an allocation or RUBS question, not a utility-transfer question. Don’t force a resident-name test onto a meter the utility won’t split.

Can you back-bill a former tenant after the final statement?

Only if the lease and the local utility rules allow it, and only with dates RadiusPoint can attach in ExpenseLogic. The operational job is to produce the meter-level usage for the overlap period. Counsel decides whether that file becomes an invoice. RadiusPoint doesn’t write lease language.

How is vacant cost recovery different from submetering?

Submetering creates a new bill to a resident from a private meter. Vacant cost recovery asks who should have been the customer of record on the utility’s own account. RadiusPoint can support both inside a UEM program. They’re different postings in ExpenseLogic.

Do you need a TEM provider or a UEM provider for vacant cost recovery?

You need Utility Expense Management. TEM won’t see the electric BAN. RadiusPoint is unusual in running TEM, mobility, and UEM on one ExpenseLogic instance, which matters when a closed store still has a circuit and a meter.

What lease language makes recovery enforceable?

Language that states who places service, who holds house account during vacancy, and how overlap days are prorated. RadiusPoint will read that clause against the invoice. Drafting it’s a legal task, not an ExpenseLogic task.

What to do before the next utility cycle

If you can’t name the customer of record on last month’s five largest vacant or closed sites, start there. RadiusPoint will load those invoices into ExpenseLogic and check owner-name continuity with you. Every cycle you skip is another owner-name bill that looks like rent.

References

  1. ExpenseLogic | RadiusPoint
  2. Utility Expense Management | RadiusPoint
  3. About RadiusPoint | RadiusPoint
  4. RadiusPoint Capability Statement | RadiusPoint
  5. Sharon R. Watkins | RadiusPoint
  6. Invoice Auditing Services: What They Cover and How to Choose a Provider | RadiusPoint
  7. ExpenseLogic reviews | Capterra
  • Utility Expense Management
  • Invoice Auditing Services
  • About RadiusPoint

Disclaimer

This article is general information for finance, facilities, and property-operations teams. It is not legal advice on leases, tariffs, or back-billing. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results.

pexels karola g2 6229

Utility Rate Optimization: Rate Class, Demand, Time of Use, Power Factor and Supply

Uncategorized0

Utility rate optimization is the work of keeping every meter and account on the cheapest published rate and supply terms it qualifies for, then rechecking that fit as load, sites and tariffs change. Some teams call it energy rate optimization. The core is a utility tariff analysis, meter by meter, across the rate schedule, demand charges, time-of-use pricing, power factor and, where the state allows retail choice, the supply contract.

Demand alone shows the stakes. A 2017 National Renewable Energy Laboratory (NREL) survey of more than 10,000 utility tariffs, and NREL’s release on it, say demand charges in many cases can account for 30% to 70% of a customer’s electricity bill.

RadiusPoint’s Utility Expense Management (UEM) covers electricity, gas, water, sewer and waste in its ExpenseLogic platform, with meter-level contract and tariff rate audit.

Key Takeaways

  • Six levers set what a meter pays, from the rate schedule and demand charges to power factor terms and, in retail-choice states, the supply price.
  • The tariff, not a rule of thumb, sets the demand interval, the power factor minimum and any ratchet.
  • In two published RadiusPoint cases, moving utility services in 4 deregulated states cut costs by 4% to 13% depending on location, and 150 service locations moved to contract rates. Both are supply results, not rate-class filings.

Short version: gather 12 or more months of usage and peak demand per meter, read each tariff’s availability, demand and power factor terms, and recheck fit whenever load, the tariff or a supply contract changes.

When Does Energy Rate Optimization Include the Supply Contract?

Energy rate optimization includes the supply contract only where the state allows retail choice, since some states’ utility commissions fully regulate electricity prices. The US Energy Information Administration (EIA) says other states combine unregulated generation prices with regulated transmission and distribution prices, which is where a supply contract can be bid.

Two published RadiusPoint cases show the returns. The first client, a national eyeglass and contact lens manufacturer and retailer, had 170 retail locations and 3 labs. Working from at least 6 months of invoices, RadiusPoint requested proposals based on actual usage, and its UEM team analyzed the competing bids. The client’s management decided to move its locations’ utility services in 4 deregulated states, and the client cut utility costs by 4% to 13% depending on location.

The second, a nationwide facility maintenance company with over 500 service locations, handled 1,300+ invoices a month. Once RadiusPoint reported actual kilowatthours (kWh) and therms by meter, management could get new bids in deregulated states. RadiusPoint moved 150 service locations to contract rates, locations already under contract are monitored to move at contract expiration, and the published case reports over $40,000 in savings.

Neither case changed a rate class. Both changed the supply price, the work of utility procurement in retail-choice states.

What Does a Utility Tariff Analysis Check, Lever by Lever?

A utility tariff analysis checks each meter’s rate schedule, demand charges, time-of-use pricing, power factor terms, fixed charges and supply price against its load. The US Department of Energy-funded OpenEI Utility Rate Database shows the range: rate structure information for over 3,700 US utilities, covering time-of-use rates, demand charges, tiered rates, fixed monthly fees and adjustment riders.

Each row names the record that proves fit.

Lever What the tariff bills on What changes the cost Record that proves fit Site page that goes deeper
Rate schedule or rate class Charges and prices for customers who meet its availability terms Load size, service voltage and load shape Rate code on the bill; the tariff’s availability section; 12 or more months of usage and peak demand by meter Utility rate reclassification
Demand charge and any ratchet Peak kilowatts (kW) in the interval the tariff sets; a ratchet sets a billed-demand minimum tied to an earlier peak The month’s highest interval; an earlier peak a ratchet carries forward Billed and metered kW; the tariff’s definition of billing demand; 12 or more months of peak demand by meter Utility bill audit
Time-of-use energy charge kWh priced by time periods the tariff defines Share of kWh in higher-priced periods The tariff’s time periods; kWh by period on the bill Demand planning and forecasting
Power factor charge A charge or demand adjustment below the tariff’s power factor minimum The site’s power factor against that minimum Power factor or reactive power (kVAR) line; the tariff’s definition of demand Energy audits
Customer or fixed charge A fixed monthly amount per account or meter Number of meters and accounts billing Customer charge line per meter; the meter list Utility meter inventory
Supply price in a retail-choice state Supply price per kWh or therm, set by contract Contract price, term and expiration Supply contract with rate and expiration date; supply line on the bill; usage by meter Utility procurement

How Do You Know a Meter Is on the Right Rate Schedule?

A meter is on the right rate schedule when no other schedule it qualifies for would cost less for the same 12 months of load. Service level shapes that answer. EIA says industrial customers use more electricity and can receive it at higher voltages, so supplying them is more efficient and less expensive.

EIA puts the 2025 US annual average retail price at about 13.63 cents per kWh, against 13.41 cents for commercial and 8.62 cents for industrial customers. No single site should expect the industrial price, but voltage, size and load shape decide which schedules a meter can take.

A tariff’s availability section says who can take a schedule, and its terms say whether a customer must stay on it for a minimum period. Read both before asking for a change. Public and municipal accounts are billed on published tariffs too. Moving a meter to another class is a utility rate reclassification: a filed request, backed by load data, that the utility must approve.

Demand Charges Are Set by One Interval, and a Ratchet Can Hold Them There

A demand charge bills the highest average kilowatt demand in one tariff-defined interval each billing period, and a ratchet can carry an earlier peak forward. NREL’s 2017 survey says the interval is usually 15 minutes; a Massachusetts state fact sheet says typically 15, 30 or 60 minutes. The tariff sets it.

NREL estimated that nearly 5 million US commercial customers, over a quarter of about 18 million, can subscribe to tariffs with demand charges above $15 per kW. That counts customers who can choose such a tariff, not customers on one. Behind-the-meter batteries, the subject of NREL’s survey, can lower the peak itself.

A ratchet, where a tariff has one, sets a minimum billed demand tied to an earlier peak, using the percentage and look-back period that tariff defines, so one high interval can raise billed demand in later months. Checking billed kW against metered kW, multiplier included, is part of a utility bill audit. Rate optimization asks whether another schedule would cost less for the same peaks. ExpenseLogic’s demand multiplier calculations support kilowatt analysis, relevant to retail and hospitality sites.

Will a Time-of-Use Rate Lower Your Bill?

A time-of-use rate lowers a meter’s bill when enough of its usage falls in the lower-priced periods the tariff defines, so load shape decides. EIA says some utilities offer time-of-day pricing to encourage conservation and reduce peak demand. Compare the tariff’s periods with each meter’s kWh by period before switching.

A site that runs mostly in on-peak hours can pay more after a switch, and some time-of-use schedules carry demand charges too. Forecasting load before a change is the subject of demand planning and forecasting. In deregulated markets, RadiusPoint’s utility procurement work includes time-of-use, demand response and green energy procurement.

Power Factor Charges Follow the Minimum Your Tariff Sets

A power factor charge applies when a site’s power factor falls below the minimum its tariff sets, and that minimum differs between utilities and schedules. The US Department of Energy (DOE) says many utilities charge an additional fee below 0.95. A Massachusetts fact sheet says providers there typically require 90% or above.

In DOE’s worked example, raising a 100 kW load from 0.70 to 0.95 power factor with a capacitor cuts apparent power from 142 to 105 kilovolt-amperes (kVA), a 26% reduction in current. The Massachusetts sheet adds two cautions: check your rate’s definition of demand to see whether power factor affects billed demand, and know that raising power factor above the required minimum won’t lower demand charges. Correction equipment is a site project that energy audits can identify.

How RadiusPoint Supports Utility Rate Optimization in ExpenseLogic

RadiusPoint supports utility rate optimization through Utility Expense Management in ExpenseLogic, with meter-level contract and tariff rate audit across electricity, gas, water, sewer and waste. The model is software plus people: RadiusPoint staff work the invoices and the exceptions, and the audit runs at meter level, not account level.

ExpenseLogic receives and validates utility invoices with line-item detail on every charge. Its meter-level audit covers contract and tariff rate audit, consumption-based audit and threshold-based audit. Utility analysis reporting compares sites and dates, cost allocation runs to location, department and meter number, and the Contract Management module keeps contract images and terms.

Every rate review starts from an accurate utility meter inventory. RadiusPoint’s Utility Expense Management also includes utility procurement in deregulated markets, a help desk with site open and close services, and Vacant Cost Recovery, and RadiusPoint can pay vendor invoices for clients once the client funds the account.

A rate review won’t catch a closed site that’s still billing. In one published RadiusPoint case, a multi-location retailer paid $1,500 a month ($18,000 a year) for electricity, gas and water at a closed location until RadiusPoint identified the site, had services disconnected and flagged it in ExpenseLogic. That’s site open and close control, not rate work.

Each month a meter stays on a schedule it no longer fits, the price gap repeats. Request a free demonstration of ExpenseLogic’s meter-level utility audit and Reporting and Analytics.

Frequently Asked Questions

How often should we check whether our utility rates still fit?

Check a meter’s rate whenever its load changes, a site opens or closes, the utility revises its tariff or a supply contract nears expiration, and review the whole portfolio on a set schedule. Any minimum term in the tariff limits how often a meter can switch.

Can we get money back if a meter was on the wrong rate?

A rate change lowers future bills; it doesn’t by itself refund past ones. Past money comes back when a charge was wrong under the tariff that applied, or where tariff or state rules allow an adjustment, which is the work of utility expense recovery.

Is utility rate optimization the same as a utility bill audit?

No. A bill audit tests whether a bill was calculated correctly under its tariff, including multipliers, consumption and ratchet math. Utility rate optimization asks whether that tariff and the supply terms behind it are the cheapest the meter qualifies for, so a utility tariff analysis checks fit, not just accuracy.

What data does an energy rate optimization review need?

An energy rate optimization review needs 12 or more months of usage and peak demand for each meter, recent bills with rate codes, and each meter’s current tariff sheet with its availability, demand and power factor terms. In retail-choice states, add each supply contract with its rate and expiration date.

References

  1. National Renewable Energy Laboratory (NREL) and Clean Energy Group, “Identifying Potential Markets for Behind-the-Meter Battery Energy Storage: A Survey of U.S. Demand Charges,” NREL/BR-6A20-68963, August 2017. osti.gov
  2. National Renewable Energy Laboratory, “Analysis identifies where commercial customers might benefit from energy storage,” news release, August 29, 2017, as published by ScienceDaily. sciencedaily.com
  3. US Energy Information Administration, “Electricity explained: Prices and factors affecting prices,” 2025 prices from Electric Power Monthly, February 2026 (preliminary data), accessed October 2026. eia.gov
  4. OpenEI, “Utility Rate Database,” funded by the US Department of Energy, accessed October 2026. openei.org
  5. US Department of Energy, “Reducing Power Factor Cost,” fact sheet DOE/GO-10096-286. energy.gov
  6. Massachusetts Office of Technical Assistance and Technology, “Understanding Your Electric Bill: Saving Money on Demand Charges and Power Factor,” fact sheet, mass.gov, accessed October 2026. mass.gov
  7. RadiusPoint, “Utilities Expense Optimization Saves as Much as 13%,” March 4, 2023.
  8. RadiusPoint, “Cost Avoidance & Savings: $40K in UEM Cost Optimization,” October 18, 2022.
  9. RadiusPoint, “Utilities Mismanagement Costs $18K in Unnecessary Expenses.”

This article is general information for finance, facilities and energy managers, not engineering, legal or regulatory advice. Demand intervals, power factor minimums, ratchet provisions and switching terms vary by utility and rate schedule, so confirm them in your utility’s current tariff. RadiusPoint results cited here come from specific published client engagements on the case pages listed in References, and results vary by organization.

Reconciling Invoice

Reconciling Invoices: How Enterprises Eliminate Billing Errors at Scale

Financial0

By Sharon Watkins, Founder and CEO, RadiusPoint · 12 min read

Reconciling invoices at enterprise scale is a four-ledger test that billed, contracted, inventory, and roster agree before anyone pays the line. A two-way AP match can bless a total while a dead circuit keeps printing. The dispute you file in April is often a January fail you paid to close.

Invoice reconciliation is the operating discipline that scores each invoice line against the live contract, the live inventory, and the live user or site, then ages the exception until a credit posts. Generic AP reconciliation matches a vendor total to a purchase order. This page is the Telecom Expense Management (TEM), Utility Expense Management (UEM), and wireless version of the job: RadiusPoint analysts working inside ExpenseLogic against BANs, meters, and mobile lines.

A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one after the billed file and the inventory disagreed. Inventory work recovered $174,000 in re-credits. One unused toll-free set ran $18,000 a year. Telecom refund recovery is the filing step.

Key Takeaways

  • Invoice reconciliation for TEM, UEM, and wireless is four ledgers agreeing: billed, contracted, inventory, and roster or site. Two-way AP match is two of four.
  • The Four-Pass Reconcile scores inventory, rate, usage, and credit on every line before payment. Refund recovery files what a pass fails.
  • A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one, plus $174,000 in inventory re-credits. One unused toll-free set ran $18,000 a year.
  • Telecom breaks look like dead circuits and late MACDs. Utility breaks look like vacant meters and wrong tariff class. Wireless breaks look like ex-employee lines and zero-use devices.
  • ExpenseLogic keeps the four ledgers on one service ID. RadiusPoint’s named analysts run the passes. A spreadsheet of invoice totals is not a reconcile.

The Short Version

Reconciling a telecom or utility invoice is four ledgers and four passes before payment. If you only match the vendor and the total, you have finished AP’s job and skipped finance’s.

In this article

Invoice reconciliation is four ledgers agreeing

Invoice reconciliation for telecom, utility, and wireless spend is the month-to-month work of making four ledgers say the same thing about one service ID. Billed is what the vendor claims. Contracted is what you signed. Inventory is what is live. Roster or site is who or where still needs it. If any ledger is missing, you are matching a story to a total.

RadiusPoint has sold this as software plus people since 1992. ExpenseLogic is the platform. Named analysts score lines against contracted rates and against inventory, rather than sampling. That model is the commercial page for telecom expense management. This article is the reconcile layer sitting under that service: the test that happens after the invoice is already in the building.

Generic AP pages teach two-way and three-way match. They treat a carrier invoice like a shipment of paper. The paper has a PO. The circuit has a BAN, a service ID, a notice window, and a disconnect duty. If your reconcile ends when the vendor name and the dollar total look familiar, you have finished the short match and skipped the long one.

The Four-Pass Reconcile

The Four-Pass Reconcile is RadiusPoint’s test that a TEM or utility invoice line must survive this cycle before anyone pays it. Generic AP matching does not run all four passes. Pass 1 asks if the ID exists. Pass 2 asks if the rate matches. Pass 3 asks if usage matches. Pass 4 asks if last month’s credit posted.

RadiusPoint stores the invoice image inside ExpenseLogic and retains billed quantity, unit price, taxes, and credits against the same service ID. An invoice audit that cannot see those four passes is a three-way match with inventory missing. Invoice auditing services find the dollar error. The Four-Pass Reconcile is how you know the error is a live-ledger failure, not an AP coding failure.

Pass Question on the line Fail mode if skipped
1 Inventory Is this circuit, meter, or mobile line still supposed to exist this cycle? You pay a dead ID until someone notices the MRC.
2 Rate Does the billed unit price match the live contract, tariff, or plan on that ID? Last year’s rate bills all year.
3 Usage Does consumption, minutes, or kilowatts match the meter or the line activity? You pay a multiplier, a pool overage, or a spike nobody used.
4 Credit Did last month’s dispute actually post, and is a duplicate still hiding in the file? You win a credit and pay it back as a restatement.

A pass is four questions answered on the same ID. A spreadsheet of invoice totals with none of those questions asked is not a pass.

Where do telecom, utility, and wireless ledgers break?

Telecom, utility, and wireless ledgers break in different shapes, and a single exception code that says mismatch hides which ledger failed. Telecom breaks look like dead circuits and wrong MRCs. Utility breaks look like vacant meters. Wireless breaks look like ex-employee lines.

Telecom still-billed disconnects, toll-free numbers that route nowhere, and a MACD that closed in the field and missed the invoice are the wireline shape. Utility breaks add wrong tariff class, closed locations still on, and demand-multiplier misses. Wireless breaks add zero-use devices, pool overage on a dead handset, and plan drift.

Buyer guides list “billing errors.” They do not tell an AP manager whether to call facilities, HR, or the carrier desk.

Utility Expense Management (UEM) runs the four ledgers at meter level. Vacant utility cost recovery is what you do after pass 1 keeps failing on a site that is already closed. A multi-location client stopped $1,500 a month, $18,000 a year, on utilities at closed locations. Vacancy cost recovery has decreased utility expenses by 12 percent in published RadiusPoint work.

Managed mobility services is where wireless ledgers meet Employee IDs. Zero-use mobile lines are a pass-1 fail that outlived the user. A food service client working with RadiusPoint on 600-plus mobility lines cut cost 22 percent and more than $400,000 in year one. A Fortune 100 engagement added $830,000 in annual savings from wireless discovery and optimisation. They start as four ledgers that would not agree.

Why doesn’t a three-way match catch a dead circuit?

A three-way match does not catch a dead circuit because its third document is a purchase order, not live inventory. Two-way and three-way can agree while pass 1 is already red. Recurring telecom invoices persist. They do not ship. A PO is the wrong third document.

PO matching is the right tool for a copier, a crate, or a one-time install. Recurring telecom, utility, and wireless invoices do not ship. They persist. The “receipt” is a live ID. The “quantity” is a month of existence, a kilowatt, or a pool of megabytes. If AP’s match logic cannot see ExpenseLogic’s inventory table, it will bless the vendor and the total and call the job done.

A late MACD is the worked example. IT disconnected the circuit on the 4th. The carrier invoice for that BAN still carries the MRC on the 18th. Three-way match has no PO to cancel. Four-pass reconcile has an inventory fail on day one of the cycle. RadiusPoint’s hold queue exists so that MRC does not become a GL fact while someone argues about the disconnect ticket.

Taxes and surcharges sit beside the MRC. A three-way match that only sees the invoice total will treat a bad surcharge as a rounding issue. Pass 2 has to score the rate and the tax as separate lines. Pass 4 has to notice that last month’s agreed credit did not post, which is a restatement, not a new charge.

What RadiusPoint finds when a pass fails

RadiusPoint finds cash when billed, contracted, inventory, and roster disagree, and the published cases put those dollars in the open. A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one. That same manufacturer added $850,000 in ongoing annual savings and a $1.3 million year-one impact. Inventory work recovered $174,000 in re-credits when services did not match the bill.

An elevator company cut monthly waste expenditure 28 percent after the contract and the haul did not match. One line of unneeded toll-free numbers ran $18,000 a year. A healthcare provider cut telecom expenses 26 percent. A global glass manufacturer saved more than $100,000 in year one.

Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category observation, not a RadiusPoint guarantee. The operating fact is simpler. If a fail has no owner, the vendor’s preferred ledger wins by silence.

RadiusPoint is ISO 9001 certified since 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. A capability statement and the about page carry the firm facts. Credentials tell you the operator is real. The four passes tell you the invoice is being tested.

How is reconciling invoices different from refund recovery?

Reconciling invoices is the four-ledger test that produces a fail, and refund recovery is the filing that follows that fail. They share a ticket. They do not share a KPI. Mixing them is how a team reports “we recovered $0” in a month when they actually found $40,000 and never sent the dispute.

A Fortune 100 $450,000 year-one recovery is a recovery number. The reconcile that produced it was inventory and rate failing on named IDs, month after month, until someone had a packet.

Pass 4 is the bridge. It asks whether last month’s dispute actually posted, and whether a duplicate is hiding in this file. Recovery teams that do not run pass 4 win a letter and lose the money on the next BAN. RadiusPoint ages credits inside ExpenseLogic so a “won” dispute is not a folklore win.

You keep the dollar decision. RadiusPoint keeps the evidence. A letter of agency is what lets RadiusPoint talk to the carrier when pass 1 or pass 2 has already failed and someone has to file. Scope it. A read-only billing grant is not dispute rights.

ExpenseLogic keeps the four ledgers on one record

ExpenseLogic holds billed, contracted, inventory, and roster or site on one live service ID before each month’s payment file runs. RadiusPoint analysts run the four passes. You keep budget approval. One platform covers telecom, wireless, and utilities at the same month-end.

HR roster feeds and real-estate open-and-close feeds are how ledger 4 stays current. Employee ID validation against a monthly HR file is a wireless reconcile rule, not a nice-to-have report. A site that closed in the real-estate system and still appears on a utility BAN is a UEM reconcile rule. If those feeds do not land, pass 1 is theatre.

Cost allocation is a downstream job once the line is correct, covered on expense cost allocation. A TEM implementation is the calendar for standing this test up. The pass names do not change because a tool vendor sold you OCR.

The reconcile does not get simpler at 1,200. It gets more expensive to skip. If four ledgers are not on the ID at 50 locations, they will not appear by magic at 500.

FAQ

How often should we reconcile telecom and utility invoices?

Every cycle, on every line, before payment. Sampling a BAN at quarter-end is how a dead circuit bills for 90 days. RadiusPoint runs the four passes as the invoice lands. A quarterly “deep dive” is a recovery project, not a reconcile.

Can we reconcile from the PDF total?

No. The total is ledger 1 collapsed. Passes 1 through 4 run on service IDs, unit prices, usage, and credits. A correct total can still hide a dead ID and a missing credit that cancel each other. ExpenseLogic keeps the lines. The PDF is the image, not the test.

Who files the dispute after a pass fails?

A named operator files, with finance owning the dollar threshold and IT or facilities confirming the service is truly gone. RadiusPoint will be that operator on an ExpenseLogic engagement, using a scoped letter of agency. If nobody owns the ticket, the fail dies in a spreadsheet.

Does invoice reconciliation cover taxes and surcharges?

Yes. Taxes, surcharges, and credits are lines, not rounding. Pass 2 scores them against the contracted or tariff treatment. Pass 4 watches whether an agreed credit actually posted. A TEM or UEM reconcile that only tests MRC will pay the junk as a cost of doing business.

What if the vendor invoice arrives late?

Book an accrual on the last clean file, hold the BAN in the missing-bill report, and run all four passes when the invoice lands. Do not pay a guessed total so the close looks clean. Late is a station-1 problem. It is not permission to skip the test.

What to do before the next invoice cycle

Pick one carrier BAN and one utility account. Fill the four ledgers from last month’s invoice, the signed file, the inventory, and the HR or site list. Then ask the four pass questions on one ID. If a cell is empty, that is the operating gap. RadiusPoint will fill those cells for a managed ExpenseLogic engagement. Every cycle you pay without them is a cycle a dead ID can keep.

References

  1. How Companies Recover Telecom Refunds and Credits From Carriers | RadiusPoint
  2. Telecom Expense Management Services | RadiusPoint
  3. Utility Expense Management | RadiusPoint
  4. Managed Mobility Services | RadiusPoint
  5. ExpenseLogic | RadiusPoint
  6. Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
  7. Invoice Auditing Services | RadiusPoint
  8. Invoice Audit vs Three-Way Match | RadiusPoint
  9. The MACD Process in Telecom Expense Management, Explained | RadiusPoint
  10. Vacant Cost Recovery: The Utility Bills Nobody Is Watching | RadiusPoint
  11. How to Audit a Utility Bill for Errors | RadiusPoint
  12. Utility Rate Reclassification and How It Lowers Bills | RadiusPoint
  13. Finding and Killing Zero-Use Mobile Lines | RadiusPoint
  14. Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
  15. Allocating Telecom and Utility Costs Across Departments | RadiusPoint
  16. 5 Strategies That Will Help Reduce Telecom Expenses | RadiusPoint
  17. Unlock Cost Savings Through Telecom Expense Management | RadiusPoint
  18. 4 Benefits of Telecom Expense Management (TEM) | RadiusPoint
  19. How Long a Telecom Expense Management Rollout Actually Takes | RadiusPoint
  20. Capability Statement | RadiusPoint
  21. About RadiusPoint | RadiusPoint
  22. Sharon R. Watkins | RadiusPoint
  23. ExpenseLogic reviews | Capterra

Related articles

Disclaimer

This article is general information for finance, IT, procurement, and facilities teams reconciling telecom, utility, and wireless invoices. It is not legal, tax, or accounting advice. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results. Category-level TEM ranges are hedged and are not RadiusPoint promises.

SD-WAN Management: Controlling Performance, Vendors, and Costs

Education/Higher Learning0

By Sharon Watkins, Founder and CEO, RadiusPoint · 12 min read

SD-WAN management is the work of matching overlay licenses, underlay circuits, and failover links as three invoices, not one network dashboard. The controller can look green while finance still cannot name the total.

Software-defined WAN (SD-WAN) is an overlay that steers traffic across broadband, leftover MPLS, and LTE. SD-WAN management, on this page, is the invoice operation that sits under that overlay: vendors, contracts, location chargeback, and the bill that arrives after the NOC hops traffic. It is not a routing primer. The category definition of telecom expense management lives on What Is Telecom Expense Management?.

Greg Bryan’s WAN Manager Survey, published 26 March 2026 from 52 responses and 13 interviews, finds SD-WAN deployed at 63 percent of enterprises, with another 15 percent rolling it out. Direct Internet Access (DIA) already connects 54 percent of sites and is used by 96 percent of respondents. MPLS is down to 22 percent of sites, yet 74 percent still keep it somewhere. RadiusPoint’s published proof on the same failure mode is named: $120,000 a year from contract rate optimization, plus a Fortune 100 manufacturer that recovered $450,000 in telecom refunds in year one.

Key Takeaways

  • TeleGeography’s March 2026 WAN Manager Survey (52 responses, 13 interviews) puts SD-WAN at 63 percent deployed and 15 percent rolling out.
  • DIA is the common underlay: 54 percent of sites, 96 percent of respondents. MPLS is 22 percent of sites, still present at 74 percent of enterprises.
  • Fully managed WANs sit at 42 percent, co-managed at 25 percent, and about one third run unmanaged. Finance still sees three bills either way.
  • The Three-Bill SD-WAN Match tests overlay license, underlay circuit, and failover SIM against inventory, contract, and location ID.
  • RadiusPoint has recovered $120,000 a year from contract rate optimization, and a Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one.

The Short Version

SD-WAN management for finance is three invoices tied to one location ID. If you can see the overlay controller and cannot total overlay, underlay, and failover by site, you are watching packets, not managing cost.

In this article

SD-WAN management is three bills, not one overlay

SD-WAN management is the work of matching overlay licenses, underlay circuits, and failover links as three invoices, not one network dashboard. The overlay is the software or managed controller. The underlay is the DIA, broadband, or leftover MPLS that carries packets. The failover is the LTE or secondary DIA that bills when traffic hops. Network operations owns the path. Finance owns the three BANs.

TeleGeography’s 2026 survey is the market shape, not a RadiusPoint result: 63 percent already on SD-WAN, DIA at 54 percent of sites, MPLS still hanging on. That mix is why the invoice count went up while the architecture diagram got simpler. Telecom expense management services is the commercial program that audits those BANs.

A controller that shows green is a performance fact. It is not a cost fact. The operating object is the three-bill file.

Why does SD-WAN multiply vendors instead of cutting them?

SD-WAN multiplies vendors because the overlay, the broadband underlay, and the LTE failover are often three suppliers with three contracts. The architecture promised fewer boxes. The AP queue got longer. Overlay vendors, access providers, and wireless failover carriers do not share a BAN, a format, or a renewal date.

Multi-vendor support is the general discipline for that sprawl. SD-WAN is the current shape of it: one site, three vendors, three clocks. TeleGeography still finds 74 percent of enterprises holding MPLS at some sites for QoS, China, Africa, or a transition that has not finished. Those leftover circuits keep billing next to the new overlay.

A MACD that turns up DIA and never stops the MPLS is how you pay for both. Vendor count is not a design preference. It is an invoice fact you either match or you guess.

The Three-Bill SD-WAN Match

The Three-Bill SD-WAN Match is RadiusPoint’s test that overlay, underlay, and failover invoices must pass against inventory, contract, and location. Generic SD-WAN pages teach routing, SASE, and controller features. They do not teach a three-row match built for BANs, site codes, and auto-renew clocks.

An invoice audit that cannot see the overlay row next to the underlay row is a three-way match with two bills missing. Invoice auditing services find the dollar error. The Match is how you know the error is an SD-WAN stack failure, not an AP coding failure.

Bill What it is What must sit on the record Fail mode if missing
Overlay SD-WAN license or managed overlay fee Vendor, site or seat count, term You cannot total the controller against the branches
Underlay DIA, broadband, or leftover MPLS Circuit ID, BAN, contracted MRC Last year’s MPLS keeps billing next to new DIA
Failover LTE, 5G, or secondary DIA SIM or circuit, location ID, usage trigger Traffic hops. The charge lands in a corporate bucket.

A pass is three bills populated against the same location ID. A network dashboard with none of those fields extracted is not a pass.

How do you allocate SD-WAN cost when traffic hops to LTE?

You allocate SD-WAN cost when traffic hops to LTE by tagging the failover invoice to the same location ID as the underlay circuit. The NOC switched paths this afternoon. Finance sees the LTE spike one or two cycles later. Without the site tag, chargeback is a guess and the “savings” from cheap broadband vanish into wireless overage.

Cost allocation is the downstream job once the location ID is on all three bills. TeleGeography puts fully managed WANs at 42 percent and co-managed at 25 percent, with about one third unmanaged. Management model does not fix allocation. The site code does.

SASE elements are already in at 53 percent of those respondents, with another 23 percent in process. Security overlays add a fourth invoice if you let them. Keep the location ID anyway. ExpenseLogic holds the three SD-WAN bills against the site so the hop is a row, not a surprise.

What network tools miss on the SD-WAN invoice

Network tools miss billed rates, auto-renew clocks, and location chargeback on the SD-WAN invoice because they watch packets, not BANs. They can tell you a circuit is down. They cannot tell you the overlay auto-renewed at list, or that the MPLS underlay is still billing 90 days after the cutover.

RadiusPoint analysts run that match. You keep budget approval. Telecom refund recovery is what you file when the billed rate and the signed overlay or access contract disagree. One line of unneeded toll-free numbers ran $18,000 a year. An SD-WAN underlay that outlived the site is the same shape.

Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That is a category range, not a RadiusPoint promise.

What should finance ask before the next SD-WAN renewal?

Finance should ask for one total of overlay, underlay, and failover spend by location before any SD-WAN contract is renewed. If that total does not exist, the renewal is a guess. Three vendors with three dates is the usual mess.

The pre-sign question list is the longer interview. Ask who holds the letter of agency on the overlay vendor and on each access carrier. Ask how long a TEM implementation takes to load three bill types, not one. Ask what strategies you will run on leftover MPLS the week after DIA is live.

A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one, added $850,000 in ongoing annual savings, and booked a $1.3 million year-one impact. ISO 9001 certified since 2002. Amalgam Insights 2024 Distinguished Vendor. The Capterra listing sat at 4.8 from 31 reviews through December 2025. A capability statement and the about page carry the firm facts. Credentials tell you the operator is real. The three-bill file tells you the SD-WAN is being used.

FAQ

Is SD-WAN management the same as SD-WAN the network product?

No. SD-WAN the product steers packets across underlays. SD-WAN management on this page is the invoice operation underneath: overlay fees, access circuits, failover usage, and location chargeback. You can have a healthy controller and an unhealthy AP queue. RadiusPoint sits on the second job.

How do we treat leftover MPLS after DIA is live?

Treat it as a live underlay row until the stop-bill posts. TeleGeography still finds MPLS at 22 percent of sites and at 74 percent of enterprises somewhere. A cutover that does not file a disconnect is two underlays. The Match fails until one BAN goes to zero.

Who should own the LTE failover bill?

Finance should own the dollar, the NOC should own the hop, and a named operator should keep the location ID on both. If the SIM bills into a wireless bucket with no site code, you cannot allocate the hop. You can only argue about it at quarter-end.

Do we need a letter of agency for overlay and underlay?

Yes, if anyone other than your staff must pull invoices or file a disconnect with those vendors. Scope each grant. An overlay read-only login is not ordering rights on the DIA carrier. RadiusPoint will tell you which grant it is asking for, and you should be able to revoke it.

What to do before the next invoice cycle

Pick one branch. List the overlay fee, the underlay MRC, and the failover SIM. Fill location ID, BAN, and term for each. If a cell is empty, that is the operating gap. RadiusPoint will fill those cells for a managed ExpenseLogic engagement. Every hop you cannot allocate is a cycle the 54 percent DIA mix can still surprise you.

References

  1. Enterprise Network Trends & Strategy: WAN Manager Survey Insights | TeleGeography, Greg Bryan, 26 March 2026
  2. Telecom Expense Management Services | RadiusPoint
  3. ExpenseLogic | RadiusPoint
  4. The Ultimate Guide on Multi Vendor Support | RadiusPoint
  5. The MACD Process in Telecom Expense Management, Explained | RadiusPoint
  6. Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
  7. Invoice Auditing Services | RadiusPoint
  8. Allocating Telecom and Utility Costs Across Departments | RadiusPoint
  9. How Companies Recover Telecom Refunds and Credits From Carriers | RadiusPoint
  10. Does Your Enterprise Face These 5 TEM Challenges? | RadiusPoint
  11. Questions to Ask a TEM Provider Before You Sign | RadiusPoint
  12. Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
  13. How Long a Telecom Expense Management Rollout Actually Takes | RadiusPoint
  14. 5 Strategies That Will Help Reduce Telecom Expenses | RadiusPoint
  15. Unlock Cost Savings Through Telecom Expense Management | RadiusPoint
  16. Capability Statement | RadiusPoint
  17. About RadiusPoint | RadiusPoint
  18. Sharon R. Watkins | RadiusPoint
  19. What Is Telecom Expense Management? | RadiusPoint
  20. ExpenseLogic reviews | Capterra

Related articles

Disclaimer

This article is general information for finance, IT, and network teams managing SD-WAN overlay, underlay, and failover invoices. It is not legal advice and it is not a network-design guide. Outcomes cited are from specific RadiusPoint client engagements already in the published proof library and are not a guarantee of future results. TeleGeography survey figures describe that firm’s 2026 respondent set, not RadiusPoint clients. Category-level TEM ranges are hedged and are not RadiusPoint promises.

How to Reduce Operational Costs: Start With the Bills Nobody Audits

cost savings0

Most cost-cutting plans start with the budget and work down. The savings that hold start with the bills and work up.

Operational costs are the recurring costs of running the business, from payroll and rent to the telecom, wireless, utility and IT bills that arrive every month. The durable way to reduce operational costs is to find the spend that isn’t delivering value and remove it, starting with recurring vendor bills, rather than cutting every department by the same percentage. Payroll and rent get negotiated on purpose; recurring service bills get approved without a line-by-line check.

For multi-location organizations, that spend leaks in four places: charges above contracted rates, zero-use lines and devices, services still billing at closed or vacant sites, and contracts that renew without a decision. RadiusPoint, founded in 1992, audits those bills through ExpenseLogic, a single cloud platform for telecom, wireless, utility and IT asset spend, and its team works each finding through to a credit, refund or disconnect.

Key Takeaways

  • Deloitte’s 2024 MarginPLUS study found 82% of companies missed their cost-reduction targets, the highest failure rate Deloitte has recorded since starting the series in 2008.
  • A line-item audit checks each charge against the contracted rate and a verified inventory, so the savings don’t depend on cutting service.
  • In RadiusPoint’s published results, a Fortune 100 manufacturer recovered $450K in telecom refunds in year one, part of $1.3M in total first-year impact.
  • Recovered money counts once it posts as a credit or refund, so each metric needs a named owner and a monthly review.

Short version: before you cut any budget line, audit the recurring bills you already pay against your contracts and inventory, because that’s where costs come down without cutting service.

Why Do Across-the-Board Cuts Rarely Stick?

Across-the-board cuts rarely stick because they shrink budgets without removing the waste inside them, so spending drifts back once the pressure eases. Deloitte’s 2024 MarginPLUS study of more than 300 business leaders found 82% of companies missed their cost-reduction targets, up from 72% a year earlier, and half of those realized less than half of their target.

Companies are adjusting. In Deloitte’s 2025 MarginPLUS study of 397 executives, targeted action in a few divisions, functions or geographies was the most common route to margin improvement, chosen by 69%, up from 65% in 2024. The shift is toward fewer, sharper targets, and recurring vendor bills are among the sharpest a multi-location organization has.

Question Across-the-board cuts Line-item expense management
Where does it start? A percentage applied to every department’s budget Every recurring charge compared with the contract, the inventory and the site list
What gets removed? Whatever each department can give up, including services people use Overbilling, unused lines and devices, closed-site services and stale rates, while used services stay
What data does it need? Budget totals by department Invoices, contracts and inventory by location, account, meter and line
Why do savings hold or slip? The waste was never identified, so it can return when budgets loosen Removed charges stay removed while monthly audits continue

Four Billing Leaks Hiding in Recurring Operational Costs

Recurring operational costs leak through four gaps: charges above contracted rates, unused lines and devices, services billing at closed sites, and unreviewed renewals. None shows up in a department budget, because each one looks like a normal bill. They surface only when someone compares the invoice with the contract, the inventory and the location list.

That comparison is the core of a line-item invoice audit, and it’s why the CFO’s unreconciled accounts and the facilities team’s closed-site bills turn out to be one problem. Use the table as a checklist for operational cost reduction strategies aimed at recurring bills.

Leak How it starts What catches it ExpenseLogic capability
Charges above contracted rates The contracted rate never reaches the account, or reaches some lines and not others Checking each charge against the signed rate Line-item audit against contracted rates and inventory
Zero-use lines and devices An employee leaves or a device is replaced, and the line keeps billing Usage review plus an HR roster check Zero-use device identification; ex-employee line detection through HR roster reconciliation
Services billing at closed or vacant sites A location closes or a tenant moves out, and no one orders the disconnect Comparing the site list with active accounts Closed-location billing exception reports; real estate system integration for setup and disconnect
Silent contract renewals A term ends with no review, and the termination date passes A contract calendar with expiration dates Vendor contract management; contract obligation alerts covering termination fees and dates

How Do You Minimize Operational Costs at Closed and Vacant Sites?

You minimize operational costs at closed and vacant sites by tying every disconnect to the real estate event, then auditing for anything still billing. Closing a location is an operations decision, and the utility, internet and phone accounts attached to it don’t close themselves. One RadiusPoint multi-location client was paying $1,500 a month, $18K a year, for utilities at closed locations.

Rising rates make every idle meter more expensive: the U.S. Energy Information Administration put average commercial-sector revenue per kilowatthour, its proxy for retail price, at 14.53 cents in July 2026, up 3.4% from a year earlier. In property management, a tenant moves out, never transfers the utility account, and the owner keeps paying. Recovering those charges is called vacant cost recovery, and RadiusPoint’s published results show it decreasing utility expenses by 12%.

ExpenseLogic works the problem from both ends: real estate system integration handles setup and disconnect when a location opens or closes, and closed-location billing exception reports catch accounts that kept billing anyway. The meter-level audit inside Utility Expense Management (UEM) adds a consumption check, because a meter at an empty site shouldn’t look like a meter at an open one.

What Do Zero-Use Lines and Silent Renewals Really Cost?

Zero-use lines charge for service nobody uses, and silent renewals lock in old rates; both keep billing until someone checks usage and contract dates. Each looks small on its own invoice. Added up, they aren’t: RadiusPoint clients have saved $18,000 a year by eliminating unneeded toll-free numbers and $120,000 a year through contract rate optimization.

For a food service company, RadiusPoint audited more than 600 wireless lines, set up a wireless policy and cut costs 22%, worth $400K in year one. ExpenseLogic finds zero-use mobile lines through zero-use device identification and flags ex-employee lines by reconciling devices against the monthly HR roster.

Renewals need a calendar, not a memory. Vendor contract management in ExpenseLogic ties expiration dates and rates to service IDs, and contract obligation alerts flag termination fees and dates, so each renewal becomes a decision instead of a default.

What Are the Steps to Reduce Operational Costs Without Cutting Service?

The steps are to inventory every recurring account, audit each charge against contracts, recover overbilling, remove unused services, then track results monthly. The order matters. Removing services before the inventory is complete risks disconnecting something a site still needs, and a dispute filed without the contract and inventory behind it is a request, not evidence.

  1. Inventory every recurring account by location. List each account, the service it pays for and the site it belongs to.
  2. Audit each charge against the contract and the inventory. Compare line items, not invoice totals, so a wrong rate on one line can’t hide inside a familiar total.
  3. Dispute and recover. File each dispute with evidence, then confirm the credit on a later invoice or the refund in the bank.
  4. Remove what isn’t used. Disconnect zero-use lines, closed-site services and redundant numbers, and decide each renewal before its date passes.
  5. Track it every month. Give each metric below an owner and a fixed review date.
Metric What it measures Data source Owner
Recurring spend by location and category Whether telecom, wireless, utility and IT costs track the number of active sites Coded invoice data and GL files Finance (CFO or controller)
Credits recovered versus disputed How much disputed money actually came back Later invoices and refund records Accounts payable
Zero-use lines and devices Billed services with no activity Usage data and the HR roster IT or telecom manager
Accounts active at closed sites Services still billing after a location closed or went vacant Real estate site list compared with active accounts Facilities or real estate
Contracts nearing expiration Renewals that need a decision before the term rolls over Contract records with expiration dates Procurement

How RadiusPoint and ExpenseLogic Turn Findings Into Recovered Dollars

RadiusPoint turns findings into dollars by pairing ExpenseLogic, one platform for telecom, wireless, utility and IT asset spend, with a team that works each finding. A report that flags an overcharge saves nothing until the carrier or utility issues the credit. The RadiusPoint team works the invoices, files the disputes and closes the tickets, so findings end as credits, refunds or disconnects.

The ExpenseLogic platform covers telecom expense management (TEM), managed mobility, UEM and IT assets, so a closed site’s phone lines, circuit and meter sit in one inventory. Daily missing-bill reporting shows when an expected invoice hasn’t arrived.

The flagship result is a Fortune 100 manufacturer with more than 10,000 wireless devices managed globally: $450K in telecom refunds in year one, $850K in ongoing annual savings and $1.3M in total first-year impact. Other published results include $174K in re-credits from inventory management, more than $250K in unrealized cost savings uncovered, and one client’s growth from 170 to 1,200 locations. Sharon Watkins, RadiusPoint’s founder and CEO, has put the carrier side of the problem plainly: “The telecom industry can’t keep up with the ubiquitous challenges and doesn’t have the time to identify savings.”

What to Do Before Your Next Billing Cycle Closes

Before your next billing cycle closes, pull every recurring account by location and compare it with your current site list and signed contracts. That single comparison shows whether closed sites are still billing and which renewals are coming due. Every month an error goes unaudited, it bills again at the same rate, and reducing operational costs starts with stopping that repeat.

If the comparison turns up more than your team can work, RadiusPoint can take it from there. It’s a women-owned business founded in 1992, a Distinguished Vendor in the Amalgam Insights 2024 TEM Vendor SmartList, and ExpenseLogic is rated 4.8 on Capterra from 31 reviews. Request a free demonstration of ExpenseLogic to see your telecom, wireless, utility and IT bills audited line by line.

Frequently Asked Questions

How much can a company save by reducing operational costs?

It depends on how long the bills have gone unaudited and how many accounts are involved, so no honest provider can promise a percentage up front. Published RadiusPoint client results show the range: a healthcare provider cut telecom expenses 26%, an elevator company reduced monthly waste expenditure 28%, and a food service company cut wireless costs 22%.

Should we cut budgets and audit invoices at the same time?

You can, but sequence them. A temporary freeze on new services buys time while the audit runs, and permanent cuts should wait for its results, because the audit shows which charges are waste and which pay for service people need. Cutting first risks removing working services while the overbilling stays.

Who should own operational cost reduction inside the company?

Finance should own the target, but the data sits with accounts payable, facilities, IT and procurement, so each metric needs a named owner. In Deloitte’s 2024 MarginPLUS study, the most common lesson from cost programs was building a solid tracking and reporting process (40%), and 20% cited a full-time role dedicated to efficiency initiatives.

Can RadiusPoint pay the vendor bills as well as audit them?

Yes. RadiusPoint can pay vendor invoices for clients once the client funds the account. On the audit side, a line-item audit checks each charge against the contracted rate and a verified inventory. The RadiusPoint team works the invoices, files the disputes and closes the tickets, so findings end as credits, refunds or disconnects. Daily missing-bill reporting shows when an expected invoice hasn’t arrived.

References

  • Deloitte. “2024 MarginPLUS study: Refocusing amidst uncertainty.” 2024. deloitte.com
  • Deloitte. “2025 MarginPLUS study: Resilience and innovation.” 2025. deloitte.com
  • U.S. Energy Information Administration. “Electricity Monthly Update, End Use: July 2026.” Released September 24, 2026. eia.gov
  • RadiusPoint. Published client case results for ExpenseLogic engagements. Accessed October 2026.
  • Amalgam Insights. “2024 Vendor SmartList for Telecom Expense Management.” 2024.
  • Capterra. “ExpenseLogic reviews.” 2026. capterra.com

Client results describe specific RadiusPoint engagements and don’t guarantee results for any other organization. Savings depend on contract terms, invoice volume, location count and how recently invoices were last audited.

action process directions performance verification icon

How to Optimize P2P Invoice Processing: A Guide for AP and Finance Leaders

Financial0

The accounts payable department is often seen as a tactical, back-office function, a necessary cost center focused on the repetitive task of paying bills. This outdated view misses the strategic importance of P2P invoice processing. In reality, the AP function is a goldmine of financial data and a critical control point in the procure-to-pay (P2P) cycle.

When optimized, it can drive significant cost savings, improve cash flow, and provide the spend visibility that finance leaders need to make informed decisions. However, for most organizations, this potential remains untapped, buried under a mountain of paper invoices and manual processes.

This guide is for the finance or AP leader who is ready to challenge the status quo and transform their accounts payable function. We will provide a detailed blueprint for optimizing your P2P invoice processing workflow, from invoice capture to payment authorization. We will also explore how centralized automation can help you reduce your cost per invoice, accelerate your invoice cycle time, and turn your AP team into a strategic asset for-profit engine for your business.

The Procure-to-Pay Lifecycle and the Role of Invoice Processing

The procure-to-pay lifecycle encompasses every step from the initial purchase requisition to the final vendor payment. Invoice processing is the critical link that connects procurement with payment, and it typically involves these five core components:

  1. Invoice Capture and Data Extraction: Receiving invoices from vendors (whether paper or electronic) and extracting the key data, such as invoice number, date, amount, and line-item details.
  2. Verification and Matching: Validating the invoice against the corresponding purchase order (PO) and proof of receipt. This is often referred to as three-way matching.
  3. Workflow Routing and Approval: Routing the invoice to the appropriate business owner for review and approval.
  4. Exception Handling: Managing and resolving discrepancies, such as price or quantity mismatches, that arise during the verification process.
  5. Payment Authorization: Authorizing the invoice for payment and scheduling it in the accounting or ERP system.

Why Manual P2P Invoice Processing Fails at Scale

For many organizations, these five steps are managed through a combination of email, spreadsheets, and manual data entry. This approach is not only inefficient but also fraught with risk.

Pain Point Financial Impact
High Processing Costs Manual labor for data entry, validation, and approval routing can drive the cost per invoice to $15 or more.
Late Payment Penalties Inefficient approval workflows and lost invoices lead to missed payment deadlines and unnecessary fees.
Lack of Spend Visibility When invoice data is trapped in paper or disconnected systems, finance leaders have no real-time view of cash flow or budget performance.
Increased Risk of Fraud Manual processes make it difficult to enforce financial controls, increasing the risk of duplicate payments and fraudulent invoices.

A 5-Step Framework for P2P Invoice Optimization

Transforming your P2P invoice processing requires a systematic approach. This five-step framework provides a clear path to achieving greater efficiency and control.

Step 1: Capture All Invoices Efficiently

The foundation of AP automation is centralized invoice capture. By converting all incoming invoices (paper, PDF, EDI) into a single digital format, you create a standardized starting point for your workflow.

Step 2: Automate Matching Rules

Implement automated three-way matching to validate invoices against POs and receipts. This eliminates the need for manual review of compliant invoices, allowing your team to focus on exception handling.

Step 3: Streamline Approval Workflows

Configure automated invoice approval workflows to route invoices to the correct approvers based on business rules, such as department, GL code, or invoice amount. This accelerates the approval process and eliminates bottlenecks.

Step 4: Resolve Exceptions Quickly

Create a dedicated process for managing invoice exceptions. A centralized platform allows for clear communication and collaboration between AP, procurement, and business owners to resolve discrepancies quickly.

Step 5: Generate Insights and Metrics

Track key AP metrics to measure the performance of your P2P invoice processing function. This includes:

  • Cost Per Invoice
  • Invoice Cycle Time
  • Exception Rate
  • Early Payment Discounts Captured

The Role of Centralized Automation in P2P Excellence

Achieving true P2P invoice processing optimization is impossible without the right technology. A centralized AP automation platform like RadiusPoint’s ExpenseLogic provides the end-to-end capabilities you need to streamline your entire workflow.

RadiusPoint helps you:

  • Automate Invoice Capture and Data Extraction: Eliminate manual data entry with intelligent OCR and machine learning.
  • Enforce Financial Controls: Implement automated matching and approval rules to ensure compliance and prevent overpayments.
  • Gain Real-Time Visibility: Use customizable dashboards to monitor your AP metrics and get a clear view of your cash flow.
  • Integrate with Your ERP: Seamlessly connect with your existing accounting system to ensure data consistency and a single source of truth.

By automating your P2P invoice processing with telecom expense management, you can reduce your cost per invoice by up to 80%, shorten your invoice cycle time from weeks to days, and provide your finance team with the spend visibility they need to make strategic, data-driven decisions.

If you are ready to transform your accounts payable function and unlock the full potential of your procure-to-pay process, contact RadiusPoint today to learn how RadiusPoint can help.

What Is Operational Financial Management? A Guide for CFOs and Finance Leaders

cost savings0

The modern CFO is expected to be more than a financial steward; they are expected to be a strategic partner to the business. However, the reality for many finance leaders is that they are bogged down in the tactical details of financial operations. 

The promise of data-driven decision-making is lost in a sea of spreadsheets, manual processes, and a fundamental lack of spend visibility. This is the challenge of operational financial management: aligning the day-to-day execution of financial processes with the long-term strategic goals of the organization.

This guide is designed for the strategic CFO who is ready to transform their financial operations from a reactive cost center into a proactive value driver. 

We will explore the core principles of operational financial management, dissect the common challenges that stand in the way of financial excellence, and provide a roadmap for implementing the systems and processes needed to achieve true financial governance and control.

Operational vs. Strategic Financial Management

Understanding the distinction between operational and strategic financial management is crucial. While both are essential, they operate on different time horizons and with different objectives.

Aspect Strategic Financial Management Operational Financial Management
Time Horizon Long-term (3-5 years) Short-term (daily, weekly, monthly)
Focus Growth, profitability, capital structure Liquidity, cash flow, cost control
Key Activities Mergers and acquisitions, capital budgeting, dividend policy Accounts payable, vendor payments, budgeting

Operational financial management is the engine that powers your company’s strategic plan. Without effective financial operations, even the most brilliant strategy will fail due to poor execution.

Core Components of Operational Financial Management

A robust operational financial management framework is built on five key pillars:

  1. Cash Flow and Working Capital Management: Ensuring the business has sufficient liquidity to meet its short-term obligations. This includes managing receivables, payables, and inventory.
  2. Budgeting and Cost Control: Establishing departmental budgets, monitoring actual spend against those budgets, and implementing financial controls to prevent overspending.
  3. Accounts Payable and Vendor Payments: Managing the end-to-end process of receiving, approving, and paying vendor invoices accurately and on time.
  4. Accounts Receivable and Revenue Tracking: Ensuring that customer payments are collected on time to maintain healthy cash flow.
  5. Financial Reporting and Operational Visibility: Providing timely and accurate financial reporting to give stakeholders a clear view of the company’s performance and financial position.

Common Challenges in Operational Financial Management

Many organizations struggle to achieve excellence in their financial operations due to a common set of challenges:

  • Limited Spend Visibility: Without a centralized system for tracking expenses, it is impossible to get a complete picture of where money is being spent, leading to missed savings opportunities and a lack of financial governance.
  • Manual and Disconnected Processes: Manual invoice processing, approval routing, and data entry are time-consuming, error-prone, and create bottlenecks in the procure-to-pay cycle.
  • Vendor and Contract Complexity: Managing thousands of vendor contracts, service agreements, and pricing structures in spreadsheets is a recipe for overpayments and missed renewal deadlines.
  • Risk and Compliance Gaps: Manual processes make it difficult to enforce financial controls and create a clear audit trail, increasing the risk of fraud and non-compliance.

Best Practices for Strengthening Financial Operations

As a CFO, you can drive significant improvements in your company’s operational financial management by focusing on these best practices:

  • Centralizing Financial Data: Consolidate all your operational spend data into a single platform to create a single source of truth and enable comprehensive financial reporting.
  • Standardizing Workflows and Controls: Implement consistent processes for procurement, invoice approval, and payment across the entire organization to improve efficiency and strengthen financial governance.
  • Automating Manual Tasks: Leverage technology to automate repetitive tasks like data entry, invoice validation, and payment scheduling to reduce costs and free up your team for more strategic work.
  • Fostering Cross-Department Alignment: Break down silos between finance, procurement, and operations to ensure that financial decisions are made with a full understanding of their operational impact.

The Role of Technology in Modernizing Financial Operations

Technology is a critical enabler of effective operational financial management. A centralized expense management platform like RadiusPoint’s ExpenseLogic provides the tools you need to transform your financial operations.

RadiusPoint helps you:

  • Achieve Real-Time Spend Visibility: Gain a complete, up-to-the-minute view of your operational spending across all locations and departments.
  • Automate the Procure-to-Pay Cycle: Streamline your entire invoice management process, from receipt to payment, with automated workflows and controls.
  • Strengthen Financial Governance: Enforce your financial controls and create a complete audit trail for every transaction.
  • Unlock Actionable Insights: Use powerful analytics and reporting to identify cost-saving opportunities and make more informed financial decisions.

By embracing technology and adopting these best practices, you can transform your financial operations from a tactical, back-office function into a strategic asset that drives business value.

If you are ready to take your company’s operational financial management to the next level, contact RadiusPoint today to learn how RadiusPoint can help you achieve your goals.

Frequently Asked Questions

What is cash management in operational financial management?

Cash management is the daily work of collecting, holding and paying out cash so the business can meet its obligations without leaving money idle. In operational financial management, it sits next to working capital: speeding up receivables, timing payables and forecasting what’s due. Recurring telecom and utility bills belong in that forecast, because they arrive every month whether or not anyone placed a new order.

What cash management strategies do CFOs use for recurring bills?

CFOs manage recurring bills by checking the charges before payment, paying close to the due date instead of early, and forecasting from usage rather than last month’s total. Paying a wrong charge on time still sends cash out the door, so validation comes first. Centralized intake keeps a bill from sitting in someone’s inbox past its due date, and tracking disputed credits until they post brings the money back.

How do telecom and utility bills affect cash flow forecasting?

Telecom and utility bills make cash flow forecasts less reliable than they look, because they move with usage, weather, rate changes and billing cycles that don’t match your close calendar. Utility bills arrive after the meter read and swing by season. Telecom bills pick up new services, one-time charges and lines nobody canceled. Forecast from usage and contracted rates by location, and the variance becomes something you can explain.

Can a provider pay utility bills without giving up cash control?

Yes, a provider can pay your utility bills while you keep cash control, as long as it pays from an account you fund. In Utility Expense Management (UEM), RadiusPoint handles invoice receipt and validation, meter-level audit and cost allocation in ExpenseLogic, with line-item detail on every charge. RadiusPoint can pay vendor invoices for clients once the client funds the account.

How often should finance review recurring vendor spend?

Finance should review recurring vendor spend every month at the invoice level and every quarter against contracts and inventory. The monthly pass catches rate changes, new charges and usage spikes while they’re one bill old. The quarterly pass asks a bigger question: are you still using every line, circuit, meter and service you pay for? Closed sites and departed employees are common reasons a recurring bill keeps running after the need ends.

high angle calculator cash arrangement

Telecom Cost Optimization: A 6-Step Framework for IT and Finance Leaders

Financial0

Your telecom bills are a black box. For most organizations, telecom spend is a significant and growing operational expense, yet it remains one of the least understood and most poorly managed cost categories. 

The complexity of telecom services, with their myriad of vendors, contracts, and billing formats, creates a perfect storm for overspending. Billing errors, charges for unused services, and suboptimal contract terms are the norm, not the exception. 

Telecom cost optimization is the process of shining a light into this black box, and for most companies, it represents one of the largest and most immediate opportunities to impact the bottom line.

This guide is for the IT, finance, or procurement leader who is ready to take control of their company’s telecom spend. We will provide a proven, six-step framework for telecom cost optimization, moving from reactive bill payment to proactive telecom expense management (TEM). 

We will also show how a centralized platform can provide the spend visibility and control you need to eliminate waste and drive sustainable savings.

Key Cost Drivers in Your Telecom Environment

To effectively manage your telecom spend, you must first understand the primary factors that drive your costs. For most organizations, these fall into three main categories:

Cost Driver Description
Service Complexity A mix of fixed-line, mobile, and data services from multiple vendors, each with its own contract terms, pricing, and billing cycles.
Lack of Visibility Decentralized management of telecom services across different departments and locations, leading to a fragmented and incomplete view of total spend.
Inefficient Processes Manual processes for invoice validation, auditing, and payment, which are time-consuming, error-prone, and prevent proactive management.

These challenges are compounded by the sheer volume and complexity of telecom invoices, which are often riddled with errors, hidden fees, and charges for services that are no longer in use.

A 6-Step Framework for Telecom Cost Optimization

A successful telecom cost optimization program is a continuous cycle of analysis, action, and monitoring. This six-step framework provides a structured path to gaining control over your telecom spend.

Step 1: Establish a Spend Baseline

The first step in any telecom expense management initiative is to create a complete and accurate inventory of all your telecom services and assets. This involves aggregating all your telecom invoices into a single, centralized platform to establish a comprehensive spend baseline.

Step 2: Audit and Validate Invoices

Once you have a complete view of your spending, you can begin to audit your telecom invoices for errors and discrepancies. This includes verifying rates against your vendor contracts, identifying charges for unused services, and flagging any unauthorized fees.

Step 3: Analyze Usage vs. Services

Compare your actual usage data with the services you are paying for. This analysis often reveals significant savings opportunities, such as right-sizing data plans, eliminating underutilized phone lines, and identifying employees with multiple devices.

Step 4: Optimize Contracts and Vendors

Armed with data from your audit and analysis, you can begin to optimize your vendor contracts. This may involve consolidating services with a single provider, renegotiating rates based on your usage patterns, or terminating contracts for redundant or unnecessary services.

Step 5: Implement Governance and Policy Controls

Establish clear policies for the procurement, use, and management of telecom services. This includes creating a standardized process for adding or removing services, setting guidelines for mobile device usage, and implementing approval workflows for all telecom-related expenses.

Step 6: Monitor and Improve Continuously

Telecom cost optimization is not a one-time project. It is an ongoing process of monitoring your telecom spend, tracking your key performance indicators (KPIs), and continuously identifying new opportunities for savings and efficiency.

The Role of a Centralized Platform in Telecom Expense Management

Attempting to manage the complexities of telecom spend with spreadsheets and manual processes is a losing battle. A centralized telecom expense management platform like RadiusPoint’s ExpenseLogic is essential for achieving sustainable cost optimization.

RadiusPoint provides the tools you need to:

  • Automate Invoice Management: Centralize all your telecom invoices in a single platform and automate the process of invoice validation, auditing, and payment.
  • Gain Complete Spend Visibility: Use real-time dashboards and reporting to get a clear, consolidated view of your telecom spend across all vendors, locations, and service types.
  • Optimize Your Wireless and Mobile Spend: Effectively manage your mobile device inventory, track usage, and identify opportunities to reduce costs in your wireless environment.
  • Streamline Vendor and Contract Management: Keep all your vendor contracts and service agreements in one place to ensure you are getting the services and pricing you negotiated.

By providing a single source of truth for all your telecom expenses, RadiusPoint empowers you to take control of your spending, eliminate waste, and drive significant savings for your organization.

If you are ready to move beyond the chaos of manual telecom expense management and build a sustainable cost optimization strategy, contact RadiusPoint today to learn how RadiusPoint can help you achieve your goals.

contract conclusion office

The Contract Lifecycle Management Process for Telecom and Utility Spend

Services0

By Sharon Watkins, Founder and CEO, RadiusPoint · 12 min read

The contract lifecycle management process runs five stages from request to termination, and most of the money sits in the long stage after signature. Legal finishes when the PDF is signed. Finance lives with the invoices that follow.

Contract lifecycle management (CLM) is the administration of an agreement across request, draft, execution, ongoing management, and renew-or-end. This page is the stage map for telecom, Utility Expense Management (UEM), and wireless spend.

WorldCC, with Ironclad, puts average post-signature value leakage at 11 percent of contracted spend. Tim Cummins, president of WorldCC, put the diagnosis in one line: the commercial intent of a deal vanishes because delivery teams are not equipped to manage it. RadiusPoint’s work since 1992 is that delivery layer, run on ExpenseLogic against carriers, meters, and mobile lines.

Key Takeaways

  • The contract lifecycle has five stages: request, draft, execute, manage, and renew or end. Manage is the long stage.
  • WorldCC puts average post-signature leakage at 11 percent of spend, with 2 to 3 percent from unrecorded scope changes and 1 to 2 percent from missed price adjustments.
  • The invoice-as-contract test treats each monthly bill as an exam of the executed agreement. A stored PDF is not a passing score.
  • Stage owners for TEM and utility spend split across finance, IT or facilities, and a named operator. Unclear ownership is WorldCC’s most severe gap.
  • ExpenseLogic and RadiusPoint analysts cover the manage stage: line-item audit, dispute filing, inventory, and the renewal clock. CLM software that stops at e-signature does not.

The Short Version

If your CLM process ends at execution, you have finished the short stage and skipped the one that lasts years. RadiusPoint runs the long stage on ExpenseLogic: every invoice is a test of the contract you already signed.

In this article

The five stages of the contract lifecycle

The contract lifecycle for telecom and utility spend moves through five stages, and only one of those stages lasts for years. Request names the need, the owner, and the budget code. Draft puts rates and service IDs into a template. Execute collects approvals and signatures. Manage tests invoices every cycle. Renew or end is the notice, the export, and the stop-bill.

This is not the six-stage telecom lifecycle of inventory, activation, usage, invoice validation, MACD, and deactivation. A circuit can finish its lifecycle while the contract auto-renews. A contract can end while the circuit is still billing. RadiusPoint has to see both, which is why ExpenseLogic holds the contract image next to the inventory record.

A TEM implementation is the calendar for standing this process up. The stage names do not change because a tool vendor sold you a repository. If stage 4 has no owner, you do not have a lifecycle. You have a filing cabinet with a start date.

Why does most contract leakage happen after execution?

Most contract leakage happens after execution because procurement and legal exit when the signature lands, and operations inherit a PDF they cannot test. WorldCC puts the average loss at 11 percent of contract value. On a $500 million spend base that is about $55 million a year.

WorldCC’s Closing the Procurement Value Gap report, covered by Digital Journal on 5 February 2026, is the public source. Complex supplier systems can climb above 15 percent.

The same research splits the 11 percent. Unrecorded scope changes: 2 to 3 percent. Missed price adjustments: 1 to 2 percent. Dormant gain-share and improvement clauses: another 1 to 2 percent. WorldCC modeling says a rebuilt post-award model can recover 2 to 3 percent in year one. Those are category figures, not RadiusPoint results. Tim Cummins’s line still holds: commercial intent vanishes in delivery.

RadiusPoint sees that delivery gap on telecom expense management invoices that no longer match the rate table, and on UEM accounts that outlive the site. The signature was fine. Stage 4 never started.

Who owns each stage for telecom and utility spend?

Stage ownership for telecom and utility contracts splits across finance, IT or facilities, and a named operator on the live account. WorldCC flags unclear responsibility as one of the two most severe capability gaps. Buyer guides list stages. They do not name who acts on a BAN, a meter, or a mobile line.

About 70 percent of Legal-Procurement pairs communicate poorly, and only 15 percent share contracting technology, per WorldCC’s legal-procurement work.

Stage Finance IT / facilities Named operator (RadiusPoint on ExpenseLogic)
Request Approves budget Names the need and the site Opens the record
Draft Confirms commercial terms Confirms technical scope Loads rates and service IDs
Execute Signs or countersigns Confirms install plan Files the image
Manage Sets dispute thresholds Confirms the service is still live Audits lines, files disputes, ages credits
Renew or end Owns the dollar decision Confirms still needed Sends notice, exports the file, files the stop-bill

If a cell is empty, that stage is theatre. RadiusPoint will fill the operator column on a managed engagement. You still own the dollar column. When you need TEM is the trigger that this split has already failed in-house.

The invoice-as-contract test

RadiusPoint’s invoice-as-contract test treats each monthly telecom or utility bill as a live exam of the executed agreement on file. A stored PDF is not a passing score. Generic CLM software celebrates execution. RadiusPoint scores the next invoice, then the one after that, inside ExpenseLogic.

A pass means the billed rate equals the table, every ID still exists in inventory, closed sites are not still billing, credits posted rather than only promised, and the renewal clock has an owner. An invoice audit finds the miss. Invoice audit versus three-way match explains why AP matching a PO is not this test. A PO does not hold a tariff class or a circuit ID.

Telecom refund recovery is what a failed test becomes once someone files. A Fortune 100 manufacturer working with RadiusPoint recovered $450,000 in telecom refunds in year one, with $850,000 in ongoing annual savings and a $1.3 million year-one impact. Inventory mismatches have recovered $174,000 in re-credits. Those dollars are stage-4 output.

What should happen in the 90 days before a renewal decision?

The 90 days before a telecom or utility renewal should produce a written decision, an inventory export, and a notice that went out. A calendar pop-up on the folder is not that packet. Those 90 days are stage 5 of the lifecycle, not a reminder in legal’s inbox.

RadiusPoint runs that window against ExpenseLogic: usage, credits, vacant sites, zero-use lines, and the contracted rate versus what billed. WorldCC says poorly planned renewals are one of the buckets inside the 11 percent.

A healthcare provider working with RadiusPoint reduced telecom expenses 26 percent. A food service client cut mobility cost 22 percent and more than $400,000 in year one on 600-plus lines after 56 departed users were still billed. HumanGood, a named client, published a 315 percent ROI. Use those as proof a program can pay. Use the 90-day window to decide whether this term should.

Switching TEM providers without losing inventory is the export problem if you leave. TEM onboarding data is the intake problem if you start. Renewal is both, compressed into one notice window.

ExpenseLogic covers the long post-signature stage

ExpenseLogic covers the long post-signature stage by holding the contract image, the rate table, the inventory, and the invoice in one record. RadiusPoint analysts audit lines and file disputes. You keep budget approval. A CLM tool that stops at e-signature is still sitting in stage 3.

The ExpenseLogic platform is the working paper for stage 4.

RadiusPoint has been in this work since January 1992. ISO 9001 certification has been in place since September 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. The capability statement and about page carry firm facts. Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That is a hedged category range, not a RadiusPoint guarantee.

A utility bill audit is the meter-level exam inside stage 4. A telecom accrual file is how finance sees stage 4 at month-end. Telecom audit services find the miss. Managed mobility is stage 4 for lines and devices. This page is the stage map that makes those jobs one process.

FAQ

Is the contract lifecycle the same as vendor contract management?

No. The lifecycle is the stage map. Vendor contract management is the operating match inside the long stage. Use this page to see which stage you are in. Use the invoice-as-contract test on this page as the working version of stage 4.

How is this different from telecom lifecycle management?

Telecom lifecycle management tracks the asset from order through deactivation. Contract lifecycle management tracks the agreement from request through renew or end. RadiusPoint has to run both, because a dead circuit can still have a live term, and a dead term can still have a live bill. Do not merge the two URLs.

Do we need e-signature software to have a CLM process?

E-signature covers stage 3. It does not audit an invoice, file a dispute, or send a stop-bill. RadiusPoint will work with whatever signature tool you already have. If stage 4 is empty, buying another signing product will not fill it.

What is a BAN in the contract lifecycle?

A BAN is the billing account number the carrier or utility uses as the commercial identity of the account. RadiusPoint loads the BAN into ExpenseLogic at draft and tests it at every manage cycle. If the BAN on the invoice is not the BAN on the contract image, the test has already failed.

When should we terminate a carrier contract instead of renewing?

Terminate when the inventory, the rate, or the site footprint no longer matches the term, and the 90-day window still lets you send notice. RadiusPoint will put that evidence in the file. A renewal that nobody can defend with last year’s invoices is a default, not a decision.

What to do before the next signature

Print the five stages. Write a name in every cell of the owner table for one carrier and one utility account. If stage 4 is blank, you are buying a signature. RadiusPoint will fill that cell for a managed ExpenseLogic engagement. Every month you skip it is another sitting of the exam you are not taking.

References

  1. Closing the Procurement Value Gap | World Commerce and Contracting
  2. Contracting: The Overlooked Source of Procurement Value | World Commerce and Contracting
  3. Contracts signed, value lost: How businesses are leaking 11% of spend | Digital Journal, 5 February 2026
  4. Telecom Lifecycle Management: A Practical Guide | RadiusPoint
  5. Telecom Expense Management Services | RadiusPoint
  6. Utility Expense Management | RadiusPoint
  7. Managed Mobility Services | RadiusPoint
  8. ExpenseLogic | RadiusPoint
  9. How Long a Telecom Expense Management Rollout Actually Takes | RadiusPoint
  10. Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
  11. Invoice Audit vs Three-Way Match | RadiusPoint
  12. How Companies Recover Telecom Refunds and Credits From Carriers | RadiusPoint
  13. Signs Your Company Has Outgrown Managing Telecom In-House | RadiusPoint
  14. What Do You Lose When You Switch TEM Providers? | RadiusPoint
  15. The Data a TEM Provider Needs Before Day One | RadiusPoint
  16. How to Audit a Utility Bill for Errors | RadiusPoint
  17. What a Telecom Accrual File Is, and How Finance Teams Build One | RadiusPoint
  18. Telecom Audit Services | RadiusPoint
  19. HumanGood Achieved 315% ROI with RadiusPoint | RadiusPoint
  20. Capability Statement | RadiusPoint
  21. About RadiusPoint | RadiusPoint
  22. Sharon R. Watkins | RadiusPoint
  23. ExpenseLogic reviews | Capterra

Related articles

Disclaimer

This article is general information for finance, IT, procurement, and facilities teams running a contract lifecycle for telecom, utility, and wireless spend. It is not legal advice. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results. Category-level ranges from WorldCC and from TEM industry research are hedged and are not RadiusPoint promises.

Why Businesses Conduct Energy Audits and What They Reveal

cost savings0

For most businesses, energy is one of the largest and most unpredictable operating expenses. Utility bills are rising, budget pressure is increasing, and there’s a growing demand for sustainable business practices.

In response, many leaders are asking a critical question: “We know our energy costs are high, but we don’t have clear visibility into our usage. 

Where do we even start?”

The answer is an energy audit.

An energy audit is the first and most important step in taking control of your organization’s energy consumption. It’s a systematic review of how, where, and when your business uses energy, and it provides a clear roadmap for reducing costs and improving efficiency.

What Is a Business Energy Audit?

A business energy audit is a comprehensive analysis of your energy consumption and billing data to identify opportunities for cost savings and efficiency improvements. It goes far beyond a simple walkthrough of your facility.

A proper commercial energy assessment involves a detailed examination of your utility invoices, rate structures, and consumption patterns to uncover hidden inefficiencies and billing errors.

The primary purpose of an energy audit is to answer three key questions:

  1. How much energy is our business using?
  2. Where are we wasting energy and money?
  3. What are the most cost-effective ways to reduce our consumption and costs?

Why an Energy Audit Is a Strategic Imperative

Conducting a thorough energy audit is not just an exercise in data collection. It’s a strategic initiative that delivers significant benefits across the entire organization.

Unlock Hidden Cost Savings

This is the most immediate and compelling benefit. A detailed audit can uncover billing errors, identify overcharges, and reveal opportunities to switch to more favorable rate plans. The result is immediate and ongoing cost savings that flow directly to your bottom line.

Boost Operational Efficiency

An energy audit often reveals operational inefficiencies that go beyond energy consumption. By understanding how and when you use energy, you can optimize processes, improve equipment performance, and reduce maintenance costs, leading to a leaner, more efficient operation.

Strengthen ESG and Sustainability Goals

For companies with ESG (Environmental, Social, and Governance) goals, an energy audit provides the foundational data needed to measure, manage, and report on their environmental impact. It’s a critical first step in any credible sustainability program, providing the verifiable data that stakeholders demand.

The Hidden Hurdles in Conducting an Energy Audit

While the benefits are clear, many businesses struggle to conduct effective energy audits. The challenges are often rooted in the complexity and fragmentation of energy data.

  • The Data Deluge: For multi-location businesses, energy data is often scattered across hundreds of PDF invoices from dozens of different utility providers. There is no centralized system to aggregate and analyze this information, making a comprehensive audit nearly impossible.
  • The Resource Drain: In-house teams are already stretched thin. They rarely have the time or specialized expertise to conduct a detailed audit of complex utility bills, which are notoriously difficult to decipher.
  • The Accuracy Trap: Manual data entry is prone to errors, leading to an inaccurate picture of your energy consumption. Without consistent, reliable data, it’s impossible to benchmark facilities or track the impact of efficiency initiatives.
  • The Action Gap: An audit is only as valuable as the actions you take based on its findings. Many businesses lack the resources to implement the recommended changes and track the resulting savings, leaving money on the table.

How Centralized Data Transforms Energy Audits

The solution to these challenges is to centralize your energy data. By automating the collection and processing of your utility invoices, you can create a single source of truth for your energy consumption and costs. 

This is where a technology-driven partner like RadiusPoint can make a significant impact.

Our ExpenseLogic platform ingests, processes, and audits all your utility invoices, regardless of the provider or format. 

This provides the clean, accurate, and centralized data needed to conduct a thorough and effective energy audit. Instead of spending weeks or months manually collecting data, you can get instant visibility into your energy spend and identify savings opportunities in a fraction of the time.

What Happens After an Energy Audit?

An energy audit is not the end of the journey; it’s the beginning. The audit report will provide a list of recommended actions, from simple operational changes to more significant capital investments. 

The next step is to prioritize these actions based on their cost, potential savings, and alignment with your business goals.

This is where a partner like RadiusPoint can provide ongoing support. We not only help you conduct the initial audit, but we also provide the ongoing monitoring and reporting needed to track your progress, measure your savings, and ensure that your energy management program delivers long-term value.

Final Thoughts

In today’s competitive landscape, businesses can no longer afford to treat energy as an uncontrollable expense. An energy audit is the first step in transforming your energy management from a reactive, administrative task into a proactive, strategic discipline.

By leveraging technology and expert support to overcome the common data challenges, you can unlock the full potential of an energy audit and turn valuable insights into measurable bottom-line savings.

Ready to uncover your hidden energy savings? 

Contact RadiusPoint today to learn more about our energy audit services.

two men shaking hands

Vendor Contract Management for Telecom and Utility Spend

Services0

By Sharon Watkins, Founder and CEO, RadiusPoint · 12 min read

Vendor contract management for telecom and utility spend is the work of matching every invoice line to a live contract rate, term, and service ID. A signed PDF in a shared drive does not do that work. The bill can still arrive at last year’s rate.

Vendor contract management is the operating discipline that stores vendor agreements, ties rates to service IDs, and tests each invoice against those terms before payment. Generic contract-lifecycle software stores documents. This page is the TEM and utility version of the job: RadiusPoint analysts working inside ExpenseLogic against carriers, energy providers, and wireless accounts. It is not a CLM SaaS explainer.

World Commerce and Contracting, with Ironclad, puts average post-signature value leakage at 11 percent of contracted spend. On a $500 million base that is about $55 million a year, as Digital Journal reported on 5 February 2026. RadiusPoint’s published proof on the same failure mode is smaller and named: $120,000 a year from contract rate optimization, plus a Fortune 100 manufacturer that recovered $450,000 in telecom refunds in year one.

Key Takeaways

  • WorldCC research puts average post-signature contract-value leakage at 11 percent of spend, rising above 15 percent in complex supplier systems.
  • RadiusPoint has recovered $120,000 a year from contract rate optimization, and a Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one.
  • The Contract-to-Invoice Match is RadiusPoint’s five-field test: vendor plus BAN, service ID, contracted rate, term plus notice, and disconnect duty.
  • Auto-renew clocks differ by category: 30 to 90 days on circuits, 30 to 60 days or none on tariffs, about 30 days on wireless lines.
  • ExpenseLogic stores the contract image and the rate table against the service ID. RadiusPoint’s named analysts run the monthly match. Storage alone is not the service.

The Short Version

Vendor contract management for TEM and utility spend is an invoice operation with a contract file attached. If you cannot name the BAN, the service ID, and the notice date, you are storing PDFs, not managing contracts.

In this article

Vendor contract management is invoice operations, not a CLM repository

Vendor contract management for telecom and utility spend is the month-to-month work of testing invoices against signed rates, terms, and service IDs. A repository that holds PDFs, clause libraries, and e-signature packets is useful for legal. It does not tell accounts payable whether this month’s MRC still matches the table RadiusPoint loaded into ExpenseLogic. The operating object is the invoice line, not the folder.

RadiusPoint has sold this as software plus people since 1992. ExpenseLogic is the platform. Named analysts audit lines against contracted rates and against inventory, rather than sampling. That model is the commercial page for telecom expense management. This article is the contract-operations layer sitting under that service.

Procurement sources the deal. Vendor contract management keeps the deal honest after signature. If your process ends when Legal files the PDF, you have finished the short stage and skipped the long one.

Why do telecom and utility contracts leak after they are signed?

Telecom and utility contracts leak after signature because invoices keep billing while the signed PDF sits unused in a shared drive. WorldCC puts that erosion at 11 percent and treats it as an accumulation, not a single miss. Unrecorded scope changes take an estimated 2 to 3 percent of spend.

WorldCC’s Closing the Procurement Value Gap work, summarized by Tim Cummins, is the source for those shares. Missed price adjustments add another 1 to 2 percent. Carriers and utilities produce that leakage in a specific shape. A circuit is disconnected in the field and still billed. A meter sits at a vacant site. A wireless line stays live after the employee leaves. WorldCC also found that about 70 percent of Legal-Procurement pairs communicate poorly, and that only 15 percent of organizations share contracting technology between those two functions. Those are category findings, not RadiusPoint results.

RadiusPoint sees the same failure on Utility Expense Management (UEM) accounts when a location closes and the tariff does not. Vacant utility cost recovery is the UEM version of a contract that outlived the site. The PDF did not fail. The monthly test failed.

The Contract-to-Invoice Match

The Contract-to-Invoice Match is RadiusPoint’s five-field test that a TEM or utility invoice line must pass against the signed agreement. Generic CLM pages teach request, draft, and signature. They do not teach a five-field match built for BANs, circuit IDs, meters, and mobile lines.

RadiusPoint stores the contract image inside ExpenseLogic and retains the terms against the service ID, with expiration dates and obligation alerts for termination fees. An invoice audit that cannot see those five fields is a three-way match with the contract missing. Invoice auditing services find the dollar error. The Match is how you know the error is a contract failure, not an AP coding failure.

Field On the contract On the invoice line Fail mode if missing
Vendor plus BAN Legal name and billing account number Invoice header BAN You cannot prove which agreement the bill is claiming
Service ID Circuit ID, meter number, or mobile line Line-level identifier A rate with no live ID cannot be tested
Contracted rate MRC, tariff class, or per-line rate Billed unit price Last year’s rate can bill all year
Term plus notice End date and auto-renew window as dates Cycle the bill belongs to The clock expires in a PDF highlight
Disconnect duty Who files the stop-bill, and the fee Presence or absence of the charge The service dies. The bill does not.

A pass is five fields populated on both sides. A stored PDF with none of those fields extracted is not a pass.

How long is the auto-renew clock on a telecom or utility contract?

The auto-renew clock on a telecom or utility contract is the notice window stored against the service ID, not against a folder. Circuits usually sit at 30 to 90 days. Wireless lines sit near 30 days. Utility accounts may have a 30 to 60 day notice, or no bilateral clock at all on a tariff class.

RadiusPoint treats those as three different clocks inside ExpenseLogic, not as one renewal reminder on a folder.

WorldCC modeling says organizations that rebuild post-award management can recover 2 to 3 percent of spend in the first year, and 5 to 10 percent over three years. That is a category range, not a RadiusPoint promise. The operating fact is simpler. If notice is not a date on the service ID, the vendor’s preferred term wins by silence.

A letter of agency is what lets RadiusPoint talk to the carrier when that clock is running. The questions that belong in the TEM contract itself sit on the pre-sign question list.

What RadiusPoint recovers when the contract and the invoice disagree

RadiusPoint recovers cash when the billed rate, the live inventory, and the signed terms disagree, and the published cases put those dollars in the open. A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one. Inventory work has recovered $174,000 in re-credits when services did not match the bill.

That same manufacturer added $850,000 in ongoing annual savings and a $1.3 million year-one impact.

An elevator company cut monthly waste expenditure 28 percent after the contract and the haul did not match. A multi-location client stopped $1,500 a month, $18,000 a year, on utilities at closed locations. One line of unneeded toll-free numbers ran $18,000 a year. A food service client working with RadiusPoint on 600-plus mobility lines cut cost 22 percent and more than $400,000 in year one. Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category observation, not a RadiusPoint guarantee.

Managed mobility services is where wireless contracts meet employee IDs. Zero-use mobile lines are a contract that outlived the user. Telecom refund recovery is what happens after the Match fails and someone files. The dollars above are what the Match is for.

ExpenseLogic keeps rates tied to service IDs

ExpenseLogic keeps vendor contract rates tied to service IDs, with the contract image, expiration dates, and termination-fee alerts in the same record. RadiusPoint analysts run that match. You keep budget approval. One platform covers telecom, wireless, and utilities at the same month-end.

RadiusPoint is ISO 9001 certified since 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. A capability statement and the about page carry the firm facts. Credentials tell you the operator is real. The Match tells you the contract is being used.

Cost allocation across departments is a downstream job once the line is correct, covered on expense cost allocation. A MACD that does not update the contract record is how a disconnect fails the Match the following month.

FAQ

Is vendor contract management the same as procurement?

No. Procurement sources and awards the agreement. Vendor contract management for TEM and utility spend tests the invoices that follow. RadiusPoint sits on the second job. A team that only negotiates rates and never scores the bill is finished at signature, which is where WorldCC says the 11 percent starts.

Who owns vendor contracts when IT, finance, and facilities all buy services?

Finance should own the dollar decision, IT or facilities should confirm the service is still needed, and a named operator should keep the record. RadiusPoint will be that operator on an ExpenseLogic engagement. If three departments can buy and nobody can close a BAN, you do not have vendor contract management. You have three inboxes.

Do we still need a letter of agency to manage carrier contracts?

Yes, if anyone other than your own staff must pull invoices or file a disconnect with the carrier. Scope it. A read-only billing grant is not ordering rights. RadiusPoint will tell you which grant it is asking for, and you should be able to revoke it.

Can a generic CLM tool replace TEM contract operations?

It can store the PDF, route approvals, and fire a calendar reminder. It cannot, by itself, audit a telecom or utility invoice line against a rate table and an inventory of record. RadiusPoint’s work starts where that reminder would have fired and the bill still came in wrong.

How often should we reopen a wireless or utility agreement?

Reopen when the inventory, the rate, or the site footprint has moved, not only when the term ends. RadiusPoint watches those three signals every cycle. A wireless pool that still bills departed users, or a tariff on a vacant meter, is already a reopened contract. You just have not scheduled the meeting.

What to do before the next invoice cycle

Pick one carrier BAN and one utility account. Fill the five Match fields from the signed file, then from last month’s invoice. If a cell is empty, that is the operating gap. RadiusPoint will fill those cells for a managed ExpenseLogic engagement. Every cycle you pay without them is a cycle the 11 percent can keep.

References

  1. Contracting: The Overlooked Source of Procurement Value | World Commerce and Contracting
  2. Closing the Procurement Value Gap | World Commerce and Contracting
  3. Contracts signed, value lost: How businesses are leaking 11% of spend | Digital Journal, 5 February 2026
  4. Telecom Expense Management Services | RadiusPoint
  5. Utility Expense Management | RadiusPoint
  6. Managed Mobility Services | RadiusPoint
  7. ExpenseLogic | RadiusPoint
  8. Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
  9. Invoice Auditing Services | RadiusPoint
  10. Vacant Cost Recovery: The Utility Bills Nobody Is Watching | RadiusPoint
  11. Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
  12. Questions to Ask a TEM Provider Before You Sign | RadiusPoint
  13. Finding and Killing Zero-Use Mobile Lines | RadiusPoint
  14. How Companies Recover Telecom Refunds and Credits From Carriers | RadiusPoint
  15. The MACD Process in Telecom Expense Management, Explained | RadiusPoint
  16. Allocating Telecom and Utility Costs Across Departments | RadiusPoint
  17. 4 Benefits of Telecom Expense Management (TEM) | RadiusPoint
  18. Capability Statement | RadiusPoint
  19. About RadiusPoint | RadiusPoint
  20. Sharon R. Watkins | RadiusPoint
  21. ExpenseLogic reviews | Capterra

Related articles

Disclaimer

This article is general information for finance, IT, procurement, and facilities teams managing telecom, utility, and wireless vendor contracts. It is not legal advice. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results. Category-level ranges from WorldCC and from TEM industry research are hedged and are not RadiusPoint promises.

business report graphs charts business reports pile documents business concept

What Is ESG Reporting? A Practical Guide for Modern Businesses

Education/Higher Learning, UEM0

Not long ago, Environmental, Social, and Governance (ESG) goals were a “nice-to-have” for many organizations, a footnote in an annual report or a small section on the company website. Today, that has fundamentally changed.

ESG reporting has moved from the periphery to the core of business strategy, driven by intense pressure from investors, regulators, and customers who demand transparency and accountability.

But for many executives, a common concern has emerged: “We have ESG goals, but no clear way to report on them accurately.”

This isn’t a failure of ambition; it’s a data problem.

So, what is ESG reporting, and why has it become one of the most critical challenges for businesses today?

What Is ESG Reporting?

ESG reporting is the process of publicly disclosing an organization’s data related to its environmental, social, and governance performance. It’s a framework for measuring a company’s impact beyond its financial results. Unlike traditional financial reporting, which focuses on profit and loss, this reporting provides a holistic view of a company’s sustainability and ethical footprint.

Let’s break down the three pillars:

  • Environmental (E): This pillar covers a company’s impact on the planet. The data required includes energy consumption, water usage, greenhouse gas (GHG) emissions (Scope 1, 2, and 3), waste management, and resource depletion.
  • Social (S): This pillar addresses how a company manages relationships with its employees, suppliers, customers, and the communities where it operates. Key data points include employee health and safety, labor standards, diversity and inclusion metrics, and data privacy.
  • Governance (G): This pillar deals with a company’s leadership, executive pay, audits, internal controls, and shareholder rights. It’s about ensuring the company is managed ethically, transparently, and in the best interests of its stakeholders.

While often confused with Corporate Social Responsibility (CSR) or sustainability reports, ESG reporting is distinct. It is a data-driven, formal disclosure process tied to specific frameworks (like GRI, SASB, or TCFD) and is increasingly scrutinized by investors and regulators.

Read RadiusPoint Case Study on ESG for an in-depth understanding.

Why ESG Reporting Is No Longer Optional

The shift toward mandatory and standardized reporting is being driven by three powerful forces:

  1. Investor and Financial Pressure: Investors and lenders no longer see ESG as a non-financial issue. They recognize that strong ESG performance is a proxy for good management and long-term financial resilience. They are increasingly using ESG data to assess risk, allocate capital, and make investment decisions.
  2. Regulatory and Compliance Expectations: Governments worldwide are introducing regulations that mandate ESG disclosure. The European Union’s Corporate Sustainability Reporting Directive (CSRD) and the U.S. Securities and Exchange Commission’s (SEC) proposed climate disclosure rules are just two examples. Compliance is quickly becoming non-negotiable.
  3. Brand Trust and Customer Expectations: Modern consumers want to buy from and work for companies that align with their values. A strong, transparent ESG report is a powerful tool for building brand trust, attracting and retaining talent, and differentiating your business in a crowded market.

Why Is ESG Reporting So Hard?

If the importance of ESG is so clear, why do so many companies struggle with it? The answer lies in the data. It is fundamentally a data collection, aggregation, and validation challenge. The traditional approach is often a logistical nightmare.

  • Manual Data Collection: Key data, especially for the “Environmental” pillar, is often trapped in thousands of PDF utility bills, spreadsheets, and disparate vendor portals. Collecting this information manually is a monumental task, prone to human error.
  • Accuracy and Consistency Issues: Without a centralized system, ensuring data is accurate, consistent, and auditable across dozens or hundreds of locations is nearly impossible. How can you be sure the energy consumption data from one facility is measured the same way as another?
  • Time and Resource Drain: The manual effort required to gather, clean, and report on ESG data consumes thousands of hours from finance, operations, and sustainability teams, pulling them away from their core responsibilities.

Read how RadiusPoint eliminated 800 hours of manual data collection for ESG reporting.

How Technology Simplifies ESG Data Collection

The biggest hurdle in this reporting is often the “E” in ESG, specifically, gathering accurate data on energy consumption, emissions, and other environmental metrics. This is where technology and specialized services can make a transformative impact.

At RadiusPoint, we support organizations by automating the most challenging part of this process. Our core business is processing and auditing complex, location-based invoices, including telecom, utility, and waste. This provides a direct, automated, and auditable data stream for your reporting needs.

Instead of manually chasing down hundreds of utility bills, our platform captures, validates, and centralizes all your energy and utility data. This means that when it’s time to report on your Scope 2 emissions or overall energy consumption, the data isn’t just available, it’s accurate, consistent, and ready for your ESG framework.

Conclusion: From Burden to Business Intelligence

ESG reporting is evolving from a burdensome compliance exercise into a powerful source of business intelligence that can unlock cost savings, mitigate risk, and enhance brand value. The key to success is moving beyond manual processes and embracing a data-driven approach.

By automating the collection of foundational data, like your energy and utility consumption, you can transform reporting from a source of frustration into a strategic advantage. It allows you to focus less on chasing data and more on using it to build a more resilient, sustainable, and profitable business. Ready to streamline your ESG data collection?

Learn how RadiusPoint can provide the accurate, auditable data you need to power your ESG reporting.

Contact RadiusPoint.

Cost Cutting Strategies

How Human Good Achieved a 315% ROI with RadiusPoint

Case Study0

Discover how one of America’s largest nonprofit senior living providers partnered with RadiusPoint to eliminate operational waste, drive significant savings, and establish a new benchmark for nonprofit efficiency through a technology-enabled shared services model.

thumbnail Infographic for RadiusPoint

Executive Summary

HumanGood, the sixth-largest nonprofit owner and operator of senior living communities in the U.S., was grappling with a decentralized and inefficient telecom expense management process. This system created significant financial leakage, operational burdens, and service disruptions that impacted over 9,200 residents.

By partnering with RadiusPoint, HumanGood undertook a strategic transformation, leveraging the ExpenseLogic platform and a shared services model to centralize and automate its entire telecom lifecycle.

The initiative delivered transformative results, proving that strategic automation can drive immense value in the nonprofit sector.

Key Metrics at a Glance:

  • $360,000 in Annual Hard-Dollar Savings (12% of total spend)
  • $150,000 in Annual Labor Efficiencies (soft savings)
  • 315% Average Monthly Return on Investment (ROI)
  • Invoice Cycle Time Reduced from 30 Days to 5 Days
  • 99.9% Invoice Processing Accuracy

The Client: A Mission-Driven Leader in Senior Living

HumanGood stands as a pillar in the nonprofit sector, dedicated to helping older adults live with purpose and joy. Operating over 100 affordable housing communities and 22 life plan communities across five states, the organization serves more than 9,200 residents. As a nonprofit, HumanGood operates with a profound sense of fiduciary responsibility.

Every dollar saved is a dollar that can be reinvested into its core mission: enhancing the quality of life for its residents.

This commitment to stewardship was the driving force behind its decision to address long-standing operational inefficiencies.

The Challenge: A Fractured System Undermining a Noble Mission

Before partnering with RadiusPoint, HumanGood’s approach to managing its vast telecom infrastructure was fragmented and manual. Lacking a centralized system, the organization faced a cascade of challenges that created a significant financial and operational drag.

1. Severe Financial Leakage

The decentralized process was rife with uncontrolled spending. Without proper oversight, unauthorized service orders were common, and inactive services often remained connected and billed for months.

The absence of a unified repository for invoices and contracts made it impossible to audit costs effectively, leading to substantial and unnecessary financial waste.

2. Crippling Operational Inefficiency

The Accounts Payable department was mired in a paper-based workflow that took 20 to 30 days to process a single telecom invoice. This involved manually chasing down data, seeking approvals, and coding invoices, a workload that consumed the equivalent of three full-time staff members.

The process was not only slow but also prone to errors, frequent delays, and misplaced invoices, creating frustration for both staff and vendors.

3. Complete Lack of Visibility

With no central database, HumanGood had no clear view of its telecom assets, services, or contractual obligations. This lack of visibility made it impossible to manage inventory, ensure compliance with vendor agreements, or make informed, data-driven decisions about its telecom spend.

4. Negative Impact on Residents and Staff

The operational shortcomings had real-world consequences. Service disruptions caused by missed or delayed payments directly impacted residents’ connectivity and well-being.

Internally, the frustrating and repetitive manual tasks led to low morale and diverted skilled finance professionals from more strategic, value-added work.

The Solution: A Strategic Partnership for End-to-End Transformation

RadiusPoint introduced a comprehensive, technology-enabled shared services solution designed to address HumanGood’s challenges from the ground up.

This was not merely a software installation but a strategic partnership focused on redesigning processes, aligning technology, and empowering people.

The core of the solution was RadiusPoint’s proprietary ExpenseLogic platform, which served as the engine for automation and centralization.

The multi-faceted solution included:

  • End-to-End Invoice Lifecycle Automation: RadiusPoint assumed full responsibility for HumanGood’s telecom invoice lifecycle. The ExpenseLogic platform automated everything from invoice receipt and processing to validation and payment, creating a single, streamlined workflow and reducing the cycle time to just five days.
  • Comprehensive Audit and Cost Optimization: The engagement began with a deep-dive audit of all existing telecom services and contracts. This process immediately identified and disconnected inactive services and optimized vendor contracts, yielding immediate hard-dollar savings.
  • Centralized Order and Inventory Management: Recognizing a critical gap, the project expanded to include full order management. All requests for new services or disconnections were centralized through ExpenseLogic, complete with automated approval paths and clear audit trails. This eliminated unauthorized orders and created a reliable, real-time inventory of all telecom assets.
  • Advanced Analytics and Real-Time Reporting: The ExpenseLogic platform provided HumanGood with on-demand access to dashboards and advanced analytics. For the first time, leadership could see a clear, accurate picture of telecom spend, track performance metrics, and make strategic decisions based on reliable data.

The Methodology: A Framework for Lasting Change

RadiusPoint’s success was underpinned by a hybrid Lean-Kaizen methodology. This dual approach focused on Lean principles to identify and eliminate non-value activities (waste) and Kaizen principles to foster a culture of continuous, team-driven improvement.

The implementation followed a structured six-month roadmap, ensuring a smooth transition without disrupting critical operations.

A cornerstone of the methodology was a robust change management and stakeholder engagement strategy.

RadiusPoint recognized that technology alone is not enough. To ensure adoption and long-term success, they focused on winning the trust of key stakeholders.

  • Overcoming Resistance: Resistance from IT middle management, who feared a loss of control, was addressed through education and by demonstrating how automation would serve as an enabler, not a replacement. Once they saw how the platform enhanced visibility and reduced repetitive tasks, they became strong advocates.
  • Building Internal Champions: The Accounts Payable team, initially burdened by the manual process, became the most supportive group. Freed from tedious tasks, they championed the new automated system, helping to educate their peers and build momentum for the initiative.
  • Data-Driven Communication: The most effective tool for winning support was a “What If” business case presentation that quantified the financial and productivity losses of maintaining the status quo. This, combined with weekly progress reviews and customized dashboards, made the benefits of the transformation tangible and undeniable for all stakeholders.

The Results: A New Standard for Nonprofit Efficiency

The partnership delivered results that exceeded all initial targets, creating a powerful ripple effect across the entire HumanGood organization.

Metric Before Transformation After Transformation with RadiusPoint Impact
Annual Hard-Dollar Savings Uncontrolled Spending $360,000 12% reduction in total spend from service optimization.
Annual Labor Efficiencies 3 FTEs on Manual Tasks $150,000 Staff reallocated to higher-value strategic work.
Average Monthly ROI N/A 315% Demonstrates exceptional and sustainable value creation.
Invoice Cycle Time 20–30 Days 5 Days 80% reduction, eliminating delays and service disruptions.
Invoice Processing Accuracy Prone to Human Error 99.9% Near-perfect accuracy, ensuring financial integrity.

Beyond these impressive numbers, the initiative transformed HumanGood’s operational culture. It fostered a commitment to continuous improvement, improved cross-functional collaboration between IT, Finance, and Operations, and established a repeatable model for automation-driven efficiency.

This success has not only strengthened HumanGood’s financial position but has also solidified its ability to deliver on its core mission for years to come.

Client Testimonial:

“The transformation was a major value-add, improving cost control, data integrity, and resident satisfaction. The outcome was a fully integrated, end-to-end telecom management process that enhanced financial accuracy, operational visibility, and strategic alignment with our shared services objectives. RadiusPoint’s expertise and technology were pivotal in achieving this success.”

— HumanGood Stakeholder

Transform Your Organization’s Potential into Performance

HumanGood’s story is a powerful testament to what is possible when a mission-driven organization embraces strategic automation.

If your organization is facing similar challenges with expense management, RadiusPoint can help.

Ready to see how much you could save?

  • Schedule a Demo – Get a personalized tour of the ExpenseLogic platform.
  • Contact Sales – Speak with one of our experts to discuss your specific needs.
vendor governance

What is Vendor Governance?

cost savings0

By Sharon Watkins, Founder and CEO, RadiusPoint · 12 min read

Vendor governance is the decision-rights framework that names who may open a BAN, file a dispute, waive an SLA credit, or let a contract auto-renew. It is not a scorecard, and it is not a contract repository. A scorecard tells you how the vendor performed. Governance tells you who was allowed to act when they did not.

KPMG’s 2026 Global Third-Party Risk Management Survey, published 20 March 2026 and covering 851 organizations, found that only 18 percent have TPRM fully integrated with enterprise risk, and only 53 percent call their programs mostly integrated. Just 17 percent rate their TPRM data as fully reliable. RadiusPoint’s job, since 1992, is to feed that framework with invoice-level evidence from ExpenseLogic so a governance meeting has facts, not vendor slides.

Key Takeaways

  • Vendor governance names who may act on a vendor. A scorecard names how that vendor scored. They are adjacent jobs, not the same page.
  • KPMG’s 2026 survey of 851 organizations found 18 percent full TPRM-ERM integration, 53 percent mostly integrated, and 17 percent fully reliable TPRM data.
  • Only 5 percent of those organizations run end-to-end managed TPRM. More than 80 percent outsource pieces. RadiusPoint is a named operator for expense vendors, not a substitute board.
  • The expense vendor decision-rights matrix assigns open/close BAN, dispute filing, SLA waiver, auto-renew, and LOA grant to finance, IT or facilities, and a named operator.
  • Governance cadence for expense vendors is monthly exceptions, quarterly decision logs, and an annual contract decision. None of those artifacts is a 1-to-5 score.

The Short Version

Vendor governance for telecom and utility spend is a written list of who may act, on what evidence, and how often they meet. If that list does not name a person for disputes, auto-renews, and letters of agency, you have a policy binder, not governance.

In this article

Vendor governance is decision rights, not a scorecard

Vendor governance is the written assignment of who may open a BAN, file a dispute, waive a credit, or allow auto-renew. A scorecard measures billing accuracy, SLA performance, and MACD speed. That measurement page already exists.

If nobody is allowed to stop an auto-renew, a perfect score still renews a bad deal.

Governance is the charter. The scorecard is a report the charter consumes. Multi-vendor support is a third term again: consolidating invoices across carriers, not OEM hardware break-fix.

Joey Gyengo, US Third-Party Risk Management Leader at KPMG LLP, put the bar this way: companies chase effectiveness, efficiency, and experience at once, and the work is building a process that is resilient and scalable, not ticking compliance boxes. RadiusPoint agrees. A binder of policies with no named actor on a BAN is a tick.

Why do telecom and utility vendors sit outside most governance programs?

Telecom and utility vendors sit outside most governance programs because they look like high-volume, low-glamour AP, while TPRM budgets chase cyber and regulatory onboarding. That defensive focus leaves the carrier BAN and the vacant meter in accounts payable, where nobody is governing them.

That same KPMG survey lists regulatory compliance as a top driver for 48 percent of respondents and cyber risk for 37 percent.

RadiusPoint has watched that blind spot for decades. A multi-location client paid $1,500 a month, $18,000 a year, on utilities at closed locations. Vacancy cost recovery has cut utility expenses 12 percent in the published case. Those are not cyber findings. They are governance findings that never made the TPRM agenda. Vacant utility cost recovery is the UEM version. Wireless versus TEM is the mobility version of the same miss: a line that TPRM never listed as a third party.

WorldCC still puts post-signature leakage at 11 percent of contract value. Expense vendors are where that 11 percent hides in plain sight, because the invoice arrives every month and looks routine. Governance that only onboards software and cloud vendors has already chosen its exceptions.

The expense vendor decision-rights matrix

The expense vendor decision-rights matrix is RadiusPoint’s five-row assignment of who may act on a BAN, a dispute, a waiver, and a renewal. TPRM guides describe onboarding, risk tiering, and reassessment. They do not name those five expense actions.

Decision Finance IT / facilities Named operator
Open or close a BAN Approves Requests Executes in ExpenseLogic
File a carrier dispute Sets the dollar threshold Provides evidence Files and ages the case
Waive an SLA credit Signs the waiver Confirms the outage Logs the waiver
Let a contract auto-renew Owns the dollar decision Confirms still needed Sends or holds notice
Issue or revoke an LOA Countersigns Scopes systems Holds the grant log

A letter of agency without a revoke path is a grant with no governor. TEM onboarding data is how the operator receives the files that make those rows real. If finance “owns vendors” and cannot name who files, the matrix is empty. RadiusPoint will occupy the operator column. You still occupy the waiver and the dollar columns.

What cadence should expense-vendor governance actually run on?

Expense vendor governance should run on three written meeting cadences, and none of those three artifacts is a weighted score. Use a monthly exception huddle, a quarterly decision log, and an annual contract decision. Scorecards already own monthly or quarterly KPI reviews. This cadence owns decisions.

Monthly: unmatched invoice lines, missed credits, vacant-site bills, zero-use lines. Artifact: an exception register. Quarterly: who filed, what aged out, which BANs drifted from inventory. Artifact: a decision log. Annual: renew, renegotiate, or terminate with the notice clock in writing. Artifact: a signed decision plus an export. KPMG found that 71 percent of organizations plan further TPRM-ERM integration over three years. Planning is not a meeting. A monthly register is.

An invoice audit feeds the monthly huddle. Invoice auditing services are how RadiusPoint staffs it.

How RadiusPoint’s managed model feeds governance without becoming the board

RadiusPoint feeds vendor governance with invoice evidence, dispute files, and inventory, and it never takes the client’s own board seat. Finance still signs waivers. You still own auto-renew. RadiusPoint is the named operator for telecom, utility, and wireless expense vendors.

KPMG found that more than 80 percent of organizations use managed services or outsourcing for some TPRM work, but only 5 percent have adopted an end-to-end managed model. ExpenseLogic is the evidence pack. RadiusPoint analysts audit lines, file disputes, and keep inventory current. A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one, with $850,000 in ongoing annual savings and a $1.3 million year-one impact. A food service client cut mobility cost 22 percent and more than $400,000 in year one on 600-plus lines. Inventory work recovered $174,000 in re-credits. Those dollars show up in a governance pack as cases, not as a slide that says “we manage vendors.”

The commercial pages are telecom expense management, Utility Expense Management (UEM), and managed mobility services. Vendor evaluation is the buyer’s companion. This page is the charter those services report into.

Governance versus third-party risk: where the invoices sit

Third-party risk management onboards and tiers vendors for cyber, privacy, and continuity, which is a different job from expense-vendor governance. Vendor governance for expense spend decides who may spend, dispute, and renew once that vendor is already inside the building.

KPMG’s 851-organization sample is the current public bar: 18 percent full integration, 17 percent fully reliable data, 5 percent end-to-end managed. RadiusPoint does not claim to replace TPRM. It claims to put invoices on the table TPRM usually skips.

RadiusPoint is ISO 9001 certified since 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. The capability statement and about page carry firm facts. Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That is a hedged category range, not a RadiusPoint guarantee.

ESG reporting has eliminated 800 man-hours of data gathering in the published RadiusPoint case. That is a governance output, not a TPRM questionnaire.

FAQ

Is vendor governance the same as vendor management?

Vendor management is the day-to-day relationship. Vendor governance is the charter that says who may do what when that relationship breaks. RadiusPoint will manage expense vendors on ExpenseLogic. Governance is still yours. If the two words are used as synonyms in your policy, rewrite the policy before the next auto-renew.

How is vendor governance different from a vendor scorecard?

A scorecard scores performance. Governance assigns rights. RadiusPoint already publishes the scorecard URL. Use that page for weights and thresholds. Use this page for who may file, waive, and renew. A high score with no named actor still auto-renews.

Does ISO 9001 count as vendor governance?

ISO 9001 is RadiusPoint’s quality system, certified since 2002. It is evidence that the operator runs a controlled process. It is not your charter. You still need the matrix and the cadence for your own BANs, even when the operator is certified.

Who should chair the expense vendor review?

Finance should chair the quarterly decision log, because the dollars sit there. IT or facilities brings the live-or-not evidence. RadiusPoint brings the exception register. A review chaired only by the operator is a status meeting. A review with no operator is a story meeting.

Do we need a separate governance policy for utilities?

You need the same five rights applied to meters and vacant sites, which generic TPRM policies rarely name. RadiusPoint’s UEM work is that application. A policy that lists “critical software vendors” and never lists the electric account at a closed store has already created the blind spot.

What to do before the next vendor review

Print the five-row matrix. Write a name in every cell for one carrier and one utility account. Schedule the monthly exception huddle against last month’s invoices. If a cell is empty, that is the governance gap. RadiusPoint will fill the operator column for a managed ExpenseLogic engagement. The other columns stay yours.

References

  1. The 2026 KPMG Global Third-Party Risk Management Survey | KPMG, 20 March 2026
  2. Closing the Procurement Value Gap | World Commerce and Contracting
  3. What is a vendor scorecard? | RadiusPoint
  4. Complete Guide on Multi Vendor Support | RadiusPoint
  5. Telecom Expense Management Services | RadiusPoint
  6. Utility Expense Management | RadiusPoint
  7. Managed Mobility Services | RadiusPoint
  8. ExpenseLogic | RadiusPoint
  9. Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
  10. Invoice Auditing Services | RadiusPoint
  11. Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
  12. The Data a TEM Provider Needs Before Day One | RadiusPoint
  13. Vacant Cost Recovery: The Utility Bills Nobody Is Watching | RadiusPoint
  14. Wireless Expense Management vs Telecom Expense Management | RadiusPoint
  15. 4 Benefits of Telecom Expense Management (TEM) | RadiusPoint
  16. Why You Need a Managed Mobility Provider | RadiusPoint
  17. Vendor Evaluation | RadiusPoint
  18. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
  19. Capability Statement | RadiusPoint
  20. About RadiusPoint | RadiusPoint
  21. Sharon R. Watkins | RadiusPoint
  22. ExpenseLogic reviews | Capterra

Related articles

Disclaimer

This article is general information for finance, IT, procurement, risk, and facilities teams designing vendor governance for telecom, utility, and wireless spend. It is not legal, compliance, or TPRM advice. Outcomes cited are from specific RadiusPoint client engagements already in the published proof library and are not a guarantee of future results. KPMG 2026 survey figures and WorldCC leakage ranges are third-party research, hedged, and are not RadiusPoint promises.

invoice processing

Invoice Processing for Telecom and Utility Spend

Education/Higher Learning0

By Sharon Watkins, Founder and CEO, RadiusPoint · 12 min read

Invoice processing for telecom and utility spend is the six-station run that takes a billing account number from receipt to a coded pay-or-hold decision. A shared AP mailbox that keys a header total does not do that work. The bill can still pay a circuit that died last quarter.

Invoice processing is the operating sequence that receives a vendor invoice, captures every line, tests those lines against live inventory and contracted rates, codes the general ledger, and either pays the clean lines or holds the exceptions. Generic accounts-payable software parses a PDF. This page is the Telecom Expense Management (TEM) and Utility Expense Management (UEM) version of the job: RadiusPoint analysts working inside ExpenseLogic against carriers, energy providers, and wireless accounts.

Perry D. Wiggins, writing in CFO.com from APQC’s database of 1,485 organizations, put top-quartile AP cost at $2.07 per invoice or less, the median at $5.83, and the bottom quartile at $10.00 or more. Those are cross-industry supplier invoices. A telecom or utility invoice that fails inventory match is not a $2.07 problem. It is a billed service that may not exist. RadiusPoint’s published path is two-day invoice processing on ExpenseLogic, with named analysts on the exceptions.

Key Takeaways

  • Invoice processing for TEM and UEM is a six-station run: receive, capture, inventory, rate, allocate, and pay or hold. Header OCR stops at station 2.
  • APQC, via Perry D. Wiggins in CFO.com, puts median AP cost at $5.83 per invoice across 1,485 organizations, with the top quartile at $2.07 or less and the bottom at $10.00 or more.
  • RadiusPoint’s published FAQ path is two-day invoice processing. ExpenseLogic stores the BAN, the service ID, and the GL code on the same record.
  • Processing is the run from inbox to GL. An invoice audit is the test of whether the bill is true. They share a file. They are not the same page.
  • A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one after the processed file and the inventory disagreed. Processing produced the file. The fail produced the cash.

The Short Version

Invoice processing for TEM and utility spend is a six-station run from BAN receipt to a coded pay-or-hold. If you cannot name the service ID, the contracted rate, and the hold queue, you are keying bills, not processing them.

In this article

Invoice processing is the run from inbox to GL

Invoice processing for telecom and utility spend is the monthly run that turns a carrier invoice into a coded general-ledger file. A repository that stores PDFs is useful for audit later. It does not tell accounts payable whether this month’s MRC still belongs to a live circuit inside ExpenseLogic. The operating object is the invoice line, not the folder.

RadiusPoint has sold this as software plus people since 1992. ExpenseLogic is the platform. Named analysts work every line against contracted rates and against inventory, rather than sampling. That model is the commercial page for telecom expense management. This article is the processing layer sitting under that service: how the BAN lands, how the file is built, and how a hold is a feature.

Generic AP pages teach receipt, OCR, two-way match, and payment. They treat a telecom invoice like a box of copier paper. The paper has a PO. The circuit has a service ID, a tariff or MRC, a location, and a disconnect duty. If your process ends when the PDF is parsed, you have finished the short station and skipped the long ones.

How is invoice processing different from an invoice audit?

Invoice processing is the operational run that receives, captures, codes, and pays or holds every TEM and utility invoice line. An invoice audit is the test that scores those same lines against contract, inventory, and usage so a fail can be disputed. They share a file. They do not share a job description, a KPI, or a page on this site.

Invoice auditing services is the commercial offer. You can process a clean bill. You cannot audit a bill you never ingested.

A three-way match asks whether PO, receipt, and invoice agree. A TEM or UEM invoice often has no PO. The “receipt” is a live circuit, a spinning meter, or a mobile line on an HR roster. Processing that still pretends the PO is the third document will code a total and miss the dead ID. RadiusPoint’s run keeps the ID on the line before anyone touches the GL.

If a team says they “process and audit” as one verb, ask which queue holds the exceptions. If there is no hold queue, they are paying to clear the inbox. That is processing with the audit switched off.

The Six-Station Invoice Run

The Six-Station Invoice Run is RadiusPoint’s map of a TEM or utility invoice from inbox to GL, and generic AP OCR stops at parse. Station 1 receives the BAN. Station 2 captures every line. Station 3 tests inventory. Station 4 tests rate. Station 5 allocates. Station 6 pays the clean lines and holds the rest.

RadiusPoint stores the invoice image inside ExpenseLogic and retains vendor, BAN, service ID, period, and amount on the same record. An analyst does not re-key a header to make AP’s calendar look busy. The run is the product.

Station What happens Fail mode if skipped
1 Receive The BAN lands by EDI, portal, or PDF. One inbox per BAN. Late fee. Missing bill. A portal login nobody owns.
2 Capture Vendor, amount, service ID, and period on every line, before GL coding. A header total with no ID to test.
3 Inventory The service ID must be live this cycle. A disconnected circuit still prints as a charge.
4 Rate Billed MRC scored against the contracted rate on that same ID. Last year’s rate bills all year.
5 Allocate Cost center, location, and GL on a validated line, not a guessed total. A department pays for a site it does not have.
6 Pay or hold Clean lines pay. Exceptions stay in queue until an analyst closes them. Paying to clear the queue. The error repeats next cycle.

A pass is six stations populated. A parsed PDF with none of those stations after capture is not a pass. Utility Expense Management (UEM) runs the same six stations at meter level, not account level. Wireless runs them at phone number and Employee ID.

How much should a telecom or utility invoice cost to process?

A telecom or utility invoice should be judged on whether the six stations finished, not on whether AP beat $5.83. APQC’s median of $5.83, top quartile of $2.07, and bottom quartile of $10.00 measure generic supplier invoices across 1,485 organizations, as Perry D. Wiggins reported for CFO.com. Those quartiles are still the figures 2026 AP automation summaries repeat. They do not measure a BAN with 400 circuit lines.

RadiusPoint does not publish a dollar-per-invoice processing fee on this page. The published operating fact is two-day invoice processing, claimed on the company FAQ, run by named analysts on ExpenseLogic. That is the TEM version of cycle time: receipt to a coded file, with holds parked. It is not a promise that every carrier PDF becomes a $2.07 event.

Quartile APQC cost per invoice RadiusPoint TEM path
Top 25% $2.07 or less Two-day invoice processing claimed on the FAQ
Median $5.83 Line-item audit plus GL file, not header OCR
Bottom 25% $10.00 or more Carrier PDFs still keyed by AP

A carrier invoice that fails station 3 is not a cheap process problem. It is a billed service that may not exist. Wiggins also split industries: distribution and transportation sat at $1.14 at the median, consumer products at $4.58, public sector at $9.43. Telecom and utility invoices behave more like the complex end of that list, because the third document is inventory, not a packing slip.

Category AP cost is a useful ceiling for paper and PO invoices. It is a misleading target for a wireless BAN.

Why do carrier and utility invoices break generic AP matching?

Carrier and utility invoices break generic AP matching because the third document is live inventory, not a purchase order, on that ID. The unit price sits on a service ID that changes when people, sites, and circuits move. Two-way match can agree that the vendor and the total look familiar. Four hundred lines can still be wrong.

A MACD that closed in the field and never hit the invoice is the classic break. The processing run has to see last cycle’s disconnect before it codes this cycle’s MRC. A vacant meter is the UEM version: the site is closed, the tariff is not. Vacant utility cost recovery is what you do after processing keeps presenting the same account. A wireless line that outlived the employee is the mobility version. Processing that cannot see the HR roster will keep coding the MRC to a cost center that no longer has that person.

Taxes, surcharges, and credits sit on the same invoice as the MRC. Generic OCR is built to find a total. RadiusPoint’s capture station is built to keep those as separate lines so station 4 can score the rate and station 6 can hold a tax that does not belong.

Vendor format drift is not a side quest. Carriers change PDF layouts. Portals timeout. EDI feeds drop a BAN. Station 1 is a receipt discipline: one inbox per BAN, daily missing-bill reporting, and a named owner when the file does not land. Without that, AP discovers the invoice when the late fee does.

What two-day processing looks like on ExpenseLogic

Two-day invoice processing on ExpenseLogic is RadiusPoint’s published cycle from receipt to a coded file, with named analysts closing exceptions instead of AP keying headers. Day one is receive and capture. Day two is inventory, rate, allocate, and the pay-or-hold split. Clean lines move. Dirty lines stay visible.

RadiusPoint is ISO 9001 certified since 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. A capability statement and the about page carry the firm facts. Credentials tell you the operator is real. The six stations tell you the invoice is being used.

The published proof sits downstream of a processed file that failed a later test. A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one, then $850,000 in ongoing annual savings, a $1.3 million year-one impact. Inventory work recovered $174,000 in re-credits when services did not match the bill. One line of unneeded toll-free numbers ran $18,000 a year. Contract rate optimization recovered $120,000 a year. They are not a processing-fee menu. They are what happens when stations 3 and 4 are allowed to fail in public instead of disappearing into a paid total.

You keep budget approval. RadiusPoint keeps the queue. A letter of agency is what lets RadiusPoint pull the invoice or talk to the carrier when station 1 needs a portal and station 6 needs a dispute. Scope it. A read-only billing grant is not ordering rights.

Processing, allocation, and the accrual file

Invoice processing is unfinished if the validated line has no cost center, and it is dishonest if a late bill has no accrual. Station 5 applies location, department, and GL to a validated line that already passed inventory and rate.

A telecom accrual file is what finance books when the BAN did not land in time. Paying a guessed total in week four so the close looks clean is how last year’s error becomes this year’s budget.

Allocating telecom and utility costs across departments is the downstream job once the line is correct. Split-billing a circuit across cost centers is a processing rule, not a spreadsheet afterthought. Closed-location exception reports are a processing output: the site is in the real-estate feed as closed, the invoice is still in station 1. A multi-location client stopped $1,500 a month, $18,000 a year, on utilities at closed locations. It only appears after processing keeps the location on the line.

Daily missing-bill reporting belongs in station 1, not in a month-end panic. RadiusPoint’s TEM build includes that report. The data a TEM provider needs before day one is the BAN list, the inventory, the GL map, and the HR or site feed that stations 3 and 5 will use. If onboarding skips those, you have bought OCR. The TEM implementation timeline is the calendar for standing the six stations up. The station names do not change because a tool vendor sold you capture.

Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category observation, not a RadiusPoint guarantee. The operating fact on this page is narrower. If station 6 has no hold queue, you will pay the 15 to 30 percent right back out.

FAQ

Can OCR software replace a TEM invoice processor?

OCR can capture a header and many line fields. It cannot, by itself, prove a circuit is still live, score an MRC against a contracted rate table, or hold a tax line while an analyst files. RadiusPoint’s work starts where the parse would have succeeded and the inventory would still have failed. Buy capture if you need capture. Do not call capture a six-station run.

Who should own invoice processing when IT and facilities both buy services?

Finance should own the dollar decision and the GL. IT or facilities should confirm the service is still needed. A named operator should keep the BAN inbox and the hold queue. RadiusPoint will be that operator on an ExpenseLogic engagement. If three departments can buy and nobody can say which BAN is late, you do not have invoice processing. You have three inboxes.

Do we pay exceptions to hit the close, or hold them?

Hold them. Station 6 exists so the close can book an accrual on a late or disputed BAN instead of paying a guessed total. RadiusPoint’s two-day path is built to get clean lines into the file fast enough that the hold queue is a real queue, not a graveyard. Paying to clear exceptions teaches the vendor that the error posts.

How long should we keep telecom and utility invoices?

Keep the image, the line file, and the exception log for the same retention window your auditors already require for AP, commonly three to seven years in the U.S. ExpenseLogic stores the image against the service ID so a later dispute still has the line, not a box of paper. Retention is not processing. Processing is what makes the retained file worth opening.

Does invoice processing include wireless bills?

Yes. Wireless invoices run the same six stations at phone number and Employee ID. Managed mobility services is the service wrap around that run: staging, help desk, and offboard.

What to do before the next invoice cycle

Pick one carrier BAN and one utility account. Write the six stations down the left side of a page. Fill what last month’s file actually contains. If capture has a total and inventory has a blank, that is the operating gap. RadiusPoint will fill those stations for a managed ExpenseLogic engagement. Every cycle you pay without them is a cycle the $10.00 invoice can keep.

References

  1. Metric of the Month: Accounts Payable Cost | Perry D. Wiggins, CFO.com, APQC data from 1,485 organizations
  2. Telecom Expense Management Services | RadiusPoint
  3. Utility Expense Management | RadiusPoint
  4. Managed Mobility Services | RadiusPoint
  5. ExpenseLogic | RadiusPoint
  6. Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
  7. Invoice Auditing Services | RadiusPoint
  8. Invoice Audit vs Three-Way Match | RadiusPoint
  9. The MACD Process in Telecom Expense Management, Explained | RadiusPoint
  10. Vacant Cost Recovery: The Utility Bills Nobody Is Watching | RadiusPoint
  11. How to Audit a Utility Bill for Errors | RadiusPoint
  12. Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
  13. What a Telecom Accrual File Is, and How Finance Teams Build One | RadiusPoint
  14. Allocating Telecom and Utility Costs Across Departments | RadiusPoint
  15. The Data a TEM Provider Needs Before Day One | RadiusPoint
  16. How Long a Telecom Expense Management Rollout Actually Takes | RadiusPoint
  17. Capability Statement | RadiusPoint
  18. About RadiusPoint | RadiusPoint
  19. Sharon R. Watkins | RadiusPoint
  20. ExpenseLogic reviews | Capterra

Related articles

Disclaimer

This article is general information for finance, IT, procurement, and facilities teams processing telecom, utility, and wireless invoices. It is not legal, tax, or accounting advice. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results. Category-level ranges from APQC and from TEM industry research are hedged and are not RadiusPoint promises.

data center technician runs code

15 Effective Ways to Reduce IT Costs for Businesses

cost savings0

IT leaders and CIOs are under constant pressure to control expenses without stalling innovation. According to Gartner, global IT spending is projected to reach $5 trillion in 2024, driven by cloud adoption, AI integration, and security requirements. These rising costs necessitate that businesses consider long-term solutions beyond short-term cost reductions and implement sustainable cost-reduction strategies.

“Reducing IT costs and accelerating innovation are not mutually exclusive. When done right, cost discipline should enable innovation.” — Arvind Joshi, COO & CFO, Global Technology, JPMorgan Chase. This perspective highlights the dividends of smarter IT management—businesses save capital while positioning themselves for long-term scalability.

The following strategies offer actionable steps for reducing IT costs while maintaining performance and driving innovation.

Reassess Cloud Costs

Cloud services are often over-provisioned. Many businesses purchase more storage, computing power, or licenses than they use. According to Flexera’s 2024 State of the Cloud Report, 32% of cloud spending is wasted on underutilized resources.

A cost-reduction approach starts with monitoring workloads and rightsizing resources. Businesses should also implement spending thresholds, schedule automated shutdowns for idle services, and consolidate workloads across fewer providers. 

Optimizing cloud contracts ensures IT budgets reflect actual consumption rather than inflated projections.

Revisit the Hardware Stack

Legacy infrastructure creates hidden costs through higher maintenance fees, frequent downtime, and energy inefficiencies. Older servers require more power and cooling, driving operational expenses.

By upgrading to energy-efficient servers, adopting virtualization, or migrating workloads to the cloud, businesses cut capital expenditure and reduce total cost of ownership. 

Evaluating the hardware stack annually helps avoid paying for systems that no longer align with operational needs.

Recheck Project Portfolio

IT teams often juggle multiple projects, but not all deliver measurable returns. Projects with low adoption, unclear objectives, or outdated outcomes drain budgets and staff hours.

Portfolio rationalization means pausing, combining, or retiring projects that no longer align with business objectives. 

CIOs should prioritize high-value initiatives that contribute directly to growth, security, or customer experience. This reduces cost leakage while ensuring resources are directed toward innovation.

Move Toward Consumption-Based Contracts

Paying for fixed resources leads to inefficiencies. A consumption-based model, often called pay-as-you-go, allows businesses to pay only for the services they actively use. This approach applies to cloud storage, networking, and even software licensing.

Consumption-based contracts reduce the risk of over-committing and allow IT budgets to flex with real demand. Businesses that shift to this model improve cost predictability and align IT spend with revenue cycles.

Realign IT Support Models

Traditional support agreements charge a flat fee for comprehensive services, but many organizations only need partial coverage. A tiered or remote-first support model helps businesses match costs with actual needs.

Shared-service arrangements or managed service providers also reduce internal labor costs while ensuring expert coverage. Realigning support saves money without compromising uptime or reliability.

Optimize Sourcing Strategies

Vendor sourcing directly impacts IT budgets. Relying on a single vendor may limit negotiation power, while managing too many suppliers creates administrative overhead.

A balanced approach, through competitive bidding or hybrid sourcing, drives cost savings while maintaining service quality. Regular sourcing reviews ensure that vendor relationships remain aligned with pricing trends and technology requirements.

Align Sourcing With Business Objectives

Sourcing decisions should extend beyond price comparisons. Vendors tied to strategic outcomes deliver more value than those based on transactional contracts. Value-based sourcing includes service-level agreements tied to performance, efficiency, or customer satisfaction metrics.

This alignment eliminates unnecessary spending on misaligned services and promotes stronger accountability across vendor partnerships.

Audit All Existing Contracts

Many businesses continue paying for outdated or overlapping contracts because renewals are automated or unnoticed. Quarterly or biannual audits uncover these inefficiencies.

Auditing ensures that subscription software, cloud services, and telecom contracts reflect current business requirements. Terminating redundant agreements or consolidating providers often leads to substantial savings.

Conduct Application Rationalization

Maintaining redundant applications is one of the most common sources of IT waste. Licensing fees, integration costs, and staff training expenses multiply when multiple tools serve the same function.

Rationalizing applications, by consolidating into a single enterprise suite or reducing overlapping platforms, lowers costs and simplifies management. For example, replacing multiple collaboration tools with a single enterprise system reduces both licensing and support expenditures.

Embrace IT Automation

Automation removes repetitive tasks such as system patching, user provisioning, monitoring, and incident response. Beyond cost savings, automation improves accuracy and reduces downtime.

Automated IT processes allow staff to focus on higher-value initiatives like digital transformation or customer service enhancements. Over time, automation produces measurable reductions in labor and operational overhead.

Adopt Expense Management Software

Expense management software provides visibility into IT, telecom, and utility costs. Platforms like RadiusPoint’s expense management solution centralize expense tracking, generate detailed reports, and identify inefficiencies.

By implementing such solutions, businesses prevent billing errors, optimize vendor contracts, and streamline payment processes. Data-driven insights transform expense management into a proactive cost-control function.

Reduce, Don’t Freeze IT Spending

Freezing IT budgets is a short-term reaction that stifles innovation. Instead, businesses should reduce expenses strategically by cutting non-essential services while continuing to fund critical areas such as cybersecurity, cloud modernization, and automation.

This approach safeguards innovation pipelines while still achieving meaningful cost reductions.

Improve IT Cash Flow Strategies

Cash flow management improves financial flexibility. Options include leasing hardware instead of purchasing outright, adopting subscription-based models, or extending payment schedules.

Shifting from large capital expenses (CAPEX) to predictable operating expenses (OPEX) ensures budgets remain balanced while meeting technology requirements.

Renegotiate Vendor Contracts

Vendors are often open to renegotiation when presented with alternatives. Businesses reduce costs by consolidating purchases, extending contract terms, or negotiating discounts.

Regular renegotiations not only cut immediate expenses but also establish stronger vendor accountability. Preparing benchmarks before discussions helps CIOs secure more favorable terms.

Implement IT Asset Lifecycle Management

Unmanaged IT assets lead to unnecessary purchases and lost efficiency. Lifecycle management ensures assets are monitored from procurement to retirement.

Strategies include redeploying underutilized devices internally, extending device lifespans with proper maintenance, and scheduling structured decommissioning. This approach maximizes asset value while avoiding redundant expenditures.

Strengthen Governance and Cost Transparency

Governance frameworks help create accountability for IT spending. Regular reporting at the department or project level builds transparency and ensures that budgets align with corporate strategy.

Cost transparency fosters informed decision-making, enabling CIOs to make adjustments before costs spiral out of control.

Final Thoughts

Reducing IT costs is not about cutting corners—it is about creating efficiency, accountability, and resilience. CIOs and business leaders who reassess contracts, rationalize applications, adopt automation, and leverage expense management software position their organizations for both savings and scalability. 

As Arvind Joshi of JPMorgan Chase noted, cost discipline and innovation go hand in hand. By treating cost optimization as a continuous process rather than a one-time initiative, businesses strengthen their financial health while keeping technology aligned with long-term growth.

business people blue background

10 Vendor Management Best Practices, From Planning to Exit

Managed Mobility Services1

Vendor management best practices are ten steps for planning, choosing, contracting with, monitoring and exiting vendors, so each invoice is checked against its contract. Those steps fit the five life-cycle stages in US banking regulators’ 2023 third-party guidance, from planning through termination.

They matter most for recurring-service vendors (telecom and wireless carriers, utility and waste vendors), where contracts, rates and invoices drift apart location by location. RadiusPoint manages that spend on ExpenseLogic, its single cloud platform.

Key Takeaways

  • US banking regulators’ 2023 guidance names five vendor life-cycle stages, from planning through termination, and says higher-risk vendors warrant more planning and more frequent monitoring.
  • Each practice should leave a record: a signed contract with rates and an expiration date, an invoice audited against it, a ticket for each change and a disconnect confirmation.
  • Four published RadiusPoint cases began with locations buying on their own and ended with savings of 28% (waste), 13.6% (cleaning), 11% (trash) and $100K+ in year one (telecom).

Short version: sort vendors by risk, put every rate and exit term in a signed contract, audit each invoice against that contract, and plan the exit before the renewal date arrives.

The Vendor Management Lifecycle: Five Stages and the Record Each One Leaves

Five stages make up the vendor management lifecycle (planning, due diligence and selection, contract negotiation, ongoing monitoring, termination), and each one should leave a record. The stage names come from US banking regulators’ guidance of June 6, 2023, which calls the life cycle continuous.

The guidance is written for banks, but any buyer can borrow the stages. It says third parties that support higher-risk activities, including critical activities, “typically warrant a greater degree of planning and consideration.” As a vendor management workflow, the stages look like this:

Stage (2023 interagency guidance) Practice a buyer runs Record that proves it ExpenseLogic capability
Planning Segment by profit impact and supply risk; keep one vendor inventory Vendor inventory by site, with each vendor’s segment Reporting and Analytics (audit analysis, budget reporting); cost allocation by location
Due diligence and third-party selection Define the service each site needs; scale checks to the segment Service level by location; the comparison behind the choice Utility analysis reporting with site and date comparisons; utility procurement in deregulated markets
Contract negotiation Put rates, fees, term and exit terms in writing Signed contract with rates and an expiration date Vendor contract management with expiration dates and rates tied to service IDs; Contract Management module
Ongoing monitoring Audit invoices, ticket changes, score performance Invoices audited line by line against the contract; a ticket per change Line-item audit against contracted rates and inventory; meter-level utility audit; MACD (move, add, change, disconnect) ticketing with client-defined approval workflows; daily missing-bill reporting
Termination Plan transition, fees and data handling; confirm the disconnect Disconnect confirmation; final invoice with no later charges Contract obligation alerts covering termination fees and dates; closed-location billing exception reports; deposit tracking

What Vendor Management Means When a Vendor Bills Every Month

Vendor management is how a company chooses, contracts with, pays, monitors and exits its vendors, so each one delivers what its contract promises. For vendors that bill every month (electric, gas, water and waste utilities, telecom and wireless carriers), the test is concrete: each invoice should match the rate and the service on record.

A one-time purchase ends at delivery. A utility or carrier account keeps billing every cycle until someone closes it, and each new site adds its own accounts and meters. Regulated utilities often bill from a published tariff, or rate schedule, instead of a negotiated contract. The National Association of Regulatory Utility Commissioners says its member state commissions have an obligation to ensure utility services are provided at rates and conditions that are “fair, reasonable, and nondiscriminatory.” For each recurring vendor, the record that proves performance depends on the vendor type:

Vendor type Rate on record Service on record What a line-item audit checks
Electric utility Tariff rate class for delivery; supply contract rate in a deregulated market Meter number, site and read dates Rate class and supply rate match the record; usage fits the meter’s history; the site is still open
Natural gas utility Tariff rate class; supply contract rate in a deregulated market Meter number, site and read dates Rate and supply charges match the record; usage fits the meter’s history and the season
Water and sewer Rate schedule from the city, water district or state commission Meter number and site Rate matches the schedule; consumption fits the meter’s history; no charges for a closed site
Waste hauler Contract rate per container and pickup, plus any agreed extra charges Container size and pickup schedule by location Pickups and container sizes match the contract; overage and extra charges are ones the contract allows
Telecom carrier (wireline and data circuits) Contract rate tied to each service ID Service ID or circuit, by location, in the inventory Each service bills at the contracted rate and is still in the inventory and in use
Wireless carrier Contracted rate plan per line Phone number tied to an employee ID Each line bills at its plan rate and belongs to a current employee

In utility vendor management, someone also has to own each bill from arrival to ledger. That ownership covers invoice intake, a line-item audit against the rate and service on record, payment, and the data finance uses afterward: general ledger (GL) coding, accruals, allocation and exceptions for closed sites. All of it runs per account and meter, so it depends on a current utility meter inventory.

RadiusPoint can own that bill lifecycle for a client’s utility and telecom vendors in ExpenseLogic. That covers utility and telecom invoice intake, line-item audit against contracted rates and inventory, accrual and GL interface files, cost allocation in the client’s chart of accounts and closed-location billing exception reports. RadiusPoint can pay vendor invoices for clients once the client funds the account. In one published RadiusPoint case, a client kept paying electricity, gas and water bills for a location that had closed, at more than $1,500 a month, or over $18,000 a year.

What Happens When Every Location Hires Its Own Vendors?

When each location hires its own vendors, there’s no corporate contract, rates vary by site, and invoices are paid without a check against agreed terms. Four published RadiusPoint cases start from that pattern and end with new or consolidated contracts. Their percentage savings run from 11% to 28%.

Published RadiusPoint case Starting point What changed Result
Worldwide elevator company, waste Over 40 locations with their own waste hauler contracts, staggered expirations and early termination fees Rates validated against invoices; services compared across sites; overage charges identified; request for proposal (RFP) report, negotiations and transition Monthly waste expenses down 28%
Healthcare organization, 300+ locations in the United States and Canada, cleaning Each location hired its own provider; contracts at only two; 363 vendors in accounts payable (AP) software; 1,400+ invoices a month Invoices analyzed to set a standard service level by location; one vendor contracted for all locations Direct savings of 13.6%; 1,400+ invoices consolidated into one, paid monthly instead of weekly
Global glass manufacturer, 200+ retail locations, telecom Locations ordered their own services with no corporate contracts Contracts consolidated; ordering moved to the MACD portal $100K+ saved in year one; return on investment (ROI) over 200%
National eyeglass and contact lens manufacturer and retailer, 170 retail locations and 3 labs, trash No ordering standard; some contracts more than 20 years old, rolled over and increased by the vendor with no checks Each location’s contract requested; evergreen contracts replaced through negotiation with current and new vendors Savings of 11%

What Are the 10 Vendor Management Best Practices?

Ten practices cover the full life cycle: segment, inventory, define service, vet, contract, audit invoices, ticket changes, score performance, assign ownership and plan the exit. Practices 1 and 2 cover planning, 3 and 4 selection, 5 contracting, 6 to 9 monitoring and 10 termination.

  1. Segment what you buy by profit impact and supply risk. A vendor management strategy starts with Peter Kraljic’s 1983 Harvard Business Review categories: strategic (high profit impact, high supply risk), bottleneck (low impact, high risk), leverage (high impact, low risk) and noncritical (low impact, low risk). Watch the first two most closely.
  2. Keep one inventory of every vendor, contract and location. The 2023 guidance links a complete inventory, plus periodic risk assessments, to seeing whether a vendor’s risk has changed. In a vendor management program, the inventory shows which sites each vendor serves and whether a contract exists.
  3. Define the service each location needs before you source it. In the cleaning case, RadiusPoint analyzed each provider’s invoices to set a standard service level by location before one vendor was contracted for all of them.
  4. Scale due diligence to the segment. The guidance says not all relationships require the same oversight. Check a strategic vendor’s finances, insurance and references more deeply than a noncritical vendor’s.
  5. Put rates, fees, term and exit terms in a signed contract. The guidance says contracts that clearly describe all costs and compensation “help reduce misunderstandings and disputes over billing.” For telecom and utility spend, vendor contract management ties each rate to a service ID or meter, with the expiration date on record.

Which Vendor Management Practices Apply After the Contract Is Signed?

Five practices apply once the contract is signed: audit each invoice, ticket each change, score performance, name an owner and plan the exit. Together they leave a record: an invoice audited against the contracted rate and inventory, a ticket with an approval step, results shared with each vendor, and a disconnect confirmed in writing.

  1. Audit every invoice against the contract. An invoice audit checks each line against the contracted rate and the inventory. In the elevator case, the audit validated contract rates against the current invoice and identified overage charges beyond the normal pick-up charges.
  2. Route every move, add, change and disconnect through a ticket. A MACD ticket with an approval step records who asked for each change. Once the glass manufacturer’s ordering moved to a MACD portal, future orders had to go through it.
  3. Score performance against the contract on a set schedule. Review strategic and bottleneck vendors against their contracted service levels and rates, and share the results with each vendor.
  4. Name one owner per vendor and report up. The guidance gives the board ultimate responsibility for oversight and calls for sufficient staffing to monitor third parties. Vendor governance sets who decides what, and on what schedule.
  5. Plan the exit before you need it. Know each contract’s notice dates, termination fees and transition plan before renewal, and confirm every disconnect in writing.

Vendor Performance Management Best Practices Start With the Contract

Vendor performance management works when every measure traces to a contract term, so a missed service level or wrong rate becomes a documented exception. The 2023 guidance says a service-level agreement can specify measures used to “monitor performance, penalize poor performance, or reward outstanding performance.”

For recurring-service vendors, billing accuracy belongs on a vendor scorecard next to uptime and response time. In the landscaping case, a company with 500+ locations had AP staff handling 1,300+ utility bills a month before RadiusPoint took over invoice processing and payment. Audits there run by meter number and type of service, and each quarter RadiusPoint prepares a report using key performance indicators (KPIs) to track spending levels and ROI.

How Do You End a Vendor Relationship Without Paying for It Twice?

End a vendor relationship by settling notice dates, termination fees, transition and data handling before giving notice, then confirm the final disconnect and final invoice. The 2023 guidance lists options for transition, “costs and fees associated with termination,” and data retention and destruction among the factors to weigh.

In the elevator case, staggered expiration dates and early termination fees ruled out one corporate contract in the first twelve months. Telecom agreements add notice windows that can renew a term if they pass unnoticed. After the exit, keep checking: a closed location can keep receiving bills for services nobody uses.

How RadiusPoint Applies These Practices to Telecom, Wireless and Utility Vendors

RadiusPoint applies these vendor management practices to telecom, wireless, utility and waste vendors through ExpenseLogic, a single cloud platform, with RadiusPoint staff working the invoices. Its published cases also cover facility services such as cleaning. It isn’t a general third-party risk, cybersecurity rating or financial-health rating service.

In ExpenseLogic, vendor contract management ties expiration dates and rates to service IDs, with contract obligation alerts covering termination fees and dates. Line-item audit covers wireline, wireless and data circuits, and RadiusPoint’s utility expense management audits electricity, gas, water, sewer and waste at the meter level.

RadiusPoint staff chase the carriers, file the disputes and close the tickets, and RadiusPoint can pay vendor invoices for clients once the client funds the account. Founded in 1992, RadiusPoint is a women-owned business. ExpenseLogic holds a 4.8 rating on Capterra from 31 reviews, with reviews through December 2025, and Amalgam Insights named RadiusPoint a Distinguished Vendor on its 2024 Telecom Expense Management (TEM) Vendor SmartList.

Every month a location keeps a vendor with no contract, the same unchecked charges repeat. Request a free demonstration of the ExpenseLogic Contract Management and Reporting and Analytics modules.

Frequently Asked Questions

Do the 2023 interagency third-party guidelines apply to companies that aren’t banks?

No, the 2023 guidance is directed to banking organizations supervised by the three federal agencies that issued it, and it doesn’t bind other companies. Its five-stage life cycle still works as a reference for any buyer, since a waste hauler or wireless carrier goes through the same stages.

What should a vendor management policy include?

A vendor management policy should say who may sign with a vendor, how vendors are segmented by risk, what due diligence each segment needs, which terms every contract carries, and how performance reviews and exits work. The 2023 guidance’s 17 contract factors, from nature and scope of arrangement to default and termination, make a practical checklist.

Is telecom vendor management different from managing other vendors?

Telecom vendor management follows the same life cycle, but the records are finer-grained: rates attach to circuits, lines and service IDs, and each location can carry its own account. That makes line-item audit against contracted rates and inventory the core monitoring practice.

How is vendor management different from vendor governance?

Vendor management is the day-to-day work of contracting with, monitoring and paying vendors, while vendor governance sets the decision rights, approval limits and review cadence that work follows. The 2023 guidance draws a similar line for banks: the board oversees, and management develops and runs the policies and practices.

How is vendor management different from procurement?

Procurement focuses on buying, while vendor management covers the vendor’s whole life cycle, from selection and contract terms through monitoring, invoice checks, changes and exit. Procurement finds suppliers, runs bids and negotiates the deal. For a utility or carrier account, the buying decision may come up only when a contract ends, while vendor management work repeats every billing cycle.

Is a vendor management system the right tool for utility and telecom bills?

Usually not, because a vendor management system (VMS) most often means software for buying and managing staffing services and contract labor. Some procurement suites use the name for supplier onboarding and records. Utility and telecom bills need a system that holds each account, meter or service ID with its contract rate or tariff, then audits every invoice line against it.

References

  1. Board of Governors of the Federal Reserve System, Federal Deposit Insurance Corporation and Office of the Comptroller of the Currency, “Interagency Guidance on Third-Party Relationships: Risk Management,” Federal Register document 2023-12340, 88 FR 37920, June 9, 2023 (final as of June 6, 2023). federalregister.gov
  2. Board of Governors of the Federal Reserve System, “Interagency Guidance on Third-Party Relationships,” June 6, 2023. federalreserve.gov
  3. Peter Kraljic, “Purchasing Must Become Supply Management,” Harvard Business Review, September 1983. hbr.org
  4. RadiusPoint, “Waste Services Case Study: 28% Reduction in Trash Spend,” January 19, 2024.
  5. RadiusPoint, “Vendor Management: 13.6% Savings on Cleaning Services,” October 9, 2022.
  6. RadiusPoint, “Glass Manufacturer Saves $100K On Telecom Expenses,” May 22, 2023.
  7. RadiusPoint, “Finding Hidden Money in your Trash,” August 25, 2019.
  8. RadiusPoint, “Vendor Billing Audits for a Nationwide Landscaping Company,” November 16, 2022.
  9. RadiusPoint, “About RadiusPoint,” accessed October 2026.
  10. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews, accessed October 2026. capterra.com
  11. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  12. National Association of Regulatory Utility Commissioners, “History & Background,” accessed November 2026. naruc.org
  13. RadiusPoint, “Utilities Mismanagement Costs $18K in Unnecessary Expenses,” October 10, 2022.

This article is general information for finance, procurement, IT and facilities buyers, not legal, regulatory or contract advice. RadiusPoint outcomes cited here come from specific published client engagements on the case pages listed in References, and results vary by organization.

medical banner with doctor working laptop

What Is Document Management in Healthcare? Patient Records vs. Vendor Contracts and Invoices

EEM0

Every health system keeps two document trails. One follows the patient: the chart, lab results, imaging and billing records. The other follows the buildings: the telecom, utility and IT contracts, invoices and dispute records behind every clinic and nursing station.

Document management in healthcare is the set of systems and rules a provider uses to capture, index, store, secure and retrieve patient records and the administrative documents around them, alongside an electronic health record (EHR) and under the HIPAA Privacy and Security Rules. That’s the first trail.

RadiusPoint doesn’t provide clinical document management, patient-records storage, EHR integration or HIPAA compliance software. RadiusPoint works on the second trail: its ExpenseLogic platform holds a health system’s telecom, utility and IT invoices, contracts and dispute records, with permissions-based image recall and line-item audit.

Key Takeaways

  • Document management in healthcare covers patient records and the documents around them, kept beside an EHR under HIPAA.
  • HIPAA’s Privacy Rule sets no record retention period. State laws generally do, and Medicare requires hospitals to keep medical records at least 5 years.
  • Large breaches reported to HHS affected 289,162,330 individuals in 2024, by HIPAA Journal’s count, and IBM’s 2026 report puts the average healthcare breach at $6.64 million.
  • Telecom, utility and IT contracts, invoices, dispute records and service inventories form a separate expense trail, and that’s where RadiusPoint works.
  • In one RadiusPoint case, an assisted living and nursing home organization cut annual telecom spend 26%, or $475,000, after an inventory found more than 700 dormant business lines.

Short version: For patient records, choose a clinical document management system built around HIPAA and your EHR; for telecom, utility and IT invoices and contracts across many sites, you need expense document management, which is RadiusPoint’s work.

What Does Document Management in Healthcare Cover?

Document management in healthcare covers the patient records, billing records and administrative documents a provider must capture, protect and produce on request, alongside its EHR. HIPAA’s definition of a designated record set includes a provider’s medical records and billing records about individuals, so both sit inside the clinical scope. Telecom and utility contracts don’t.

Question Clinical and administrative records Telecom, utility and IT expense documents
What’s in it Medical history, diagnoses, medications, allergies, imaging, lab results and patient billing records Vendor contracts, monthly invoices, dispute and credit records, and service inventories by location
System of record The EHR, used in certified form by 99.4% of non-federal acute care hospitals in 2024 An expense management platform, or files kept site by site
Rules that shape it HIPAA Privacy, Security and Breach Notification Rules; Medicare conditions of participation for hospitals Each vendor contract’s terms and your own financial controls
Retention set by State law and payer rules; at least 5 years for hospital medical records under Medicare Your records policy and each contract’s terms
Where RadiusPoint fits Not a RadiusPoint service ExpenseLogic Document Management, Contract Management and Expense Audit

In this context, DMS means document management system, not the device management systems that track phones, tablets and other hospital hardware.

How Is a Healthcare Document Management System Different From an EHR?

An EHR is the patient’s digital chart, while a healthcare document management system captures, indexes and controls access to the documents surrounding that chart. The federal health IT office, ASTP/ONC, defines an EHR as “a digital version of a patient’s paper chart.” A document system handles files that arrive as documents rather than as structured chart data.

Nearly every hospital runs an EHR. ASTP’s Data Brief No. 83 (June 2026) puts certified EHR use among non-federal acute care hospitals at 99.4% in 2024, so the open question is how the documents around the EHR get captured, indexed and found.

The American Health Information Management Association (AHIMA) calls health information management “the practice of acquiring, analyzing, and protecting digital and traditional medical information.” The load reaches clinicians, too. In a 2016 Annals of Internal Medicine time-and-motion study of 57 physicians, Sinsky and colleagues found that 49.2% of the office day went to EHR and desk work and 27.0% to direct clinical face time.

Which Federal Rules Shape Clinical Document Management?

HIPAA’s Privacy, Security and Breach Notification Rules shape clinical document management: who sees records, how electronic records are protected and what follows a breach. Retention is the gap. HHS states that the Privacy Rule “does not include medical record retention requirements” and that state laws generally govern how long medical records are kept.

The Security Rule (45 CFR Part 164, Subpart C) requires covered entities and their business associates to protect the confidentiality, integrity and availability of electronic protected health information (ePHI). Its technical safeguards include access control, audit controls, authentication and transmission security, and the documentation it requires must be kept until six years after it was created or last in effect, whichever is later.

The Privacy Rule requires safeguards for medical records for as long as they’re kept, through disposal (45 CFR 164.530(c)). Patients can request their designated record set, which includes a provider’s medical and billing records, and the provider must act within 30 days (45 CFR 164.524). Medicare’s conditions of participation require hospitals to keep medical records for “at least 5 years” (42 CFR 482.24). Beyond that floor, state law sets the period, so a multi-state system can face a different schedule in each state.

Large Healthcare Breaches Exposed Data on More Than 289 Million People in 2024

Large healthcare data breaches reported to HHS exposed or impermissibly disclosed the health information of 289,162,330 individuals in 2024, according to HIPAA Journal’s analysis. That count covers 742 breaches of 500 or more records. In 2025, the count was 710 breaches affecting at least 61,556,256 individuals.

Covered entities must report any breach affecting 500 or more individuals to the HHS Secretary “without unreasonable delay and in no case later than 60 days following a breach.” IBM’s Cost of a Data Breach Report 2026 puts the average healthcare breach at $6.64 million, down from $7.42 million in 2025, and healthcare has had the highest average breach cost of any industry for 13 consecutive years.

Patient records belong in systems built around those safeguards. RadiusPoint isn’t a clinical document management vendor.

Which Expense and Contract Documents Does a Multi-Site Health System Need to Track?

A multi-site health system needs to track telecom, utility and IT contracts, monthly invoices, dispute and credit records, and service inventories for every location. These aren’t patient records, but they decide what each site pays for phone lines, data circuits, electricity and water. When each facility files its own, billing errors and renewal dates drop out of view.

RadiusPoint’s case pages show how that happens. At a healthcare organization with 275 locations, each location approved its own telecom invoices and sent them to corporate for payment, causing processing lag and past-due fees; the AP and ordering automation case reports a 448% ROI in the first six months of service. At an assisted living and nursing home organization, some vendors billed only a total, with no service details or phone numbers.

These documents are the paper side of healthcare telecom expense management:

Document Why it needs central tracking Where it lives in ExpenseLogic
Telecom, utility and IT vendor contracts Rates, end dates and termination fees get lost when each site keeps its own copy Contract Management (image storage, terms retention); vendor contract management with expiration dates and rates tied to service IDs; contract obligation alerts
Monthly invoices from every vendor They’re the evidence for checking each charge against contracted rates Document Management (permissions-based image recall) and Expense Audit (line-item detail, contract compliance)
Dispute and credit records They show which errors were raised and which credits posted Expense Audit (dispute tracking)
Service inventories by location They confirm which lines, circuits and meters are still active Line-item audit across wireline, wireless and data circuits; meter-level utility audit
Records for closed or consolidated sites A closed site can keep billing until someone checks Closed-location billing exception reports
Spend and audit reports Finance and facilities need one view of cost by site and vendor Reporting and Analytics (audit analysis, budget reporting, export to Excel, CSV and PDF)

ExpenseLogic Keeps Healthcare Invoices and Contracts Behind Permissions

ExpenseLogic stores a health system’s telecom, utility and IT invoice and contract images in one platform, with recall controlled by user permissions. For healthcare, that pairs permission-based access with detailed auditing of every invoice line. ExpenseLogic isn’t a clinical records system; its listed integrations are ERP systems, accounting-system interface files, HR employee-list feeds and real estate system feeds.

Healthcare adds its own pressure: services that have to stay up around the clock, and wireless devices spread across clinical floors. In RadiusPoint’s 26% healthcare case study, each location must keep two copper lines for direct fire notification, and the organization now uses the ExpenseLogic platform for invoice images, line and circuit inventory and monthly costs by location.

Closed Sites and Silent Renewals Are Where Scattered Records Cost Money

Scattered expense records cost money when a site closes or a contract renews unnoticed, because nobody connects the bill to the change. One RadiusPoint multi-location client paid $1,500 a month, $18,000 a year, for utilities at closed locations. A health system that closes a clinic or consolidates a wing carries the same exposure.

ExpenseLogic’s closed-location billing exception reports flag sites that keep billing after they close, the same gap behind vacant utility cost recovery. Inventory checks pay back too: in one RadiusPoint engagement, reconciling a telecom inventory against the carrier’s records recovered $174,000 in re-credits. For contracts, vendor contract management in ExpenseLogic stores expiration dates and rates against service IDs, and contract obligation alerts cover termination fees and dates.

Where RadiusPoint Fits in Healthcare Document Management

RadiusPoint fits the expense side of document management in healthcare: telecom, utility and IT invoices, contracts, dispute records and service inventories, not patient records. For clinical records, a provider needs a system built around HIPAA and its EHR. ExpenseLogic holds the expense documents, and RadiusPoint’s team audits invoices and files carrier disputes.

RadiusPoint was founded in 1992. Amalgam Insights named it a Distinguished Vendor in its 2024 Vendor SmartList for Telecom Expense Management, and ExpenseLogic holds a 4.8 rating from 31 reviews on Capterra. It’s also a women-owned business. RadiusPoint can pay vendor invoices for clients once the client funds the account.

A closed site billing $1,500 a month costs $18,000 a year until someone catches it. Request a free demonstration of ExpenseLogic for your health system’s expense documents.

Frequently Asked Questions

Does HIPAA require a document management system?

No. HIPAA’s rules require safeguards rather than a type of software. The Security Rule sets safeguards for electronic protected health information, and the Privacy Rule requires safeguards for medical records for as long as they’re kept, including through disposal. A document management system is one way to meet those duties for scanned and document-based records.

Can ExpenseLogic hold patient records?

No. ExpenseLogic is an expense platform for telecom, utility and IT invoices, contracts and related records, and it isn’t a clinical records system. Its listed integrations are ERP systems, accounting-system interface files, HR employee-list feeds and real estate system feeds. Patient documents belong in a clinical records system.

Do telecom contracts fall under HIPAA’s designated record set?

They don’t fit its definition. Under 45 CFR 164.501, a designated record set is a group of records that include protected health information, such as a provider’s medical and billing records about individuals. A telecom or utility contract covers services, rates and terms for a site, not a patient, so your own records policy governs it.

Does the same approach work for utility bills?

Yes. Utility Expense Management (UEM) covers electricity, gas, water, sewer and waste, and ExpenseLogic audits utility invoices at meter level on the same platform as telecom and IT. For a health system, closed-location billing exception reports flag clinics and offices that keep billing after they close.

References

  1. U.S. Department of Health and Human Services, “Summary of the HIPAA Security Rule,” content last reviewed August 7, 2026. hhs.gov
  2. U.S. Department of Health and Human Services, “Does the HIPAA Privacy Rule require covered entities to keep patients’ medical records for any period of time?” HIPAA FAQ 580, accessed October 2026. hhs.gov
  3. U.S. Department of Health and Human Services, “Breach Notification Rule,” accessed October 2026. hhs.gov
  4. 45 CFR 164.501, Definitions (“designated record set”), Cornell Law School Legal Information Institute, accessed October 2026. law.cornell.edu
  5. 45 CFR 164.524, Access of individuals to protected health information, Cornell Law School Legal Information Institute, accessed October 2026. law.cornell.edu
  6. 42 CFR 482.24, Condition of participation: Medical record services, Cornell Law School Legal Information Institute, accessed October 2026. law.cornell.edu
  7. ASTP/ONC, “What Are Electronic Health Records (EHRs)?” HealthIT.gov, December 10, 2025. healthit.gov
  8. ASTP/ONC, “Non-Federal Acute Care Hospital Electronic Health Record Adoption, 2008 to 2024,” Data Brief No. 83, June 2026. healthit.gov
  9. American Health Information Management Association (AHIMA), “Health Information 101,” accessed October 2026. ahima.org
  10. Sinsky C, Colligan L, Li L, et al., “Allocation of Physician Time in Ambulatory Practice: A Time and Motion Study in 4 Specialties,” Annals of Internal Medicine 165(11), 2016. doi.org
  11. Steve Alder, “2025 Healthcare Data Breach Report,” HIPAA Journal, February 13, 2026. hipaajournal.com
  12. IBM, “Cost of a Data Breach Report 2026,” accessed October 2026. ibm.com
  13. Becker’s Hospital Review, “Healthcare data breaches cost $6.64M on average: Report,” July 31, 2026 (healthcare figures from IBM’s Cost of a Data Breach Report 2026). beckershospitalreview.com
  14. RadiusPoint, “Healthcare Case Study: Telecom Expenses Down by 26% in Healthcare,” December 28, 2023.
  15. RadiusPoint, “AP/Ordering Process Automation Nets 448% ROI,” August 3, 2019.
  16. RadiusPoint, “Streamlining Invoice Processing for a Healthcare Client,” October 10, 2022.
  17. RadiusPoint, “ExpenseLogic,” platform modules page, accessed October 2026.
  18. RadiusPoint, “Vacant Cost Recovery: The Utility Bills Nobody Is Watching,” accessed October 2026.
  19. RadiusPoint, “How to Build a Telecom Inventory of Record From Carrier CSRs,” accessed October 2026.
  20. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  21. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews, accessed October 2026. capterra.com
  22. RadiusPoint, “About RadiusPoint,” accessed October 2026.

This page is general information about document management in healthcare and isn’t compliance, legal or regulatory guidance. RadiusPoint doesn’t provide clinical document management, EHR integration or patient records services. Client results describe specific RadiusPoint engagements on the case pages listed in References and aren’t a guarantee of results for your organization.

close up man s hand using cellphone

Why is Mobile Device Management Important?

Managed Mobility Services0

By Sharon Watkins, Founder and CEO, RadiusPoint · 12 min read

Mobile device management is important because it is the control plane that enrolls, encrypts, locks, and remotely wipes the handset. It does not pay the carrier. A wiped device that still bills is an MDM success and a finance failure.

Mobile device management (MDM) is the software and policy layer that configures enterprise phones and tablets, enforces encryption and authentication, and runs remote actions when a device is lost. NIST SP 800-124 Rev. 2, published May 2023, treats MDM as part of Enterprise Mobility Management (EMM). This page is why that control plane matters for a RadiusPoint account, and why it still needs a bill loop on ExpenseLogic.

Verizon’s 2026 Data Breach Investigations Report, the 19th edition covering more than 22,000 confirmed breaches, found the median click rate on mobile-centric phishing simulations (voice and text) is 40 percent higher than email. Human element was present in 62 percent of breaches. MDM policy without a bill loop still pays for the device after the wipe. RadiusPoint’s job since 1992 is the invoice that follows.

Key Takeaways

  • MDM is the control plane: enroll, encrypt, lock, remote wipe, and app allowlist. It does not prove the line is still billed.
  • Verizon’s 2026 DBIR (19th edition, more than 22,000 confirmed breaches) found mobile-centric phishing simulations click 40 percent higher than email.
  • NIST SP 800-124 Rev. 2 (May 2023) covers deployment, use, and disposal. RadiusPoint’s bill loop starts at the HR roster and ends at stop-bill.
  • A wiped device that still bills is an MDM success and a finance failure. ExpenseLogic joins serial number, Employee ID, and the wireless invoice.
  • RadiusPoint does not replace the MDM console. Named analysts run the invoice allocated to the phone number after the console has done its job.

The Short Version

MDM is the lock. MMS is the bill, the help desk, and the Employee ID join. If your wipe policy has no stop-bill, you have secured a handset that finance is still paying for.

In this article

Mobile device management is the control plane, not the carrier bill

Mobile device management is the control plane that enrolls the handset, pushes policy, encrypts data, and runs lock or wipe. MDM / EMM does enroll, encrypt, remote wipe, lock, and app allowlist. MDM / EMM does not prove the line is still billed, match Employee ID to the carrier BAN, or kill a zero-use MRC.

RadiusPoint’s managed mobility services sit on the bill side: serial number plus Employee ID, line contract audit, invoice allocated to the phone number. Together, a wiped device that still bills is an MDM success and a finance failure.

Why is MDM important if it does not pay the invoice?

MDM is important because the handset is the phishing surface, the data store, and the remote-work endpoint, even when finance owns the BAN. Security buys MDM for that surface. Finance still needs a bill loop after the wipe. Those are two tickets.

Verizon’s 2026 DBIR, summarized in the executive brief and reported by SecurityWeek, put human element in 62 percent of breaches and social engineering in 16 percent. Median click rates on mobile-centric simulations ran 40 percent higher than email.

A device that is not enrolled cannot be wiped. A device that is enrolled and wiped still needs a stop-bill. MDM answers the first sentence. RadiusPoint answers the second. Security officers get the console. Finance gets the invoice. Both are true on the same Tuesday.

Telecom lifecycle management owns the asset from acquisition through deactivation. MDM is the security slice of that life. The bill loop is the expense slice. Skipping either slice leaves a live risk: data on an unmanaged phone, or MRC on a managed one.

How do MDM, EMM, and Unified Endpoint Management differ from the bill?

MDM, enterprise mobility management, and Unified Endpoint Management differ from the wireless bill because none of those scopes pays the carrier. MDM concentrates on the handset. EMM adds apps and identity. Unified Endpoint Management, not Utility Expense Management, consolidates phones with desktops.

NIST SP 800-124 Rev. 2 treats EMM as the suite, with MDM as one piece inside it, sometimes referred to as UEM. RadiusPoint does not sell that suite. ExpenseLogic does serial number plus Employee ID, line contract audit, and the wireless invoice allocated to the phone number. Pick MDM, EMM, or UEM for the lock. Pick a named operator for the BAN.

Aspect MDM / EMM / UEM RadiusPoint on ExpenseLogic
Scope Device, app, or all endpoints Line, invoice, Employee ID
Actions Enroll, encrypt, wipe, lock Audit the MRC, file the dispute, stop the bill
Source of truth Console inventory Carrier BAN plus HR roster
Fail mode Unmanaged device Wiped device still billing

A console that reports 2,000 enrolled devices and a BAN that bills 2,400 lines is not a UEM problem. It is a join problem.

NIST’s device life cycle still needs a stop-bill

NIST’s mobile-device life cycle still needs a stop-bill because dispose or reuse does not yet talk to the carrier BAN. Deployment, use, and disposal are the security stages NIST names. Stop-bill is a finance step on that same device this cycle.

NIST SP 800-124 Rev. 2, final on 17 May 2023, names deployment, use, and disposal. RadiusPoint’s bill loop runs HR roster, serial plus Employee ID, line-item invoice, zero-use flags, and stop-bill.

The NIST announcement is explicit: recommendations cover deployment, use, and disposal. Disposal is a security event. Stop-bill is a finance event. They can happen weeks apart if nobody joins them.

The MACD process is the ticket that should fire when NIST’s last stage fires. Zero-use mobile lines is the hunt when it did not.

What happens when a wiped device keeps billing?

When a wiped device keeps billing, MDM has finished its security ticket and finance has not started the carrier stop-bill. The console already shows a successful wipe. The BAN still prints an MRC against a serial that no longer boots.

Pass that serial to ExpenseLogic and the line either matches an Employee ID or it does not. If the roster says gone, the next action is stop-bill, not another policy push.

A Fortune 100 engagement managed 10,000-plus wireless devices globally and recorded $830,000 in annual savings from wireless discovery and optimization. A food service client on 600-plus lines cut cost 22 percent and more than $400,000 in year one after policy and inventory were joined. Those are invoice outcomes, not console outcomes.

Telecom expense management is the wireline cousin of the same join. TEM onboarding data is the HR feed and the BAN list you have to hand over before the loop can run. MDM enrolls what you already bought. The bill loop asks whether you should still be buying it.

Should MDM offboard wait for a letter of agency?

MDM offboard should not wait for a letter of agency to wipe the handset, but stop-bill still needs carrier authority. Wipe is a console action. Stop-bill is a carrier action. RadiusPoint needs a scoped letter of agency to run the second job. A read-only billing grant is not ordering rights.

NIST SP 800-124 Rev. 2 ends at dispose or reuse. Dispose does not include a BAN instruction. If security wipes on Tuesday and the letter of agency is still in legal review on Friday, ExpenseLogic can flag the MRC. It cannot file the disconnect. RadiusPoint has published $18,000 a year from eliminating unneeded toll-free numbers. MDM never enrolled those circuits. The bill loop did.

A food-service fleet of 600-plus lines still needed policy plus inventory, not a better wipe profile. The 22 percent / more than $400,000 year-one result sat on the invoice. Fortune 100 wireless discovery of $830,000 a year sat on the same loop. Neither figure is an MDM console metric. Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category observation, not a RadiusPoint guarantee, and it does not attach to a wipe count.

Event Who acts without an LOA What RadiusPoint still needs
Wipe MDM or EMM admin, same day Serial number on the ExpenseLogic record
Roster close HR, on the monthly feed Employee ID joined to the line
Stop-bill Your staff, or RadiusPoint once the LOA is scoped Billing grant or ordering grant, written down

Switching TEM providers is a different inventory risk: the LOA and the serial-to-employee file have to leave with you. If the wipe ticket closes and legal still has the grant, write the MRC as a known miss. Do not call the offboard complete.

ExpenseLogic joins serial number, Employee ID, and the wireless invoice

ExpenseLogic joins serial number, Employee ID, and the wireless invoice so a wipe, a departure, or a zero-use flag can become a stop-bill. RadiusPoint analysts run that join. You keep the MDM console and the dollar approval. One platform covers wireless next to wireline and utilities at the same month-end.

RadiusPoint is ISO 9001 certified since 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. A capability statement and the about page carry the firm facts. Credentials tell you the operator is real. The join tells you the wipe hit the BAN.

FAQ

Is MDM the same as managed mobility services?

No. MDM is the control plane on the handset: enroll, encrypt, lock, and wipe. Managed Mobility Services (MMS) is device lifecycle plus wireless expense: staging, help desk, Employee ID, and the bill. RadiusPoint sells MMS on ExpenseLogic. You still need an MDM or EMM console that can wipe a lost phone. Wiping a phone is not paying the BAN, and paying the BAN is not encrypting the phone. Both jobs have to run on the same offboard.

Does RadiusPoint replace our MDM console?

No. RadiusPoint does not enroll devices, push OS policy, or remote-wipe a handset. ExpenseLogic stores serial number and Employee ID and audits the wireless invoice down to the phone number. Keep Intune, Jamf, or whatever console you already run. Add the bill loop so a wipe, a roster close, or a zero-use flag can become a stop-bill. A managed engagement that tries to replace your console is selling the wrong plane.

What is the difference between MDM and EMM?

MDM concentrates on the device. EMM adds applications, content, and identity. NIST SP 800-124 Rev. 2 treats EMM as the suite and MDM as a piece inside it. Unified Endpoint Management (UEM, here the endpoint product, not Utility Expense Management) widens the same suite to desktops and other endpoints. None of those products is a TEM invoice operator, and none of them files a carrier disconnect.

Do we still need MDM if we outsource wireless expense?

Yes. Outsourcing the BAN does not encrypt the phone. A managed mobility engagement that cannot wipe a lost device has a finance operator and no control plane. RadiusPoint will run the invoice on ExpenseLogic. You still need a console that can lock and wipe, including a selective wipe on BYOD. The food-service 22 percent result and the Fortune 100 $830,000 wireless figure are invoice outcomes. They assume the device layer already exists.

How does MDM relate to BYOD?

On BYOD, MDM or EMM typically containers corporate data so a wipe can be selective. The carrier line may still be corporate, stipend, or personal. RadiusPoint’s join still needs an Employee ID and a BAN. A personal phone on a corporate line is a policy question and an invoice question at once. A container that wipes email and leaves the MRC running is the same Gap as a corporate wipe with no stop-bill.

Is UEM on this page Unified Endpoint Management or Utility Expense Management?

On this page, UEM means Unified Endpoint Management, the endpoint suite that stretches MDM across desktops. RadiusPoint’s other UEM is Utility Expense Management: meters, tariffs, and vacant-site bills, on utility expense management. Write the words. The acronym is already overloaded. A wipe policy is not a meter audit, and a meter audit will not lock a lost phone.

What to do before the next invoice cycle

Pick ten serial numbers that security marked wiped or recovered last quarter. Match each to a carrier line and an Employee ID. If a line still bills, that is the operating gap. RadiusPoint will run that join on a managed ExpenseLogic engagement. Every cycle you wipe without a stop-bill is a cycle MDM can succeed and finance can fail.

References

  1. 2026 Data Breach Investigations Report executive brief | Verizon
  2. Verizon DBIR 2026: Vulnerability Exploitation Overtakes Credential Theft as Top Breach Vector | SecurityWeek
  3. SP 800-124 Rev. 2, Guidelines for Managing the Security of Mobile Devices in the Enterprise | NIST CSRC
  4. Guidelines for Managing the Security of Mobile Devices in the Enterprise: NIST Publishes SP 800-124 Revision 2 | NIST
  5. Managed Mobility Services | RadiusPoint
  6. Why You Need a Managed Mobility Provider | RadiusPoint
  7. Wireless Expense Management vs Telecom Expense Management | RadiusPoint
  8. Finding and Killing Zero-Use Mobile Lines | RadiusPoint
  9. The MACD Process in Telecom Expense Management, Explained | RadiusPoint
  10. Telecom Lifecycle Management: A Practical Guide | RadiusPoint
  11. Telecom Expense Management Services | RadiusPoint
  12. The Data a TEM Provider Needs Before Day One | RadiusPoint
  13. 4 Benefits of Telecom Expense Management (TEM) | RadiusPoint
  14. Capability Statement | RadiusPoint
  15. About RadiusPoint | RadiusPoint
  16. Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
  17. What Do You Lose When You Switch TEM Providers? | RadiusPoint
  18. Utility Expense Management | RadiusPoint
  19. ExpenseLogic | RadiusPoint
  20. Sharon R. Watkins | RadiusPoint
  21. ExpenseLogic reviews | Capterra

Related articles

Disclaimer

This article is general information for IT, security, finance, and mobility teams. It is not security, legal, or accounting advice. Verizon DBIR figures describe category breach research, not RadiusPoint incidents. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results. RadiusPoint does not sell MDM, EMM, or UEM software.

aerial view business team

Detailed Guide on IT Asset Management for Enterprises & SMBs

TEM Managed Services0

By Sharon Watkins, Founder and CEO, RadiusPoint · 12 min read

IT asset management at RadiusPoint is the serial, lease, and employee record that every invoice line has to match each cycle. A CMDB that maps configurations does not do that work. The bill can still arrive for a laptop that left with the user.

IT asset management (ITAM) is the practice of tracking hardware, software, leases, and related spend from acquisition through disposal so finance can test the invoice against the live asset. This page is the RadiusPoint version of that job: serial-number records inside ExpenseLogic, wrapped around telecom, wireless, and utilities. It is not a ServiceNow explainer.

Inventory work has recovered $174,000 in re-credits when services did not match the bill. A Fortune 100 client ran about 10,000 wireless devices against Employee IDs. RadiusPoint has published $120,000 a year from contract rate optimization and $250,000-plus in unrealised cost savings uncovered. ISO/IEC 19770-1:2017, confirmed in 2024, is the ITAM management-system standard. RadiusPoint’s published credential on process discipline is ISO 9001 since 2002, not a 19770 certificate.

Key Takeaways

  • RadiusPoint ITAM is serial, lease, and Employee ID on the same record the invoice is scored against. A configuration database is a neighbor, not a substitute.
  • Inventory management has recovered $174,000 in re-credits when billed services did not match live assets.
  • ExpenseLogic stores 28-plus lease data fields, including automatic annual increase calculations, against the serial.
  • ISO/IEC 19770-1:2017 (37 pages, third edition, confirmed 2024) is a discipline-specific extension of ISO 55001:2014. RadiusPoint does not claim 19770 certification.

The Short Version

IT asset management for TEM, mobility, and utility spend is an invoice operation with a serial attached. If you cannot name the serial, the Employee ID, and the lease term, you are listing devices, not managing assets.

In this article

IT asset management here is an invoice record, not a CMDB

IT asset management at RadiusPoint is the serial, lease, and employee record that every invoice line has to match each cycle. A configuration management database (CMDB) maps how components depend on each other so incidents resolve faster. Useful for operations. It does not tell accounts payable whether this month’s lease bill still matches the serial ExpenseLogic holds.

RadiusPoint has sold software plus people since 1992. ExpenseLogic is the platform. Named analysts audit lines against inventory rather than sampling. That model is the commercial page for telecom expense management. This article is the asset-record layer sitting under that service.

Do not keep a second source of truth. A scan without a bill is a museum catalog.

How does ITAM differ from telecom lifecycle management?

IT asset management tracks the serial, lease, and owner of a device; telecom lifecycle management tracks the service from order through disconnect. They share a month-end close. Mixing them hides a live serial next to a dead circuit on the same bill.

A laptop can finish its ITAM life while the wireless line auto-renews. A circuit can die while the router lease keeps billing. RadiusPoint has to see both. Managed mobility services attach the serial to the Employee ID. SaaS and cloud spend management is the license cousin: a seat with no user is the same failure mode as a serial with no owner.

The Serial-to-Invoice Match

The Serial-to-Invoice Match is RadiusPoint’s five-field test that an IT asset record must pass against the billed invoice line each cycle. Generic ITAM pages teach discovery, CMDB, and ISO vocabulary. They do not teach a five-field match built for serials, leases, Employee IDs, and BANs.

An invoice audit that cannot see those five fields is a three-way match with the asset missing. Telecom refund recovery is what happens after the Match fails and someone files. The Match is how you know the error is an asset failure, not an AP coding failure.

Field On the asset record On the invoice or lease bill Fail mode if missing
Serial Hardware ID, IMEI, or asset tag Billed identifier You cannot prove which unit the charge claims
Employee ID HR owner on the roster Allocation to a person or role Departed users keep the device and the bill
Lease or rate Term, increase, residual, or MRC Billed unit price Last year’s schedule can bill all year
Cost center Department or location Chargeback code The cost hides in corporate overhead
Disconnect duty Who files the stop-bill, and the fee Presence or absence of the charge The asset leaves. The bill does not.

A pass is five fields populated on both sides. A stored spreadsheet with none of those fields extracted is not a pass.

Which lease fields actually have to live on the asset?

Lease fields that have to live on the IT asset include term, increase schedule, residual, cost center, and the billed serial. RadiusPoint’s asset module holds 28-plus lease data fields and calculates automatic annual increases. A folder of PDFs does not do that math on the anniversary date.

The increase is the quiet failure. A 3 percent annual bump that nobody loads becomes an “invoice error” that is actually a contract performing as written. ExpenseLogic keeps the schedule on the serial so the invoice is scored against the right year, not against year-one memory.

Cost allocation is downstream once the serial is correct. A MACD that moves a user and leaves the lease on the old cost center fails the Match the following month. The lease fields are the asset’s contract. Treat them that way.

What RadiusPoint recovers when the asset and the invoice disagree

RadiusPoint recovers cash when the billed serial, the live employee, and the lease terms disagree, and the published cases name those dollars. Inventory management recovered $174,000 in re-credits. Contract rate optimization has returned $120,000 a year. Unrealised cost savings uncovered have exceeded $250,000.

A Fortune 100 wireless program with about 10,000 devices is ITAM at mobility scale: serial plus Employee ID plus BAN. One line of unneeded toll-free numbers ran $18,000 a year. That is a ghost asset with no handset. Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category observation, not a RadiusPoint guarantee.

Zero-use mobile lines are ITAM after HR already closed. Client location counts have grown from 170 to 1,200 on the same inventory discipline. That discipline is the asset layer under operational cost reduction.

What does ISO/IEC 19770-1 leave for the invoice to prove?

ISO/IEC 19770-1 leaves the invoice unmatched, because the standard specifies an ITAM system, not a BAN test against a billed serial. The live ISO record for ISO/IEC 19770-1:2017 is 37 pages, third edition, confirmed 2024. RadiusPoint does not claim 19770 certification. The published certificate is ISO 9001 since 2002. Five fields on the serial still have to meet the billed line.

Finance teams who treat 19770 as the whole program still miss Employee ID, BAN, and stop-bill duty. Those are RadiusPoint’s Serial-to-Invoice Match fields. A 19770 program can be excellent at software entitlement and still pay a lease on a laptop that left. ExpenseLogic stores 28-plus lease fields, including automatic annual increases, against the serial so the anniversary math is not year-one memory. A 3 percent contractual bump that nobody loaded becomes an “invoice error” that is actually the contract performing as written.

Client location counts have grown from 170 to 1,200 on the same inventory discipline. Inventory work recovered $174,000 in re-credits when billed services did not match live assets. One line of unneeded toll-free numbers ran $18,000 a year: a ghost asset with no handset. Contract rate optimization has returned $120,000 a year. Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category observation, not a RadiusPoint guarantee, and it is not a 19770 badge.

Utility expense management applies the same Match to a meter: location, tariff, consumption. UEM there means Utility Expense Management, not Unified Endpoint Management. A closed site with a live meter is the facilities version of a departed user with a live serial. Vacant utility cost recovery is what you do after the meter outlives the occupant. Do not let an ISO catalog collapse them.

Why does ExpenseLogic store serials against employee IDs?

ExpenseLogic stores serials against employee IDs so a departed user cannot keep a device and a line billing after HR already closed. The HR feed is monthly. Annual line registration forces a clean user dataset once a year. Those two clocks are how ITAM stays honest between audits.

Onboarding data is what RadiusPoint needs before day one, including the roster that makes Employee ID real. If you switch providers, the serial-to-employee file is the asset you cannot afford to leave behind.

ISO/IEC 19770-1:2017, IT asset management systems, requirements, is 37 pages, third edition, confirmed in 2024, with Amendment 1 in 2024 on climate. It is a discipline-specific extension of ISO 55001:2014. RadiusPoint’s published certificate is ISO 9001 since 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. A capability statement and the about page carry the firm facts. Credentials tell you the operator is real. The Match tells you the asset is being used.

FAQ

Is IT asset management the same as a CMDB?

No. A CMDB maps configurations and dependencies so incidents resolve. IT asset management at RadiusPoint maps serial, lease, owner, and billed rate so the invoice can be tested. You can have a perfect dependency map and still pay a lease on a laptop that left. Feed the CMDB from the same inventory. Do not let it replace the Match. ExpenseLogic is the invoice record. The CMDB is a neighbor, not a substitute that never sees the BAN.

Do we need ISO/IEC 19770-1 certification to run ITAM?

No. ISO/IEC 19770-1:2017 specifies requirements for an IT asset management system and was confirmed in 2024. It is useful vocabulary. RadiusPoint’s published certificate is ISO 9001 since 2002. Do not treat a 19770 badge as a substitute for five populated fields on the serial. The $174,000 re-credit figure and the $18,000 toll-free ghost line are invoice outcomes. They do not require a 19770 certificate to be true.

How does ITAM connect to utility spend?

Utility Expense Management (UEM) is meter-level invoice operations for electricity, gas, water, sewer, and waste. It is not Unified Endpoint Management. A meter is an asset with a location and a tariff. The same Match logic applies: if the site is closed and the meter still bills, the asset outlived the owner. Vacancy cost recovery has decreased utility expenses by 12 percent in published RadiusPoint work.

What do we export if we change providers?

Export serial, Employee ID, BAN, lease term, and cost center in a usable file. If those five fields stay inside a vendor portal, you do not own your ITAM. You rent a list. RadiusPoint will tell you what leaves with you. Ask that before you sign. The 170-to-1,200 location growth only matters if the serial file survives the conversion. A 19770 binder that cannot export those five fields is documentation, not an asset record.

Do the monthly HR feed and annual line registration replace each other?

No. The HR feed is monthly and catches departures between audits. Annual line registration forces a clean user dataset once a year. ExpenseLogic runs both clocks against the serial. Skip the monthly feed and a January leaver bills until December. Skip registration and shadow devices never declare an owner. RadiusPoint named analysts still test the invoice every cycle. The clocks tell them who should be on it.

What to do before the next invoice cycle

Pick 20 serials. Fill the five Match fields from the asset record, then from last month’s invoice or lease bill. If a cell is empty, that is the operating gap. RadiusPoint will fill those cells for a managed ExpenseLogic engagement. The $174,000 re-credit figure is what the gap costs when nobody fills them.

References

  1. ISO/IEC 19770-1:2017 Information technology: IT asset management, Part 1: IT asset management systems, Requirements | ISO
  2. ExpenseLogic | RadiusPoint
  3. Telecom Expense Management Services | RadiusPoint
  4. Telecom Lifecycle Management: A Practical Guide | RadiusPoint
  5. Managed Mobility Services | RadiusPoint
  6. SaaS & Cloud Spend Management Results in Cost Savings | RadiusPoint
  7. Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
  8. How Companies Recover Telecom Refunds and Credits From Carriers | RadiusPoint
  9. Allocating Telecom and Utility Costs Across Departments | RadiusPoint
  10. The MACD Process in Telecom Expense Management, Explained | RadiusPoint
  11. Finding and Killing Zero-Use Mobile Lines | RadiusPoint
  12. 5 Strategies That Will Help Reduce Telecom Expenses | RadiusPoint
  13. The Data a TEM Provider Needs Before Day One | RadiusPoint
  14. What Do You Lose When You Switch TEM Providers? | RadiusPoint
  15. Reduce Your Operational Costs | RadiusPoint
  16. Capability Statement | RadiusPoint
  17. About RadiusPoint | RadiusPoint
  18. Utility Expense Management | RadiusPoint
  19. Vacant Cost Recovery: The Utility Bills Nobody Is Watching | RadiusPoint
  20. Sharon R. Watkins | RadiusPoint
  21. ExpenseLogic reviews | Capterra

Related articles

Disclaimer

This article is general information for finance, IT, and procurement teams managing IT assets that generate telecom, wireless, lease, and utility invoices. It is not legal, accounting, or ISO-certification advice. Outcomes cited are from specific RadiusPoint client engagements already in RadiusPoint’s published case studies and are not a guarantee of future results. Category-level ranges and ISO standard descriptions are hedged and are not RadiusPoint promises. RadiusPoint does not claim ISO/IEC 19770 certification.

iStock 13871340702x

What Is Invoice Auditing? A Guide for SMBs and Enterprises

UEM Managed Services0

A supplier invoice is a claim, not a fact. Approving it only confirms that someone expected a bill from that vendor; whether the charges are right is a separate question, and answering it is the job of an invoice audit.

An invoice audit is the line-by-line test of a supplier invoice against the contract, the agreed rates and evidence that the goods or services were delivered, run before payment to stop errors or after payment to recover them. The method holds across accounts payable (AP), but the reference data changes: a purchase order and receiving record for goods, a rate schedule and service inventory for telecom, a tariff and meter read for utilities. Recurring telecom and utility invoices arrive with no purchase order, which is why they need a category-specific audit.

Skipping the test has a measurable cost. In the Association of Certified Fraud Examiners (ACFE) report Occupational Fraud 2026, the fraud examiners surveyed estimate that organizations lose 5% of revenue to fraud each year, and the typical scheme among the study’s 2,402 cases ran 12 months before anyone caught it. RadiusPoint, founded in 1992, audits telecom and utility invoices through its ExpenseLogic platform; for a Fortune 100 manufacturer, that work produced $450,000 in telecom refunds in the first year.

Key takeaways

  • An invoice audit tests each charge against the contract, the agreed rate and proof of delivery.
  • Federal law (31 U.S.C. § 3351) defines improper payments to include duplicates, payments for things not received and missed discounts, giving AP teams a ready-made test list.
  • Pre-payment audits prevent losses; post-payment audits recover them, but only inside claim windows, which run two years for tariffed telecom overcharges (47 U.S.C. § 415).
  • Telecom and utility invoices have no purchase order, so they’re tested against inventories, contract rates, tariffs and meter data.
  • The ACFE’s 2026 study names billing schemes among the most serious fraud risks when frequency and financial damage are weighed together.

The short version: check every supplier invoice before payment, and audit every line of recurring telecom and utility spend against contract rates and an inventory of live services, because those errors repeat each month until someone disputes them.

What does an invoice audit actually test?

An invoice audit tests whether each charge was owed, priced at the contract rate, actually delivered, not paid twice, and net of discounts due. Those tests aren’t arbitrary. They mirror how US federal law defines an improper payment in the Payment Integrity Information Act of 2019, which lists payments to ineligible recipients, duplicate payments, payments for goods or services not received, and payments that ignore applicable discounts.

Improper payment type (31 U.S.C. § 3351) What the audit compares General AP example Telecom or utility example
Incorrect amount, including an overpayment Billed price against the contract or rate schedule Unit price above the agreed price list Circuit billed above its contracted rate
Duplicate payment Invoice number, amount and period against payment history Same invoice under two vendor records Same period billed on an old and a new account
Good or service not received Billed items against receiving records or the service inventory Goods that never reached the dock Line still billing at a closed location
Ineligible good or service Billed items against what the contract allows Excluded item invoiced anyway Feature or plan nobody ordered
Missed applicable discount Contract terms against the invoice net Volume discount left off Contracted credit missing
Ineligible recipient Payee details against the vendor master Bank details changed by email request Bill from a provider absent from the inventory

The last row is where fraud gets in. In the Association for Financial Professionals (AFP) 2026 Payments Fraud and Control Survey of 465 treasury practitioners, 76% of US organizations reported attempted or actual payments fraud in 2025, and business email compromise affected 74%.

Approval and matching test something else: an approver confirms the spend was authorized, and a three-way match confirms the invoice agrees with a purchase order and receiving record. Neither asks whether a recurring charge is still at the contracted rate or whether the service still exists, the gap explained in how an invoice audit differs from three-way matching.

Pre-payment audits prevent losses; post-payment audits recover them

A pre-payment audit stops a wrong charge before cash leaves, while a post-payment recovery audit reclaims money already paid, within whatever claim window remains. US federal law builds both into its payment rules. The Payment Integrity Information Act calls for both prepayment and postpayment controls and requires recovery audits for any agency program spending $1,000,000 or more a year when auditing is cost-effective.

Dimension Pre-payment audit Post-payment recovery audit
When it runs Between invoice receipt and approval After payment, often months or years later
What it needs Current rates, purchase orders or a service inventory, the vendor master Paid invoice history, contract terms in force at the time, proof of delivery
Hard limit Only as good as the reference data on the day Claim windows: two years for tariffed telecom overcharges (47 U.S.C. § 415); four years by default for sale-of-goods contracts, reducible to one year by agreement (UCC § 2-725)

Payment errors mostly cost the payer: the Government Accountability Office (GAO) found overpayments made up $153 billion of an estimated $186 billion in federal improper payments in fiscal year 2025, about 82%. Recovery also runs on a clock. For tariffed telecom charges, a written claim to the carrier inside the two-year window extends it, so file disputes in writing as soon as an error is confirmed.

How does the invoice audit process work, step by step?

The invoice audit process gathers reference documents, captures every line, tests each charge, verifies the vendor, disputes errors, and records the cause so it stops. The order matters. Testing before the reference set is complete produces false passes, because a charge can only fail against a rate, a record, or an inventory you’ve actually loaded.

  1. Assemble the reference set: contracts, rate schedules, purchase orders and receiving records where they exist, the vendor master, and an inventory of live services and locations for recurring spend.
  2. Capture every line item, not a sample.
  3. Test each charge for price, quantity or service existence, duplicates across accounts and periods, taxes and surcharges, and promised credits.
  4. Verify the payee and any change to remittance details through a contact already on file, never through the message requesting the change.
  5. Dispute in writing and track to credit. A finding isn’t recovered until the credit appears on a later invoice or the refund arrives.
  6. Record the finding and fix the cause: log the charge, the reference it failed and the amount, then correct the contract record, inventory or approval rule that let it through.

The invoice auditing process is the same for every spend category; only step one’s reference set changes. Step six matters more than it looks. Under the Payment Integrity Information Act, a federal payment that can’t be shown proper for lack of documentation is treated as improper for estimation purposes, and that’s a sound rule for any audit trail.

Why do telecom and utility invoices need their own audit?

Telecom and utility invoices bill recurring services without purchase orders, so they must be audited against contracts, service inventories, tariffs and meter data instead. A general AP review sees a familiar vendor, a familiar amount and an approved account, then passes a charge that may have stopped being valid months earlier.

Telecom invoices also carry regulatory rules a generic audit doesn’t know. Under Federal Communications Commission (FCC) rule 47 CFR § 54.712, a carrier’s Universal Service Fund line item can’t exceed the interstate portion of the bill times the quarter’s contribution factor, which is 42.0% for the fourth quarter of 2026. No purchase order tells you which charges are interstate. The wider scope is covered in what a line-item telecom audit finds.

Utility bills fail differently. The reference is a tariff or supply contract plus the meter, and the core test is consumption. US Energy Information Administration (EIA) data show 16.5 million of the 20.4 million commercial-sector electric meters in 2024 were advanced meters, about 81%, which EIA defines as recording usage at least hourly, so a closed store still drawing daytime load shows up. The checks for a single bill are in how to audit a utility bill for errors.

How RadiusPoint and ExpenseLogic audit every telecom and utility line

RadiusPoint audits every line of client telecom and utility invoices in ExpenseLogic against contracted rates, tariffs and inventory, without sampling. The platform is software; the audit is software plus people. RadiusPoint staff work the exceptions, chase the carriers, file the disputes and close the tickets.

Within RadiusPoint’s telecom expense management (TEM) and Utility Expense Management (UEM) services, each ExpenseLogic capability answers a specific failure:

  • Line-item audit across wireline, wireless and data circuits against contracted rates and inventory, so a mismatched charge is flagged, not approved.
  • Daily missing-bill reporting, because an invoice that never arrives can’t be audited and can turn into late fees.
  • Closed-location billing exception reports for service still billing at shut sites. One multi-location client recovered $1,500 a month, $18,000 a year, from utilities at closed locations.
  • Meter-level utility audit of contract and tariff rates, consumption and thresholds, so a misapplied rate surfaces at the meter, not inside an account total.
  • Accrual and general ledger (GL) interface files with enterprise resource planning (ERP) integration, so corrected amounts reach the general ledger without rekeying.

Published RadiusPoint client results include $120,000 a year from contract rate optimization, $18,000 a year from eliminating unneeded toll-free numbers, and $174,000 in re-credits recovered through inventory management.

Sharon Watkins worked in internal audit at a bank before founding RadiusPoint in 1992. RadiusPoint was named a Distinguished Vendor in the Amalgam Insights 2024 Telecom Expense Management Vendor SmartList, and ExpenseLogic holds a 4.8 rating from 31 Capterra reviews. As Watkins has put it: “The telecom industry can’t keep up with the ubiquitous challenges and doesn’t have the time to identify savings.”

Where invoice audits miss money they should have caught

Invoice audits miss money when they sample instead of testing every line, start after claim windows close, or lack an inventory to test against. Control gaps compound all three. In the ACFE’s 2026 study, more than half of fraud cases involved either missing internal controls or an override of controls that existed.

Sampling estimates an error rate; it doesn’t recover dollars in lines nobody opened. Delay is the second leak: the ACFE found schemes caught within six months had a median loss of $40,000, against more than $1.1 million for schemes running past five years, and recurring billing errors compound the same way.

Without an inventory of record, an audit can’t tell you a correctly priced service should have been disconnected. A credit recovered without fixing the contract record or inventory returns next month. The ACFE tied proactive data monitoring, management review and surprise audits to lower losses and faster detection, and a standing line-item audit is proactive data monitoring.

What should you do before the next invoice cycle closes?

Before the next cycle closes, pick one recurring vendor category, build its inventory of live services, and audit one month of invoices line by line. A single month of line-level results shows whether the errors are isolated or structural, and structural errors repeat on every invoice until someone disputes them.

Every month that goes unaudited is another month of the same errors billing at the same rate. If you’re scoping a broader program, what invoice auditing services cover and cost sets out the options.

Frequently asked questions

Is invoice auditing the same as invoice reconciliation?

No. Reconciliation confirms that what you paid matches what you recorded in the ledger and on the bank statement. Invoice auditing asks whether the charge should have been billed at all, at that price, for that period. A fully reconciled ledger can still hold an overcharge that was paid and recorded correctly.

Can a small business run its own invoice audit?

Yes. The ACFE’s 2026 report found smaller businesses had the highest median fraud losses of any organization size. A small team can start with its largest recurring vendors: pull each contract, list what’s actually in service, and test one month of invoices against both before widening the scope.

Who should perform an invoice audit, your AP team or an outside firm?

Either can, provided the auditor isn’t the person who approved the spend. Federal recovery audit rules let agencies use their own staff, other agencies or private contractors, while the agency keeps the final decision on any overpayment claim. The same split works anywhere: the auditor finds and documents, and your organization decides what to dispute.

Can an invoice audit catch fraud, or only billing mistakes?

Both, though it’s built around errors. The tests that flag an overcharge also surface services never received, duplicates and payees that don’t match the vendor master, which is how billing schemes work. The ACFE lists an unusually close relationship with a vendor or customer among the behavioral red flags with the highest median losses, $300,000 per case.

References

  • Association of Certified Fraud Examiners, Occupational Fraud 2026: A Report to the Nations, 2026. acfe.com
  • Association of Certified Fraud Examiners, “Report: 84% of fraudsters show at least one behavioral red flag,” press release, May 12, 2026. acfe.com
  • Association of Certified Fraud Examiners, “Key Findings from Occupational Fraud 2026: A Report to the Nations,” ACFE Insights, May 19, 2026. acfe.com
  • Association for Financial Professionals, “Over 75 Percent of US Firms Experienced Payments Fraud in 2025 While AI Adoption for Fraud Mitigation Lags,” press release, April 14, 2026. financialprofessionals.org
  • US Congress, Payment Integrity Information Act of 2019, Public Law 116-117, 134 Stat. 113 (2020), 31 U.S.C. §§ 3351 and 3352. govinfo.gov
  • US Government Accountability Office, “Payment Integrity: Agencies’ Estimated Improper Payments Increased to $186 Billion in Fiscal Year 2025,” GAO-26-108694, 2026. gao.gov
  • US Government Accountability Office, “GAO Reports Improper Payments Rose to an Estimated $186 billion Across the Federal Government in Fiscal Year 2025,” press release, April 27, 2026. gao.gov
  • 47 U.S.C. § 415, Limitations of actions. law.cornell.edu
  • 47 CFR § 54.712, Contributor recovery of universal service costs from end users. law.cornell.edu
  • Federal Communications Commission, Office of Managing Director, “Proposed Fourth Quarter 2026 Universal Service Contribution Factor,” Public Notice DA 26-946, September 2026. docs.fcc.gov
  • Uniform Commercial Code § 2-725, Statute of Limitations in Contracts for Sale. law.cornell.edu
  • US Energy Information Administration, Electric Power Annual, Table 10.05, Advanced Metering Count by Technology Type, 2015 through 2024. eia.gov
  • US Energy Information Administration, “How many smart meters are installed in the United States, and who has them?” eia.gov
  • Amalgam Insights, 2024 Vendor SmartList for Telecom Expense Management, Distinguished Vendor designation, February 2024.
  • Capterra, ExpenseLogic reviews, 4.8 from 31 reviews. capterra.com
  • RadiusPoint, published client case studies: Fortune 100 manufacturer telecom refunds; contract rate optimization; toll-free number elimination; inventory re-credits; closed-location utility recovery.

Third-party figures describe the populations each source studied and won’t predict results for a specific organization. RadiusPoint client results reflect individual engagements, and outcomes depend on invoice volume, contract terms, inventory accuracy and how quickly errors are disputed. This article is general information, not legal or accounting advice.

pexels pixabay 416405 2

What Is Telecom Lifecycle Management? Every Stage From Order to Disconnect

TEM Managed Services0

Clearing the bills took 4,049 disconnect orders and a 6-month effort with vendors, some of which kept billing lines after disconnects had been requested. The skipped step came much earlier. A healthcare company with more than 700 locations installed SIP trunks at each one, and the regular business lines they replaced were supposed to be canceled. No inventory had been taken first, and overpayments were estimated at more than $30,000 a month.

Telecom lifecycle management is the practice of tracking each telecom service and device a company pays for, from the order through installation, billing, changes and the final disconnect. At every stage, the inventory, contract, invoice and cost allocation records should change with it. Telecom asset lifecycle management applies the same stages to the devices and equipment behind each service. Skip a stage and the invoice keeps charging for a service the company has moved, changed or replaced. This guide covers that enterprise side, not a carrier’s subscriber or product lifecycle.

It runs alongside telecom expense management (TEM), which works the invoice side of the same loop. RadiusPoint covers the stages with its ExpenseLogic platform, including MACD (move, add, change, disconnect) ticketing with client-defined approval workflows, service validation, line-item audit against contracted rates and inventory, and closed-location billing exception reports.

Key Takeaways

  • Every stage from order to disconnect should change at least one record: inventory, contract, invoice or cost allocation.
  • In a published RadiusPoint case, SIP trunks replaced business lines at more than 700 locations without an inventory; the cleanup took 4,049 disconnect orders and returned more than $174,000 in credits.
  • Mobile devices add stages a circuit never has, from kitting to recycling, and the HR roster decides when a device’s lifecycle should end.
  • In 2015, the U.S. Government Accountability Office (GAO) found only 5 of the 15 federal agencies it reviewed had complete mobile service and device inventories.

Short version: treat every telecom order, change and disconnect as unfinished until the inventory, contract, invoice and cost allocation records all reflect it, and take the inventory before any technology change is approved.

Every Stage From Order to Disconnect Should Change a Record

Each stage in a telecom service lifecycle should update at least one record: the inventory, the contract, the invoice or the cost allocation. The table maps each stage to its record, the invoice symptom when the update is skipped, and the ExpenseLogic or RadiusPoint capability that covers it.

Stage Record that should change What the invoice shows if it’s skipped Capability that covers it
Order placement Inventory: pending service, site and owner. Contract: the rate it should bill at. A new charge nobody can match to an approved order MACD ticketing with client-defined approval workflows; Intelligent Queue ordering portal
Installation verification Inventory: service marked installed, with its start date Charges for a circuit that isn’t installed or isn’t performing Service validation
Invoice receipt Invoice record: every billing account number (BAN) expected that cycle A missing bill that surfaces later as a past-due notice Daily missing-bill reporting
Cost allocation Cost center and general ledger (GL) code for each service Charges posted to the wrong department, or to one that closed Circuit split-billing across cost centers; monthly accrual and GL interface files
Invoice audit Each invoice line checked against the contract and the inventory Rates above contract, or services missing from the inventory Line-item audit across wireline, wireless and data circuits
Cost optimization Usage and owner for each line Zero-use lines and lines for people who’ve left, still at full price Zero-use device identification; Employee ID validation against a monthly HR roster
Payment Payment against the audited invoice; deposits on file An invoice paid before audit, or a deposit held after the service ends Deposit tracking; RadiusPoint can pay vendor invoices for clients once the client funds the account
Move, add or change Inventory: new site, feature or user. Contract: new rate. Old and new service billing side by side MACD ticketing
Contract renewal Contract: expiration date, rates and termination fees by service ID A renewal on old terms, or a termination fee when a service is cut early Vendor contract management; contract obligation alerts covering termination fees and dates
Disconnect or site closing Inventory: service retired. Cost allocation: charge removed. A line still billing after the disconnect request MACD ticketing; real estate system integration; closed-location billing exception reports

Invoice receipt, cost allocation, audit, optimization and payment repeat every billing cycle. The rest happen when something changes, and moves, adds, changes and disconnects arrive as tickets through the telecom MACD process. A ticket that leaves the inventory unchanged leaves every later stage checking against an old list.

What Happens When a Lifecycle Stage Gets Skipped?

When a stage is skipped, the carrier keeps billing for the old state, because nothing told the billing record that the service changed. Each charge looks like any other month’s, so nothing on the invoice flags it. The healthcare case shows what that looks like at scale.

In RadiusPoint’s inventory management case, nobody had listed the lines and services before the SIP trunk project, so nobody knew which business lines each trunk replaced. RadiusPoint inventoried 3,632 regular business lines and identified the purpose of each. Some vendors kept billing lines after disconnects had been requested, so RadiusPoint worked with them over a 6-month period to get those lines disconnected, removed from billing and recredited. It sent 4,049 disconnect orders and retrieved more than $174,000 in credits.

Two stages broke at once: the replaced lines weren’t disconnected as the trunks went live, and some requested disconnects never reached the bill. The case page’s lesson is to complete the inventory before a technology change is approved.

Mobile Devices Add Stages a Circuit Never Goes Through

A mobile device runs a longer lifecycle than a circuit: procurement, staging, kitting, deployment, troubleshooting, repair, recovery, recycling and retirement. Each stage should update the device record. The key record links the device, its line and a current employee, because that link breaks the day someone leaves.

ExpenseLogic tracks each device by serial number and Employee ID, and RadiusPoint’s managed mobility services reconcile lines against the HR roster to catch ex-employee and zero-use lines, with annual line registration to keep user records current.

Two published cases show what a broken link costs. In RadiusPoint’s Fortune 100 paper manufacturer case, with more than 10,000 wireless devices and end users, the organization was still paying for phones and services for employees no longer on the payroll. RadiusPoint identified more than $850,000 in ongoing telecom savings as cost avoided. In a separate food service case, an audit of more than 600 lines led to a 22% cut in monthly costs, more than $400,000 a year.

For recovery and recycling, the National Institute of Standards and Technology (NIST) Guidelines for Media Sanitization (SP 800-88 Rev. 2, September 2025) cover making data on storage media infeasible to access before reuse or disposal, and the U.S. Environmental Protection Agency (EPA) recommends certified electronics recyclers under the R2 or e-Stewards standards. Cancel or reassign the line in the same request, so a recycled phone leaves no monthly charge behind.

Why Does Every Other Stage Depend on the Inventory?

Every other record points back to the inventory: contracts tie to its service IDs, audits test invoices against it, and cost allocation reads from it. If the inventory is wrong, every later check confirms the wrong thing. That’s why the inventory has to come before a technology change, not after it.

Public audits find the same gap. In a May 2015 report, the GAO found that only 5 of the 15 federal agencies it reviewed had complete mobile service and device inventories. Only 1 had documented procedures for reviewing devices and plans for overuse, underuse or zero use. The same report put federal spending at about $1.2 billion a year on about 1.5 million mobile devices and associated services.

For wireline circuits and lines, an inventory of record built from carrier customer service records (CSRs) gives each later stage a list to test against. Keep the cost center and GL code on the same record, so a disconnect removes the charge from the right budget.

How Is Telecom Lifecycle Management Different From TEM?

Telecom lifecycle management tracks the service from order through disconnect, while TEM works the invoice side of that loop, from order to general ledger. The two share one inventory. Neighboring disciplines split the rest: IT asset management follows devices, and contract lifecycle management follows terms and renewals.

RadiusPoint’s guide to what telecom expense management is calls telecom lifecycle management the operational view of that cycle, from sourcing through disconnect. IT asset management tracks the serial, lease and owner of a device, while telecom lifecycle management tracks the service on it.

The names overlap: telecommunications lifecycle management, communications lifecycle management and TLM are other names for the same practice.

RadiusPoint and ExpenseLogic Cover the Stages With Software and People

RadiusPoint covers the telecom lifecycle with ExpenseLogic, a single cloud platform for telecom, wireless and utility expenses, backed by RadiusPoint staff. Its capabilities line up with the stage table, from MACD ticketing and service validation to line-item audit, contract obligation alerts, GL interface files and closed-location billing exception reports.

RadiusPoint staff work the invoices, chase the carriers, file the disputes and close the tickets in the ExpenseLogic platform. In the healthcare case, ExpenseLogic flagged the business lines vendors kept billing, so RadiusPoint could contact them and stop the charges.

RadiusPoint was founded in 1992 and is a women-owned business. ExpenseLogic holds a 4.8 rating on Capterra from 31 reviews, with reviews through December 2025, and Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 Vendor SmartList for Telecom Expense Management.

Every month a replaced line stays on a carrier’s records is another month of charges for a service you’ve already retired. Request a free demonstration to see MACD ticketing, service validation and closed-location billing exception reports in ExpenseLogic.

Frequently Asked Questions

Do you need a telecom lifecycle management platform, or will a spreadsheet do?

A spreadsheet lists services but doesn’t keep each one linked to its contract, invoices and cost center as they change. A telecom lifecycle management platform should hold those links by service ID, so a disconnect that never reached the bill shows up as an exception. ExpenseLogic holds them in one cloud platform for telecom, wireless and utility expenses.

Where do you start with telecom lifecycle management?

Start with the records the inventory is built from: the latest invoice for every billing account, the carrier contracts, and a signed letter of agency (LOA) that lets a third party request carrier records on your behalf. The TEM implementation timeline guide covers what takes the time in a rollout.

Does a telecom audit replace lifecycle management?

No. An audit compares invoices with contracts and inventory at one point in time, while lifecycle management keeps the inventory and contracts current between audits. A line-item audit is only as good as the inventory it checks against, and the inventory stays accurate only when audit findings feed back into it. ExpenseLogic runs line-item audit across wireline, wireless and data circuits.

Who should own telecom lifecycle management inside a company?

No single team holds every record. Telecom and wireless managers handle orders and carrier disputes, procurement holds contracts, facilities knows when sites close, finance owns cost centers, and HR knows who has left. Name one owner for the inventory of record and have each team send its changes there, so a closed site or a departed employee reaches the bill.

References

  1. RadiusPoint, “Inventory Management Helps Recovering $174K in Credits,” October 12, 2022.
  2. RadiusPoint, “$1.3M in Telecom Refunds and Cost Savings: Case Study,” June 10, 2023.
  3. RadiusPoint, “How Managed Mobility Services Cut Costs 22% ($400K in Year 1),” May 15, 2023.
  4. RadiusPoint, “Managed Mobility Solution & Service,” accessed October 2026.
  5. U.S. Government Accountability Office, “Telecommunications: Agencies Need Better Controls to Achieve Significant Savings on Mobile Devices and Services,” GAO-15-431, May 21, 2015. gao.gov
  6. National Institute of Standards and Technology, “NIST Special Publication (SP) 800-88 Rev. 2, Guidelines for Media Sanitization,” September 2025. csrc.nist.gov
  7. U.S. Environmental Protection Agency, “Certified Electronics Recyclers,” last updated July 31, 2026. epa.gov
  8. Capterra, “ExpenseLogic” product reviews, 4.8 from 31 reviews, accessed October 2026. capterra.com
  9. Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
  10. RadiusPoint, “About RadiusPoint,” accessed October 2026.

General information for IT, telecom and finance teams, not legal or contract advice. Carrier contract terms, termination fees and dispute rules vary by agreement. RadiusPoint outcomes cited here come from specific published client engagements on the case pages listed in References, and results vary by organization.

pexels rdne 7648020

Multi-Vendor Support: IT Hardware Maintenance vs. Multi-Carrier Expense Management

TEM Managed Services0

Two people search for “multi-vendor support” on the same morning. One runs servers, storage arrays and switches from several manufacturers and wants a single number to call when something fails overnight. The other manages carrier and utility invoices for every company location and wants one place to audit, dispute and renew them. Same phrase, two different jobs.

Multi-vendor support, in its standard IT sense, is a service model in which one provider maintains and troubleshoots hardware and related software from several manufacturers under a single contract and a single point of contact. RadiusPoint doesn’t provide that service. RadiusPoint provides the financial counterpart: multi-carrier expense management, which consolidates invoices, contracts, disputes and renewals from telecom carriers, wireless carriers and utility providers into one platform, ExpenseLogic, worked by a named RadiusPoint team.

Both disciplines exist because managing vendors one at a time is expensive. ITIC’s 2024 Hourly Cost of Downtime Survey of more than 1,000 firms found that a single hour of downtime costs over $300,000 for more than 90% of mid-size and large enterprises. On the billing side, World Commerce & Contracting’s 2023 research with Deloitte put average contract value erosion, the gap between what contracts should deliver and what they actually deliver, at 8.6%.

Key Takeaways

  • IT multi-vendor support puts break-fix, troubleshooting and escalation for mixed-manufacturer servers, storage and network gear under one provider. It’s an operations discipline.
  • Third-party maintenance overlaps with it but isn’t identical. It replaces manufacturer coverage, usually after warranty, and doesn’t always span every brand in the estate.
  • Multi-carrier expense management consolidates invoices, contracts, disputes and renewals across carriers and utilities. It’s a financial and audit discipline.
  • RadiusPoint delivers only the second. One multi-location RadiusPoint client saved $1,500 a month ($18,000 a year) on utility charges at locations that had already closed.

Short version: if mixed-manufacturer hardware needs fixing, hire a multi-vendor support or third-party maintenance provider; if carrier and utility bills, contracts and disputes need one owner, that’s multi-carrier expense management, which is the work RadiusPoint does.

What does multi-vendor support mean in IT?

In IT, multi-vendor support means one provider maintains, troubleshoots and repairs hardware and related software from several manufacturers under one contract and one escalation path. During an outage, the customer opens one ticket instead of several, and the provider coordinates whichever part, engineer or manufacturer the fix requires. One party owns the incident from first call to resolution.

Mordor Intelligence’s 2026 market report draws the same boundary: third-party support for mixed-vendor servers, storage and networks, excluding OEM (original equipment manufacturer) warranties bundled with equipment sales. It sizes multi-vendor support services at USD 59.29 billion in 2026, rising to USD 70.83 billion by 2031 at a 3.62% compound annual growth rate. Managed contracts held 70.65% of 2025 spending, and on-site support made up 55.95%.

The phrase also appears in contexts unrelated to hardware repair:

Context What “multi-vendor support” means there What gets consolidated
IT hardware services One provider supports servers, storage and network gear from several manufacturers Support contracts, break-fix tickets, parts and engineers
Network and IT monitoring software A tool can discover, monitor and manage devices from several manufacturers Device views, alerts and dashboards
Ecommerce marketplaces A platform lets independent sellers list products and fulfill orders Seller catalogs, orders and seller reporting
Telecom and utility expense management One platform and team handle accounts from several carriers and utilities Invoices, contracts, disputes and renewals

Multi-vendor network support

Multi-vendor network support applies the same model to routers, switches, firewalls and wireless controllers from different manufacturers. Uptime Institute’s Annual Outage Analysis 2025 reported that outages caused by IT and network-related issues are increasing, though power remains the most common cause of serious data center outages, and its 2026 analysis found more outages originating outside the data center, including in network connectivity.

Multi-vendor support, third-party maintenance and OEM support solve different problems

OEM support covers one manufacturer’s equipment, third-party maintenance replaces that coverage with an independent provider, and multi-vendor support puts mixed equipment under one accountable provider. The three often overlap inside one contract, which is why buyers mix them up. The useful question isn’t what a provider calls its service, but which equipment it covers and who owns a fault that crosses brands.

OEM support Third-party maintenance Multi-vendor support
Who provides it The manufacturer An independent provider One provider, independent or a manufacturer’s services arm
Equipment covered That manufacturer’s products Often post-warranty equipment, one brand or several Mixed equipment from several manufacturers
Typical trigger New equipment purchase Warranty expiry or a renewal quote that no longer makes sense Contracts and escalation paths multiplying across brands
Owner of a cross-brand fault Each manufacturer, for its own part Depends on contract scope The single provider
Main trade-off Direct access to firmware and engineering Extends older gear, but check warranty terms One contract, but depth varies by platform

Hybrid arrangements are common. Mordor Intelligence notes that buyers often keep OEM coverage on newer assets and move older fleets to third-party maintenance, partly because some manufacturers warn that unauthorized service can affect warranty coverage. The availability bar explains the caution: ITIC’s reliability polling, reported in its 2024 downtime survey, found that 90% of organizations require at least 99.99% availability, or 52 minutes of unplanned downtime per server per year.

Why do organizations consolidate IT support across vendors?

Organizations consolidate IT support because mixed-vendor outages are expensive, and every additional manufacturer adds another contract, renewal date and escalation path to manage. When a fault sits between a storage array and a switch, separate support contracts can turn one incident into parallel investigations. A single provider shortens that loop, and that’s the whole business case.

ITIC’s 2024 survey found that 41% of enterprises put the cost of one hour of downtime at $1 million to more than $5 million, and 97% of large enterprises with more than 1,000 employees put it above $100,000. In Uptime Institute’s 2025 annual survey, reported in its 2026 outage analysis, 57% of respondents said their most recent major outage cost more than $100,000. Its 2025 analysis found one in five respondents put their most recent outage above $1 million.

Those figures describe outages, not vendor counts, so they don’t prove consolidation prevents downtime. ITIC’s respondents ranked security (84%), human error (69%) and software flaws (65%) as the leading causes, and none of those disappear under one contract. What consolidation changes is how quickly the right engineer starts on the fault.

Does RadiusPoint provide IT hardware multi-vendor support?

RadiusPoint doesn’t provide IT hardware multi-vendor support, break-fix repair or OEM coordination; it manages telecom, wireless and utility expenses through its ExpenseLogic platform. If a server, storage array or switch fails, you need a multi-vendor support provider, a third-party maintenance firm or the manufacturer. An expense management firm can’t fix hardware, and RadiusPoint doesn’t claim to.

RadiusPoint’s overlap with “multi-vendor” is on the billing side. Sites in different regions come with different carriers, utilities and contract terms. The U.S. Energy Information Administration counted almost 3,000 electric distribution utilities operating in 2017 (168 investor-owned, 1,958 publicly owned and 812 cooperatives), and the Environmental Protection Agency’s service-area dataset maps more than 44,000 community water systems. That billing sprawl, not hardware, is what RadiusPoint has worked on.

Multi-carrier expense management puts every bill and contract in one place

Multi-carrier expense management consolidates carrier, utility and vendor invoices, contracts, disputes and renewals into one system that a single team audits against contract terms. It’s the billing equivalent of a single support contract. Instead of logging into a separate portal for every provider, finance and IT teams work from one record of what each location has, what it should cost and what’s in dispute.

Here’s how the two disciplines map:

IT multi-vendor support Multi-carrier expense management equivalent
One provider owns every hardware incident One platform and one team own every carrier and utility account
Service level agreements set response targets Contracted rates, tied to service IDs, set what each service should cost
Incident tickets track faults to resolution Billing disputes track overcharges to credit
Warranty and support renewal dates Contract expiration dates and termination fees
Asset inventory by serial number Spend and services reported by location, vendor and category

In telecom, this work is called telecom expense management (TEM), and our guide to reconciling billing account numbers across national and regional carriers covers the carrier mechanics. Electricity, gas, water, sewer and waste accounts follow the same logic under Utility Expense Management (UEM), audited at meter level.

Fragmented vendor contracts leak value even when nothing breaks

Fragmented vendor contracts lose money quietly, because renewals, rate changes and termination fees go unchecked when each agreement sits in a different portal or inbox. Nothing fails, so nothing opens a ticket. The cost shows up later as an auto-renewal at an outdated rate, or as a monthly bill for a site that closed long ago.

World Commerce & Contracting and Deloitte measured this across more than 1,200 organizations in 2023. Average contract value erosion was 8.6%, down from 9.2% in WorldCC’s 2014 study, with the best performers at a little over 3% and the worst above 20%. WorldCC lists invoicing errors, missed entitlements and avoidable disputes among the contract-related causes of that erosion. In RadiusPoint client work, contract rate optimization alone has returned $120,000 a year for one client.

A checklist for consolidating carrier and utility contracts

  1. Store every signed contract and its terms in one repository (the ExpenseLogic Contract Management module handles image storage and terms retention).
  2. Tie each contracted rate to its service ID and record the expiration date.
  3. Set alerts for contract obligations, including termination fees and dates, before renewals pass unreviewed.
  4. Audit every invoice line against those rates instead of sampling.
  5. Report spend by location, vendor and category so outliers stand out.
  6. Route moves, adds, changes and disconnects (MACD) through tickets so inventory and billing stay aligned.
  7. Give every dispute a named owner who follows it through to credit.

ExpenseLogic supports the first six steps in one platform, and the RadiusPoint team works the disputes in the seventh with carriers and utility providers.

How does RadiusPoint consolidate multi-carrier telecom and utility spend?

RadiusPoint consolidates multi-carrier telecom, wireless and utility spend in ExpenseLogic, one platform, while a RadiusPoint team audits invoices, tracks contracts and works disputes. Clients get software and people together: the platform holds the data, and named staff act on what it shows instead of leaving every follow-up to an already stretched internal team.

One RadiusPoint client grew from 170 to 1,200 locations on the platform, and a Fortune 100 client saved $830,000 a year through wireless discovery and optimization. Zero-use lines and closed-site billing are easier to catch once every vendor’s data sits in one place, and our guide to how companies recover telecom refunds and credits from carriers covers what happens next.

RadiusPoint was named a Distinguished Vendor in the Amalgam Insights 2024 TEM Vendor SmartList, and ExpenseLogic holds a 4.8 rating from 31 reviews on Capterra. Every month a closed site stays on an active account, the same charge bills again, and for one client that was $1,500 a month. If your contracts live in more places than your team can check, see how ExpenseLogic brings them into one platform.

Frequently asked questions

Is multi-vendor support the same as managed IT services?

Not quite. Multi-vendor support focuses on maintaining and repairing hardware and related software across manufacturers, while managed IT services usually take on broader operations such as monitoring, patching and help desk work. Mordor Intelligence’s market definition excludes pure help-desk outsourcing that isn’t tied to multi-vendor infrastructure support, which is a useful line to draw when you compare proposals.

How many carriers or utility providers does it take before consolidating bills is worth it?

There’s no published threshold that holds across industries. A better test is whether your team can answer these questions for every location without opening a vendor portal: what you’re contracted to pay, when each contract expires, which disputes are still open, and whether any closed site is still billing. If any of those answers lives only in one person’s inbox, that account is a candidate for consolidation.

What should we gather before consolidating carrier and utility accounts?

Start with a signed copy of every active contract, recent invoices for every account, a list of services by location, and any open disputes or credits you’re still waiting on. Those records let whoever audits the accounts compare billed charges with contracted rates. Contracts you can’t locate are worth chasing early, because an expiration date you can’t see is a renewal you can’t negotiate.

Does ExpenseLogic monitor hardware or replace our IT service desk?

No. It stores contracts, tracks expiration dates and termination fees, supports line-item invoice audit, reports spend by location, vendor and category, and runs MACD tickets for service changes. Hardware health, incident response and break-fix repair stay with your IT team and its support providers, while RadiusPoint handles the expense side.

References

  1. ITIC (Information Technology Intelligence Consulting), Laura DiDio, ITIC 2024 Hourly Cost of Downtime Survey Results, 2024.
  2. Uptime Institute, Annual Outage Analysis 2025, key findings, May 2025.
  3. Uptime Institute, Uptime Announces Annual Outage Analysis Report 2026, press release, 13 May 2026.
  4. Mordor Intelligence, Multi Vendor Support Services Market Size and Share Analysis, Growth Trends and Forecast (2026 to 2031), page updated September 2026.
  5. World Commerce & Contracting with Deloitte, The ROI of Contracting Excellence, summarized in Are organizations unlocking their full financial potential?, WorldCC, 18 August 2023.
  6. World Commerce & Contracting, Contract Management, research summary, August 2025.
  7. U.S. Energy Information Administration, Investor-owned utilities served 72% of U.S. electricity customers in 2017, Today in Energy, 2019.
  8. U.S. Environmental Protection Agency, Public Water System Service Areas, 2026.
  9. Amalgam Insights, 2024 Vendor SmartList for Telecom Expense Management, Distinguished Vendors, 2024.
  10. Capterra, ExpenseLogic reviews, 4.8 rating from 31 reviews, accessed October 2026.
  11. RadiusPoint, published client case studies: multi-location utility charges at closed locations; contract rate optimization; Fortune 100 wireless discovery and optimization; client growth from 170 to 1,200 locations.

This page provides general information about IT hardware multi-vendor support for reference purposes only. RadiusPoint does not provide IT hardware maintenance, break-fix support, or OEM coordination services. Client results described here reflect specific engagements and are not a guarantee of future savings.

pexels pixabay 236380

Utilization Management in Healthcare: Clinical Review vs. IT and Telecom Asset Utilization

cost savings1

Physicians complete an average of 40 prior authorizations a week, consuming 13 hours of physician and staff time, according to the 2025 AMA Prior Authorization Physician Survey. That’s the most visible side of utilization management in healthcare.

Utilization management in healthcare is the process health plans, review organizations and hospitals use to decide, case by case, whether a medical service is necessary and appropriate before, during or after it’s delivered.

The term has a second, unrelated meaning in hospital finance and IT: checking whether the phones, tablets, lines and circuits a health system pays for each month are actually in use. Different teams run the two, different rules govern them, and different records prove them.

RadiusPoint, a telecom expense management (TEM) firm in business since 1992, works only on the second kind, auditing telecom, wireless and utility invoices against real inventory in its ExpenseLogic platform. It doesn’t provide clinical utilization management, prior authorization or medical necessity review.

Key Takeaways

  • Clinical utilization management reviews medical necessity before care (prior authorization), during an inpatient stay (concurrent review) and after care (retrospective review).
  • Since January 1, 2026, CMS generally requires Medicare Advantage, Medicaid and CHIP payers to decide urgent prior authorization requests within 72 hours and standard ones within seven calendar days.
  • Device and line utilization review asks a billing question instead: is anyone using the phone, tablet or circuit on this month’s invoice?
  • Hospital employee turnover reached 18.5% in 2025, according to NSI Nursing Solutions, and each departure can leave a line billing.
  • In one published RadiusPoint case, a healthcare provider cut telecom expenses 26% after unused lines were verified and removed. It’s one client’s result, not an average.

The Short Version

If you need prior authorization or medical necessity review, that’s a job for a health plan or a clinical utilization management vendor; if you’re paying for devices and lines nobody uses, you need a line-by-line utilization review of the invoice.

Clinical utilization management and device utilization review answer different questions

Clinical utilization management asks whether a patient’s care is medically necessary, while device utilization review asks whether a billed line or device is in use. They share a word, not a regulator, a data source or a vendor category. The table below compares them on the points that decide who should own each one.

Point of comparison Clinical utilization management Device and line utilization review
Core question Is this care medically necessary for this patient? Is anyone using this line or device?
Who does it Health plans, their delegated review organizations, hospital review committees Telecom, IT and finance teams, often with a TEM provider
When it happens Before care, during an inpatient stay, after care Before an order, every billing cycle, and in audits of past invoices
Rules and standards CMS rules including CMS-0057-F, 42 CFR 482.30 for hospitals, voluntary NCQA accreditation Carrier contracts and internal wireless, offboarding and approval policies
Evidence used Medical records and written clinical criteria Carrier invoices and usage, the HR roster, the device and site inventory
Possible outcomes Approval, denial with a specific reason, appeal Keep, reassign, suspend or disconnect, plus billing disputes

The timing lines up: an ordering approval workflow mirrors prior authorization, the monthly usage and roster check mirrors concurrent review, and an invoice audit mirrors retrospective review. The stakes don’t. One decision governs a patient’s access to care, and the other governs what the organization pays a carrier.

How does clinical utilization management work before, during and after care?

Clinical utilization management runs in three stages: prior authorization before care, concurrent review during an inpatient stay, and retrospective review after care is billed. Each stage applies written clinical criteria to one patient’s case, and each can end in approval, a request for more information, or a denial the provider can appeal.

  • Prior authorization, also called precertification or prospective review, happens before a planned service. The payer approves the request, denies it or asks for more documentation.
  • Concurrent review happens while a patient is admitted. It checks whether continued inpatient care still meets criteria.
  • Retrospective review happens after care is delivered and billed. It confirms the care was appropriate and given at the right level.

The Institute of Medicine’s 1989 report, Controlling Costs and Changing Patient Care?, described utilization management as techniques that purchasers of health benefits use to control costs by reviewing, case by case, whether care is appropriate before it’s provided. Under 42 CFR 482.30, a hospital in Medicare and Medicaid must keep a utilization review plan run by a committee of two or more practitioners, unless a Quality Improvement Organization has assumed binding review. So one admission can be reviewed twice: by the hospital and by the patient’s health plan.

Which federal rules and standards shape utilization management in 2026?

CMS sets prior authorization deadlines for Medicare Advantage, Medicaid and CHIP payers, hospital rules require review plans, and NCQA accreditation adds voluntary standards. The CMS Interoperability and Prior Authorization final rule, CMS-0057-F, matters most this year, because its first operational deadlines took effect on January 1, 2026.

Provision What CMS-0057-F requires Compliance date
Decision timeframes 72 hours for expedited (urgent) requests and seven calendar days for standard requests; Qualified Health Plan (QHP) issuers on the Federally Facilitated Exchanges are excluded Generally January 1, 2026
Denial reasons A specific reason for every denied request Generally January 1, 2026
Public metrics Prior authorization metrics posted annually on the payer’s website First report by March 31, 2026
Prior Authorization API A FHIR-based interface for electronic requests, documentation requirements and decisions Generally January 1, 2027

The rule covers medical items and services, not drugs, and KFF notes it cut the standard response window from 14 calendar days to seven. For healthcare utilization management organizations, NCQA’s Utilization Management Accreditation is the voluntary layer. It checks quality improvement, member confidentiality, use of appropriate professionals, fair and timely decisions and appeals handling, and NCQA says more than 50 organizations hold it.

Why prior authorization draws scrutiny from physicians and policymakers

Prior authorization draws scrutiny because request volume keeps climbing, most appealed denials are overturned, and physicians link the process to delayed and abandoned care. Medicare Advantage insurers received nearly 53 million prior authorization requests in 2024, up from 49.8 million in 2023, according to a KFF analysis of data insurers report to CMS.

Insurers denied 4.1 million of those requests, or 7.7%. Only 11.5% of denials were appealed, but 80.7% of appeals were fully or partially overturned. In the 2025 AMA survey of 1,000 practicing physicians, 95% said prior authorization delays access to necessary care and 26% said it had led to a serious adverse event. About 60 insurers pledged in June 2025 to simplify the process, yet only 33% of those physicians expect a meaningful difference. The cost pressure behind it is real: CMS puts 2024 U.S. health spending at $5.3 trillion, up 7.2% and equal to 18.0% of GDP.

What does utilization review mean for hospital phones, tablets and lines?

In hospital telecom, utilization review means matching every billed device or line to a current user, site and purpose, then acting on each mismatch. It’s a cost and asset question with no clinical judgment involved, and its evidence comes from carrier invoices, the HR roster and the device inventory rather than medical records.

Workforce churn feeds the problem. The 2026 NSI National Health Care Retention and RN Staffing Report, covering 527 hospitals, put 2025 hospital employee turnover at 18.5% and found that 29.5% of new hires left within a year. Over five years, the average responding hospital turned over 106% of its workforce. Each departure that leaves a device behind keeps billing until offboarding reaches the carrier. Scale multiplies it: the American Hospital Association counts 397 U.S. health systems holding 4,157 hospitals.

That reconciliation is the only utilization work RadiusPoint does. RadiusPoint analysts compare carrier bills against an inventory of employees, devices and sites in ExpenseLogic, auditing every line item rather than a sample. RadiusPoint doesn’t offer clinical utilization management or make medical necessity decisions.

Seven checks that catch unused devices and lines before the next invoice

A health system can find unused devices and lines with seven checks, each tied to a capability the RadiusPoint team already runs inside ExpenseLogic. The checklist below lists what each check catches and which ExpenseLogic capability performs it, so you can test your own process line by line.

Check What it catches ExpenseLogic capability
1. Zero use No voice, data or text activity in the review window Zero-use device identification
2. Roster match Lines assigned to people who’ve left the organization Ex-employee line detection through HR roster reconciliation
3. Registration Numbers no current employee will claim Annual line registration
4. Ownership Smartphones, tablets and wearables with no serial number or Employee ID match Device inventory by serial number and Employee ID
5. Site status Lines and circuits billing at a closed clinic, wing or office Closed-location billing exception reports
6. Post-cancellation charges Services still billing after a disconnect order Line-item audit against contracted rates and inventory
7. Purpose Quiet lines serving fire alarm panels, elevator phones or other building systems Client-defined approval workflows on MACD (move, add, change, disconnect) tickets

Run the roster match before acting on zero use: a quiet line with a current owner needs a conversation, while one with no owner is a disconnect candidate. The method for both checks is in our walkthrough on finding and retiring zero-use mobile lines. The seventh check matters most in hospitals, where a line can sit silent for months and still be required. Our guide to healthcare telecom expense management covers how health systems tier life-safety circuits before any change.

One healthcare operator cut telecom expenses 26% by verifying which lines were in use

RadiusPoint’s published healthcare case shows a 26% reduction in telecom expenses for one provider after its unused business lines were verified and removed. It’s a single client’s result, not an average across clients, and the method behind it is what transfers to other health systems.

The client ran assisted living and nursing home sites with no prior telecom inventory or audit. RadiusPoint verified each line with test calls and, where nobody answered, site visits, then removed the dormant lines from the invoices. The audit also caught charges for services canceled years earlier. The full account is in the published healthcare telecom case study.

Two other published results are relevant. A healthcare AP and ordering automation engagement returned a 448% ROI, also a single case. And one multi-location client was paying $1,500 a month, $18,000 a year, for utilities at closed locations, the same problem on Utility Expense Management (UEM) invoices. RadiusPoint has been in expense management since 1992. Amalgam Insights named it a Distinguished Vendor in its 2024 TEM Vendor SmartList, and ExpenseLogic holds a 4.8 Capterra rating from 31 reviews.

Which utilization problem should your team solve first?

Solve the problem your team actually owns: payer and clinical teams own medical necessity review, while finance, IT and telecom teams own billed device utilization. If your question is about prior authorization, the CMS rule and your payer contracts are the place to start.

If your question is why the telecom bill doesn’t match the devices your staff carry, start with one month: pull every billing account, match each line to this month’s HR roster and flag anything billing at a closed site. Every month that check doesn’t run, the same charges post again. See the full scope of RadiusPoint’s telecom expense management services.

Frequently asked questions

Is utilization review the same thing as utilization management?

Close, but not identical. StatPearls notes that utilization management was originally called utilization review. Today, utilization review usually means the case-level check of one admission or service, while utilization management means the wider program of criteria, staff and appeals around it. Federal hospital rules at 42 CFR 482.30 still use the older term.

Who decides whether a prior authorization request gets approved?

The health plan decides, directly or through a utilization management organization working for it, using written clinical criteria. NCQA accreditation checks that appropriate professionals make those decisions. Physicians doubt it happens reliably: in the 2025 AMA survey, only 24% said medical necessity denials are consistently reviewed by appropriately qualified clinicians.

Does RadiusPoint handle prior authorization or medical necessity review?

No. RadiusPoint is a telecom, wireless and utility expense management firm, and it doesn’t provide clinical utilization management, prior authorization or medical necessity review. Its utilization work is financial: RadiusPoint analysts use ExpenseLogic to find devices, lines and services a health system still pays for after the user or site is gone.

How often should a health system review device and line usage?

Monthly for usage and HR roster matches, since both change every billing cycle, plus a yearly line registration that makes every user confirm their number. With hospital employee turnover at 18.5% in 2025, according to NSI Nursing Solutions, an annual-only check would leave up to twelve months of departures unreconciled.

References

  1. American Medical Association, AMA survey: Prior authorization reform pledge falls short with physicians (2025 AMA Prior Authorization Physician Survey), May 13, 2026.
  2. Institute of Medicine, Controlling Costs and Changing Patient Care? The Role of Utilization Management, National Academies Press, 1989.
  3. StatPearls Publishing, Utilization Management, NCBI Bookshelf, 2025.
  4. California Health Benefits Review Program, Explainer: Utilization Management: An Overview, January 2026.
  5. Code of Federal Regulations, 42 CFR 482.30, Condition of participation: Utilization review, via Cornell Legal Information Institute.
  6. Centers for Medicare and Medicaid Services, CMS Interoperability and Prior Authorization Final Rule CMS-0057-F (fact sheet), January 17, 2024.
  7. National Committee for Quality Assurance, Utilization Management Accreditation Requirements and Utilization Management Accreditation FAQs, accessed October 2026.
  8. KFF, Medicare Advantage Insurers Made Nearly 53 Million Prior Authorization Determinations in 2024, January 28, 2026.
  9. Centers for Medicare and Medicaid Services, NHE Fact Sheet (National Health Expenditure data for 2024), 2026.
  10. NSI Nursing Solutions, 2026 NSI National Health Care Retention and RN Staffing Report, March 2026.
  11. American Hospital Association, Fast Facts: U.S. Health Systems 2025 Infographic, June 2025.
  12. RadiusPoint, Healthcare Case Study: Telecom Expenses Down by 26% in Healthcare, December 2023 (linked above).
  13. RadiusPoint, AP/Ordering Process Automation Nets 448% ROI, case study, 2019.
  14. RadiusPoint, Vacant Cost Recovery: The Utility Bills Nobody Is Watching, August 2026.
  15. Amalgam Insights, 2024 Telecom Expense Management Vendor SmartList.
  16. Capterra, ExpenseLogic reviews, accessed October 2026.

This page provides general information about utilization management for reference only and isn’t clinical, regulatory or legal guidance. RadiusPoint does not provide clinical utilization management, prior authorization or medical necessity review services. Case results describe specific published RadiusPoint engagements and don’t guarantee results for other organizations.

pexels pixabay 416405 1

What is Usage Management? Detailed and updated Guide

TEM0

Usage management is the structured process of collecting, monitoring, analyzing, and controlling how resources, such as data, software, network bandwidth, or infrastructure, are consumed within an organization. 

It helps businesses gain visibility into actual usage patterns, enforce policies, and optimize allocation of assets and services. This process plays a pivotal role in enabling usage-based pricing models, quota management, and compliance enforcement. 

It also underpins cost-effective service delivery in telecom, SaaS, and cloud environments. Key elements include data collection through user activity and system logs, real-time usage monitoring, quota enforcement based on defined thresholds, policy automation to govern usage behavior, and structured reporting through dashboards or usage APIs.

How does usage management work across systems and platforms?

The usage lifecycle typically includes capture, storage, analysis, and action. Systems first capture data by logging user interactions, consumption events, or device activity. 

This data is securely stored in structured databases or cloud storage. 

Analytical tools then evaluate patterns, detect anomalies, and flag overages or inefficiencies. Based on these insights, automated systems trigger actions such as restricting access, provisioning additional resources, or sending notifications. 

In cloud services, management ensures resource efficiency and cost control. 

According to OpenMetal, 28% of public cloud spend is wasted, highlighting the necessity of real-time controls and proactive policy enforcement in cloud environments.

Why is usage management important for organizations today?

It provides a foundational layer of operational control and financial discipline. It supports resource optimization, eliminates untracked consumption, and drives billing transparency in usage-based service models. 

It is especially critical for organizations operating at scale, where decentralized systems and fragmented data can quickly lead to overspending or compliance failures. 

According to Flexera, 84% of organizations struggle to manage cloud spend, reinforcing the need for granular usage visibility, real-time monitoring, and cross-functional alignment across IT, finance, and operations.

What are the benefits of implementing usage management?

Implementing management leads to measurable gains in cost-efficiency by identifying underutilized or redundant assets. 

It enhances operational transparency, allowing stakeholders to understand usage behavior and make informed decisions. 

Accurate metering and consumption logs support predictable billing and enable companies to adopt usage-based pricing without revenue leakage. It also simplifies compliance by maintaining audit-ready records. 

StormForge reported that over $17 billion is spent annually on idle cloud resources, a figure that highlights the urgency of deploying management strategies that align resource allocation with actual demand.

What statistics highlight the need for effective usage management?

According to Statista, 30% of cloud spend is wasted, while Flexera notes that 84% of organizations struggle to control cloud costs.

PR Newswire projects $44.5 billion in cloud waste in 2025 due to disconnects between FinOps and developer teams. 

G2 Track also found that 85% of organizations fail to comply fully with software license terms. 

These figures underscore the importance of usage management as a foundational discipline for cost control, policy enforcement, and operational agility.

Which industries rely heavily on usage management?

Industries such as telecom and utilities use it for service metering, quota enforcement, and billing accuracy. 

SaaS providers and software vendors rely on it to support consumption-based pricing models. In cloud infrastructure, it facilitates real-time usage tracking and cost control. 

Manufacturing and energy sectors use it to monitor machine usage and energy flow, while healthcare and IoT ecosystems depend on it for device-level usage visibility. 

According to Chargebee, 46% of SaaS companies now offer usage-based pricing, and as Metronome reports, 78% of them adopted it in the last five years, signaling a shift toward transparent, consumption-linked billing.

What are the common types or models of this management?

This management model varies based on how resources are consumed. 

Quota-based systems allocate fixed limits to users or devices, while time-based models track usage over defined periods such as CPU hours or connection time. 

Event-based tracking monitors discrete actions like API calls or login sessions. 

Resource-based usage logs quantify consumed units such as storage space, bandwidth, or energy. Pay-as-you-go models link service costs directly to usage without long-term commitments. 

These models are often supported by embedded APIs and real-time dashboards that provide administrators with ongoing insights.

How is usage management different from utilization management?

While it focuses on tracking, billing, and policy enforcement based on actual consumption, utilization management is more about ensuring optimal use of available resources or services. 

In industries like healthcare or insurance, utilization management ensures services are necessary and cost-effective, often linked to patient outcomes or resource eligibility. 

Usage management, on the other hand, measures quantity consumed and enforces predefined policies. Though both intersect in data and analysis, their objectives and contexts differ significantly.

What are the challenges businesses face in managing usage?

Businesses often face challenges in integrating usage data from multiple, disconnected systems. 

Many organizations lack consistent usage logs, making it hard to apply quota limits or detect anomalies in real-time. User behavior can fall outside predefined policies, especially in large or decentralized teams. 

Software license non-compliance remains a costly concern. According to OpenIT, over half of organizations have incurred millions in costs from software audit failures. 

Usage tracking plays a critical role in preventing such penalties and ensuring alignment with vendor agreements.

What tools and platforms support usage management?

It is supported by various tools, including real-time dashboards, metering engines, and integration APIs. 

Dashboards allow teams to view historical and real-time consumption trends, while APIs enable automated data sharing across billing systems, CRM platforms, or financial systems. 

Cloud FinOps platforms help control infrastructure costs, and Telecom Expense Management tools offer deep usage tracking across telecom assets. Platforms like RadiusPoint’s ExpenseLogic provide full lifecycle visibility by linking usage data with billing records, contracts, and inventory, making them ideal for organizations operating in complex environments.

How does it connect with Telecom Expense Management (TEM)?

Usage management supports TEM by enabling data usage monitoring, carrier billing validation, and device-level visibility across mobile and fixed telecom assets. It automates alerts for threshold breaches and integrates consumption patterns with billing details to ensure accountability. 

RadiusPoint’s telecom expense management solution brings these capabilities together, combining real-time usage tracking with contract-level oversight. This ensures telecom services are used efficiently, billed correctly, and aligned with policy.

What are the best practices for implementing usage management?

To implement management effectively, organizations should centralize usage data across departments and platforms. 

Defining clear and enforceable policies is essential, supported by real-time alerts to flag overages or anomalies. 

Integration with billing, CRM, and contract management systems creates a seamless flow of data. Regular audits and benchmarking help identify trends and optimization opportunities. 

An effective governance framework supports consistent, scalable practices and reinforces accountability across teams.

How can small and mid-size businesses (SMBs) benefit from it?

SMBs benefit from it by avoiding over-provisioning, ensuring cost predictability, and enhancing service transparency. 

Modern SaaS-based tools offer scalable solutions without requiring significant IT overhead. Historical usage trends help with budget forecasting and vendor negotiations. 

Usage alerts prevent unnecessary consumption, while usage logs support client billing or internal reporting. 

CIOL reported that 27% of enterprises spend $500K+ annually due to license non-compliance, evidence that effective management is just as crucial for SMBs as it is for large enterprises.

What metrics or KPIs are critical in tracking usage data?

Key metrics include volume of resource consumption, cost-to-usage ratio, license quota utilization, overage percentage, and user-level activity distribution. 

These indicators help organizations understand usage patterns, manage risk, and ensure alignment with operational and financial goals. 

Regular review of these KPIs supports continuous improvement and operational efficiency.

What role do APIs play in management implementations?

APIs play a central role by enabling automated capture, retrieval, and integration of usage data. They allow systems to exchange real-time information with billing platforms, CRMs, and reporting tools. 

APIs also support extensibility, allowing developers to build custom dashboards, enforce policies dynamically, and trigger workflows based on usage thresholds. 

Their flexibility makes them foundational for modern, scalable usage management systems.

What does a successful usage management setup look like?

A successful setup features a centralized data warehouse for usage logs, role-based dashboards for various departments, and pre-configured alert thresholds. 

Policy automation tools enforce usage rules, while integrated billing systems ensure accurate invoicing. Teams should have access to actionable insights for decision-making. 

Proper documentation and change management practices support long-term success, allowing organizations to scale their usage strategies across new services or geographies.

How is usage management evolving with AI and predictive analytics?

AI and predictive analytics are transforming it by enabling systems to forecast consumption, detect irregular patterns, and optimize resource allocation. 

Machine learning models analyze historical data to predict peak periods or detect misuse. These capabilities reduce operational waste, minimize risk, and support continuous improvement. 

They are particularly valuable in fast-moving environments like cloud services, where manual oversight is insufficient to manage dynamic demand.

How does RadiusPoint help businesses with usage management?

RadiusPoint helps organizations gain control over consumption data and optimize expense accountability through its telecom expense management. It provides full-spectrum usage management capabilities that include real-time tracking, policy automation, and analytics integration. 

RadiusPoint serves eight core sectors: telecom, utilities, manufacturing, logistics, SaaS, healthcare, retail, and education, delivering tailored insights and reporting for unique needs.

Its platform links usage records with billing, contracts, and service inventories, creating an intelligent feedback loop that reduces waste and improves operational transparency. 

Finance, IT, procurement, and operations teams benefit from a centralized dashboard that supports proactive decisions and compliance enforcement. 

Whether it’s mitigating cloud waste, monitoring telecom thresholds, or managing IoT resource utilization, RadiusPoint ensures consistent visibility across services.

For companies facing rising infrastructure and software costs, RadiusPoint’s solution offers a unified approach to manage usage from a single pane of glass. To learn how ExpenseLogic fits your organization’s needs, request a demo today and discover how to unlock real-time cost control and operational efficiency.

pexels n voitkevich 6837777

What Is a Vendor Scorecard? Metrics and a Template

TEM Managed Services0

A vendor scorecard is a recurring report that rates each vendor you already use against agreed metrics, such as quality, timeliness, cost and contract compliance, so renewal and escalation decisions rest on records rather than impressions. Procurement usually owns it, finance and operations supply the data, and reviews run on a fixed cycle. Federal agencies, for example, must rate covered contractors at least annually.

For telecom, IT and utility vendors, the generic version measures the wrong things. The costly failures with carriers and utility providers show up on the invoice: a circuit billed above the contracted rate, a credit that posts months after the dispute, a disconnect that never stops the billing, a contract that renews because nobody caught the notice date. A scorecard for these vendors rates billing accuracy, dispute and credit turnaround, MACD (move, add, change, disconnect) turnaround and contract compliance, using invoices, contracts and tickets instead of the vendor’s own reports. RadiusPoint has audited carrier and utility invoices, and ExpenseLogic already holds the data such a scorecard needs.

Key takeaways

  • A vendor scorecard rates vendors you already use, not candidates you’re still choosing.
  • For carriers and utilities, score billing accuracy, dispute and credit turnaround, MACD turnaround, and contract and renewal compliance.
  • The federal model under FAR 42.1503 uses five rating levels and gives the vendor up to 14 calendar days to respond.
  • Agree weights and thresholds in writing before the first period is scored.
  • ExpenseLogic doesn’t score your vendors; it holds the audited data your team scores from.

Short version: if your scorecard can’t tell you which carrier billed above contract, which credit is overdue and which MACD order has stalled, rebuild it around invoice and contract data before your next renewal.

What Does a Vendor Scorecard Measure, and Who Uses It?

A vendor scorecard measures how well an existing vendor meets agreed standards for quality, timeliness, cost and contract compliance across a fixed review period. Procurement typically owns the format, finance and operations supply the data, and the vendor sees the results. The value is a repeatable record: the same metrics, scored the same way every period, so trends surface before a renewal forces the question.

The federal government runs one of the clearest public versions. FAR 42.1502 requires agencies to evaluate contractors on covered contracts at least annually and again when the work is completed. Under FAR 42.1503, each evaluation covers at least five factors (technical quality, cost control on non-fixed-price contracts, schedule, management or business relations, and small business subcontracting where a plan applies), and each factor gets one of five ratings with a written narrative. Agencies then draw on evaluations from within three years of completion (six for construction and architect-engineer work) when choosing future contractors.

Private-sector teams call it a vendor performance scorecard or supplier scorecard. It isn’t a selection tool. Scoring a provider before you sign is the job of a vendor evaluation questionnaire; the scorecard starts after the contract does.

What Changes When the Vendor Is a Carrier or a Utility?

When the vendor is a carrier or utility, scoring shifts from delivery and defect metrics to billing accuracy, credit turnaround, order turnaround and contract compliance. A carrier doesn’t ship a pallet late. It bills a circuit at the wrong rate, posts a credit long after the dispute, or keeps billing a line after the disconnect order. Those failures live in invoices, so that’s where scoring starts.

Generic supplier metric Carrier or utility equivalent Where the evidence lives
On-time delivery MACD turnaround, including whether billing changed with the order MACD tickets, order confirmations, the next invoice
Defect rate Billing accuracy against contracted rates, tariffs and live inventory Invoice line items, rate tables, service inventory
Price compliance Contract and renewal compliance, including notice dates Contracts, amendments, expiration and termination dates
Responsiveness Days from dispute filed to credit posted Dispute log, carrier case numbers, later invoices
Fill rate Compliance with the service level agreement (SLA) Your own trouble tickets and outage records
Invoice accuracy Missing or late bills, and charges at closed sites Missing-bill reports, location records

Regulation sets a floor for carrier bills, not a match to your contract. The FCC’s Truth-in-Billing rules, adopted in 1999 and codified at 47 CFR 64.2401, require telephone bills to describe each charge in plain language, name the provider behind it, and list a toll-free number for disputes, though some provisions exempt wireless carriers. A compliant bill can still charge the wrong rate.

Utilities add meter-level detail: each charge depends on the rate schedule, the meter and the read, so accuracy means checking every meter against its tariff or supply contract. A MACD order that completes on time but leaves the old service billing fails two metrics at once, which is why the MACD process and the next invoice belong in the same review.

A Vendor Scorecard Template for Carriers and Utilities, With the Weights Left to You

This vendor scorecard template lists the metrics, data sources and owners for carrier and utility vendors, and leaves weights to your team on purpose. Published templates often ship with preset percentages, but those reflect the publisher’s priorities, not your contracts. Your contract terms and risk tolerance should set the weights, written down before the first period is scored.

Metric What it measures Data source Who owns it Weight
Billing accuracy Charges at contracted rates, for services in your inventory Invoice line items, rate tables, inventory Finance or accounts payable Set by your team
Dispute and credit turnaround Days from dispute filing to credit on an invoice Dispute log with dates and case numbers Whoever files disputes Set by your team
MACD turnaround Days from approved order to completed change MACD tickets, the following invoice IT or telecom operations Set by your team
Service level compliance Availability and response against the signed SLA Trouble tickets, outage records IT operations Set by your team
Contract and renewal compliance Billing within contracted terms; renewals handled inside the notice period Contract records, expiration dates Procurement Set by your team
Bill completeness Missing, late or duplicate bills by account Missing-bill reports, account list Accounts payable Set by your team
Closed-site billing Charges continuing at closed locations Billing exception reports Facilities or real estate Set by your team

Score each metric on the scale below, multiply by its weight, and add the results. Give no weight to a metric without an independent source: an SLA score built from the carrier’s own uptime report measures its reporting, not its service. Score contract compliance on dates too, because the renewal notice windows in each agreement decide whether a poor score can still change the next contract.

Score From Invoices, Contracts and Tickets, Not Vendor Reports

The data behind a credible vendor scorecard comes from records the vendor doesn’t control: your invoices, your contracts and your own ticket and dispute logs. A carrier’s business review deck can add context, but it reports the carrier’s view of its own performance. When the carrier’s numbers and your invoice data disagree, the invoice is the record that costs you money.

In ExpenseLogic, those records already sit in one place, because RadiusPoint uses them to audit and manage the spend. Before the first scored period, confirm each input:

  • Every billing account is in the feed, with daily missing-bill reporting flagging invoices that didn’t arrive.
  • Contract rates are tied to service IDs through vendor contract management, so the line-item audit checks each charge against rate and inventory.
  • Expiration dates and termination fees are loaded, so contract obligation alerts fire before a renewal locks.
  • Closed-location billing exception reports are reviewed each cycle.
  • Reporting and Analytics schedules the reports by email and exports them to Excel, CSV or PDF for your scoring workbook.

The platform supplies the inputs; your team applies the weights and assigns the scores.

How Should You Rate Each Vendor So the Score Holds Up?

Rate each vendor on a fixed, written scale whose thresholds are agreed before the first review period and applied the same way to every vendor. Two reviewers reading the same dispute log should reach the same score. If they can’t, the scale is too vague, and a carrier will challenge it at renewal.

The five levels in FAR Table 42-1 work well because each is defined by evidence. Agree the numeric cutoffs for each level before scoring starts.

Rating FAR Table 42-1 (paraphrased) How it might read for a carrier or utility
Exceptional Meets requirements and exceeds them, with highly effective fixes Bills match contract; the vendor credits its own errors before you dispute
Very good Meets requirements and exceeds some, with effective fixes Occasional errors, credited without escalation
Satisfactory Meets requirements; minor problems, satisfactorily corrected Errors credited once disputed, within the agreed turnaround
Marginal Misses some requirements; serious problem, no corrective action identified A recurring error or overdue credits with no committed fix
Unsatisfactory Misses most requirements; timely recovery unlikely Errors across accounts and no credible correction plan

Two FAR rating rules transfer well. Plus or minus signs can flag a trend too small to change the rating. And a marginal rating should cite the notice that told the vendor about the problem, so no carrier is marked down for something nobody raised with it.

Three Moments When a Vendor Scorecard Earns Its Keep

A vendor scorecard earns its keep at three moments: contract renewal, dispute escalation and the first months with a new carrier or utility provider. Between them, a steady review cycle keeps the record current. Set the cycle by spend and risk and keep it fixed; federal practice treats annual review as the minimum, not the target.

At renewal, the history replaces “they’ve been fine” with a dated record, if it arrives before the notice period closes. In a dispute, the same error across consecutive periods is a pattern, and the turnaround metric proves it, which supports escalation and efforts to recover telecom refunds and credits beyond the latest invoice. With a new provider, agree metrics, sources and thresholds in writing at contract start, so the baseline is never in dispute.

Does a Vendor Scorecard Help With Audits and Regulatory Reviews?

A vendor scorecard helps with audits because each score ties to a dated record, but on its own it doesn’t satisfy any specific regulatory requirement. Auditors want to see that vendors were monitored, problems were raised, and responses were recorded. A scorecard built from invoices and dispute logs shows all three without anyone rebuilding the history from email.

Banking shows how regulators frame this oversight. On June 6, 2023, the Federal Reserve Board, the Federal Deposit Insurance Corporation (FDIC) and the Office of the Comptroller of the Currency (OCC) issued the Interagency Guidance on Third-Party Relationships: Risk Management (88 FR 37920, June 9, 2023). It sets out a five-stage life cycle (planning, due diligence and selection, contract negotiation, ongoing monitoring, and termination) and expects monitoring scaled to each relationship’s risk and complexity. It replaced the FDIC’s 2008 guidance and the Federal Reserve’s and OCC’s 2013 guidance, and the agencies state it imposes no new requirements. A scorecard is evidence of monitoring, not a compliance checkbox.

How RadiusPoint and ExpenseLogic Supply the Data Behind Your Scorecard

RadiusPoint and ExpenseLogic supply the audited invoice, contract, MACD and dispute data a carrier or utility scorecard depends on, while your team owns the scoring. ExpenseLogic holds the records, and RadiusPoint’s analysts audit invoices line by line, file and chase disputes, and track contract obligations. You set the metrics, weights and thresholds, which suits a procurement team facing dozens of vendors and contracts that expire silently.

ExpenseLogic covers telecom expense management (TEM), wireless and Utility Expense Management (UEM) in one platform, so carriers and utilities can be scored from the same kind of record.

The audit and contract work behind those records produces results of its own. A Fortune 100 manufacturer recovered $450K in telecom refunds in its first year. Contract rate optimization saved one client $120,000 a year, eliminating unneeded toll-free numbers saved $18,000 a year, and inventory management recovered $174K in re-credits. An elevator company cut monthly waste expenditure by 28%, and RadiusPoint has supported a client’s growth from 170 to 1,200 locations.

Amalgam Insights named it a Distinguished Vendor in its 2024 TEM Vendor SmartList, and ExpenseLogic holds a 4.8 rating from 31 reviews on Capterra.

Every unscored billing cycle repeats the same errors at the same rates, with no record to bring to renewal. Request a demo of ExpenseLogic to see the data your scorecard would draw on.

Frequently Asked Questions

What role does vendor feedback play in a scorecard review?

Vendor feedback is the vendor’s documented response to its scores: corrections, context and a corrective action plan. Share the draft scorecard, give the carrier a fixed window to answer with invoice or ticket evidence, and record its response next to the score. The federal model works this way: contractors get up to 14 calendar days to comment, and disagreements go to a reviewer above the contracting officer.

Can a vendor scorecard replace a telecom audit?

No. A scorecard tracks performance over time and points to problems, while a line-item telecom audit reconciles every charge against contract and inventory to find specific overbilling. The two feed each other: audit findings become billing accuracy scores, and a falling score tells you which carrier to audit next. The scorecard shows where to look; the audit shows what’s recoverable.

Is a spreadsheet enough to run a vendor scorecard?

A spreadsheet works when the vendor list is short enough that one person can rebuild the inputs each cycle. It breaks when invoice, contract and dispute data live in separate places and every review starts by reassembling them. The scoring math stays simple at any size; clean inputs are the real work.

Is a vendor scorecard the same as a vendor risk scorecard?

No. A vendor scorecard rates how well a vendor performs under its contract, using your invoices, tickets and contract records. A vendor risk scorecard usually means a cybersecurity or financial risk rating of a third party, often produced by an outside ratings service. The two answer different questions and draw on different data.

References

  • Federal Acquisition Regulation, 48 CFR 42.1502, Policy. FAC 2026-01, effective March 13, 2026. Acquisition.gov.
  • Federal Acquisition Regulation, 48 CFR 42.1503, Procedures, and Table 42-1, Evaluation Rating Definitions. FAC 2026-01, effective March 13, 2026. Acquisition.gov.
  • Federal Reserve Board, FDIC and OCC. Interagency Guidance on Third-Party Relationships: Risk Management. 88 FR 37920, June 9, 2023.
  • Federal Reserve Board. SR 23-4, Interagency Guidance on Third-Party Relationships: Risk Management. June 7, 2023.
  • Federal Communications Commission. 47 CFR 64.2400 and 64.2401, Truth-in-Billing Requirements for Common Carriers. eCFR.
  • Federal Communications Commission. Truth-in-Billing Policy. FCC.gov, 2025.
  • Federal Communications Commission, Common Carrier Bureau. Truth-in-Billing and Billing Format, Order, DA 00-893, CC Docket No. 98-170. 2000.
  • Amalgam Insights. Telecom Expense Management Vendor SmartList, 2024.
  • Capterra. ExpenseLogic reviews, 4.8 from 31 reviews.
  • RadiusPoint. Client case results (telecom refunds, contract rate optimization, toll-free numbers, inventory re-credits, waste reduction, location growth).

This article provides general information about vendor scorecard practices and isn’t legal, compliance, audit or financial advice for any organization. Set metrics, weights and thresholds to match your own contracts, risk tolerance and regulatory obligations.

image 2024 12 30T16 49 24 599Z

Expense Management Services

Services0

Tailored Solutions That Maximize Value and Meet Your Budget

We understand that finding the right service provider means balancing your goals with your budget. That’s why we specialize in creating fully customized solutions designed to deliver maximum value for every dollar spent. Our pricing reflects the care and expertise we put into every project—no cookie-cutter services here.

Your needs and custom solution drive the pricing model with the monthly cost aligning with the annual expense. Costs can be applied per invoice processed monthly, an hourly fee for project-based tasks, or help desk tasks.

What Can You Expect to Invest?

Our services are as unique as your needs, and pricing varies based on factors like the number of locations and invoices to be managed, the annual dollar volume, and the level of services required. We provide services at three different levels but can tailor a service to meet your specific needs:

  1. Host & Load
    • Receiving and loading invoices monthly
    • Missing bill retrieval
  2. Basic
    • All Host & Load services
    • Invoice payment
    • GL Interface file
    • Accrual file
  3. Enhanced
    • All Host & Load and Basic services
    • Invoice audit and reconciliation
    • Contract management
    • Access to our Help Desk ticketing module
    • Asset Management module

Clients provide their invoice information and desired services, and we create a tailored solution and pricing. We’re here to help you explore the right options for your goals and budget requirements.

A Few of the Driving Factors:

  • Type of services: Telecom, IT, Wireless, or Utilities
  • Number of locations: How many locations will we be managing?
  • Annual dollar volume: The monthly fee is based on a percentage of your telecom and IT spend.
  • Number of utility invoices: How many invoices will we receive and process?
  • Wireless devices: How many devices will be under management?

Lastly, think about what services you want to take off your plate. Many clients need us to simply load the invoices and manage daily tasks like auditing, reconciling, and paying invoices. Enhanced Services allow you and your team to focus on core business tasks while we ensure all invoices are paid on time.

Why Choose Us?

Bringing unique value to the partnership is our key focus, and we differentiate our services, software, and problem-solving team in several ways:

  • ExpenseLogic Software: Our in-house developed and maintained software can be tailored to any Business Intelligence needs.
    • Combines eight software packages into one: accounting, expense audit, help desk, asset management, contract management, document management, wireless management, and reporting analytics.
    • Enables seamless collaboration across finance, operations, facilities, and real estate departments.
  • Invoice Reconciliation: We handle incorrect billing by disputing errors and recovering overcharges, shouldering the burden for you.
  • High ROI: Our clients achieve an average ROI of over 400%.
  • Effortless Onboarding: Our team manages vendor transitions and invoice setup seamlessly. Clients frequently commend our efficiency during this phase.
  • Proven Experience: Over 33 years of expertise with continuous innovation. Our software is now in its 10th release.
  • Exceptional Retention: Client retention exceeds 98% over the past six years, with many clients partnering with us for nearly two decades.

What’s Included in Your Investment?

  • Custom-Tailored Solutions: We develop solutions specifically aligned with your goals and operational needs.
  • Dedicated Problem-Solving Staff: Our team collaborates closely with your organization to address challenges and implement effective strategies.
  • Seamless Collaboration: You’ll work directly with an experienced Account Team committed to understanding your business.
  • Exceptional Post-Project Support: We remain available to answer questions, provide guidance, and ensure sustained success after implementation.
  • Transparent Processes: We keep you informed every step of the way, ensuring clarity and confidence in the services provided.
  • Focus on Your Business Needs: Our staff takes pride in proactively solving problems, offering innovative solutions, and adapting to the unique demands of your business environment.

Provide us with the services that are needed, and we will tailor a solution and pricing to meet those needs.

Client Testimonials

Our clients consistently praise our expertise, efficiency, and ability to deliver meaningful results. Here are just a few success stories:

Efficient Setup in 4 Weeks

“I cannot speak highly enough about your team. The RP team supported our team through managing the challenging vendor base, providing great guidance and all the necessary tools required for success. The implementation was FAST but also successful. Most implementations that go as fast as this have hiccups, and we had very few items to clean up after go live.”

Kristen, Director of Accounts Payable, 400-Location Healthcare Organization

Ease of Use

“The features provided are very helpful and the system is very user-friendly.”

Debbie, Director of Accounts Payable, 1200-Location Nationwide Retailer

Time-Saving

“I have been more organized than ever. My time is precious, and countless hours have been saved.”

Samantha, Operations, 200-Location Financial Services Firm

Improved Vendor Management

“RadiusPoint has helped us streamline our vendor relationships and keep our expenses in check. Their team’s dedication to resolving disputes and ensuring accurate billing has saved us both time and money.”

Michael, CFO, Regional IT Services Firm

Scalable Solutions

“As we expanded, RadiusPoint adapted seamlessly to our growing needs. Their tailored approach and comprehensive software have been invaluable.”

Lisa, COO, Multi-State Retailer

These testimonials demonstrate the trust our clients place in us and the results we deliver. Whether you need help managing a few locations or scaling solutions across a nationwide network, we’re here to help.

Ready to Learn More? Let’s Talk!

Contact us today for a no-pressure consultation. We’ll explore your needs and provide a customized plan that works for you.  Visit us at Contact Us or Schedule a Discovery Call

iStock 1347032235

2024 Gartner press release

News0

For immediate release:

Orlando, FL November 27, 2024 – The 2024 Gartner Market Guide for Telecom Expense Management Services recognizes RadiusPoint as a Representative Vendor, affirming its position as a premier single-source SaaS platform and BPO service provider in the TEM services sector, a testament to its over three decades of market presence.

Gartner states, “To be commercially and operationally efficient, enterprises must eliminate service redundancy and ensure that all services add value to the business. TEM providers are offering program management capabilities to oversee fragmented estates spanning multiple carriers, lines of business, contracts and internal organizational units.”

When sourcing a TEM vendor, Gartner recommends best practices, “To increase the chances of a successful engagement, it is critical to conduct due diligence regarding what the provider will deliver and how that will be achieved.”

As a result of the ongoing advancements in the IT market, RadiusPoint is consistently enhancing the features and functionalities of its proprietary software, ExpenseLogic. RadiusPoint is committed to providing business intelligence, and ExpenseLogic empowers businesses to attain a favorable return on investment. Moreover, it helps transform the complexity of telecom management into streamlined efficiency while optimizing and reducing communication expenses, including IoT, mobile, fixed line, and cloud devices, as well as utility costs.

The success of businesses hinges on the precision and meticulous attention to detail required for technology and utility invoices and inventory every month. All financial transactions must be meticulously documented and systematically monitored, providing easy access for auditing and reporting through a unified platform. Alongside pinpointing costly billing errors, RadiusPoint’s exclusive software, ExpenseLogic, grants clients access to a range of Internet billing options that can be efficiently processed and managed within its IoT section. The flexibility of their service delivery enables RadiusPoint to adapt and scale as required.

“We are thankful to be included in Gartner’s Market Guide as a Representative Vendor, as we believe their key findings and recommendations are highly valued for enterprises of all sizes. Our flexibility and automation allow us to move faster and hold hands easier, said Sharon Watkins, CEO of RadiusPoint. “We believe Gartner provides clear evidence for those in the IT arena to make informed business decisions so you can focus on your core business strategy.”

Earning a place in the Gartner 2024 Market Guide for Telecom Expense Management Services represents a significant milestone for RadiusPoint and marks the sixth year of inclusion in this guide.

Subscribers to Gartner can find the 2024 Market Guide for Telecom Expense Management Services here.

Disclaimer: Gartner does not endorse any vendor, product, or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.

About RadiusPoint

Established in 1992, RadiusPoint is a prominent provider of services encompassing Telecom Expense Management (TEM), Utility Expense Management (UEM), Wireless Expense Management (WEM), and Mobile Device Management (MDM). Located at its corporate headquarters in Orlando, Florida, RadiusPoint offers a comprehensive range of business and technology solutions, all aimed at enhancing the global business performance of its clients.

Vector illustration about caring for and saving the World

The Role of Utility Expense Management in Sustainability

UEM, UEM Managed Services, UEM page6

Utility expense management supports sustainability by giving organizations the granular spend data ESG reporting actually requires: usage by meter, by location and by vendor, which is exactly the data most companies lack when a board or investor asks for Scope 3 emissions figures. The same audit that finds billing errors also finds the vacant-site charges and inefficient usage patterns that inflate an organization’s environmental footprint.

Important Points Explained Ahead

  • ESG reporting requires granular spend visibility, by vendor, by category, by location, that most organizations do not have without centralized utility expense management.
  • Vacant-site utility billing, meters still running at closed locations, inflates both cost and reported emissions data simultaneously.
  • Roughly two-thirds of the average company’s ESG footprint sits with its suppliers rather than its own operations, which is why vendor-level utility data matters for credible reporting.
  • Utility expense management and sustainability reporting are not separate initiatives when the underlying data source, contracted vendor invoices, is the same for both.
  • RadiusPoint, a certified women-owned business, also contributes directly to the social pillar of ESG for clients whose procurement spend counts toward supplier diversity targets.

Short version: most organizations trying to report ESG data discover the real gap is not intent, it is spend visibility. Utility expense management closes exactly that gap.

Why ESG Reporting Depends on Utility Spend Data

ESG reporting requires centralized visibility into where every utility dollar goes, by vendor, by category, by location and by cost center, and without that foundation, reporting becomes guesswork rather than governance. Roughly two-thirds of the average company’s environmental, social and governance footprint sits with its suppliers, not within its own operations, which means vendor-level data is not optional context, it is the majority of the picture.

A meaningful share of organizations required to report Scope 3 emissions, which are embedded across the entire supplier value chain, do not have centralized visibility into operational spend at the granularity that credible reporting requires. Utility invoices arrive from dozens of providers across dozens of locations, and none of that shows up in a purchase order system unless someone specifically consolidates it.

Where Utility Waste and Emissions Waste Overlap

Vacant-site utility billing is the clearest example of where cost waste and emissions waste are the same problem measured two different ways. When a location closes or a tenant vacates, utility accounts frequently remain active, generating both unnecessary charges and unnecessary reported consumption that has nothing to do with actual business activity.

Inefficient usage patterns work the same way: a facility running HVAC or lighting beyond actual occupancy needs shows up as both a cost line item and an emissions line item, and an audit built to catch one catches the other automatically, since they share the same underlying meter data.

What Effective Utility Expense Management for Sustainability Looks Like

  • Regular audits of utility bills, meter readings and consumption patterns to identify inefficiency and vacant-site billing before it compounds.
  • Centralized spend visibility across every vendor, location and cost center, feeding both financial reporting and ESG reporting from one data source.
  • Vendor-level ESG documentation that supports supplier scorecards and due diligence requirements, not just cost tracking in isolation.
  • Clear targets and KPIs, such as spend visibility coverage and zero-use asset rate, tracked over time rather than measured once a year.

How RadiusPoint Supports ESG-Aligned Utility Expense Management

RadiusPoint delivers the spend visibility, vendor accountability and cost optimization that ESG procurement strategies require through utility expense management, consolidating utility, telecom and IT expense tracking by vendor, by meter number and by location inside ExpenseLogic. Line-item audits across utility accounts catch the vacant-site billing and inefficient usage patterns that distort both financial and emissions reporting at once, rather than treating cost recovery and sustainability reporting as separate projects with separate data.

As a certified women-owned business operating since 1992, RadiusPoint also contributes directly to the social pillar of ESG: procurement dollars a client spends on RadiusPoint services count toward supplier diversity targets, which is a documented benefit alongside the spend visibility itself. Organizations looking to recover vacant-site waste specifically can see the pattern in more detail in how companies recover telecom refunds and credits from carriers, which covers the same zero-use principle applied to telecom rather than utility accounts.

Frequently Asked Questions

Does utility expense management directly reduce a company’s carbon footprint?
It reduces waste, unused or inefficient consumption, which lowers both cost and reported emissions together. It does not replace dedicated energy efficiency upgrades or renewable sourcing, but it removes the waste that distorts what those investments are actually measured against.

Why do vacant-site utility charges matter for ESG reporting specifically?
A closed location that keeps generating utility charges also keeps generating reported consumption tied to no actual business activity, which inflates emissions figures the same way it inflates cost. Catching one catches the other.

Is this the same process as a regular telecom or utility audit?
The audit mechanics are the same, invoice against contract against actual usage, but the output serves two purposes at once: cost recovery and ESG-grade spend data, rather than cost recovery alone.

How does supplier diversity spend factor into ESG reporting?
Procurement spent with a certified women-owned or minority-owned vendor counts toward an organization’s supplier diversity targets, which is typically tracked under the social pillar of ESG reporting alongside environmental data.

References

  • RadiusPoint client engagement data, utility expense management and ESG procurement, 1992 to present

Related Articles

This page provides general information about the relationship between utility expense management and ESG reporting and is not sustainability accounting or compliance guidance.

Checklist concept. Businessman use smartphone

Factors That Impede Your Inventory Efforts

Solutions - TEM, TEM, TEM Managed Services, TEM page2

Factors That Impede Your Inventory Efforts

Creating and maintaining an inventory of your telecommunications services, invoices, and vendors is a substantial undertaking that demands consistent attention to detail. Ensuring the cleanliness and accuracy of this inventory is a challenging task, often requiring dedicated daily efforts. Engaging the services of a Telecom Expense Management (TEM) company is essential in effectively managing these tasks.

Many organizations opt to outsource the periodic inventory assessment of their telecom services and invoices. While some may view this as a sporadic necessity, often with a minimal financial benefit, a more strategic approach suggests otherwise. Rather than periodic assessments, an audit encompassing a comprehensive inventory conducted once, followed by regular maintenance, offers a more pragmatic solution.

The practicality of maintaining a clean inventory on an ongoing basis is often hindered by time constraints within most companies. However, partnering with a reputable TEM provider enables the execution of this task every month. This proactive approach not only mitigates the risks of overbilling but also streamlines the recovery process for any erroneous charges. Additionally, any recovered funds resulting from the initial audit can be efficiently managed and shared, maximizing overall savings and efficiency.

Challenges in Maintaining an Accurate Inventory of Telecom Services

Many factors contribute to an organization needing help maintaining an accurate inventory.

  • Absence of Corporate Contracts: When corporate contracts are lacking, employees may independently enter into agreements, resulting in higher service costs.
  • Decentralized Spending: This occurs when employees make equipment purchases without organizational oversight, leading to inefficiencies.
  • Inaccurate Inventory: Without proper tracking of telecom and IT services at each location and for each employee, overspending is likely due to duplicate or unnecessary services.

Addressing these factors is crucial for effective inventory management of telecom services. Implementing corporate policies and contracts can help control spending. Engaging a reputable Telecom Expense Management (TEM) company is the initial step in assessing service distribution through a comprehensive Inventory and Audit. This process necessitates a thorough examination of services beyond superficial refunds, providing detailed descriptions of phone or circuit numbers, monthly charges, service types, and features.

Enhancing Cost Reduction Strategies with Comprehensive TEM Solutions

Upon establishing an accurate inventory, a Telecom Expense Management (TEM) system empowers organizations to consistently drive cost reductions by offering comprehensive visibility into their communication ecosystem and invoice lifecycles. Centralizing all telecom-related data in a unified repository, accompanied by robust reporting tools, facilitates precise cost assessments, aids in identifying and disputing billing discrepancies, streamlines contract management including contract imaging and auditing, and uncovers optimization opportunities. Additionally, capacity planning and call accounting functionalities mitigate resource wastage within the network.

This goes beyond just telecom. A good TEM vendor will provide a comprehensive cost reduction management strategy that includes both telecom and IT, managing the complete communications lifecycle. The accuracy behind these transactions is vital to the overall efficacy of the organization.

Steps to Maintain a Clean Inventory

Keeping the inventory clean will be affected by the following:

  • Monthly services being added.
  • Monthly services being disconnected.
  • Employees moving to different departments, being hired or terminated.
  • Vendor’s changes in monthly fees.

To maintain a clean inventory every month, it is imperative to establish an order process that fosters transparency throughout the organization. Integration of a Help Desk module within the TEM provider’s software is instrumental in capturing all moves, additions, changes, or disconnects effectively. This ensures a seamless transition of new invoices to accounting without delay for coding, thereby preventing overpayment for previously disconnected services.

The next critical step in maintaining inventory accuracy is invoice and service validation. Conducting a monthly audit of each invoice and charge is essential for any TEM company. This line-item audit enables prompt identification of overcharges and provides an efficient mechanism to notify vendors for dispute and recovery. Rigorous tracking of disputes to ensure proper crediting on invoices is paramount in the recovery process facilitated by TEM services.

Optimizing Inventory Accuracy

Maintaining the accuracy of your monthly inventory relies heavily on verifying it against the established baseline inventory. A reputable TEM provider should offer validation services with select telecom vendors, enabling swift identification and rectification of discrepancies to prevent recurring overcharges on subsequent invoices.

Leveraging its proprietary SAAS platform, ExpenseLogic, RadiusPoint facilitates the creation of a concise list of invoices and services for monthly validation against the baseline inventory. This validation process provides organizations with a clear overview of services at each location, streamlining interactions with telecom vendors and pinpointing opportunities for cost reduction by identifying unnecessary services. Partnering with the right TEM provider can significantly save time, money, and resources while empowering internal teams to take control of expenses.

Hundred dollars on fishing hook

Diving Into Your Trash

News4

Waste management stands as a sizable industry that is essential for every company. In the United States alone, a staggering 624,700 metric tons of trash get discarded daily, incurring an annual expense of approximately $11 billion. Businesses shoulder a substantial 80% of these expenses. Across the board, companies are actively seeking strategies to curtail costs while simultaneously minimizing waste generation and maximizing recycling opportunities wherever feasible.

Invoices and Fees

The initial phase of cost reduction in waste management involves scrutinizing usage patterns and existing services. Numerous companies grapple with expensive monthly waste services, often burdened by additional charges appended to their regular service bills. These fees often include:

  • Management fees
  • Environmental fees
  • Gas surcharge fees
  • Lock fees
  • Extra Pick-up fees
  • Contamination fees
  • Overage fees
  • Locked gate fees

By comprehending the invoice details and extra fees, you can effectively optimize your cost savings.

Questions to Ask

Some of the above fees can be eliminated or negotiated just by asking the right questions including:

  • Do we need a separate bin for environmental waste? This could involve quick-service restaurants discarding spoiled food or spent grease.
  • Can we recycle cardboard, plastic, and metal? Breaking down boxes for recycling might save both money and the environment.
  • Is there a vendor we can use to collect scrap metal? This move could cut costs for larger roll-off bins and potentially lead to rebates.
  • Are any bins situated behind locked gates? If trash collection is hindered due to inaccessibility, expect additional fees. To avoid this, place bins outside locked areas or coordinate gate access on pickup days.
  • Are extra pickup fees a routine on your invoices? A quick review of the invoice can help resolve this by adjusting bin size or pickup frequency.
  • Is there a corporate contract governing waste services? Ensure your team is aware of this contract to benefit from agreed-upon rates when ordering services.

Given the array of questions, it’s evident that most companies will require support in overseeing trash invoices and managing multiple service providers. Generating detailed, precise information crucial for optimal business decisions demands dedicated time and meticulous attention to detail from a skilled team.

Problems with Billing Complexity

The billing intricacies present a convoluted mix of charges that necessitate monthly and long-term analysis to pinpoint the most optimal services at the most favorable prices. Monthly invoices might vary, with additional charges appearing one month and none the next, leading to potential confusion. It’s crucial to meticulously identify each charge on the invoice every month to ensure informed business decisions for each location.

Vendors contribute to this complexity by offering multiple trash haulers within a single area. This approach proves more advantageous than having only one hauler since multiple options enable bidding and price competition. However, managing these multiple vendors requires a dedicated effort and a specific finesse to navigate pricing and negotiate contract terms effectively.

Optimization Solutions with RadiusPoint

Having a partner who can break down the invoice monthly is critical to effectively managing your trash or waste services and meeting your sustainability goals.  RadiusPoint’s Waste Optimization process involves a deep dive into the waste invoices and current business programs and policies to provide a multi-point approach to managing waste services.  This inventory and audit process delivers an environmentally responsible waste management program that assists in reaching waste initiatives and provides unmatched value.

RadiusPoint’s optimization involves investigating services with the current vendor and determining best practices to provide a cost-saving program to our clients. Many multi-location organizations have ordered services as needed with no thought given to contract terms, bin size, or the frequency of pick-up.  All of these factors determine the monthly cost and could result in huge savings if managed with cost savings, efficiency, and program goals in mind.

During our inventory and audit of the waste services, RadiusPoint would:

  • Obtain a copy of the vendor’s current contract.
  • Validate the contract rates against the current invoice.
  • Comparison of services across all sites for any anomalies.
  • Identifying any overage charges or other charges beyond the normal pick-up charges.
  • Identifying better rates for those locations not under contract.
  • Identifying better rates and possible early termination penalties, if applicable, for those locations under contract.
  • Identify and recommend service changes to eliminate overage charges.
  • Provided consolidated report for Request for Proposal (RFP).
  • Provide analysis once the RFP is returned to show savings.
  • Assist with contract negotiations for each contract or global contract.
  • Assist with issues that arise at the location during the term of the agreement.

Once the inventory and audit is complete, RadiusPoint employs our exclusive software, ExpenseLogic, to handle and settle the monthly invoice. Simultaneously, continued auditing is conducted to guarantee precise billing according to contracted rates.

Connect with us to learn how RadiusPoint will support you in achieving your business’s waste service savings goals.

A close up of a printing factory management team

Why Companies Use a Managed Mobility Service Provider

Managed Mobility Services2

A managed mobility service provider centralizes device procurement, carrier billing, inventory control and lifecycle management across an organization’s mobile fleet, replacing fragmented, department-by-department mobile spend with one accountable process. Companies typically turn to this model once device counts and carrier relationships outgrow what an internal IT or procurement team can track manually.

Important Points Explained Ahead

  • Managed mobility services cover device procurement, provisioning, inventory control, carrier billing audit and lifecycle management, not endpoint security software.
  • Zero-use mobile lines, devices assigned to employees who left or roles that no longer exist, are one of the most reliable sources of recoverable savings in any mobile fleet.
  • Reducing total cost of ownership comes from negotiated carrier rates, eliminated waste and reduced administrative overhead, not from any single tactic alone.
  • Scalability matters because mobile fleets rarely stay static; a provider needs to handle growth, consolidation and M&A-driven device changes without rebuilding the process each time.
  • RadiusPoint’s Managed Mobility Solution ties device inventory directly to billing data, so a line that should have been disconnected shows up as a finding, not a guess.

Short version: the case for a managed mobility provider is not about adding a vendor, it is about consolidating a mobile fleet that has already outgrown ad hoc, department-level tracking.

Why Mobile Fleets Outgrow Manual Management

Device procurement, provisioning, carrier billing and support each carry their own process, and once an organization crosses a few hundred devices, tracking all of it manually starts producing the exact blind spots a managed provider is built to close. Without a centralized system, most companies lose visibility into which devices are active, which are still billing after an employee departs, and which carrier plans no longer match actual usage.

The complexity compounds with growth: new locations, acquisitions and remote hiring all add devices and carrier relationships faster than a manual spreadsheet process can keep up with, which is exactly when the gap between what is billed and what is actually in use starts to widen.

What a Managed Mobility Provider Actually Does

Function What it addresses
Device procurement and provisioning Consistent ordering and setup instead of ad hoc, department-level purchasing
Carrier billing audit Charges checked against contracted rates and actual usage, line by line
Inventory and lifecycle tracking Every device tied to an employee, location and status, not a guess
Zero-use line identification Lines still billing after an employee leaves or a role is eliminated
Contract negotiation support Rates benchmarked and renegotiated as the fleet and market change

This is a cost, inventory and vendor management discipline, not an endpoint security service. Organizations needing device encryption, mobile threat defense or two-factor authentication enforcement need a dedicated mobile device management (MDM) or security vendor working alongside the mobility expense provider, not instead of it.

Where the Cost Savings Actually Come From

Reducing total cost of ownership on a mobile fleet comes from three compounding sources: negotiated carrier rates that reflect actual volume and usage, elimination of zero-use lines and devices that keep billing after they stop being needed, and reduced administrative overhead from no longer tracking procurement and billing manually across departments. None of these three sources works in isolation as well as it works combined.

Zero-use lines specifically tend to be the most reliably recoverable finding in a first mobility audit, since a device assigned to someone who left the company continues billing indefinitely until someone specifically checks the assignment against current headcount. That gap is invisible in a standard invoice review and only surfaces once inventory and billing data are reconciled against each other.

What to Look For in a Managed Mobility Provider

Look for a provider with a documented track record managing mobile fleets at a comparable scale, not just a general telecom or IT vendor extending into mobility as an afterthought. A comprehensive service offering, device management, carrier billing audit and expense reporting together, matters more than any single feature, since gaps between these functions are exactly where waste hides.

Scalability and flexibility matter as much as current fit, since a mobile fleet rarely stays the same size, and a provider that cannot absorb growth, consolidation or M&A-driven device changes without a full process rebuild will become a bottleneck at the worst possible time.

How RadiusPoint’s Managed Mobility Solution Works

RadiusPoint’s Managed Mobility Solution ties device inventory directly to carrier billing data inside ExpenseLogic, so a line that should have been disconnected surfaces as a specific, dollar-quantified finding rather than a general impression that something might be wrong. This runs on the same audit discipline RadiusPoint applies across telecom expense management generally, extended to mobile-specific billing patterns.

Organizations evaluating whether to bring mobility management in-house or outsource it can see the questions worth asking in questions to ask a TEM provider before you sign, most of which apply directly to a mobility-specific evaluation as well.

Frequently Asked Questions

Does a managed mobility provider handle device security?
Not directly. Managed mobility services cover procurement, billing, inventory and lifecycle management. Device encryption, threat defense and access control require a dedicated MDM or security vendor working alongside the mobility expense provider.

How many devices does a company need before a managed provider makes sense?
There is no fixed threshold, but organizations managing more than a couple hundred devices across multiple carriers typically find manual tracking starts missing zero-use lines and billing errors that a centralized system would catch.

What is the fastest way to find out how much a mobile fleet is overpaying?
Reconciling current device inventory against carrier billing data is the direct way to find it, since that comparison is what surfaces zero-use lines and rate mismatches fastest.

Can managed mobility services scale with company growth or M&A activity?
Yes, when the provider is built for it. Ask specifically how a provider handles fleet changes from new locations or acquisitions before signing, since this is where less scalable providers tend to fall behind.

References

  • RadiusPoint client engagement data, managed mobility services, 1992 to present

Related Articles

This page describes RadiusPoint’s managed mobility expense and inventory services. RadiusPoint does not provide device security, encryption, or mobile threat defense software.

Cropped shot of a garbage collection team

Waste Services Case Study: 28% Reduction in Trash Spend

Case Study, cost savings2

28% Reduction in Trash Spend

Trimming expenses on waste management serves as the initial step in an organization’s sustainability journey. A prominent elevator company operating worldwide successfully slashed its monthly waste expenditure by 28%. Additionally, by securing a corporate contract, they paved the way for greater savings across their new locations, fortifying their commitment to sustainability.

Issues

Our client grappled with numerous challenges in its billing and services. Upon conducting an initial review, it became evident that over 40 locations had individually inked contracts with local waste haulers. Consequently, these contracts staggered in expiration, often incurring hefty early termination fees. This complexity rendered negotiating a unified corporate contract unfeasible within the initial twelve months of gaining contract and service visibility.

Solution

To tackle these issues, the organization teamed up with RadiusPoint. Collaborating on bill processing and payment services for their monthly waste invoices, RadiusPoint unearthed a route toward cost reduction during the standard optimization process.

RadiusPoint’s optimization process delved into scrutinizing services provided by the existing vendor, aiming to uncover contractual obligations and service specifics. Numerous locations had ordered services sporadically without considering contract terms, bin sizes, or pickup frequency. RadiusPoint conducted a comprehensive analysis across the organization, tailoring services to match the office types and specific service requirements to ensure an appropriate fit.

During our inventory and audit of the waste services, RadiusPoint:

  • Obtained a copy of the vendor’s current contract.
  • Validated the contract rates against the current invoice.
  • Compared services across all sites for any anomalies.
  • Identified overage charges or other charges beyond the normal pick-up charges.
  • Identified better rates for those locations not under contract.
  • Identified better rates and possible early termination penalties, if applicable, for those locations under contract
  • Recommend service changes to eliminate overage charges.
  • Provided consolidated report for Request for Proposal (RFP).
  • Provided analysis once RFP is returned to show savings.
  • Assisted with contract negotiations for each contract or global contract.
  • Managed the transition project.
  • Assisted with issues that arose at the location during the term of the agreement.

Results

Partnering with RadiusPoint empowered the client to leverage our exclusive software, ExpenseLogic. This tool facilitated the seamless processing and payment of monthly invoices while concurrently conducting an audit to guarantee precise billing per contracted rates. This meticulous approach culminated in an impressive 28% decrease in monthly waste expenses. Embracing transparency in management paves the way for astute business choices, fostering cost-effectiveness, operational efficiency, and the achievement of sustainability objectives. Entrust RadiusPoint to guide you toward attaining your business savings targets, specifically with your waste services.

doctor working with medical statistics and financial reports

Healthcare Case Study: Telecom Expenses Down by 26% in Healthcare

Case Study, cost savings0

Reducing Telecom Expenses by 26% in Healthcare

RadiusPoint collaborated with an Assisted Living and Nursing Home organization to enhance their oversight of telecom, IT, and wireless expenses. Serving as their telecom expense management (TEM) partner, RadiusPoint offered comprehensive insight into their invoices and spending and the range of services and equipment deployed across each site. This detailed visibility enabled RadiusPoint to identify and deactivate over 700 dormant business lines at various locations leading to a 26% reduction of their annual spend or $475k once the lines were disconnected and removed from the invoices.

Background

Given the healthcare industry’s focus on emergency preparedness, there’s a constant demand for reliable access to emergency personnel. Landlines play a critical role in ensuring immediate response in case of facility emergencies. Each location is mandated to have two copper lines for direct fire notification, with the option to add more lines for direct point-to-point access to the fire department. Safety for patients and staff is the top priority for this organization, necessitating RadiusPoint to meticulously validate vendor-provided information at every site.

Issues

The organization lacked previous inventory and audits of its telecom, IT, and wireless services. The service introduced detailed identification of each service type on vendor invoices, outlining all features, fees, taxes, and surcharges billed for each phone number. Various telecom vendors used different billing formats, with some providing only the total amount due without specific service descriptions or associated phone numbers. This limited visibility hindered effective decision-making regarding service removal or cost reduction through optimization.

As the costs of regular business lines escalated with vendors, the organization faced pressure to cut expenses. However, stringent regulations and safety protocols concerning patient well-being posed a challenge. Over the past two years, regular business line costs surged significantly, soaring from $50.00 to over $200.00 per line. Although newer, more cost-effective technology existed, regulatory restrictions prevented its use for regular business lines, prioritizing security measures.

Solution

RadiusPoint conducted an audit and inventory, yielding crucial information for eliminating unnecessary lines. This initiative validated services and phone lines across all sites, uncovering errors and overcharges in invoices. Some invoices continued to bill for services canceled years ago, obscured by invoice complexity or consolidation. RadiusPoint’s scrutiny pinpointed erroneous charges like features and taxes on phone lines canceled five years prior, prompting requests for credits from the vendor. In one case, even after an account was disconnected, circuits associated with it continued to bill due to a failed disconnection request.

The inventory and audit process began by verifying each phone line’s use through multiple calls and on-site visits for lines without responses. This process revealed over 700 unused regular business lines, some unconnected even in the phone rooms at various locations. Additionally, RadiusPoint offered recommendations to reduce line counts and optimize necessary lines. This enhanced visibility into remaining monthly expenses, enabling contract negotiations with vendors, and resulting in a further 10% cost reduction.

Results

Now equipped with ExpenseLogic, RadiusPoint’s proprietary software, this organization possesses comprehensive visibility into its telecom invoices and a complete inventory management system. In the Site Manager section of ExpenseLogic, a single click grants their team access to detailed invoice images, individual phone lines, circuits, wireless numbers, service features, and monthly costs for each location. Their annual savings exceeding $500k, alongside the elimination of 700 unnecessary lines, have led to reduced costs, improved services, and heightened accuracy in their monthly telecom billing.

Mid adult man checking financial information

UEM Collaboration Saves Over $1 Million

Case Study, UEM, UEM Managed Services4

UEM Collaboration Saves National Home Builder Over $1 Million

RadiusPoint recently collaborated with a national home builder to simplify the process of utility ordering and ensuring installations for more than 5,000 new home projects yearly. During this collaboration, RadiusPoint uncovered monthly billing exceeding $25,000 for homes sold two years earlier and identified over $100,000 in refunds from vendors holding funds for closed locations. The anticipated annual cost savings for this client are estimated to surpass $1 million, based solely on the initial six months of RadiusPoint’s services.

Background

A national home builder faced significant challenges in various areas, particularly in handling utility vendors, invoices, and expenses. With multiple divisions under corporate management and an annual workload of over 5,000 new home projects, each division independently managed meter installations but directed the resulting invoices to the corporate office for payment. This decentralized process led to numerous problems, including multiple service outages that required division intervention to restore services.

Issues

The initial challenge for the home builder revolved around service setup. Several individuals in each division handled order placements, causing delays in meter installation and service initiation, consequently impacting the start of construction projects. Additionally, the lack of a standardized process and the involvement of multiple individuals led to vendors not sending invoices to the corporate office. Often, invoices were mistakenly delivered to empty lots without mailboxes, resulting in returns. Subsequently, vendors would disconnect services, further delaying the work of trade workers on the homes. These complications collectively resulted in significant losses, amounting to thousands of dollars due to decreased productivity.

The subsequent problem concerned accurately tracking expenses related to meter usage. Typically, builders assign charges for individual homes to different accounting codes, enabling corporate oversight across various completion stages. This accounting system also offers insights into the completion date and turnover to the Sales department. However, while the corporate office had a daily method for monitoring home progress and stages, there was no established process to align this information with monthly utility expenses.

Adding to the list of issues was the discontinuation of services after home sales. Although each division was responsible for disconnecting services, this task was often neglected. The process of transferring services to the new homeowner’s name relied on the homeowner, but due to consistent confusion around final permit approvals and multiple contacts required with the vendor, ensuring that the homeowner completed this step was frequently overlooked.

Solutions

Service Order Placement

In their initial interaction with the Accounts Payable department, RadiusPoint pinpointed various issues that could be resolved through their Invoice Processing services, offering improved invoice management and cost allocation. While assessing the current service order process, RadiusPoint identified a fundamental issue underlying most of the problems faced. Leveraging their proprietary software, ExpenseLogic, the RadiusPoint team developed a streamlined service order process for each division. This involved creating a customized order form tailored to the builder’s requirements. The form also featured a link accessible on the builder’s tablet, enabling on-site service order placements.

Another valuable feature contributing to the process streamlining was the capability for the builder and their team to include permits or necessary documents when placing orders with utility vendors for future needs. Many utility vendors require a city government-issued permit before setting up a meter at a property. RadiusPoint incorporated this ability to attach documents to the order forms tailored for each builder’s requirements. These documents are centralized in the Site Manager Dashboard within ExpenseLogic, ensuring easy access not only for the division but also for anyone within the corporate structure. This customized addition significantly reduced the hours spent searching for documents previously held by one individual.

Timely order placement and ensuring prompt meter setups were crucial, and RadiusPoint facilitated this by collaborating with vendors through ExpenseLogic’s Moves, Adds, Changes & Disconnect (MACD) module. This module provided comprehensive tracking of the ordering process and seamlessly connected with the Invoice Processing section to guarantee proper invoice setup and allocation to the correct Cost Center, ready for the first invoice. One significant corporate benefit was the RadiusPoint team’s ability to track missing invoices. Daily Missing Bill reports were generated to identify vendor invoices that hadn’t been received. RadiusPoint then contacted the vendors to retrieve and process these invoices. Prior to RadiusPoint’s involvement, missing invoices could result in the property receiving the invoice after service disconnection, causing site downtime and productivity loss.

Proper Accounting and Allocation

ExpenseLogic functions as comprehensive accounting software, enabling the allocation of invoices to Cost Centers or project codes. Leveraging the builder’s daily report illustrating the 12 stages of home completion, RadiusPoint easily devised a solution for accurate allocation. They implemented a daily import system into ExpenseLogic, aligning Cost Centers with invoice expenses. This method ensured precise monthly expense allocation corresponding to each home’s building stage, facilitating accurate chargebacks and providing enhanced visibility into expenses. Additionally, it offered improved forecasting capabilities for total costs, adding value to the process.

Disconnecting Utility Services

One frequently overlooked aspect was the essential follow-up required after home sales. Divisions were responsible for contacting the vendor two weeks post-sale to confirm the new homeowner’s transfer of electric, gas, and water services into their name. Due to difficulties in tracking the home-building stage, these follow-ups often slipped through the cracks. Compounding the issue, vendors sometimes hesitate to change the account name due to pending permits or final inspections, necessitating additional follow-ups after inspection completion. Failures in inspections further prolonged the process. These hurdles transformed what should have been straightforward into a complicated and time-consuming procedure.
RadiusPoint established a clear timeline for vendor follow-up. By utilizing the MACD module in ExpenseLogic for service orders, the follow-up, including any required documentation, became more efficient. With all stages meticulously tracked, upon receiving subsequent invoices, RadiusPoint ensured the final bill accuracy and requested any outstanding credits, streamlining the process.

Results

The custom processes established by RadiusPoint through ExpenseLogic enabled numerous end users to not just initiate orders but also track home stages, offering clearer insights into utility expenses for each home build. This innovative approach empowered the home builder to reassign staff and, within the initial six months, achieve nearly $1M in savings.

Businessman using a laptop with graphs and charts on a laptop computer

Streamlining Utility Expense Management with Expense Software

Cloud Expense Management, cost savings, Solutions - UEM, UEM, UEM Managed Services0

Utility expense management software automates data capture, monitors usage in real time, integrates directly with utility providers, enforces spending policy, and generates the customized reporting finance teams need to act on utility spend rather than just record it. The complexity of utility billing, fluctuating rates, meter-level tracking across dozens of locations, is exactly what makes manual UEM slow and error-prone at any real scale.

Important Points Explained Ahead

  • Manual utility expense tracking is both time-consuming and error-prone, which is why automated data capture is the first capability worth evaluating in any UEM software.
  • Real-time monitoring surfaces usage anomalies, like a vacant-site meter still running, fast enough to act on rather than discovering it a quarter later.
  • Direct integration with utility providers matters more than generic dashboard features, since it is what lets a platform reconcile invoices against actual billing data automatically.
  • Scalability is not optional. Utility expense grows with location count, and software that cannot scale with it becomes the bottleneck it was meant to remove.
  • ExpenseLogic ties utility invoice data, meter-level usage and rate classification together in one platform, which is what makes vacant-cost recovery and rate reclassification findings possible in the first place.

Short version: the features that matter in UEM software are the ones that turn utility data into an action, a caught error, a disconnected meter, a reclassified rate, not just a dashboard that looks organized.

Why Utility Expense Management Is Harder Than It Looks

Utility expenses pose a distinct challenge because rates fluctuate, billing cycles vary by provider, and tracking has to happen at the meter level across every location, not just at the company level. Manually managing that volume of detail consumes real time and introduces errors that compound the more locations an organization operates.

Expense management software built specifically for UEM has become close to essential for organizations trying to optimize this process, since it replaces manual reconciliation with a system built to hold and cross-reference that level of detail automatically.

What UEM Software Actually Needs to Do

Capability Why it matters
Automated data capture Removes manual entry error and keeps utility data current without staff time spent re-keying invoices
Real-time monitoring Surfaces usage anomalies, like a vacant-site meter still running, while they are still cheap to fix
Utility provider integration Enables direct invoice reconciliation instead of manual cross-checking against provider portals
Policy enforcement Keeps utility spend aligned to organizational guidelines rather than drifting location by location
Customized reporting and analytics Turns raw usage data into decisions finance and facilities teams can actually act on
Scalability Keeps pace as location count and utility spend grow, rather than becoming a bottleneck at scale

Where Automation Finds Money, Not Just Data

Automated data capture and real-time monitoring only pay for themselves when they lead to an action, a disconnected meter, a corrected rate class, a resolved billing error, rather than sitting in a dashboard nobody checks. The value of UEM software is not the volume of data it displays, it is how directly that data connects to a specific dollar figure someone can recover or stop paying.

Streamlined approval workflows and mobile accessibility matter operationally, but they support the core function rather than replace it: a fast approval process for a bill that was never checked against contract terms just moves the error through the system faster, it does not catch it.

How ExpenseLogic Applies This to Utility Expense Management

ExpenseLogic ties invoice data, meter-level usage and rate classification together in one platform built specifically for utility expense management, rather than a general-purpose expense tool adapted to utility billing after the fact. That connection is what makes specific findings possible: vacant cost recovery, catching meters still billing at closed locations, and utility rate reclassification both depend on cross-referencing invoice, meter and account status data automatically rather than reviewing each one separately.

Real-time monitoring inside ExpenseLogic surfaces the same usage anomalies described above, fast enough for a facilities or finance team to act before a quarter of wasted spend accumulates. To see how this applies to a specific utility portfolio, request a demonstration.

Frequently Asked Questions

What is the single most valuable feature in UEM software?
Direct integration with utility providers, since it is what makes automated invoice reconciliation possible. Dashboards and reporting are only as good as the underlying data feeding them.

How does UEM software find vacant-site billing specifically?
By cross-referencing active meter and account status against a facility or location roster, so a meter still billing at a location marked closed or vacant surfaces as a specific, actionable finding rather than a line lost in a general invoice review.

Does UEM software replace the need for a human audit?
No. Software surfaces the anomalies and automates data capture; a human review still confirms findings, especially before disputing a charge with a utility provider. The software makes the review faster and more complete, not unnecessary.

How long does it take to see ROI from UEM software?
Initial findings, like vacant-site billing or rate misclassification, typically surface within the first 60 to 90 days of implementation, once invoice and meter data are fully loaded and cross-referenced.

References

  • RadiusPoint client engagement data, utility expense management software applications, 1992 to present

Related Articles

Capabilities described reflect RadiusPoint’s ExpenseLogic platform. Results depend on invoice volume, meter count and data completeness at implementation.

Online Virtual Teleworking Meeting On Computer

The Role of MMS in Remote Work Enablement

Managed Mobility Services0

By Sharon Watkins, Founder and CEO, RadiusPoint · 12 min read

Managed Mobility Services (MMS) enable remote work as device, line, help desk, and offboard for people who are not in the building. Shipping a laptop is not that stack.

Managed Mobility Services (MMS) is device lifecycle plus wireless expense: procurement, staging, kitting, deployment, troubleshooting, repair, recovery, and the invoice allocated to the phone number. This page is the remote-work operating stack. RadiusPoint analysts run that stack on ExpenseLogic for people who are not in the building.

Gallup’s Hybrid Work in Retreat? Barely. research found 51 percent of remote-capable U.S. employees are hybrid, down from 55 percent over two quarters, with fully on-site and fully remote each up two points. Hybrid workers spend 46 percent of the workweek in the office, or about 2.3 days, unchanged in the past year. Hybrid work is stable. The mobility bill is not, unless someone owns offboard.

Key Takeaways

  • Managed Mobility Services (MMS) is device lifecycle plus wireless expense. For remote work that stack is device, line, help desk, and offboard.
  • Gallup found 51 percent of remote-capable U.S. employees are hybrid, down from 55 percent over two quarters, with 2.3 office days (46 percent of the workweek) unchanged in the past year.
  • Remote work fails most often at offboard: HR says gone, the device is in a home, and the BAN keeps printing.
  • A food service MMS engagement cut cost 22 percent and more than $400,000 in year one across 600-plus lines. A Fortune 100 wireless discovery case recorded $830,000 in annual savings.
  • ExpenseLogic keeps Employee ID on the line when the user is not in the building. RadiusPoint analysts run help desk and stop-bill. MDM still owns the wipe.

The Short Version

Managed Mobility Services (MMS) for remote work is four stations: device, line, help desk, and offboard. If offboard has no owner, hybrid work is a staffing policy with an open BAN.

In this article

Managed Mobility Services enable remote work as a four-station stack

Managed Mobility Services (MMS) enable remote work as a four-station stack of device, line, help desk, and offboard for home-based users. Station one stages and ships with the serial on the record first. Station two activates the line against Employee ID. Station three is the help desk the user reaches from home. Station four is offboard: HR says gone, recover the device, stop the bill.

Generic “remote work tools” pages talk about video and VPN. They do not name four stations that have to survive a home address.

RadiusPoint has sold MMS as software plus people since 1992. ExpenseLogic is the platform. The commercial page is managed mobility services. The hire decision sits next door.

Why does hybrid work still break the mobility bill?

Hybrid work still breaks the mobility bill because the office is no longer the place where a departed device gets dropped on a desk. Gallup’s 51 percent hybrid share, down from 55 percent over two quarters, is a staffing fact. The 2.3 office days, 46 percent of the workweek, have not moved in a year. The BAN does not read Gallup. It reads the last activation.

A hybrid worker who is in the office 2.3 days still takes the handset home 2.7 days. When they leave the company, the handset is in a kitchen, not in IT. MDM can wipe. MMS has to recover the device and stop the bill. Zero-use mobile lines are what the BAN looks like when station four never ran.

Wireless versus telecom expense management is the category split. Remote work sits on the wireless side. The wireline cousin still matters for the home-office circuit, which telecom expense management covers. MMS is the handset and the line.

The remote-work MMS stack

The remote-work MMS stack is four stations that still have to work when the user is not in the building. Device: stage, kit, ship, serial on the record first. Line: carrier activation against Employee ID, plan and pool membership. Help desk: suspend, forward, replace, unauthorized purchase, because the user cannot walk to IT. Offboard: HR roster says gone, device recovery plus stop-bill. Remote work fails here most often.

Station Remote-work job Fail mode if skipped
1 Device Stage, kit, ship to a home or hotel. Serial on the record before the box opens. A phone in a kitchen with no asset record.
2 Line Activate against Employee ID. Plan and pool, not a consumer SIM. A personal line on a corporate BAN, or the reverse.
3 Help desk Suspend, forward, replace, unauthorized purchase. The user is not in the building. The ticket dies.
4 Offboard HR says gone. Recover the device. Stop the bill. Wipe succeeds. MRC continues.

A letter of agency is what lets RadiusPoint talk to the carrier on stations 2 through 4. The MACD process is the ticket shape for add, replace, and disconnect.

How does MMS differ from shipping a laptop to a home office?

MMS differs from shipping a laptop because a laptop can be an IT asset with no monthly carrier BAN attached. Shipping kit is logistics. Managed Mobility Services (MMS) is logistics plus a live wireless invoice plus a help desk plus an offboard that hits the carrier. A laptop MDM policy does not stop a pooled-data overage.

Remote-IT playbooks treat “send the hardware” as the enablement moment. RadiusPoint treats enablement as incomplete until Employee ID, serial, and BAN sit on the same record, and incomplete again until that record can be closed from a home address.

Expense cost allocation is how the MRC lands on a department when the person sits in three cities in one month. TEM onboarding data is the HR feed that makes station four possible. Shipping without that feed is a welcome box, not MMS.

What RadiusPoint recovered when remote lines outlived the roster

RadiusPoint recovered cash when remote and distributed lines outlived the roster, and the published cases put those dollars in the open. A food service client where RadiusPoint audited 600-plus lines, established a wireless policy, and cut costs 22 percent saved more than $400,000 in year one. A Fortune 100 engagement recorded $830,000 in annual savings from wireless discovery and optimization, on 10,000-plus wireless devices managed globally.

They are what happens when stations 2 through 4 actually run. A line that bills a departed remote worker is not a culture problem. It is an offboard miss.

Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category observation, not a RadiusPoint guarantee. When you need TEM is the trigger that in-house mobility admin has already failed the remote case.

When does a home-office circuit become a TEM problem, not an MMS one?

A home-office circuit becomes a TEM problem, not an MMS problem, when the billed object is a network service at a dwelling. Managed Mobility Services (MMS) owns the handset and the cellular BAN. TEM owns the circuit that followed the employee home. Utility Expense Management (UEM, meters and tariffs, not Unified Endpoint Management) owns vacant-desk electricity.

Gallup’s 51 percent hybrid share means roughly half of remote-capable employees still occupy a seat some of the week. The other days, the desk can still have a circuit and a meter. Vacancy cost recovery has decreased utility expenses by 12 percent in published work. Those are not wireless lines. They are the TEM and UEM cousins of station four.

Vacant utility cost recovery is the play after processing keeps presenting a closed site. Utility expense management is the commercial home for that cousin.

A letter of agency scoped only to wireless will not pull the home-office DIA invoice. Scope the grant to the BANs you actually have. Hybrid work multiplies BAN types. MMS is one of them. A healthcare provider cut telecom expenses 26 percent in published RadiusPoint work. If HR can change a work location and facilities cannot close the desk circuit, remote work is enabled for the person and still leaking for the site.

ExpenseLogic keeps Employee ID on the line when the user is not in the building

ExpenseLogic keeps Employee ID on the wireless line so a home-based user can still be suspended, replaced, or stopped without walking into IT. RadiusPoint analysts run help desk and stop-bill. You keep MDM, budget approval, and the HR roster feed. One platform covers wireless next to wireline and utilities at the same month-end.

RadiusPoint is ISO 9001 certified since 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. A capability statement and the about page carry the firm facts. Credentials tell you the operator is real. The four stations tell you remote work is actually enabled.

FAQ

What does MMS stand for in remote work?

MMS stands for Managed Mobility Services: device lifecycle plus wireless expense. In a remote-work setting that means staging and shipping the handset, activating the line against Employee ID, running a help desk the user can reach from home, and stopping the bill when HR says gone. It is not the text-message protocol, and it is not MDM. If your remote-work policy uses the three letters without the words, rewrite the policy before the next hire class.

Is MMS the same as MDM for a distributed team?

No. MDM is the control plane: enroll, encrypt, lock, wipe. Managed Mobility Services (MMS) is the bill, the help desk, and the Employee ID join. RadiusPoint runs MMS on ExpenseLogic. You still need a console that can wipe a lost phone in a kitchen. A wipe without stop-bill is only half the offboard. Remote work needs both, because the handset is not on a desk IT can walk to.

Who owns a remote worker’s line when they leave?

HR owns the roster date. IT owns device recovery and the wipe. Finance owns the dollar decision. A named MMS operator files the stop-bill with the carrier. RadiusPoint will be that operator on a managed ExpenseLogic engagement. If the handset is in a home and nobody has a letter of agency, the BAN keeps printing. The food-service 22 percent / $400,000 result is what happens when that filing actually runs against 600-plus lines.

Do hybrid workers still need a managed mobility help desk?

Yes, because 2.3 office days still leave 2.7 days where the user cannot walk to IT. Suspend, call-forward, replacement, and unauthorized-purchase tickets do not wait for a Tuesday in the office. RadiusPoint’s help desk is built for that. A laptop-only service desk is not. Gallup’s hybrid share moved from 55 percent to 51 percent over two quarters. The help-desk queue did not shrink with it.

How is this different from deciding to hire a managed mobility provider?

This page is the remote-work operating stack you are hiring them to run: device, line, help desk, and offboard for people who are not in the building. If a provider cannot name those four stations, and cannot say who files the home-office circuit disconnect, you have bought a console admin, not MMS. Ask for last month’s offboard exceptions, not a portal demo.

Does remote work change whether a meter is an MMS problem?

No. A meter is Utility Expense Management (UEM, not Unified Endpoint Management). A home-office circuit is TEM. A cellular line is MMS. RadiusPoint runs all three on ExpenseLogic, which is the point of one platform. Calling every remote-work bill an MMS issue is how a vacant desk circuit survives inside a wireless program. The $1,500 a month closed-location figure is the proof that the cousin exists.

What to do before the next invoice cycle

Pick ten employees who left in the last two quarters and still had a home address on the ship-to file. Match each to a serial, a BAN, and a stop-bill date. If a cell is empty, that is the operating gap. RadiusPoint will fill those cells for a managed ExpenseLogic engagement. Every cycle hybrid work stays stable and the BAN does not is a cycle station four can leak.

References

  1. Hybrid Work in Retreat? Barely. | Gallup
  2. Managed Mobility Services | RadiusPoint
  3. Why You Need a Managed Mobility Provider | RadiusPoint
  4. Telecom Expense Management Services | RadiusPoint
  5. Wireless Expense Management vs Telecom Expense Management | RadiusPoint
  6. Finding and Killing Zero-Use Mobile Lines | RadiusPoint
  7. Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
  8. The MACD Process in Telecom Expense Management, Explained | RadiusPoint
  9. Allocating Telecom and Utility Costs Across Departments | RadiusPoint
  10. The Data a TEM Provider Needs Before Day One | RadiusPoint
  11. Signs Your Company Has Outgrown Managing Telecom In-House | RadiusPoint
  12. 4 Benefits of Telecom Expense Management (TEM) | RadiusPoint
  13. Does Your Enterprise Face These 5 TEM Challenges? | RadiusPoint
  14. Capability Statement | RadiusPoint
  15. About RadiusPoint | RadiusPoint
  16. Vacant Cost Recovery: The Utility Bills Nobody Is Watching | RadiusPoint
  17. How to Audit a Utility Bill for Errors | RadiusPoint
  18. Utility Expense Management | RadiusPoint
  19. Sharon R. Watkins | RadiusPoint
  20. ExpenseLogic reviews | Capterra

Related articles

Disclaimer

This article is general information for IT, HR, finance, and mobility teams enabling remote and hybrid work. It is not legal, HR, or accounting advice. Gallup figures describe U.S. remote-capable employees, not RadiusPoint clients. Outcomes cited are from specific RadiusPoint client engagements already in the published proof library and are not a guarantee of future results. Category-level TEM ranges are hedged and are not RadiusPoint promises.

Coin stacks and chart graphs on a chessboard background

Deep Dive Eliminates Telephone Overcharges

Case Study, cost savings2

Most organizations with multiple locations will have many telephone vendors that they must deal with daily. Each Telecom vendor will have different service offerings that will create confusion and ambiguous monthly invoices.

How do you keep your organization from overpaying for your services or having the wrong ones in place at each location?

Organizations require telecom services at each location for several reasons:

  • Regulatory – fire alarm and elevator lines
  • Security – alarm lines for the security system
  • Order Management – Point of Sale (POS) over data circuits
  • Customer Access – Direct Lines to departments for customers
  • Connectivity for location to corporate – Data circuits
  • Long distance – Connecting the location to the outside world for long-distance calls
  • Wireless Service – Wireless devices for employees

These services will be provided by multiple vendors, which means that there will be multiple invoices for each location, each month. Identifying the best vendor with the best rates is not the beginning of the quest to eliminate overcharges. The beginning is the deep dive that is required to identify what services are already in place and how those services are used.

Most organizations have specific telephone needs that require circuits and copper lines for each location. Keeping up with the circuit numbers, each copper line phone number, and what it is used for is a cumbersome task.

For one retailer, not ensuring that services and equipment were properly cataloged and monitored created an embarrassing situation for the telecom and IT team and overcharges of over $62k paid needlessly by the retailer.

Retailers must have telephone numbers that allow a patron to call a specific department such as men’s shoes or children’s clothing. To have this type of service a retailer needs to have direct lines to each department.

Keeping an inventory of the circuits and phone numbers may have identified that the services were not canceled when the location closed. The other issue that created this overcharge situation was the ambiguous invoice from the telephone vendor.

The billing did not break down the services with enough detail to allow the telecom and IT team to realize that when they requested the services to be disconnected, not all services were disconnected. This oversight caused a 2 year overpayment period of $62k.

So, beyond the obvious of making sure your company is not overpaying for services, why is this deep dive needed?

In the Telecom industry, this deep dive is referred to as an inventory and audit of the telecom and IT services. This inventory and audit should create a baseline of service types, costs, contracts, and invoices.

It should also validate what services you have, the location address, and the department or personnel using the services. Identifying errors, overcharges and inefficiencies in your environment will bring the entire process together to cut costs and increase efficiency.

Having this information detailed by location would have saved this retailer over $60k because when the services were no longer needed and a disconnect request was made, it would have been quickly identified that the services continued to bill.

Identifying the right partner to work with to perform the inventory and audit is a must. There are many organizations that will “audit” your telephone invoices, some only charging for a portion of the savings however, defining exactly what will be audited and what the deliverables should be the first questions asked of your potential partner.

If you need this deep dive to identify very detailed information about your current telecom environment, you will most likely not receive that with a contingency-based model as often these are quick looks at the services to identify the low-hanging fruit.

The deep dive needed to specifically identify all services and their purpose will need to be performed by a project-based company that defines the deliverables with multiple steps and a very detailed work product.

Identifying the information that will be included in the inventory and audit is one of the first steps in gathering the information required and a timeline that will produce cost-saving results. One of the most frequent inventory and audits performed is for copper lines or Plain Old Telephone System (POTS) lines.

These lines are often required for businesses for alarm or elevator lines. Several years ago, this was the best and most cost-effective solution, however, innovation has created new types of services that work better and are much more cost-effective.

A business can transition over to these new services. However, if you do not have an inventory of all of your current services and phone lines, you run the risk of not disconnecting all of the POTS lines and you will keep paying for them.

A recent inventory and audit identified over 600 POTS phone lines that should have been canceled years before, however, the locations continued to pay for the lines because they had no idea the lines still existed.

The services had moved to a more modern service at a much lower cost, but the telecom team performing the work did not realize that the lines continued to bill. This oversight cost this company over $30k per month.

How can your chosen partner prevent this type of oversight from occurring? Identifying all the current services is the best place to start by ensuring that you’re only paying for what you need.

A successful project consists of a framework for managing fixed telecom environments that focuses on people, processes, and tools/technology. The inventory and audit establish a contract, invoice, service detail, and cost baseline.

The visibility gained through the project supports technology selection, budgeting, contract negotiations, vendor relationships, change management, and other integral telecom activities.

What type of information is needed to complete an inventory and audit?

  • Location address
  • Service contracts
  • Invoices
  • Customer Service Records
  • Organizational information
  • Service ordering process

Identifying the services and lines or circuits is one of the most important areas of the project as this is where most of the hidden services are found. Ensuring that an organization is only paying for the services that they want, and need is an integral part of the process and can uncover thousands in savings.

During an inventory and audit for an auto parts after-market organization, it was uncovered that there were 25 toll-free lines billing long-distance calls however the lines did not belong to them.

The lines were billed through the long-distance carrier and were on an invoice that was billed monthly; however, the total invoice cost was over $500k monthly and was more than 1,000 pages in length.

The only way this type of overcharge is identified is by calling each phone line to ask who the line belongs to. Once this occurred, the lines were moved from the organization’s account, saving them $10k per month.

Verifying ownership of the services is the first part of the process and once the services are verified as belonging to your organization, it is necessary to ensure that the monthly charges are accurate.

Identifying where contracts exist for each location is time-consuming but a required part of performing the inventory and audit steps. A quick-service restaurant learned the hard way that obtaining a global contract does not mean that you can set it up and forget about it.

For their 280 locations, the Internet Service Provider (ISP) set up services under contract, however, they set up an incorrect rate plan that caused this client to bill at a higher rate for each location’s Internet service.

The higher rate cost them $16,000.00 for the year, something that they had not budgeted for, and the overage caused financial reporting issues for their locations.

With the various types of services telephone or landlines, wireless, internet, long distance, etc. the steps to complete the inventory and audit are different for each type of service.

Ensuring that your partner is fully versed on each type of service and understanding what steps will be taken to audit each type of service will eliminate issues during the deliverable phase.

Upon completion of the project, you should have a set of these discoveries. It will also give you the baseline of information you need to effectively manage your environment on an ongoing basis, optimizing cost-effectiveness and efficiency.

Completion of this project will provide key insights, revealing what services are installed, where services are installed, what services are invoiced, and how much services cost.

This project will provide you with the comfort of a complete inventory of your telecom environment and will give you the baseline of information needed to manage your telecom environment in the most efficient and cost-effective manner.

With the skyrocketing costs for telecom services and the need for fiscal responsibility in the face of inflation and possible recession, it is imperative that a business consistently monitors their telecom and IT invoices and services.

Hands of businessman putting coins into piggy bank and holding money

How to Implement Telecom Expense Management: A Step-by-Step Guide

cost savings, Solutions - TEM, TEM, TEM Managed Services0

Implementing telecom expense management follows five steps: audit current telecom spend, develop a strategy based on what the audit finds, choose a TEM solution that fits the organization’s scale, implement it against a defined timeline, and monitor continuously afterward. Skipping the audit and jumping straight to software selection is the most common reason TEM implementations underdeliver.

Important Points Explained Ahead

  • A telecom audit has to come first. Choosing software before knowing what you actually spend and where it leaks means optimizing against guesswork.
  • Structured TEM implementation typically delivers 15% to 30% in telecom savings, a figure that holds consistently across RadiusPoint’s own client base and independent research alike.
  • The global telecom expense management market has grown steadily as businesses recognize that unmanaged telecom spend scales faster than headcount.
  • Complexity of billing, disparate internal systems, and lack of dedicated resources are the three most common reasons TEM implementations stall internally.
  • Monitoring is not a final step, it is the ongoing discipline that keeps savings from eroding back to pre-audit levels within a year or two.

Short version: the software matters less than the sequence. Audit first, strategy second, solution third, implementation fourth, ongoing monitoring last, and each step depends on the one before it actually being done well.

Why Telecom Spend Needs Deliberate Management

Telecom expenses now represent a larger share of operating budgets than most finance teams expect, driven by distributed teams, constant connectivity requirements and a growing number of service providers per organization. Managing that spend without a structured process is difficult given how complex telecom billing has become, with voice, data and mobile services often billed by entirely separate providers under separate terms.

Structured TEM implementation typically delivers 15% to 30% in telecom savings, consistent with what independent research and RadiusPoint’s own client outcomes both show. Organizations that skip formal telecom expense management risk losing ground to competitors who have already converted that gap into recovered budget.

What Telecom Expenses Actually Include

Telecom expenses span voice, data and mobile services, each typically billed by different providers under different terms, plus hardware, software, maintenance and support layered on top. Voice services come from traditional landline or VoIP providers, data services cover internet connectivity and networking, and mobile services cover both voice and data plans for devices, each with its own billing quirks and error patterns.

Without active management, these components compound into unnecessary cost fast, since nobody outside a dedicated audit process is checking whether a given circuit, line or plan still matches what the organization actually needs.

The Five Steps to Implementing TEM

1. Conduct a telecom audit

The audit establishes visibility into current spend and identifies where inefficiency lives before any solution gets selected. Skipping this step means every later decision is based on assumption rather than data.

2. Develop a TEM strategy

Based on audit findings, define goals, objectives and an action plan covering rate optimization, contract renegotiation and error elimination, so the strategy targets the specific waste the audit actually found.

3. Choose a TEM solution

Evaluate scalability, customization and integration capabilities against the organization’s actual telecom footprint, not a generic feature checklist, since the right solution for a 40-location retailer looks different from the right solution for a single-site professional services firm.

4. Implement the solution

Integrate with existing systems, train employees, and build the processes that keep the platform accurate going forward, since a TEM platform is only as good as the inventory and contract data feeding it.

5. Monitor and optimize continuously

Regular monitoring keeps the savings the audit and implementation surfaced from eroding back to baseline. This is the step most commonly treated as optional, and the one whose absence explains why savings so often fade within a year or two.

Common Implementation Challenges and How to Address Them

Challenge How it gets addressed
Complexity of telecom billing across providers A TEM solution with real-time, consolidated visibility across every vendor
Disparate internal systems and processes Integration with ERP and finance systems rather than parallel spreadsheets
Lack of internal resources or expertise Outsourcing to a specialist TEM provider rather than building in-house
Poor visibility into actual spend Real-time reporting tied to the audit baseline, not a static annual snapshot
Difficulty negotiating vendor contracts Leveraging a TEM provider’s rate benchmarking and negotiation experience

Best Practices Once TEM Is Implemented

Regular audits, not just the initial one, keep visibility current as vendors, locations and services change over time. Automated invoice processing reduces both the labor cost and the error rate that manual review introduces, and clear policies defining who owns telecom spend decisions prevent the kind of decentralized purchasing that recreates the original problem.

Training the people actually using the platform matters as much as the platform itself, since a TEM solution nobody understands how to use degrades into a reporting tool nobody checks. Continuous monitoring closes the loop, turning implementation from a one-time project into an ongoing discipline.

How RadiusPoint Runs This Process End to End

RadiusPoint runs all five implementation steps through ExpenseLogic, starting every engagement with a telecom audit rather than a software demo, so the strategy that follows targets whatever the audit actually finds. This is the same telecom expense management discipline RadiusPoint has applied since 1992, and organizations evaluating whether to build this in-house or outsource it can see what to ask in questions to ask a TEM provider before you sign.

Frequently Asked Questions

How long does a full TEM implementation take?
Most organizations complete the audit and strategy phases within 60 to 90 days, with solution implementation and staff training following over the next one to two months, depending on inventory complexity and vendor count.

Can a small business implement TEM, or is it only for large enterprises?
The five-step process scales down as well as up. A smaller telecom footprint means a faster audit and a simpler implementation, not a fundamentally different process.

What is the biggest reason TEM implementations underdeliver?
Skipping or rushing the initial audit. Choosing a solution before understanding actual spend and waste means optimizing against assumptions instead of data, which limits how much the implementation can realistically recover.

Should TEM be managed in-house or outsourced?
It depends on internal resources and telecom complexity. Organizations without dedicated telecom expertise typically get faster, more complete results outsourcing to a specialist, since the audit and negotiation work benefit directly from vendor-specific experience.

References

  • RadiusPoint client engagement data, telecom expense management implementation, 1992 to present

Related Articles

Savings ranges reflect industry research and RadiusPoint client outcomes and are not a guarantee of results for every organization. Actual savings depend on telecom footprint, contract complexity and implementation scope.

businessperson pointing at document in touchpad at meeting

ESG Reporting: Eliminating 800 Man-Hours of Data Gathering

Case Study, cost savings, UEM0

Many organizations have a workable Corporate Social Responsibility (CSR) plan in place.  However, Environmental Social Governance (ESG) will be the new benchmark going forward to ensure that both your organization and brand stay relevant and socially acceptable.  How does your organization get ready and stay ready for this very intricate and detailed reporting that is required for electric, gas, and water consumption?

Challenge

A nationwide retailer with over 1,600 locations has required reporting for the electric, gas and water consumption for each one of their locations.  The information required must be gathered from the monthly invoices.   The time to gather this information manually would have taken over 800 hours which would have involved someone reviewing each invoice for each month and contacting the vendor for the necessary information that was missing from the invoice.

Issues to Resolve

  1. Time constraints – the reporting is needed during the 1st quarter of the year for the previous year
  2. Personnel constraints – The Accounts Payable team did not have time which required temporary staff to be hired
  3. Knowledge Gap – the vendor’s invoices vary from vendor to vendor so being able to read an electric, gas, or water invoice was necessary to get the work completed timely
  4. Invoice Availability – the invoices for a portion of the required review had been moved off-site and had to be recalled for this review.

Opportunity

Identifying the requirements early in the relationship with RadiusPoint and this client created the perfect opportunity for this client to have the required reporting in advance of the need.  RadiusPoint provides the monthly utility expense management services for each of the 1,600 locations from receipt of the invoice to the bill pay portion of the process.  This utility expense management also involves energy expense management that identifies the usage in kWh, therms, and gallons to create more detailed reporting.  Using the information that was already being gathered from the invoices and adding the additional required information, RadiusPoint was able to ensure that this client had the required reporting by location for each type of service.

Solutions

The data usage that is needed from each invoice is compiled by the chosen ESG company that creates the client’s overall ESG report.  Having this accurate data when it is needed was paramount to the client.   The data is required during the first quarter of the next year for the previous year which puts a large burden on an already busy Accounts Payable department.  RadiusPoint was able to pull together the reporting and provided an ongoing report solution so that the following year, the report would be completed by the last week of January for the entire previous year.  This solution allows the RadiusPoint team to review the data and add any missing components on a monthly basis to ensure that all data is reported for the year by the beginning of the following year.  This solution alone eliminated the normal delays of trying to identify who would be pulling together this information and when it would be provided.

Once the client looked at hiring temporary staff to pull the additional required data from the invoice, it was determined that this project would involve over 800 man-hours for the 1,600 locations.  RadiusPoint’s solution provided most of the required usage data and the RadiusPoint team was able to go through and identify the missing information quickly to populate as required.

Utility invoices are not easily deciphered and having staff to read the invoices and gather the necessary data was a stumbling block for this client.  Trying to find the staff that could perform this data gathering task that was knowledgeable about the electric, gas and water services was problematic.  RadiusPoint’s team has an ESG department with knowledgeable personnel that easily filled this knowledge and personnel gap for the client.

Having the invoices on hand presented a problem for this client but it was one that was easily resolved by RadiusPoint.  All invoices processed by RadiusPoint are electronically attached to the account number and the digital image is saved for up to seven (7) years.  Reviewing past invoices was made easy with the information readily available at the click of a mouse.

The Results

Most ESG programs make provisions for reducing the cost of those services, but the “how” to achieve these cost reductions can be hard to predict.   Measuring consumption is the first step in the right direction to reducing usage and monthly costs.  The monthly ESG management services allow for the client to see the usage information on a monthly basis which in turn allows for necessary pivots that could result in a reduction of usage.

RadiusPoint’s monthly invoice processing and expense management services manage the utility invoice from receipt to payment of the invoice.  Utility and telecom auditing are also important parts of the monthly service that allows RadiusPoint to fully manage the entire lifecycle of the utility or telecom invoice and service.  This client saved over $48k and received their detailed and required ESG reporting on time.

TEM Audit Cost Savings

Telecom Expense Management (TEM) – Auditing Telecom Invoices for Saving Opportunities

cost savings, TEM0

The telecom expense management (TEM) industry has grown in size over the last few years, concurrent with the evolution of telecom technology, the demand for bandwidth, and the rising use of wireless devices and video conference services during the pandemic.

As a result of these trends, medium-sized and large corporations have resorted to using the services of third-party providers specializing in the analysis of telecom vendor services and billing to curb the increasing weight of telecommunication services on their P&L.

As part of their mission, telecom expense management specialists like RadiusPoint audit the invoices issued by telecom and internet service providers, to detect cost-saving opportunities and erroneous charges driving up the cost of the lines.

TEM Auditing Terms Definitions

To do their invoice analysis, telecom expense management specialists must gather specific data points from the client and the telecom operators billing the client. Here are 11 data points that the TEM specialist always must collect. The TEM specialist provides the client with the 12th one in the following table.

Some definitions are necessary:

DATA POINT WHAT IT IS
Service Address / Identifier The physical location or unique identification of the client’s telecom service
Service Provider The company that provides telecom services to the client
Master Account Number The main account number associated with the client’s services from the service provider
Sub-Account Number Secondary account numbers tied to the master account often used to track usage and costs for specific departments or locations
Circuit ID/Number A unique identifier for each circuit or line that connects the client’s service location to the service provider’s network
Circuit Type The technology used for the circuit, such as T1, E1, DSL, MPLS, or Ethernet
Port Size The bandwidth capacity of the port (measured in Mbps or Gbps) used to connect the client’s equipment to the service provider’s network
PVC (Permanent Virtual Circuit) A virtual connection between two points on a network that simulates a dedicated physical connection
DLCI (Data Link Connection Identifier) A unique number assigned to a PVC in a Frame Relay network, used to identify the virtual connection
CIR (Committed Information Rate) The guaranteed minimum data transfer rate provided by the service provider for a particular circuit
Un-Audited MRC (Monthly Recurring Charge) The monthly cost for the telecom service as billed by the service provider, before the audit
Audited MRC The corrected or optimized monthly cost for the telecom service, identified during the audit process

 

Data points: how they are used for Telecom audit

Each of the data points above has a role in the auditing process which will eventually lead to identifying potential savings or billing discrepancies. The table below summarizes the use of these data points.

Data Point Auditing Purpose & Identifying Savings/Discrepancies Reference/Source Document Flagging Cost-Saving Opportunities or Billing Discrepancies
Service Address / Identifier Verify service locations and validate service usage Service provider invoices, contracts, and client’s internal records Compare the service address with the client’s records to identify unused services or locations
Service Provider Ensure appropriate providers and services are being used Service provider invoices and contract Look for better rates or service options from alternative providers or negotiate with the current provider
Master Account Number Verify account accuracy and organization Service provider invoices and contract Ensure charges are billed to the correct account and identify unauthorized charges
Sub-Account Number Analyze costs and usage by department or location Service provider invoices and client’s internal records Identify high-usage areas, reallocate resources, or uncover billing errors
Circuit ID/Number Validate the circuits and their usage Service provider invoices, contracts, and circuit inventory Compare circuit IDs with inventory to identify unused circuits or billing discrepancies
Circuit Type Assess if the correct technology is being used Service provider invoices, contracts, and client’s internal records Evaluate if a more cost-effective or efficient circuit type is available
Port Size Check if the bandwidth capacity meets the client’s needs Service provider invoices, contracts, and client’s internal records Identify underused ports or opportunities to upgrade/downgrade for cost savings
PVC Validate virtual connections between network points Service provider invoices, contracts, and client’s internal records Ensure PVCs are correctly billed and identify unused or unnecessary virtual connections
DLCI Confirm Frame Relay network connections Service provider invoices, contracts, and client’s internal records Verify DLCIs match the client’s records and identify billing discrepancies
CIR Ensure the guaranteed data transfer rate is being met Service provider invoices, contracts, and client’s internal records Monitor actual usage vs. CIR to identify opportunities for negotiation or cost savings
Un-Audited MRC Establish a baseline for monthly telecom expenses Service provider invoices Compare with audited MRC to determine cost-saving opportunities
Audited MRC Identify optimized monthly telecom expenses after the audit Service provider invoices and audit findings Validate the effectiveness of the audit and track potential savings

 

TEM Cost-saving opportunities

Once the information has been collected, and the telecom operators‘ billing has been analyzed, the TEM specialist looks for specific types of cost-savings their client can make on their telecom bills.

Here are 10 types of cost-savings a TEM specialist would look for:

  1. Unused services: Discontinue services or circuits that are no longer in use, which helps reduce monthly costs.
  2. Negotiated rates: Renegotiate contracts with the service provider to obtain better service rates or discounts.
  3. Service bundling: Combine multiple services or features into a bundled package for discounted rates.
  4. Optimized service plans: Choose service plans that better match usage patterns, such as unlimited plans for high usage, or pay-as-you-go plans for variable usage.
  5. Technology upgrades: Replace outdated or inefficient circuits with newer, more cost-effective technologies.
  6. Volume discounts: Leverage the client’s purchasing power to negotiate volume discounts based on the number of lines or the total spending.
  7. Optimization of port sizes: Adjust port sizes to match the client’s bandwidth requirements more accurately, avoiding over- or under-provisioning.
  8. Resource reallocation: Identify high-usage areas and redistribute resources or services to better align with the organization’s needs.
  9. Tax and regulatory fee adjustments: Verify and correct taxes and regulatory fees, which can result in cost savings if errors are found.
  10. Alternative providers: Research and consider alternative service providers offering better rates or service options.

Typical telecom overcharging situations and billing errors

TEM specialists use proprietary SaaS platforms to automate the analysis and processing of telecom bills. These complex systems compare the client’s current telecom invoices with the vendor’s conditions, the line number, and the device ID when applicable.

The function of these SaaS platforms is to accelerate and systematize the processing of telecom invoices, a big organization with hundreds of retail locations that can quickly become a monthly nightmare for their Accounts Payable department. In fact, it is not uncommon for a large organization to have to process over a thousand telecom invoices in the course of a month. This represents a very large workload, and when reduced by automation, sizable soft-dollar savings for the organization.

The TEM specialist sets up the SaaS platform to flag out any inconsistency in telecom billing, and mismatch with known rates. Here is an example of 10 common overcharges and billing errors found in a telecom operator’s invoice:

  1. Double billing: Charges for the same service or feature appear multiple times on the invoice.
  2. Incorrect rates: Charges that do not match the contracted rates or discounts agreed upon with the service provider.
  3. Unauthorized charges: Charges for services or features not requested or approved by the client.
  4. Misapplied taxes: Incorrect application of taxes or regulatory fees, resulting in overcharges.
  5. Billing for disconnected services: Charges for previously disconnected or terminated services.
  6. Incorrect usage charges: Overstated charges due to metering errors or inaccurate data.
  7. Billing for non-existent locations: Charges for services at places where the client lacks telecom services.
  8. Incorrect service plan charges: Charges for a more expensive service plan than agreed upon or requested.
  9. Incorrect circuit charges: Charges for circuits not in the client’s inventory or assigned incorrect circuit IDs.
  10. Late payment fees and penalties: Unwarranted late payment fees or penalties that are not justified based on the client’s payment history or the contract terms.

The TEM specialist’s job is to flag these errors and let the Accounts Payable department deal with the vendors to recover credits and refunds.

But TEM specialists like RadiusPoint offer their clients to take over this part of the service, and recover credits and refunds themselves, as well as follow up with billing corrections so that the same errors don’t reappear in the next billing cycle.

By identifying cost-saving opportunities and billing discrepancies, and requesting refunds and credits from telecom operators, Telecom Expense Management specialists ensure their clients can curb the rising costs of telecommunications services, spend no more than what is necessary for their organization to operate, and offer their clients valuable business intelligence about the utilization of their telecom assets and their allocation by cost centers. This enables an organization to make better-informed decisions in procurement, cost allocation, and technology.

$1.3M in Telecom Refunds and Cost Savings: Case Study

Case Study, TEM Managed Services1

In this new case study, CEO Sharon Watkins discusses the telecom refunds and cost saving opportunities discovered by RadiusPoint during an Inventory & Audit of the telecom invoices of a global paper manufacturer. This case study highlights the need for organizations to streamline their telecom invoice processing to avoid overcharges and paying for services that telecom operators add to their billing. 

Transcript of the video

Summary

In this video, we will talk about how we were able to assist a paper manufacturer, a Fortune 100 company with a global presence, with their mobility management and telecom expense management needs.

To start with results, RadiusPoint obtained telecom refunds of over $450,000 on their wireless expenses in the first year of service. These refunds matched identified overcharges on wireless invoices. The primary challenge of our client was that they did not have the personnel to manage over 10,000 wireless devices and end-users. This was a global situation, the end-users were spread around the world.

The second major challenge was they could just not manage their telecom billing: at that time, invoices came in a box of over 3 feet high. According to our client, it took six people each month to go through these invoices, flipping through pages and pages to verify costs. So they needed assistance with the invoicing side, as well as with managing the servicing of so many end-users.

Inventory & Audit

We assisted our client with our proprietary platform, ExpenseLogic™, getting them set up to audit and process those invoices each month. We identified billing errors, and went back to the telecom operators to obtain all necessary refunds and reconcile the credits back on the bill.

We did identify over $450,000 in telecom refunds the first year. Those came back to the invoice. Then, still in the first year of service, we reduced costs by identifying services that were not supposed to be on their bill, or that Corporate did not want to pay for or authorize their end-users to have on their company phone. We identified over $850,000 in ongoing telecom savings (cost avoided).

Discoveries during the process

During our Inventory & Audit process, we discovered several major anomalies. For instance, the organization was still paying for phones (and services) for employees no longer on the payroll. Some of them had given their company phone to their children, and our client was still paying for them phones though these ex-employees had not worked there in two years.

We also identified instances when employees were downloading services (apps) — basically almost every phone had paid-app downloads — that were not authorized by company policy. However, since our client had no way to audit the bills, they had no idea their staff had downloaded those extra apps.

Initial TEM mission

Initially, RadiusPoint was hired by this client to perform a one-time audit, Then we continued on with monthly services for Telecom Expense Management and Mobility Expense Management.

Telecom refunds & savings

Q: Where did the $1.3 million in saving come from?

A: The $1.3 million came from two areas. First, we got over $450,000 in telecom refunds. During the first leg of our mission, as we were performing our Inventory & Audit process, we identified what actually belonged to the client, and disconnected what did not belong to them.

Second, going forward, we made recommendations that resulted in another $850,000 in telecom savings. Our recommendations aimed at cutting costs, consolidating the wireless operators, and optimizing contract rates.

That’s where the $850,000 [and ultimately, the $1.3M] came in.

TEM mission follow-up

Q: Does the client continue saving money on their telecom expenses?

A: Our client does continue to save money on an annual basis through our Telecom Expense Management services and the refunds we identify. It’s no longer a historical audit because the service occurs on a monthly basis and as the telecom invoice comes in, it is audited through our ExpenseLogic software platform. We then go to the vendor and reconcile. So yes, they continue to save money on a monthly basis.

Additional resources and references:

These links provide additional relevant information on our services and client feedback.

RadiusPoint and Telecom Expense Management: Our Presence in the Gartner Market Guide

TEM services: One of the two core business lines of RadiusPoint

Next case study:

Click here to discover how a glass manufacturer saved $100K on telecom expenses using RadiusPoint services

In this new video case study, Sharon shares how RadiusPoint helped a global glass manufacturer with large retail operations in the U.S. to overcome a lack of procurement framework, and curb their telecom expenses by $100K+ in Year 1 to get a ROI of 200% on TEM services.