MSP Billing Discrepancy Types Explained: Calculated, Estimated, Unmapped, and Unaccounted

A billing discrepancy simply means there is a difference between what is being billed and what connected systems suggest should be reviewed.

But not every discrepancy has the same cause or confidence level. Some are based on hard values. Others depend on estimates, missing mappings, or usage that has not been captured by a rule.

A calculated discrepancy is based on values the system can directly derive from connected data and PSA records.

For example, if the PSA bills 20 units and the connected system clearly shows 24 billable units, the difference can be treated as a hard discrepancy because both sides of the comparison are known.

An estimated discrepancy relies on platform logic when an exact value is not available. This can still be useful, but it should be reviewed with a little more context.

Estimated discrepancies help teams notice possible billing issues, but they may need validation before making a billing change.

An unmapped discrepancy usually means integration-side usage exists, but there is no matching PSA-side billing item attached to it.

This can indicate a real underbilling issue, but it can also mean the service mapping setup is incomplete.

An unaccounted discrepancy usually means usage exists, but it was not captured by any current mapping rule.

This often points to a rule coverage gap. The usage is present, but the reconciliation setup does not yet know which billing model should apply to it.

A good review process starts with the discrepancies that have the highest revenue impact and the clearest supporting data.

From there, teams can work through estimated, unmapped, and unaccounted discrepancies to separate true billing issues from setup cleanup.