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:
- A reasonable basis. Every saving ties to a service ID, a billing account and an invoice amount, not to a percentage of total spend.
- 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.
- 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.
- 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
- U.S. Securities and Exchange Commission, “Amendments to Financial Disclosures about Acquired and Disposed Businesses,” Release No. 33-10786, May 2020. sec.gov
- 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
- Code of Federal Regulations, Title 47, Section 52.103, “Lag times,” Electronic Code of Federal Regulations, current as of October 15, 2026. ecfr.gov
- RadiusPoint, “M&A Support Services: A New Way to Think About Their Role.”
- RadiusPoint, “Telecom Expense Management Solution.”
- RadiusPoint, “Inventory Management Helps Recovering $174K in Credits,” October 12, 2022.
- RadiusPoint, “Utilities Mismanagement Costs $18K in Unnecessary Expenses.”
- RadiusPoint, “Normalizing Invoice Processing and Payment in Hyper-Growth Phase.”
- RadiusPoint, “About RadiusPoint.”
- 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. 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.