Skip to content

Billing & revenue assurance for telecom

Catch billing errors before your customers do.

Morag reconciles every supplier charge against every service you bill, then verifies the run before a single invoice leaves. No spreadsheets. No month-end guesswork.

Currently running in a live UK telecom environment. Built for providers and MSPs invoicing 50 to 5,000 customers a month.

workspace.moragbilling.com/billing/runs/2026-07
Example workspace using illustrative data
Live

Running in a UK telecom environment

Not a prototype — used for real monthly billing operations today.

1,000+

Invoices in a billing run

Rated, checked and issued within a single monthly cycle.

Automated

Supplier reconciliation

Supplier invoices matched to billed services, line by line.

Telecom

Purpose-built workflows

CDRs, rate cards, bundles, ports and credit notes — natively.

What Morag does

Four jobs, done properly.

Billing platforms usually stop at producing an invoice. The expensive part is everything around it — proving the invoice is right before it goes out.

  • Automated Billing

    Rentals, usage and one-off charges assembled from source data, on a schedule, with proration and mid-month changes handled properly.

    • Rate cards, bundles and markups applied per service
    • Part-month proration on connect and cease
    • Immutable runs — corrections issue a credit note, never a silent edit
  • Supplier Reconciliation

    Every supplier invoice matched against the services you actually bill — per CLI, per circuit, per SIM — not just totals that happen to agree.

    • Line-level matching across multiple supplier formats
    • Cost allocated to the component that incurred it
    • Variances surfaced with the lineage behind them
  • Revenue Protection

    Find the money quietly leaking in both directions: services still billed after supply ceased, and services supplied but never billed.

    • Ceased-supply detection against live supplier feeds
    • Unbilled service and below-cost pricing alerts
    • Margin by customer, product and supplier
  • Proof & Audit Trail

    Every figure on every invoice traces back to the record that produced it — the CDR, the rate card, the supplier line, the person who changed it.

    • Full lineage from invoice line to source record
    • Credit-note and correction workflows designed around UK invoicing requirements
    • Change history on rates, plans and charges

Before and after

The month-end you have, and the one you could have.

Most providers are not missing a billing system. They are missing the layer that checks the billing system agreed with reality.

Manual billing

Spreadsheets, supplier portals and institutional memory.

  • Supplier invoices checked on totals, if at all
  • Rate changes applied by hand, one spreadsheet at a time
  • Ceased services keep billing until a customer notices
  • Errors found after the invoice has been sent
  • Corrections made by editing the original invoice
  • Margin known at year end, roughly

With Morag

One system, one source of truth, checked before issue.

  • Every supplier line matched to the service that incurred it
  • Rate cards versioned and applied across every affected service
  • Supply stops, the charge is flagged before the next run
  • Run verified against source data before anything is issued
  • Immutable runs — a credit note and a new invoice, properly recorded
  • Margin per customer, product and supplier, every month

Inside the product

Every number, with its working shown.

Nothing in Morag is a black box. Open any figure and you can see the supplier line, the rate and the record it came from.

workspace.moragbilling.com/billing/reconciliation
Example workspace using illustrative data

Reconciliation

Supplier invoices matched against allocated cost. Variances are worked, not written off.

workspace.moragbilling.com/billing/revenue-protection
Example workspace using illustrative data

Revenue protection

Leakage in both directions, quantified per month so you can decide what to fix first.

Built for telecom

Generic billing software does not know what a CLI is.

Morag was built inside a working telecom reseller, against real supplier files and real month-ends. The awkward parts below are not roadmap items — they are the reason the product exists.

  • 01Usage does not line up with rentals

    Rentals bill in advance, call usage bills in arrears, and the supplier's file labels lag a month behind. Morag models the offset instead of assuming a single period.

  • 02Suppliers bill on a different key to you

    You bill a customer by phone number; the supplier invoices by circuit reference, SIM or account. Matching is a mapping problem, and Morag treats it as one.

  • 03Cost sits on the wrong component

    A broadband line and a WLR line on the same CLI, a SIM bundle priced at the account level. Cost gets allocated to the component that incurred it, not the first row that matched.

  • 04Bundles, markups and special rates interact

    Inclusive minutes, per-destination overrides, passthrough with markup. Rating applies them in the right order and shows which rule produced each line.

  • 05Services cease quietly

    A supplier stops charging for a service and nothing tells the billing system. The charge keeps going out until someone notices. Morag notices.

  • 06Corrections have to be defensible

    Rebilling by editing an invoice does not survive an audit. Runs are immutable: a correction is a credit note and a fresh invoice, with the reason attached.

Where Morag came from

Built inside telecom operations, not around assumptions.

Morag was created after years of watching billing teams reconcile supplier files, customer services, special rates and legacy systems by hand — chasing a variance across three spreadsheets and a supplier portal because no system could show where a charge had come from.

It is shaped by the problems that appear in a real billing month: a supplier that invoices on a different key to the one you bill on, a service that ceased without anyone telling the billing system, a bundle that quietly over-recovers. Not by a generic subscription-billing model with telecom bolted on.

It runs today in a live UK telecom environment, which is also where every change gets tested first.

How it works

Four steps, every month, the same way.

The value is in the order: nothing is invoiced until it has been validated against source data and reconciled against what the supplier actually charged.

  1. 1

    Import

    Supplier files and customer data land in one place.

    CDR feeds, supplier invoices, rate cards and service records — pulled on a schedule or dropped in. Each import keeps its own audit record.

  2. 2

    Validate

    Every record is checked before it counts.

    Numbers normalised, services attributed to the right account, duplicates and gaps flagged. Nothing rates on data that has not been checked.

  3. 3

    Reconcile

    Supplier cost is matched to billed service.

    Line by line, per CLI, circuit or SIM. Variances, unbilled supply and ceased services surface with the evidence behind them.

  4. 4

    Invoice

    The run is verified, then issued.

    Charges assembled, margin checked, invoices produced and delivered. The run is immutable — corrections become credit notes.

Free telecom billing health check

Find out what your billing is missing, before you commit to anything.

Tell us a little about your billing environment. We will contact you to arrange a secure transfer of the relevant supplier and billing files, then compare them against each other and send you a written summary of what we find.

What we look for

  • Missing billing — services supplied and paid for, but never invoiced on
  • Pricing discrepancies between your rate card and what the supplier charged
  • Duplicate charges across accounts, components or supplier feeds
  • Supplier and customer mismatches, where the two sides do not line up
  • Service cessations you are still being billed for, or still billing for
  • Margin leakage — services priced at or below what they cost you

How your data is handled

The form below collects enquiry details only — please do not attach or email invoices or billing extracts. We arrange a secure transfer once we have replied. Files are used only for the analysis, are not shared outside our team, and are deleted when it is finished.

Request your health check

A few details about your billing setup. We reply within one working day.

We use your details to reply to you. Privacy policy.

Free, by email

25 Billing Checks Every Telecom Provider Should Perform Every Month

The checks we run before a billing run is allowed out — grouped by stage, with the failure each one is designed to catch. Use it as a manual checklist or as a specification for automating your own.

Not ready to share data? Start here instead.

Early access

How you actually get Morag.

Morag is currently onboarding a limited number of telecom providers through an early-access programme. It is not a self-service product you can sign up for today, and there is no account to create — onboarding starts with a conversation.

  • We migrate your supplier feeds and rate cards with you, not for you to figure out
  • Your first reconciliation runs alongside your existing process, not instead of it
  • A small number of providers at a time, so each migration gets proper attention

Most providers start with the free billing health check above — it costs you nothing and tells us both whether Morag is worth your time.

Enquire about early access

Tell us where you are and we will talk through whether the fit is right.

Roughly how many you invoice each month.

We use your details to reply to you. Privacy policy.

One email a month, on the unglamorous part of telecom.

Revenue Recovery: billing controls, reconciliation lessons, revenue-leakage patterns and practical operational improvements — plus the occasional Morag update. Approximately once a month.

Reply “unsubscribe” to any issue. We never sell or share your address.

See it against your own numbers.

Start with a free billing health check: tell us about your billing environment, and we will arrange a secure transfer of the files we need to look at.