This post is one of a series I’m creating connected with Project Service Automation (PSA) for Microsoft Dynamics 365. This time I will consider sales prices.
Sales Price Lists
A sales price list is used to hold the prices that will be charged to customers for all project related activity plus any “regular” products purchased. For example, in a CRM implementation you may have project costs for a developer’s time but you may also have product costs for things like software licenses.
Before we start adding prices for specific roles we first need to define several fields. These are itemised below.
| Field | Description |
| Name | A mandatory field that is simply a text field to describe the purpose of this price list. |
| Context | The context for a sales price list MUST be set to “Sales”. Other options include Cost and Purchase. |
| Start Date | An optional date that defines when these prices become effective. |
| End Date | An optional date that defined when these prices will expire. |
| Currency | A mandatory field that cannot be changed after the price list is created. |
| Time Unit | Once set the time unit cannot be changed. It will default to hours but you can see in my example that I have changed it to days. This field selects the possible units from the “Time” unit group.
You’ll find some more detail on unit groups later in this post. |
| Description | An optional text field that can be used to describe the purpose of this price list. |
Role Prices
Once you have created the price list you can add role prices. The concept of a role price is to define the price of a type of resource per organizational unit. (Or resourcing unit.)
In my example above I have shown that a developer in the UK will cost the customer £130 per hour. But if an off-shore resource is used from India then they will cost £80 per hour.
Below you can see the quick create form that is used when adding role prices to an organisational unit. Notice that the units cannot be changed. As all of the prices need to be expressed in terms of the units defined on the cost price list. In my case “hours”. Also, the currency for all of the role prices will match the currency defined on the price list.
Price List Items
In addition to role prices a sales price list can contain prices for other items from the product catalog. This is achieved by using standard CRM pricing functionality as found in the Price List Items option.
Below you can see that I have added price list items for some CRM licenses. (Not real prices!)
Unit Groups
In my example the price list I used worked in hours. The possible time units can be configured in the unit groups option. In settings navigate to the Unit Groups option, which you will find in the Product Catalog area.
In unit groups, you will find a unit group called “Time”. Mine is shown below. The units option lets you define the units of time that you wish to operate in.
Notice that the base unit is hours. Then a day is defined as 8 hours. You could change this or add additional units. For example, you could add a unit of “Week”, which could be defined as 5 days or maybe 40 hours etc.
Obviously calculating the sales price of a project is an important task. I hope I have shown that pricing options in PSA are flexible enough to cope with most situations.
J
Microsoft Dynamics 365 
Pingback: PSA – Opporunities | Microsoft Dynamics CRM and Unified Service Desk
Pingback: PSA – Complete Guide | Microsoft Dynamics CRM and Unified Service Desk
Pingback: PSA – Invoicing (Part One) | Microsoft Dynamics CRM and Unified Service Desk