Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Most often there are differences between employees within an organization like additional bonuses should be triggered if something happens or an extra pay type should be triggered for all working hours for some users. There are SO many different ways of giving payment it is some times overwhelming. I believe that this is where the AX solution shines. You can create any type of delimitation rule to solve any issue. Please challenge me if you have a nut to crack.
By using pay agreements delimitation you can create common pay agreements that can fit the entire organization, but keep a good record of what you are doing as these can grow to be pretty big. This is how I do it. If someone has an input on the matter. Please share! :)
The reason why I like to create one pay agreement for the entire or at least the majority of the organization is that often there are some common denominators and these might be changed now and again. So if you have one pay agreement you only have to change this once and not replicate it to the entire organization. I would love to see the opportunity of adding multiple pay agreements to a user in the future.
So I use the pay agreement to mainly work for the entire day (No time entered). Then I use the configuration of the profile and/or worker to trigger the different agreements.
I’d thought I would go through each of the parameters and give an example to what it can be used for, but you have to open your mind to the possibilities here. Often combinations of more then one delimitation can be used for the wanted effect.
There is a button on the form called Delimitations which get even more Advanced. I’ll go in to those in another post later as the functionality does not seem to be finished at this time.
Use this to add more or less than one pr. each working hour. I had a case where they needed to add 25% more hourly pay if the user worked flex hours. I used this on the Flex+ type with 0,25 of the standard hourly pay type.
If the times only apply during a certain time span. I don’t use these and let the profiles control the triggering.
This is often used if you only want to trigger the pay type from, to or between between a given interval. For instance a bonus is paid if the worker works more then 12 hours. You can easily create a stair case modeling of pay types by using this delimiter.
If you have pay types triggered differently between certain periods like summer or winter you can use this. This is not for Public holidays or Things like that. That is what the “special” day is used for.
The seniority is calculated based on the seniority date on the employees time and attendance settings. The seniority date can differ from the hire date and is not a mandatory field, so make sure to fill this out before you use this feature. I believe the fallback will be to the employement start date.
Pretty common stuff, but I have never used it. In Norway we normally don’t round off until the payment is done.
These are measures that are counted within a period. Meaning it is set to zero at the start of each period. If the count unit is between the min and max values the pay type is triggered. This is mostly used to limit the amount of transactions within a period.
This was mentioned in the Profiles setup as well. These are codes that are triggered by the users and can be used to switch to a secondary profile type. It can also be used to select what type of pay type to be triggered. I use this often for building up a “time-off” account (as opposed to using flex time) when the user should not have overtime but is outside the normal working hours. I then put this delimiter on the overtime records to get this to trigger. Often used in conjunction with a “Count unit” and a secondary factor if for example they get 1,25 for each overtime hour worked, but only up to 5 hours pr. week.
I use this A LOT! This is the manufacturing operations. If a user should get a premium for each hour he does an certain operation, then this is triggered. Customers love this as this is normally solved by using extra time sheets, and with this it just works by it self.
Project ID and activity:
I guess this could be used for standardized internal projects or if a customer pays extra for a special Project, but if a type of Project Activity or category should give a premium as standard across multiple projects; then the “Advanced delimitations” must be used.
This is the indirect activities of type “Jobs”. For instance some companies does not pay for union meetings.
I had a customer who would not allow contractors to have their time be posted to the systems waiting job. So they said that for all Contractors the Activity: “System job” should deduct 1:1 hour pay. This really increased the accuracy for their time registrations!
I use this a lot because some rules for payment of absence types often only apply to some types of workers. I use this as opposed to use the pay type settings directly on the absence code. I often use the “Advanced delimitations” for this as I can then trigger on a group level.
On Call Activity:
These are indirect activities of the type On Call. I use these for the Forman or Team leader permiums to be triggered if someone not normally in this position has to fill in during absence. The On Call is active for all working hours within the profile. I also use this when a person triggers his own permiums like emergency call outs, but then often with a fixed quantity.
I use this to trigger shift premiums for night or evening shifts. I often use “Advanced delimitations” if more then one profile triggers the same pay type.
Skill (with leveling):
Skills are set on the individual employee. I use this for Premiums related to a skill some times.
I use this for individual separation and multiple grouping of employees. You can also use skill for this purpose. The difference is that skill is leveled, and certifications can expire. I separate the worker types and special Premiums for this. So a user can for instance be a part of the manufacturer, hard laborer and forman, while another might not have the forman or hard laborer active. Both on the same pay agreement, but different terms.
In the profile calendar you can determine special days. This does not need to trigger the “special pay agreement day type”, but could be a special Tuesday for some reason… Thus giving a special premium for that particular day.
This gives a negativ amount of the pay type triggered.
If this checkbox is active the system post the cost, but does not create a pay transaction. So this is just for a costing perspective. As I don’t use the costing in time and attendance this doesn’t apply to my setup.
Hour rate / Piece work:
You can select both or one or the other.
I use this actively as I differentiate between 100% or 50% overtime payment in my profiles. You can also create your own type of profile types. I have had an example where the users working Friday after lunch got 1,25. In that case I used a special profile type of the type work and added a pay type with 0,25 extra for each of the hours worked on this profile type.
Go to the AX 7 – Time and Attendance guide page
Business Applications communities