Reference
Definitions for common terms used throughout BillingReconcile, including reconciliation workflows, mappings, discrepancy types, and integration-related language.
The process of comparing PSA-side billing records with integration-side usage or operational data to identify mismatches.
A difference between what is being billed and what connected systems indicate should be billed or reviewed.
A discrepancy based on hard values that BillingReconcile can directly derive from connected systems and PSA records.
A discrepancy that relies on platform logic when an exact count or value cannot be determined directly from the available data.
A discrepancy where integration-side usage exists but there is no matching PSA-side billing item attached to it.
A discrepancy where usage exists but was not captured by any current service mapping rule.
The process of linking integration-side client records to the correct PSA-side client so reconciliation is performed against the right organization.
The process of defining which PSA billing items should be compared against which integration-side usage sources.
A predefined mapping rule or configuration designed to match a common real-world billing pattern for an integration.
A billable unit such as a user, license, subscription, device, backup entity, or similar countable record depending on the integration.
A PSA-side service or billing item that BillingReconcile highlights for review because of a pricing or validation concern.
A usage-side record that has not been active for an extended period and may no longer reflect current billable usage.
The current operational state of a connector, typically shown as healthy, needing attention, or failed.
Professional Services Automation software used to manage agreements, additions, service items, tickets, billing relationships, and related MSP workflows.
Remote Monitoring and Management software used to track devices, endpoints, and operational service data.