Service Mapping

SECURITY  Manager

NAVIGATION   > Contracts > Search > Contracts > open a contract > Menu > Service Mapping

The Service Mapping page only appears on a recurring service contract if

Once these prerequisites are met, usage data for mapped KaseyaOne modules and organizations is transferred to Autotask for integrated customer billing. The services on a recurring service contract are the billing vehicles for the unit counts synced from these modules.

Theoretically, you could use any existing service and map it to one or more module billing types. However, this can lead to a lot of confusion down the line when a customer has questions about the invoice. We recommend the following best practices:

BEFORE YOU BEGIN  Before you can map billing types to Autotask services, you must add the services to the contract. Refer to Adding services and service bundles.

On the Service Mapping page, you assign a service to each billing type of each KaseyaOne module that is enabled for Integrated Customer Billing and select how changes to the unit counts are billed.

  • The Service Mapping page has a separate section for each KaseyaOne module mapped for the contract organization. All modules you enable on the Map Autotask Organizations to Module Organizations page appear here. Refer to Mapping Autotask organizations to module organizations.
  • Each section features a table that lists all the ways the KaseyaOne module counts billable items.

Use the table to map the billing types and configure the settings:

Column Description

[Module Name] Billing Type

Each KaseyaOne module has a number of different ways to count billable items. MSPs may want to charge their customers per device, per user, per mailbox, per agent, etc. Each option for the specific module is transferred to Autotask and can separately be assigned to an Autotask billing service. This allows for a very granular billing setup.

Autotask Service

Click the dropdown control to select an Autotask Service for each billing type.

NOTE  Service Bundles are excluded.

Adjustment Frequency

Autotask will receive daily updates of the number of billing items for each billing type. You can, however, set the effective billing date for each unit change. Select one of the following two options:

  • Daily (full period billing): Your customer will be charged for the full billing period for items added or subtracted during the billing period. This is the default option.

EXAMPLE  On March 17, the unit count increases by 5. Starting on March 1, the customer will be charged for 5 additional units.

  • Daily (prorated billing): Billing for added and subtracted items will be prorated.

EXAMPLE  On March 17, the unit count increases by 5. Starting on the 17th, the customer will be charged for 5 additional units.

Ignore

If you select Ignore, the row mapping will be cleared, and the billing type will not be included in the count of Unmapped Billing Types in the section title. Since no billable service will be associated with the billing type, you will not be billing for it in Autotask.

Although we do not recommend this practice, it is possible to map two separate billing types to one and the same Autotask service. You may want to do that if Per User and Per Device have the same price. As a result, each increase and decrease of the Per User and Per Device unit counts will impact the one service.

EXAMPLE  Your VulScan - Per User/Device Autotask service has a unit count of 30. The count of the billing type of Per Scanned User increases by five on March 13. The VulScan - Per User/Device unit count rises to 35. On March 15, the Per Device count increases by two. The VulScan - Per User/Device count rises to 37. Looking at the service unit count on the Services page and on the invoice, it is not obvious how many units are Per Scanned User and how many Per Device. If you increased Per Scanned User by two and decreased Per Device by two, it would appear as though the service unit count didn't change. This may be hard to follow for the customer.