Service Mapping for MSP Billing Reconciliation

Service mapping connects a billed PSA item with the vendor product, licence, device category, or coverage quantity that supports it. Without that relationship, two correct quantities can still produce a misleading comparison.

The mapping gives the review a shared meaning: this recurring service is checked against this source category for this customer and billing model.

A PSA may use an internal service name while a distributor or vendor uses a SKU, package, policy, subscription, or device-class label. MSPs also rename services for packaging and customer-facing invoices.

Name similarity can help a reviewer find candidates, but the decision should consider the product, unit of measure, customer, agreement, and way the service is sold.

The simplest relationship connects one recurring PSA item with one source product or count. A billed endpoint service may correspond to active managed workstations, or a licence service may correspond to an active subscription quantity.

Even a one-to-one relationship needs period and lifecycle context. Recently added, cancelled, inactive, or pending items may legitimately differ at a billing cutoff.

MSPs often sell bundles that include several operational products or use several PSA service names for one source category. Those relationships cannot be understood from names alone.

A reviewer should confirm which source quantities support the bundle, whether all items are billable, and how customer-specific agreements change the interpretation.

Human confirmation is important when multiple source products appear plausible, a service is bundled, the billing unit differs, or the agreement contains an exception.

Suggestions can reduce search work, but they should not silently create a relationship that changes how quantities are interpreted.

A missing mapping can hide a billable quantity or make the source count appear unavailable. An incorrect mapping can attach valid usage to the wrong service and create a false difference.

A healthy review process keeps mapping questions visible, distinguishes them from quantity differences, and revisits relationships when products or service packaging change.

BillingReconcile keeps customer, service, source, and billed-quantity context together so a team can confirm the relationship before relying on a comparison.

Exact presets, rule fields, operators, conditions, and automation logic remain product implementation details; buyers only need to understand the relationship and review outcome.