Attendance control: reading entry-exit records together with leave records
What is attendance control software? Match PDKS entry-exit records with leave, approve late-arrival and absence exceptions, and prepare the timesheet.
According to the turnstile record, an employee came in at 08:47; according to the leave record, the same employee is on annual leave that day. Two records, same company, same day, both “correct”, yet contradicting each other. When entry-exit data is read on its own, these contradictions turn into manual fixes in the timesheet at month-end. An attendance control program is software that tracks employees’ entry-exit movements, working hours, late arrivals, early departures and absences to produce accurate timesheet data. In YazSis KurumsalPortal, the Time & Attendance Control module handles this.
Why does raw entry-exit data mislead?
A PDKS (time and attendance) device records what happened; it does not know what should have happened. Whether the employee was on leave that day, on a work assignment or on a different work pattern is outside the device’s knowledge. The device correctly records a pass through a door, but it cannot say whether that pass was a working day, a leave day or an exit for an assignment. So when raw data is carried into the timesheet without interpretation, typical errors appear:
- Leave days look like absences.
- A forgotten exit record causes working time to be calculated wrongly.
- For shift workers, a late arrival measured against fixed working hours does not reflect reality; the company has to define late arrival according to the work pattern.
- The same event is recorded differently in two separate sources, and people argue about which one to rely on.
Attendance control in five steps
Instead of leaving movement data scattered, the Time & Attendance Control module of YazSis KurumsalPortal brings it together on one screen and carries it to the timesheet through this flow:
- Receive the data: PDKS movements are brought together on one screen.
- Match to the employee: Each movement is matched to the relevant employee; entry-exit and working time can be followed from the same record.
- Check the exception: Late arrival, early departure and absence are tracked separately as exceptions.
- Complete the approval: When each exception has been checked and approved, the attendance record becomes final.
- Produce the timesheet: The timesheet is generated from the approved records.
Matching with leave: absence or leave day?
When attendance records are matched with leave records, leave days are separated from absences. This step looks small, but it reduces one of the most time-consuming corrections in payroll preparation: at month-end, human resources no longer has to flag every suspicious row one by one with “this person was on leave”. Putting two separate lists side by side for each employee and comparing them takes hours even in a company with a few dozen people; matching turns that comparison into the system’s job. The timesheet does not become clean by itself, but because it is prepared from checked data, it needs less manual intervention.
How does month-end go in two different ways?
In the first scenario, human resources pulls a dump from the device on the last day of the month, opens the leave table beside it and asks the manager about every suspicious row. The answers take two days, corrections are made by hand and payroll waits. In the second scenario, movements were matched to employees during the day, leave days were separated, and exceptions were approved through the week; at month-end only a few open records remain. The second scenario does not mean there are never any errors. The difference is that errors are resolved in small pieces on the day they occur, not as one big load at month-end. You can see which one your company is closer to today by looking at the time spent on the timesheet in the next payroll period.
It is not enough just to record attendance data; you need to manage late arrivals, absences and exceptions.
Don’t leave exception handling to month-end
The habit that helps most is handling exceptions as they occur rather than in bulk at month-end. When a late arrival or absence is checked and approved within the same week, the reason for the event is still remembered; a month later, managers cannot answer the question “what happened that day?” Because each exception is tracked separately in the module, you can see where records are waiting in the approval queue. The division of work by role can be summarized like this:
- Human resources: Monitors the consistency of attendance data and follows up on the closing of exceptions.
- Payroll: Takes the checked timesheet for preparation.
- Department managers: See the late-arrival and absence situation in their teams and approve exceptions.
Three questions before you start
- Where will the movement data come from? The transfer method needs to be settled according to the type of device and system.
- How does the company define late arrival, early departure and absence? If the rule is not written down, it will be applied inconsistently in the software too.
- Which payroll process will the approved timesheet feed into, and by what route will the data be carried?
A short preparation reduces the arguments that would otherwise come up in the first weeks of setup. Agreeing in advance with team managers on the definition of late arrival in particular speeds up exception approval. The answers to these three questions determine the scope of the attendance control setup. For details of the module, see the Time & Attendance Control page, and for the whole platform, the KurumsalPortal page.
Frequently asked questions
Can the data from our existing PDKS device be used?
The module brings PDKS movements together on one screen and matches each record to the relevant employee. How your existing device’s data is transferred is agreed with you during the project; which data is moved, and by what route, depends on the device and system you use.
How are late arrivals and absences tracked?
Late arrival, early departure and absence are followed on one screen together with the entry-exit movements. These cases are checked and approved as exceptions, and then the timesheet is produced.
Do leave days show up as absences?
Because attendance records are matched with leave records, leave days are separated from absences. The timesheet is prepared from this cleaner data.
How is timesheet data used in payroll preparation?
The timesheet is generated from attendance records whose exceptions have been checked and approved, providing clean attendance data for payroll preparation. The scope of the data flow with the payroll system is agreed with you during the project.
More articles
RFID on-metal tags: metal, liquid and read-zone analysis before installation
A tag that reads perfectly on the office desk may not give the same result in a warehouse with metal shelves and cartons of drinks. We put in order what to measure on site before installation and how to tune the read zone.
November 16, 2026 · 8 min readWhat drives custom software cost? Custom software pricing and how to read a quote
Three quotes for the same custom software need can differ widely, and that is no surprise. We explain the factors behind the cost, the questions to ask when reading a quote and a comparison table, without quoting any figures.
November 16, 2026 · 8 min readMobile app development cost and pricing: the key cost items in an enterprise app
Mobile app pricing cannot be reduced to a single figure; it depends on the items that make up the scope. We list the items that drive the cost of an enterprise field app and what you should put in writing before asking for quotes.
November 16, 2026 · 8 min read