In the project module, you can choose whether hours/employees should be sold via Item numbers or via salary types.
We recommend using a combination, as this provides the most options. In timesag, it is recommended that only salary types are used for hours.
OBS: If a Salary type is set up with "Salary type" "Default", the prices specified here will be the default for all employees in the timesheet.
If you choose to only use goods, the registration of hours and materials in the project draft follows the same model. Read
more about it
Combination
If a combination is used, both options are available. This means that both item and wage type are registered. Here the price is taken from the wage type in the project draft. The combination can only be achieved by using service items for which the cost and sales price is 0.00.
This does not apply in time registration. Wage types are always used here
Setting up items to combine the two models.
The combination is done by creating a service item without cost and sales price.
The group is set and under Salary types, select the Salary type to be used as a price model (Employee rate).
Here is selected Wage type Hours
Employee rates can be seen
here
Description of the fields under Salary types/Employee rates
| Field name |
Field Description |
| Unit of measure |
Unit is filled in directly on the salary type |
| Invoice text |
Enter the text you want on the invoice here |
| Type |
Here you can relate to a Project Type. If filled in here, the Type field should not be filled in the draft |
| Species name |
Retrieved from the species and cannot be edited here. |
| Item |
Here you can relate to an Item. Directly or via Project type. If filled in here, the Type field does not need to be filled in the Draft |
| Item name |
Retrieved from the item/species and cannot be edited here. |
| Sales price |
A unique sales price for the employee can be entered here. |
| Invoiceable |
Here you can set whether all postings on this Project type are billable or not |
| External Salary type |
Using payroll types provides additional facilities for employee rates and integration to payroll programs. |
| ATP. |
Using payroll types provides additional facilities for employee rates and integration to payroll programs. |
| Batch |
Here you can enter a rate for the current employee.
The rate is used as the cost price of the project entries. For example, if the Rate field is filled with 200 and the Sales price field with 500, the cost price of the entries will be DKK 200 and the sales price will be DKK 500.
However, please note that no sales prices are posted on non-billable salary types/projects.
For example, the Rate field can be used to specify the government rate for mileage reimbursement on the mileage wage type or another cost price for overtime hours. |
| Dimensions |
If dimensions are set here, they will override all other dimension selections from other modules regardless of setup. See for example Employees, Project number series, Preferences |
Setting up internal salary types
Under Internal "Salary types", the following fields must be set up: These types must be used for internal registration.
- Internal type
- Factor
- Internal project
- Billable
Vacation & Flex
Vacation/Flex etc. is set up here
The salary type must be assigned an Internal type and a dedicated internal project. An additional overtime factor can be assigned if you use it.
Entry of start-up balances (Vacation, Flex, mileage etc) is done via a Project draft. NB Holiday balance must be entered as a negative number, as the registrations are positive
Vacation must be booked per 01.05.2019 (Start of vacation year)
Overtime
In the salary types, you can set up how overtime should be calculated automatically. The overtime factor is set in the factor field. If the factor is 1.5, the overtime record will show that the overtime is increased by 1.5 hours for each hour of overtime. Other overtime factors must be calculated and entered manually.
It is possible to operate on two automatic overtime calculations. This is done by setting a calendar as default. Read more
here. If this calendar is e.g. 37 hours, it can be set up so that there are different factors up to the standard calendar normal time and above the standard calendar normal time.
Below are two overtime rates set up. One at 1.5 and one at 1.0
If the standard calendar is 37 hours and an employee has 30 hours as Standard Time, overtime will be calculated as follows.
From 30 hours to 37 hours. X hours (max. 7 hours) gives (X * (number of registered hours - 30) * 1) on the project record.
From 37 hours to Y hours. Y hours (max. 7 hours) gives (Y * (number of registered hours - 37) * 1.5) on the project record.
See the registration in Timekladden
here
Driving
In order to use the mileage registration function in the time registration drafts, a salary type must be created where the Internal type field = Mileage.
If a project is entered in the Internal project field, driving will always be registered on this project. Registration on other projects will not be accepted. This setup should be used if customers should not be charged for mileage.
If a project number is not specified in the Internal project field on the mileage wage type, the mileage will be registered on the project where the time is registered. the driving is registered.
The 'Rate' column. The tax-free mileage allowance per kilometer should be entered here.
The 'Sales price' column. Here you can enter the rate that customers should be charged per kilometer.
Note! If kilometers are registered on internal projects, these will automatically be booked without sales prices, regardless of whether or not a sales price is specified on the salary type.
Mileage rates follow the same logic as hourly rates. Therefore, mileage rates can also be entered in our price matrix under the Employee rates button. If an employee has reached the border between high/low rate, lines can be entered for this employee under employee rates, with the low rate. There is no automatic check if the mileage balance exceeds x number of kilometers.
If you use IGVA by cost value, it is recommended to define employee rates with 0 in both the cost and sales price of internal projects, so that internal projects are not charged with a cost value.
If there is no cost and/or sales price in the price matrix, the search will fall back to the setup under Salary types and retrieve prices from there.
Employee rates on salary types must be registered
Employee rates are seen
here
Items on Lønart
The timesheet can use an item + price if it is specified on the Salary type.
The item is retrieved for simulation and posting of the Timesheet and prices/discounts from the item will be used. It is the same price lookup that is in the Project draft.
No validation is made as to whether prices have been set up for the item. If prices are missing, the normal price matrix will be used. Read more
here.