By Sharon Watkins, Founder and CEO, RadiusPoint · 15 September 2026
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
- Census BANs and circuits from both entities (CSRs, BAN lists, contracts).
- Flag duplicates and dual BANs per site.
- Decide retain or disconnect with an owner.
- Pursue credits for erroneous charges.
- 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.
Duplicate circuits and dual BANs after legal day one
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.