Skip to main content
Branch preview for the September 18 release. These controls are not yet published. Screenshots show MSPortal Demo running the release branch.
Audience: MSP staff managing Standards or financial-reporting settings. The catalog supports synchronized ConnectWise, Autotask, and Halo billing. Billing evidence can mark an unanswered standard as deployed. It establishes that a matching service or agreement type was billed; it does not verify an agent installation or protection on every device.

​
Before you start

  • Create the standard and any deployment options in Standards settings.
  • Ensure your PSA billing has synchronized. The default evaluation uses the last three completed calendar months; current-month-only charges are not included.
  • Review device-platform and company-field applicability. Automatic billing answers must still respect those rules.
  • Viewing the catalog requires financial-reporting settings read or Standards settings read access. Revenue classification edits require financial-reporting settings management. Mapping edits in this financial grid require financial-reporting settings management; edits in a standard’s own editor require Standards settings management. Re-checking billing requires Standards settings management or Planner write access. Write operations require active billing.
1

Open SKU Mapping

Open Settings > MSP Tools > Financial Reporting and select SKU Mapping. Review the SKU label, provider, revenue category, and Standards links. Use Columns to show Clients billed and Monthly revenue when needed; existing saved column preferences are retained. This is a shared settings catalog for your MSP, rather than a company-filtered matrix.
2

Choose the revenue category and Standards

Set the row’s revenue category when needed, then select the standards it proves. These choices save from the row; wait for confirmation before navigating away. Revenue classification and Standards links are independent.
3

Re-check billing

Select Re-check billing and wait for the results. This updates automatic Standards answers in your permitted company scope, including other configured mappings. It is not just a preview of the selected row.
4

Review the resulting deployment

Open MSP Tools > Standards and select a matching company. Review the automatic-answer indicator and hover explanation naming the billing evidence.
SKU Mapping

Branch preview: Default columns prioritize editable revenue and Standards controls.

Big Design automatically receives Managed protection from matching billed products.

Matching billing answers Managed Endpoint Protection for Big Design.

The supported keys are services and contract types. A service identifies the billed offering; a contract type can represent a bundled agreement.

​
Require alternatives or multiple services

Expand a standard’s editor in Settings > MSP Tools > Standards to configure its SKU groups and optional deployment choices.
  • Within one group, any matching SKU satisfies that group: A or B.
  • With multiple groups, every group needs a match: (A or B) and (C or D).
  • A matching group can imply a deployment option. When several matched options apply, the highest tier wins.
Two required billing groups configured with Basic protection and Managed protection options.

Alternatives within a group; every required group must match.

The flat SKU Mapping picker adds new Standards links to the default alternatives group. Keeping a standard selected while changing other links preserves its existing group and deployment-option configuration.

​
Keep manual decisions authoritative

Automatic evaluation can answer an unanswered Not Started cell or revise an answer it previously generated. If matching evidence disappears, its automatic answer returns to Not Started. A recorded manual decision such as Declined, In Progress, or Deployed is preserved on later evaluations. Manually editing an automatic answer transfers that answer to manual control. Leaving a cell Not Started makes it eligible for automation; it is not an opt-out setting.
Blue Light retains its manually Declined answer after billing is evaluated again.

A manual Declined decision remains authoritative.

An onboarding-controlled unanswered cell remains owned by its onboarding task. Review the task link rather than expecting billing to take over that cell.

​
Troubleshooting

Deployment tiers and options

Set up the choices that billing can imply.

Update a deployment

Record a manual decision for a company.