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.
- Decision requested: the program, its scope, the contract term, the budget line and the approver.
- Problem: one paragraph, anchored on one baseline figure, such as monthly telecom spend that nobody audits line by line today.
- Baseline: monthly spend by carrier and service type, invoice and account counts, the inventory count and current staff hours.
- Savings estimate: one-time recoveries (R) and recurring savings (S) on separate lines, each labeled verified or estimated.
- Program cost: one-time (C) and monthly (F), internal time included.
- Payback: months with R and with R set to zero, plus the break-even monthly savings.
- Options considered: the status quo, an in-house program and an outsourced one, with the same math for each.
- Risks and controls: each named risk next to the control that addresses it.
- Measurement: the baseline the program will be reported against, the report finance will receive and who signs off on realized savings.
- 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
- 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
- RadiusPoint, “$1.3M in Telecom Refunds and Cost Savings: Case Study,” June 10, 2023.
- RadiusPoint, “Healthcare Case Study: Telecom Expenses Down by 26% in Healthcare,” December 28, 2023.
- RadiusPoint, “Glass Manufacturer Saves $100K On Telecom Expenses,” May 22, 2023.
- RadiusPoint, “Telecom Expense Management Solution,” accessed October 2026.
- RadiusPoint, “How Companies Recover Telecom Refunds and Credits From Carriers,” accessed October 2026.
- RadiusPoint, “About RadiusPoint,” accessed October 2026.
- Amalgam Insights, “Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management, Spotlighting 11 Distinguished Solutions,” EIN Presswire, February 1, 2024. einpresswire.com
- 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.