# Telecoms

> Sumarity for telecoms: standard workflows with every judgement checked.

Source: https://www.sumarity.ai/industries/telecoms/

Telecoms 

# Telecoms: the doubts, not the drudgery.

Settlements with partners, usage against billing, and customer disputes: large volumes of records that should agree and sometimes don't.

Talk to usFilter the library  

What teams tell us

## Where the time goes

Partner invoices that don't match our traffic

Usage that never reaches a bill

Billing disputes decided case by case

Workflows

## Standard workflows for telecoms

3 workflows · Proven by code: 2 · Cross-checked: 1

### Interconnect and roaming settlement reconciliation

Partner invoice vs our traffic records

Proven by code

### Revenue assurance: usage vs billed

Why usage wasn't billed

Proven by code

### Billing dispute resolution

Valid dispute; credit due

Cross-checked  

Questions

## What buyers ask

Which process should we start with?

The one with the most items your team checks by hand and a clear way to tell right from wrong: usually a reconciliation or a matching process. Its judgements are proven by code, so most settle without a person.

Do you connect to our systems?

Files in any layout (spreadsheets, CSV, PDF, bank formats), e-mail inboxes and folders, and an API for software. Connectors for particular systems are built as customers need them.

How long does a pilot take?

A few weeks alongside your own process, on your own data, at our cost. It ends in a line-by-line comparison: what it settled, what it sent to people, what it caught, and the time it took.

## Bring one telecoms process. Run it alongside yours.

We design it with your expert, run it in parallel, and show you the comparison.

Talk to us