Telecom Billing Vendors: 12 Questions to Ask Before You Shortlist

Before shortlisting a telecom billing vendor, ask twelve questions covering service fit, rating accuracy on your real data, rate management, integrations, revenue controls, migration, pricing, data ownership, support, upgrades, security and references. Vendors that answer clearly and offer evidence are usually safe to move forward. Vague answers are the earliest warning sign you will get.

Key takeaways

• Most billing problems trace back to questions that were never asked during selection.

• The single most useful request is: "Rate a sample of our real usage records before we sign."

• Pricing, data ownership and exit terms deserve as much attention as features.

• Compare answers in writing. Verbal assurances rarely survive implementation.

Why vendor questions matter

A billing platform sits between your network and your revenue. A mistake in rating, a missed integration or a hidden cost can cost more than the licence fee over the life of the contract. Because the cost of switching later is high, the best time to find problems is before you sign. These twelve questions are designed to surface them.

The 12 questions

1. Which of our services and billing models do you support out of the box?

Why it matters: Workarounds multiply cost and error. List every service (voice, SIP trunks, hosted PBX, DIDs, SMS, mobile, broadband) and every charging model (per minute, per seat, prepaid, bundles). Listen for: A direct "yes, here is how" for each item, not "we can customise that."

2. Can you rate a sample of our real usage records before we sign?

Why it matters: Demonstrations use clean data. Your CDRs contain odd formats, special numbers and edge cases. Listen for: A willingness to process an anonymised sample and let you compare results with your own calculations.

3. How does the platform manage rates, rate sheets and rate changes?

Why it matters: If you buy and sell routes, rate management drives margin. Manual updates are where errors and delays appear. Listen for: Vendor and customer rate sheet processing, bulk updates, rate tables, least-cost routing support and automated customer notifications.

4. Which systems do you integrate with, and who maintains those integrations?

Why it matters: Switches, payment gateways, accounting packages, tax engines and CRM tools all need to connect. Custom integrations are the most common reason for late go-lives. Listen for: A published list of integrations the vendor builds and maintains, plus a clear process for requesting new ones.

5. How do you detect billing errors, revenue leakage and fraud?

Why it matters: Problems found by customers are expensive. Problems found by your team in real time are cheap. Listen for: Reporting and monitoring, exception alerts, usage anomaly detection and fraud controls built into the platform.

6. How will you migrate our data, and can we run parallel billing?

Why it matters: Migration is a risk event. Your finance team will check the first invoices line by line. Listen for: A named project owner, a defined data migration scope and at least one parallel billing cycle before cutover.

7. What does your pricing include, and what triggers extra cost?

Why it matters: Pricing models differ widely: per account, per CDR, per module, flat fee or revenue share. The cheapest quote can become the most expensive as you grow. Listen for: A written breakdown covering implementation, support, integrations, additional modules, volume growth and renewal increases.

8. Who owns our data, and what is the exit process?

Why it matters: Your customer, usage and invoice data is a core asset. You should be able to leave without losing it. Listen for: Clear data ownership terms, export formats and a defined exit process with timeframes.

9. What are your support hours, response commitments and escalation path?

Why it matters: Billing runs on deadlines. A failed invoice run at month end needs a fast response. Listen for: Defined service levels, named escalation contacts and support hours that match your business.

10. How do you handle upgrades without breaking our configuration?

Why it matters: Vendors that ship frequent updates improve fast, but only if upgrades are controlled and predictable. Listen for: A release cadence, upgrade notes, testing guidance and a policy for customisations.

11. What security and compliance controls do you provide?

Why it matters: Billing systems hold customer and financial data. Weak access control or poor audit trails create real exposure. Listen for: Role-based access, audit logging, data protection practices that match your regulatory environment and clear hosting arrangements.

12. Can we speak to three customers like us, and who will implement our project?

Why it matters: Reference customers with a similar service mix and size tell you what the brochure does not. The people implementing your project matter as much as the product. Listen for: References that match your profile and introductions to the actual implementation team.

What are the red flags?

• Reluctance to test your data. If a vendor will not rate your CDRs, ask why.

• "Everything is customisable." Often a sign that nothing works out of the box.

• No published integration list. You cannot verify what you cannot see.

• Vague pricing. If you cannot model cost over three years, the vendor has not made it clear.

• No reference customers like you. The vendor may be new to your segment.

• Pressure to sign quickly. A good vendor expects due diligence.

How should you score the answers?

Turn the twelve questions into a simple scorecard. Rate each answer from 1 (vague or missing) to 5 (clear, specific, evidenced). Weight the questions that matter most to your business, usually questions 2, 3, 4 and 6 for VoIP and wholesale providers. Compare totals across your shortlist, and treat any score of 1 as something to resolve before moving forward.

How does Neon Soft approach these questions?

We expect to be asked these, and you should ask them of every vendor, including us. A few of the answers are easy to check without a sales call. Neon Soft publishes its feature pages for rate management, including the rate generator, vendor rate management, customer rate management and rate sheet processing, and a broad list of integrations covering switches and PBXs, payment gateways, accounting packages and tax engines such as Avalara and CereTax. Use these to check questions 3 and 4 before any conversation.

For questions 2, 6 and 12, ask for a trial rating of your own records, a written migration plan with parallel running, and introductions to comparable customers. A vendor confident in its product will welcome all three.

Frequently asked questions

What should I ask a telecom billing vendor?

Ask about service and billing model fit, rating accuracy on your real data, rate management, integrations, fraud and revenue controls, migration, pricing, data ownership, support, upgrades, security and references.

How many telecom billing vendors should I shortlist?

Three is usually enough. More vendors slow the process without improving the outcome, and each added vendor needs a real-data test.

How do I test a telecom billing vendor?

Provide an anonymised sample of your CDRs and rate plans, ask the vendor to rate them, and compare the results to your own calculations. Check rounding, special numbers, time-of-day pricing and rate changes.

What are the biggest red flags when choosing a billing vendor?

Reluctance to test your data, no published integration list, unclear pricing, no comparable references and pressure to sign before you finish due diligence.

Should I ask for a pilot or proof of concept?

Yes, when the decision is large. A pilot with real data over one billing cycle reveals problems that demonstrations cannot.

Next step

Want to run these questions against Neon Soft? Book a demo and bring a sample of your usage records.