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.
Key Takeaways
- A spreadsheet tracks totals well and evidence poorly. It records what you paid, not the proof, history, and documents that justify each charge at audit.
- Growth breaks the file through concurrency and evidence before it breaks the arithmetic: multiple editors, MACD volume, contract images, dispute packets, and versioned GL files that one spreadsheet can’t hold together.
- ExpenseLogic keeps inventory, contract, MACD ticket, invoice line, and GL code linked as one record, so every change traces from the asset to the invoice to the general ledger.
- RadiusPoint isn’t handing you a file to maintain. Its staff work the invoices, disputes, and MACD tickets inside ExpenseLogic on your behalf.
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.
| Link in the record | What it answers | What a spreadsheet holds instead |
|---|---|---|
| Inventory (asset or service) | What exists, where, and under whose Employee ID | A row that may already be out of date |
| Contract | The rate this asset should bill at | A document in someone’s inbox |
| MACD ticket | What changed, when, and who approved it | Usually nothing at all |
| Invoice line | What the carrier actually billed | The number you keyed by hand |
| GL code | Where the cost is allocated | A formula that breaks on edit |
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.