November 5, 2026

3CX Billing Has Almost No Coverage: ictVoIP Billing Is the Edge Provider Now

Last Updated: November 5, 2026 | Reading Time: 4 minutes

3CX is everywhere (hosted PBX, office PBX, MSP tenants, ITSP trunks), yet if you search for "3CX billing" what you mostly find is manual workarounds, generic tools that were never designed for it, and a handful of half-finished integrations. Meanwhile the platform's own billing story remains thin for anyone reselling VoIP through it.

That gap is exactly what ictVoIP Billing now fills.


What ictVoIP Billing Does for 3CX

We built the 3CX provider against the platform's real-world deployments, verified end to end on a live 3CX V20 system:

  • CDR collection: normalized call detail records pulled straight from the 3CX database through our on-host collector agent: caller and destination numbers, CNAM lookup names, direction (inbound, outbound, internal), answer/hangup times, billable seconds, and dispositions (ANSWERED, NO ANSWER, BUSY, FAILED)
  • Tenant and extension scoping: multi-tenant 3CX systems (Multi-Tenant/Multi-Company modes) map cleanly to per-tenant billing; each extension can be bound to its own client service so call records only appear where they belong
  • Tariff rating: outbound legs rate against destination tariffs the same way they do on our FusionPBX and FS PBX integrations: national, international, custom rates, all auditable per call
  • Autobill invoicing: scheduled rating runs collect a billing period's calls, rate them, and drop them straight onto the client's next invoice, with no manual exports or spreadsheet gymnastics
  • Provisions you can sell: a provider template installs into 3CX (trunk, DID, outbound route setup) so the billing platform can deliver the working phone side of the service, not just count the minutes

Works Across All 3CX Editions

Billing data collection is edition-agnostic: our collector reads the system's own PostgreSQL call records directly and serves them over a hardened, IP-restricted API, so CDR billing works across every 3CX edition, including 3CX Free and the hosted tiers that ITSPs and small providers run at scale. XAPI remains available for shops that want it for other integrations.

Where It's Available

  • FOSSBilling, today. The open-source edition is live: server registration, provider configuration, tenant/extension import, client-area CDR views, and autobill all work now. Try it on our live demo. The 3CX service shows a realistic call history in the client area.
  • WHMCS, available now. The same 3CX provider support runs on WHMCS: server registration, tenant/extension scoping, CDR collection and autobill.

Why This Matters for 3CX Resellers

If you're an MSP or ITSP running clients on 3CX, you already know the pain: 3CX bills per-extension licensing but says nothing about the minutes your clients burn on trunks. Your clients either get a raw CSV or, more likely, nothing at all.

ictVoIP Billing gives you the missing half: the trunk-side billing engine, inside a billing platform your clients already know.


Try It

The FOSSBilling demo includes a 3CX service with sample call history. Sign in with the demo credentials on the landing page and open the service's CDR view. For production deployments on either edition, contact us. We're onboarding early 3CX billing customers now.


← Back to Blog