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.
| Charge class | What it IS | What it ISN’T |
|---|---|---|
| Statutory tax | A levy set by federal, state, or local law and remitted to a government body | Not negotiable and not waivable by the carrier |
| Permitted carrier surcharge | A cost-recovery charge a tariff or contract allows for a defined service | Not a government tax, even when the name is built to look like one |
| Discretionary fee | A carrier pricing decision passed through to the customer | Not mandated and not automatically owed just because it prints on the bill |
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.
- 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.
- Tariff: Is the surcharge in the carrier’s filed tariff at the rate and basis billed?
- Contract: Does your signed agreement permit this charge, or does it cap or exclude it?
- 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.