Skip to content
A hazy skyline at sunset with a plane overhead
Carriers

Every invoice, in any form.

The catalogue indexes 2,231 operators across 228 countries and territories, so an invoice matches a carrier and a carrier matches its parent group.

Request a pilot
Golden fibre-optic strands of light
Catalogue
2,231 operators across 228 countries and territories, built deterministically from open reference data and reproducible from the same query.
What it is for
Matching an invoice or a monitored circuit to the right carrier, and resolving regional operators to the enterprise brand and parent group that actually negotiates.
What it covers
Identification and reference. Every operator sits in the index on equal terms, because we earn zero carrier commission and the catalogue ranks nobody.
Bill paths
CSV and XLSX through saved mappings, built. PDF through AI extraction into a human review queue, built; its accuracy is measured per carrier in a pilot. Structured e-invoicing XML and carrier portals are planned. Each path below carries its own status label.
Connections
Each operating company holds its own carrier connections, with a connection test and scheduled bill polling. The framework is built, and each carrier's own connector carries its status.
Carrier APIs
Research only. The interface is defined so that a carrier API path is an addition rather than a rewrite, and it is scoped against the operators who publish an enterprise billing API today.
Rooftop chimneys and antennas with a tower beyond

Bill paths

Every path below writes into the same tables, so each one can be added on its own schedule.

  • PDF extraction — Pages go to an AI extraction step, and every field lands with a confidence and a pointer back to its place on the page. Anything below the carrier's floor opens a review item. Its accuracy is measured per carrier in a pilot.Built
  • CSV and XLSX mapping — Mappings are keyed to the fingerprint of the header row plus the carrier and the entity, and hold their own transforms for digits, separators, dates and currency. A saved mapping is why a carrier's second month costs less than its first.Built
  • Structured e-invoicing XML — Designed as a peer of the PDF parser rather than a later port, because two of the jurisdictions we care about already mandate or will mandate it.Planned
  • Carrier portals — Portals keep bills for a limited window, often months and varying by operator, which is why we ingest early and keep the raw bytes indefinitely. A portal export lands through the same mapping path a spreadsheet does.Planned
  • Carrier billing APIs — Research only. The interface is defined so that a carrier API path is an addition rather than a rewrite, and the survey of who publishes one is the work in hand.Research only

Regional depth, deliberately first

These invoice shapes drive the parser work, so they are the ones we build for first. The built bill paths above read their files. Here Planned means that carrier's invoice format is not yet measured on real invoices; the label moves when a pilot measures it. No carrier named here is a partner.

  • e& and du — United Arab Emirates.Planned
  • stc and Mobily — Saudi Arabia, where structured e-invoicing is already mandatory.Planned
  • Zain and Ooredoo — Multi-country groups across the Gulf and beyond, each with per-market invoice differences.Planned
  • Batelco and Omantel — Bahrain and Oman, both three-decimal currencies.Planned
  • Türk Telekom — Türkiye, where a special communications levy sits outside the VAT base and has to be computed rather than described.Planned
  • Safaricom — Kenya.Planned
A skyline at blue hour

Multinational groups in the catalogue

Where a group bills centrally, one enterprise brand can resolve to many national operators. The catalogue holds that relationship so spend can be totalled across it.

  • Vodafone Business — Global reach, central billing.Planned
  • Deutsche Telekom, T-Business — Global reach, central billing.Planned
  • Orange Business — Europe and Africa.Planned
  • Telefónica Business — Iberia and Latin America.Planned
  • BT Business — United Kingdom.Planned
  • AT&T Business and Verizon Business — North America.Planned
Catalogue coverage by region
RegionCountriesOperators
Europe51487
Middle East and Africa67559
Asia-Pacific55682
Americas55503
Total2282,231

Why files work best

Carrier billing APIs are the integration everybody assumes exists. For a group of this shape, a handful of operators publish one, and each of those gates it behind an account relationship that needs your permission and your credentials.

So the first bill path is file-based, and the parser is the moat and the treadmill. Our estimate, with the working in the article on invoice formats: 40–80 invoice formats across 15 countries for a group of this shape, and carriers revise them. A new format starts from three invoices, and the status label on each path says where it stands.

Matched on evidence

Carrier names on invoices are inconsistent, transliterated, abbreviated and bilingual. Matching runs through normalisation and a synonym list rather than string equality, and a low-confidence match opens a review item rather than quietly creating a new carrier.

The catalogue is current-state: merged and dissolved operators are removed rather than kept as history, and known misclassifications are corrected explicitly. It is a reference index, and your own carriers are whichever of them your invoices name.

People crossing a sunlit city street

Send three invoices. A person replies with what they show.

Request a pilot