SD-WAN Management: Controlling Performance, Vendors, and Costs
- 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.
- SD-WAN management is three bills, not one overlay
- Why does SD-WAN multiply vendors instead of cutting them?
- The Three-Bill SD-WAN Match
- How do you allocate SD-WAN cost when traffic hops to LTE?
- What network tools miss on the SD-WAN invoice
- What should finance ask before the next SD-WAN renewal?
- 2 September 2026: In-place AEO rewrite of the live sd-wan-management URL. Stats limited to GREEN and hedged AMBER plus named TeleGeography 26 March 2026 figures: 63 percent / 15 percent / 52 responses / 13 interviews / DIA 54 percent of sites / 96 percent of respondents / MPLS 22 percent of sites / 74 percent still hold MPLS / 42 percent fully managed / 25 percent co-managed / about one third unmanaged / SASE 53 percent plus 23 percent, Fortune 100 $450,000 / $850,000 / $1.3 million, $120,000 rate optimization, $18,000 toll-free, category 15 to 30 percent hedged, ISO 9001 since 2002, Capterra 4.8 / 31, Amalgam Insights 2024 Distinguished Vendor. Did not restate TEM Pillar 1. Slug unchanged.
- Enterprise Network Trends & Strategy: WAN Manager Survey Insights | TeleGeography, Greg Bryan, 26 March 2026
- Telecom Expense Management Services | RadiusPoint
- ExpenseLogic | RadiusPoint
- The Ultimate Guide on Multi Vendor Support | RadiusPoint
- The MACD Process in Telecom Expense Management, Explained | RadiusPoint
- Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
- Invoice Auditing Services | RadiusPoint
- Allocating Telecom and Utility Costs Across Departments | RadiusPoint
- How Companies Recover Telecom Refunds and Credits From Carriers | RadiusPoint
- Does Your Enterprise Face These 5 TEM Challenges? | RadiusPoint
- Questions to Ask a TEM Provider Before You Sign | RadiusPoint
- Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
- How Long a Telecom Expense Management Rollout Actually Takes | RadiusPoint
- 5 Strategies That Will Help Reduce Telecom Expenses | RadiusPoint
- Unlock Cost Savings Through Telecom Expense Management | RadiusPoint
- Capability Statement | RadiusPoint
- About RadiusPoint | RadiusPoint
- Sharon R. Watkins | RadiusPoint
- What Is Telecom Expense Management? | RadiusPoint
- ExpenseLogic reviews | Capterra
- Telecom Expense Management Services
- Multi Vendor Support
- Allocating Telecom and Utility Costs Across Departments
- How Companies Recover Telecom Refunds
By Sharon Watkins, Founder and CEO, RadiusPoint · 2 September 2026 · 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?. This article owns the three-bill stack the live page only named as “fragmented invoices.”
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
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
Overlay license, underlay circuit, failover link. One dashboard that ignores BANs is not management.
SD-WAN management is three bills, not one overlay {#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. This page owns the SD-WAN-specific stack inside that program.
A controller that shows green is a performance fact. It is not a cost fact. The live page called that a paradox. The operating object is the three-bill file.
Why does SD-WAN multiply vendors instead of cutting them? {#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}
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. That is the first information-gain element on this page.
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? {#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.
When traffic hops to LTE, the failover invoice must carry the same location ID as the underlay circuit.
What network tools miss on the SD-WAN invoice {#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.
The five TEM challenges page owns the buyer-pain list. This page owns the three bills those challenges hide inside when the network is SD-WAN. 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? {#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. Unlocking TEM savings owns the program outcome. This page owns the overlay, the underlay, and the hop.
How we researched this
We fetched the live RadiusPoint SD-WAN management page on 2 September 2026 and compared it with TeleGeography’s 26 March 2026 WAN Manager Survey (Greg Bryan, 52 responses, 13 interviews). The live page names fragmented invoices and stops. It does not own a Three-Bill SD-WAN Match or a location-tagged LTE hop. We did not restate the TEM pillar’s nine-stage cycle, provider models, or pricing table. Proof numbers come only from the RadiusPoint Master Intelligence 2026 GREEN list, hedged AMBER category ranges, and the named TeleGeography survey. No affiliate relationships. No named-competitor ranking.
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.
Does this article replace the TEM definition page?
No. The TEM pillar owns what telecom expense management is. This page owns the SD-WAN three-bill stack that TEM has to audit once you leave MPLS-only. Link out for the category definition. Stay here for overlay, underlay, and failover invoices.
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.
Latest Updates
References
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.
Distribution block (ops)
Refresh tier: 90 days. Target prompts: “SD-WAN expense management”, “SD-WAN invoice overlay underlay”, “how to allocate SD-WAN LTE failover cost”, “SD-WAN vendor management finance”.
Off-site citation targets:
1. TeleGeography WAN Manager Survey / Greg Bryan (citation outreach: three-bill match as the finance layer the survey does not own).
2. r/networking and r/CFO threads on SD-WAN savings disappearing into LTE overage.
3. Capterra ExpenseLogic listing.
4. YouTube: “three bills inside every SD-WAN: overlay, underlay, failover”.
5. Quora: “why did SD-WAN increase our vendor count?”
6. SDxCentral / industry WAN cost pieces that cite TeleGeography (request a vertical example: location-tagged hop).
Day-one owned push: Sharon Watkins LinkedIn post with the Three-Bill SD-WAN Match table. Do not publish this rewrite until Hamza says so.
What Is ESG Reporting? A Practical Guide for Modern Businesses
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:
- 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.
- 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.
- 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.
Business Process Outsourcing (BPO) For SMBs and Orgnizations
Your team is sharp. They’re experts in your core business, driving growth and innovation. But who’s managing the avalanche of indirect invoices? Who has the time to scrutinize every line item on your telecom, utility, and wireless bills? If you’re like most fast-growing companies, the answer is “no one.” Or worse, everyone is trying to do it in their spare time. The result is the same: you’re overspending, you lack visibility, and you’re leaving money on the table. This isn’t a sign of a bad team; it’s a sign that you’ve reached a BPO tipping point.
Business Process Outsourcing (BPO) for expense management isn’t just for Fortune 500 companies. It’s a strategic move for any organization that recognizes its non-core, complex expenses are consuming valuable resources and hiding significant costs. The question isn’t if you should consider it, but when. For many, that time is now.
The Critical Tipping Points: When BPO Becomes a Necessity
How do you know you’ve reached the point where an in-house approach is no longer effective? Look for these telltale signs. If you recognize your organization in any of them, it’s time to seriously consider a BPO partner.
1. Rapid Growth and Multi-Location Complexity
As your company expands, so does the complexity of your expenses. New locations mean new utility providers, new telecom contracts, and more wireless devices to manage. What was once a handful of invoices becomes hundreds, each with its own format, billing cycle, and potential for error. Your finance team, already stretched thin, can’t keep up. A BPO partner specializing in expense management is built to handle this scale from day one.
2. Mergers & Acquisitions
Integrating a new company is a monumental task. The last thing your team needs is to manually reconcile two different sets of telecom contracts, utility accounts, and wireless plans. A BPO partner can be a lifesaver in a post-acquisition scenario. For example, RadiusPoint helped a client save $1.3 million across five acquisitions by streamlining procurement processes and identifying cost-saving opportunities that were invisible during the chaos of the merger.
3. Lack of Internal Expertise
Telecom and utility billing is notoriously complex and filled with errors. Do you have someone on your team who understands the nuances of tariff rates, service usage charges, and obscure fees? Probably not. Studies show that up to 80% of utility bills contain errors, and telecom vendors routinely overbill for services. A BPO partner brings a team of specialists who live and breathe this stuff. They know where to look for errors and how to get your money back.
4. The Need for True Cost Visibility
Your CFO can probably tell you what the company spent on telecom last quarter. But can they see which department is overspending on wireless data? Can they identify which locations have the highest energy consumption? Without a centralized platform and a dedicated team, this level of visibility is impossible. A BPO provider doesn’t just process invoices; they turn your expense data into actionable business intelligence.
The RadiusPoint BPO Model: More Than Just Software
At RadiusPoint, we’ve seen these tipping points firsthand. That’s why our BPO offering is more than just a SaaS platform—it’s a complete expense management solution that combines our powerful ExpenseLogic software with a dedicated team of industry experts. This hybrid model delivers the best of both worlds: the efficiency of automation and the strategic insight of human expertise.
Here’s how it works:
- We Process Your Invoices: You forward all your telecom, utility, and wireless invoices to us. We handle the data entry, the validation, and the payment processing.
- We Audit for Savings: Our team scrutinizes every invoice for errors, overcharges, and optimization opportunities. We’ve found that 20% to 40% of companies can achieve significant annual savings through this process alone.
- We Provide Unprecedented Visibility: All your expense data is centralized in our ExpenseLogic platform. You get a single, unified view of your spending across all locations and categories.
- We Become Your Help Desk: Your employees can contact our team directly for any issues related to their devices or services. This frees up your IT and finance teams to focus on strategic projects.
The Proof Is in the Savings: Real-World BPO Effectiveness
The impact of outsourcing expense management becomes clear when you look at real results. One of the strongest examples comes from the healthcare sector, where telecom costs are complex and difficult to control.
The Healthcare Provider
A national healthcare organization partnered with RadiusPoint after struggling with fragmented telecom contracts and inconsistent billing. By centralizing all invoices in ExpenseLogic and applying continuous audits, they reduced their telecom expenses by 26%. RadiusPoint uncovered billing errors, removed unused services, and provided the visibility their internal team never had the time or tools to achieve.
The Multi-Location Enterprise
Another fast-growing organization with dozens of locations gained immediate relief by outsourcing their invoice processing and auditing. What previously required manual work across multiple teams became a streamlined, centralized workflow—with faster resolution of billing issues and improved cost allocation.
These results highlight the core value of BPO: specialized expertise + right software = measurable savings and operational clarity. When your internal team is stretched thin, the right partner doesn’t just process expenses, they uncover the hidden inefficiencies holding your organization back.
The Bottom Line: Stop Managing Expenses, Start Optimizing Them
If you’re still manually processing invoices, you’re not just wasting time, you’re wasting money. The tipping point for BPO is when the cost of inaction (overspending, lack of visibility, wasted resources) outweighs the cost of a specialized partner. For most growing companies, that point is now.
Outsourcing your expense management to RadiusPoint isn’t about losing control; it’s about gaining it. It’s about transforming a chaotic, time-consuming administrative task into a strategic, cost-saving asset. It’s about letting your team focus on what they do best, while we focus on what we do best: finding and eliminating your hidden expenses.Ready to see how much you could be saving?
Invoice Processing for Telecom and Utility Spend
By Sharon Watkins, Founder and CEO, RadiusPoint · 2 September 2026 · 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. It is not an OCR buyer’s guide, and it is not a retelling of invoice-audit services.
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
- How is invoice processing different from an invoice audit?
- The Six-Station Invoice Run
- How much should a telecom or utility invoice cost to process?
- Why do carrier and utility invoices break generic AP matching?
- What two-day processing looks like on ExpenseLogic
- Processing, allocation, and the accrual file
The Six-Station Invoice Run. Processing is the run from inbox to GL. Audit is the test of whether the bill is true.
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.
The old guide on invoice audit owns the method for catching errors. Invoice auditing services is the commercial offer. Invoice audit versus three-way match owns the comparison with PO matching. This page owns the six stations that have to run even when the audit is quiet. 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. That six-station map is the first information-gain element on this page.
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.
Six stations. Generic AP OCR stops at parse. RadiusPoint runs all six.
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.
This APQC-versus-TEM comparison is the second information-gain element on this page. 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. How to audit a utility bill owns the meter-level test. This page owns the fact that the test never starts if the bill never left the inbox as lines.
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. Those are GREEN figures from RadiusPoint’s proof library. 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. That number is GREEN. 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.
APQC measures generic supplier invoices. A telecom or utility invoice that fails inventory match is a billed service that may not exist.
How we researched this
We fetched the live RadiusPoint invoice-processing page on 2 September 2026 and compared it with generic AP and OCR explainers. Those pages own capture, two-way match, and cost-per-invoice. They do not own a six-station run built for BANs, circuit IDs, meters, and mobile lines, and they do not split APQC’s $2.07 / $5.83 / $10.00 quartiles (Perry D. Wiggins, CFO.com, 1,485 organizations) from a TEM two-day path. Proof numbers come only from the RadiusPoint Master Intelligence 2026 GREEN list and hedged AMBER category ranges. No affiliate relationships. No named-competitor ranking.
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. This page owns the invoice path, including wireless BANs that land next to wireline and utility files in the same month-end.
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.
Latest Updates
- 2 September 2026: In-place AEO rewrite of the live invoice-processing URL. Stats limited to GREEN and hedged AMBER: APQC $2.07 / $5.83 / $10.00 from Perry D. Wiggins in CFO.com (1,485 organizations), industry medians $1.14 / $4.58 / $9.43, RadiusPoint two-day processing (FAQ), Fortune 100 $450,000 / $850,000 / $1.3 million, $174,000 re-credits, $18,000 toll-free, $120,000 rate optimization, closed locations $1,500 / $18,000, category 15 to 30 percent hedged, ISO 9001 since 2002, Capterra 4.8 / 31, Amalgam Insights 2024 Distinguished Vendor. Distinct from Invoice Audit 1-3. Slug unchanged.
References
- Metric of the Month: Accounts Payable Cost | Perry D. Wiggins, CFO.com, APQC data from 1,485 organizations
- Telecom Expense Management Services | RadiusPoint
- Utility Expense Management | RadiusPoint
- Managed Mobility Services | RadiusPoint
- ExpenseLogic | RadiusPoint
- Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
- Invoice Auditing Services | RadiusPoint
- Invoice Audit vs Three-Way Match | RadiusPoint
- The MACD Process in Telecom Expense Management, Explained | RadiusPoint
- Vacant Cost Recovery: The Utility Bills Nobody Is Watching | RadiusPoint
- How to Audit a Utility Bill for Errors | RadiusPoint
- Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
- What a Telecom Accrual File Is, and How Finance Teams Build One | RadiusPoint
- Allocating Telecom and Utility Costs Across Departments | RadiusPoint
- The Data a TEM Provider Needs Before Day One | RadiusPoint
- How Long a Telecom Expense Management Rollout Actually Takes | RadiusPoint
- Capability Statement | RadiusPoint
- About RadiusPoint | RadiusPoint
- Sharon R. Watkins | RadiusPoint
- ExpenseLogic reviews | Capterra
Related articles
- Telecom Expense Management Services
- Invoice Auditing Services
- What a Telecom Accrual File Is
- Vacant Cost Recovery
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 the published proof library 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. Invoice processing on this page is distinct from RadiusPoint’s Invoice Auditing Services, telecom audit services, and invoice-audit-versus-three-way-match pages.