Contents
1. What is this module for?2. The personnel record — where everything starts3. Legislation — the numbers are not baked into the code4. Working time — shifts, attendance, overtime5. Qualification — not everyone can step up to any machine6. Occupational health and safety6b. Assigned items and PPE — signed issue, return, renewal6c. Absence — late arrivals, Bradford score, warnings and discipline, sick note tracking6d. Training management — mandatory training matrix, plan and budget, results, renewal, effectiveness6e. Targets and evaluation — period, target card, self and manager evaluation, calibration, bonus proposalAutomatic measurement of production, quality and delivery targets6f. Pay bands and raise simulation — band, compa-ratio, market data, raise scenario, approval and application6g. Shift plan — weekly schedule suggestion, rules, publishing and swaps6h. Org chart and headcount plan — position tree, vacancies, succession, approval chain6i. Employee self-service — payslip, advance / document / information requests, announcements and surveys, wishes and complaints6j. Onboarding and exit checklist — documents, assigned items, access, training, mentor, release6k. Recruitment funnel — job postings, candidate pool, interviews, job offers, hire6l. Subcontractor and daily workers — document set, site access, payments6m. Digital personnel file and personal data (KVKK / UU PDP) — documents, retention, access log, requests6n. Single personnel source — production staff and Work Center operators from the HR record6o. Portal count approvals6p. The Audit tab7. Earnings — piece rate, commission, trips, vehicles8. The personnel portal and the phone app8.1 First, signing in to the portal: employee number + PIN8.1A If the portal account changed: 409 and refresh8.2 What is on the Shift tab?8.3 Reading the plan table8.4 The plan and the punch history are not the same thing8.5 Step by step: "Which shift am I on tomorrow?"8.6 The shift plan — frequently asked9. Defence pack — stamps, signature authority, access10. Discipline and exit11. Record forms and attachments11.1 Shift and pattern setup — before attendance12. Dashboard — today at a glance13. Common mistakes14. Record forms › "Bulk staff import (CSV / list)" and the "Hire date" field15. Portal lock: the login throttle counts only wrong PINs, the lock opens without waiting15.1 Finding the right account in a crowded list16. Garnishment files and the period deduction16.1 Queue and the legal ceiling16.2 No net wage means no deduction16.3 Preview and write are two separate steps17. The Payroll tab — summary, bank list, social-security data17.1 This summary is GROSS17.2 "Not calculated" rows and the payment list17.3 Bank list: checksum and suspicious accounts17.4 Social-security data: occupation code and dominant absence reason17.5 Net payroll (Türkiye) — SGK, income tax, stamp tax, net pay18. Shuttle service — routes, stops, boarding list, contractor billing18.1 Capacity is a gate, not a warning18.2 Billing and lateness19. Canteen — card taps, entitlement checks, catering reconciliation19.1 Reconciling the catering invoice20. Union and collective agreement20.1 Union leave is a paid day21. Social-security declaration (MPHB) — worksheet, workplace record, XML package22. Bank salary file — the template engine23. The Dates tab — probation, contract end, examinationWho sees pay and payroll amountsA finalised payroll periodID, IBAN, birth date, leave days and currency checksOne open advance requestChanging the PIN in the portalPay contract, personnel card and recruitment limitsLeave and date-of-birth limitsHire date and historical record transferEmployee portal: My payslip and period finalizationRefresh on the recruitment candidate cardCancelling approved leave and portal accountsHuman Resources — A Guide from Scratch
This module puts the person at the centre. Previously one employee lived in four separate places: a name on a customer card, another record in production, a free-typed name in the leave book, a login account. The same human being, four separate identities. Now there is one personnel record, and attendance, pay, leave, health, custody and authorisation all hang from it.
1. What is this module for?
The Personnel window has fourteen tabs. Nobody uses them all; reading the one that matches your job is enough. Even so, everyone should read Sections 2 and 3 — knowing where a record is opened removes the "who is this?" question at month end.
The tabs, briefly: Dashboard (today's summary) · Personnel (headcount and person card) · Shift / Attendance (shifts, rotation pattern, timesheet) · Leave (requests and entitlement) · HSE (accidents and PPE) · Competence (matrix and assignment checks) · Approvals (reports coming from the shop floor) · Earnings (piece rate and commission) · Stamp / Access · Audit · Discipline / Exit · Portal accounts · Legislation (country settings) · Record forms.
2. The personnel record — where everything starts
For a new employee you first open the personnel card, then an employment period. These are separate, and the separation matters: a person is defined once, but may join, leave and join again. In seasonal work the same person is hired a third time; had we kept a single start–end pair, seniority and leave entitlement would be wrong from the outset.
2.1 Two mandatory fields
Employee number and employment type cannot be left blank. Without an employee number you end up with two of the same name at month end. Without an employment type (payroll / subcontractor / freelance / trainee / outsourced service) turnover, cost per head and the attendance summary break silently: if a subcontracted haulier is counted as staff, three reports go wrong at once.
2.2 Who can see sensitive fields?
Pay, identity number, bank account, health information and address are filtered by role. There is an important design decision here: if you lack permission the field is not shown empty, it does not arrive at all. Masking with asterisks is misleading — "something exists but I cannot see it" is itself information. A foreman enters attendance but does not see pay or identity; it is not needed to enter attendance.
3. Legislation — the numbers are not baked into the code
The overtime multiplier, the weekly maximum, the number of leave days, the deduction ceiling, the notice period — these are all numbers that change by country, and none of them is written inside the program. They live in the Legislation tab and can be edited. Opening in a new country requires no code: copy the existing set and change the figures.
Why does this matter so much? In Türkiye overtime is a flat ×1.5. In Indonesia it is ×1.5 for the first hour, ×2 thereafter, and the hourly rate is the monthly wage divided by a fixed 173 — not by that month's actual hours. Compute both countries with the same formula and payroll comes out wrong; the gap is not small, so a complaint arrives sooner or later.
Rows whose source shows "Awaiting confirmation" are figures the program assumed but has not verified. Confirm them with your accountant or advisor before using them for payroll, and update the record. The warning sits in a yellow strip; it does not disappear on its own.
4. Working time — shifts, attendance, overtime
A shift is a template: start, end, breaks, and whether the break is paid. A night shift spills into the next day; the program resolves this itself — do not open a second record because "it passed midnight". Attendance is kept day by day and every day has a status: worked, on leave, sick-noted, work accident, absent, public holiday.
A work accident and a sick note are not the same thing. Both mean "did not come", but one arises from an accident and counts as lost work days, the other does not. The program keeps them as separate statuses; when you record a work accident the lost days drop into attendance automatically. If you type "sick-noted" by hand, your accident statistics look smaller than they are.
4.1 If you have no time-clock device
A device is not required. A punch can arrive four ways: a shared terminal (a tablet in the workshop, card number + PIN — no extra hardware), a phone (the personnel portal), a CSV import (if you already own a device), and manual entry. Whichever way it arrives, the raw punch is written into the same ledger.
A raw punch is never altered. If a punch is wrong it is not deleted; the correction is written as a separate row and who corrected it and why stays in the record. In an audit this is the only sound answer to "was attendance edited after the fact?".
When the year closes, the Year carry-over button on the Leave tab (manager) writes the remaining leave into a carry row: entitlement + previous carry − that year's usage. A preview is shown first; nothing is written without confirmation. Leave crossing the year boundary (e.g. 28 Dec–9 Jan) is split between the two years by day ratio. Once carried, the balance is computed per year; the izin.devir_azami parameter can cap the carry (empty = unlimited). A negative remainder carries too — debt is not silently erased.
Manual punch and the timesheet period. HR writes a forgotten clock-in/out by hand; this needs an HR role, a reason (at least 5 characters) and an open timesheet period; closing and reopening the period belongs to the HR Manager. Details: Timesheet and Leave › Manual punch and the timesheet period.
5. Qualification — not everyone can step up to any machine
Which machine an operator may run, which operation they may perform and which decision they may take is recorded. Where a qualification requirement is defined the program blocks: an unqualified person cannot confirm that work. Where no requirement is defined nothing is blocked — installing the pack does not stop a running production line.
The qualification matrix also shows single-point risk: if only one person can do a job, work stops when that person goes on leave. The dashboard shows this count in red; it is an early warning to train a second person.
6. Occupational health and safety
A medical examination may impose a restriction: "may not work in noise", "may not lift loads". From the moment it is recorded the restriction blocks assignment. It is not a warning; assignment to that environment or duty is not possible. A restriction is specific to the hazard: someone restricted from noise may still be assigned to dusty work.
The same logic works in three more places: anyone under 18 cannot be assigned to night shift or to a hazardous environment; anyone without the mandatory certificate (driving licence, operator certificate) cannot be assigned to that equipment; and when PPE life expires the item lands on the renewal list.
6b. Assigned items and PPE — signed issue, return, renewal
On the Assigned items / PPE tab of the Personnel window, PPE and equipment (laptop, phone, hand tool, measuring device) are given to a person with Assign in three steps: assigned item, signature, save. The recipient signs with a finger on a phone or tablet; the signature is stored unchangeably and is shown with the Handover signature button on the row. The same measuring device, or the same stock code and serial number, cannot be in open assignment with two people.
Issue period. In the Definitions view each PPE gets a service life (days), whether it is sized and whether it is taken back when the employee leaves; role requirements set the mandatory PPE and the issue period for each role (an empty period means the definition's service life). When the same PPE is issued again, the previous record is closed by renewal: it drops off the end-of-life list and out of the assignment gate. The Due view shows expired renewals, those due within 7 days and upcoming ones, expected equipment returns and mandatory PPE missing by role; the same dates are reminded 30 and 7 days ahead in the HR source of the contract calendar.
Return. In the Take back wizard choose the result (returned intact, returned damaged, lost, consumed, wrong entry); an explanation is mandatory for damaged, lost and cancelled records, and the person returning may sign (no signature for a loss). A closed assignment cannot be taken back a second time; if two screens press at the same moment only one is saved. The HR manager, HR staff, department managers and foremen can issue and take back PPE and equipment; returning cash custody (cash, cheques, receipt books), cancelling a wrong entry and the definitions belong to the HR manager only.
Exit hook. An employment period cannot be closed while the person still holds open items or cash custody or PPE that must be returned (blockers ACIK_ZIMMET, ACIK_KKD; a justified override leaves a trail), and the Assignment return and PPE return items of the exit checklist cannot be completed by hand. When the last item is returned, the checklist item completes itself. The Awaiting return view lists, person by person, what is still held by people who have left or whose exit checklist is open.
6c. Absence — late arrivals, Bradford score, warnings and discipline, sick note tracking
The Personnel › Absence tab measures everything from the timesheet (the day record that goes to payroll). Late arrival: clock-in later than the day's shift start by more than the tolerance (default 5 minutes). Early leave: clock-out earlier than the shift end by more than the tolerance. Absence day: timesheet status Absent. Sick day: On sick leave / Rest / Work accident, or approved sick leave. The attendance board shows these counts per employee and the Bradford score for the last 365 days (spells² × days; days separated only by holidays or weekly rest belong to the same spell). Frequent short absences score higher than one long absence. Click a row for the day-by-day list, sick periods, cases and disciplinary records.
Rules: the HR Manager defines the measure (late arrival count or minutes, early leave, absence days, consecutive absence, Bradford score, overdue sick note), the period (calendar month or last N days), the threshold and the action (warning or disciplinary procedure); the scope is all employees or one department. Legal thresholds are checked even without rules and are read from the HR regulation parameters: Türkiye 4857/25-II-g (2 consecutive workdays, 3 workdays in a month, twice a month on the workday after a holiday; the right to terminate lapses 6 workdays after learning of it, 4857/26), Indonesia PP 35/2021 art. 36 j (5 consecutive workdays and 2 written summonses). A legal threshold only warns; termination or penalty is HR's decision. Check thresholds now first shows a preview; every recorded breach is a case and the same breach is never opened twice.
Case decision (2 steps): open disciplinary case (HR Manager only; decision "statement requested" — no penalty can be recorded before the statement, the penalty is given on the record in the Discipline / Exit tab), warning given, close or dismiss (reason required). For a rule with the discipline action, the case is opened together with the check if the person running it is the HR Manager. The step comes from valid earlier penalties of the same type (in Indonesia a warning letter is valid for 6 months — PP 35/2021 art. 52(2)); the suggested decision is read from the disciplinary step order (TR verbal → written warning → deduction → termination; ID SP1 → SP2 → SP3 → PHK). A new case is messaged to the supervisor and HR staff; an undecided case is reported to the HR Manager after the escalation period (default 3 days) and to the managers after twice that. The daily automatic check is enabled on the server with DEVAMSIZLIK_GOREV=1 (off by default).
Sick note tracking: the sick periods in the timesheet are matched with sick note records (type, number, issuing institution or doctor, date HR received it and the scanned document attachment); once the submission period (default 3 days) passes, the period becomes "Sick note overdue" and can trigger an "overdue sick note" rule. Unrecorded workdays: for employees who clock in/out, workdays with no punch, no approved leave and no closed timesheet day are listed; a timesheet manager records them as absent or sick leave with one click (at most 62 days; not written in a closed month, never recorded twice for the same day). If the person worked, correct the punches first. On phones (Garden / Step interface) the same views appear as cards, and sick note recording and case decisions open step by step.
6d. Training management — mandatory training matrix, plan and budget, results, renewal, effectiveness
In the Personnel › Training tab start with Definitions: the training catalogue (code, duration, validity in months — 0 means no expiry, renewal reminder, cost per person, effectiveness evaluation day) and the mandatory training matrix (all employees, department, role, machine, work centre or product × training; optional “days after hire”). Machine, work centre and product rows cover the employees of operators who hold a competence on that target. The Status view shows for every active employee: valid, renewal approaching, expired, never taken, due at hiring or planned; the compliance percentage and the gaps per training are on top.
Plan: Create plan on a “Gaps per training” row or Plan training opens a 3-step wizard — Training (date, location, trainer) → Participants → Budget and save. The annual training budget for the company or a department is entered in the Budget view; a completed plan counts with its actual cost, an open plan with its planned cost, a cancelled plan does not count. What happens when the budget is exceeded is a setting: Do not check, Warn (the record is saved and a warning is shown) or Block (passes only when the HR manager approves with a reason).
Results: the Enter results wizard on the plan detail (Attendance → Result → Save). For every attendee one row is written to the training history (the training record on the employee card; a correction updates the same row); certificate validity = end date + validity months. If the catalogue links the training to a competence, the work centre competence matrix is written to the operator record of each person who passed at the same time (the level goes up, validity comes from the training); if the person has no operator record the screen says it could not be written. Results of a completed plan cannot be changed; a participant with a recorded result cannot be removed and such a plan cannot be cancelled.
Renewal, effectiveness, competence gaps: the end of validity appears in the company calendar as “Training renewal” (T-30 / T-7 / T-0 reminders and escalation follow the calendar rules; clicking the item opens this tab). The Effectiveness view asks “did the training work?” the catalogue number of days after the end: method + effective / partly effective / not effective. The Send to training plan button in Work centres › Competence opens this tab’s Competence gaps view: for every operation whose routing requirement lacks competent operators it offers the suggested training and candidate operators, a plan in one click. Permissions: definitions, budget and budget overrun approval — HR manager; plan and results — HR manager or HR staff; effectiveness — also the department manager. There is no new permission bit.
6e. Targets and evaluation — period, target card, self and manager evaluation, calibration, bonus proposal
In Personnel › Targets › Periods the HR manager opens an evaluation period: code, start and end, self- and manager-evaluation deadlines, the weight of targets in the result (the rest goes to competencies), the achievement cap and the grade table (grade, minimum score, bonus proposal as a percentage of the monthly gross, raise proposal). Stages move in order: Draft → Target setting → Evaluation → Score calibration → Closed. In the Targets view company, department and individual targets form a tree; each target has a measurement source (manually entered actual, CRM sales target with actual revenue, production efficiency from the MES scorecard, absent days from the timesheet, mandatory training compliance or, for company/department targets, the average of sub-targets), a direction and a weight. Individual targets are written by HR or the person’s manager, and one target can be given to many people at once; if a person’s weights do not total 100 a warning is shown.
Scoring is calculated in one place: the achievement percentage is actual ÷ target × 100; for a “the lower, the better” target staying under the target counts as 100% and the result drops by the overshoot rate; the value is limited by the achievement cap. For a target that cannot be measured (no source or no records) the manager’s 1–5 rating × 20 is used. The target score is the weighted average of the rows. Competence rows come from the person’s role, department and company competence requirements and from the valid authorisations they hold (current and required level are shown); the manager rates each from 1 to 5. Result = target weight × target score + remaining weight × competence score; if one is missing the other alone is the result.
Start the evaluation opens a card for everyone with an individual target; the card’s manager is the person’s manager at that moment. The person opens the card from My card and completes the self-evaluation with a 3-step wizard (targets, competencies and comment, summary and send); for someone without an HNR user, HR enters it on their behalf and this is recorded. A manager sees only their own team’s cards and evaluates them with the same wizard; the person sees the manager’s ratings once the evaluation is complete, and the self-evaluation can no longer change from then on. A sent manager evaluation cannot be changed; if it is sent twice at the same moment, the second is rejected. Self and manager deadlines are reminded in the Company calendar 30, 7 and 0 days ahead. The My goals tab in the Employee portal shows the person’s card read-only (no bonus amount is shown).
The Score calibration screen shows the grade distribution and department averages; in the calibration meeting the HR manager enters a calibrated score on a card, and a reason is required if it differs from the result. Close period freezes the measurements at their current values, converts the final score (the calibrated score, otherwise the result) to a grade using the grade table, and calculates the bonus proposal = monthly gross in the employment contract valid today × the grade’s bonus percentage and the raise proposal = the grade’s raise percentage. While a card’s evaluation is incomplete, closing is possible only with the HR manager’s reason. Bonus and raise proposals are visible only to the HR manager; Send proposals for approval places each proposal in the Approvals box, the decision is made there or on this screen, and a person cannot decide on their own proposal. Proposals are not written to payroll; an approved proposal is the basis for HR’s pay action.
Automatic measurement of production, quality and delivery targets
In the target form five automatic sources can be chosen as the Measurement source; the value is calculated with the same rule as the existing measure — there is no second calculation. MES OEE: availability × performance × quality — the same as the MES board and the machine utilisation report; if the target value is left blank the OEE target in the MES settings is used. Scrap rate: scrap reported in confirmations ÷ produced quantity — the same as the scrap and waste report; if the products have different units no company-wide rate is given and a product filter must be chosen. Confirmed good quantity: confirmed quantity − reworked quantity. Customer PPM: (sales returns + customer-complaint nonconformities) ÷ quantity shipped × 1,000,000. On time in full (OTIF): the same as the OTIF report; with “Supplier delivery” it is the on-time delivery rate of the supplier performance report. A cancelled confirmation never enters any measurement. These sources can be used on company, department and personal targets; for scrap and PPM the direction is “the lower, the better”.
Depending on the source, the Measurement filter takes a machine code, station code, shift code, product (stock code), account code and the first / last month of measurement; if Only this person’s terminal records is ticked on a personal target, or Only this department’s operators on a department target, the measurement uses the jobs those people closed on the MES terminal. Before saving, Try the measurement (without saving) shows the result. Show measurement trail on a target row shows which records the actual comes from: the measurement range, the filter, the components (availability, performance, quality, shipped, returned…) and the numbers of the production confirmations, downtime records, terminal events, return documents, nonconformities or orders. If there are no records the row shows “Could not be measured” with the reason and the manager gives that target a 1–5 rating. My goals in the personnel portal also shows the source of the automatic measurement.
6f. Pay bands and raise simulation — band, compa-ratio, market data, raise scenario, approval and application
The Employees › Pay bands tab is visible only to the HR manager (and the system administrator); amounts are never sent to other roles. The Band position view compares each employee's current gross pay with their own band: the band is chosen by the job code (position) and level (grade) on the personnel card — first the exact grade, otherwise the band whose grade is *. The result is Below band, Within band, Above band or no band defined; compa-ratio = gross ÷ band midpoint. People whose pay type is not monthly (piece rate, etc.) or whose contract currency differs are not compared. In the employee list the Pay band filter lists those outside their band; the person panel shows a band badge. Pay outside the band and below minimum wage also appears in the Owner Dashboard and Pulse alert boxes (without amounts).
In the Pay bands view a band is entered with position (job code), grade (* = all), minimum, midpoint (average if blank), maximum and validity start / end; the currency is the company's local currency. Bands are never deleted, they are revised: revising with the same start keeps the old version as Revised; revising with a later start opens a new validity period and the previous period ends one day earlier. Two bands with overlapping periods cannot exist for the same position and grade. The History button shows the revision chain. In Market data you enter 25% / median / 75% values by hand with a mandatory source note (survey, report, job site); the row shows how far the median is from today's band midpoint.
Raise scenarios › New raise scenario is a 3-step wizard (full screen on phones). 1. Scope: name, effective date of the new pay, department / position selection and band position filter (all if none selected). 2. Method: percentage raise for everyone, fixed amount for everyone, bring those below the band up to it (to the minimum or the midpoint; optional rate for those within) or raise by performance class of a closed evaluation period (the raise proposals on Employees › Targets cards; a separate rate for people without a card). Optional round up and do not exceed the band maximum settings are available. 3. Preview: the calculation runs on the server; each person's current and new gross, increase percentage and compa-ratio change are shown, and a new pay can be entered manually on the row (it cannot go below current pay). Minimum wage check: if the new pay is below the minimum wage on the Legislation tab (the regional key if one exists), it is raised to the minimum and flagged; if no minimum wage is entered a warning appears. People without a contract, with non-monthly pay or with a non-local contract currency are listed separately with the reason.
The budget impact uses payroll rules. Current gross is the pay payroll uses (the largest of contracts with no end date or ending after today). Employer share: if the company carries BPJS rates (Indonesia) the social security premium calculation runs unchanged with the new gross (including JP and health caps and the minimum-wage floor); otherwise gross × the employer social security rate (Türkiye). The boxes show the monthly cost difference, the annual cost (12 months of gross + employer share + extra salaries per year; Indonesia default 1 THR) and the impact this year (months left from the effective date to year end × monthly difference + extra salary difference); months and extra salaries can be changed in the wizard. Saved scenarios stay in the list; tick up to three and use Compare selected to see method, headcount, cost difference and new gross per person side by side.
Approval and application. Submit for Approval puts a draft scenario on the Approvals screen as a Raise scenario (amount = annual cost difference); a scenario awaiting approval cannot be changed, use Withdraw from approval if needed. Four eyes: the person who sent the scenario cannot decide; the decision comes from another manager (from this screen or the Approvals screen — the status syncs automatically). For an approved scenario, Apply new pay to contracts closes each person's open contract on the effective date and adds a new pay version with the new gross (contract and pay type are carried over and the HR change log is written); it is one transaction — if one person fails nothing is written. If someone's contract changed after the scenario, or the new pay is below the current minimum wage, application stops and asks for the scenario to be recalculated; if a locked timesheet period exists after the effective month, neither application nor undo is possible. Undo application (justification required) does not delete the added versions: it makes them never-valid and reopens the old contract; if a new pay version was entered for someone after the scenario, undo is refused.
6g. Shift plan — weekly schedule suggestion, rules, publishing and swaps
The Personnel › Shift plan tab suggests the weekly schedule. Choose the week (Monday), a department and/or work centers and the shifts to plan, then press Generate suggestion. Demand comes from two sources: operations in the official APS schedule (the number of operators needed at the same time within the shift window and the competence in the routing; an operation without an operator requirement counts as one operator) and Minimum staffing rules (non-production work such as warehouse or maintenance; where both apply to a slot, the larger wins).
The suggestion assigns only available people: approved leave, a valid sick note and training days are never assigned, and a pending leave request is flagged. Rules come from the regulation set: rest between two shifts, uninterrupted weekly rest and the consecutive-night limit (vardiya.* parameters), normal weekly hours (more requires an overtime request) and the legal ceiling with the overtime cap. If a parameter is not defined, that rule is not applied and the screen says so. Night and weekend shifts are shared fairly, also counting the last four weeks of published plans; unmet demand is shown as “Capacity shortfall”.
Click a cell in the grid and choose a shift or Rest day; violations get a red frame, while capacity shortfall and warnings are listed. Save Draft → Publish: publishing writes in one step to the shift-plan register that timekeeping and the overtime gate read; rest days count as the weekly day off. A plan with rule violations can be published only with a reason, and never in a locked timesheet period. To change it, use Revise (new draft); the new publication replaces the old one, open swaps on the old plan are cancelled and people whose shifts changed are notified.
In the personnel portal › Shift › My shifts, employees see their published week (this and next week) and request a shift swap with a colleague in the same plan: on the chosen day(s) the two people's shifts are exchanged. The request is checked against the rules before it is sent; once the colleague accepts in the portal, it goes to the supervisor. The supervisor or timekeeping manager decides under Shift plan › Swap requests or in the Approval Center; on approval the rules are checked again, and a swap on a changed plan cannot be approved.
Permissions: writing plans and minimum staffing needs the timekeeping management permission; reading needs HR, timekeeping or leave approval permission (no new permission bit). On phones (Garden/Step) the plan is a three-step wizard: Week and scope → Review the suggestion (day-by-day cards, a shift choice per person) → Save and publish.
6h. Org chart and headcount plan — position tree, vacancies, succession, approval chain
Positions are defined in the Personnel › Organisation tab: code, title, department (the same department text as on the employee card; there is no separate department master), grade, parent position, headcount, validity dates and the critical position flag. Codes are unique among open positions; a position cannot report to itself or to one of its sub-positions; a position with assignments or open sub-positions cannot be closed. Records are never deleted, only closed.
The Assign to position wizard has three steps: person → position (filled/headcount shown) → date and type. A Primary assignment counts toward headcount; a person’s new primary assignment closes the previous one the day before. An Acting assignment does not count toward headcount; it is used in the approval chain while the position has no holder. If the headcount is full the entry is rejected; only the HR manager can exceed it by entering a reason (the reason is kept on the record). Optionally the department and job on the employee card are updated to match the position. Assignments are ended or cancelled with a reason; picking a date shows the chart as it was on that day.
The Headcount view lists vacant headcount (headcount − primary assignments), over-headcount and employees without a position. Open vacancy creates the pre-record of a hiring request (at most as many as vacant); once a primary assignment fills the headcount the vacancy closes automatically, and it can also be closed or cancelled by hand. In the Succession view critical positions get successors in priority order with a readiness level (ready now / within a year / within two years); a critical position with no ready successor shows red, one with only long-term successors shows amber. Successor and vacancy information is shown to the HR role only.
Approval chain: leave, overtime, shift swaps and goal reviews find a person’s supervisor in this order: 1) the manager on the employee card, 2) the department supervisor in timesheet settings, 3) the org chart — the holder of the first filled position up the person’s position line (vacant positions are skipped). The Approval chain view shows each person’s supervisor, its source and the people who differ from the org chart. Pay bands are chosen by position code first and, if there is no band, by the job code on the employee card. The chart is drawn with department colours; TV mode refreshes every 5 minutes and Print opens a landscape page. On the phone (Garden/Step) the Person card shows the supervisor, the reporting line and the team; the chart is nested cards. Access: chart and person card for everyone with the Personnel module, management for the HR role (no new permission bit).
6i. Employee self-service — payslip, advance / document / information requests, announcements and surveys, wishes and complaints
The employee portal (/personel, employee number + PIN) has five new tabs: My payslip (payslips for the last 12 months, opens as PDF), My requests (a 3-step request for an advance, a document or an information update, and its status), Announcements (HR announcements and surveys), Wishes / complaints and, for supervisors, My team’s requests. The selector at the top right opens the page in one of 24 languages; Arabic, Urdu and Persian are shown right to left. Employees see only their own record; the identity is taken from the session on every request.
Approval path. An advance goes to the supervisor first, then HR; the supervisor is the effective supervisor from the org chart (the manager on the employee record, the department supervisor in the time-and-leave settings, or the position tree). If there is no supervisor, the request goes straight to HR. Document and information update requests need HR approval only. Supervisors decide in the portal under My team’s requests (shift swaps included) or in HNR under Personnel › Portal requests and the Approval Centre; a reason is required to reject. HR can skip the supervisor step, but nobody can decide on their own request.
Advance. The cap is the smaller of a percentage of the current gross pay (default 50%) and a fixed amount; if neither is set, HR evaluates the amount. The number of instalments is limited and only one advance request can be open at a time. Approval creates no payment: the approved request moves to Approved advances, HR opens the advance with a payment entry (with instalments) on the Payroll tab and marks it Processed here. The cap, instalments and requestable document types are changed only by the HR manager under Portal requests › Settings; every change is logged with the old and new value.
Documents and information updates. The employment certificate, salary letter and medical visit form are produced as a PDF in the language the employee chose once HR approves, stored as a shared file attachment and opened in the portal; every document carries a "NOT OFFICIAL" note and does not replace an official form required by law. For an information update the employee proposes contact details, a bank account or an emergency contact, or adds a family member; the record is updated once HR approves. If the stored value changed after the request, approval is refused (409) and a new request is needed. The bank account is shown in the portal with only its last four digits.
In the My requests list the request number is the document number on the approved document (e.g. IKS-12; AVT-3 on older advance records).
Announcements, surveys, wishes and complaints, and the payslip. HR writes an announcement or survey as a draft, can limit it to a department and a date range, then publishes it; a published entry cannot be changed and is closed and replaced when needed. When an employee opens the announcement a read mark is recorded; if "confirm they have read it" is chosen, the confirmation is recorded too and the Result screen lists who has not read it. In an anonymous survey the choice is not linked to the person, and results with fewer than 3 votes and the participant list are not shown. In an anonymous wish or complaint the name is not stored; the employee sees the reply with the tracking code kept on that device. This channel is separate from discipline and absence processes. The payslip is the employee’s own row of the GROSS summary on the Payroll tab; it does not include social security or tax deductions.
6j. Onboarding and exit checklist — documents, assigned items, access, training, mentor, release
On Personnel › Onboarding / Exit, HR opens a checklist for every new or leaving employee: the Open checklist wizard has three steps (person and process · date, mentor and role · preview and open). Items come from the Template; an item can apply only to a given department or job title. Each item has an owner (HR, supervisor, the employee, system administrator), a due date (days from the start or exit date) and a status; supervisor items go to the effective supervisor from the organisation chart, who gets an in-app message. The board shows open checklists, progress percentage, overdue items and items assigned to you.
Evidence. Items the system can verify close automatically with Check evidence: when no assigned items or PPE needing return remain (6b), when the job’s mandatory PPE has been issued, when the mandatory trainings in the training matrix are valid (6c), when the person’s system user exists, when the portal account is open or closed, when a mentor is assigned and when a first 10 days plan exists. The First 10 days plan button links the person’s existing plan or creates one from the role template — a second plan is never created. Personnel documents (ID, diploma, medical report, contract) are uploaded to the item’s Attachments or an evidence note is written. Closing a required item as Not applicable is reserved for the HR manager and needs a reason. Every change is version-checked: two people cannot change the same item at the same time.
Exit. Revoke access (HR manager or system administrator) blocks the person’s sign-in and immediately ends their open sessions; the user is not deleted and can be restored on rehire from Settings › Revoked system access, with a reason. The checklist detail shows the payroll engine’s severance / notice pay estimate; when the final pay item is completed this estimate is kept as evidence. Release draft generates a PDF with the company, the person and the estimate and attaches it to the item; the draft is marked “NOT OFFICIAL” and must not be used before your lawyer reviews it — upload the signed copy as an attachment. Assigned items and PPE are taken back with the return wizard in 6b; the last return closes the item automatically.
Period gate. While an open exit checklist has an unfinished required item, the employment period cannot be closed: the exit summary and period closing show the same block (“required item not completed”). When unavoidable, only the HR manager can override by writing a reason, which is kept permanently. If Settings has “Do not allow closing an employment period without an exit checklist” switched on, an exit without any checklist is blocked as well. A checklist can be cancelled (HR manager only, with a reason); records are never deleted and numbers are never reused.
Portal and phone. Employees see their own checklist read-only on the My onboarding / exit checklist tab of the employee portal: progress, due dates and the items expected from them — evidence, reasons and owner names are not sent to the portal. On a phone (Garden / Step) the board and items open as cards, and opening and marking a checklist open as full-screen wizards. The checklist from the old Discipline / Exit tab has moved here; old items already marked are linked when a new checklist is opened.
6k. Recruitment funnel — job postings, candidate pool, interviews, job offers, hire
Open job postings in Personnel › Recruitment. If you pick a vacancy from Organisation › Headcount, the position, department and headcount come from it and the vacancy is linked to the posting; otherwise the position is optional. A posting is internal (employees only), external or both. It starts as a draft; Publish takes applications, Put on hold pauses it and Close posting ends it. A cancelled posting releases its vacancy; no record is ever deleted.
Candidate pool: the Add candidate wizard has three steps (identity → contact and data consent → posting and save). For external candidates the personal data consent date is mandatory (can be switched off in Settings); if the deletion date is left blank it becomes the consent date + retention period (12 months by default). A second candidate with the same email or phone is refused. CVs and documents are visible to HR roles only. Candidates past their deletion date appear under the Past deletion date filter; the HR manager uses Delete personal data to erase name, contact details, notes and CV files (not possible while an application is open or hired).
Funnel: applications appear in the columns New application → Screening → Interview → Job offer → Offer accepted → Started work (stage buttons on phones). In an application, the next-stage button moves it one step; an optional 1–5 score and evaluation note go into the stage history. Move back a stage requires a reason, and there is no way back from Started work. Reject asks for a rejection reason; scheduled interviews are cancelled and an open offer is withdrawn. A rejected or withdrawn application continues from its stage with Reopen. If two people change the same card at once, the second save is refused.
Interviews: Schedule interview asks for date and time, duration, type (in person, video, phone), location or link and the interviewer; it is not saved if the same interviewer has an overlapping interview. The interviewer gets a message and the interview appears in the company calendar as their item. Even without an HR role, the interviewer sees only their own interviews under Personnel › Recruitment › My interviews and fills in the scorecard: five criteria (communication skills, technical competence, relevant experience, team and culture fit, motivation) scored 1–5, a recommendation (hire / undecided / do not hire) and a note. The application score is the average of completed interviews; interviews cannot be scored before their date.
Job offer and hiring: Prepare job offer asks for the monthly gross salary, currency, start date, grade and the end of validity. If the position has a salary band, the offer's place in the band is shown; an out-of-band offer is saved but needs a reason. An application can have only one open offer at a time. Submit for Approval also sends the offer to Management › Approvals; the approver must be an HR manager or administrator other than the sender. The candidate's answer is recorded on an approved offer; if they accept, the application moves to Offer accepted. Hire (HR manager only) takes the employee number and start date and, in one step, opens the employee card with the candidate's details (an internal candidate keeps their existing card), records the contract with the offered salary, assigns the person to the posting's position as primary holder and starts the onboarding checklist. If one of these steps cannot be written, hiring does not stop and the step is shown as a warning. When every opening of the posting is filled, the posting and its linked vacancy close; a second hire request for the same candidate is rejected.
Report, settings and internal postings: The funnel report shows, for the chosen date range (and optionally one posting), stage conversion (how many applications reached each stage and the rate), source effectiveness (applications, interviews, offers, hires and conversion by source), rejection reasons and the average time from application or from posting opening to start. In Recruitment settings the HR manager sets how long candidate personal data is kept (1–120 months) and whether a consent date is required for external candidates. Published internal and mixed postings appear on the staff portal under Internal postings; an employee applies with one tap, the application enters the funnel as an internal application and the employee follows its stage in the portal.
Job offer rules. The monthly gross salary can be at most 999.999.999.999; when exceeded the field turns red, Save becomes disabled and the reason is written under it (the server returns 422 TUTAR_SINIR_ASIMI; the contract gross and net pay are on the same limit). An HR user who is not the HR Manager also sees the Approve button but it is disabled and says “The HR Manager or a manager approves the job offer.”; for the person who sent the offer the four-eyes reason (someone else must approve) is written under the button. In Hire, if the registration number is empty the button is disabled; the reason shows both under the field and under the button.
6l. Subcontractor and daily workers — document set, site access, payments
People whose employment type on the employee card is Contractor or Daily worker are tracked in Employees › Contractor. A subcontractor worker is linked to the subcontractor company card through the subcontractor account code on the card: account, contract number and term, rate basis (hour or day), unit rate, overtime multiplier, the service card used on the purchase invoice and the cost center. Subcontractor and daily workers are not on payroll — without a pay contract they do not appear in the payroll summary; their hours go into payments and the daily pay list.
The document set comes from the country package. Türkiye: subcontracting agreement, SGK subcontractor registration, the monthly MPHB service list and wage payment proof (Labour Act 4857 art. 36: the principal employer checks subcontractor wage payments every month), and the SGK employment start notification for each person. Indonesia: alih daya agreement, Perizinan Berusaha / NIB, monthly BPJS contribution proof, and BPJS Ketenagakerjaan and BPJS Kesehatan registration for each person. The Upload document wizard first creates the record and then attaches the file (with the camera on a phone); a document without a file does not count. A monthly document is required after a set day of the following month (TR 26, ID 15 — the values and sources are under HR › Regulations); the list of mandatory documents is changed in Settings.
Site access permission is granted to a person for everywhere or for a plant, warehouse, work center or station. The person may enter only if the subcontractor company card and contract are valid, mandatory documents have files and are in date, mandatory training (Training tab) and mandatory PPE issue (Assigned items / PPE tab) are complete and there is a permission for that location. The Site status view lists every missing item and upcoming document dates; the Site access check wizard (also on the phone) checks one person for one location without writing anything.
Gate: for clock-in (phone, Nabız, employee portal), production terminal login and the shift plan, choose Off, Warn or Block separately. With Warn the entry is written and a warning trail is kept; with Block the entry of a person with missing requirements is not recorded and the person cannot be assigned in the shift plan. The HR manager can give a temporary access pass of up to 24 hours with a justification; the pass, issuer and justification are recorded. Payroll staff are not affected by the gate; manual clock corrections are outside the gate.
Payments: pick a period (at most 3 months); hours come from the timesheet (closed days) or, for days not yet closed, from clock-in/out records (breaks not deducted). On an hourly basis the amount is hours × unit rate + overtime × unit rate × multiplier; on a daily basis worked days × daily rate. A personal rate overrides the company rate, and a new rate closes the old one on the day before. The payment opens as a draft and must be approved by an HR manager other than its creator (four-eyes); a subcontractor payment is then linked to a purchase invoice (service card, one line) and a daily pay list to an expense entry. A second payment cannot be opened for the same period and a linked payment cannot be cancelled. In Indonesia, a warning appears when a daily worker works 21 days or more in each of 3 consecutive months (PP 35/2021 art. 10), because the contract becomes permanent. Approved payments enter HR analytics (Analysis Studio, ik-kadro cube) as a subcontractor line in labour cost.
6m. Digital personnel file and personal data (KVKK / UU PDP) — documents, retention, access log, requests
Personnel › Personnel file › Personnel file status shows the documents required from each employee and what is missing. The list comes from the country package (TR: ID, residence, employment contract, SGK start notification, health report, OHS training; ID: KTP, BPJS, PKWT, health certificate; a work permit for foreigners) and is extended by role, department or employment type under Document rules. Upload a document from the person panel or link one of the person’s existing files (no copy is made); a record without a file does not count. Subcontractor documents and training records also count as evidence. Expiry dates are reminded in the company calendar; the onboarding checklist’s document items close from here with “Check evidence”.
Retention periods run from the exit date and are shown with their official source — TR personnel file 10 years (TBK art.146), SGK and payroll records 10 years from the start of the following year (5510 art.86/2), health and OHS records 15 years (OHS Services Regulation art.7); ID tax documents 10 years (UU KUP art.28/11), others 10 years marked “secondary source”. Former employees, document files and recruitment candidates past their period are only SUGGESTED; when the HR manager approves with a reason, the employee row is kept, personal fields are masked and files are destroyed; for a candidate the recruitment module’s own deletion runs. A person with an open employment period or an open portal account cannot be anonymised.
Access log: every view of the employee card, personnel file, personnel document file, signed archive and a single-person payroll is recorded with user and time (read-only users included). In the Access log view, filter by user, record type and date range; the summary at the top shows who viewed how many people. In the employee portal’s My data page, the employee sees who viewed their file in the last 12 months; their own views are not logged. Showing names in the portal can be switched off in the settings.
Requests and privacy notice: data subject requests (information, correction, erasure, objection, withdrawal of consent, restriction, portability) are recorded from the portal or the Requests view; the reply deadline comes from the country package — TR 30 days (KVKK art.13/2), ID 3 × 24 hours (UU PDP art.30, 32, 40, 41; erasure and objection marked “secondary source”). Overdue requests appear in red and a reply is recorded only once. The privacy notice is versioned: the HR manager prepares and publishes the draft; the employee clicks “I have read it” in the portal or HR marks it as read on paper; a new version asks for reading again.
The data inventory produces the VERBİS columns (data category, special category, fields, purpose, legal basis, recipient groups, retention period, number of people and documents recorded) for employees and downloads as CSV. The signed archive, created with “Create signed archive” in the person panel, collects the person’s document list and the SHA-256 hashes of their files into a manifest, signs it with the application’s signing key (CMS) and stores it together with a PDF. “Verify” compares the signature, the manifest hash and today’s file hashes; files changed or cancelled after archiving are shown. NOT OFFICIAL — it is not a qualified electronic signature.
On a phone (Garden / Step interface) the personnel file status appears as cards; tap a person and, for a missing document, “Upload” opens a three-step wizard: type → number and dates → file (photo with the camera). Retention, access log and requests open full screen with the same views; touch targets are at least 44 pixels.
6n. Single personnel source — production staff and Work Center operators from the HR record
The same employee is now defined in one place: the HR record. When “Production staff” is ticked and an hourly / piece rate is entered in the Production box of the personnel record, the person appears in Production › Personnel and in the work order confirmation staff list from the HR record; if “Work Center operator resource” is ticked too, an operator resource is created (code OP- plus employee no.). Name, employee no. and terminal PIN stay in HR: renaming in HR renames the production row, and an operator who signs in at the MES terminal with a PIN is matched to production staff through the HR record link.
When training results write competence (6d) and at the competence gate of work order confirmation (gate 13), the operator is found through the HR record link: an operator created from HR and an older operator linked to production staff count as the same person. For people previously entered with a free-text name in Production › Personnel, that screen suggests matches by first and last name; only a system administrator approves the link, and unmatched rows stay in the list.
6o. Portal count approvals
The Personnel › Portal count approvals tab is where depot count entries from the personnel portal are approved. The list shows “Pending count drafts” with a warehouse filter (All warehouses); Refresh reloads the list and approve all gives a bulk approval. A count from the portal does not change stock: when you approve it a real count slip is issued (“Count slip issued” and the slip number) and the difference is posted to stock; if you reject it the draft is closed without touching stock. HR approvals such as leave, advance and job offer are not on this tab; they are on the Portal requests tab and in the Notification and Approval Centre.
6p. The Audit tab
The Personnel › Audit tab shows three things. (1) Expiring: records whose validity will end, or has ended, within the window you choose (within 30, 60, 90 or 180 days) are counted by source and listed with the columns Source, Employee, What, Validity, Days left; a negative number of days means it has expired (red). (2) Targets without an access rule (if any): targets that have no access rule defined and how many people can reach each. (3) Who looked at a sensitive record: with a person filter (All records) it shows, in the columns Time, User, Whose record and Field, who read sensitive personnel fields; if there is nothing it says “No read trail”.
7. Earnings — piece rate, commission, trips, vehicles
7.1 Piece rate
The tariff is kept per operation × product and is date-bound; after a rise, older records keep their old rate. Two rules are fixed: scrap is not paid (pay for parts that failed quality and the piece-rate system collapses) and no entitlement arises without quality approval.
Piece-rate earnings cannot fall below the minimum wage. The difference is topped up by the company and appears in a separate column of the summary — so that "piece rate" and "minimum top-up" are not confused on the payslip. The minimum wage is entered in the Legislation tab; if it has not been entered the top-up is not calculated. Producing nothing is right; producing an invented figure is not.
In Indonesia the minimum wage is not a single national figure: each regency/city sets its own UMK. The field is therefore a single number that the company fills in for its own region.
7.2 Commission — three stages
Commission is not paid in one step; it passes through three states:
-
Accrued — the sale was invoiced and the commission computed, but it is not yet earned.
-
Earned — the money was collected. This is the default rule: no commission is paid on an uncollected sale.
-
Clawback — goods were returned or payment failed. If the commission was not paid it is cancelled; if it was paid it is not deleted — it is marked as recoverable and appears as a deduction on the next payslip. The trail of a paid amount must not vanish.
A clawback cannot be made without a reason. If the reason field is empty the operation is rejected; six months later the answer to "what was this deduction?" must still be in the record.
7.3 Team commission
In some work the commission belongs to the team rather than the individual, and is then split by share. The shares need not add to 100 — a foreman may be given an extra share; the program prorates against the total. The rounding remainder is added to the largest share, so that the distributed total equals the amount given, exactly.
7.4 Trips, vehicles and fines
A trip is opened and closed on return; the number of days and the per-diem are computed automatically. A trip shorter than the threshold counts as half a day. Expenses (accommodation, meals) are attached to the trip and the payable is summed as per-diem + expenses + trip fee.
Vehicle custody answers "who is driving which vehicle". A vehicle can be with only one person at a time; it cannot be handed to another without being returned first. Fuel and odometer entries can be made by the driver from their own phone, but only for the vehicle assigned to them.
A fine that arrives against a plate does not automatically belong to the driver. If the driver has not been identified the program makes no deduction; the fine stays with the company. Even when identified, the deduction cannot exceed the share of wages set in legislation and is clipped to that ceiling. For damage, no deduction can be made until fault has been apportioned.
8. The personnel portal and the phone app
A worker on the floor has no program account, and does not need one. The portal uses a separate identity: employee number + PIN. HR opens the account (Portal accounts tab); if no user name is given the employee number is used — that is the one thing remembered on the floor.
What the portal can do: a shift punch (one button), a production report, a stock count entry, a leave request, vehicle odometer/fuel, and the person's own summary (leave balance, items in custody, expiring certificates). The address in a browser is /personel.
You no longer need to be a global system administrator for HR administration. The dedicated ik_muduru role can use portal accounts, entry/exit checklists, legislation, and other HR management actions inside Personnel. That opens HR administration without giving warehouse or production leads banking access.
You sign in to the portal with your employee number and PIN; the table on the Shift tab shows only your own week (Monday–Sunday) as day, shift name and hours. The table is a plan — it tells you what you are scheduled to do, not what you actually did.
8.1 First, signing in to the portal: employee number + PIN
The portal opens by adding /personel to the program's address in a browser — for example http://192.168.100.24:5173/personel. Two boxes appear: Employee no / username and PIN. This is not an HNR user: a person on the floor has no program account, HR issues them a separate portal identity. If no username was given, the employee number is used — that is the one thing remembered on the floor.
On an installation with more than one company the sign-in screen also has a Company code field. If you leave it empty you cannot sign in; a “Write the company code…” warning appears. The company code you entered earlier on this device is remembered and fills the field automatically. If the portal address HR gave you contains ?firma=, the field stays hidden. With a wrong code you see “Company code not found. Check the company code from the portal address given by your HR department.” On a single-company installation this field is not needed.
- A session lasts 8 hours and is refreshed on every use — one sign-in covers a whole shift. Even if the tablet sleeps or the browser closes, the PIN is not asked again.
- The address may carry
?firma=(e.g./personel?firma=hesap). In organisations running several companies, the link HR gives you carries this suffix; a short address you type yourself may look at the wrong company. Save the link exactly as HR sent it to your home screen. - You can change your own PIN — the portal's PIN change asks for the old PIN first. Five wrong PINs lock the user for 15 minutes; that lock lives in the program itself, so switching phones does not help.
8.1A If the portal account changed: 409 and refresh
A portal account can be opened by two HR users at the same time. The later save no longer silently overwrites the earlier one. If another person changes that account's PIN, active flag, or role after you opened the list, you receive a 409 / record changed warning when saving.
- This warning is protection, not failure. Refresh the list first; the new version, active flag, and role appear on screen.
- Then enter only the change you truly want to make. Resetting a PIN no longer changes the active flag or role by accident.
8.2 What is on the Shift tab?
The tab has three cards, in a deliberate order: first what to do now, then what you did today, and last what you will do this week.
| Card | What it shows | When you look at it |
|---|---|---|
| The PUNCH button | One big button; it looks at your last punch and sets itself to in or out | At the start and end of a shift |
| My punches today | The in/out times actually stamped today — the past, the record | When you doubt "did I punch this morning?" |
| My weekly shift plan | Monday–Sunday: day, shift name, hours — the future, the plan | When you ask "what time do I come in tomorrow?" |
8.3 Reading the plan table
Above the table the week's range is written (e.g. 17.08.2026 → 23.08.2026). There are three columns:
| Column | What is in it | What an empty cell means |
|---|---|---|
| Day | The day name (Monday…) with the date underneath | Never empty; if there is a row there is a day |
| Shift | The shift name (Day, Night…); the shift code if there is no name. A status badge may sit beside it and the supervisor's note underneath | A "—" means no shift was written into the plan for that day |
| Hours | A range such as 08:00–16:00; it comes from the shift card, not from the plan | A "—" means no hours are defined on the shift card — tell HR |
- Today's row is highlighted with a dark blue background — your eye lands there when you open the phone.
- An amber badge next to the shift name means that day departs from the normal plan (leave, swap, overtime… — the badge text is the status HR entered). With no badge the day is simply "planned".
- If the range line ends with "· period locked", HR has closed that month's plan and it will not change any more. If it is not locked the plan can still be updated — which is why a second look in the evening pays off.
8.4 The plan and the punch history are not the same thing
Because the two tables sit next to each other they get confused. The difference is both legal and practical: a plan is an intention, a punch is evidence. Your attendance, your overtime and your pay are computed from the punch, not from the plan.
| My weekly shift plan | My punches today | |
|---|---|---|
| Who writes it | HR / the shift supervisor, from the monthly plan | You — the moment you press PUNCH |
| What it tells | What you are expected to do | What you actually did — with the time |
| Span | This week: Monday → Sunday | Today only (older ones are on the History tab) |
| Can it change | Yes — HR can change it until the period is locked | No — a punch stays as stamped; corrections are the supervisor's job |
| Effect on pay | None — a plan alone does not produce pay | Yes — attendance and overtime are derived from it |
Appearing on the day shift in the plan does not mean you worked that day. If you do not punch, the day stays empty in attendance and fixing it needs your supervisor's manual intervention. The rule is simple: read the plan, press the punch.
8.5 Step by step: "Which shift am I on tomorrow?"
- Open the portal in the phone's browser (tap the icon if you added a home-screen shortcut). If your session is still open you go straight in; otherwise employee number + PIN.
- Tap the Shift tab. The plan table is fetched again every time you enter the tab — so what you see is always the latest plan; you do not need to reload the page.
- Scroll down to the My weekly shift plan card. The highlighted row is today; the row below it is tomorrow. Read the shift name and the hours.
- If tomorrow's row carries an amber badge, read its text — a special status was entered for that day (leave, swap…). Small text under the shift cell is the supervisor's note.
- If you ask the same question on a Sunday, the answer is not in the table: it shows only the week you are in, and Monday opens as a new week. Ask your supervisor about next week.
8.6 The shift plan — frequently asked
The table says "no plan entered for this week".
This is not an error; no row has been written for you yet for that week. The cause is usually one of two: the plan has not been prepared, or it was entered against a different employee number than yours. Ask your supervisor whether this week's plan has been entered — on the HR side it is visible at a glance from the Shift plan screen.
The shift name shows but the hours are "—".
The hours do not come from the plan but from the shift card. If no start/end minute is defined on the card, the portal does not invent one — it honestly shows "—". The fix is on the HR side: enter the hours on that shift card and they appear the next time the table is read. Your plan row is unaffected.
Can I look at a colleague's plan?
No — and that is deliberate. When the portal asks for the plan it reads the employee number not from your phone but from the session you obtained at sign-in. There is no way to ask for another employee number by fiddling with the address; whatever the request says, the server uses the number in its own record. The same protection covers punches, leave requests and vehicle entries.
Does the plan slip a day on the night shift?
No. The week boundaries and the "today" highlight are computed with the server's local calendar — done deliberately so a date does not slip back a day on shifts that cross midnight. If you open the table at 23:00, the highlighted row is still that day's row.
The portal will not open / it says "session required".
"Session required" means the 8-hour window has expired: sign in again with employee number + PIN, nothing is lost. If the page does not open at all the problem is almost always the network — are the phone and the server on the same network, is the address right (http:// and the port), is a firewall blocking it. The third is the most common cause and your system administrator holds the fix.
The portal creates no stock movement. A production report is not a confirmation: stock does not move and the work order does not close. A count entry is a draft: when the warehouse supervisor approves it, the real count slip is issued and the difference is posted. The reason is simple — the tablet in the workshop is unattended, and letting a wrong figure hit inventory instantly would require a correcting movement afterwards.
This is why the Personnel window has an Approvals tab. Count drafts sit there beside the book quantity with the difference shown; approving them issues the slip. Pending production reports are counted on the same screen.
The phone apps use the same endpoints; there is no separate interface. No shared key is kept on the device — the only secret is the person's PIN. After five wrong attempts the account locks briefly, and the lock is per person: on a shared terminal one person's mistake does not lock everyone else out.
Portal PIN rule and lock. A portal PIN must be 4–6 digits; a repeated digit (0000) and consecutive digits (1234, 4321) are refused (“Open account / Reset PIN” under Personnel › Portal accounts gives the same sentence). 5 wrong attempts per user name lock it for 15 minutes; a wrong old PIN typed while changing the PIN is counted too. The sentence does not reveal whether the account exists. The HR team opens the lock with Unlock on the same screen. When the PIN or role changes, or the account is closed or locked, that person’s open portal sessions are closed; a portal session lives at most 24 hours.
9. Defence pack — stamps, signature authority, access
This pack is optional; without it the module works exactly the same. It exists for firms that make parts for defence or aviation.
A quality stamp is a physical item in custody: its number, who holds it and when it was issued are recorded. One stamp cannot be with two people at once. A lost stamp is cancelled, and cancellation cannot be undone: that number is never issued again, because every part struck with it must remain traceable and a new holder would muddle the trail.
Signature authority is tied to a subject and an amount. The critical distinction: some authorities cannot be delegated. Saying "the manager is on leave, let the deputy sign" would, for qualification-bound authorities such as quality release or first-article approval, defeat the very purpose of this pack. The program refuses such a delegation. For delegable authorities the deputy's limit cannot exceed the grantor's — it is clipped automatically if asked for more.
Project access can be tied to a security clearance and a signed confidentiality undertaking. Where a rule is defined the program does not grant access; this is a refusal, not a warning. Clearance is hierarchical: someone cleared to "secret" cannot enter a project requiring "top secret". Where no rule is defined nothing is blocked.
10. Discipline and exit
No disciplinary decision can be recorded without a defence. This is a block, not a warning; a penalty without a defence is procedurally void and will not stand in court. The flow is: record the incident → request the defence → receive the defence → decide. If the defence does not arrive in time, that fact is minuted and the decision is recorded on that basis.
For repeated incidents of the same kind the step rises automatically (verbal warning → written warning → deduction → dismissal). You need not enter the step by hand; the program counts it from earlier records.
10.1 Clearing an employee out
On exit a checklist is opened: stamp return, cash/cheque/receipt-book custody, vehicle keys, closing system and project access, card cancellation, closing the portal account, portfolio handover, settling remaining leave, the release document. Until the mandatory items are ticked the window does not say "clear to leave".
The right-hand panel of the person card also carries a clearance summary: open custody, open stamps, open access, assigned vehicles, leave balance and unpaid commission are visible at a glance. Look here before you sit down for the exit interview.
11. Record forms and attachments
The Personnel module is no longer just a list-and-decision screen. Its record forms now cover the person's optional fields, employment period, shift and rotation definitions, raw-punch linkage, access and defence pack, legislation choice, premium and piece-rate data, plus leave, HSE, PPE, and entry-exit attachments.
Note: no fresh HR-form PNG was captured for this update. This existing screen is the closest real image showing the shared attachment panel's metadata, security-class, and file-identity behaviour.
| Form group | Coverage |
|---|---|
| Personnel and period | Covers all optional identity fields, employment type, start-end dates, rehire, card number, and portal linkage. |
| Shift and punch | Shift cards, rotation patterns, attendance periods, raw punches, and correction trails are kept as one process. |
| Access, defence, legislation | Stamps, signature authority, system/project access, the discipline-defence flow, and country-based legislation selection all attach to the same personnel record. |
| Premium, piece rate, leave, HSE, PPE, and exit | Premium and piece-rate records, plus leave, HSE incidents, PPE delivery, and entry-exit checklists can now attach evidence files through the shared panel. |
11.1 Shift and pattern setup — before attendance
A shift card defines working hours; a pattern defines their day-by-day repetition. The HR manager first opens Time → Shifts and records the shift code, name, start, finish, and night/day-overrun status. Then, under Patterns, the manager sequences the shift codes and uses X for a rest day.
- Save the hours for day/office, morning, evening, and night shifts. If the night shift ends the next day, verify day overrun.
- For example, create G,G,G,G,G,X,X for office staff and S,S,A,A,N,N,X,X for three-shift production. Use only registered shift codes; X means a day off and is not a shift code.
- Apply the pattern to one test employee with a start date. If the eight-day plan is correct, apply it to the team in bulk.
- Check the weekly plan and employee portal. “—” hours mean an incomplete shift card; no shift name means the pattern or plan was not applied.
- Open attendance only after these checks. Do not delete a historical plan; record the change with a new effective date.
For shifts/patterns, troubleshooting, and the common record sequence across modules, see the Practical User Handbook.
A frozen attachment never changes silently. If an entry-exit checklist, HSE incident, or defence letter has been tied into a frozen file, upload a new revision instead of overwriting it. The shared panel accepts multi-upload, but not cancellation without reason; the file is not deleted, it is retired with a stated reason.
12. Dashboard — today at a glance
The dashboard answers three questions: how does headcount stand (active people, joiners, leavers, turnover), what is waiting (leave requests, production reports, count drafts, expiring certificates, open discipline) and where is the risk (accidents, lost days, single-point risk).
Turnover is the number of leavers over the active headcount. If headcount is zero it is not computed and "—" is shown; saying it cannot be computed is right, inventing a figure by dividing by zero is not.
HR indicators. The strip above the Dashboard tab opens the HR indicators dashboard (Analysis Studio) and the HR indicators report (Reports): headcount trend, employee turnover rate, absence and overtime rates, labor cost as a share of net sales. The turnover rate there divides the period's exits by the average headcount; the turnover on this Dashboard divides this year's leavers by today's active headcount, so the two figures can differ. Details: Analysis Studio — HR dashboard.
13. Common mistakes
-
Opening a personnel card but no employment period. The card alone does not make someone an employee; a person without a period is not counted in headcount and cannot sign in to the portal.
-
Expecting portal punches without entering a card number. Punches attach to the card number; a person without one cannot punch. The error message says so.
-
Expecting the piece-rate guarantee without entering the minimum wage. If the minimum wage is 0 in Legislation, no top-up is computed — this is not a fault but a decision not to invent a figure.
-
Forgetting to approve a count draft. Stock does not change merely because someone on the floor entered a count. If rows are waiting in the Approvals tab, your inventory has not been updated yet.
-
Leaving a departed employee's portal account open. The exit summary counts this as a blocker. Someone without an active employment period cannot sign in anyway, but closing the account is an item on the list.
For production confirmation and work orders see the Production guide, for stock counts and movements the Warehouse guide, and for approval thresholds the Cockpit guide.
14. Record forms › "Bulk staff import (CSV / list)" and the "Hire date" field
Entering a fifty-person shift by opening personnel cards one by one meant opening an employment period for each card too — a hundred operations. Two conveniences arrived. (1) "Hire date (opens the period too)": fill this field on the personnel card and the card and the employment period are opened in the same operation; if the period cannot be opened (e.g. an open period already exists) the card is not written either — no half records. (2) The "Bulk staff import (CSV / list)" card: paste a list copied from Excel, give a common hire date, press Upload.
- HR › Record forms › open the "Bulk staff import (CSV / list)" card.
- Paste the rows. The separator may be
;,,or tab. A header row is optional; without one the fixed order is expected:sicilno;ad;soyad;istihdam_tipi;giris;departman_kod;gorev_kod;telefon. - Optionally give a common hire date (used when a row has no giris). Press Upload.
- The result arrives row by row: sequence no, period no or an error text. If one row fails the others are still written — partial success is normal; fix the failed rows and upload only those again.
Permission: the HR manager role or system administrator. Limits and messages: a personnel number that appears twice in the same list is refused with "SICIL_TEKRAR" before reaching the database; an already registered number gives "personnel number already in use" (409); more than 500 rows gives 413 — split the list; if every row fails, 422. About 400 rows per upload is the practical ceiling.
15. Portal lock: the login throttle counts only wrong PINs, the lock opens without waiting
The "personnel number + PIN" login of section 8.1 has two protections, and neither locks up a shift change any more:
| Protection | When it kicks in | How it clears |
|---|---|---|
| IP throttle (429 "Too many attempts — wait 1 minute") | Many wrong PINs from the same network address in a short time. Correct logins do not count — fifty people logging in correctly from the same factory network do not trigger it (they used to). | By itself, after a minute. |
| Account lock | 5 wrong PINs for the same personnel number → 15-minute lock ("account locked, wait until …"). | By itself after 15 minutes — or immediately by an HR manager via "Unlock": the failed-attempt counter is reset, the lock end is cleared, the action is logged. The button appears in Personnel › Portal accounts, at the right of a locked row (or one with failed attempts); the endpoint underneath is POST /api/ik/portal/kullanicilar/<seq>/kilit-ac. The old "change the PIN" route keeps working too. |
Five plants sharing one portal account means one person's wrong PIN locks everyone. Every employee should have their own personnel number and PIN; the portal account is created against the personnel number in HR › Portal accounts (role: operator). Lock and throttle counters are per personnel number.
15.1 Finding the right account in a crowded list
Do not scan a hundred-plus portal accounts by eye. Above the Personnel › Portal accounts table there is a search box (user name, personnel number or full name) and a "locked only" filter. Tick the filter first: the list narrows to rows that are locked or carry failed attempts — and the "Unlock" button only ever appears on those rows.
16. Garnishment files and the period deduction
Garnishment files live in the Garnishment files card at the bottom of Personnel › Earnings. Opening a file needs the personnel number, the type (garnishment or alimony), the file number, the principal amount and the service date — the queue is built from that date, which is why it is mandatory.
16.1 Queue and the legal ceiling
The Calculate period deduction button runs this order: (1) alimony files come first and sit outside the ceiling; (2) the remaining files are ordered by service date and sequence number, and no file is started before the previous one is cleared; (3) the total garnishment may not exceed the kesinti.icra_azami_oran percentage of the net wage (25% in the Turkish set). That rate is a parameter — there is no hard-coded number; change it under Legislation.
16.2 No net wage means no deduction
The deduction sits on the net wage. If the contract carries no approved net figure the program will not invent a gross-based garnishment: the person is flagged NET_UCRET_YOK and no deduction is produced. The fix is to enter the net amount on the contract.
16.3 Preview and write are two separate steps
Calculate period deduction (preview) writes nothing; it shows, with a reason per file, how much would be taken. Write posts the deductions to the ledger, reduces the file balances and closes a file that is fully paid. Running the same period twice does not double-deduct — what is already in the ledger is subtracted.
17. The Payroll tab — summary, bank list, social-security data
Personnel › Payroll has three sub-views: Summary (earnings and deductions per person), Bank list (amount payable + account) and Social-security data. All three offer Download CSV at the top right.
17.1 This summary is GROSS
The amber band at the top is there for a reason: in this version social-security and income-tax deductions are NOT calculated. The summary totals items that each module already calculated and approved (base wage, piece rate, commission, overtime, per-diem, advances, vehicle deductions, garnishment). For net pay, subtract the deductions from your statutory payroll program; the bank list is not a payment order.
17.2 "Not calculated" rows and the payment list
A person with an open garnishment file whose period deduction has not been calculated yet shows a red Not calculated badge; the Garnishment and Payable columns become a dash and the row is kept out of the bank list — it never reaches a payment order and is listed with its reason under "Excluded from the payment list". This case used to bring down the whole summary; now it only marks that row. Fix: write the period deduction from the Garnishment card on the Earnings tab.
17.3 Bank list: checksum and suspicious accounts
The bank list gives the record count, the total in minor units and a SHA-256 digest of the rows; compare the file you send to the bank against those three values. A row whose IBAN check digits fail gets a red Suspicious badge (in countries without IBAN, purely numeric accounts are not checked this way). The bank's own fixed-width file schema is not produced here — it varies per bank and version and is never invented; you get CSV, and mapping is a separate job.
17.4 Social-security data: occupation code and dominant absence reason
The declaration data now also carries the person's occupation code (a field on the personnel card); missing ones are counted. When a person has several absence reasons the institution wants one: the program picks the reason with the most days, breaks ties by the sgk.eksik_gun_oncelik order and states its choice on the row — it never decides silently. Mapping a reason to an official code lives in sgk.eksik_gun_kod; with no mapping no code is produced and the row says so. The official e-declaration file is not generated here — what is produced is the data it rests on.
17.5 Net payroll (Türkiye) — SGK, income tax, stamp tax, net pay
When the Türkiye legislation set is active, the Payroll summary tab gets a Net payroll sub-tab. It adds the statutory deductions on top of the gross summary (contract gross + piecework + bonus + overtime): SGK employee contribution and unemployment insurance, income tax (bracket by the cumulative base of the year), stamp tax, the income and stamp tax exemption on the minimum-wage portion and the disability allowance; it then subtracts the summary's advance / garnishment / vehicle deductions and shows net pay and the total employer cost. Travel allowances and expense refunds are outside the SGK and tax bases. The tab does not appear in the Indonesian set; Indonesian payroll is unchanged. This calculation is informational; it does not replace the official payroll or tax return.
Mid-month joiners/leavers (pro rata) and the accounting voucher: if an employee worked only part of the month, the monthly gross wage is calculated by the share of days in the service period, and the social-security day count follows calendar days; bonuses and overtime are taken in full. The finalised net payroll becomes the month's voucher as a Payroll accrual in accounting automation: gross wage and employer share are debited to expense account 770; social-security premiums payable 361, income and stamp tax 360, net wage 335 and advances offset from payroll 196 are credited. The account mapping can be changed in the accounting rules.
In a period whose net payroll is finalised, the My payslip page in the staff portal shows the statutory deductions (employee social security share, unemployment insurance, income tax and stamp duty) and the net payable from the line finalised by HR; the slip states that it is the net payroll. In a period not yet finalised the gross summary is shown.
The link between a system user and an HR employee record is a single field: Settings › Users › HR employee record selector, or Personnel › Record forms › System user name. The link appears as a badge in the Personnel list and as "System user" in the side panel. The employee portal also opens, in companies set up with the wizard, at the address given by the HR screen; the portal uses the language you chose in the main system.
Order of calculation: SGK base = earnings, limited between the monthly floor and ceiling (days/30 in a partial month) · SGK employee = base × (pension + health employee rates) · unemployment employee = base × rate · income tax base = earnings − SGK employee − unemployment employee − disability allowance · income tax = tariff(previous months + this month) − tariff(previous months) · exemption = the minimum wage's cumulative tax for the same month · stamp tax = earnings × per mille − gross minimum wage × per mille. Every number (minimum wage, floor/ceiling, rates, incentive points, tariff, stamp rate, disability amounts) is a year-keyed parameter in the Türkiye legislation package and is shown with its official basis (Official Gazette date/number, article, communiqué) under Parameters and sources; change it in Legislation › Parameters. If the new year's value is missing, the calculation does not silently produce zero; it stops and lists the missing keys. The minimum living allowance (AGİ) has not existed since 2022.
Finalization: the HR manager opens a three-step wizard with Finalize period (Check → Summary → Approval; full screen on a phone). The rows of the finalized month are stored, and the cumulative tax base of later months is read from them. Months are finalized in order (409 if the previous month is open); if the calculation you saw changed before saving, the save is rejected. Undo is possible only for the last finalized month of the year and needs a reason; rows are not deleted but marked cancelled. If earlier months are not finalized, the cumulative base is estimated from those months' summaries and the row shows an "Estimated" badge. For someone who joined mid-year from another employer or an old payroll program, enter the last month and cumulative base under Carried-over tax base; months up to it are not estimated. The SGK contribution incentive (non-manufacturing / manufacturing) is a company choice and only affects employer cost; the default is "No incentive applied".
Payslip and export: the Payslip button on each row downloads the person's payslip as a PDF (earnings, statutory deductions, employer shares, cumulative base and bracket); the PDF begins with a "NOT OFFICIAL" notice. Withholding return data (CSV) gives SGK days, SGK base, income tax base, calculated tax, exemption, income tax and stamp tax per person — for manual entry into the withholding and premium service return; no official return file is produced. Out of scope (this version): rates for working pensioners (SGDP), day reductions by absence reason (days are taken as 30 except in the entry/exit month), carrying earnings above the ceiling into later months, person-level conditions of the various incentives, special allowances other than the disability report. In these cases use the amounts from your official payroll program.
The final period in net payroll. The note “cumulative tax base was estimated because earlier months were not finalised” counts only non-finalised months and only the people in this period’s payroll. If the period is final and a person was not included in net payroll in that month (e.g. unpaid that month), that month is not estimated, the base stays 0; the final period does not change. The My payslip page in the staff portal lists the periods HR has finalised in addition to the last 12 months and by default opens the newest final period; the slip of a finalised period can be requested even if it is older than 24 months.
18. Shuttle service — routes, stops, boarding list, contractor billing
The Shuttle view under Personnel › Shuttle / Canteen / Union holds contractor vehicles, their stops and the staff riding them. A route must carry a capacity; the occupancy percentage comes from it. This is not staff travel (per-diem) — that lives in the Trip records on the Earnings tab.
18.1 Capacity is a gate, not a warning
Adding a rider to a full vehicle is refused (SERVIS_KAPASITE_DOLU). If you knowingly need to record an overloaded run, assign with kapasiteOnay; the record then goes through but a CAPACITY EXCEEDED warning stays in the response and on the route list.
18.2 Billing and lateness
The number of runs is never invented: it is the count of distinct days on which staff assigned to that route actually worked according to the timesheet (the vehicle ran that day). The amount is that count × the run fee. Lateness is only flagged in this version; the program does not apply the penalty clause of the contractor agreement on its own — a human decides and posts the deduction.
19. Canteen — card taps, entitlement checks, catering reconciliation
Each meal is defined by a code, a time window and a unit cost. On a tap the program tries three gates in order and, when it refuses, says why: KART_TANIMSIZ if the card belongs to nobody, MUKERRER_BASIM for a second tap on the same meal, IZINLI_GUN if the person is on approved leave or sick that day, DAMGA_YOK if there is no entry stamp at all.
19.1 Reconciling the catering invoice
Reconciliation counts only accepted taps; a refused card never enters the amount. Enter the contractor's invoice count and total and the program shows both differences. Diet/allergen information comes from the diet code field on the personnel card and is returned with the tap so the kitchen screen can show it.
20. Union and collective agreement
A union is defined by a code, a name and a dues type: daily (dues = daily gross × number of days), rate (a percentage of gross) or fixed. The default number of days is the sendika.aidat_yevmiye parameter — no hard-coded figure.
20.1 Union leave is a paid day
A timesheet day with status sendikal_izin counts as a paid day and enters the social-security premium days; it is not reported as an absence. A representative's weekly leave hours are kept on the membership record. The dues list is grouped per union and can be exported as CSV; it does not create a payment instruction.
21. Social-security declaration (MPHB) — worksheet, workplace record, XML package
The Social-security declaration tab in the Payroll window gathers everything the month-end declaration rests on in one place: premium days, earned wage, bonus/premium, missing days and their reason, start/leave dates and the occupation code per person. This is a review screen — it produces no file, it counts what is missing.
Scope — this is half a declaration. MPHB combines two filings: withholding tax and social-security contributions. Because HNR does not compute income-tax withholding, only the social-security part is produced; the tax fields are left out and not filled with 0 — writing 0 produces a filing the agency will reject. Complete the tax part from your accountant's software before submitting.
The workplace record is mandatory. The declaration wants the 26-digit workplace registration number split into parts. Type the number into one field and press "Parse the number": the new unit, old unit, workplace sequence, province code and subcontractor code are derived from the character ranges in the official guide. The positions of the industry, district and check numbers are not published, so they are not derived — you enter them by hand. If a part you typed contradicts the parsed one the save stops and names the conflicting part; there is no silent correction.
Occupation code (NNNN.NN). The agency wants a 4-digit ISCO-08 code plus a 2-digit sub-breakdown. HNR does not embed the 7,556-line occupation dictionary (copyright, freshness and maintenance cost); it validates the format only and offers two ways to set the code: the person card or the job tag. If you set it on the job tag, everyone in that job inherits it. A person without a code shows in red on the worksheet.
Why XML and the ZIP package are off by default. The agency's machine-readable schema (XSD) is not published and the format changed in the June/2026 period. So HNR does not invent a schema: you define the XML element names yourself on the Declaration schema tab (from your agency software's field names). While Settings › Safety gates › sgk.xml_uret is off, the worksheet and CSV work exactly as before and XML/package are refused. Turn the gate on after you have verified your definition matches your agency software. The package may be at most 15 MB per the guide; if it exceeds that, split the filing with the workplace filter.
A row whose mandatory field is empty is NOT written to the file. If a field you marked "mandatory" in the schema is empty for a person, that person's row does not enter the file and appears in the missing list with its reason. This is deliberate: an empty mandatory field means a filing the agency will reject; seeing the gap on screen beats seeing the rejection letter.
| What you see | Cause and remedy |
|---|---|
| The XML / ZIP buttons are missing | Either sgk.xml_uret is off or no schema is defined for this type. Define the schema first, then open the gate. |
| "SEMA_TANIMSIZ" | No definition exists. Save one on the Declaration schema tab using your agency software's field names — HNR does not invent a default. |
| "PAKET_BUYUK" | The compressed package exceeded 15 MB — the guide's limit. Take separate packages using the workplace filter. |
| A person is missing from the file | Two possibilities: the person is not attached to the selected workplace (check the "people" count on the workplace record) or a mandatory field is empty (check the missing list). |
22. Bank salary file — the template engine
Payroll › Bank file converts the bank payment list into the text layout your bank wants. The layout is not hard-coded, and there is a measured reason: no Turkish bank publishes its fixed-width TXT schema; the only official document published is Ziraat's Excel template, and bank manuals themselves say "a custom layout can also be accommodated". So there is no single "bank format" — you get the column map from your bank and define it here.
Six gates, all of them stop the file. (1) If a value does not fit its field the file is not produced; you are told who, which field and by how many characters — silently trimming means sending the bank a wrong IBAN. (2) If two fields overlap the template is not saved. (3) If you set a record length every line is exactly that long. (4) With cp1254 or ASCII, an unconvertible character stops the file — a Turkish name never silently becomes "?"; if you want transliteration you ask for it explicitly with bicimleme=ascii on that field. (5) A person failing the IBAN check does not enter the file; to send anyway you tick "Include invalid accounts too" and that is recorded in the audit trail. (6) The file's record count and total in cents are compared with the list, and the file's own SHA-256 is computed.
Why the preview shows a column ruler. In a fixed-width file a single character shift breaks everything. "Preview" prints a numeric ruler above the first lines so you can count column starts by eye. If you left the template source empty, both the screen and the output carry the "not official — verify with your bank" warning. While Settings › Safety gates › banka.txt_uret is off, the existing CSV and JSON outputs keep working unchanged.
23. The Dates tab — probation, contract end, examination
The Dates tab shows the employees' time-bound records in one list: probation and the last day for termination notice, fixed-term contract end and the legal maximum total term, certificate and document validity, periodic medical examination. Legal warnings are written in red; limits come from the parameters in the Legislation tab. Reminders and escalation belong to the Contract calendar — details: Contract Calendar › Employee dates.
Who sees pay and payroll amounts
The contract gross/net pay is seen only by the HR Manager and the Administrator. The HR Staff role sees payroll amounts but not the contract pay; on a job offer the pay is replaced by “Pay hidden — only the HR Manager and administrator see it” (including the offer row in the application detail and the Hire step). A Personnel user without an HR role does not see the ID number, the IBAN or the pay on the personnel card; the contract section is hidden. HR roles are assigned under Personnel › Registration forms › HR roles.
Screens that carry amounts — payroll summary, bank list, social-security notification, severance, advance statement, piece-rate summary, cash projection and exit summary — as well as the Payroll summary comparison, Overtime and HR indicators reports under Reports › HR and the official declaration exports need an HR role; a user without the role gets 403 with the sentence “Payroll and pay amounts are open only to the HR role (HR Manager, HR Staff) and the administrator”. On the personnel portal an employee still sees their own payroll.
A finalised payroll period
No timesheet entry can be written any more to a month whose net payroll is finalised: a punch (manual, phone, Pulse, portal), a correction request and its approval, a day close, a leave request and its approval, “apply to timesheet” from absences and an overtime entry return 422 with “… net payroll is finalised; no timesheet, punch, leave, absence or overtime entry can be written for this period”. To undo, the HR Manager uses Undo with a reason on the finalisation under Personnel › Net payroll.
The accounting period lock covers HR too. Advances, bonuses, piecework, travel allowance, garnishment, hiring/leaving, pay contracts, leave (request, approval, cancellation, bulk), absence, overtime, attendance punches and day close cannot be written into a month locked by accounting (409): “The personnel transaction dated 03.10.2026 falls in the locked accounting period 10.2026; first unlock the period with a reason.” An administrator unlocks it in Accounting › Periods with a reason (at least 5 characters). Payroll finalisation (422) and a closed timesheet period are separate rules and still apply. Punches coming from the staff portal and the MES terminal pass the same gate.
What does a finalised period lock? A salary contract, hire, termination, advance, bonus, piecework, travel allowance and garnishment record that starts in or before a finalised month cannot be written either: “The {donem} payroll is finalized; a salary contract starting in this month or earlier cannot be written. The HR Manager must first undo the finalization with a reason (Personnel › Payroll summary › Net payroll); a contract starting next month is allowed.” The hire and exit of a former employee entered with the historical-record import flag are checked only against their own month. Reverse finalisation asks for a reason of at least 5 characters; the reason is written to the audit trail (Cockpit › Audit › the “Human resources › Payroll — finalisation” and “Human resources › Payroll — reversal” rows).
A period is finalised with a payroll reviewed on screen: finalising without opening the Net payroll tab and checking the list is not accepted (“The period cannot be finalised before the payroll is reviewed on screen…”). Only the HR Manager and the Administrator finalise.
ID, IBAN, birth date, leave days and currency checks
On the employee card (and on bulk employee import rows, and in the portal under Update details › Bank) the following are checked: the Turkish ID number must have 11 digits and pass the check digits; a foreign ID number is at most 20 characters, only letters, digits and hyphens; the IBAN must start with a country code, its length must fit the country (26 characters for TR) and its check digits must match, while a digits-only value is accepted as a 5–34 digit account number; the birth date must be in the past and after 01.01.1900. A faulty field refuses the record with its own sentence and the card does not change; in a bulk import the faulty row is listed with its code.
Leave days: if the day count is left empty in a leave record it is calculated as working days from the date range; if you type it, it cannot exceed the number of calendar days (“The number of leave days does not match the date range: … – … is at most … days”), and leave longer than a year is not saved. The leave type must be one of the company’s defined types (Payroll Regulations › Parameters › leave types; the same list as the leave request in the employee portal): an undefined type is refused with “This leave type is not defined: …” and the type cannot be left empty (“Leave type is required.”). Currency: a job offer and a pay contract take a three-letter ISO code (TRY, USD, EUR; TL = TRY), otherwise it says “Invalid currency.”.
One open advance request
An employee has one open advance request at a time. While one of the two routes on the personnel portal (Advance request and Request › Advance) is open, the other returns 409 with a sentence like “you already have an open advance request”; both routes share one queue and two simultaneous submissions open only one request. A new one can be opened once the request is concluded (approved or rejected).
Changing the PIN in the portal
The PIN that HR gives from Personnel › Portal accounts is also known to HR, so the account is opened with a “must change PIN” flag, and when the employee first signs in to the portal a mandatory “Change your PIN” screen replaces the application (current PIN, new PIN, new PIN again). The same form stays available later under My data › Change PIN. The new PIN must be 4–6 digits; a repeated digit (0000) and consecutive digits (1234) are refused, and the new PIN cannot be the same as the old one. Even if the page is refreshed, the screen comes back until the flag is cleared.
Until the PIN is changed the portal’s write actions (leave, advance, requests and similar submissions) cannot be done: the sentence “Change your PIN before continuing — My data › Change PIN.” appears; the read screens stay open. If you type the current PIN wrongly, the sentence “Current PIN is incorrect; try again. After five wrong attempts sign-in stops for 15 minutes.” appears; a wrong current PIN is added to the sign-in brake counter and after 5 wrong attempts the account is locked for 15 minutes (open sessions are closed). When the PIN is changed successfully, the employee’s sessions on other devices are closed too.
Reset PIN: updates the existing account of the employee you selected in Personnel › Portal accounts and does not open a new one (if the employee has several accounts a picker appears and the screen tells you which account will be reset). When the employee signs in with the new PIN, the employee changes the PIN again. For accounts with a custom name, Close / Open and Unlock also work with the row’s own user name. On the phone the table turns into a card view that shows User · Personnel · Status and the Unlock / Close buttons at first glance; the last sign-in, the device and the number of wrong attempts are under “Details”.
In the portal’s My requests, advance requests opened from the previous portal screen are listed too (“This advance request was opened from the previous portal screen.”) and can be withdrawn with Withdraw request; a request that is already decided or is not yours cannot be withdrawn (“This request cannot be withdrawn: it is already decided or it is not yours.”). In My payslip the period list and the slip are read again each time you return to the tab and with the Refresh button; the period you picked by hand is kept, and if you picked none the newest closed period is shown.
Pay contract, personnel card and recruitment limits
Pay contract: gross pay must be a number greater than zero; an empty, “abc”, 0 or negative value is refused with “Gross wage must be greater than zero.” and the previous contract is not closed (the start date is also required). The new contract’s start must be after the previous contract’s start; when a valid new contract is written, the previous contract closes one day before the new start (a reversed range returns 422: “The new contract's start date (…) must be after the previous contract's start date (…); the previous contract ends one day before the new start.”). Employee card: the collection limit must be at most 999,999,999,999 and the discount authority and disability rate must be between 0 and 100; first name and surname are at most 40, registration no. and ID no. at most 20 characters and other text fields at most 300 characters. No free-text field in HR is silently shortened: if a limit is exceeded, the record is refused naming the field (“First name can be at most 40 characters (41 typed); shorten it and save again.”) and the card does not change. If a limit is exceeded Save is disabled and states the reason; if the save is refused, the ID, IBAN, birth date or text field is marked red and the screen scrolls to it. Recruitment: if offer, interview and hiring notes and reasons exceed the limit the record is refused (never silently shortened); the registration no. is at most 20 characters.
Fixed-term contract. When the contract type “Fixed-term” is chosen the Contract end date is mandatory; if empty it is refused with “A fixed-term contract needs an end date.” The end shows on the personnel card as “Fixed-term contract end” and the contract calendar starts the reminder 30 days ahead. In the recruitment wizard a fixed-term contract cannot be written without an end either.
Mid-month contract change. The payroll of that month is calculated from the contracts in force pro rata by days (e.g. 52,000 for 29 days and 60,000 for the last 2 days gives 52,516.13); a future-dated contract does not enter the payroll until its start month. The contract and wage type are chosen from a list.
Leave and date-of-birth limits
Leave days must fall between the employee’s hire date and exit date; leave cannot be written for a day before the hire or after the exit (422). The same rule applies to the HR leave screen, bulk leave, Timekeeping leave and the leave request in the employee portal. In bulk leave, people whose single employment period does not cover the leave range are listed separately in the preview; on apply, if they have not been added to the exceptions the save stops (“Bulk leave cannot be written for N people whose employment period does not cover …: … Add these people to the exceptions or change the dates.”) — nobody is silently skipped. Portal and timekeeping leave dates are also within the document-date range (10 years before – 2 years after today); a day that does not exist in the calendar (29.02.2027) or an out-of-range year such as 1900 is refused with separate sentences, the range in the sentence is written as dd.mm.yyyy, and typing DD.MM.YYYY is accepted. The birth date must be in the past and after 01.01.1900 (employee card and bulk import row).
Hire date and historical record transfer
Hire, period open, period close (exit), seniority start and recruitment dates must be at most 10 years before – 2 years after today; a date outside the range or one that does not exist in the calendar returns 422 and the server sentence writes the range as dd.mm.yyyy. If you are transferring a former employee or an old record, tick the Historical record transfer box in Employees › Record forms: “Historical record transfer — former employee or old record: the hire date may go back up to 100 years (the action appears in the audit trail).” The box applies only to that record’s write; every ticked write is recorded in the audit trail with its dates and the user. Without the tick, the 10-year limit applies.
The start date of a pay contract and of a framework contract may also be up to 100 years in the past; the end date and the forward limit do not change (for example an end of 9999 is refused).
Employee portal: My payslip and period finalization
The My payslip tab in the portal shows a period’s payroll once HR has finalized the period. For a period that is not final it says “This period’s payroll is not final yet: your slip appears here once HR finalizes the period.”; this is not an error. The Refresh button reloads the list.
Refresh on the recruitment candidate card
The Refresh button at the top of the recruitment application (candidate) card reloads not only the document list but also the offer approval status; if another user has approved the offer you see it without closing and reopening the card.
Cancelling approved leave and portal accounts
Cancelling approved leave. An approved leave row has a Cancel button; only the HR Manager uses it, it asks for a reason (at least 5 characters) and the action is written to the audit trail as “leave cancellation”. Leave that has started or passed cannot be cancelled: “The leave has started or passed; an approved leave that has started cannot be cancelled.” Cancellation is not done in a month whose payroll is final either. Cancelled leave does not hold a place; new leave can be written for the same days.
Portal accounts. “Open account / Reset PIN” requires the HR Manager; if you do not have the role the button is disabled and states the reason: “This action requires the HR Manager role — role: Personnel › Record forms › HR roles.”
In the staff portal, if the start or end date of a leave request is empty the field turns red and “Start and end dates are required.” is written under it; the request is not sent.
Related guides
- Time and Leave — clock-in from the phone, leave approval, labour budget, targetsThe Time and Leave window brings together the employee's clock-in/out from the phone, the day close that turns punches into regular / overtime / night /.
- Practical User HandbookThis page is for an employee using the program for the first time and needing to complete daily work safely. Read the common rules here first.
- Analytics Studio — A Guide from ScratchReady-made reports answer fixed questions. The Analytics Studio lets you ask your own: "How were net sales last year by city and quarter?"
- Payroll Legislation — A Guide from ScratchThe Personnel window holds the person and the gross figure. This window sits on top of it and performs the calculations your country's legislation asks for.