Is Webroot available in BillingReconcile?

Yes. Webroot is listed as an available integration. Exact record coverage depends on the vendor plan, account configuration, permissions, and the billing model being reviewed.

Does BillingReconcile change Webroot or PSA records automatically?

No. The current reconciliation workflow is read-oriented. It presents source and billing context for human review; your team controls any resulting change.

Does every quantity difference require a billing change?

No. Timing, account mapping, service mapping, lifecycle state, agreement terms, and source freshness can all explain a difference.

Available integration guide

Webroot Billing Reconciliation for MSPs

BillingReconcile supports Webroot as a read-oriented source for billing review. MSP teams can review site, protected-endpoint, product, licence, and coverage counts beside PSA billing context before deciding whether a difference needs action.

Book a Demo View Integrations

What Webroot contributes to billing review

Webroot can provide endpoint-security coverage context for recurring billing review. The useful comparison depends on the services your MSP sells and which supported records are available to the connected account.

BillingReconcile keeps source evidence and billed quantities together for review. It does not treat every difference as proof that an invoice is wrong.

Data categories that may be reviewed

Sites and customer context

Protected endpoints

Product or licence context

Coverage-related counts

Common differences worth investigating

A protected endpoint is not represented in the billed security quantity

A removed endpoint remains represented in recurring billing

A product or licence category is associated with the wrong billed service

A Webroot site does not clearly correspond to the PSA client

A review-first sequence

1
Connect the supported PSA and operational source with appropriate authorization.
2
Confirm that the customer account and billed service correspond across systems.
3
Compare the billed quantity against the relevant source count.
4
Investigate timing, mapping, lifecycle, and agreement context.
5
Have an authorized person decide whether billing, mapping, or source data should change.

Human review and read-only boundaries

BillingReconcile's current reconciliation workflow is read-oriented. It organizes comparisons and supporting evidence without silently changing invoices or third-party records.

A person who understands the agreement and billing policy remains responsible for the final decision.

Connector scope

Available Webroot records vary by vendor plan, account configuration, permissions, and API changes. BillingReconcile confirms the data needed for the agreed billing model during onboarding. Product-specific setup instructions remain in the signed-in Help Center.