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.
| Right | What it authorizes at the carrier | Routine audit work needs it | Where control belongs |
|---|---|---|---|
| Inquire (read) | Pull CSRs, view account, line, and feature inventory | Yes | The LOA |
| Dispute | File billing disputes and pursue credits and refunds | Yes | The LOA |
| Order (adds, moves, changes) | Place new services and change existing ones | No, not by default | Your approval workflow |
| Disconnect | Cancel or disconnect provisioned services | Only on explicit approval | Your approval workflow |
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.
- 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.
- 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.
- Locations and geography. For a regional estate or a pilot, bound the LOA to named sites or states so it matches the actual work.
- An expiry date. Tie the end date to the contract term. Open ended agency outlives the relationship that justified it.
- 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.