From call to invoice · five steps

The team that stays through the bill run.

Every call your network carries becomes a record that has to reach an invoice by morning. Promon migrates and runs the systems on that journey, and we stay on shift while it happens.

SCROLLFollow the night engineer. Every step on the way is something we build, migrate or run.

Step 1 of 5 · Mediation

Sent twice. Counted once.

Network elements send records in bulk, in different formats, and sometimes twice. Mediation collects and validates them, drops duplicates and turns every format into one. Nothing lost, nothing counted twice.

Received0Duplicates dropped0Passed to rating0

Where Promon worksMediation and data flows from the switch to rating, built and run by us.

ASN.1
CSV
1F3A
XML
ASN.1
1F3ADUPLICATE
DUPLICATES
MEDIATION
CollectValidateDeduplicateNormalise
REC
REC
REC
REC
1F3A
Illustrative example

Step 2 of 5 · Catalog & rating

One wrong price. Thousands of wrong bills.

Rating prices every record against the product catalog. If the catalog is wrong, every invoice built from it is wrong too. So the fix belongs in the catalog, once, before the bill run.

18,400 invoices would carry the wrong add-on price.

Where Promon worksProduct catalog (TMF620), CRM and order management, built so the price and the contract agree.

Essentials

£12/mo
  • Data20 GB
  • VoiceIncluded
Catalog error

Unlimited 5G

£20/mo
  • VoiceIncluded
  • Roaming Europe£50.00£5.00

Unlimited Max

£30/mo
  • VoiceIncluded
  • Roaming EuropeIncluded
Rating · CDR 1F3A
Voice · 4m 12s · Leeds252 s
Tariff · Unlimited 5Gincluded
Rated amount£0.00
Illustrative example

Step 3 of 5 · Billing migration

From the old billing system to the new, plank by plank.

During a migration both systems bill the same accounts every night. Each difference is traced to a root cause and fixed in the target, until the bills agree to the penny. Then we cut over, with a rollback the team has rehearsed.

Parallel run · night 01 of 14

Where Promon worksCerillion and Comverse migrations: coexistence, parallel runs, reconciliation and cutover.

Differences4,812
READ-ONLYLegacy billing
Comverse
acct 40021-77
total £43.00
LIVETarget billing
Cerillion
acct 40021-77
total £42.61
Root causes fixedRoundingTax codesProrationDiscount orderCurrencyCycle datesBundlesCredits
ROLLBACK PATH · REHEARSED
Illustrative example

Step 4 of 5 · 24/7 operations

02:31 in Europe. 07:01 in Chennai.

The new platform is live and Europe is asleep. In Chennai the morning shift is already at their desks. Monitoring raises a ticket and an engineer owns it: diagnose, fix, restart, write it up.

  1. Detected · bill-run job 7 stalled
  2. Assigned · Chennai morning shift
  3. Diagnosed · archive volume at 91%
  4. Mitigated · job 7 restarted from checkpoint
  5. Resolved · bill run back on schedule

Where Promon works24/7 managed operations, follow-the-sun from Chennai.

CET · Europe01:5806:28IST · CHENNAI
Platform statustarget billing · live
MediationOperational
RatingOperational
Invoice generationOperational
Bill-run jobsOperational
db-node-2 · archive volume91% used
Illustrative example

Step 5 of 5 · Bill run

Home by morning.

The record reaches the bill run and becomes one line on an invoice: rated, billed and reconciled. Your team starts the day with a summary, not a crisis.

  • Rated usage equals billed usage
  • Records lost between mediation and invoice: 0
  • Legacy shadow total matches: £43.00
  • Bill cycle closed on schedule
From Promon Ops
Bill run 10/2026 · closed on schedule
One incident overnight, resolved at 02:58. Nothing is waiting for your team.
INVOICEAcct 40021-77 · 10/2026
Unlimited 5G£20.00
Roaming Europe£5.00
Device 12/24£18.00
Voice 4m12s£0.00
Total£0.00
BILL RUN · CYCLE 10/2026
Illustrative example

Five steps, five things we do

Migrate it. Run it. Keep the catalog and the invoice on one stack.

  • Step 1

    Mediation and integration

    Data flows from the switch to rating, ERP and payments. Every record accounted for.

    Replay step 1
  • Step 2

    Catalog and rating

    TMF-aligned catalog, CRM and orders, so the price, the contract and the rated amount agree.

    Replay step 2
  • Step 3

    Billing migration

    Cerillion and Comverse cutovers with parallel runs and a rehearsed rollback.

    Replay step 3
  • Step 4

    24/7 operations

    Monitoring that becomes tickets, owners on every job, follow-the-sun cover after go-live.

    Replay step 4
  • Step 5

    Bill run and reconciliation

    Invoices that match what was rated and sold, cycle after cycle.

    Replay step 5
ISAE 3402 Type IISOC 2 Type IICerillion · ComverseTM Forum open APIsChennai · since 2014

Start a programme

Your bill run deserves a crew that stays.

Tell us the stack and the date you cannot miss. A delivery lead replies during 08:00–12:00 Central European time, and the people who scope the work stay for the first bill run.

Illustrative scenario: records, prices, counts and incidents on this page are examples.