Billing that silently drifts from actual traffic costs you money in one direction and credibility in the other. Reconcile User Billing compares what was billed to users against the vendor message summaries for the same period, and shows the gap as a number and a percentage.
Step 1: Confirm the billing run actually completed
Open Message Billing Generation Info and search a date range. For each day it shows:
- User Start Time / User End Time and User Billed Status
- Vendor Start Time / Vendor End Time and Vendor Billed Status
An end time of NA means that run is still going or never finished. Reconciling a day whose billing run didn’t finish will always show a false discrepancy, so check this first. If a run shows an error, raise it with support rather than re-running blindly.
Step 2: Reconcile
- Open Reconcile User Billing.
- Enter From Date and To Date.
- Click Search.
Results, per date:
| Column | Meaning |
|---|---|
| User Total | Total counted on the user side |
| Billing Total | Total counted on the billing side |
| Diff Total / Diff Total % | The gap |
| User Success / Billing Success | Successful counts on each side |
| Diff Success / Diff Success % | The gap on successful messages |
A total summary row sits at the bottom, and Export downloads the data.
Step 3: Read the difference
- A steady small percentage every day usually points to a configuration difference (e.g. which error codes are set to charge the user) rather than a fault. Review your Global Error Codes’ Charge to User flags.
- One day at 100% normally means the billing run for that day didn’t complete. Go back to Billing Generation Info.
- A gap that starts on a specific date lines up with a change: a new connect, a changed rate, a new route, a modified error mapping. Check what you changed that day.
- Success counts differing while totals match points at DLR handling, not billing: statuses arriving late or mapping to the wrong global code.
Step 4: Trace it to transactions
Use Credit Usage to see the individual debits and credits behind a user’s balance. Filter by User Name, Transaction ID, date range, Method (Batch, Phonebook, Admin, Reseller), Product and Type (Credit/Debit). Each row shows amount, resulting balance, method, comments and timestamp, which is what you need when a client disputes a deduction.
Make it a routine
- Reconcile weekly, not at month end. A week-old discrepancy is traceable; a month-old one is an argument.
- Export and keep each reconciliation. It’s your evidence in client and vendor disputes.
- Reconcile immediately after adding a vendor, changing rates, or editing error-code charge flags.
Related articles
- How to Check Profit and Loss per Connect
- How to Set Up Global Error Codes
- How to Map Vendor Error Codes to Global Error Codes
- Credit or Wallet: Choosing the Right Billing Model
- Can I download any or all user credit summary from the reseller panel?