# Billing dispute resolution

> Billing dispute resolution: Valid dispute; credit due Checked: cross-checked. Produces credits, replies.

Source: https://www.sumarity.ai/library/billing-dispute-resolution/

Telecoms 

# Billing dispute resolution

Reads disputes, usage, tariffs. Produces credits, replies. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.

Cross-checkedClaims, disputes and exceptions
Start from this workflowMore for telecoms  

What it decides

## Narrow questions, each with a check behind it.

Valid dispute; credit due
Cross-checked: usage, tariff. A second source has to agree: a register, a contract, a list. When it does the judgement settles; when it doesn't, a person decides.

| Reads | Disputes, usage, tariffs 
| Produces | Credits, replies 
| Who signs | A person on your team, with every figure traced to its document and every call on record 
| Process | Claims, disputes and exceptions 
| Industry | Telecoms    

See it run

## Every line, decided where it's safest.

An example run. Each stage lights up as a line is decided there; pick a stage to see its lines.

ReadsDisputes, usage, tariffsCodeReads, matches, ties out and works out every figure.JudgementValid dispute; credit due. Settles only when it clears the cutoff and a second source agrees.A personGets whatever stays uncertain, with the evidence. Their ruling tunes the next run.ProducesCredits, replies  
Billing dispute resolution · example run Example run  

| Ref | Item | Value | Decided by  
| BD-101 | Charged for a cancelled add-onCancelled 02.09: credit | 9.90 | Code · credited 
| BD-102 | Roaming charge disputedUsage recorded abroad · 0.93 | 45.00 | Engine · cross-checked 
| BD-103 | Premium SMSSubscription confirmed · 0.88 | 15.00 | Engine · cross-checked 
| BD-104 | Bill doubledTwo lines merged? Unclear | 120.00 | To a person 
| BD-105 | Late feePaid on time | 10.00 | Code · waived  
|  

Settled 4 To a person 1 Settled wrong 0      Illustrative lines. Amber rows are the Judgement Engine's calls; each settles only above its cutoff and when its check agrees.    

What it could save

## Your volumes in. Your hours out.

In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data.

Items per run 
Runs per month 
Minutes per item by hand 
Cost per hour

Share of items that still need a person: 30%  

By hand today80 ha month 
With Sumarity24 ha month, for the items people decide 
Saved56 hCHF 53,760 a year    

Related

## Start from what's closest.

### Claims, disputes and exceptions in other work

Finance

### Customer deductions and short-pay disputes

Valid deduction (promotion, damage) or not

Proven by codeBanking

### Payment exceptions and investigations

Why a payment failed or is queried; the action

Proven by codeBanking

### Card disputes and chargebacks

Network reason code; evidence enough to fight

Cross-checked

### More for telecoms

### 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  

Questions

## What buyers ask

What happens when Sumarity isn't sure?

Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run.

How are its judgements checked?

A second source has to agree: a register, a contract, a list. When it does the judgement settles; when it doesn't, a person decides.

Can we change it to fit how we work?

Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it.

Does it read our files as they are?

Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it.

Where does our data go?

Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland.

How does it get better?

Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission.

## Start from this workflow. Run it on your data.

A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison.

Talk to usBack to the library