This is the first post in the AX 7 T&A guide series.
Time and attendance is a very flexible solution for registering attendance and absence as well as manufacturing execution and realtime project feedback.
This is a pretty big setup job if you want it to be done properly. You can however get started right away! Following these steps will get you to start registering time clocking in and out.
1. First you need to run the configuration wizard under Wizards. This will create the required setting like system jobs in indirect activities (clock in/out, wait time, abort pause and more), terminal configurations and profile types.
2. Go to time profiles (Time and attendance > Setup >Time profiles > Profiles) and set up a profile single. This define the workers actual working times. You do not need to enter anything in to the profiles, but you need atleast to create a blank one for setting the required parameters on a user.

- Profile group
Time and attendance > Setup > Time profiles > Profile groups - Calculation group
Time and attendance > Setup > Groups > Calculation groups - Approval group
Time and attendance > Setup > Groups > Approval groups
4. Go to the Workers (Human resources > Workers > Workers). On the “Time” pane in the menu bar under the “Maintain” group: Click on “Activate on registration terminals” and fill inn the required fields.
5. Now launch the Time and attendance registration terminal and select a terminal setup.
Common > Common > Time and attendance > Clock in/out (Punch clock)

You can now clock in and out using the employee Id (Leave password blank if not set) and do the same to clock out.
This is the bare minimum to actually start registering attendance. Cool thing is… If you’re only looking for the attendance part of the solution you can start punching time and do the rest of the setup later.
Go to the AX 7 – Time and Attendance guide page
Hello, I did the process but unfortunately, when a worker “clock in” his stamp been copied to all workers and I can’t change it because of this error
Processing has stopped because of a validation issue.
Hi there,
I would try and go explore the jmgTermReg in TableViewer to see what is going on… There is a pilot function, but each person has to be assigned a pilot at that point. That is the only way I know a person could “inherit” transactions from another clock in.