All posts by Sharon Watkins

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

1. Census BANs and circuits from both entities (CSRs, BAN lists, contracts).
2. Flag duplicates and dual BANs per site.
3. Decide retain or disconnect with an owner.
4. Pursue credits for erroneous charges.
5. 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:

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.

By Sharon Watkins, Founder and CEO, RadiusPoint

Utility bill pay clears invoices by their due date. Utility Expense Management, UEM after this first use, starts earlier. It audits the meter inventory, the tariff, and each site’s open or closed status before any funds move. Bill pay answers “did we pay on time.” UEM answers “should we have paid this at all, and at this rate.”

Here’s the tension that quietly drains a facilities budget. An accounts payable team can hit every due date, dodge every late fee, and still remit thousands of dollars a month for electricity, gas, and water at buildings nobody occupies. The invoices were paid correctly. They should never have reached payment. At RadiusPoint, one multi-location client was paying roughly $1,500 a month, about $18,000 a year, in utilities at closed locations that bill pay alone had no reason to question.

If you’re a Facilities Manager, Real Estate leader, Controller, or CFO deciding what to buy or build, the distinction below decides whether spend gets validated or just settled.

Utility Bill Pay Goals vs UEM Goals: Timeliness vs Correctness

Bill pay aims to avoid late fees and keep service running, while UEM aims to pay only validated, meter-level charges billed at the correct tariff.

Bill pay is measured on cycle time and clean remittance: received, coded, approved, and paid before the disconnect date. Every one of those steps assumes the charge is legitimate. Bill pay has no mechanism to ask whether the meter behind the account still serves an active site, or whether the rate matches what the account qualifies for.

UEM inverts the order. Before it clears anything, it validates the charge against a record of what should exist: which meters, at which sites, on which tariff, within which consumption range. When a building goes dark, UEM flags the still-arriving invoice and triggers vacant utility cost recovery rather than routing it to payment like any other bill.

Where the Audit Starts in a UEM Program

A UEM audit starts before payment with a meter inventory, a tariff class check, consumption thresholds, and each site’s open or closed status.

Remittance is the last step, not the first. Bill pay begins at the invoice and ends at the payment. UEM begins several steps upstream, at the reference data that tells you whether the invoice deserves to be paid. That reference data is a meter-level inventory, not an account list, because a single account can span multiple meters and a single site can carry meters that were never decommissioned. Auditing at account level is how closed-site charges survive. Auditing at meter level is how they get caught.

A bill pay process runs step one and skips to payment. A UEM process runs steps two through four first. Tariff validation is where a surprising share of recoverable money sits, because a wrong rate class bills quietly and consistently for years. When usage or site type no longer matches the assigned rate, that’s a utility rate reclassification finding, and it belongs to the audit, not to accounts payable.

Utility Bill Pay vs UEM: The Operating Model Side by Side

Side by side, bill pay and UEM differ in who owns them, what data keys they use, which exceptions they raise, and what they report.

Bill pay and UEM look identical at the moment of payment, because the invoice gets paid either way. The divergence lives in everything before and after that payment, which the table below lays out.

The data key row drives everything else. Bill pay is organized around the vendor account. UEM is organized around the meter, mapped to a site and a cost center. That single choice is what lets UEM allocate spend accurately, benchmark one location against another, and detect a charge at a site that closed last quarter. Fixing exceptions rather than settling invoices is why UEM sits closer to the discipline described in our overview of invoice auditing services than to a payment queue.

Vacant and Closed Sites: The Proving Ground for UEM

Vacant and closed sites prove whether you manage expenses or only pay bills, because site status should stop charges accounts payable would otherwise remit.

When a location closes or a tenant moves out, the meters rarely stop with them. The account stays open, the utility keeps billing, and unless someone has connected site status to the payment process, the invoices keep clearing. They arrive on schedule, for a plausible amount, against a real account, and they pay on time for a building that’s empty.

This is exactly where the RadiusPoint closed-location figure comes from: roughly $1,500 a month, about $18,000 a year, for one multi-location client, paid out on utilities at sites no longer in use. Under bill pay alone, that spend is invisible. Under UEM, the vacant or closed status flags the meter, the charge routes to an exception instead of to payment, and recovery begins. Across a property portfolio, chasing exactly this pattern is how vacant cost recovery has decreased utility expenses by 12 percent.

A late invoice gets noticed within days. A perfectly paid invoice for an empty building can bill for years. Only UEM is looking for the second one.

How RadiusPoint Runs UEM on ExpenseLogic

RadiusPoint validates utility invoices at meter level inside ExpenseLogic, allocates each cost to the right site, and recovers spend that tenant transitions leave behind.

The platform holds the inventory and people work the exceptions. ExpenseLogic is the record of what should be billed: the meters, the sites, the tariffs, and the consumption thresholds each account is measured against. Every incoming utility invoice for electricity, gas, water, sewer, and waste is validated line by line against that record, then allocated down to location, department, and meter number. When a charge fails the tariff check, breaks a threshold, or hits a meter at a closed site, ExpenseLogic raises the exception.

The other half is the part most platforms leave to the client. A RadiusPoint analyst takes the exception, files the dispute with the provider, pursues the credit, and, in the vacant case, works the account back to closure so the leak stops rather than just gets reported. Software plus people is the model.

Verdict: if your first question is the due date, you’re buying bill pay. If your first question is the meter inventory and the tariff, you’re buying UEM. Both keep the lights on. Only one keeps you from paying for lights in a building that’s dark.

The practical move for most portfolios isn’t to abandon bill pay. It’s to put a UEM audit layer in front of it, so validation happens before funds move. If you also manage telecom or wireless spend and want the same allocation and close pattern across categories, the case for a managed provider is laid out in our guide to when you need TEM. RadiusPoint delivers that layer on ExpenseLogic, and it starts at the meter, not the due date.

Frequently Asked Questions

These answers clarify what UEM means here, whether AP automation suffices, how deregulation and rate reclassification apply, and whether TEM and UEM belong together.

Is UEM Unified Endpoint Management?

No. In this article UEM means Utility Expense Management. Unified Endpoint Management is an unrelated IT term for managing devices. Here, UEM is the discipline of auditing, allocating, and controlling utility spend across electricity, gas, water, sewer, and waste.

Can AP automation alone deliver UEM?

It can pay, but it can’t audit. Accounts payable automation processes and remits invoices efficiently, which is bill pay done well. Meter and tariff audit still need UEM inventory and rules, because AP automation has no record of which meters should exist or what rate each account qualifies for.

Do we need deregulated procurement to start UEM?

No. Audit and allocation create value in regulated markets too. Procurement and rate shopping depend on deregulation, but validating meters, catching wrong tariff classes, allocating cost by site, and recovering charges at closed locations work regardless of market structure.

How does rate reclassification fit?

Wrong tariff classes are a UEM audit finding, not a bill pay task. When an account’s assigned rate no longer matches its usage or site type, the charge bills quietly and correctly from the provider’s side. Only a meter-level audit that validates tariff against the account catches it and files for the correction.

Should TEM and UEM share a platform?

Sharing ExpenseLogic gives Controllers one allocation and close pattern across categories. Telecom, wireless, and utility spend then validate, allocate, and report the same way, on one meter-and-account-keyed record, instead of living in separate tools with separate exception handling and separate month-end routines.

By Sharon Watkins, Founder and CEO, RadiusPoint

Prove TEM savings with hard refunds, documented rate cuts on live services, and eliminated inventory, while labeling avoidance separately so finance never sees inflated totals. The reason this matters is simple. A Controller has sat through too many savings decks that fall apart on the second question. A headline number lands, someone asks how it was calculated, and half of it turns out to be avoidance annualized on optimistic assumptions. Once that happens, every future number your telecom expense management programme reports gets quietly discounted.

Key Takeaways

This is the entire method in one place: separate the three buckets, evidence every line, label avoidance honestly, and hand audit a re-performable ledger.

• Hard savings are cash refunds and permanent bill reductions tied to a BAN and an invoice period.
• Avoidance is real but different, because it’s spend prevented, not cash hitting the ledger.
• Inflated avoidance, the habit of counting every hypothetical, destroys credibility with Controllers faster than a missed number ever will.
• Evidence packs need before and after rates, inventory IDs, carrier credit memos, and GL impact.
• RadiusPoint structures savings reporting from ExpenseLogic audit work so finance can re-perform the logic without a meeting.

Hard savings versus avoidance versus soft claims

Hard savings change cash or recurring bills, avoidance prevents spend, and soft claims without BAN-level evidence do not belong in a finance packet.

The difference isn’t academic. It decides which line a Controller will defend to an auditor and which line gets struck before the report leaves the building. Sort every claimed saving into one of three buckets. We call it the Three-Bucket Savings Model, and it’s the first thing that goes on any RadiusPoint savings report.

Soft claims are everything else: productivity, hours saved, general efficiency. They can be true and still not belong in the savings total, because finance can’t reconcile them to a BAN. Put them in the narrative, not the number. The cleanest hard-savings line is a recovered credit, which is the core of telecom refund recovery, and it’s also the line auditors accept most easily, because a credit memo is a document a carrier issued, not a calculation you performed.

Where programmes inflate numbers and how to stop

Inflation happens when one-time credits are annualized forever, baseline rates are fictional, or disconnected services get double-counted as both a refund and ongoing avoidance.

None of these require dishonesty. They usually come from a spreadsheet that was built to look impressive rather than to survive review. Each has a fix, and the fix is always the same shape: anchor the number to evidence and count it once.

The common root is missing evidence. A disciplined line-item telecom audit is what produces the credit memos, rate exhibits, and disconnect confirmations that keep each number anchored to something a carrier or a contract can confirm. Without that evidence, a programme is left estimating, and estimates drift upward until the first hard question exposes them.

Evidence Controllers accept

Controllers accept credit memos, rate exhibits tied to service IDs, disconnect confirmations, and GL postings that reconcile cleanly to the savings story you are telling.

Everything else is a claim awaiting proof, and a Controller will treat it that way. The evidence pack behind a defensible savings report is short and specific:

• Carrier credit memos with case numbers, matched to the BAN and to the invoice that carried the credit.
• Before and after invoices on the same service ID, comparing like periods, so a rate change is visible rather than asserted.
• Signed rate exhibits or contract amendments showing the old rate and the new rate.
• Disconnect confirmations from the carrier, not just the internal disconnect order, since an order raised is not a service removed.
• GL postings that show the credit or the reduced charge landing in the correct cost center and period.
• The inventory of record, dated, showing the service removed from what you own.

This is why credible savings reporting is a byproduct of a real invoice auditing service, not a quarter-end spreadsheet exercise. The audit generates the documents. The report only has to organise them and point each one at the line it supports.

A savings ledger finance can re-perform

Keep a ledger carrying BAN, service ID, savings type, monthly impact, start date, and owner, so audit can re-perform each line without a slide deck.

Internal Audit should pick any row, pull evidence, redo the arithmetic, and reach the same number. The Re-Performable Ledger uses these fields:

How RadiusPoint reports savings from ExpenseLogic work

RadiusPoint ties refund recovery and optimisation outcomes to inventory and invoices inside ExpenseLogic, so every reported saving stays traceable when finance reviews it.

ExpenseLogic holds inventory, rate tables, and invoice history together, while RadiusPoint analysts pursue carrier disputes, track credits, and update moves, adds, changes, and disconnects. That combination lets a Controller trace each saving to a BAN and period.

Published client outcomes illustrate the rule, not a guarantee. One Fortune 100 manufacturer recovered $450,000 in first-year telecom refunds and moved to $850,000 in ongoing annual savings. The refund is one-time hard savings; the $850,000 carries forward only while rates remain lower. A client also achieved $120,000 a year through contract rate optimisation, a negotiated recurring line. Other reported outcomes include a healthcare provider’s 26% telecom expense reduction and a food service company’s 22% wireless reduction after mobility auditing. Each must be labeled by bucket.

Frequently Asked Questions

These are the questions finance and Internal Audit ask most about a TEM savings report, answered the way a Controller would want them answered.

Should avoidance appear in the same total as hard savings?

No. Show both, labeled separately, and never blend them into one headline number without a footnote that says which part is cash and which part is prevented spend. The moment they merge, the whole figure inherits the credibility of its weakest line.

How long can a rate reduction count?

Count a rate reduction for as long as the service stays active at the new rate. Stop counting it the moment the service disconnects or the contract changes again. A saving on a service that no longer exists is not a saving.

What baseline should we use?

Use the contracted or previously billed rate on the same service ID. Don’t baseline against a market rate or a list price you never actually paid, because that manufactures savings no invoice ever reflected.

Do category benchmarks like typical year-one TEM reductions help?

Only as context, and only with attribution. Organisations implementing telecom expense management often see 15% to 30% first-year reductions, but that’s a Gartner figure about the category in general, not a RadiusPoint guarantee. Present it as background, never as your own projected result.

Who signs the savings report?

Telecom, or the TEM programme owner, prepares it. Finance validates the material lines against the evidence. Internal Audit may sample. Shared ownership across those three roles is what makes the number credible, because no single party both produces and blesses it.

The short version for finance

Report hard and negotiated recurring savings as your headline, keep avoidance labeled and footnoted, and hand audit a ledger it can re-perform without you.

That discipline is the difference between a number finance defends and one it discounts. Re-sort last quarter’s report into three buckets. Anything without a BAN, service ID, and carrier evidence belongs in a footnote until supported. That is the work RadiusPoint does through ExpenseLogic.

By Sharon Watkins, Founder and CEO, RadiusPoint

A spreadsheet can track what you spent on telecom, but it can’t hold the evidence that proves each charge, records every change, and survives an audit. ExpenseLogic tracks the things a file structurally cannot: MACD ticket history, contract and invoice images, customer service record extracts, dispute packets, and versioned general ledger files, all tied to the billing account number they belong to. That difference is invisible at small scale and decisive the moment a telecom estate grows.

If you’re running telecom expense management in a spreadsheet, you built the right tool for the size you started at. A single owner, a few accounts, one carrier, and a monthly check against last month’s totals is a reasonable system, and for a while it works. The gap doesn’t appear because anyone did the job badly. It appears because the estate outgrew what any file was designed to hold, and the first place it shows up is the evidence you can’t retrieve when someone asks for it.

What spreadsheet TEM actually tracks well

Spreadsheets work for small BAN counts and single owners until concurrency and audit evidence outgrow the file. A billing account number (BAN) or two, one carrier, and one person who knows where everything lives is a system a spreadsheet handles cleanly. It records totals, compares this month to last, and splits a handful of cost centers without much friction. The useful question is when you need TEM, tied to change and evidence.

Tracking gaps after first growth spurt

After growth, spreadsheets lose MACD history, contract images, dispute packets, and versioned GL files needed at month-end close. Each gap is a different kind of missing evidence. MACD history, the record of moves, adds, changes, and disconnects, tells you what changed and who approved it, and a spreadsheet overwrites that with every edit. Contract images, including the letter of agency and negotiated terms, live in someone’s inbox rather than beside the charge they govern. A dispute packet, the bundle of invoice image, customer service record, and notes you send a carrier to win a credit, has nowhere to sit. And the general ledger file that finance needs at month-end close exists in five slightly different saved versions, none of them clearly the current one.

The breaking point is usually concurrency, not size. When more than one person needs the record, the single file stops being a source of truth and becomes a set of conflicting copies. Here’s a short checklist for spotting the breaking point:

• More than one person needs to edit the record in the same week.
• You manage more than a small handful of BANs, or more than one carrier.
• MACD activity happens faster than you can log it.
• Finance asks for the same GL allocation two different ways at close.
• An auditor, or your own CFO, asks for the invoice image or dispute proof behind a line.
• You can’t answer “what changed since last month, and who approved it” from the file itself.

If two or more of those are already true, the spreadsheet has passed its concurrency breaking point, and the cost is no longer convenience. It’s the evidence you can’t produce on demand.

Inventory, contract, and ticket history in one record

ExpenseLogic ties inventory to contracts and MACD tickets so every change leaves a trail spreadsheets cannot guarantee. In ExpenseLogic, RadiusPoint’s platform, a service isn’t a row. It’s a linked record that runs from the inventory of the asset, to the contract that sets its rate, to the MACD ticket that last changed it, to the invoice line that bills it, to the GL code that allocates it. That chain is the whole point, because it lets you trace a single charge backward to the change that created it and forward to the budget it lands in.

Because every link is stored together, ExpenseLogic can answer a question a spreadsheet can only guess at: is this charge valid, given the contract, the inventory, and the last approved change? RadiusPoint uses that same chain to catch a rate that reverted at renewal, a circuit that kept billing after a disconnect ticket, and a line still assigned to an employee who left, because each of those shows up as a break between two links that should agree.

Audit evidence and document recall

Line-item audit needs invoice images, CSR extracts, and dispute notes retrievable by BAN and period. A real audit doesn’t compare totals. It compares each line to the contracted rate and to the customer service record (CSR) extract that shows what the carrier has on file, and when it finds a discrepancy, it assembles the invoice image and the dispute note into a packet the carrier will act on. All of that has to be recallable by billing account number and billing period, months later, when the credit is still working its way through. A spreadsheet stores the number and throws away the proof. ExpenseLogic stores the proof, which is what makes line-item invoice auditing repeatable rather than heroic.

One RadiusPoint client had been paying roughly $18,000 a year for toll-free numbers that no longer routed anywhere. The charge repeated on the invoice for years, so a month-to-month spreadsheet never questioned it. Recovering it took retrieving the invoice image and the inventory record together and asking whether those numbers still did anything. They didn’t, and the only reason anyone could prove it was that the documents were still there to pull.

How RadiusPoint uses ExpenseLogic beyond a tool licence

RadiusPoint staff work invoices, disputes, and tickets inside ExpenseLogic. That’s the difference between buying a platform and buying an outcome. RadiusPoint does that work for you inside ExpenseLogic: validating every line against the contract, filing and tracking disputes until the credit posts, processing MACD tickets, and reconciling wireless serial numbers and Employee IDs against the HR roster so departed employees stop billing.

The results come from the work, not the file. A Fortune 100 manufacturer recovered $450,000 in telecom refunds in its first year with RadiusPoint and roughly $850,000 in ongoing annual savings while managing more than 10,000 wireless devices, and inventory reconciliation on another engagement recovered $174,000 in re-credits. The same record structure carries into utility expense management (UEM, meaning Utility Expense Management), where one multi-location client recovered about $18,000 a year from utilities still billing at closed locations. Whether you’re standing up a new program or moving off a file, the starting point is the same: getting the onboarding data into a record that finally links the pieces.

Frequently Asked Questions

ExpenseLogic answers the tracking questions spreadsheet teams face when history, evidence, and concurrent ownership outgrow one file.

Can I just export from ExpenseLogic to Excel?

Yes. ExpenseLogic exports to Excel, CSV, and PDF whenever you need it, so nobody is trapping your data. The distinction is that an export is a snapshot, while the live record keeps the history, the images, and the links between inventory, contract, MACD ticket, invoice line, and GL code. You can take the numbers to a spreadsheet anytime. What you can’t take is the evidence chain that made those numbers defensible.

When is a spreadsheet actually sufficient?

When the estate is small, stable, and owned by one person: a few BANs, one or two carriers, and little monthly MACD activity. If you can answer what changed and who approved it straight from the file, and no one is asking for invoice images or dispute proof, you’re below the concurrency breaking point and a spreadsheet is a fair tool. The moment two or more of the checklist signals above are true, that stops being the case.

Does this cover utilities and UEM meters?

Yes. ExpenseLogic tracks utility expense management alongside telecom and wireless, including meter-level detail, tariff and rate data, and billing at closed or vacant locations. Because utilities sit in the same record structure as telecom, one reconciliation and one general ledger process cover voice, data, wireless, and facility invoices instead of three separate spreadsheets that never quite agree.

Can it track wireless serial numbers and Employee ID?

Yes. ExpenseLogic stores device detail at the serial-number level and reconciles each line to an Employee ID and the HR roster. That link is exactly where ex-employee lines and zero-use devices surface, because the platform can compare who a line is assigned to against who still works there. A spreadsheet has no reliable connection to HR, which is why those lines keep billing.

If we switch, do we lose our inventory history?

No. Preserving the inventory of record is the whole objective of onboarding, and RadiusPoint rebuilds it from carrier orders, CSRs, and your existing file rather than starting from a blank sheet. If you’re weighing a move, the mechanics of switching TEM without losing your inventory are worth reading before you commit, because a clean transfer is what protects the history you already paid to build.

See what your spreadsheet can’t show you

Every month the evidence stays uncaptured, a dispute window closes on a credit you could have won and a change goes into the estate with no record of who made it. The fix isn’t a better template. It’s a record that links inventory to contract to MACD to invoice line to GL, and a team that works that record for you. Ask RadiusPoint to audit one month of your invoices in ExpenseLogic, and see in specific dollars, with the images to prove it, what your spreadsheet has been unable to track.

By Sharon Watkins, Founder and CEO, RadiusPoint

Multi-carrier TEM works when AT&T, Verizon, and regional carrier BANs share one inventory schema, one audit ruleset, and one GL coding model inside a single estate. The moment each carrier keeps its own spreadsheet language, reconciliation stops being analysis and turns into translation, and the errors that matter start hiding in the gaps between files.

Picture a mid-market company that just acquired a competitor with three sites in another state. Overnight it inherited a regional carrier it had never billed against, a fresh set of billing account numbers, and an accounts payable team now approving invoices in two formats it only half understands. Nothing breaks on day one. The break comes a quarter later, when a disconnected circuit keeps billing and nobody catches it, because that carrier’s invoice lives in its own file and answers to no one. The multi-carrier problem is a data problem before it is a cost problem, and RadiusPoint treats it as one by starting with the billing account number rather than the invoice total.

Why Multi-Carrier Estates Break First at the BAN Layer

Multi-carrier programs break when each carrier’s BAN set lives in a separate file with no shared owner, status, or cost-center map. A BAN, the billing account number a carrier uses to group services under one bill, is the unit everything else hangs from, and once you hold BANs from several carriers, the weakest link is never the biggest bill. It is the small account no analyst was assigned to watch.

The failure mode is predictable. National carriers get attention because their invoices are large and their portals are familiar. Regional carriers arrive through acquisitions, local builds, or a single site only one provider serves, and they slot into a spreadsheet as an afterthought. That spreadsheet has no concept of status, so a circuit that should have been disconnected keeps paying. It has no owner, so no one is accountable when a charge drifts, and no cost-center default, so finance codes it to a catch-all where the variance disappears into overhead.

This is the complexity threshold where a managed telecom expense management program earns its keep. A single carrier can be run out of a well-kept spreadsheet by a diligent person. Three to seven carriers, each with its own billing format and dispute path, cannot, because the human effort scales faster than the savings. The estate does not need more spreadsheets. It needs one schema every carrier’s data is forced to enter.

Normalize National and Regional Invoice Languages

Normalize product codes, tax lines, and service ID formats from AT&T, Verizon, and regional carriers into one ExpenseLogic schema before you compare spend. Carriers do not describe the same service the same way. One labels a charge as network access, another buries it in a bundled feature code, a third splits it across two line items with a surcharge attached. Compare those raw invoices and you are comparing vocabularies, not costs.

Normalization is a ladder, and each rung turns raw billing into something you can audit. No charge reaches your general ledger, the finance system’s chart of accounts, until it has passed every rung.

Only after the ladder is climbed does a line-item telecom audit become possible across carriers, because the audit ruleset now reads one taxonomy instead of five. A rate reversion on a Verizon circuit and one on a regional carrier’s circuit look identical to the ruleset, which is the point. Regional carriers are not worse billers than the nationals. They simply speak a different dialect, and normalization translates it rather than penalizing it.

An Ownership Model for Every BAN in the Estate

Assign a business owner, a telecom owner, and a cost-center default to every BAN so regional accounts cannot bill without an accountable party. Ownership is the control spreadsheets never enforce and the one that quietly saves the most, because an owned account gets questioned and an orphan account gets paid.

The grid below is the artifact that makes this real. Every BAN gets a row, and every row names the same five facts. When a new carrier arrives through an acquisition, it does not go live in ExpenseLogic until its rows are complete.

That last row is why the grid exists. An orphan BAN is not a rare event in a multi-carrier estate; it is the default outcome of acquisition-driven growth unless something forces assignment. Building this census is the first onboarding artifact any serious TEM program should demand, and it should be complete across all carriers before a single invoice is loaded.

A BAN is owned when three roles are named: a business owner accountable for the spend, a telecom owner accountable for the service, and a default cost center for coding. A BAN missing any of the three is an orphan account, and orphan accounts are where regional overbilling lives longest.

One Exception Queue Across Carriers

Run one exception queue ranked by dollars and age so a small regional BAN error does not hide behind national carrier noise. The instinct in a multi-carrier estate is to work each carrier separately, because each has its own portal and dispute process. That instinct is what lets the expensive errors slip, because it ranks work by carrier rather than by impact.

A single queue changes the ordering. Every exception the audit ruleset raises, whatever carrier produced it, lands in the same list, sorted by dollars at stake and how long it has been open. Age matters as much as size, because carrier dispute windows are finite and a correct finding raised too late is unrecoverable no matter how correct it is.

The design has three practical effects. It surfaces a large regional error above a trivial national one, because it ranks money rather than brand. It keeps aging disputes visible so nothing ages past its recovery window. And it gives one analyst a single place to work, so the estate closes from one queue rather than three carrier-specific lists that never agree.

How RadiusPoint Reconciles Multi-Carrier BANs in ExpenseLogic

RadiusPoint consolidates carrier feeds into ExpenseLogic, reconciles BANs to inventory, and produces one audited path to payment and GL posting. The platform holds the schema, the ownership grid, and the exception queue described above, and named people work them. That combination of software and a human on the account is the part a spreadsheet cannot copy.

In practice, ExpenseLogic ingests each carrier’s billing, applies the normalization ladder so AT&T, Verizon, and every regional carrier land in one taxonomy, and matches recurring charges against the inventory of record. Charges that do not match an owned asset become exceptions. A RadiusPoint analyst works that one queue, files disputes through the correct carrier path, tracks each to a credit, and only then releases charges to payment and general ledger posting. The estate closes once, in one file, with one set of cost centers.

This model matters most during change, when multi-carrier estates are most fragile. Acquisitions add carriers and BANs faster than internal teams can absorb them, and a provider transition can quietly lose the inventory that took years to build. The safe path is consolidating carriers without losing your inventory of record, so the BAN census, the ownership grid, and the audit history survive the move. One estate, one schema, one audited path to payment, no matter how many carriers the business collects.

Frequently Asked Questions

Do we need a separate TEM instance per carrier?

No. A separate instance per carrier recreates the spreadsheet problem inside software, because you end up with several systems of record that still have to be reconciled by hand. The value of TEM comes from one estate holding every carrier’s BANs against one inventory, one taxonomy, and one queue. Separate instances just give you separate closes.

How should regional carriers be prioritized?

By spend, site criticality, and invoice complexity, not brand familiarity alone. It is tempting to prioritize the nationals because their names are familiar and their bills are large, but a regional carrier serving a critical plant, or one with a genuinely tangled invoice, often carries more recoverable error per dollar. Rank carriers the way you rank exceptions: by impact.

What about wireless sub-accounts under national carriers?

Treat wireless master accounts and their sub-accounts with the same BAN discipline you apply to fixed services. A master account often hides dozens of sub-accounts, each capable of billing for lines assigned to people who left months ago. Give the master and its sub-accounts owners, statuses, and cost-center defaults like any other BAN. Wireless and fixed spend have their own differences, but the ownership rule does not change.

Can carriers be compared on unit cost easily?

Only after normalization. Raw invoice PDFs are documents, not comparable analytics, so any unit-cost comparison drawn straight from them compares two vocabularies and calls the result a number. Once every carrier’s charges pass the ladder into a shared taxonomy tied to inventory, unit cost becomes a fair comparison. Before that, it is a guess wearing a decimal point.

What is the first onboarding artifact?

Sharon Watkins, Founder and CEO, RadiusPoint

A finance team automates accounts payable, watches invoice processing get faster and cleaner, and assumes telecom spend is now under control. Then an audit finds a circuit still billing for a site that closed two years ago, a rate that reverted at renewal, and a mobile line for someone who left last spring. The AP system did nothing wrong. It processed, coded, and paid exactly what it was designed to process, code, and pay. It just had no way to ask whether those charges should have been on the invoice at all.

Here’s the verdict up front. Keep accounts payable automation for invoice logistics, keep telecom expense management for telecom truth and audit, and integrate the two at the general ledger handoff. AP automation owns capture, routing, coding, and payment. Telecom expense management owns the service inventory, the contract rate audit, line-item validation, and carrier disputes. They aren’t rivals. They’re two halves of one workflow. RadiusPoint runs the telecom expense management half through ExpenseLogic, its proprietary cloud platform, and hands your AP system a coded, audited file it can post without rework.

What AP Automation Does Well for Telecom Invoices

AP automation does the logistics well: it captures telecom invoices, extracts the data, routes them for approval, posts the coding, and pays the carrier. That’s real work, and doing it by hand is slow, error-prone, and expensive. A modern AP platform reads a bill, suggests a general ledger code from vendor history, moves it to the right approver, and releases payment before a late fee lands. For a category with hundreds of monthly invoices from dozens of carriers, that automation is genuinely worth having.

The important thing is to be honest about the boundary of that value. AP automation makes a decided invoice move faster. It doesn’t decide whether the invoice was right. It has no inventory of your circuits, no copy of your carrier contracts, and no mechanism to file a dispute. It trusts the bill and processes it. For most vendor categories that trust is reasonable, because a purchase order and a receipt already vouched for the charge. Telecom is the category where that vouching never happened, which is where the second half of the workflow has to begin.

What Only TEM Can Do

Only telecom expense management builds the service inventory, audits each line against the contracted rate, and disputes wrong charges with the carrier until credits post. This is a different discipline with different reference data. Instead of a purchase order and a receipt, it validates every charge against what services should exist and what those services should cost.

Building and holding that reference data is the hard part, and it’s the reason TEM is a standing function rather than a one-time cleanup. Somebody has to pull carrier service records, reconcile them against invoices and site lists, and then keep the inventory current through every move, add, change, and disconnect. Somebody has to keep the rate table matched to signed contracts as they renew. Somebody has to open a dispute when a charge fails, follow it through the carrier’s process, and confirm the credit actually arrives. None of that is an AP task, and none of it happens by itself. Our guide to when you need TEM walks through the signals that this work has outgrown a spreadsheet and a diligent analyst.

Why Three-Way Match Is Not Enough for TEM

Three-way match needs a purchase order and a receipt to compare against, and recurring telecom services produce neither, so the check has nothing to verify. A monthly carrier bill has no discrete order event and nothing to receive at a dock. The control was built for procured goods, and telecom isn’t procured goods.

Organizations work around this in ways that all leak. A blanket purchase order for annual spend only catches invoices above the blanket, which means it misses almost everything, since nearly every error lives inside the blanket. Two-way match compares a total to an order value and never sees a rate that reverted to list price. Variance monitoring flags a sudden jump, but a ghost charge that has billed steadily for a year reads as the baseline, and nobody questions the baseline. A wrong charge that repeats every month looks identical to a right one under any matching rule. The deeper explanation of invoice audit against three-way match covers why the reference data, not the matching logic, is the thing that fails.

Three-way match asks whether the invoice agrees with the paperwork. A line-item audit asks whether the paperwork was ever right.

A Clean RACI for AP, Telecom, and the TEM Provider

A clean RACI assigns the work so nobody double-owns it: the TEM provider audits, telecom approves service truth, AP processes payment, and finance stays informed. When ownership blurs, charges fall between IT, procurement, and finance, and the reconciliation nobody owns is exactly where the leakage lives. Naming a single accountable role for each task closes that gap.

Read down the first column and the pattern is clear. The TEM provider is responsible for everything upstream of payment, which is truth, audit, and disputes. AP is responsible for everything from approval onward, which is logistics. Finance stays accountable for the numbers landing correctly, and telecom stays accountable for whether a service should exist in the first place. No task has two owners.

How RadiusPoint Hands Work to AP Through ExpenseLogic

RadiusPoint runs the audit inside ExpenseLogic, its proprietary cloud platform, then hands accounts payable a coded file your AP system can post without rework. ExpenseLogic holds the inventory of record and the contract rate table, tests every invoice line against both, and routes failures to RadiusPoint analysts who file disputes with carriers and utility providers. Charges that pass are allocated to cost center, location, and general ledger account, then delivered into your ERP and AP systems. This is additive, not a rip and replace. Your AP automation keeps capturing, routing, and paying, and our invoice auditing services make sure what reaches it is already correct.

The Handoff Contract

The handoff works because both sides agree on a fixed data contract for every line that crosses it. Four fields carry the meaning, and the AP system only ever sees charges that have already cleared the audit.

Agreeing on those four fields is usually the first integration worth building, and the cleaner your TEM onboarding data is, the faster the file starts flowing. Once the contract holds, the verdict takes care of itself: AP automation runs the logistics, telecom expense management runs the truth and the audit, and the two meet at one coded handoff into the ledger.

Frequently Asked Questions

Can we turn off TEM if we buy AP automation?

No, because the two don’t do the same job. AP automation captures, routes, and pays invoices. It has no service inventory and no contract rate table, so it can’t tell whether a telecom charge is legitimate. Turning off telecom expense management leaves you paying wrong invoices quickly and cleanly instead of slowly and manually.

Should TEM pay carriers directly?

It can, through bill pay, but it doesn’t have to. Many clients keep payment in their own AP system and use RadiusPoint only for audit, coding, and disputes. Others let RadiusPoint pay carriers after the audit clears. Either model works, as long as the RACI names one owner for payment.

Where do disputes live?

Disputes live with the TEM provider, not with AP. RadiusPoint opens the dispute, works it through the carrier’s process, and confirms the credit posts. The exception flag on the handoff file keeps a contested line out of the payment run until it resolves, so AP never pays a charge that’s still being challenged.

Who owns vendor master data?

Accounts payable owns the vendor master as the system of record for who gets paid, with finance accountable for its integrity. The TEM provider consults on it, mapping carrier billing accounts to the right vendor records so the coded file reconciles cleanly. Splitting it this way stops duplicate vendors and misrouted payments.

Does this apply to utilities too?

Yes. Utility Expense Management, or UEM, has the same structure as telecom. Electricity, gas, water, and waste bill for recurring service with no purchase order or receipt, and their reference data is a tariff schedule and a meter inventory rather than an order document. The audit and the handoff work the same way.

What is the first integration to build?

Build the coded handoff file first, agreed on the four fields above: BAN, coded amount, exception flag, and period. It’s the smallest change that delivers the whole benefit, because it lets audited charges flow straight into AP. Direct bill pay, deeper ERP feeds, and inventory syncs can follow once that file is reliable.

By Sharon Watkins, Founder and CEO, RadiusPoint

A utility meter inventory is the UEM parallel to a telecom service ID file because both are the authoritative list of every billable identifier an organization pays for, and both are the level where a real audit actually happens. In Telecom Expense Management (TEM), an auditor works from the service ID, the unique number tied to a single line, circuit, or trunk. In Utility Expense Management (UEM), the equivalent unit is the meter. Audit the meters and you’re doing expense management. Pay the account totals and you’re only doing bill pay.

Here’s the thesis in one line: UEM audits at the meter level the way TEM audits at the service ID level, and without a meter inventory of record, utility bill pay is payment, not expense management. That gap has a price. When a site closes or a unit goes vacant and its meter never leaves your inventory, the invoice keeps arriving and finance keeps paying it. At RadiusPoint we run UEM on ExpenseLogic right beside TEM, on one platform, so the same discipline that catches a ghost phone line also catches a meter that should have gone dark months ago.

Key takeaways

• A utility meter is the UEM equivalent of a telecom service ID, the smallest unit a real audit can work from.
• Bill pay without a meter inventory is payment only. Meter-level auditing is what turns it into expense management.
• A meter inventory of record needs six fields at minimum: meter ID, commodity, site, tariff class, status, and cost centre.
• Closed and vacant sites are where a missing meter costs the most, because nobody’s watching an invoice for a location nobody visits.

UEM versus paying the utility bill

Utility Expense Management is the practice of validating utility charges at the meter level, and it’s a fundamentally different job from paying the utility bill. Bill pay is a three-step loop: receive the invoice, code it, remit the payment. It answers one question, whether the bill got paid on time. UEM answers a harder set. Is this meter on the correct tariff class? Does the consumption make sense for this site? Did a charge cross a threshold that signals an error? Is the cost landing in the right cost centre?

Those questions map to three kinds of audit that only exist once you work at the meter level: a contract and tariff rate audit, a consumption-based audit, and a threshold-based audit. None of them are possible from an account total, because a total hides the meter that’s wrong behind the meters that are right. It’s the same reason a telecom invoice total tells you nothing useful until you break it down by service ID. A program that stops at bill pay is paying accurately and auditing nothing. Knowing when a managed expense program earns its keep starts with recognizing that the audit, not the payment, is where the money is.

Why the meter is the service ID of utilities

The meter is the service ID of utilities because it’s the one identifier that ties a physical point of consumption to a rate, an account, and a cost centre, which is exactly what a telecom service ID does for a line or circuit. Every discipline TEM applies to a service ID has a clean counterpart in UEM at the meter. The unit of consumption changes from minutes and data to kilowatt-hours, therms, CCF, and gallons, but the structure is identical: an identifier, a rate applied to it, a volume measured against it, and a cost centre it belongs to.

The tariff class row is where a lot of recoverable money hides. A meter left on the wrong rate schedule after a site’s usage profile changed can overbill for years without ever triggering a late payment. That’s a meter-level finding, and it’s the utility version of a telecom line stuck on an outdated contract rate. RadiusPoint treats it exactly that way through utility rate reclassification, which is only possible when every meter carries its tariff class in the inventory. You cannot reclassify what you have never recorded.

Building a meter inventory of record

Building a meter inventory of record means creating one authoritative list of every meter, reconciled against actual invoices, so no billable point of consumption exists off the books. The build follows the same path as a telecom inventory. You extract every identifier from the invoices, cross-check it against a physical site list, and resolve the two into a single source of truth. In telecom that source is the service ID file. In utilities it’s the meter inventory. The onboarding work that produces a clean TEM data foundation is the direct model for how a meter inventory gets stood up.

At minimum, every meter record in ExpenseLogic captures these six fields.

Closed and vacant sites where meter inventory pays off

Closed and vacant sites are where a meter inventory pays for itself, because a meter that stays active after a location goes dark keeps billing every month with nobody left to review the invoice. This is the utility twin of the ex-employee wireless line no one disconnects. The location is empty, the service is still on, and the charge flows straight through bill pay because it looks exactly like every legitimate invoice. The status field in the inventory is the only thing that catches it, which is why a meter inventory without a status column simply cannot do this work.

Property management feels this most sharply during tenant transitions. A tenant moves out, never transfers the account, and the utility keeps billing the property owner for a unit generating zero revenue. Recovering those charges is the core of vacant utility cost recovery, and it only works when you can prove which meters map to which vacant units. One multi-location RadiusPoint client recovered about $1,500 a month, roughly $18,000 a year, from utilities that were still billing at locations the company had already closed. That money was recoverable for one reason: the meters were in the inventory, flagged by status, and audited against the site list. Without the inventory, those invoices would still be quietly paid.

One ExpenseLogic estate for TEM and UEM keys

Running TEM and UEM on one ExpenseLogic estate means telecom service IDs and utility meters live in the same system of record, audited by the same team against the same rules. Most vendors split these into separate products, which forces you to maintain two inventories, two audit workflows, and two exception queues that never talk to each other. On ExpenseLogic, the service ID file and the meter inventory are two expressions of one idea, a complete list of every billable identifier, each carrying its rate, its status, and its cost centre.

The verdict

The verdict is simple. If you can’t produce a current list of your meters with their commodity, tariff class, status, and cost centre, you don’t have Utility Expense Management, you have utility bill pay. The meter is the service ID of the utility world, the meter inventory is your service ID file, and the audit that recovers real money can only happen at that level. Build the inventory of record first. Everything else in UEM, from rate reclassification to vacant cost recovery, depends on it.

Frequently asked questions

Does UEM mean Unified Endpoint Management here?

No. In this article UEM means Utility Expense Management, the practice of auditing electricity, gas, water, sewer, and waste charges at the meter level. Unified Endpoint Management is a separate discipline in device and IT security that happens to share the acronym. When RadiusPoint says UEM, it always means the utility spend side of ExpenseLogic.

What is a meter inventory of record?

A meter inventory of record is one authoritative, invoice-reconciled list of every utility meter an organization pays for, with each meter carrying its meter ID, commodity, site, tariff class, status, and cost centre. It’s the utility equivalent of a telecom service ID file.

How does a utility meter compare to a telecom service ID?

A utility meter is the direct counterpart of a telecom service ID, since both are the smallest billable unit and the level at which a genuine audit takes place. A service ID ties a rate and a cost centre to a single line or circuit. A meter ties a tariff class and a cost centre to a single point of consumption.

Why do closed or vacant sites cost so much in utilities?

Closed or vacant sites cost so much because their meters often stay active and keep billing long after anyone stops reviewing the invoice. The charge looks legitimate, so bill pay processes it without question. Only a meter inventory with a status field catches it, which is what makes vacant cost recovery possible

Can TEM and UEM run on the same platform?

Yes. RadiusPoint runs both Telecom Expense Management and Utility Expense Management on ExpenseLogic, so service IDs and meters share one system of record, one audit workflow, and one exceptions queue.

By Sharon Watkins, Founder and CEO, RadiusPoint

A Letter of Agency (LOA) should give a telecom expense management partner exactly the carrier permissions the work requires, reading Customer Service Records (CSRs), validating inventory, and filing billing disputes, and nothing more. The authority to order, move, or disconnect services belongs behind your own approval workflow, not in a blanket grant on the LOA. Scope the agency to inquiry and dispute, keep change authority with your named approvers, and RadiusPoint works inside that scope while routing any ordering through ExpenseLogic approval workflows.

An LOA usually lands on a procurement or legal desk in the first weeks of onboarding, and it tends to trigger one of two reflexes: sign it fast because the project is waiting on carrier access, or stall it for weeks because “authorizing a vendor to act with our carriers” reads like handing over the keys. Both miss the same point. An LOA isn’t one switch that’s either on or off. It’s a scoped permission you write, and a safe one separates the right to look and dispute from the right to change and cancel.

Key Takeaways

• An LOA is a permission instrument addressed to the carrier, not a blanket approval for every move, add, change, or disconnect a vendor might propose.
• Separate read and dispute rights from order and disconnect authority wherever the carrier’s process allows.
• Write named account numbers, product families, and expiry dates into the LOA so its scope can’t quietly widen.
• RadiusPoint operates within the LOA limits you set and routes ordering through ExpenseLogic approval workflows you control.

This article describes governance practice, not legal advice. Bring your own legal and vendor management teams into any decision about contract language.

What a Letter of Agency has to unlock for TEM to work

A TEM partner needs carrier permission to pull CSRs, validate inventory, and file billing disputes, which is exactly why an LOA appears during onboarding.

Telecom expense management runs on carrier data the carrier won’t release to just anyone. To audit a bill, an analyst has to read the CSR that shows what’s provisioned, compare it to the inventory of record, and, when a charge is wrong, file a dispute in your name and pursue the credit. None of that works unless the carrier recognizes the analyst as authorized to act on your account, and the LOA is how that recognition happens.

So the real question isn’t whether TEM needs an LOA, it’s which permissions the work actually requires: obtain CSRs and account records, view line and feature inventory, and open and manage billing disputes. These read and remediation rights let a partner find money and recover it, and they map to the material you hand over at kickoff, covered in our guide to the data a TEM onboarding actually needs. Notice what isn’t on the list: the authority to place new orders or cancel existing services.

Ordering rights versus the right to inquire and dispute

Inquiry and dispute agency lets analysts read records and fix bills; ordering rights let someone place or cancel services, and the two shouldn’t be bundled by default.

This is the distinction most LOA templates blur. Agency to inquire and dispute is backward looking: it works on services that already exist, reading them, checking them, challenging the charges. Ordering authority is forward acting: it changes the estate, adding a circuit, moving a line, cancelling a service, each with cost and operational consequences. Carriers often grant both under one LOA because a single broad grant is simpler to administer, but simpler for the carrier isn’t safer for you.

Ask, in writing, for the narrowest grant the template supports. The matrix below splits the four rights that commonly ride on one LOA so you can decide each on its own terms rather than accept them as a bundle. Knowing which to insist on and which to hold back is part of the wider set of questions worth asking a TEM provider before you sign anything.

Reading and disputing a bill can save money without ever changing your estate. Ordering and disconnecting change the estate itself. Grant the first freely, and keep the second on a leash.

Scope clauses that keep a Letter of Agency tight

Limit an LOA by named account numbers, product families, locations, and an end date, and require written change control before anyone widens the scope.

A well intentioned LOA still drifts if it’s written in open ended language. “All accounts, all services, ongoing” is easy to sign and impossible to govern, because nothing in it tells you or the carrier where the authority stops. Tight scope comes from naming things, and five clauses do most of the work.

1. Named billing account numbers. List the specific BANs (Billing Account Numbers) the agency covers rather than authorizing “the account” in general, so a new BAN takes a deliberate addition.
2. Named product families. Spell out which service types are in scope, for example wireline, wireless, or data circuits, so agency over one estate doesn’t silently extend to another.
3. Locations and geography. For a regional estate or a pilot, bound the LOA to named sites or states so it matches the actual work.
4. An expiry date. Tie the end date to the contract term. Open ended agency outlives the relationship that justified it.
5. A change control clause. Require any scope expansion to be requested and approved in writing. This one line stops scope creep, because it turns “widening the LOA” into an event someone has to sign off on.

Getting these drafted, reviewed by legal, and executed with each carrier takes time, so sequence it into onboarding rather than treat it as an afterthought. Our view of a realistic TEM implementation timeline builds LOA execution in as a named step, because carrier turnaround on agency forms is one of the things that most often slows a launch.

Approval workflows that replace blanket ordering rights

Keep every add, move, change, and disconnect inside an ExpenseLogic ticket routed to your named approvers, so the LOA never becomes the only control on ordering.

Here’s the objection behind most broad grants: “if we don’t authorize ordering, how does anything get done?” Fair question. Ordering still happens, it just happens through a control you own rather than a permission you signed away. The LOA gives the carrier a reason to accept an order; your approval workflow decides whether that order should be placed at all.

So every move, add, change, or disconnect (MACD) runs as a ticket. Someone requests the change, the request carries its cost and justification, and it routes to the approver you’ve designated for that cost center or site before anything reaches the carrier. Nothing is ordered on standing authority. RadiusPoint runs this inside ExpenseLogic, so the approval trail and the resulting inventory change live in the same system as the audit. The signals that make this worth formalizing are the same ones that tell you it’s time to bring in a TEM partner: an estate too large and too active to govern by email.

The short version

If you take one thing from this, make it the split. A Letter of Agency should carry the rights that let a partner read your records and fight your bills, and stop there. Ordering, moving, and disconnecting services belong to a workflow with your name on the approvals, not to a broad line in a carrier form. Scope the LOA by named accounts, products, and dates, give it an expiry, and require written change control to widen it. Do that, and you get the operational benefit of agency with none of the exposure of a blank check.

How RadiusPoint honors a scoped Letter of Agency in practice

RadiusPoint works only inside the LOA you sign and routes ordering through ExpenseLogic approval workflows, so changes still require your named approvers, not open carrier access.

RadiusPoint treats the LOA scope you define as a boundary, not a starting point to expand from. Under the agency you grant, RadiusPoint pulls CSRs, loads the provisioned detail into ExpenseLogic alongside your rate tables and inventory of record, validates each invoice line against what’s actually provisioned, and files disputes when a charge is wrong. That read and remediation work runs entirely on inquiry and dispute rights.

When a change does need to happen, a disconnect on a stranded service, a move tied to a real relocation, it doesn’t run on standing authority. RadiusPoint opens a MACD ticket in ExpenseLogic, attaches the cost and the reason, and routes it to the approver you’ve named, so the order reaches the carrier only after your approval posts. ExpenseLogic is the software that finds the exceptions and holds the workflow; RadiusPoint analysts are the people who work the disputes and manage carrier follow through. If you’d like to see a scoped agency run day to day, RadiusPoint can walk your procurement and legal teams through a sample LOA scope and the ExpenseLogic workflow behind it.

FAQ

A Letter of Agency should authorize the carrier access a TEM partner needs to read and dispute, while ordering stays behind your own approval workflow.

Can one Letter of Agency cover every carrier?

Usually not. Most carriers require their own LOA form with their own language, so you’ll sign several. What you keep consistent is the scope: the same rights split, the same named accounts, and the same expiry logic across every form, even when the templates differ.

Does dispute authority require ordering authority?

No. Filing a billing dispute and placing an order are different permissions, and disputing a charge never requires the power to change services. When a template bundles them, ask whether the two can be separated. Many carriers accommodate a read and dispute grant without ordering rights.

What happens when an LOA expires mid contract?

Agency lapses, and with it the ability to pull CSRs or file disputes, which can stall an audit that was working fine the week before. Treat renewal as a calendar item tied to the contract, not a document you go looking for only when something breaks.

Should Legal rewrite the carrier’s template?

Often yes, particularly on scope limits and liability language, where carrier templates tend to be broadest. The one thing to preserve through any rewrite is the operational permission set, the read, inventory, and dispute rights, because stripping those out leaves a TEM partner unable to do the work you hired them for.

Is an LOA required if we only want bills paid?

Bill payment on its own may need remittance setup rather than agency. The moment you want inventory validated, invoices audited line by line, or disputes filed, you’re into work that needs agency-level access, which is where a scoped LOA comes in.

By Sharon Watkins, Founder and CEO, RadiusPoint

To catch a telecom contract before it silently renews, tie three facts together well ahead of the deadline: the term end date, the notice-by date, and the billing accounts and service IDs the contract actually covers. Auto-renewal clauses roll you into another term, often at reverted rates, unless written non-renewal notice lands inside a window that commonly runs 30 to 90 days before expiration. A renewal alert only prevents the lock-in if it reaches a named owner while there’s still time to act.

Most teams treat a contract renewal as a date on a calendar. It’s more accurate to treat it as the last day you had a choice. Up to that day you can renegotiate, switch carriers, or walk away. One day past the notice-by deadline, the same contract becomes a fact you now pay for, usually for another one to three years, and often at a rate nobody agreed to in a meeting. The clause did exactly what it was written to do. The failure was upstream, in whether anyone was watching the date.

How Notice Windows and Auto-Renew Clauses Work

A notice window is the fixed period before your term ends when you must tell the carrier, in writing, that you won’t renew. Miss it, and the auto-renewal clause (sometimes called an evergreen clause) does the rest. The contract rolls into a fresh term automatically, and your right to renegotiate closes with the window.

Four parts of the clause decide how much a missed window costs, and they’re worth reading together.

Two of these bite after the fact. If a renewal reverts pricing to list, your monthly recurring charge climbs the moment the new term starts. And if you try to leave once you’re locked in, the early termination fee usually equals the remaining months of the term multiplied by the monthly charge, plus repayment of any promotional credits, waived installation or discounted hardware from the original deal. The window matters more than the exit: leaving is expensive on purpose, not renewing is free if you act in time.

Why Silent Renewals Still Happen in Mature Estates

Large estates miss deadlines not from carelessness but because the people, records and systems that hold the dates keep drifting apart over time. The bigger and older the estate, the more places a renewal date can hide. Four failure modes account for most of it.

• Owner attrition. The person who signed the contract has left, and the carrier’s renewal reminder still routes to a mailbox nobody reads. The date exists; the reader doesn’t.
• BAN sprawl. Billing account numbers multiply across carriers, regions and acquisitions until no single list maps contracts to what’s actually billing. You can’t defend a deadline you can’t find.
• PDF-only storage. The contract lives as a scanned PDF in a shared drive, with the notice-by date trapped inside a clause no system can read, sort or alert on.
• Missing ETF awareness. Nobody knows what leaving would cost, so even a renewal that’s caught in time gets rubber-stamped rather than challenged.

Every one of these is a records failure, not a judgment failure. The managers involved are perfectly capable of making the call. They just never got a prompt they could act on, attached to information they could trust. That crossover, where manual tracking stops scaling, is when telecom expense management starts to pay for itself.

A Practical Notice-Window Calendar for Telecom and Procurement

A working renewal calendar counts backward from the term end and assigns a named owner an action at each staged deadline before notice closes. The moment you sign, record the term end date and count back from there. Staged alerts turn a single terrifying deadline into a sequence of small tasks. Recording the dates this early also feeds renewals into demand planning and forecasting, so each decision lands inside the budget cycle.

• 120 days out. Pull the contract, confirm the notice window and the exact delivery method, and start a vendor performance review.
• 90 days out. Decide: renew, renegotiate or exit. If you’re renegotiating or leaving, get competing quotes now, while the carrier still has a reason to compete.
• 60 days out. If you’re not renewing, draft and send written notice by the method the clause requires. Don’t wait for the last legal day.
• 30 days out. Confirm the carrier acknowledged the notice in writing. If it’s silent, escalate before the window shuts.

The calendar only works if each contract carries the same small set of fields. At a minimum, every tracked contract needs five.

• Term end date. The day the current term expires.
• Notice-by date. The last day written non-renewal notice can land, counted back from the term end.
• Owner. One named person accountable for the decision, not a shared inbox.
• BAN list. The billing account numbers and service IDs the contract covers.
• Delivery method. Exactly how notice must be sent, whether that’s certified mail, a carrier portal, or a registered address named in the clause.

Inventory Linkage That Makes Alerts Actionable

An alert only helps if it names the billing accounts and service IDs it covers, so you know exactly what a renewal locks in. A reminder that reads “Carrier X master agreement expires” is nearly useless across a real estate. It doesn’t tell you which circuits, sites or lines it governs, so you can’t price the decision. Tie the notice-by date to the BANs and service IDs, and the same alert now shows what’s at stake and what walking away would actually mean.

Inventory linkage also catches the failure that a calendar alone never will. When a negotiated rate expires and the account quietly returns to list price, the renewal date can pass on time and the overbilling still starts. The only thing that catches rate reversion is a line-item comparison of each invoice against the contracted rate table, which is the discipline of a continuous invoice audit rather than a diary entry. That verified inventory is also the difference between switching TEM without losing inventory and starting over blind.

How RadiusPoint Surfaces Obligation Alerts

RadiusPoint stores each contract, its expiration and its notice-by date inside ExpenseLogic, tied to the same inventory its analysts audit every billing cycle. The contract management module holds the contract image, the expiration date and the negotiated rates against service IDs, and it raises obligation alerts covering both termination fees and dates. Those alerts route to a named owner rather than into the void.

Because the platform audits every invoice line against the contracted rate table each cycle, a rate that reverts at renewal gets caught as a billing exception, not just as a date that passed. Software surfaces the alert; a named RadiusPoint analyst works it, files disputes when a rate slips, and pursues credits until they post. In one case, a client recovered $120,000 a year once contract rates were tied to service IDs and audited every cycle, a figure specific to that estate rather than a number to expect. This is what continuous telecom expense management does that a spreadsheet cannot. The questions worth asking any TEM provider start with how they tie contract terms to inventory and who works the alert.

The Verdict

Catching silent renewals is a records problem, not a negotiation problem, and it’s solved before the notice window opens, not after it closes. Every term that renews unwatched is another one to three years at a rate you never tested against the market, plus an early termination fee if you try to leave. The fix costs far less than a single missed window: put every contract’s term end, notice-by date, owner and BAN list in one place, and alert the owner while there’s still room to act. Ask RadiusPoint to inventory your contracts and set the alerts against the services they cover.

Frequently Asked Questions

These are the questions procurement and telecom managers ask most often when they start tracking telecom contract notice windows and non-renewal deadlines seriously.

How do I find the notice window in a telecom contract?

Read the clause, not the pricing page. Look in the general terms and conditions for language like “automatic renewal,” “renewal term” or “automatic extension,” then confirm the exact number of days and the required delivery method.

How should I send a non-renewal notice?

Send it exactly the way the clause specifies, which is often certified mail or a named carrier portal, and treat the send as a task rather than a memory. Record the tracking number, the date, and the carrier’s written acknowledgment. If the clause requires certified mail and you email it instead, the carrier can treat the notice as never given.

Who should own catching renewals, finance or procurement?

Finance sees the spend, but procurement or the telecom team executes the notice, so the owner has to be whoever can actually send it and run the negotiation. A dashboard that finance watches and procurement acts on works only if one named person is accountable for the decision on each contract.

When should I start renegotiating?

Before the notice-by date, not the term end. Once the window closes, you’ve renewed, and your negotiating position is gone for another full term. Starting at 90 to 120 days out gives you time to gather competing quotes while the carrier still competes for your business.

Do wireless contracts need the same notice discipline?

Yes. Wireless agreements carry the same auto-renewal and notice mechanics as wireline, and they change faster because lines and devices turn over constantly. Applying the same term-end, notice-by and owner tracking to managed mobility keeps mobile contracts from renewing on stale line counts nobody reconciled.

By Sharon Watkins, Founder and CEO, RadiusPoint

Voice wireline and data circuits move through the same telecom expense management lifecycle, but they cannot share one inventory key. Voice keys on telephone numbers under a billing account number. Data keys on circuit IDs, bandwidth, and location pairs. Run both on one platform with category-correct keys, and finance gets a single audit trail while telecom keeps accurate inventory.

The confusion rarely surfaces until month-end. A controller pulls one telecom accrual, ties the voice invoices to a phone-number list, then runs the same match against the data invoices and finds that nothing lines up. Circuit invoices do not carry phone numbers. They carry circuit identifiers, bandwidth tiers, and the two addresses each circuit connects. The two spend types belong to one discipline, yet they are keyed, contracted, and audited differently, and treating them as a single list is exactly where reconciliation breaks.

Key Takeaways

• Voice keys on telephone numbers under a BAN; data keys on circuit IDs, bandwidth, and location pairs.
• Voice uses seat or line rates; data uses port, loop, and committed bandwidth terms.
• Voice audits features and usage; data audits installed versus billed service and MRC variance.
• RadiusPoint runs both categories in ExpenseLogic with category correct keys and shared GL output.

One lifecycle, two inventory keys: where voice and data split

Both voice wireline and data circuits run the same four stages of order, inventory, invoice audit, and pay, but voice keys on telephone numbers while data keys on circuit identifiers and endpoints. The lifecycle is what makes them one discipline. The inventory key is what makes them two problems inside it. A voice line is identified by its number, grouped under a billing account number (BAN), and described by its feature set. A data circuit is identified by a circuit ID, sized by committed bandwidth, and defined by the two locations it joins, the A end and the Z end.

That single difference cascades through every later stage. It changes what the order confirms, what the inventory of record stores, what the audit tests, and what accounts payable is being asked to approve. Deciding whether that lifecycle belongs in-house or with a provider is a separate question, covered in our guide on when you need TEM. The keying difference below applies either way.

A voice audit asks whether the number should still exist. A data audit asks whether the circuit was ever installed at the bandwidth you are paying for.

Voice wireline expense management: auditing numbers under a BAN

Voice wireline expense management tracks numbers, features, and usage against contract rates under each billing account number before accounts payable releases the invoice. The unit of work is the telephone number. Every number rolls up to a BAN, every BAN rolls up to a carrier contract, and the audit tests each number against the rate and feature set that contract actually specifies.

The errors cluster in predictable places. Features billed per line and applied estate-wide long after anyone used them. Lines that survive a role change or an office move because nobody cancelled them. Long-distance and usage charges that drift above the contracted rate. Rates that revert to list pricing at renewal because the amendment was never loaded into the rate table. None of these are exotic. They persist because a manual reviewer cannot test hundreds of numbers against contract terms every cycle, so the invoice gets approved on its total rather than its lines. A line-item audit reverses that default, testing each number before payment rather than sampling after it. The mechanics of that recurring test are set out in our telecom audit services overview.

Data circuit expense management: auditing IDs, bandwidth, and endpoints

Data circuit expense management validates circuit IDs, bandwidth, locations, and monthly recurring charges against the inventory of record and the contract. Here the unit of work is the circuit, and the reference data is harder to hold. A circuit does not announce itself with a phone number. It appears on the invoice as an identifier, a bandwidth level, a pair of addresses, and a monthly recurring charge, and every one of those has to match a maintained inventory record for the charge to be legitimate.

Data circuits also fail in a way voice lines rarely do: they keep billing after they are gone. A disconnected MPLS or SD-WAN circuit that was ordered off but never confirmed off will bill for months, because the carrier’s billing system and the client’s inventory are not the same record. Bandwidth is a second recurring problem, where a circuit contracted at one tier bills at another, or a port charge outlives the loop it supported. Closed and relocated sites produce a third, with circuits still charging monthly recurring cost at addresses the business has vacated. Catching these means testing installed against billed, checking mileage or MRC variance, and matching every circuit ID on the invoice to a circuit in inventory. The full validation sequence sits in our invoice auditing services.

Align five fields, and one close covers both categories

Controllers and telecom teams can keep category-correct keys and still close as one, provided five fields are identical across voice and data. The keys diverge on purpose: a number is not a circuit ID and should not be forced into the same field. What has to match is the connective tissue that lets both categories feed a single accrual and a single general ledger interface. Align these five, and the difference between a number and a circuit ID stops mattering to finance. The comparison logic that separates wireless keying from wireline keying is developed further in our note on wireless versus telecom expense management.

The Shared-Close Rule. Five fields controllers require identical across both categories, even when the inventory keys differ:

1. Billing account number (BAN). The account each service rolls up to, so voice and data on the same account reconcile to the same payable.
2. Service ID type. A single field that flags whether the record is keyed by number or by circuit ID, so both resolve through one logic rather than two spreadsheets.
3. Site or location code. The shared address key that lets a closed location surface every voice line and every circuit billing against it at once.
4. Cost center. The allocation target, identical in structure across categories, so chargeback and GL coding do not fork by spend type.
5. Contract rate reference. The pointer to the contracted rate or bandwidth term, so every line is testable against what was actually agreed.

Why RadiusPoint runs voice and data on one ExpenseLogic estate

RadiusPoint manages wireline voice and data circuits in one estate on ExpenseLogic, so finance gets one audit trail while telecom keeps category-correct inventory keying rules. ExpenseLogic holds the rate table, the inventory of record, and the invoice history for both categories in a single system, keying voice on telephone numbers under each BAN and data on circuit IDs, bandwidth, and location pairs. ExpenseLogic validates every invoice line against the contracted rate, the provisioned service, and the applicable tax treatment each billing cycle. RadiusPoint analysts file disputes directly with carriers under a letter of agency, pursue each case until the credit posts, and update the inventory of record as moves, adds, changes, and disconnects occur. ExpenseLogic then feeds allocated, coded charges into the client’s ERP and accounts payable systems from one close.

The cost of not doing this compounds monthly. Every cycle a data estate goes unaudited, disconnected circuits keep billing at full monthly recurring charge and closed-location circuits keep posting to live cost centers. Every cycle a voice estate goes unaudited, reverted rates and orphaned features bill again at the same amount they billed last month. A one-time sweep converts that history into a refund. A continuous audit converts the same analytical work into error that never reaches an invoice, which is money kept rather than money recovered.

Ask RadiusPoint to audit one month of your wireline voice and data invoices on ExpenseLogic, and see how many circuit IDs and telephone numbers on your current bill no longer match your inventory of record.

FAQ

Voice and data should share one TEM platform while retaining category specific inventory keys.

Should voice and data have separate TEM tools?

Separate tools multiply GL and inventory reconciliation. Prefer one ExpenseLogic platform with different keys for each product family.

Where does wireless fit in this comparison?

Wireless is a third keying model based on device and Employee ID. It should not be forced into voice or circuit inventory.

What breaks first when keys are mixed?

Data circuits billed like phone lines, or voice features lost inside circuit summaries, create false inventory and unreliable reconciliation.

Do MACD workflows differ?

Yes. Voice MACD often means feature or number changes. Data MACD means bandwidth, demarcs, and install verification.

Can one LOA cover both?

Scope carefully by product family. Ordering rights for circuits are not the same as ordering rights for voice lines.

By Sharon Watkins, Founder and CEO, RadiusPoint

A Customer Service Record (CSR) is the carrier’s record of what it has provisioned on your account, every service and feature, line by line. A telecom invoice is narrower: the carrier’s demand for payment this period, with that detail compressed into totals. So a real audit starts from the CSR, not the bill, which is why RadiusPoint pulls CSRs into ExpenseLogic and tests each invoice line against what is actually provisioned.

Here’s how it usually surfaces. Someone in finance questions a charge on a telecom bill, a feature that’s been riding the same account for years, and the invoice can’t answer because it never itemized the feature. It rolled the cost into a monthly total and moved on. Pull the CSR, and the feature is right there: provisioned on a specific line, tagged with the order code that put it there and the date it went live. The bill wasn’t hiding it out of malice. It was never built to show you what you’re paying for. The CSR was.

Key Takeaways

• The CSR is the carrier’s view of what’s provisioned. The invoice is the carrier’s view of what to collect this period. They are not the same document, and they don’t carry the same detail.
• Features, USOC order codes, hunting arrangements, and directory listings routinely appear on a CSR while the invoice shows only rolled totals.
• Inactive and pending-disconnect services can sit on a CSR for months and keep generating charges the invoice never flags.
• RadiusPoint loads CSR detail into ExpenseLogic so analysts can match every invoice line to true provisioned inventory.

Payment document versus provisioning document: what each one is really for

Invoices exist to collect payment for a period. CSRs exist to document how the carrier has provisioned your services and features. That single difference in purpose explains almost everything a CSR reveals.

An invoice is a billing artifact. It’s built to state a balance due and get it paid, so it favors a total over transparency. It summarizes, groups, and reprints last month’s recurring charges without re-explaining them. That isn’t deceptive. It’s just what a payment document does.

A CSR is a provisioning artifact. It records exactly what the carrier has turned on: which lines exist, which features sit on each one, how calls hunt between them, which listings are published, and what status each service is in. It’s written in carrier code, which is why it’s rarely read, but it’s the closest thing to ground truth a carrier will hand you.

The invoice tells you what to pay. The CSR tells you what you’re paying for. Auditing the first without the second is checking arithmetic you can’t actually see.

This is why a line-item audit can’t run on invoices alone, and why our overview of invoice auditing services treats the provisioning record, not the bill, as the reference data every charge gets tested against.

The CSR hidden five: detail your invoice quietly compresses into a total

CSRs commonly reveal feature codes, hunting configurations, directory listings, and service status flags that monthly invoices compress into opaque totals. Five categories account for most of what goes unnoticed.

1. Features and USOC codes. Each feature is provisioned with a Universal Service Order Code (USOC) and billed per line. Voicemail, call forwarding, caller ID, and legacy add-ons can persist for years. The invoice shows a feature total; the CSR shows which features, on which lines, at what rate.
2. Hunting arrangements. Hunting defines how an unanswered call rolls to the next line in a group. It carries its own charges and routinely outlives the phone system it was built for. Invoices don’t describe hunt groups. CSRs do.
3. Directory listings. Published, non-published, and additional listings each carry a recurring charge. A company can pay for listings tied to departments or locations that closed long ago, and never see them itemized on a bill.
4. Service status flags. A CSR records whether a service is active, pending, or disconnecting. That status is the difference between a charge you should pay and one you shouldn’t, and the invoice carries none of it.
5. Pending and stranded disconnects. A service ordered off but never confirmed off can sit on the CSR in a limbo state, billing every cycle. The bill looks unchanged, which is exactly the problem.

Reading these categories against the bill is the core of what a real audit does, and it’s the reason our telecom audit services reconstruct the CSR before testing a single invoice line.

How a hidden CSR line turns into paid waste

When CSR lines stay active after a site closes or an employee leaves, the invoice keeps charging while accounts payable has no inventory flag telling it to stop. The waste is quiet, and it compounds.

Consider the mechanics. A location shuts down. The lease ends, the staff move, the lights go off. The telephone lines and features provisioned to that address, though, don’t disconnect themselves. Unless someone issues a disconnect order and confirms it posted, those services stay on the CSR, and every charge tied to them keeps flowing onto an invoice that gets approved on its total. Accounts payable pays it because nothing on the bill says the site is gone. Nothing on the bill ever could.

The same pattern hits individual services: a feature nobody uses, a line assigned to a role that no longer exists, a listing for a merged division. Each one is small. Each one recurs. And because the invoice reprints the total rather than re-justifying the line, the charge renews month after month with no natural moment of review. A CSR-driven audit creates that moment on purpose, and when it finds a service that should have stopped billing, the next step is recovering what was already paid. That recovery work is described in our note on telecom refunds and cost avoidance.

How finance and telecom should read a CSR together

Finance should learn which CSR fields drive cost, while telecom owns service status and change activity, so both teams share one interpretation of the same record inside ExpenseLogic.

The two teams read a CSR for different reasons, and both readings matter. Finance cares about the fields that map to money: the billing account number a service rolls up to, the cost center it should be allocated to, the rate each feature carries, and the tax jurisdiction that applies. Telecom cares about the fields that describe reality: which services are active, what’s pending a move, add, change, or disconnect (MACD), and whether the provisioned configuration still matches how the business actually operates.

Neither reading is complete alone. Finance can flag a charge that looks wrong but can’t say whether the underlying service should exist. Telecom knows the service should be gone but doesn’t see it hitting a live cost center every month. Put both readings on the same record, and a stranded line becomes visible from two directions at once. Turning that shared reading into a maintained system, rather than a one-time exercise, is the subject of our guide to building a telecom inventory of record from carrier CSRs.

The short version

If you remember one thing, make it this: the bill is not the inventory. A telecom invoice tells you what a carrier wants paid. A CSR tells you what the carrier has actually provisioned, and the gap between the two is where overcharges live. Start every audit from the CSR, reconcile the invoice to it, and the questions your bill can’t answer suddenly have answers.

How RadiusPoint turns CSR insight into audit action

RadiusPoint compares CSR extracts to invoices and contracts inside ExpenseLogic, then opens disputes or disconnect tickets on anything that shouldn’t be billing. Software finds the mismatch; people resolve it.

RadiusPoint requests CSRs from each carrier under a letter of agency and loads the extracted detail into ExpenseLogic alongside the rate table, the inventory of record, and the invoice history. ExpenseLogic validates every invoice line against the provisioned service, the contracted rate, and the applicable tax treatment each billing cycle. When a charge has no matching CSR line, or a CSR line carries a status it shouldn’t, ExpenseLogic flags the exception and RadiusPoint analysts take it from there, filing disputes with the carrier, pursuing each case until the credit posts, and issuing disconnect orders on services that should have stopped. RadiusPoint updates the inventory of record as moves, adds, changes, and disconnects occur, so the next cycle starts from an accurate baseline rather than repeating the same finding.

The result is one audit trail for finance and one accurate provisioning record for telecom, drawn from the same source. RadiusPoint runs this as a continuous managed service rather than a one-time sweep, which converts the analytical work from money recovered after the fact into error that never reaches an invoice.

Ask RadiusPoint to pull one month of CSRs against your current telecom invoices in ExpenseLogic, and see how many provisioned lines and features on your bill no longer match anything your business still uses.

FAQ

A CSR is the carrier’s provisioning record, and it belongs at the start of any telecom audit, not the invoice alone.

Is a Customer Service Record a free document?

It depends on the carrier. Some deliver a CSR electronically at no charge, others treat it as a special request. Access is a right you can scope through a letter of agency (LOA), so build CSR retrieval into the LOA rather than negotiating it case by case.

How is a CSR different from a bill of materials?

A CSR is the carrier’s record of provisioned telecom services and features. A bill of materials is a manufacturing and project term for the components that make up a product. The language overlaps in equipment or installation contexts, but for recurring telecom service the document you want is the CSR.

Can electronic bills replace CSRs?

No. E-bills improve how the invoice is delivered and formatted, which helps processing, but they don’t add provisioning detail. An e-bill is still a payment document. It won’t show you feature-level configuration or service status the way a CSR does.

How often does a CSR change?

Any move, add, change, or disconnect can change it. Treat a CSR as a snapshot, not a permanent truth: re-pull it after major changes and on a scheduled refresh, so your inventory of record keeps pace with what the carrier has actually provisioned.

Does wireless have a CSR equivalent?

Not by that name. Wireless carriers provide account and line-level detail extracts that serve a similar purpose, with different field names and structure. Treat them as inventory sources for the wireless estate and reconcile them the same way, invoice line against provisioned record.

By Sharon Watkins, Founder and CEO, RadiusPoint

Controllers use a TEM GL interface file to turn a month of audited telecom charges into one pre-coded batch the ERP can post in minutes, instead of a stack of invoices someone keys by hand. The file is the finished output of telecom expense management (TEM): every charge has already been checked line by line, mapped to a general ledger account, and tagged to a cost centre. By the time it reaches your close, the coding decisions are done and the disputes are flagged. What lands in the ERP is a reviewed subledger feed, not a pile of PDFs.

Key takeaways

• The GL interface file is the audited product of TEM, not an invoice dump. Each line carries the billing account number, service period, amount, GL account, and cost centre.
• It belongs early in the close, after the audit finishes and before journals lock, so telecom posts alongside every other subledger.
• Clean lines flow straight through; exception lines route to an accrual or a hold, so one disputed charge can’t stall the close.
• RadiusPoint generates the file from ExpenseLogic after line-item audit, so your team posts a reviewed file rather than coding carrier bills.

The short version: an audited, pre-coded GL file lets you post telecom like any other subledger. Clean lines flow through, exceptions get handled on the side, and the work that makes the file trustworthy (the audit and the coding) happens before it ever reaches your ERP.

What’s Actually Inside a TEM GL Interface File

A TEM GL interface file lists every audited telecom charge with its billing account number, service period, amount, GL account, and cost centre for posting.

Start with the fields, because they’re what make the file postable. Each row typically carries the billing account number (BAN), which is the carrier’s account identifier and the anchor for tracing a line back to its source invoice. Alongside it sit the service period the charge covers, the audited amount, the GL account it maps to, and the cost centre or allocation string your organization uses to push spend to the right department, location, or entity.

The file separates into two kinds of rows, and controllers should treat them differently. Clean lines are charges that passed audit and matched contract, plan, and inventory. They’re ready to post with no human touch. Exception lines are charges that failed a check: a rate that doesn’t match the agreement, a service billed after disconnection, a new line nobody ordered, a credit still pending. These don’t get suppressed. They get marked so finance can decide whether to accrue, hold, or post with a note.

Where the GL File Lands in Your Close Calendar

Controllers load the GL file early in the close, after the audit finishes but before journals lock, so telecom posts with other subledgers on time.

Timing is where a good file earns its keep. Telecom is a recurring, high-volume expense that arrives on the vendor’s schedule, not yours, so it has a habit of showing up late and forcing a last-minute manual journal. Placing the feed deliberately fixes that. Below is a Close-Calendar Placement Map most finance teams can adapt to their own cycle.

Handling Accruals and Exception Lines Without a Pile of Manual Journals

Clean lines post straight to the general ledger; exception lines route to an accrual or hold, so the close isn’t blocked by one disputed charge.

This is where the interface and the accrual do different jobs, and it’s worth being precise. The interface file is the posting mechanism for real, audited spend in the period. An accrual is your estimate for spend that belongs to the period but isn’t cleanly billable yet, usually because an invoice is late or a charge is under dispute.

A well-built feed supports both. Clean lines give you the confirmed base. Exception lines give you the accrual candidates, already itemized, so your accrual isn’t a round-number guess. Instead of accruing “telecom, roughly the usual,” you accrue the specific held lines with their amounts and reasons attached. When the dispute resolves or the credit posts, it flows through a later file and the accrual reverses against something concrete.

Balancing matters here too. Before anything posts, the file should tie to the source invoices it was built from, so the total you book reconciles to what carriers actually billed, net of audited adjustments. That reconciliation is what lets you sign the close knowing the telecom line is defensible, not approximated. RadiusPoint’s invoice auditing services are what produce that audited base in the first place, which is why the exception lines are trustworthy rather than arbitrary.

The Controls That Keep the TEM Feed Trustworthy

Feed controls cover versioning, balancing to source invoices, restricted access, and a named coding owner, so the file you post is the file you audited.

A GL feed is only as good as the controls around it, because it writes directly into your books. Use a TEM Feed Control Checklist and run it every period:

1. Versioning. Every generated file is versioned and archived. If a correction is needed, you produce a new version rather than editing the posted one, and you can always show which file backed which journal.
2. Balancing. The file totals reconcile to source invoices and to the amounts audited before import. No line posts that can’t be traced to a BAN and a service period.
3. Access. Only named roles can generate, approve, and import the file. The person who audits isn’t automatically the person who posts.
4. Coding owner. One owner is accountable for the GL account and cost-centre mapping. When the mapping changes, that owner signs off before the next file uses it.

The mapping itself is set up once and maintained deliberately, not reinvented monthly. Most of that structure gets defined during onboarding, when your chart of accounts and cost-centre logic are captured. If you want to see what that setup involves, RadiusPoint documents the inputs in its TEM onboarding data requirements, and the sequence in its TEM implementation timeline.

How RadiusPoint Produces a GL-Ready File from ExpenseLogic

RadiusPoint produces the file inside ExpenseLogic after line-item audit, mapping each charge to your chart of accounts, so your team posts instead of coding.

Here’s the part that separates a real GL feed from a spreadsheet export. RadiusPoint audits every invoice line first: rate against contract, service against inventory, plan against usage. Only then does ExpenseLogic assemble the audited charges into a file coded to your GL accounts and cost centres. The output is GL-ready because the review and the coding are already finished by the time it’s generated.

ExpenseLogic covers telecom, wireless, and utility expense management (UEM) on one platform, so the same audited-then-coded logic applies across all three categories and lands in a consistent file rather than three different formats. That single unified feed is easier to control and easier to reconcile.

And it’s software plus people, not software alone. The platform builds and balances the file, but a RadiusPoint analyst works the account, resolves disputes with carriers, and confirms the exception lines make sense before the file reaches finance. Automation handles the volume; a named human handles the judgment. That combination is what lets your controller treat telecom as a clean subledger instead of a monthly investigation.

Frequently Asked Questions

Is the GL interface file the same as an accrual?

No. The interface file posts confirmed, audited spend for the period. An accrual estimates spend that belongs to the period but isn’t cleanly billable yet. The file’s exception lines feed the accrual, so your estimate is itemized rather than a round number.

Doesn’t AP automation already do this?

AP automation routes and pays invoices, but it approves recurring telecom charges by default because there’s usually no purchase order or goods receipt to match against. It doesn’t audit the line against contract, plan, or inventory. The TEM feed adds that audit and the GL coding before anything posts.

What happens when our GL structure or cost centres change?

The coding owner updates the mapping and signs off before the next file uses it. Because the mapping lives in ExpenseLogic and is versioned, the change is applied once and carries through every future file, rather than being re-keyed each month.

Who signs off on the cost-centre coding?

A single named coding owner on the finance side is accountable for the GL account and cost-centre mapping. RadiusPoint proposes the mapping from your chart of accounts during onboarding, and your owner approves it, so accountability stays in-house.

How far before close should the file arrive?

Ideally before the close opens, so clean lines post early and exceptions get worked mid-close rather than at the deadline. The earlier the audited file lands, the less telecom shows up as a last-minute manual journal.

The Verdict

A TEM GL interface file is what lets a controller stop treating telecom as a monthly fire drill and start treating it as a subledger. Audited lines, pre-coded to your accounts and cost centres, post like everything else. Exceptions get accrued or held with specifics attached. The file balances to source and stays versioned, so the close is defensible. RadiusPoint builds that file from ExpenseLogic after a real line-item audit, which is the difference between posting numbers you trust and coding invoices you hope are right. If you’re evaluating whether a provider can deliver a genuinely GL-ready feed, the questions to ask a TEM provider are a good place to start.

By Sharon Watkins, Founder and CEO, RadiusPoint

Open a telecom invoice and almost every line below the plan rate wears the same official costume: a tax, a fee, or a surcharge with a government-sounding name. The quiet assumption in most accounts payable departments is that all of it is mandatory and none of it can be questioned. That assumption is where the money leaks.

Here is the direct answer. A telecom tax and surcharge audit checks each bill line against statute, tariff, and contract so finance pays only the charges that truly belong. Not every line labeled “tax” or “surcharge” is a statutory obligation. A real audit separates three things carriers print in one indistinguishable block: statutory taxes set by law, carrier surcharges permitted by a tariff or your contract, and discretionary fees a carrier chose to pass through. RadiusPoint runs that separation as a line-item audit inside ExpenseLogic, flagging what does not belong before the payment goes out, not months later in a recovery sweep.

This is audit guidance, not legal or tax advice. Jurisdiction rules differ and change, so the method below is about classification and proof, not a ruling on any specific statute.

Key takeaways

These points sum up how a telecom tax and surcharge audit separates mandatory charges from questionable ones and turns exceptions into recoverable credits for finance.

• Statutory taxes, permitted surcharges, and discretionary fees are three different classes. Treating them as one “tax” bucket is what hides recoverable errors.
• Contract language and jurisdiction rules decide what belongs. The label a carrier prints on the line is not proof.
• A line-item audit in ExpenseLogic lets RadiusPoint analysts challenge miscoded surcharges before the charge posts to the general ledger.
• Every dispute needs the account number, service ID, charge code, and billing period documented, so a credit can be proven to finance later.

The three charge classes hiding on every telecom invoice

Telecom invoices mix statutory taxes, carrier surcharges allowed by tariff or contract, and discretionary fees, and each class deserves its own audit test. Bundle them into a single “taxes and fees” total and you lose the ability to challenge the one class that is actually challengeable.

Statutory taxes are levied by federal, state, or local government. Federal excise tax, state and local telecom taxes, and E911 or 988 charges that fund emergency systems all sit here. They are set by law, they vary widely by jurisdiction, and a carrier cannot waive them.

Permitted carrier surcharges are cost-recovery line items a tariff or your signed contract authorizes. Some, like the Federal Universal Service Fund pass-through, are tied to a government program yet still applied at the carrier’s discretion in how much they recover and how. That discretion is exactly what makes them auditable.

Discretionary fees are the carrier’s own pricing decisions dressed in regulatory language. “Regulatory cost recovery,” “administrative fee,” and “cost assessment” lines usually fall here. They are not government taxes even though they share the block, and they are the first place a line-item invoice audit earns its keep.

What “belongs on the bill” actually means

A charge belongs when law or the signed contract authorizes it for that service, jurisdiction, and period, and everything else is an exception worth challenging. “Belongs” is not a feeling about whether a fee looks official. It is a test with a yes or no answer for each line.

The failure mode is treating the invoice label as the authority. A line reading “state regulatory fee” is a claim by the carrier, not evidence the fee applies to your service type in your jurisdiction for the month billed. The proof lives in the statute, the carrier’s filed tariff, and your contract, not in the description field. RadiusPoint validates each line against the inventory of record and the contract inside ExpenseLogic, which turns a vague “that looks high” into a specific, defensible exception during a line-item telecom audit.

The Belongs Test: four questions before you pay

Run every questioned line through four questions. A “no” on any one of them makes the charge an exception to hold and document.

1. Law: Does a federal, state, or local statute require this charge for this service? If it is a tax, you should be able to name the authority.
2. Tariff: Is the surcharge in the carrier’s filed tariff at the rate and basis billed?
3. Contract: Does your signed agreement permit this charge, or does it cap or exclude it?
4. Service type: Does the charge match the actual service? Wireless, wireline, and data carry different rules, so a fee valid on one can be wrong on another.

How to run a surcharge audit without stalling accounts payable

Sample the high-variance charge codes first, hold only the disputed lines, and keep undisputed taxes moving so month-end close still finishes on time. An audit that freezes the whole invoice to argue over one surcharge creates more damage than the surcharge did.

The workable split is simple. Undisputed statutory taxes and clearly authorized surcharges flow through to payment on schedule. Only the questioned lines get held, ticketed, and worked. That keeps the AP cycle intact while the audit runs in parallel instead of in the critical path.

This is also where automation gets oversold. Three-way match confirms that an invoice ties to a purchase order and a receipt, but telecom tax and surcharge codes rarely map to a PO line, so the match passes them straight through. That gap is the whole reason invoice audit and three-way match are not interchangeable. Pair the PO-level control with a line-item audit that actually reads the tax and surcharge block.

The evidence pack that wins carrier disputes

Winning disputes cite the account number, service ID, invoice period, charge code, and the contract or tariff clause showing the surcharge does not apply. A carrier credits a documented exception far faster than an email that just says a fee looks wrong.

The pattern that wins is boring and repeatable: one exception, one packet, every field a carrier’s billing team needs to verify without a phone call. RadiusPoint files these directly with carriers under a letter of agency and tracks each pending credit in ExpenseLogic until it posts, the same discipline behind documented telecom refund recovery on client accounts.

Evidence Pack Template: the fields finance will accept

• Billing account number (BAN): the specific account, not just the carrier name.
• Service ID: the phone number, circuit ID, or meter tied to the charge.
• Invoice period: the exact billing month and invoice number.
• Charge code and label: the carrier’s own code plus the line description as printed.
• Amount and basis: what was billed and how it was calculated, per line or per rate.
• Authority tested: the statute, tariff section, or contract clause the Belongs Test failed on.
• Requested correction: the credit sought and the go-forward fix so the error does not reappear next cycle.

Where RadiusPoint fits in the tax and surcharge workflow

RadiusPoint audits every line in ExpenseLogic against inventory and contract so surcharge exceptions surface before payment, not after the books close. The point of a managed telecom tax and surcharge audit is not a one-time refund sweep. It is a monthly control that catches the same miscoded fee the first time it appears.

ExpenseLogic holds the rate table, the inventory of record, and the invoice history in one system, and validates invoice line items against contracted rates, provisioned services, and applicable tax treatment each billing cycle. RadiusPoint analysts work the exceptions, file the disputes, and update the inventory as moves, adds, changes, and disconnects happen, so a corrected surcharge stays corrected. It is the same line-item discipline RadiusPoint applies across telecom, wireless, and Utility Expense Management (UEM), which gives finance one reconciliation process instead of three.

The short version

Not every charge printed as a tax or surcharge is mandatory, so a telecom tax and surcharge audit exists to prove which lines truly belong. A telecom tax and surcharge audit sorts each line into statutory tax, permitted surcharge, or discretionary fee, tests it with four questions, and documents the exceptions so finance pays only what belongs. RadiusPoint runs that audit continuously inside ExpenseLogic, which is how a miscoded fee gets caught before payment instead of after the close.

Frequently asked questions

These are the questions finance and telecom teams ask most often when they start auditing telecom taxes and surcharges against contract and jurisdiction rules.

Are Universal Service and similar fees always legitimate?

Many are statutory or tariff-based, but the amount and whether they apply to your service type still need a line-level check. A fee funding a real government program can still be miscalculated or applied to the wrong service.

Should tax lines go through three-way match?

Three-way match alone rarely validates telecom tax codes, because those lines seldom tie to a purchase order or receipt. Pair it with a TEM line-item audit that reads the tax and surcharge block directly.

Who should approve surcharge write-offs?

Finance owns materiality and the write-off decision, telecom owns the carrier negotiation, and both should be recorded in the dispute ticket so the trail is clear later.

Do wireless and wireline follow the same surcharge rules?

They overlap in name only. Audit wireless and wireline under their own product and contract rules, because a surcharge that is valid on one can be wrong on the other.

Can spreadsheet filters catch bad surcharges?

Filters help you triage a single invoice, but sustained auditing needs charge-code history tied to inventory in a platform like ExpenseLogic. Otherwise the same miscode returns the next month and no one remembers the last dispute.

By Sharon R. Watkins, Founder and CEO, RadiusPoint

To build a telecom inventory of record, pull the Customer Service Records (CSRs) from each carrier, normalize the service IDs, map every line to a location and a cost center, then load a validated, versioned file into a system that can audit invoices against it. A CSR states what the carrier believes you subscribe to. Your inventory of record is the version your company trusts after that record has been validated, de-duplicated, and reconciled. At RadiusPoint we build that inventory inside ExpenseLogic first, so invoice audit finally has something true to match against.

Most teams build inventory in the wrong direction. They start from the invoice, because the invoice is the thing that shows up every month and demands payment. But an invoice is a summary. It rolls features into bundles, hides disconnected services that never stopped billing, and says nothing about the account that quietly vanished from the file. Reconcile a summary against itself and you confirm the summary. You don’t find the money. The carrier’s own record is where the truth lives, and building from it changes what the whole program can see.

Why Carrier CSRs Beat Invoices as Your Inventory Source

CSRs list the provisioned services and features that the invoice often summarizes away, so inventory should start from the carrier record, not the bill. An invoice is built to be paid, not to be audited. It groups charges, applies bundle pricing, and presents a total that clears accounts payable without ever exposing the line-level detail underneath.

A CSR is drawn from the carrier’s provisioning database. It shows the individual working telephone numbers, circuit IDs, features, and service order codes attached to a billing account number, including the ones the invoice has folded into a package or, worse, kept billing after the service was supposed to end.

This is why the inventory you assemble at the start of a program matters more than any dashboard you buy. The data gathered during onboarding becomes the reference every later audit depends on, and if it’s sourced from bills alone, every audit inherits the bill’s blind spots. Start from the carrier record and those blind spots have nowhere to hide.

If your inventory was built from invoices, you have a list of what you’re paying for. You still don’t have a list of what you have.

How to Turn CSRs Into an Inventory of Record: Five Steps

Pull the CSRs by BAN, normalize the service IDs, map locations and cost centers, then freeze a versioned inventory of record for audit. The build follows five steps in order, and the order is the point. Skip normalization and your map is unreliable. Skip validation and you version a file full of the carrier’s own errors.

1. Pull. Request the full CSR for every billing account number, under a letter of agency, from each carrier in scope. Ask for the official service record, not a billing summary, because carriers will send the shorter document if you let them. A partial pull that covers some BANs but not others produces an inventory with holes you can’t see.
2. Normalize. Carriers describe the same service in different formats, with different service order codes and different naming. Translate each carrier’s raw record into one consistent schema so a circuit from one carrier and a circuit from another sit in the same column with the same meaning.
3. Map. Attach every line and circuit to a physical location and an owning cost center. This is where a raw carrier extract becomes something finance can use, because a service with no site and no cost center is a service nobody is accountable for.
4. Validate. Reconcile the normalized, mapped records against invoices and against whatever internal inventory already exists. Flag every disagreement. Disagreements aren’t noise to be smoothed over, they’re the findings.
5. Version. Freeze the reconciled file as a dated inventory of record and give it an owner. Every future change gets recorded against this version, so you always know what the inventory looked like when a given audit ran.

How long this takes depends mostly on how scattered the source data is, which is usually the real variable in a first build. Centralized billing shortens it. Invoices spread across accounts payable, IT, and individual site managers lengthen it. Either way, the five steps don’t change, only the effort at step one.

The Seven Fields Every Inventory Row Must Carry

Each inventory row needs a BAN, a service ID, a product code, a site, a cost center, a contract rate, and a status before ExpenseLogic can audit invoices line by line. A row missing any one of these can’t be fully audited, because each field answers a question the audit has to ask.

The contract rate field is the one most inventories omit, and it’s the one that turns a list into an audit. Without a rate to test against, you can confirm that a charge exists, but you can’t say whether it’s correct. It’s also the field that carries forward when you change providers, which is why an inventory built this way stays portable rather than trapped inside one vendor’s tool.

Where CSR-Based Inventory Builds Break Down

CSR builds fail when partial BAN pulls, stale feature codes, or unowned locations leave orphans that keep billing long after the site closed. The failure modes are consistent, and knowing them in advance is most of the defense.

• Partial BAN pulls. The team requests CSRs for the accounts it knows about and never discovers the accounts it doesn’t. A billing account nobody remembers is exactly the account most likely to be paying for something dead.
• Stale feature and service order codes. A CSR can carry codes for features and configurations that were changed years ago and never cleaned up. Loaded without interpretation, they inflate the inventory with services that don’t really exist in their billed form.
• Unowned locations. A line mapped to a site that closed, or to a site no cost center will claim, is an orphan. Orphans are where the money hides, because a charge nobody owns is a charge nobody questions.
• Format drift between carriers. Two carriers rarely format CSRs the same way. A build that assumes one layout will silently mis-parse the other, dropping or mislabeling rows.

Orphaned and duplicate lines aren’t only a data-quality problem. They’re usually the first dollars a program recovers, and finding them is the front end of telecom refund recovery. In one inventory clean-up, eliminating toll-free numbers that no longer routed anywhere returned $18,000 a year. In another, reconciling the inventory against the carrier’s records recovered $174,000 in re-credits. Those numbers don’t come from renegotiating anything. They come from having a true inventory to compare the bill against.

An orphan is a charge nobody owns. And a charge nobody owns is a charge nobody cancels.

How RadiusPoint Keeps the Inventory True After the First Load

RadiusPoint refreshes the inventory through MACD tickets and recurring CSR pulls inside ExpenseLogic, so the file stays current between audits instead of decaying the moment it’s built. An inventory of record is only true on the day you freeze it. Every move, add, change, and disconnect (the MACD activity that runs constantly in any live estate) starts pulling the file out of alignment with reality.

A one-time build ignores this and is stale within a quarter. RadiusPoint treats the inventory as a living file instead. Every MACD request is ticketed and written back to the inventory as it happens, and periodic CSR pulls re-confirm the carrier’s record against the file we maintain. Because ExpenseLogic holds the inventory, the rate table, and the invoice history in one place, each month’s audit runs against a current inventory rather than a snapshot from onboarding.

That continuity is what separates a managed program from a project. The same inventory that makes the first audit possible is the thing that keeps every later telecom audit honest, because the file the audit tests against was updated the day the service changed, not the day someone remembered to update a spreadsheet.

The Short Version

Build from the carrier’s record, not the bill. Pull every CSR, normalize the service IDs into one schema, map each line to a site and a cost center, validate against invoices, and freeze a versioned inventory with an owner. Give every row a BAN, service ID, product code, site, cost center, contract rate, and status. Then keep it alive with ticketed MACD and recurring CSR pulls. Do that, and the invoice finally has something true to be audited against. Skip it, and you’re auditing the bill against itself.

Frequently Asked Questions

Can we build a telecom inventory from invoices alone?

No, and it’s the most common mistake. Invoices show what you’re being charged, not what you have. They bundle line items, omit disconnected services that are still billing, and carry a billing address rather than a service location. An invoice-only inventory confirms the bill instead of testing it. Use the carrier’s Customer Service Records as the source, then reconcile the invoices to them.

How often should CSRs be refreshed?

Refresh on two triggers. First, on change: any move, add, change, or disconnect should update the inventory as it happens, through a ticket rather than from memory. Second, on a schedule: a periodic full CSR pull, commonly annual or semi-annual, re-confirms the carrier’s record against the file you maintain and catches anything that slipped between tickets. Estates with high turnover or frequent site changes need the scheduled pull more often.

What if two carriers format their CSRs differently?

They will, and that’s what the normalization step is for. Each carrier’s raw record gets translated into one consistent schema, so a circuit from one carrier and a circuit from another land in the same fields with the same meaning. This is exactly where builds that assume a single format break, because a parser tuned to one carrier’s layout will quietly mislabel another’s. Normalizing first is what makes a multi-carrier inventory trustworthy.

Who approves inventory changes?

A named owner, working from a defined approval workflow. Because every row carries a cost center, a change to that row has an accountable owner attached, and MACD activity flows through a ticket that records who requested the change and who approved it. The point of versioning the inventory is that no change is silent. You can always see what changed, when, and on whose authority.

How does this relate to switching TEM providers?

Directly. A properly built inventory of record is portable, which means it’s yours to carry to a new provider rather than something locked inside one vendor’s platform. The BAN, service ID, product code, site, cost center, contract rate, and status fields are provider-neutral. If you’re weighing a change, our guide to switching TEM providers without losing inventory covers how to move the file without losing the accuracy you paid to

By Sharon R. Watkins, Founder and CEO of RadiusPoint. Sharon founded the company in 1992 after a career in bank internal audit, and has spent more than three decades building the ExpenseLogic platform and reconciling carrier invoices against the accounts that generate them.

A billing account number, or BAN, is not a reference code you type into a carrier portal. It is the account identity a carrier bills under, and in telecom expense management the BAN is the one key that has to reconcile to three separate records at once: the invoice header, the customer service record from the carrier, and the inventory of services you actually run. When the BAN agrees across all three, your payables are auditable. When it does not, you get ghost payables, which is real money leaving the building against accounts nobody can tie back to a service.

Most finance and telecom teams never look at the BAN directly. They approve an invoice total, code it to a cost center, and pay it. The BAN sits quietly on the invoice header doing the one job nobody audits: deciding which account, and therefore which inventory, a charge belongs to. That works until a carrier migration, a merger, or an acquisition changes the BAN underneath a stream of charges that keeps arriving on the old schedule. Deciding whether to reconcile that yourself or hand it to a provider is a large part of knowing when you need a TEM program.

How BANs relate to CSRs, invoices, and inventory

The BAN sits at the top of a hierarchy, and every other telecom identifier hangs beneath it. On the customer service record, the CSR the carrier maintains for your account, the BAN is the parent. Under it sit the service IDs: circuit IDs, billing telephone numbers, and mobile numbers, each one a service the carrier has provisioned. Undder each service ID sit the charge lines: the monthly recurring charge, usage, features, taxes, and surcharges. That chain, BAN to service ID to charge line, is the structure a real reconciliation follows.

The invoice header carries the BAN. The inventory of record carries the service IDs. Reconciling the header to the CSR and to the inventory, line by line rather than by sampling, is the core of invoice auditing services, and it is where the account identity has to hold. If the BAN on the invoice does not match a BAN in your inventory, the charge has nowhere to land and the audit stops before it starts.

BAN, service ID, invoice number, remittance ID: four identifiers people conflate

Four numbers travel together on a telecom account, and treating any two of them as interchangeable is how reconciliations break. Each names a different thing and changes on a different schedule.

One BAN groups multiple service IDs, so counting BANs tells you how many accounts you have, not how many services. The invoice number is disposable, new every cycle, and useless as a reconciliation key. The remittance ID is the one most likely to drift away from the BAN, because accounts payable sets it up for payment routing without reference to the carrier’s account structure. That gap is where the next section lives.

Common BAN failures that create ghost payables

A ghost payable is a charge that clears every month against an account you can no longer connect to a service. The money is real and the payment posts cleanly, which is exactly why nobody catches it: nothing bounces, nothing errors, the general ledger balances. The BAN is what failed, quietly, upstream. Five failure modes account for most of them, and a line-item telecom audit is built to surface all five.

The last two are the most expensive because they hide the longest. After an acquisition, the inherited estate arrives without a clean inventory, and the BANs that came with it bill against no clear owner until someone reconciles them deliberately. A remittance versus BAN mismatch is worse still: the payment side looks healthy, so the mismatch never raises an exception. Both need the same fix, which is a single inventory owner who holds the authoritative list of active BANs and reconciles every remittance back to it.

A ghost payable never bounces. It clears, it balances, and it bills again next month. That is why it survives.

How RadiusPoint and ExpenseLogic keep BANs audit-ready

RadiusPoint loads every BAN into ExpenseLogic as a controlled key, so each invoice, each dispute, and each general ledger file points to one account identity rather than to whatever string happened to be typed that month. Once the BAN is controlled, the hierarchy underneath it becomes testable: every service ID maps to a BAN, every charge line maps to a service ID, and every payment maps back to the BAN it settled. When a carrier reissues a BAN in a migration, the old and new identities are linked in the platform rather than left to drift, so the retired account cannot keep billing unnoticed.

This is where the software-plus-people model matters. The platform holds the controlled keys and the rate table; RadiusPoint analysts do the reconciling work that keeps them true, validating every invoice line item against the inventory of record each billing cycle instead of sampling a few. RadiusPoint captures and validates every BAN, alias, and account number during onboarding and data collection, which is the step that decides whether the rest of the program reconciles or guesses. In one client estate, correcting the inventory of record recovered $174,000 in re-credits that had been sitting behind mismatched accounts.

Every month a BAN stays uncontrolled is another cycle of the same charges posting against an account nobody can audit. Ask RadiusPoint to reconcile one carrier’s BANs against your inventory of record, and you will see how many of your payables point at a service and how many point at a ghost.

Frequently Asked Questions

Is a BAN the same as a phone number or circuit ID?

No. A phone number, a billing telephone number, and a circuit ID are service identifiers that sit under a BAN, and one BAN can hold multiple of them. The BAN names the account; the service IDs name the individual services the carrier has provisioned on that account.

Who owns BAN accuracy, accounts payable or telecom?

Both, on different sides of the same number. Telecom owns inventory truth, meaning which services exist under which BAN. Accounts payable owns payment posting, meaning which BAN a payment settles against. They need the same BAN to agree, which is why a single inventory owner and a shared account list matter more than which department holds them.

What if a carrier uses an account number instead of a BAN?

Treat the account number as the BAN equivalent. Some carriers, particularly wireless and utility providers, label the field differently. Document the alias against the account in ExpenseLogic so the account number, the BAN, and any legacy identifier all resolve to one controlled key rather than three that look unrelated.

Can one location have multiple BANs?

Yes, and it is common. Adds, carrier migrations, and acquisitions all create new BANs for a site that already had one, so a single location can carry several active BANs at once. The inventory of record has to list every active BAN for the location, or charges under the unlisted ones become ghost payables.

Does wireless use BANs too?

Yes. Wireless bills roll up to a master account number that functions as the BAN, with individual mobile numbers as the service IDs beneath it. Map wireless the same way you map wireline: master account number as the controlled key, mobile numbers reconciled against an employee or cost center directory underneath it.

By Sharon Watkins, Founder and CEO, RadiusPoint · 31 August 2026 · 12 min read

When you switch telecom expense management providers you can lose the inventory of record, open disputes, unposted credits, letters of agency, and current customer service records, unless you export them before access ends. A TEM contract ending is not a software logout. RadiusPoint rebuilds a working inventory in ExpenseLogic from those five files plus fresh carrier records, not from a portal you can no longer open.

This page is the switch process. It is not a vendor list, and it is not a named-competitor comparison.

Key Takeaways

• The five things that walk out with the old provider are inventory, open disputes, the credit pipeline, letters of agency, and carrier customer service records (CSRs).
• Inventory work at RadiusPoint has recovered $174,000 in re-credits when the record of services did not match the bill. That file is what you are trying not to lose.
• A Fortune 100 manufacturer working with RadiusPoint recovered $450,000 in telecom refunds in year one. Unposted disputes of that kind die if nobody owns them during the gap.
• The Switch-Safe Handoff is four moves: export first, re-request CSRs, reissue letters of agency, then park open credits.
• Notify the incoming provider and start the export before you tell the outgoing provider the access date.

The Short Version

Export the inventory of record, the dispute register, and the credit log while you still have login rights, then re-request CSRs and reissue letters of agency, before anyone cuts the old portal.

In this article

• The five things that walk out with the old provider
• What happens to open disputes and credits during a TEM switch?
• How do you keep the inventory of record when you change providers?
• Letters of agency and customer service records have to be reissued
• The Switch-Safe Handoff
• When should you notify the old provider versus the new one?
• How RadiusPoint rebuilds a working inventory instead of importing a stale one

The five things that walk out with the old provider

The five things that walk out with the old TEM provider are inventory, open disputes, credits, letters of agency, and CSRs. RadiusPoint asks for those five before ExpenseLogic is treated as live. A TEM platform can hold years of tickets you never copied. When the login dies, the tickets die with it.

Telecom refunds and cost-avoidance is the live page for recovery work. Recovery is only as durable as the register you carry across the gap. A glass manufacturer working with RadiusPoint saved $100,000-plus in year one. Those dollars started as line items someone could still see.

This is a process page. It does not rank providers. If you need a commercial starting point after the handoff, the telecom expense management service is that page.

What happens to open disputes and credits during a TEM switch?

Open disputes stall, and unposted credits expire, unless a named owner keeps the evidence pack and the carrier ticket number alive through the gap. RadiusPoint parks that register in ExpenseLogic and will not call a credit “saved” until it appears on a later invoice. Identified dollars are not banked dollars. A switch that reports “$400,000 identified” and then drops the follow-up has converted recovery into a story.

A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one, with $850,000 in ongoing annual savings and a $1.3 million year-one impact. That pipeline had an owner. Invoice auditing services find the error. Telecom audit services keep the audit moving. Neither page replaces a dispute register you forgot to export.

Ask the outgoing provider for a list of every open ticket, the amount, the carrier reference, and the last follow-up date. If they cannot produce it, assume the pipeline is already at risk.

How do you keep the inventory of record when you change providers?

You keep the inventory of record by exporting it while you still have rights, then reconciling that file to a fresh CSR. RadiusPoint treats the outgoing export as a hypothesis in ExpenseLogic. The CSR is the carrier’s current picture. The next invoices are the proof. Inventory management at RadiusPoint has recovered $174,000 in re-credits when those pictures disagreed.

An inventory export that lacks service ID, BAN, carrier, contract, location, cost centre, monthly rate, status, last invoice date, and open-ticket reference is a contact list. It is not an inventory of record. RadiusPoint will say which fields are missing rather than load a false baseline.

Multi-vendor support is the live reminder that each carrier is a separate export and a separate CSR request. One “download all” button is rare.

Letters of agency and customer service records have to be reissued

Letters of agency have to be revoked and reissued, and customer service records have to be requested again from each carrier. Customer service records have to be requested again from each carrier. RadiusPoint will not reuse an outgoing provider’s letter, and ExpenseLogic will not treat a six-month-old CSR as current. The grant is personal to the agent. Copying a PDF does not transfer authority.

This is not a second letter-of-agency explainer. It is the switch step: revoke the old grant so two agents are not writing the same carrier, then issue a scoped grant to the incoming team. CSR timing sits on the carrier, not on your preferred go-live date.

If utilities are in scope, Utility Expense Management (UEM, not Unified Endpoint Management) needs the same revoke-and-reissue pattern on utility accounts. RadiusPoint can hold those grants on the same ExpenseLogic instance. They are still different vendors.

The Switch-Safe Handoff

The Switch-Safe Handoff is RadiusPoint’s four-move sequence: export first, re-request CSRs, reissue letters of agency, then park open credits with a named owner. ExpenseLogic is where those four outputs land. Exit blogs in this category say “collect invoices and tell your vendors.” They do not teach a four-move order that delays notice to the outgoing provider until the export is in motion.

When should you notify the old provider versus the new one?

Notify the incoming provider first, start the export, then give the outgoing provider a dated access-end notice that still leaves time to pull files. RadiusPoint would rather see a complete pack than an early announcement. A provider who loses the account can still behave professionally. Do not test that by cutting access the same day you send the email.

Read the current contract for notice periods and auto-renewal. That is a calendar fact, not a vendor review. RadiusPoint will work to your notice date. ExpenseLogic still needs the four Switch-Safe outputs inside that window.

If the outgoing team offers a “transition file,” take it, then still re-request CSRs. Their file is their picture. The carrier’s CSR is the picture the next invoice will be billed from.

How RadiusPoint rebuilds a working inventory instead of importing a stale one

RadiusPoint rebuilds the inventory in ExpenseLogic by matching your export to new CSRs and to the next invoices, then opening exceptions where the three disagree. Importing a stale file and calling it go-live is how ghost circuits survive a switch. Analysts file new disputes under the new letter of agency. Old tickets stay in the parked register until they post or are written off with a reason.

The glass manufacturer case is a savings story after the record was usable. HumanGood’s published 315% ROI is a running-program figure. Neither number appears during a messy cutover.

RadiusPoint has done this since January 1992. ISO 9001 certification has been in place since September 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. Sharon Watkins founded the firm after internal-audit work at a bank. A TEM switch is an audit handoff with a cancellation email attached.

How we researched this

We compared live RadiusPoint TEM, refund, and audit pages with 2026 switcher and “legacy TEM exit” posts. Those pages own a generic transition checklist. They do not own a five-loss list plus a four-move Switch-Safe order that delays outgoing notice. Proof numbers come only from the published RadiusPoint proof library and live pages fetched 28 August 2026. No affiliate relationships. No named-competitor ranking. No invented week counts for a cutover.

FAQ

Can we run two TEM providers at once during the gap?

You can, if letters of agency are scoped so only one agent can order, and both can read bills. RadiusPoint will say which rights it needs. Two agents filing the same dispute is how credits get lost.

What if the old provider will not export inventory?

Start with carrier CSRs and the last 12 months of invoices. RadiusPoint will rebuild from those in ExpenseLogic. The $174,000 re-credit case is what a rebuild can still find. You will spend more calendar time.

Do we need to re-sign every letter of agency?

Yes, or execute a revoke-and-replace that the carrier will accept. A forwarded PDF of the old letter is not a grant to the new agent.

Is this the same as the Day-Zero pack for a first-time TEM buyer?

No. First-time onboarding gathers your internal files. A switch also has to extract files that live inside the outgoing platform and keep the credit pipeline alive. Overlap exists. The risk is different.

What if we are only switching the software and keeping the same people?

You still need the export and the CSR refresh. People remember tickets. Portals do not migrate memory. RadiusPoint will still reconcile the file to the next invoice.

What to do before you give notice

List the five files. Pull the ones you can download today. Call RadiusPoint with that list and the notice date on the current contract. ExpenseLogic can start on a partial export. It cannot start after the portal is already dark.

Latest Updates

• 31 August 2026: Article drafted. Stats used: $174,000 inventory re-credits, Fortune 100 $450,000 / $850,000 / $1.3 million, glass $100,000-plus, HumanGood 315% ROI, ISO 9001 since 2002, Capterra 4.8 / 31, Amalgam Insights 2024 Distinguished Vendor. Process page only. No vendor ranking.

References

1. Telecom Expense Management Services | RadiusPoint
2. Telecom Refunds, Cost Avoidance, Savings | RadiusPoint
3. Invoice Auditing Services | RadiusPoint
4. Telecom Audit Services | RadiusPoint
5. Multi-Vendor Support | RadiusPoint
6. Glass Manufacturer Saves $100K on Telecom Expenses | RadiusPoint
7. HumanGood Achieved 315% ROI with RadiusPoint | RadiusPoint
8. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
9. ExpenseLogic reviews | Capterra
10. Sharon R. Watkins | RadiusPoint
11. ExpenseLogic | RadiusPoint

Related articles

• Telecom Expense Management Services
• Telecom Refunds and Cost Avoidance
• Invoice Auditing Services
• Telecom Audit Services

Disclaimer

This article is general information for teams changing TEM providers. It is not legal advice on contracts, notice periods, or letters of agency. Outcomes cited are from specific RadiusPoint client engagements already in the published proof library and are not a guarantee of future results or of a cutover duration.

By Sharon Watkins, Founder and CEO, RadiusPoint · 30 August 2026 · 12 min read

A telecom expense management provider needs invoices, contracts, a starter inventory, allocation rules, an employee roster, and site open-and-close dates before the first cycle, and a letter of agency is only one file in that pack. Accounts payable emails three PDFs and calls it kickoff. RadiusPoint cannot build an inventory of record in ExpenseLogic from three PDFs. Day one is the day the pack is complete enough to load, not the day the contract is countersigned.

This page is onboarding-readiness. It is not a letter-of-agency explainer, and it is not the handoff you run when you leave a provider.

Key Takeaways

• The Day-Zero Data Pack is eight files: scoped letters of agency, invoice history, contracts, starter inventory, GL and allocation rules, HR roster, site dates, and named owners.
• A letter of agency authorizes carrier conversations. It does not create invoices, rate tables, or an employee list.
• A food service onboarding at RadiusPoint needed two months for users to register 600-plus lines. Fifty-six of those users were already gone.
• HumanGood, a named RadiusPoint client, has a published 315% ROI once the program is running. That figure is not a substitute for a complete kickoff pack.
• Kickoff stalls when IT is asked for every file. AP, procurement, finance, HR, and real estate each own a slice.

The Short Version

Before RadiusPoint can run ExpenseLogic on your accounts, you need a Day-Zero Data Pack: invoices, contracts, a starter inventory, allocation rules, an HR roster, site dates, named owners, and a scoped letter of agency, not the letter alone.

In this article

• What a TEM provider can start without, and what it cannot
• Why is a letter of agency not the onboarding file?
• Which invoice, contract, and inventory files should be ready first?
• What finance and HR have to contribute before kickoff
• The Day-Zero Data Pack
• Who inside your company owns each file?
• How RadiusPoint uses ExpenseLogic once the pack arrives

What a TEM provider can start without, and what it cannot

A TEM provider can start a RadiusPoint kickoff call without a perfect inventory, but it cannot validate invoices without bills. RadiusPoint still needs a rate source and a way to reach the carrier. RadiusPoint will load what you have into ExpenseLogic and mark the gaps. A missing contract exhibit delays rate matching. A missing letter of agency delays portal access. A missing site list delays allocation. Those are different delays.

The telecom expense management service names monthly accrual files and GL interface files as outputs. Outputs require inputs. This page is the input list. The TEM FAQ answers how the platform behaves after load. Do not treat the FAQ as the pack.

You can begin without 36 months of history. You should not begin without at least one full recent cycle per major carrier and the current contract that is supposed to govern it.

Why is a letter of agency not the onboarding file?

A letter of agency authorizes a TEM provider to speak to a named carrier on a scoped set of rights only. It is not the onboarding file. RadiusPoint still needs invoices, contracts, and owners after the letter is signed, and ExpenseLogic will not invent those records from the authorization. Scope the letter. A read-only billing grant is not ordering rights. A blanket grant is a governance problem, which the live TEM pillars already warn against.

This section names the letter so you do not confuse it with the pack. It is not a second letter-of-agency article. If you want the legal mechanics of the grant, that is a different page. If you want to know what to gather this week, stay here.

RadiusPoint will tell you which carrier the letter must name and which rights it must include. You still have to produce the other seven files.

Which invoice, contract, and inventory files should be ready first?

Ready first means 12 months of invoices or portal access, current contracts, and the best inventory you already have on file. RadiusPoint loads those three into ExpenseLogic before it asks for a polished spreadsheet. Invoice audit work cannot start on a carrier you have not shown. Contract images are the rate table. The starter inventory is a hypothesis the bills will test.

A food service client had no wireless procurement policy and no structure for adding users. RadiusPoint stood up a Register Your Line portal and spent two months collecting registrations on 600-plus lines. That timeline is published on the managed mobility case study. The pack was incomplete on purpose. The invoices and the portal still had to exist on day one.

Telecom lifecycle management is the live companion for how services move after kickoff. This question is only about the files that have to exist before that lifecycle has a baseline.

What finance and HR have to contribute before kickoff

Finance has to contribute the chart of accounts, cost-centre list, and allocation rules before RadiusPoint can code ExpenseLogic files. HR has to contribute a current employee roster for wireless matching. RadiusPoint cannot code a GL interface file in ExpenseLogic without the map finance already uses, and it cannot flag a departed user without a roster dated in the same month as the wireless bill. Those two files are why kickoff is not an IT-only request.

The food service case found 56 identified users who were no longer employed. That finding required a roster, not only a carrier extract. HumanGood’s published 315% ROI is a running-program figure. It does not appear until allocation and inventory have something to post against.

If finance plans to copy last month’s bill for the accrual, say so. RadiusPoint will then know the accrual file is part of the pack, not a later enhancement.

The Day-Zero Data Pack

The Day-Zero Data Pack is RadiusPoint’s eight-file list of what has to be present, even if incomplete, before ExpenseLogic can run a first cycle. Implementation guides in this category say “send us your invoices and an LOA.” They do not name an eight-file pack with an owner for each file.

Who inside your company owns each file?

IT or telecom owns the inventory, BANs, circuit IDs, and portal logins that RadiusPoint will load into ExpenseLogic. Accounts payable owns invoice PDFs and the vendor master. Procurement owns contracts. Finance owns the GL map. HR owns the roster. Real estate or facilities owns site dates and, if utilities are in scope, the utility account list. RadiusPoint will send one request list. Your internal owners still have to move the files.

Multi-vendor support is the live page for a carrier-heavy environment. That environment makes file H (named owners) non-negotiable. A single inbox labeled “TEM kickoff” will sit.

Utility Expense Management (UEM, not Unified Endpoint Management) adds meter IDs and tariff sheets to files B, C, and G. RadiusPoint can load those on the same ExpenseLogic instance. They are still different owners inside your company.

How RadiusPoint uses ExpenseLogic once the pack arrives

RadiusPoint loads the pack into ExpenseLogic, builds a baseline inventory from bills plus your starter file, and opens exceptions where the two disagree. Analysts then validate lines, file disputes where authorized, and return an allocation file that matches the finance map you sent. You do not receive a portal with empty tables and a note to “upload more later” as if that were go-live.

RadiusPoint has done this since January 1992. ISO 9001 certification has been in place since September 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. Credentials do not shrink the pack. They tell you the load process is repeatable.

Sharon Watkins founded RadiusPoint after internal-audit work at a bank. Day-zero data is an audit binder. ExpenseLogic is where that binder becomes the inventory of record.

How we researched this

We compared live RadiusPoint TEM, FAQ, lifecycle, and mobility-case pages with 2026 implementation guides that list “LOA, invoices, contracts.” Those pages own a short start list. They do not own an eight-file Day-Zero Data Pack with internal owners. Proof numbers come only from the published RadiusPoint proof library and live pages fetched 28 August 2026. No affiliate relationships. No invented week counts for a full TEM rollout.

FAQ

Can we start if our inventory spreadsheet is two years old?

Yes, if invoices and contracts are current. RadiusPoint will treat the spreadsheet as a hypothesis in ExpenseLogic and rebuild against the bills. Mark file D as stale so nobody pretends it is the inventory of record.

Do we need portal passwords or only PDFs?

PDFs can start a historical load. Portal or EDI access is what keeps the next cycle arriving without a mailbox chase. RadiusPoint will say which carriers still require a human upload.

What if HR will not release a roster?

Wireless matching will be incomplete. RadiusPoint can still process wireline invoices. File F stays red on the pack until HR sends a dated active list, even if names are limited to employee ID.

Is this the same as the data we send when we switch providers?

No. Switching is a handoff out: export, open disputes, reissued letters, carrier CSRs. This page is a handoff in: the first pack a new provider needs. Overlap exists. The jobs are different.

How complete does file G need to be on day one?

Every location you know is still open or that closed in the last 12 months, with a date. RadiusPoint will catch more from the bills. A blank site list makes every invoice a mystery BAN.

What to do before kickoff

Assign an owner to each of the eight codes this week. Send RadiusPoint the files you have, and label the files you do not. ExpenseLogic can start on a partial pack. It cannot start on a letter of agency and a promise.

Latest Updates

• 30 August 2026: Article drafted. Stats used: food service two-month registration / 600-plus lines / 56 departed users, HumanGood 315% ROI, ISO 9001 since 2002, Capterra 4.8 / 31, Amalgam Insights 2024 Distinguished Vendor. No invented implementation week counts.

References

1. Telecom Expense Management Services | RadiusPoint
2. Telecom Expense Management FAQ | RadiusPoint
3. Invoice Audit | RadiusPoint
4. Telecom Lifecycle Management | RadiusPoint
5. Multi-Vendor Support | RadiusPoint
6. How Managed Mobility Services Cut Costs 22% ($400K in Year 1) | RadiusPoint
7. HumanGood Achieved 315% ROI with RadiusPoint | RadiusPoint
8. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
9. ExpenseLogic reviews | Capterra
10. Sharon R. Watkins | RadiusPoint
11. ExpenseLogic | RadiusPoint

Related articles

• Telecom Expense Management Services
• Telecom Expense Management FAQ
• Invoice Audit
• Telecom Lifecycle Management

Disclaimer

This article is general information for teams preparing a TEM kickoff. It is not legal advice on letters of agency or data-sharing. Outcomes cited are from specific RadiusPoint client engagements already in the published proof library and are not a guarantee of future results or of a kickoff duration.

By Sharon Watkins, Founder and CEO, RadiusPoint · 29 August 2026 · 12 min read

You need a telecom expense management provider when your team can no longer produce a complete inventory this week, invoices are approved without a line-item check, and contracts renew without a rate review. How many mobile lines does your company pay for right now? Not approximately. Exactly. Most in-house owners cannot answer inside five business days. That gap is the sign. RadiusPoint takes the operational load on ExpenseLogic while you keep the budget.

This page is a readiness self-assessment. It is not a rewrite of Outsourced Telecom Expense Management, which owns what outsourcing transfers and what it costs to keep the work inside.

Key Takeaways

• The first sign you have outgrown in-house TEM is an inventory you cannot finish this week, with a location, a cost centre, and a contract rate on each service.
• A food service company working with RadiusPoint had 600-plus lines, one overloaded owner, and 56 departed users still billing. Monthly cost fell 22%, more than $400,000 in year one.
• Amalgam Insights’ IT Rule of 30 states that the average unmanaged IT expense category is wasting 30% in spend, a category claim, not a RadiusPoint promise (EIN Presswire, 2024).
• Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. Treat that as a category range, not a guarantee.
• The Outgrown-In-House Scorecard is six operational signs. Three or more yes answers is a staffing problem.

The Short Version

If your team cannot name every circuit, mobile line, and data service this week, you have already outgrown in-house telecom expense management, whether or not you still have a “telecom person.”

In this article

• The inventory question your team should answer this week
• What happens when invoices get approved without a line-item check?
• How carrier and location count turns a spreadsheet into a leak
• What happens when telecom contracts renew without a review?
• The Outgrown-In-House Scorecard
• Does a dedicated telecom person still mean you can stay in-house?
• How RadiusPoint and ExpenseLogic take the operational load

The inventory question your team should answer this week

The inventory question is exact headcount of circuits, mobile lines, and data services, each with a location, a cost centre, and a contract rate. RadiusPoint treats that file as the inventory of record inside ExpenseLogic. A spreadsheet that is 90 days old is a memory. It is not an inventory. The telecom expense management FAQ is where buyers ask how the platform holds that file. This page asks whether you can produce it at all.

A food service company came to RadiusPoint with hundreds of wireless devices and no identification of the employees using them. The managed mobility case study records 600-plus phones billed monthly, 56 users no longer employed, and a 22% monthly-cost cut that the video transcript states as more than $400,000 a year. That is what “we are handling it in-house” looked like with one person who also had other duties.

If you cannot answer the inventory question this week, the rest of the scorecard is already in motion.

What happens when invoices get approved without a line-item check?

Invoices approved without a line-item check become paid vendor claims, including charges for services that no longer exist at all. RadiusPoint audits invoice lines against contracted rates and inventory in ExpenseLogic before the payment run. Rubber-stamp approval is the quiet version of in-house failure. The due date is real. The GL coding is complete. The circuit may have been dead for a year.

RadiusPoint published $18,000 a year recovered by eliminating unneeded toll-free numbers. Inventory work has recovered $174,000 in re-credits when the record of services did not match the bill. A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one. Those dollars sat on invoices someone had already been allowed to pay. Facing five TEM challenges names the operational pressure. This page names the sign: approval without a line check.

Carrier dispute windows are finite. An invoice reviewed 60 days late is often a permanent write-off. That is an in-house capacity problem, not a software preference.

How carrier and location count turns a spreadsheet into a leak

Complexity, not a round spend number, is usually what outgrows a part-time telecom owner that RadiusPoint still sees monthly. RadiusPoint sees the break when a second and third carrier land, then when sites open and close faster than MACD tickets close. One carrier and one site can still fit a careful analyst. Three carriers plus wireless plus utilities will not, if that analyst also owns help desk and hardware refresh.

RadiusPoint published a client that grew from 170 to 1,200 locations. At that scale, a missed disconnect on a thin percentage of sites is not a rounding error. ExpenseLogic holds telecom, wireless, and utility invoices together so the same owner problem does not hide in three spreadsheets. Cutting telecom expenses with TEM is the commercial companion. This section is the complexity test.

An automotive-salvage engagement on the live TEM page generated $1.3 million from inventory and audit after acquisitions consolidated invoices. That is what a location-count jump looks like when nobody rebuilds the record.

What happens when telecom contracts renew without a review?

A telecom contract that auto-renews at the old rate is an unowned calendar RadiusPoint sees every month, not a market decision. RadiusPoint tracks expiration dates and rates against service IDs in ExpenseLogic and raises the date before the notice window closes. In-house teams lose that date because the person who signed the deal left, or because the file lives in a procurement inbox no one opens.

Silent renewal is one of the six scorecard signs. It pairs with departed employees who still have live mobile lines, which is the wireless face of the same ownership gap. The food service case had both: no wireless policy, and users who had been gone more than two years while billing continued. RadiusPoint wrote the policy after the inventory, not before.

What Is Telecom Expense Management? explains the discipline. This page asks whether anyone on your payroll still practices it every month.

The Outgrown-In-House Scorecard

The Outgrown-In-House Scorecard is RadiusPoint’s six-sign test of whether one internal owner can still finish the work each month. ExpenseLogic is where RadiusPoint would take those six jobs if the score is already failed. Pillar pages tell you what outsourcing transfers. They do not give finance a six-sign operational scorecard.

Three or more yes answers is a staffing problem. Buying a dashboard without moving the work does not clear a yes.

Does a dedicated telecom person still mean you can stay in-house?

A dedicated person can keep TEM in-house if they still finish inventory, line checks, and renewals without dropping the accrual. RadiusPoint does not treat a job title as proof of capacity. The food service owner was dedicated to phones and still had other telecom duties. The lines outran the person.

Stay in-house when the scorecard is mostly no, the carrier mix is simple, and finance already trusts the accrual. Move the operational work when three or more signs are yes. The outsourced pillar owns the cost comparison. This question only tests whether the person you already have can still see the file.

A healthcare provider working with RadiusPoint reduced telecom expenses 26%. A glass manufacturer saved $100,000-plus in year one. Those are program outcomes after the work moved. They are not a rule that every titled telecom manager must outsource.

How RadiusPoint and ExpenseLogic take the operational load

RadiusPoint takes invoice collection, line-item audit, dispute filing, and inventory maintenance onto ExpenseLogic, and leaves budget approval and carrier strategy with you. The telecom expense management service is that model. You still own the yes or no on a disconnect. RadiusPoint owns proving the charge is gone.

Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The same 2024 release cycle is where Amalgam published the IT Rule of 30: the average unmanaged IT expense category is wasting 30% in spend. Use that as a category warning. Do not write it as a RadiusPoint guarantee. Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one, again a category range.

RadiusPoint has done this since January 1992. ISO 9001 certification has been in place since September 2002. The Capterra listing sat at 4.8 from 31 reviews through December 2025. Sharon Watkins founded the firm after internal-audit work at a bank. The outgrown-in-house problem is an audit problem with a headcount attached.

How we researched this

We compared the live RadiusPoint TEM, FAQ, and mobility case pages with 2026 “do you need TEM” guides that lead with spend thresholds ($500,000, $1 million). Those pages own a dollar cutoff. They do not own a six-sign operational scorecard that starts with the inventory question. Proof numbers come only from the published RadiusPoint proof library, Amalgam’s published Rule of 30, and live pages fetched 28 August 2026. No affiliate relationships. No invented week counts for a rollout.

FAQ

Is there a spend number that means we must outsource?

No honest operator can name one number that fits every carrier mix. RadiusPoint starts with the six signs. A simple single-carrier environment can stay in-house at a higher spend than a messy multi-carrier one at a lower spend.

Does a TEM platform without managed service fix a failed scorecard?

Only if you staff the work the platform reports. RadiusPoint’s model is software plus people. A license that leaves disputes and inventory with a team that already failed the scorecard is a reporting layer over the same leak.

What if we only failed the mobility signs?

Start with wireless inventory and the HR roster. The food service case was a mobility failure that sat next to a TEM failure. RadiusPoint can take one expense category first. The scorecard still applies to that category.

How is this different from the outsourced TEM pillar?

The pillar explains what moves to a provider and what stays with you. This page tells you whether you are already past the point where keeping it is working. Read the pillar after you score three yes answers.

Can we run the scorecard on utilities too?

Yes, with Utility Expense Management (UEM, not Unified Endpoint Management) substituted for TEM on the invoice type. RadiusPoint holds both on ExpenseLogic. A closed-site electric bill is the utility face of sign 1 and sign 3.

What to do before the next invoice cycle

Score the six signs this week. If you cannot name the inventory, stop there and call that a yes. RadiusPoint will load one month of invoices into ExpenseLogic and show you which signs are already costing you. Every cycle you skip is another unread approval.

Latest Updates

• 29 August 2026: Article drafted. Stats used: food service 22% / $400,000 / 600-plus / 56 users, $18,000 toll-free, $174,000 re-credits, Fortune 100 $450,000, $1.3 million salvage/acquisition, healthcare 26%, glass $100,000-plus, 170-to-1,200 locations, Amalgam Rule of 30, category 15 to 30 percent hedged, ISO 9001 since 2002, Capterra 4.8 / 31, Amalgam 2024 Distinguished Vendor.

References

1. Outsourced Telecom Expense Management | RadiusPoint
2. What Is Telecom Expense Management? | RadiusPoint
3. Telecom Expense Management Services | RadiusPoint
4. Telecom Expense Management FAQ | RadiusPoint
5. How Managed Mobility Services Cut Costs 22% ($400K in Year 1) | RadiusPoint
6. Facing Five TEM Challenges | RadiusPoint
7. Cutting Telecom Expenses with TEM | RadiusPoint
8. Amalgam Insights Unveils Vendor SmartList for Telecom Expense Management | EIN Presswire
9. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
10. ExpenseLogic reviews | Capterra
11. Sharon R. Watkins | RadiusPoint

Related articles

• Outsourced Telecom Expense Management
• What Is Telecom Expense Management?
• Telecom Expense Management Services
• Managed Mobility Services case study

Disclaimer

This article is general information for finance and IT leaders deciding whether in-house TEM still fits. It is not a staffing or legal recommendation. Outcomes cited are from specific RadiusPoint client engagements already in the published proof library. Category-level ranges, including Amalgam’s IT Rule of 30 and the 15 to 30 percent TEM range, are not RadiusPoint guarantees.

By Sharon Watkins, Founder and CEO, RadiusPoint · 28 August 2026 · 12 min read

The questions that belong in a telecom expense management contract are the ones that name a person, a percentage, and a file you will receive if you leave. Most buyers treat the TEM demo as the evaluation. RadiusPoint treats the statement of work as the evaluation. A platform can show you a variance. A managed service has to say who files the dispute, who updates the inventory, and who hands you the export on the last day.

This page is the pre-sign question list. It is not a rewrite of How to Choose a Telecom Expense Management Company, which owns vendor models and selection criteria. It is not a named-competitor comparison.

Key Takeaways

• Ask who files the carrier dispute and who confirms the credit on a later invoice. A report is not a recovery.
• Ask what share of invoice lines is audited against the contracted rate table, not what share is loaded into the tool.
• Ask how the inventory of record is built, and in what format you receive it if the engagement ends.
• A food service client working with RadiusPoint on 600-plus lines cut mobility cost 22% and more than $400,000 in year one after 56 departed users were still being billed.
• The Sign-Day Seven is RadiusPoint’s list of questions that have to survive into the contract, not only into the sales deck.

The Short Version

Before you sign a TEM agreement, write seven answers into the statement of work: who files, what share of lines is audited, how inventory is exported, what the letter of agency covers, which pricing model you are buying, who the named analyst is after go-live, and what files you receive on the last day.

In this article

• The questions that belong in the contract, not the demo
• Who files the dispute when an invoice is wrong?
• What percentage of invoice lines will you actually audit?
• How will we get our inventory of record if we leave?
• The Sign-Day Seven
• Which pricing model are you buying, and what does it reward?
• How RadiusPoint answers these questions in a managed TEM engagement

The questions that belong in the contract, not the demo

The questions that belong in a TEM contract are the ones a RadiusPoint demo, or any demo, can dodge with a screenshot. RadiusPoint writes those questions into ExpenseLogic’s operating model so a buyer can test the answer after month three, not only on the sales call. “We audit invoices” is demo language. “What percentage of lines, against which rate table” is contract language. The vendor evaluation page on the RadiusPoint site is the commercial companion. This page is the script you take into the room.

What Is Telecom Expense Management? owns the definition. This page assumes you already know what TEM is and you are about to sign. Do not use this list as a second 101.

A letter of agency, an inventory export, and a dispute register are three different documents. RadiusPoint will ask you for the first at kickoff. You should ask RadiusPoint, or any other provider, for the other two in writing before you sign.

Who files the dispute when an invoice is wrong?

The provider should file the dispute, age it, and confirm the credit on a later invoice, unless you have staffed that work internally on purpose. RadiusPoint files carrier disputes on the client’s behalf and tracks them in ExpenseLogic until the credit posts. A flag-only model hands you an exception list. A draft-only model writes the letter and leaves the follow-up with you. Ask which box you are buying.

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. That figure is a recovery story. It is only useful in a pre-sign meeting if the provider can say who filed, who chased, and how the credit was proven. Invoice auditing services find the error. Filing is the next job.

If the answer is “we send you a report,” write that into the statement of work as your labor, not as their managed service.

What percentage of invoice lines will you actually audit?

Ask for the invoice-line coverage percentage in writing, and ask RadiusPoint or any bidder what happens below a dollar threshold. RadiusPoint audits invoice line items against contracted rates and against inventory, rather than sampling, and records that work in ExpenseLogic. Loading an invoice is not auditing it. Anomaly flags are not a rate-table match.

Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category-level observation, not a RadiusPoint guarantee, and it only holds if someone actually checks the lines. A glass manufacturer working with RadiusPoint saved $100,000-plus in year one. A healthcare provider reduced telecom expenses 26%. Ask each bidder to show a comparable finding, then ask whether those dollars were identified, disputed, or credited.

Telecom expense management pricing explains how providers charge. This question is about what you receive for that charge.

How will we get our inventory of record if we leave?

You should receive a documented export of services, BANs, locations, rates, disputes, and credits that the next operator can load. RadiusPoint treats the inventory of record as a client-owned file inside ExpenseLogic, not as a vendor hostage. Ask for the export format, the field list, and the number of business days after notice.

A food service client had 600-plus phones billed monthly with no employee identification, and 56 identified users who were no longer employed. That inventory work is published on the RadiusPoint managed mobility case study. If you cannot leave with that file, you will rebuild it from carrier bills. That rebuild is the cost people forget to price into the contract.

Inventory management at RadiusPoint has also recovered $174,000 in re-credits when the record of services did not match the bill. Ask the bidder how that kind of mismatch is found, and whether you keep the evidence pack.

The Sign-Day Seven

The Sign-Day Seven is RadiusPoint’s list of seven questions that have to be answered in the statement of work before a TEM signature is safe. ExpenseLogic is built so those answers can be tested after go-live. Buyer guides in this category list features. They do not lock a seven-question contract script that separates demo language from operating language.

Which pricing model are you buying, and what does it reward?

You are buying a recovery share, a per-invoice or per-line fee, a platform license, or a hybrid, and each model pays a different behavior. RadiusPoint is a managed service on ExpenseLogic, not a one-time contingency audit. A recovery-only fee pays someone to find refunds. It does not, by itself, pay them to stop the next invoice from repeating the error. Read that incentive before you read the case study.

The live pricing explainer owns the model definitions. This section only asks you to match the model to the work you just scoped. If you want disputes filed and inventory kept current, a license that leaves those tasks with you is the wrong purchase.

HumanGood, a named RadiusPoint client, has a published 315% ROI case. Use named cases as proof that a program can pay. Use the Sign-Day Seven to test whether this contract will produce that kind of program.

How RadiusPoint answers these questions in a managed TEM engagement

RadiusPoint delivers managed telecom expense management on ExpenseLogic: analysts audit lines, file disputes, and keep inventory, while you keep budget approval. The telecom expense management service is the commercial page for that model. This article is the question list you should still ask RadiusPoint, in writing, before you sign.

RadiusPoint has been in this work since January 1992. ISO 9001 certification has been in place since September 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. Credentials tell you the firm is real. The Sign-Day Seven tells you the contract is real.

Sharon Watkins founded RadiusPoint after internal-audit work at a bank. The pre-sign problem is an audit problem with a sales deck attached. ExpenseLogic is the working paper after you sign. The seven questions are the working paper before you sign.

How we researched this

We compared live RadiusPoint TEM, pricing, and invoice-audit pages with 2026 buyer guides that ask feature questions (inventory, integrations, dashboards). Those pages own “how to choose.” They do not own a seven-question contract script that separates demo language from operating language. Proof numbers come only from the published RadiusPoint proof library, plus live RadiusPoint pages fetched 28 August 2026. No affiliate relationships. No named-competitor ranking.

FAQ

Is this the same as a TEM RFP scorecard?

A scorecard ranks vendors. The Sign-Day Seven writes operating duties into one contract. RadiusPoint can sit on a scorecard and still fail this list if the statement of work is vague. Ask both.

Should we ask for a sample audit before we sign?

Yes, if you can provide a slice of invoices and contracts. RadiusPoint will treat a sample as evidence, not as a promise of year-one dollars. A sample that only loads PDFs and never files a dispute is a warning.

What if the provider will not name an analyst?

Write a named analyst plus a backup into the statement of work, or treat the gap as a staffing risk. RadiusPoint’s model is a named human on the account. A ticket queue with no name is a different purchase.

Do we still need a letter of agency if we only want reporting?

If the provider must pull invoices or talk to a carrier, yes. Scope it. A read-only billing grant is not the same as ordering rights. RadiusPoint will tell you which grant it is asking for.

How is this different from the TEM companies pillar?

The companies page tells you how vendor models differ. This page gives you the questions to ask after you have picked a model and before you sign. Use both. Do not merge them.

What to do before you sign

Print the Sign-Day Seven. Put the bidder’s answers in the left column and the contract clause in the right. If a cell is empty, you are buying a demo. RadiusPoint will fill those cells for a managed ExpenseLogic engagement. Every week you sign without them is a week you cannot test the work.

Latest Updates

• 28 August 2026: Article drafted. Stats used: food service 22% / $400,000 / 600-plus lines / 56 departed users, Fortune 100 $450,000 / $850,000 / $1.3 million, glass $100,000-plus, healthcare 26%, inventory $174,000 re-credits, HumanGood 315% ROI, category 15 to 30 percent hedged, ISO 9001 since 2002, Capterra 4.8 / 31, Amalgam Insights 2024 Distinguished Vendor.

References

1. How to Choose a Telecom Expense Management Company | RadiusPoint
2. What Is Telecom Expense Management? | RadiusPoint
3. Telecom Expense Management Services | RadiusPoint
4. Telecom Expense Management Pricing | RadiusPoint
5. Invoice Auditing Services | RadiusPoint
6. Vendor Evaluation | RadiusPoint
7. How Managed Mobility Services Cut Costs 22% ($400K in Year 1) | RadiusPoint
8. HumanGood Achieved 315% ROI with RadiusPoint | RadiusPoint
9. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
10. ExpenseLogic reviews | Capterra
11. Sharon R. Watkins | RadiusPoint

Related articles

• Telecom Expense Management Companies
• Telecom Expense Management Pricing
• Invoice Auditing Services
• Telecom Expense Management Services

Disclaimer

This article is general information for finance, IT, and procurement teams evaluating a TEM contract. It is not legal 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 are hedged and are not RadiusPoint promises.

By Sharon Watkins, Founder and CEO, RadiusPoint · 28 August 2026 · 12 min read

Utility rate reclassification is the filed request that moves a meter onto a different published rate class so the same kilowatt-hours and peak kilowatts are priced under a schedule the load actually qualifies for. A plant that added a night shift two years ago can still be billed as a daytime general-service account. Rate reclassification is a Utility Expense Management (UEM, not Unified Endpoint Management) tariff action. RadiusPoint runs it on ExpenseLogic as a schedule change, not as a vacant-cost recovery and not as a line-item bill audit.

This page owns the class change. The live utility rate optimization page covers the wider program, including demand management and power-factor work.

Key Takeaways

• Utility rate reclassification changes the published class on an account. It does not change the meter read, the tenant name, or the occupancy date.
• The U.S. commercial average was 14.19 cents per kWh in June 2026, up 4.8% from June 2025, per the EIA Electricity Monthly Update.
• RadiusPoint published vacant cost recovery that decreased utility expenses by 12%, and a multi-location client paid $1,500 a month ($18,000 a year) for utilities at closed locations. Those are payer problems. Reclassification is a schedule problem.
• An elevator-company engagement cut monthly waste expenditure 28% through vendor and contract work. RadiusPoint keeps that credit type separate from a rate-class move.
• The Rate-Class Fit Test uses four gates: load factor, voltage or service level, demand threshold, and operating hours.

The Short Version

If the invoice math is correct and the account is still on a class the load no longer fits, RadiusPoint should file a rate reclassification in ExpenseLogic, not open a billing-error dispute.

In this article

• What utility rate reclassification actually changes
• How is rate reclassification different from a utility bill audit?
• Why a correctly calculated bill can still be the wrong bill
• What load data do you need before you apply for a new rate class?
• The Rate-Class Fit Test
• Who files a rate reclassification, and who has to approve it?
• How RadiusPoint and ExpenseLogic keep tariff analysis in the monthly cycle

What utility rate reclassification actually changes

Utility rate reclassification changes the published tariff class the utility uses to price an account, while consumption and peak demand stay on the same meter. RadiusPoint treats that class change as a Utility Expense Management (UEM) action inside ExpenseLogic. The invoice still lists energy charges, demand charges, customer charges, and riders. The class decides which published prices attach to those lines.

A reclassification is a customer-initiated filing in most territories. The utility will keep billing the class it assigned at turn-on until someone applies, qualifies, and is moved. RadiusPoint stores the current schedule, the interval history, and the candidate class in ExpenseLogic so finance can see the before-and-after on the same account.

Vacant cost recovery asks who should be the customer of record. Rate reclassification asks which published class that customer should sit in. RadiusPoint keeps both on the utility expense management service so a facilities lead can open two exception types without mixing the workstreams.

How is rate reclassification different from a utility bill audit?

A utility bill audit at RadiusPoint tests whether this invoice matches the meter, the tariff, and the signed contract. Rate reclassification tests whether that tariff is still the class the site qualifies for. RadiusPoint runs both inside ExpenseLogic and posts them as different exception types. A bill audit recovers a wrong multiplier, a duplicated demand line, or a tax that does not belong. A reclassification leaves those lines intact and changes the schedule they are priced on.

Invoice auditing services catch category errors on telecom and related invoices. On the utility side, the same discipline still stops at “is this charge correct for the class we are on.” Reclassification starts after that question is answered yes.

Vacant cost recovery is a third job. RadiusPoint’s vacant cost recovery work is the owner-name and occupancy match. Do not send a rate-class application to fix a tenant who never transferred service.

Why a correctly calculated bill can still be the wrong bill

A correctly calculated bill can still be the wrong bill when the published class no longer matches how the site draws power. RadiusPoint sees this in ExpenseLogic after a shift change, an automation project, a square-footage change, or a voltage upgrade. The utility did the arithmetic. The class was assigned years earlier. Finance kept paying because the due date was real.

The U.S. commercial average sat at 14.19 cents per kWh in June 2026, 4.8% above June 2025, according to the EIA Electricity Monthly Update (U.S. retail sector, June 2026). At that all-in level, a class that prices the same kilowatt-hour and the same peak kilowatt on a different published schedule changes the invoice without touching the meter. RadiusPoint does not publish a house percentage for reclassification savings. The dollar outcome is the difference between two filed tariffs on one load.

RadiusPoint has published other utility outcomes that are easy to confuse with a class change. Vacant cost recovery decreased utility expenses by 12%. A multi-location client paid $1,500 a month, $18,000 a year, for utilities at closed locations. An elevator-company engagement cut monthly waste expenditure 28%. Those credits stay in their own buckets in ExpenseLogic.

What load data do you need before you apply for a new rate class?

You need interval history, the current tariff sheet, billed demand, and a dated note on how the site now operates, before anyone files. RadiusPoint loads those four inputs into ExpenseLogic so the Rate-Class Fit Test has evidence. Twelve to 24 months of interval data is the usual ask from utilities and from analysts, because one summer peak can hide a winter load factor. The current tariff sheet tells you which classes exist and what kW floor, voltage, or hours each one requires.

A class application without operating-hours context fails in two directions. You can apply for a time-of-use class a 9-to-5 office cannot use. You can also stay on a high-demand general-service class after production moved off-peak. RadiusPoint will not file from a single monthly kWh total. ExpenseLogic needs the peak interval and the hours that created it.

Site status still matters. A closed location is a vacant-cost or disconnect job first. RadiusPoint will not reclassify a dark meter to “save” an account that should be ended.

The Rate-Class Fit Test

The Rate-Class Fit Test is RadiusPoint’s four-gate method for load factor, service voltage, demand threshold, and operating hours on one account. ExpenseLogic is where RadiusPoint stores the four inputs so the test can run when a site changes, not only when a consultant is hired. Ranking tariff pages in 2026 walk demand charges. They do not teach this four-gate sequence as a named finance test.

A fail on gate 4 with a pass on gate 3 is a time-of-use candidate. A fail on gate 2 is a service-level application, which can require utility construction, not only a paper filing. RadiusPoint writes the fail type onto the ExpenseLogic exception so facilities is not guessing. Vacant cost is the wrong payer. Bill audit is the wrong charge. Rate class is the wrong schedule. RadiusPoint will not treat those three as one “utility savings” line.

Who files a rate reclassification, and who has to approve it?

The customer of record files, and the utility (or the commission rules behind that utility) approves if the account qualifies. RadiusPoint prepares the analysis in ExpenseLogic and can submit on the client’s authority where a letter of agency or similar grant allows it. The utility is not obligated to shop you into a cheaper class. That is why a paid invoice can stay expensive for years.

Approval is a qualification test, not a negotiation. If the site is below a demand floor, the industrial class is closed. If the site cannot shed load, an interruptible rider is closed. RadiusPoint will show the failed gate rather than promise a move. Utility service options on the RadiusPoint site is the procurement companion for deregulated supply. Reclassification of the delivery class is a different filing.

Sharon Watkins founded RadiusPoint in January 1992. The class-change problem is an audit problem with a tariff book attached. ExpenseLogic is the working paper. RadiusPoint is the team that files.

How RadiusPoint and ExpenseLogic keep tariff analysis in the monthly cycle

RadiusPoint runs tariff analysis as managed Utility Expense Management, and ExpenseLogic watches for a load that has left its class. The utility expense management service already stores tariff schedules, demand readings, and site comparisons. Reclassification is the exception that says “apply,” not “dispute.”

A one-time consulting study goes stale when the next shift change lands. RadiusPoint keeps the Rate-Class Fit Test on the same monthly feed that catches a vacant name and a closed-site bill. ISO 9001 certification, in place at RadiusPoint since September 2002, is how that exception process stays repeatable when the location count moves. RadiusPoint published a client that grew from 170 to 1,200 locations. At that scale, a missed class on a handful of sites is not a rounding error.

RadiusPoint’s Capterra listing sat at 4.8 from 31 reviews through December 2025. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. Those credentials sit on the firm. They are not a savings percentage for a class change.

How we researched this

We compared the live RadiusPoint utility, vacant-cost, and rate-optimization pages with 2026 commercial tariff and demand-charge explainers. Those pages own demand math or a bundled “optimization” offer. They do not own a four-gate Rate-Class Fit Test or a three-way split between vacant payer, bill-audit charge, and rate class. Proof numbers come only from the published RadiusPoint proof library, from live RadiusPoint pages, and from the EIA June 2026 end-use table, all fetched 28 August 2026. No affiliate relationships. No invented reclassification savings percentage.

FAQ

Does rate reclassification work on gas, water, and waste, or only on electric?

Electric is where published commercial classes and demand gates show up most often. RadiusPoint still reviews gas, water, sewer, and waste schedules in ExpenseLogic when a territory publishes more than one class. The elevator-company 28% waste reduction was contract and vendor work, which RadiusPoint keeps separate from a class filing.

Can you recover prior months after the class is changed?

Only if the utility’s tariff or the commission rules allow a back-effective date, and only with interval evidence RadiusPoint can attach in ExpenseLogic. The operational job is to show the qualification date. Counsel and the utility decide whether that date is retroactive. RadiusPoint does not write tariff language.

Is a time-of-use enrollment the same as a rate reclassification?

Time-of-use is one kind of class or rider change. It still has to pass the operating-hours gate. RadiusPoint will not enroll a site that cannot move load off-peak and then call the higher on-peak rate a win.

How is this different from shopping a retail energy supplier?

Shopping a supplier changes the energy commodity in a deregulated market. Reclassification changes the utility’s published delivery or bundled class. RadiusPoint can support both. They are different filings and different lines on the invoice.

Do you need interval meters to do this?

You need enough history to prove load factor and peak timing. Interval data is the clean path. A monthly kWh and kW pair is a start, not a filing pack. RadiusPoint will say so in ExpenseLogic rather than file blind.

What to do before the next utility cycle

If you cannot name the published class on last month’s five largest electric accounts, start there. RadiusPoint will load those invoices into ExpenseLogic and run the Rate-Class Fit Test with you. Every cycle you skip is another month priced on a class the load may have already left.

Latest Updates

• 28 August 2026: Article drafted. Stats used: EIA commercial 14.19 cents/kWh in June 2026 (+4.8% YoY), 12% vacancy recovery, $1,500 / $18,000 closed-location utilities, 28% waste reduction, 170-to-1,200 locations, ISO 9001 since 2002, Capterra 4.8 / 31 through December 2025, Amalgam Insights 2024 Distinguished Vendor. No invented reclassification percentage.

References

1. Electricity Monthly Update, End Use: June 2026 | U.S. Energy Information Administration
2. ExpenseLogic | RadiusPoint
3. Utility Expense Management | RadiusPoint
4. Vacant Expense Recovery Solution | RadiusPoint
5. Utility Rate Optimization | RadiusPoint
6. Invoice Auditing Services: What They Cover and How to Choose a Provider | RadiusPoint
7. Utility Service Options | RadiusPoint
8. Sharon R. Watkins | RadiusPoint
9. RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
10. ExpenseLogic reviews | Capterra

Related articles

• Utility Expense Management
• Vacant Cost Recovery
• Utility Rate Optimization
• Invoice Auditing Services

Disclaimer

This article is general information for finance and facilities teams. It is not legal advice on tariffs, commission rules, or back-effective dates. Outcomes cited are from specific RadiusPoint client engagements already in the published proof library, or from named public sources, and are not a guarantee of future results.

By Sharon Watkins, Founder and CEO, RadiusPoint · 27 August 2026

Companies recover telecom refunds by filing a documented dispute, keeping a carrier case number open, and confirming the credit posted on a later invoice. A finding in a spreadsheet is not a refund. It is a claim that dies if nobody pursues it through the carrier’s window.

Refund recovery is the work that turns an audit exception into cash on a bill you can show finance. RadiusPoint’s live FAQ says credits pending are tracked in ExpenseLogic until the credit is received. That sentence is the job.

Key Takeaways

• Filed is not recovered. Recovery is the posted credit, allocated in the next GL file.
• A Fortune 100 manufacturer on RadiusPoint’s published record recovered $450,000 in telecom refunds in year one.
• Inventory management on that same published record recovered $174,000 in re-credits.
• Unneeded toll-free numbers produced $18,000 a year. Contract rate optimisation produced $120,000 a year.
• 47 CFR 64.2401 requires a toll-free dispute contact on the bill and forbids unauthorized charges (Cornell LII).

The Short Version

Keep a register: case number, service ID, months open, dollars claimed, window, status. Close a row only when the credit hits an invoice.

In This Article

• Finding an Error Is Not Recovering a Credit
• How does a carrier credit actually post?
• What do Truth-in-Billing rules actually give you?
• What belongs on the refund register?
• Which refund figures are published?
• How RadiusPoint Pursues the Case
• Frequently Asked Questions

Finding an Error Is Not Recovering a Credit

Finding an error is the audit, and recovering the credit is a second job with a case number and a posted invoice. Recovering the credit is a second job with a case number, a window, and a posted invoice. RadiusPoint already drafted a telecom-audit page for the first job. This page starts when that page would stop.

ExpenseLogic’s expense-audit module lists dispute tracking next to line-item detail. The capability statement names credit recovery and prevention of recurring error through maintained reference data. Prevention matters because a recovered credit that repeats next month was a refund, not a fix.

Sharon Watkins’s published line is that the telecom industry “can’t keep up with the ubiquitous challenges and doesn’t have the time to identify savings.” Identification is cheap compared with pursuit. The people who find the error are rarely the people the carrier will still take a call from six months later.

A glass manufacturer on the published record saved more than $100,000 in year one at 200% ROI. The number is useful here only if you ask whether those dollars were credits received or costs avoided. RadiusPoint’s live capability language groups “telecom refunds and cost savings” together on a $1.3 million program. This page prefers the figures that say refund or re-credit in the published library.

How does a carrier credit actually post?

A carrier credit posts as a later invoice line, bill adjustment, or remittance you can show finance once the carrier issues it. RadiusPoint tracks the pending credit inside ExpenseLogic until that moment.

Typical post paths:

1. Credit memo on the next BAN invoice.
2. Adjustment inside a tax or surcharge bucket, easy to miss.
3. Check or wire, rare on large estates.
4. “Account credit” that sits until someone asks AP to apply it.

If the credit is buried in a tax bucket, allocation has to follow it or the department that overpaid never sees the cash. That is why the last step of Credit-to-Cash is the GL file, not the carrier email.

Managed mobility services recover a different flavour of credit: zero-use and ex-employee lines that should stop billing. A food service client cut 22% ($400,000) in year one across more than 600 lines. Some of that is avoidance going forward. Ask which dollars were back-credits.

Two-day invoice processing, a live FAQ claim, helps you see the credit when it lands. It does not file the dispute.

What do Truth-in-Billing rules actually give you?

Truth-in-Billing rules give you a dispute contact and a clear bill, not a deposited refund you still must pursue. RadiusPoint’s job is to file inside the window and keep the case alive.

47 CFR 64.2401 requires a clear description of each charge, a named provider, a distinct section for third-party charges, a toll-free inquiry number, and a ban on unauthorized charges (e-CFR via Cornell). The FCC’s Truth-in-Billing page restates those duties and was updated 22 April 2025 (FCC).

Those rules give you a contact and a right to contest. They do not deposit the money. Cramming (unauthorized third-party charges) is the consumer-facing cousin of a problem enterprises still see on BAN invoices. Recovery is still a case file.

Gartner forecast $1.354 trillion in communications services spend for 2026 (Gartner, 27 July 2026). A small error rate on a number that large is why pursuit, not discovery, is the scarce skill.

What belongs on the refund register?

Finance should demand a six-field refund register: case number, service ID, months open, dollars claimed, window, and posted status. RadiusPoint’s pending-credit tracking is that register inside ExpenseLogic.

A register without a case number is a wish list. A register that closes on “carrier agreed” is a wish list with a date. Close only on a posted invoice image.

Unapplied credits are a named finding type in RadiusPoint’s audit language: a credit agreed but never posted. That row is why this page exists. Inventory of record plus the register is how you stop paying for the same error after you “won.”

Utility expense management (UEM means Utility Expense Management, not Unified Endpoint Management) produces the same register for meters. Do not mix those rows into a telecom BAN without a service-ID key.

Which refund figures are published?

RadiusPoint’s usable refund proof is the published library of published named client outcomes, and never a guarantee of future cash. The 2019 ROI figure of 437% appears on a live capability page and is not a named line in the published proof library, so it is not used here.

published figures that name refund, re-credit, or a cash-like recovery:

• Fortune 100 manufacturer: $450,000 telecom refunds, year one.
• Inventory management: $174,000 in re-credits.
• Unneeded toll-free numbers: $18,000 a year.
• Contract rate optimisation: $120,000 a year.
• $250,000-plus in unrealised cost savings uncovered (published language; treat as uncovered value, not as posted cash, unless the case file says posted).

Industry range, hedged: organisations implementing TEM typically see 15% to 30% cost reduction in year one. That is category language, not a RadiusPoint refund promise. Average ROI of 370% to 580% is an industry-range statement and is an average of self-published figures. Prefer a named case.

Has managed more than $550 million in annual client spend is an industry-range statement and from 2019. Skip it when you are proving a refund.

Capterra 4.8 from 31 reviews through December 2025 (Capterra), ISO 9001 since 2002, and Amalgam Insights Distinguished Vendor 2024 are process credentials. They support the claim that someone will still be on the case next quarter.

How RadiusPoint Pursues the Case

RadiusPoint analysts file with the carrier under a scoped letter of agency, then keep the case in ExpenseLogic until the credit posts. Telecom expense management is the service wrapper. Sharon Watkins is the founder who still treats pending credits as unfinished work.

The about RadiusPoint page is the company story. The operating rule is here: a dedicated internal audit team reports daily statistics on invoice processing and support-ticket accuracy, per the live capability statement. Daily is the cadence a register needs.

An automotive salvage client published $1.3 million on the TEM page. The capability page also cites a $1.3 million telecom refunds-and-savings program. Use the figure as published scale. Ask, in diligence, how much of it was posted credits versus avoided spend.

Ask to see five closed rows: case number, invoice image of the credit, and the GL line. If a provider can find errors but cannot show those three, you have an audit. You do not have recovery.

How We Researched This

On 28 August 2026 we read 47 CFR 64.2401, the FCC Truth-in-Billing page (updated 22 April 2025), and Gartner’s 27 July 2026 IT spend forecast, then mapped RadiusPoint’s live FAQ pending-credit language and published proof library. Invoice Audit 2 was treated as a sibling finding page, not as a source to rewrite. 437% (2019) was excluded because it is not a named published proof line. No affiliate relationships.

Frequently Asked Questions

If the auditor found $200,000, do we have $200,000?

No. You have a claim. You have the money when the credit posts and the GL file reflects it. Ask for the register, not the slide.

What is the difference between a refund and cost avoidance?

A refund or re-credit is cash or a billed credit for a past error. Avoidance is the same error not repeating. Both matter. Only the first belongs on a refund page.

Do Truth-in-Billing rules force the carrier to pay?

They force a clear bill, a dispute contact, and no unauthorized charges. They do not set your enterprise window or wire the money. You still file and pursue.

Can we recover credits on wireless lines?

Yes, when the line should not have billed (zero-use, ex-employee, wrong plan). RadiusPoint’s MMS work is the usual path. The register fields do not change.

Why not use the 2019 437% ROI figure?

It is not a named line in the published RadiusPoint proof library. This page uses named refund and re-credit cases instead.

Close the Row When the Invoice Shows the Credit

A dispute without a posted invoice is still open, and the register should keep that row live until the credit image exists. Build the register. Staff the pursuit. Allocate the cash.

Request a demo of ExpenseLogic and ask to walk five pending credits to posted. Every month a case sits without a number is another month the carrier keeps the money.

Latest Updates

• 27 August 2026: Drafted as a recovery page, not an audit rewrite. published refund figures only. 437% excluded.

References

1. 47 CFR § 64.2401 – Truth-in-Billing Requirements | Cornell LII / e-CFR
2. Truth-In-Billing Policy | Federal Communications Commission, updated 22 April 2025
3. Gartner Forecasts Worldwide IT Spending to Grow 14.2% in 2026, Totaling $6.37 Trillion | Gartner newsroom
4. ExpenseLogic | Capterra
5. Telecom Expense Management | RadiusPoint
6. ExpenseLogic | RadiusPoint
7. Managed Mobility Services | RadiusPoint
8. About | RadiusPoint
9. RadiusPoint Capability Statement | RadiusPoint
10. Sharon Watkins | RadiusPoint

Related Reading

• Telecom expense management
• ExpenseLogic
• Capability statement
• Sharon Watkins

This article is educational. RadiusPoint does not guarantee refund amounts, credit posting dates, or carrier outcomes. Figures were current as of 28 August 2026 and should be re-checked on refresh.

By Sharon Watkins, Founder and CEO, RadiusPoint · 26 August 2026

A telecom expense management rollout takes as long as it takes to build a defensible inventory, collect letters of agency, gather scattered invoices, and agree the ERP file spec. RadiusPoint does not publish a week count, and any provider who gives you one before seeing those four inputs is selling a Gantt, not a close date.

TEM implementation time is gated by inventory completeness, not by software provisioning. You bought the program because invoices were already late and incomplete. That mess is the clock.

Key Takeaways

• RadiusPoint’s published proof is stated in year-one outcomes, not in a published week range.
• Organisations implementing TEM typically see 15% to 30% cost reduction in year one. That is an industry-range statement, not a RadiusPoint guarantee.
• A Fortune 100 manufacturer on RadiusPoint’s published record recovered $450,000 in telecom refunds in year one, plus $850,000 in ongoing annual savings.
• A food service client cut 22% ($400,000) in year one across more than 600 lines.
• Two-day invoice processing is a live RadiusPoint operating claim after a bill exists. It is not a rollout clock.

The Short Version

Do not accept a week count as the answer. Ask which work unit is open: agency letters, invoice scatter, inventory build, or the ERP spec. Published RadiusPoint proof lands in year one.

In This Article

• Why RadiusPoint Will Not Quote a Week Count
• What actually consumes the calendar?
• Why is year one the honest published window?
• What must you bring before day one?
• What Live Means, and What It Does Not
• Frequently Asked Questions

Why RadiusPoint Will Not Quote a Week Count

RadiusPoint will not quote a TEM week count because no published source in the 2026 proof library states one. Sharon Watkins has run this company since January 1992. The honest answer after three decades is that the inventory is the clock.

Vendor blogs publish 90 to 120 days, 90 to 180 days, or 4 to 8 weeks. Those are their marketing ranges, not RadiusPoint’s, and they are not adopted here. The capability statement says setup is completed by the RadiusPoint team and that configuration follows the client. It does not attach a week number to that sentence.

ISO 9001 since September 2002 and a 2024 Amalgam Insights Distinguished Vendor listing are process signals. They are not a Gantt. Capterra lists ExpenseLogic at 4.8 from 31 reviews through December 2025 (Capterra). Reviews describe the work. They do not invent a week count we refused to invent.

Gartner named RadiusPoint a Representative Vendor in the 2023 Market Guide for TEM Services. Always keep the year. That recognition is not a delivery calendar.

What actually consumes the calendar?

Four client-side inputs consume the calendar: letters of agency, invoice scatter, inventory quality, and ERP specs RadiusPoint cannot skip. RadiusPoint’s telecom expense management service cannot audit a circuit the carrier has not confirmed.

Letters of agency are a separate page in this cluster. Here they matter as a gate: no LOA, no customer service records, no inventory of record. Invoice scatter is the second gate. Twelve to thirty-six months of bills usually sit in AP, IT, and site inboxes. That gathering is not software.

Inventory build is the longest honest work. ExpenseLogic can store the result. It cannot invent a CSR the carrier has not sent. The ERP spec is the fourth gate: accrual files and GL coding have to match the client’s close, which is why RadiusPoint collects file specifications during setup.

A glass manufacturer on the published record saved more than $100,000 in year one at 200% ROI. That number is a year-one outcome. It is not evidence the project finished in a quoted week.

Why is year one the honest published window?

Year one is the only time window RadiusPoint’s published proof consistently uses for outcomes rather than a week count. If a proposal talks in weeks and the proof talks in years, believe the proof.

Published year-one marks:

• Fortune 100 manufacturer: $450,000 telecom refunds, $850,000 ongoing annual savings, $1.3 million total year-one impact, more than 10,000 wireless devices.
• Food service: 22% reduction, $400,000, more than 600 lines.
• Global glass manufacturer: more than $100,000, 200% ROI.
• Healthcare provider: 26% reduction in telecom expenses (period stated as the engagement result, not as a week count).

Industry range, hedged: organisations implementing TEM typically see 15% to 30% cost reduction in year one. Attribute that to the TEM category, not to a RadiusPoint promise.

Has managed more than $550 million in annual client spend is an industry-range statement and dates to 2019. Use it as historical scale only. Client growth from 170 to 1,200 locations is published scalability proof, which tells you the platform can absorb a larger estate. It still does not give you a week count.

What must you bring before day one?

You must bring carrier and BAN lists, signed letters of agency, trusted inventory, and the ERP layout AP will accept. RadiusPoint’s managed mobility services add employee IDs and device serials to that pack.

A later page in this cluster will list onboarding data in full. This section only names the items that move the clock. If any of them are missing, the honest range stays “year one to first validated outcomes,” not a week you picked because a competitor printed one.

About RadiusPoint states the firm has been serving businesses since 1992. Longevity is relevant because carrier processes have not gotten faster. The telecom industry, in Sharon Watkins’s published line, “can’t keep up with the ubiquitous challenges and doesn’t have the time to identify savings.” That is why the rollout is a records project.

Utility expense management (UEM means Utility Expense Management, not Unified Endpoint Management) adds meter lists and tariffs to the same pack when utilities are in scope. Do not pretend a TEM-only Gantt covers meters.

What Live Means, and What It Does Not

Live means one complete invoice cycle has been received, validated, exceptioned, and exported into AP, not merely a portal login. RadiusPoint’s two-day processing claim starts after that cycle exists. A portal login is not live.

Dispute credits still in flight are not a reason to call the rollout unfinished, and they are not a reason to call it finished. They are a register. Healthcare 448% ROI and HumanGood 315% ROI are published outcomes of running the process, not of flipping a switch.

Ask every provider a single question: what work is complete on the day they say they are live? If the answer is “the software is provisioned,” you still do not have TEM. If the answer is “the inventory of record and the first coded file,” you are in the honest window.

How We Researched This

On 28 August 2026 we compared Tellennium, Socium, Asignet, and Temforce implementation pages, then refused to import their week counts as RadiusPoint’s range. published items were taken from the published RadiusPoint proof library. Live FAQ supplied the two-day processing and setup-spec claims. Gartner 2023 naming is year-stamped. No affiliate relationships.

Frequently Asked Questions

How long does a TEM implementation take at RadiusPoint?

RadiusPoint does not publish a week count. Time follows letters of agency, invoice scatter, inventory build, and the ERP file spec. Published proof is year-one outcomes.

Why do other vendors quote 90 days or 8 weeks?

Those are their marketing ranges. They are not in RadiusPoint’s published proof library, so they are not repeated here as a promise or as our range.

Is two-day invoice processing the rollout time?

No. Two-day processing is how fast a received invoice is worked after go-live. It is not how long it takes to build the inventory that invoice is tested against.

When should we expect savings?

Published RadiusPoint cases that state a period use year one. Category-level industry language is 15% to 30% in year one for organisations that implement TEM. Neither is a guarantee.

What is the fastest way to stall a rollout?

Leave letters of agency unsigned, or keep invoices in site inboxes. Software cannot request a CSR the carrier has not been authorised to send.

Ask for Work Units, Not a Gantt

If a proposal’s first number is a week count and its proof is year-one, the week count is decoration. Score the four gates. Then look at year-one cases.

Request a demo of ExpenseLogic and ask what RadiusPoint considers live. Every month spent arguing about a fictional week is a month the same inventory errors keep billing.

Latest Updates

• 26 August 2026: Drafted with no invented week counts. Honest window taken from published year-one cases and industry-range 15-30% category language.

References

1. ExpenseLogic | Capterra
2. Gartner Forecasts Worldwide IT Spending to Grow 14.2% in 2026, Totaling $6.37 Trillion | Gartner newsroom (market context only)
3. Telecom Expense Management | RadiusPoint
4. ExpenseLogic | RadiusPoint
5. Managed Mobility Services | RadiusPoint
6. About | RadiusPoint
7. RadiusPoint Capability Statement | RadiusPoint
8. Sharon Watkins | RadiusPoint

Related Reading

• Telecom expense management
• ExpenseLogic
• Capability statement
• Sharon Watkins

This article is educational. RadiusPoint does not guarantee a rollout date, a week count, or a savings percentage. Figures were current as of 28 August 2026 and should be re-checked on refresh.

By Sharon Watkins, Founder and CEO, RadiusPoint · 24 August 2026

A telecom accrual file is a structured estimate of circuits, lines, and meters that were consumed this period but not yet invoiced, coded so the close can post. If you cannot name the unbilled service IDs at month-end, you are not accruing telecom. You are hoping last month repeats.

A telecom accrual file is the finance extract of live inventory that still lacks an invoice, not a copy of the AP pay file. RadiusPoint’s live TEM FAQ says the company can provide a monthly accrual file based on the client’s accounting specifications, delivered on the client’s timing.

Key Takeaways

• Accrued expenses are costs incurred with no invoice in hand by close. Accounts payable starts when the invoice arrives (FinQuery, 29 May 2026).
• RadiusPoint works a missing-bill report daily and can deliver a monthly accrual file specified during setup (live TEM FAQ).
• ExpenseLogic lists accrual files next to allocation in the accounts payable module.
• RadiusPoint processes invoices within a two-day window after receipt, a live FAQ operating claim, which shrinks late-fee risk once the bill exists.
• Gartner forecast $1.354 trillion in worldwide communications services spend for 2026 (Gartner, 27 July 2026).

The Short Version

Build the file from inventory and rates, not from last month’s paid total. Reverse it when the invoice lands so you do not expense the same circuit twice.

In This Article

• The Accrual File, Defined
• How do finance teams calculate the rows?
• Why is a missing bill an accrual row?
• Why is last month’s total a weak accrual?
• What RadiusPoint Delivers at Close
• Frequently Asked Questions

The Accrual File, Defined

A telecom accrual file is a row-level list of unbilled service IDs with amount, period, GL, and reversal flag. RadiusPoint treats it as an AP-module output, sitting beside allocation, not as a slide in a QBR.

FinQuery’s May 2026 explainer is the accounting backbone: accrued expenses exist because the benefit was consumed and the invoice was not. Utilities and usage-based services are named in that category. Telecom circuits and wireless lines behave the same way. The file is how a TEM program makes that journal auditable.

The capability statement lists accounts payable feeds, accrual files, and general ledger coding in the client’s own chart of accounts. That sentence is the product definition. This page teaches the contents.

Do not confuse the file with RadiusPoint’s older misspelled accrual-accounting primer. That post explains the principle. This page explains the artifact finance actually loads.

How do finance teams calculate the rows?

Finance calculates each accrual row from a live inventory record, a rate, and the number of unbilled days in the period. RadiusPoint’s telecom expense management stack already holds the inventory, the contract rate, and the invoice history, which is why the file can be more than a guess.

Three honest methods, in descending quality:

1. Contract or tariff rate times the open days for that service ID.
2. Last billed amount for the same service ID, adjusted for known MACDs.
3. Account-level average, used only when the inventory row is still being built.

Method 3 is a placeholder. It is how most closes work today, and it is why a late $80,000 circuit makes the next month look like a miracle. Healthcare AP and ordering automation on RadiusPoint’s published record showed a 448% ROI. HumanGood, a named client, showed 315% ROI. Those figures are published process outcomes. They are not a promise that your accrual variance disappears.

Reverse the row when the invoice posts. FinQuery is blunt: accruals that are not reversed double-count. ExpenseLogic’s job is to know which invoice killed which accrual row.

Why is a missing bill an accrual row?

A missing bill on a live service is an accrual row because the inventory says you consumed it this period. RadiusPoint works the missing-bill report daily, tracks vendor conversations, and sets reminders if the invoice is still out, which is the live FAQ language.

Utility expense management (UEM means Utility Expense Management here, not Unified Endpoint Management) produces the same artifact for meters. Electric, gas, water, sewer, and waste invoices arrive on their own calendars. A retail chain that closes on day six cannot wait for every utility.

Client growth from 170 to 1,200 locations is published RadiusPoint scalability proof. At 1,200 sites the missing-bill report is the close. Daily missing-bill work is also how RadiusPoint says it avoids disconnects and late fees, which is a service-continuity claim, not an accrual formula.

Two-day invoice processing after receipt is a live operating claim. It does not replace the accrual. It shortens the gap between “invoice exists” and “AP can post,” so the reversal happens inside the next cycle instead of the next quarter.

Why is last month’s total a weak accrual?

Last month’s paid total ignores new circuits, dead circuits, late credits, and every BAN that did not bill on time. RadiusPoint still sees organisations close on that number because it is available.

Gartner’s July 2026 communications services line is $1.354 trillion, growing 4.4% (Gartner newsroom). A category that large, moving 4.4%, will not land every invoice before your close calendar. The file exists because the market is late, not because finance is fussy.

Capterra lists ExpenseLogic at 4.8 from 31 reviews through December 2025 (Capterra). ISO 9001 has been in place since September 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor in 2024. Those are process credentials for a file an auditor will sample.

Organisations implementing TEM typically see 15% to 30% cost reduction in year one. That range is an industry-range statement, not a RadiusPoint guarantee. Write it that way. Do not put it in the accrual file as a plug.

What RadiusPoint Delivers at Close

RadiusPoint delivers the monthly accrual file on the specification collected during setup, then keeps delivering it on the client’s close calendar. Sharon Watkins has been adjacent to this problem since 1992: invoices that arrive after the period they describe.

The about RadiusPoint page is the company narrative. The operating pieces are here: inventory of record, daily missing-bill report, two-day process once the bill exists, coded GL and accrual extracts.

Has managed more than $550 million in annual client spend is an industry-range 2019-era statement. Use it only as historical scale, or wait for an updated figure. Prefer the named published cases when you need a number a prospect can check.

Ask to see last month’s accrual file and the reversals that cleared this month. If a provider cannot show both, they are sending you a spend report.

How We Researched This

On 28 August 2026 we compared RadiusPoint’s live FAQ, ExpenseLogic AP module copy, and capability statement against FinQuery’s 29 May 2026 accrued-versus-AP explainer and Gartner’s 27 July 2026 IT spend forecast. We treated the misspelled live accrual-accounting post as a sibling primer, not as this page. published RadiusPoint figures only. No affiliate relationships.

Frequently Asked Questions

Is the accrual file the same as the invoice upload?

No. The invoice upload is AP. The accrual file is the estimate for service IDs that have not been invoiced yet. RadiusPoint produces both, on the client’s file spec.

What if we just accrue a flat percentage of last year?

You will be close in a quiet month and wrong in a month with installs, disconnects, or a missing BAN. Inventory-based rows survive those months. Flat percentages do not.

Do utilities belong in a telecom accrual file?

They belong in the same close package, often as a second file or a second sheet, at meter grain. RadiusPoint’s UEM (Utility Expense Management) is the source of those rows.

When do you reverse the accrual?

When the matching invoice posts, or when you learn the service died. FinQuery’s control point is the same: reverse in the period the invoice is expected so the expense hits once.

Does two-day invoice processing replace the accrual?

No. Two-day processing starts after the invoice exists. The accrual covers the days before it exists. You need both.

Close on Inventory, Not on Hope

If the file cannot name the unbilled circuit, you do not have a telecom accrual, only a plug for the close. You have a plug.

Request a demo of ExpenseLogic and ask for the monthly accrual file layout plus the missing-bill report. Every close that skips those rows is another variance you will explain in the next meeting.

Latest Updates

• 24 August 2026: Drafted from live TEM FAQ (accrual file, missing-bill, two-day processing), FinQuery 29 May 2026, Gartner 27 July 2026, and published-proof proof rules.

References

1. Accrued Expenses vs. Accounts Payable Explained | FinQuery, 29 May 2026
2. Gartner Forecasts Worldwide IT Spending to Grow 14.2% in 2026, Totaling $6.37 Trillion | Gartner newsroom
3. ExpenseLogic | Capterra
4. ExpenseLogic | RadiusPoint
5. Telecom Expense Management | RadiusPoint
6. Utility Expense Management | RadiusPoint
7. About | RadiusPoint
8. RadiusPoint Capability Statement | RadiusPoint
9. Sharon Watkins | RadiusPoint

Related Reading

• ExpenseLogic
• Telecom expense management
• Capability statement
• About RadiusPoint

This article is educational. RadiusPoint does not guarantee close accuracy or a specific accrual variance. Figures were current as of 28 August 2026 and should be re-checked on refresh.

By Sharon Watkins, Founder and CEO, RadiusPoint · 17 August 2026 · 11 min read

Wireless expense management is the mobile-billing discipline inside telecom expense management; TEM still owns wireline, data, contracts, and the GL file. Your organization negotiated a wireless rate. Your organization isn’t being billed at that rate on every handset. Both can be true for 18 months. RadiusPoint runs WEM and TEM on ExpenseLogic so finance isn’t buying two truths.

This page is a comparison. It isn’t TEM 101. For the definition of the parent category, use What Is Telecom Expense Management?. It’s also not WEM versus MDM. Device security is a different buy.

Key Takeaways

• ETMA describes wireless expense management as a special category of TEM focused on wireless services and mobile devices. Wikipedia calls WEM an extension of TEM.
• RadiusPoint’s Fortune 100 wireless program recovered more than $450,000 in refunds and continues to save more than $830,000 a year.
• A RadiusPoint food service mobility engagement cut cost 22%, more than $400,000 a year, across 600-plus lines.
• WEM is billing, plans, zero-use, and Employee ID. TEM is that work plus wireline, data circuits, allocation, and bill pay.
• Managed mobility services sit beside both: staging, repair, recovery. RadiusPoint delivers all three through ExpenseLogic.

The Short Version

Buy WEM when the estate is handsets and pooled data. Buy TEM when the estate also includes circuits, BANs, and a month-end file. Buy MMS when you also kit and retire the device. RadiusPoint will run the mix you actually have.

In this article

• The difference in one table
• What does wireless expense management cover that TEM doesn’t own alone?
• Where TEM still includes wireless billing
• When do you need WEM instead of a full TEM program?
• How WEM, TEM, and managed mobility services stack
• Why do buyers confuse WEM with TEM in RFPs?
• How RadiusPoint runs both inside ExpenseLogic

The difference in one table

The difference is scope: WEM is the wireless invoice, plan, and user record, and TEM is the whole communications estate those wireless lines sit inside. RadiusPoint keeps both scopes in ExpenseLogic so a controller can see a handset MRC and a circuit MRC on one allocation file. ETMA is the clean third-party sentence: WEM programs are a special category of TEM programs with a focus on wireless services and mobile devices.

A glass manufacturer working with RadiusPoint saved more than $100,000 on telecom. That’s TEM proof. The $830,000 figure is WEM proof. Don’t paste one into the other RFP.

What does wireless expense management cover that TEM doesn’t own alone?

Wireless expense management covers Employee ID, rate-plan fit, roaming, pooled data, and zero-use flags a wireline-first TEM process will skip. RadiusPoint runs those flags in ExpenseLogic as a mobility workflow, then rolls the result into the TEM invoice file so AP still sees one vendor. TEM can include wireless. WEM is what you call the work when the wireless file is the job.

The food service case needed a Register Your Line portal, a wireless policy, and a 60-day registration window. That’s WEM operating cadence. A circuit audit doesn’t ask 600 people to claim a number. ExpenseLogic held the claimed set.

Teligistics and other WEM vendors contrast WEM with MDM. We aren’t repeating that contrast here. MDM is endpoint control. WEM is the bill. RadiusPoint will say that once and move on.

Where TEM still includes wireless billing

TEM still includes wireless billing because the wireless BAN is a telecom invoice, and the GL doesn’t care that the access method is radio. RadiusPoint’s telecom expense management service already lists line-item audit across wireline, wireless, and data. ExpenseLogic is the same platform. Calling the wireless slice WEM doesn’t pull it out of TEM. It names the specialist queue.

A Fortune 100 estate of about 10,000 wireless devices still needed TEM invoice processing, contract terms, and exception reporting. RadiusPoint’s published $450,000 refund pile sat next to the $830,000 annual exception savings. That’s one program with two labels.

Organizations implementing TEM typically see 15% to 30% cost reduction in year one. Treat that as a category range, not a RadiusPoint guarantee. WEM-only cleanups can land inside that range when the estate is almost all handsets.

When do you need WEM instead of a full TEM program?

You need WEM instead of full TEM when the unexplained spend is almost all mobile and the circuit file is already small. RadiusPoint will still load those wireless invoices into ExpenseLogic. You don’t need to buy a wireline project to retire 56 ex-employee lines. You do need TEM when AP is also coding MPLS, DIA, and toll-free on the same close.

How WEM, TEM, and managed mobility services stack

WEM sits inside TEM, and managed mobility services sit beside both as the device-lifecycle layer RadiusPoint runs on the same ExpenseLogic record. Managed mobility services cover procurement, staging, kitting, repair, recovery, and retirement. WEM covers the bill that follows the device. TEM covers that bill plus every other communications invoice. Confusing the three is how RFPs ask for “TEM” and evaluate a kitting warehouse.

Why do buyers confuse WEM with TEM in RFPs?

Buyers confuse WEM with TEM because every wireless invoice is a telecom invoice, and vendor marketing uses the two acronyms as synonyms. RadiusPoint writes the RFP response from the ExpenseLogic module list, not from the acronym in the subject line. If the statement of work is “audit AT&T and Verizon wireless, match HR, kill zero-use,” you’ve a WEM SOW. If it’s “process every BAN, allocate to cost center, produce an accrual file,” you’ve a TEM SOW.

A healthcare provider in the RadiusPoint proof library cut telecom expenses 26%. Read the case before you file it under WEM. Telecom is the parent. Wireless may be the slice that moved.

ISO 9001 has been in place at RadiusPoint since September 2002. The process name on the SOP is less important than whether ExpenseLogic holds the inventory of record. Ask for that file.

How RadiusPoint runs both inside ExpenseLogic

RadiusPoint runs WEM and TEM as one ExpenseLogic service: wireless gets Employee IDs, circuits get service IDs, AP gets one file. The about page still describes a company founded in 1992 to manage telecom, technology, and utility expenses. Utility Expense Management stays on its own UEM page. Don’t fold electric BANs into a WEM buy.

Capterra listed ExpenseLogic at 4.8 from 31 reviews through December 2025. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. Those anchors describe the firm. The $830,000 and the 22% describe the wireless slice.

Sharon Watkins is the founder who still sits with the software team. The comparison she wants buyers to make isn’t WEM versus TEM as a religious war. It’s “which layer is failing this quarter,” then load that layer into ExpenseLogic.

How we researched this

We read ETMA and Wikipedia on WEM, Teligistics on WEM versus MDM (used only as a boundary we refuse to rewrite), Asignet and Vigilis on TEM-plus-wireless, and RadiusPoint’s live TEM, MMS, and wireless cases. The gap is a four-row buy grid and a three-layer stack that includes Utility Expense Management as a non-TEM row. Proof is from published RadiusPoint materials and live pages fetched 28 August 2026. No affiliate relationships.

FAQ

Is WEM a subset of TEM or a separate buy?

Functionally a subset. Commercially a separate SOW when the estate is almost all mobile. RadiusPoint will sell the slice or the parent and still use ExpenseLogic.

Does WEM include device procurement?

Not by itself. Procurement, staging, and repair are managed mobility services. RadiusPoint will attach MMS when the device, not only the bill, is the problem.

Can one platform do WEM and wireline TEM together?

Yes. ExpenseLogic is built for that join. That’s the point of RadiusPoint’s single-platform pitch against buying a wireless tool and a circuit tool.

How is WEM different from rate-plan optimization software?

Rate-plan software suggests a cheaper plan. WEM, as RadiusPoint runs it, also matches HR, kills zero-use, files disputes, and allocates the invoice. A suggestion without a disconnect ticket is a slide.

Do utility invoices belong in TEM or in WEM?

Neither. They belong in Utility Expense Management (UEM, not Unified Endpoint Management). RadiusPoint will take the electric BAN on the UEM side of ExpenseLogic.

What to do with the next RFP

Rewrite the first paragraph so it names handsets, circuits, or both. Send that paragraph to RadiusPoint. ExpenseLogic can be scoped to the sentence you actually wrote.

Latest Updates

• 17 August 2026: Article drafted. Fortune 100 $450,000 / $830,000 / 10,000 devices, food service 22% / $400,000 / 600-plus, glass $100,000, healthcare 26%, ISO 9001 since 2002, Capterra 4.8 / 31, Amalgam Insights 2024, founded 1992. Category range: 15% to 30% TEM category range.

References

1. What is Wireless Expense Management (WEM)? | ETMA
2. Wireless Expense Management | Wikipedia
3. ExpenseLogic | RadiusPoint
4. What Is Telecom Expense Management? | RadiusPoint
5. Telecom Expense Management | RadiusPoint
6. Managed Mobility Services | RadiusPoint
7. Utility Expense Management | RadiusPoint
8. About RadiusPoint | RadiusPoint
9. Sharon R. Watkins | RadiusPoint
10. Wireless Expense Management Yields $830K in Annual Savings | RadiusPoint

Related articles

• What Is Telecom Expense Management?
• Managed Mobility Services
• Telecom Expense Management

Disclaimer

This article is general information for finance and telecom buyers. It is not a vendor-selection guarantee. Outcomes cited are from specific RadiusPoint client engagements in the published proof library. Category ranges are not RadiusPoint promises.