The MACD Process in Telecom Expense Management, Explained
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.
This page owns the process. It isn’t a second TEM 101, and it isn’t a rewrite of What Is Telecom Expense Management?.
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
- Why do disconnects fail so often?
- The Disconnect Closeout Ladder
- How do moves and adds create duplicate billing?
- What finance sees when a MACD ticket never closes
- Who should own MACD: IT, telecom, or accounts payable?
- How RadiusPoint tickets MACD inside ExpenseLogic
Editorial diagram of the four MACD types. Disconnect is the tile that leaks cash.
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. Socium and other MACD explainers list similar vendor-side causes. The finance-side failure is the one this page owns.
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 information-gain element on this page.
| 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.
The Disconnect Closeout Ladder. RadiusPoint doesn’t retire the inventory in ExpenseLogic until invoice three is clean.
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.
Editorial still: the original circuit and the replacement circuit both carrying a monthly charge.
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. This mapping is the second information-gain element. Competitor MACD pages stay in the NOC. This page stays in AP.
| 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. Scope comes later on the LOA page in this set. 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 the RadiusPoint proof library 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.
How we researched this
We read live MACD pages from Socium IT, Digital Direction, Sequential Tech, and Vigilis, plus RadiusPoint’s TEM service page and the live TEM pillar. Those pages define MACD and list vendor-side disconnect failures. None publishes a five-rung Disconnect Closeout Ladder or a finance-symptom table tied to RadiusPoint proof. Numbers are GREEN or hedged AMBER from the 2026 Master Intelligence file and live RadiusPoint cases fetched 28 August 2026. No affiliate relationships.
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.
Latest Updates
- 6 August 2026: Drafted for the RadiusPoint AEO set. GREEN proof used: $18,000 toll-free, $174,000 inventory re-credits, $120,000 rate optimization, Fortune 100 $450,000 / $850,000 / $1.3 million and 10,000-plus devices, glass $100,000 / 200% ROI, healthcare 26%, automotive salvage $1.3 million. AMBER: 15% to 30% TEM category year-one range.
References
- Telecom Expense Management | RadiusPoint
- What Is Telecom Expense Management? | RadiusPoint
- Outsourced Telecom Expense Management | RadiusPoint
- Telecom Audit Services: What a Line-Item Telecom Audit Actually Finds | RadiusPoint
- Glass manufacturer saves $100K on telecom expenses | RadiusPoint
- About RadiusPoint | RadiusPoint
- Sharon R. Watkins | RadiusPoint
- MACD in Telecom: What It Means and How to Manage It | Socium IT
Related articles
- 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 the published proof library.