Features
What Morag does
Billing platforms usually stop at producing an invoice. The expensive part is everything around it — proving the invoice is right before it goes out.
Rentals, usage and one-off charges assembled from source data, on a schedule, with proration and mid-month changes handled properly.
Every supplier invoice matched against the services you actually bill — per CLI, per circuit, per SIM — not just totals that happen to agree.
Find the money quietly leaking in both directions: services still billed after supply ceased, and services supplied but never billed.
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.
Inside the product
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.
Supplier invoices matched against allocated cost. Variances are worked, not written off.
Leakage in both directions, quantified per month so you can decide what to fix first.
Built for telecom
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.
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.
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.
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.
Inclusive minutes, per-destination overrides, passthrough with markup. Rating applies them in the right order and shows which rule produced each line.
A supplier stops charging for a service and nothing tells the billing system. The charge keeps going out until someone notices. Morag notices.
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.
How it works
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.
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.
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.
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.
The run is verified, then issued.
Charges assembled, margin checked, invoices produced and delivered. The run is immutable — corrections become credit notes.
Bring a supplier invoice and a month of billing. Half an hour is usually enough to find something worth fixing.
