Available
Leave Management
Annual leave entitlement calculation designed around Turkish labor legislation, with requests, approvals and a team calendar.
Which questions do the time and attendance modules answer?
Time and attendance modules answer three basic questions: When did the employee work, when were they on leave, and how will these hours be reflected in pay at the end of the month? Sora İK (Sora Yazılım Teknolojileri's human resources management software) answers the first two today with the following modules; automatic reflection of these hours in payroll is coming soon:
- Leave Management: to track requests and approvals for annual, unpaid and excused leave and employees' leave balances; sick leave and maternity leave types are coming soon.
- Time & Attendance (PDKS): to collect clock-in and clock-out records, known in Türkiye as PDKS (Personel Devam Kontrol Sistemi), with a fixed QR code at the location and a location check.
- Attendance Ledger (Puantaj): to turn leave and clock-in data into a monthly working schedule per employee and export it as CSV.
Clock-in records are personal data directly linked to the employee. Our approach to protecting this data is on the Security and data protection page, and plans and prices are on the Pricing page.
In what order does time data reach the attendance ledger?
Today, time data moves in this order:
- The employee submits a leave request, the manager or the people in the approval flow approve it, and the approved leave is entered in the calendar.
- The employee's clock-ins and clock-outs are recorded in PDKS; letting employees send a correction request for a missing record is coming soon.
- The attendance ledger combines leave and clock-in data in one sheet; the human resources (HR) team reviews days that are missing or inconsistent and, where needed, adds a PDKS record manually or invalidates an incorrect one (the record is not deleted and stays in the audit log), marks sick leave days and enters overtime items.
Today Payroll is not fed by the attendance ledger: the number of days is 30 for a full month and, when an employee joins or leaves during the month, is calculated from those dates. Soon, the attendance ledger period can be locked after a manager check and HR approval, and payroll will use only the locked period; unpaid leave, absence and sick leave days will also be reflected in payroll as missing days.
Today the working hour definition sets the expected working hours: start and end times, breaks, late-arrival and early-departure tolerances, night shift; the company's default schedule and employee-specific assignments. Late arrivals and early departures are calculated against this definition; HR defines weekly rest days and the company's holidays. Modules coming soon will add new links to this chain: the shift plan will add rotating and day-by-day shifts, the overtime module the calculation and approval of hours beyond normal working time, the remote work module records made outside the office, and project timesheets the work on which time was spent.
What will the time and attendance modules coming soon do?
The following modules are coming soon; their scope will be defined during development. For other categories, see the Modules page.
| Module | What it does |
|---|---|
| Shift Scheduling | Plan in advance who works on which day and at what time |
| Overtime & Compensatory Time | Track hours beyond normal working time from approval to payroll |
| Remote & Field Workforce | Collect working records of employees who work outside the office |
| Project Timesheets | Split working time by project, client and work item |
Shift Scheduling Coming soon
Sora İK has working hour definitions today: HR enters start and end times, breaks and late-arrival and early-departure tolerances; night shifts that end the next day can also be defined. The company's default schedule is selected, employee-specific schedules are assigned, and late arrivals and early departures are calculated from Time & Attendance (PDKS) records against this definition. The company's weekly rest days and holidays are also defined; the attendance ledger shows an alert when daily, weekly and night work limits are exceeded. Because each employee has one schedule, rotating patterns and shifts that change by day cannot be set up at the moment; in most businesses these rosters are prepared in spreadsheets and compared with the attendance ledger by hand when the plan changes.
Shift Scheduling is coming soon for businesses that work in shifts, such as manufacturing, retail, healthcare or logistics, to plan in advance who works on which day and at what time. In the planned module, shift templates and rotating patterns will be defined day by day on a work calendar, and managers will see approved leave on the same screen while preparing the team plan. The published plan will give the expected work day by day; PDKS records will be compared against the plan, and unplanned work will become visible through this comparison. Shift swap requests and letting employees see their own schedule in advance are also being considered. The legal assessment of the plan remains the employer's responsibility.
Overtime & Compensatory Time Coming soon
Today the Attendance Ledger (Puantaj) module does not calculate overtime from clock-in records: HR manually enters overtime (fazla çalışma) and extra-hours work (fazla sürelerle çalışma) as items with their date and minutes. The items appear in the ledger totals and in a separate column of the CSV file; an alert is shown when the year's overtime total exceeds 270 hours. Payroll does not read these items automatically.
Overtime & Compensatory Time is coming soon to track hours beyond normal working time through request, approval and calculation steps. Most businesses calculate overtime retroactively at month end; whether it was approved in advance, which period it belongs to, or whether it is paid or compensated with time off stays in scattered messages. In the planned module, overtime can be requested and approved in advance and the actual time compared with the PDKS record; unapproved or unplanned overtime will be flagged separately. Managers will be able to watch overtime build up in their teams during the period and spread the workload more evenly. For businesses that use averaging (denkleştirme), a view showing whether working time balances out within the set period is planned. Paid hours will flow through the Attendance Ledger (Puantaj) into the payroll calculation, while hours taken as time off will be tracked in the employee's balance. The limits, pay and averaging conditions of overtime are set by labor legislation. The module aims to provide a calculation infrastructure based on these rules; for situations specific to your business, seek expert advice.
Remote & Field Workforce Coming soon
Remote & Field Workforce is coming soon to keep working records for employees who work away from the office or spend their day on customer visits. In hybrid setups, office and home days are usually agreed in messages; in field teams, task start and end times are written from memory at day's end. Such records are hard to verify once they reach the attendance ledger. In the planned module, employees will enter remote days as a plan and field staff will record the start and end of tasks; these will flow into the ledger alongside office clock-ins. Reporting remote days as planned versus actual will show how the hybrid work policy is applied. Capturing location only at specific moments, such as the start of a task, and leaving this setting to the company is being considered; continuous location tracking is not a goal. Location is personal data under KVKK (Türkiye's Personal Data Protection Law No. 6698): informing employees and assessing whether processing is proportionate rests with the employer as data controller. The module is planned for use with the mobile app coming soon in the platform category.
Project Timesheets Coming soon
Project Timesheets is planned to record which project, client or work item working time is spent on. For businesses that work by the hour, such as consulting, software, engineering and agencies, knowing project cost and billable time matters as much as knowing total working time. Today this is usually kept in a separate spreadsheet or entered from memory at the end of the week, so project profitability rests on estimates. In the planned module, employees will fill in a weekly timesheet by project and task, and managers will approve it. Managers will define project codes and task lists; employees can log time only to projects assigned to them. Separating billable from non-billable hours will make it easier to calculate the time charged to clients. Comparing hours logged to projects with total working time in PDKS will help reveal days with missing or excess entries. The data can be reported by project and department through Reporting & People Analytics. Where working time on R&D projects must be documented, these records are also intended to feed the R&D and technopark payroll work in the payroll category.