Make commission and billing exceptions visible and explainable.
Reconcile carrier commission and billing statements against your own records — expected-versus-paid, missing activations, SPIFFs and residuals, duplicate credits, chargebacks, and vendor invoice variances.
Telecom agencies, resellers, carrier partners, MVNOs, ISPs, and MSPs whose finance or operations teams repeat manual billing or commission checks.
Starts with a Scoping & Data-Fit Assessment ($2,500–$5,000, credited to the build) on one statement source and one historical period.
| Record | Expected | Paid | Status |
|---|---|---|---|
| ACT-10482New line activation | $150.00 | $0.00 | Unpaid |
| SPF-2291Quarterly SPIFF | $75.00 | $50.00 | Short-paid |
| CRD-7733Service credit | $40.00 | $40.00 ×2 | Possible duplicate |
| RES-5510Monthly residual | $12.40 | $12.40 | Matched |
Every statement period, finance rebuilds the same math.
Carrier statements, activation records, invoices, and payments use different identifiers. Finance reconstructs expected amounts every period and spends time resolving the same ambiguities. PD Insights turns the approved matching and calculation rules into a repeatable expected-versus-paid workflow.
Make commission and billing exceptions — unpaid activations, short-paid SPIFFs, duplicate credits — visible, explainable, and ready for dispute or review.
Five working parts, delivered as internal software.
Data fit findings
Examine a representative historical period, identifiers, rule coverage, and record quality before confirming the build.
Normalized records
Map the agreed statement and business-record formats into a traceable reconciliation dataset.
Matching and exact calculations
Apply approved rates, effective dates, splits, adjustments, and matching rules in software.
Exception review queues
Identify expected-versus-actual differences, possible duplicates, unmatched records, and items needing finance judgment.
Evidence and operating handoff
Export source-to-result records, review decisions, period summaries, validation examples, and a repeatable operating procedure.
Bring one statement period and the rules used to check it.
I'll determine whether the data supports a reliable build.
Book a 30-minute fit call →Define it. Build it. Prove it.
Confirm data fit
Test identifiers, record completeness, effective dates, and the availability of approved financial rules.
Build the reconciliation
Normalize inputs, calculate expected values, and classify records for matching or review.
Validate a period
Reconcile against a finance-approved historical example and confirm the exception process before ongoing use.
Start narrow, then expand
Begin with a Scoping & Data-Fit Assessment ($2,500–$5,000, credited in full to the build if it is signed within 60 days of the assessment readout) using one statement source and one representative historical period. The first build then covers either commission reconciliation or billing review with the approved rules and formats.
Add statement sources, historical periods, or a second reconciliation type once the first process is accepted. Any recovery-based fee arrangement requires a separate agreement on verified amounts and measurement periods.
What moves the price
$10,000–$30,000One-time build · confirmed in a written proposalStatement formats, periods, transaction volume, identifier quality, calculation rules, and reconciliation destinations determine the fee. Multiple carriers, billing plus commissions, or direct accounting connections expand scope.
Compare every service and range →Inputs
Statements, invoices or activation records, approved agreements and rate schedules, effective dates, adjustment history, known exceptions, and a finance reviewer. Provide only the data required for the scoped reconciliation.
Acceptance
Every imported row is accounted for as matched, excluded with a reason, or queued for review. Calculations reproduce approved examples. Exceptions retain their source evidence and a visible resolution history.
An exception is a finding to investigate, not confirmed recoverable revenue. Finance approves adjustments and disputes. Payment execution, accounting entries, contract interpretation, and recovery services are outside the base build. This build runs under the same controls as every PD Insights system. See the controls →
Related work
POTS Tracker
Turns a sprawl of carrier bills and analog lines into one normalized inventory and a prioritized migration plan: the same normalize-then-match foundation.
See it on the case-studies page →Financial Analysis (local-model)
Parses statements and bills and computes deal-level economics on local models, so confidential financials stay inside the building.
See it on the case-studies page →Bring one statement period and the rules used to check it.
I'll determine whether the data supports a reliable build.