Setting up your services

SECURITY  Security level with Admin permission to configure Products, Services, & Inventory. Refer to Admin security settings.

NAVIGATION   > Admin > Features & Settings > Products, Services, & Inventory > Services

NAVIGATION   > Admin > Features & Settings > Finance, Accounting & Invoicing > Price List

1. To add a new service, click New on the Services page or click New > Service on the Price List page.
   To edit an existing service, select Edit Service from the context menu on the Services page, or click the Edit icon on the Price List page.
   

2. Populate or modify the following fields:

Field Name	Description
General
Name*	This field should be descriptive enough to ensure the correct service is being added to the contract.
Active	Selected by default. Clear this check box to make the service inactive. Inactive services cannot be added to contracts or service bundles, but existing contracts or service bundles are not impacted.
Description	The Description field appears on many Autotask entities. On entities like ticket, task, note, and to-do, the Description field is a core part of the data record. Wherever it is available, it tracks essential information about the record. This field is often prefaced with the entity name. For example, Quote Description. Enter a detailed description of the entity instance, the issue with which the customer needs help, or the service that they requested.
Invoice Description	Enter the description that will appear on invoices. This description can be modified at the contract level to add more information (domain names, etc.).
Service Level Agreement	The point of an SLA is standardization. A service level is a performance standard that defines the time frame in which an issue will be resolved, based on its severity and impact. A service level agreement is a minimum set of service levels that your company defines to meet the service needs of one or more customers. For example, you promise your customers that critical tickets that impact multiple contacts will be resolved within 8 business hours 90% of the time. For more information on SLAs, refer to Introduction to service level management. You should rarely have to manually select an SLA. If they are correctly set up, SLAs should be applied automatically. If an entity is created from or associated with multiple entities that can default in a service level agreement, the more specific SLA is prioritized over a more general one: Manual selection (or applying a form template, which counts as manual selection) SLA on the device SLA on the recurring contract service or service bundle SLA on the contract This applies also to tickets created in the Client Portal. For more on this complex subject, refer to Applying service level agreements.
Vendor Name	A vendor is an organization Your Autotask instance may be configured to use one of the following terms instead: Account, Business Unit, Client Company, Customer, Site. whose primary business relationship with your company is to provide goods and services. Products can be associated with multiple vendors, one of which is designated as the default vendor. All other entities that reference a product vendor are associated with one specific vendor (the one from which the item was actually purchased). The field will default to the Product Default Vendor, but additional Product Vendors (associated with the product) and Other Vendors (not associated with the product) are available from the dropdown menu. Services can only have one vendor. If you change the vendor of a service, contracts that include the service will reference the new vendor as of the next billing period. NOTE  When you associate a service with a vendor and provide a Unit Cost, you can track profitability by vendor and report on vendor payments.
Manufacturer/Service Provider	This is an optional field that you can use to track a manufacturer or service provider, which may be different than the vendor who supplies the service.
Manufacturer/Service Provider Product Number	This is an optional field that you can use to track a manufacturer or service provider product number.
Catalog Number/Part Number	This is an optional field that you can use to track the catalog or part number.
Service SKU	This is an optional field that you can use to track the service SKU.
Internal Service ID	This is an optional field that you can use to track an internal service ID.
External Service ID	This is an optional field that you can use to track an external service ID.
Service Link (URL)	This is an optional field that you can use to provide a link to a website for the service. The text will appear as a hyperlink.
Billing
Unit Cost	This field allows you to capture costs of providing a service, such as licensing fees. Unit cost can be edited on the Recurring Contract > Services page. You can enter up to 4 decimals. NOTE  Providing the Unit Cost allows you to track recurring service contract profitability. When you provide a Vendor Name as well, you can track Vendor payments.
Markup %	This field appears on entities that are part of the billing workflow. It is hidden from users who do not have permission to view internal cost data. It indicates the difference between Unit Cost and Unit Price as a percentage. When you select the item name, the Markup % field is populated but it can be edited.
Unit Price*	This is the default price for the service per billing period and unit. You can enter up to 4 decimals, but note that the Extended Price field on quotes and invoices will be rounded to 2 decimals. If Multi-currency is enabled, the price is always displayed in your internal currency. For information on setting prices in customer currencies, refer to Managing your price list.
Period Type*	The choices are Monthly, Quarterly, Semi-Annual, and Yearly. When the service/bundle is assigned to a contract, the period type will be used in conjunction with the contract period type to determine the time interval at which the service will be billed. NOTE  Once a service/bundle is saved, the Period Type can no longer be edited. • If the service/bundle has a longer billing period type than the contract, the service/bundle will be billed in its entirety. If the service/bundle period type is quarterly and the contract period type is monthly, the service/bundle will be billed for the entire quarter on the next contract billing date. • If the contract billing period is longer, the service/bundle will be billed for the number of times that would have occurred since the last billing. For example, if the service/bundle period type is quarterly and the contract period type is semi-annual, service will be billed twice on the next contract billing date. The table below illustrates the combinations of monthly and quarterly periods for services/bundles and contracts. Billing Period Price per Period Contract Billing Period Due on Jul. 1 Due on Aug. 1 Due on Sep. 1 Due on Oct. 1 Monthly $10 Monthly $10 $10 $10 $10 Quarterly $10 Monthly $10 - - $10 Monthly $10 Quarterly $30 - - $30 Quarterly $10 Quarterly $10 - - $10 Also note that if services are added to a bundle, the bundle's period will always override the periods of the services added.
Service Code*	Click the selector icon and select a Service Code. Refer to Service codes.
User Defined
Any user-defined fields for the services entity will appear here. Refer to Managing user-defined fields.

3. Click Save & Close.

Changing a field value does the following: