Time Transaction Pricing

Timesheet transactions are the most common type of Input Based transactions that require pricing. Below you will find the priority of pricing rules that are applied to these transaction types:

Activity Codes:

The pricing regime looks first at the Activity Code to see whether it should price the transaction. Where the Subtype on the Activity Code is Charge, it prices the transaction using the rules below. Where the Subtype on the Activity Code is No Charge, the Retail value and Retail Rate equal $0 without exception.

Price Codes:

Where there are entries in the Labour Tab of the Price Code, these rules will take first precedence in establishing the Retail Value of the transaction.

The Retail value will derive from the Sell Rate field, or the Markup % on Cost (MU%) field.

Note: you can have a Sell Rate OR a MU %, not both. If one of the fields has data, the other will not be available until the first is zeroed out.

The Priority for a line can be set to High or Low, to determine which of two conflicting rules is to apply first. E.g. if there are rules for a Person AND their Employee Class AND the Person, the rule designated as High will take precedence.
If ALL Priorities are set to High, the order of preference is Activity Code, then Person, then Employee Class.

Employee Class:

Where there is no rule applying from the Price Code, the Selling Rate from the Employee Class belonging to the User will apply.

Note: The Activity Code Sell Rate and Markup % are NOT used in any pricing of Time-type transactions.