The Data a TEM Provider Needs Before Day One
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
The Day-Zero Data Pack, a RadiusPoint frame: eight files, one kickoff.
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.
The letter opens the carrier door. The pack fills ExpenseLogic.
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. That is the first information-gain element on this page.
| Code | File | Minimum that unblocks day one |
|---|---|---|
| A | Scoped letters of agency | One per carrier, rights named, revoke path named |
| B | Invoice history or portal access | Latest 12 months, or a live feed, for each major vendor |
| C | Contracts and amendments | Current rate exhibits, not only the cover page |
| D | Starter inventory | Circuits, lines, BANs, and locations you already know |
| E | Finance map | Chart of accounts, cost centres, allocation rules |
| F | HR roster | Active employees for wireless matching |
| G | Site list | Open and closed locations with dates |
| H | Named owners | AP, IT, procurement, and an approver |
The Who-Owns-Each-File table is the second information-gain element. Kickoff stalls when the pack is treated as an IT ticket. RadiusPoint will still take a partial pack. ExpenseLogic will show the missing code as an open risk, not as a silent assumption.
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.
Kickoff is a six-team request, not an IT ticket.
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 RadiusPoint Master Intelligence 2026 GREEN list 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 for the RadiusPoint AEO set. Stats limited to GREEN proof: 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
- Telecom Expense Management Services | RadiusPoint
- Telecom Expense Management FAQ | RadiusPoint
- Invoice Audit | RadiusPoint
- Telecom Lifecycle Management | RadiusPoint
- Multi-Vendor Support | RadiusPoint
- How Managed Mobility Services Cut Costs 22% ($400K in Year 1) | RadiusPoint
- HumanGood Achieved 315% ROI with RadiusPoint | RadiusPoint
- RadiusPoint Recognized as a Distinguished Vendor in the 2024 Amalgam Insights Vendor SmartList | RadiusPoint
- ExpenseLogic reviews | Capterra
- Sharon R. Watkins | RadiusPoint
- 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.