Pricing and costing dimensions home page
The dimensions that are used in human resources to set up pricing and costs fall into two categories:
- Planned work
Because of this, there are two types of pricing dimension values available in Project Service Automation (PSA):
- Option sets - Dimensions that are fixed enumerations for a set of values.
- Entity-based values - Dimensions that can be a varied set of values.
PSA ships with a default set of pricing dimensions. You can view these by going to Project Service > Parameters. In the parameter record, on the Amount-based pricing dimensions tab, verify that the role, msdyn_resourcecategory and resourcing organizational unit, msdyn_organizationalunit have the fields Applicable to sales and Applicable to cost set to Yes. This will allow you to set up the price and cost for each role and organizational unit combination.
If you have been the using out-of-the box fields of role and organizational unit as pricing dimensions prior to version 3 of PSA, there will not be any observable change. You can continue to use Project Service as usual.
If you need to price or cost for your resources using additional attributes, you can create customized fields, entities, and dimensions. For more information, see the following topics, however note that you must complete the procedures in the order listed below:
- Create custom fields and entities
- Add custom fields to price setup and transactional entities
- Set up custom fields as pricing dimensions
- Update plug-in attributes to include new pricing dimensions
Pricing human resource time
How an organization prices human resource time is often an important strategic consideration that directly affects the organization's profitability. Work with the finance teams and practice heads when your organization is ready to identify how it wants to set up bill and cost rates for human resource time.
Other considerations for pricing include whether to re-use fields or entities that are not currently pricing dimensions but apply as a pricing dimension for your organization. Fields like Transaction Category (msdyn_transactioncategory) and Bookable Resource (bookableresource) are examples of candidate dimensions.
You should also consider whether your pricing dimension should be a table or an option set. If you foresee changes to the values of a dimension which will exceed 10 or 12 and you need additional attributes on these values, you could create an entity rather than an option set. Maintaining an option set, such as adding or removing values, requires an admin or developer whereas adding new rows to a table can be done by most users.
The following example shows bill rates that are set up based on the role and the resourcing org unit to which the resource belongs. Cost rates are typically based on the salary band of the employee and the org unit that they belong to. In this example, the bill rate and cost rate tables will look like the following.
Sample bill rates
Sample cost rates
|Salary Band||Org Unit||Unit||Price||Currency|
|My company_Band1||Contoso US||Hour||145||USD|
|My company_Band2||Contoso India||Hour||67||USD|
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.