Timekeeping and Payroll Digitalization: Shift-to-Salary Data with GDPR-Compliant Design

Timekeeping is one of the most contentious processes in businesses: paper lists, late shift changes, and discrepancies in overtime calculations. Because payroll is built upon this data, every error in timekeeping is reflected in salaries. Digitalization fixes this chain; however, processing personnel location, check-in/check-out, and sometimes biometric data requires placing personal data protection legislation at the center of the design.

End-to-end flow: four layers

1. Planning: Shift templates, site- or branch-based assignments, and leave calendar.
2. Recording: Mobile check-in, dynamic QR verification, and manager-approved manual adjustments.
3. Calculation: Daily and monthly timekeeping, overtime, missing days, and leave deductions.
4. Payroll: Salary components, deductions, multi-lingual payroll output, and transfer to accounting.

Each layer takes the output of the preceding one as input; therefore, accuracy begins at the recording layer.

Why is dynamic QR safer than a fixed card?

A fixed personnel card or static QR code can be copied and scanned on behalf of someone else. In dynamic QR, the code is renewed at short intervals and verified on the server side, making the "buddy punching" scenario difficult. This method provides a reasonable level of verification without collecting biometric data, which is a significant advantage in terms of personal data.

Personal data: principles to embed into design

The Law on the Protection of Personal Data (KVKK) numbered 6698 in Turkey, the Protection of Personal Data Law in the TRNC, and GDPR for EU-related operations emphasize similar principles for timekeeping systems. Their software design equivalents are as follows:

• Purpose limitation: Location data is collected only at the moment of check-in and to verify workplace boundaries; tracking is not performed throughout the day.
• Data minimization: Biometric verification is not collected unless required. If required, explicit consent and separate security measures are needed; make this decision with your legal counsel.
• Notice: Personnel must be able to see within the application which data is processed for what purpose.
• Retention period: A defined retention period and automatic anonymization/deletion rule for raw check-in records.
• Access control: A site manager only sees their own team, and HR only sees the company they are authorized for.

The cheapest form of compliance is the decision made during the design phase. A "KVKK module" added later often attempts to legitimize an existing data collection habit on paper.

Approval flows: whose responsibility is timekeeping?

In digital timekeeping, saying "the system calculated it" is not enough; every monthly timekeeping must have an approver. An example flow: the field supervisor makes daily adjustments and approves them, HR checks and locks the monthly timekeeping, and payroll is calculated from the locked timekeeping. In a locked period, changes can only be made by an authorized role, with the justification recorded.

Payroll calculation: keep rules as data

Rules such as overtime coefficients, weekly rest days, public holidays, and night work vary by country and collective bargaining agreement; Law No. 4857 is taken as basis in Turkey, and its own labor legislation in the TRNC. Keeping these rules in date-ranged parameter tables instead of hardcoding them into the software eliminates the need for software redeployment when regulations change. Having multi-lingual payroll output reduces disputes in businesses with foreign employees.

Connection with accounting

When payroll accruals are transferred to the accounting software, using summaries based on cost centers or sites rather than personnel reduces personal data sharing and directly feeds project cost reports. This also forms the basis of valuation and cost analysis in construction companies.

Implementation proposal

Shift planning: the upstream of timekeeping

Timekeeping errors often start at planning. If shift templates (morning, evening, night, rotating), weekly rest rules, and leave calendar are defined in the system, the "expected" working hours of the personnel are known in advance; actual check-ins are compared against this expectation, and discrepancies (late arrival, early departure, unplanned work) are automatically flagged. The supervisor's job is not to write timekeeping from scratch, but to approve or correct the flagged discrepancies.

Exception management: forgotten card scanning

The most common exception in any digital timekeeping system is personnel forgetting to scan the code upon exit. The system should treat this situation not as an error, but as a record to be resolved: the missing exit is flagged, the personnel or supervisor completes it with a justification, and the completion record includes who made it. The possibility of unreasoned and unrecorded corrections destroys the reliability of the system within a month.

Subcontractor personnel and site entry

In construction and manufacturing sectors, subcontractor teams are on the field alongside your own personnel. You do not calculate payroll for these individuals, but knowing who enters the site is mandatory for occupational health and safety (OHS) and security. The system should keep subcontractor personnel in a separate class, record only check-in/check-out and OHS training status, and not collect payroll data. This is a concrete application of data minimization: if the purpose is different, the collected data is also different.

Reports: for whom, at what detail?

• Site manager: Who is on the field today, who is missing, which adjustments are pending.
• HR: Monthly timekeeping summary, leave balances, overtime distribution, periods awaiting approval.
• Finance: Labor cost based on cost center; without individual-based details.
• Management: Site and period comparison; personnel data only at summary level.

Narrowing report detail according to the role both prevents unnecessary data sharing and simplifies screens.

Technical design notes

-- Example: locked period rule (conceptual)
-- A timekeeping row belonging to a locked period can only be modified by the 'hr_manager' role and with a justification.
create policy timesheet_update on timesheets for update using (
  not period_is_locked(period_id)
  or (current_role_key() = 'hr_manager' and current_setting('app.change_reason', true) <> '')
);

When the rule lives in the database, a bug in the interface cannot open a locked period; this is the technical foundation of payroll reliability.

Personnel trust

The biggest benefit of digital timekeeping is reducing disputes: personnel can see their own check-in/check-out records and timekeeping from the app, and submit objections in a recorded manner. Transparency is a requirement of both personal data legislation and industrial peace.

Our experience shows that running timekeeping digitalization in parallel (paper and digital together) on a single site or branch first is the healthiest way. Discrepancies are compared daily, rules become clear, and then it is rolled out to other locations. Cy Logic's HR and timekeeping solutions include this phased transition and the personal data principles above as standard.