MSPs struggle with telecom billing and taxes because both sit outside standard managed services logic. Telecom billing requires usage-based rating from carrier CDR data, something no PSA is built to handle. Communications taxes are calculated by customer location and service type across constantly changing jurisdictions, not by standard sales tax rules. Get either one wrong and you’re losing revenue, carrying a tax liability, or spending more time on billing admin than the margin from the service is worth.
These are two separate problems, and they stack on top of each other.
The billing side is harder than it looks
Most of an MSP’s recurring revenue is flat. A service agreement, a monthly managed services fee, a handful of add-ons. That’s billing you can run almost on autopilot.
Telecom is typically usage-based. You’re billing for actual call volume: minutes made and received, messages sent, seats active, international calls placed. That data lives in your carrier’s systems and your UCaaS platform, not your PSA. It comes in a different format from every provider. And it has to be rated, which means applying your pricing structure to raw call records before a single invoice can go out.
Without a system built for this, that process runs through spreadsheets and manual carrier reports. You’re downloading CDR files, normalising them, building out rate calculations by hand, then manually pushing the results into your PSA or accounting platform. Every billing cycle.
The complexity compounds quickly. Most MSPs reselling UCaaS work with more than one provider — each sending CDR data in its own format, on its own schedule. Normalising data from multiple sources before rating even starts adds hours. Then add bundles and usage pools: a customer on a 1,000-minute shared plan who goes over, or a per-seat package with variable month-to-month usage. Multi-site customers, where each location needs to be rated separately with potentially different pricing, add another layer. The more customers you add, the worse the manual process gets.
Two things happen as a result.
The first is revenue leakage. If your billing process is manual, something will get missed. A service that was delivered but not captured in the data pull. A pricing rule that wasn’t updated when you changed a rate. A customer site that fell through the cracks. MSPs who switch to automated rating consistently find charges they’d been missing, sometimes running to thousands of dollars per month in previously unbilled services.
The second is time.
Jimmy Burns, COO of In-Telecom, found that after implementing Datagate, his team saved “at a minimum, two full days of manual work each month.” That was time previously spent pulling, reconciling, and manually processing telecom billing data. For a team already stretched thin, two full days a month adds up fast.
The tax side is a genuinely different problem
Assume you’ve fixed the billing, the invoice is accurate, the usage is rated correctly, you still have the tax problem to solve, and it works differently from what most MSPs expect.
The instinct is to treat communications tax like sales tax: figure out what’s taxable, apply the right rate, collect it. That framework doesn’t hold.
Communications tax is based on where your customer receives the service, not where your business is registered. For US-based MSPs, this means that serving customers across multiple states can create active tax obligations in each of those states, regardless of where you’re located. Every jurisdiction has its own rates. Those rates change, sometimes multiple times per year, across federal, state, and local levels.
The service type matters too. Voice, data, UCaaS, and messaging are all taxed differently from each other. Getting the classification wrong produces the wrong tax calculation, even if every other piece of the invoice is correct.
Will Slappey at IT Voice described watching USAC rates shift repeatedly: “They handle all of the taxation fees and all of that… You got USAC that’s constantly changing the rates… cutting into our revenue.” Without a system tracking those changes automatically, you’re either collecting the wrong amount or manually checking rate tables before every billing run.
Getting it wrong isn’t just an accounting inconvenience. Under-collecting creates a liability that compounds as the billing period extends. Over-collecting creates disputes and damages customer trust. And if you’ve been filing incorrectly and get audited, the documentation burden is significant.
Bob Bascom at Charleston Telecom Services put it plainly: “It would be a major tax headache to try to figure out what all the taxes and fees were for those 20 locations… but that’s all taken care of by Datagate and SureTax.”
The MSPs who get this right tend to say the same thing once the system is in place. Eric Wakkuri, President of DS Tech: “Datagate’s integration with CCH SureTax ensures tax calculations and exemptions are automatic and accurate. Since DS Tech switched to Datagate partner CCH SureTax for tax calculations, customer queries are fewer.” Fewer customer queries on tax lines is a real operational improvement — every dispute that doesn’t happen is time your team doesn’t spend resolving it.
At WaveFly: “I trust CCH SureTax, I never have problems. I love the entire tax part of our solution, it’s made us more compliant.” At LineOne: “I don’t really have to worry about it. All the taxes are calculated on the backend.”
Why existing tools don’t close either gap
The instinct most MSPs have is to route telecom billing through tools they already use. The PSA manages customers and services. The accounting platform handles invoices. Why not handle telecom there too?
PSAs aren’t built for usage-based rating. They don’t have the logic to ingest CDR data from dozens of carrier formats, apply complex rate structures, handle bundles, and produce an itemised invoice with accurate usage by site. Accounting platforms don’t have communications tax engines. And carriers provide their data in their format, on their schedule, not formatted for your PSA.
You can make it work manually. Most MSPs who’ve tried describe the same experience: it works until it doesn’t, and then it doesn’t at the worst possible time.
What actually changes it
The MSPs who have gotten telecom billing and tax compliance right run a dedicated billing platform connected to a purpose-built tax engine. The billing platform handles CDR data, rating, invoicing, and PSA sync. The tax engine handles jurisdiction calculations, updates automatically as rates change, and returns the correct tax line items for every invoice, without manual input.
In the US and Canada, this typically means integrations with engines like CCH SureTax, Avalara, CereTax, or CSI. The UK, Australia, and New Zealand markets have different requirements, but the principle is the same: purpose-built tools that handle what general-purpose software wasn’t designed to do.
It’s also worth knowing that calculating taxes correctly and filing them are two separate problems. A tax engine ensures the right amount appears on the invoice. Filing and remitting those taxes to government authorities is a different step, handled by a tax filing partner rather than billing software. MSPs who only solve the calculation side and not the filing side have fixed half the problem.
When all the pieces are in place, the billing cycle shortens. Tax calculations run in the background. And the hours spent on manual reconciliation become something you can redirect elsewhere.
If you’re still running telecom billing through spreadsheets or chasing down carrier data each month, the problem isn’t that telecom is inherently unmanageable. It’s that the tools you’re using weren’t built for it.
To see how Datagate handles telecom billing for MSPs, get in touch today.
Disclaimer: The information provided in this blog is for general informational purposes only and should not be construed as legal or tax advice. For guidance on specific tax matters, please consult with a qualified tax professional.
