Your Turkish entity has grown past 240 people across a head office and two plants. Every month, overtime from one plant arrives after the cutoff. Last quarter a leaver’s final pay was calculated twice. When your team asks the current provider why, the answer is a ticket number.
Now you are asked to fix it, and every proposal on your desk looks the same: a per-employee fee and a generic list of services.
At this size, payroll in Turkey is an operating model. It has dozens of inputs, several owners, and a monthly statutory deadline that will not wait for a late file.
This guide sets out what an outsourced provider should own for a 200+ employee entity and who should do the work on both sides. It also covers how inputs and exceptions are controlled and which drivers should build the quote. Datassist has run Turkish payroll since 1999 and calculates more than 1.5 million payrolls a year, so the model below reflects how large Turkish payrolls actually run.
Table of Contents
- Why Payroll in Turkey Changes Shape Above 200 Employees
- Turkey Payroll Outsourcing Scope: Who Owns What
- The Team Model Behind the Payroll Service Delivery Model
- Input Controls, Escalation, and Exception Ownership
- Payroll Outsourcing Cost Drivers at 200+ Employees
- A Quote Checklist for Enterprise Payroll Outsourcing
Why Payroll in Turkey Changes Shape Above 200 Employees
A 30-person payroll can survive on one accountant and a spreadsheet. A 200+ employee payroll cannot, because volume and variety grow together. You typically have more than one SGK (Social Security Institution) workplace file, shift and overtime pay, site-level allowances, and a steady flow of joiners, leavers, and contract changes. Some employers also apply a collective agreement at one site and individual contracts at another.
The statutory backbone stays the same for every employer. Labor Law No. 4857 requires wages to be paid at least monthly (Article 32) and requires a wage statement that itemizes every addition and deduction (Article 37). Law No. 5510 requires the SGK start notification before an employee’s insurance starts, with limited sector exceptions (Article 8). Withholding tax and SGK premium data are then filed together on one monthly return, due by the 26th of the following month unless the Revenue Administration extends it.
What changes at scale is how far a single error travels. One wrong parameter, one missed joiner notification, or one late overtime file now touches hundreds of payslips and the same monthly return.
What Law No. 7566 Changed in January 2026
2026 shows why this matters. Law No. 7566 was published in the Official Gazette on December 19, 2025. From January 2026, it raised the Invalidity, Old Age, and Death premium from 20% to 21%, with the employer share moving from 11% to 12%. The same law cut the Treasury-funded premium discount for private employers outside manufacturing from four points to two.
Law No. 7566 also raised the SGK earnings ceiling from 7.5 to 9 times the minimum wage from January 1, 2026.
Regulation Note: These changes landed in the same January run: a new employer rate for every employee, a smaller discount outside manufacturing, and a higher ceiling for high earners. A provider that updates one parameter and misses another produces a wrong return for the whole entity.
Changes like these are why parameter updates must sit inside the provider’s scope, with a named owner and a test before the first affected run. Our explainer on Turkey’s Law No. 7566 covers the payroll impact in detail.
Turkey Payroll Outsourcing Scope: Who Owns What
Most disputes with a payroll provider start with scope. A proposal says “end-to-end payroll,” and each side reads it differently. The fix is a written scope matrix that names an owner for every activity. Below is the structure we recommend for a 200+ employee entity.
| Activity | Provider | Client | Notes |
|---|---|---|---|
| Employee master data | Maintains payroll records | Owns HR source data | Agree which system is the source of truth |
| Monthly inputs (overtime, absence, bonuses) | Collects, validates, queries gaps | Submits by cutoff | Cutoff per input type |
| Gross-to-net calculation | Owns | Reviews summary | Dual review on provider side |
| Payslips | Produces and distributes | None | Article 37 content requirements |
| Monthly withholding and SGK return | Prepares and files | Funds payments | Filing proof shared each month |
| SGK start and exit notifications | Files on instruction | Instructs on time | Late instruction is a client exception |
| Final pay and severance pay calculation | Calculates | Approves and decides policy | Termination reason drives the outcome |
| Wage garnishments | Applies and tracks | Forwards notices | Same-day handover of notices |
| Bank payment file | Prepares | Approves and releases | Client keeps payment authority |
| Statutory parameter updates | Implements and tests | Informed | Change control (see below) |
| Inspections and authority queries | Prepares payroll evidence | Represents the employer | Shared, define response roles |
| Reporting and general ledger (GL) journal | Produces to agreed format | Defines chart of accounts | Format fixed at implementation |
What Should Stay With the Client
A sound Turkey payroll outsourcing scope also states what stays with the client. Pay policy, approvals, and payment release should remain in-house. The provider calculates, files, and documents the work, while the employer decides and pays.
Datassist’s payroll outsourcing service is built on this split, so the people approving pay are never the people calculating it.
Risk: Anything not listed in the matrix will later be treated as a change request. Gray areas such as off-cycle runs, incentive claims, retroactive pay changes, and employee query handling should be listed by name, even if the answer is “client.”
The Team Model Behind the Payroll Service Delivery Model
A payroll service delivery model is only as good as the people named in it. For payroll in Turkey at 200+ employees, a single generalist cannot cover calculation, review, legislation, and integration in the same week. Ask every provider to name these roles and say who fills them.
Provider side:
- Relationship manager. One named owner for the account, accountable for the monthly result and the escalation path. When something breaks, this is the person you call.
- Payroll specialists. Prepare the run, chase missing inputs, and answer employee questions within agreed rules.
- Independent reviewer. Checks the run before it reaches you. The reviewer should not be the person who calculated it.
- Legislation and compliance expert. Tracks regulatory change, interprets edge cases, and signs off parameter updates.
- Data and integration specialist. Owns file formats, HRIS interfaces, and the GL output.
- SGK and incentive specialist. Available on call for registrations, inspections, and social security incentives.
Client side: a payroll owner who signs off each run, an HR data owner for each site, a finance approver who releases payment, and an IT contact for interfaces.
How many people sit in each role depends on your pay complexity, so treat any fixed staffing ratio in a proposal with caution. What matters is that each role is named, backed up, and present in the monthly rhythm. That rhythm means an agreed close calendar, a pre-close check on inputs, a post-run review of variances, and a periodic service review with the relationship manager.
Expert Take: The pattern we see most often in failing enterprise payrolls is not a skills gap. It is an ownership gap. When nobody on the provider side owns the result end to end, every error becomes a ticket and nobody fixes the cause.
Input Controls, Escalation, and Exception Ownership
In our experience running payroll in Turkey, late or wrong inputs cause more errors than wrong formulas. Enterprise payroll outsourcing should therefore be built around controls that run every month, whoever is on shift.
The controls we expect to see written into the service description:
- Cutoffs by input type. Master data changes, overtime, absence, and one-off payments each get a cutoff date in the payroll calendar.
- Validation before calculation. Joiners without an SGK start notification, leavers without final pay data, and missing bank details are flagged before the run.
- Variance review after calculation. Each employee’s net pay and the employer total are compared with the prior month, and outliers are explained before sign-off.
- Client approval before payment. No bank file is released without written approval from your payroll owner.
Escalation should run in levels: specialist, then relationship manager, then provider management, with response and resolution times classified by priority in the SLA. A periodic payroll compliance audit then tests whether the controls actually work.
Exceptions are where contracts are tested. Agree the first owner of each one in advance:
| Exception | First owner | What the contract should state |
|---|---|---|
| Input received after cutoff | Client | Processed next run or off-cycle, at agreed terms |
| Off-cycle payment request | Client requests, provider runs | Number included and price beyond that |
| Provider calculation error | Provider | Correction route, cost of reruns, and liability terms |
| Statutory change mid-period | Provider | Implementation and test before the next run |
| SGK or tax inspection | Shared | Evidence the provider prepares and how fast |
| Employee pay dispute | Client, supported by provider | Who replies to the employee and in which language |
Payroll Outsourcing Cost Drivers at 200+ Employees
Headcount is only the starting point of a quote. Two Turkish entities with the same headcount can price very differently, because the work behind each payslip differs. These are the payroll outsourcing cost drivers worth asking about:
- The number of entities and SGK workplace files, since each one adds filings and reconciliations
- Pay complexity: shift patterns, overtime rules, collective agreement terms, and the number of pay elements
- How many runs you need beyond the regular one, such as bonus, off-cycle, and correction runs
- Leaver volume, because final pay and severance pay take more work than a standard payslip
- Interfaces with HRIS, time and attendance, and ERP systems, and the file formats each one needs
- Reporting: GL journals, cost-center splits, headquarters packs, and audit requests
- Employee services such as a self-service portal, query handling, and the languages required
- Whether the provider identifies, applies, and monitors SGK incentives for you
- Implementation work (data migration, parallel runs, testing), which should be priced once rather than hidden in the monthly fee
Cost therefore varies with company size, scope, pay complexity, and integration needs. Any quote should show which of these drivers it assumes. Implementation effort deserves its own line, and the steps in our payroll migration checklist show what a provider move involves.
A Quote Checklist for Enterprise Payroll Outsourcing
Before you sign, ask each provider to answer the same questions in writing. The answers make quotes comparable and expose what a headline fee leaves out.
- Which activities in the scope matrix are included, and which are priced separately?
- Who are the named relationship manager and reviewer, and who covers their absence?
- What are the input cutoffs, and what happens to input received after them?
- How many off-cycle runs are included each year?
- How are statutory changes, such as the January 2026 SGK changes, implemented and charged?
- What does the provider pay for, or redo at its own cost, when its calculation is wrong?
- What evidence comes with each run: filing proofs, variance reports, and approval records?
- What audit assurance can the provider show? Datassist operates under ISO 27001 and ISAE 3402 certification.
- How does the contract cover the provider’s role as data processor under Law No. 6698 (KVKK), including security measures and sub-processors?
- What does exit look like: data return format, handover support, and notice period?
Score the written answers side by side rather than the headline fees. For the wider provider comparison, our guide Turkey Payroll Outsourcing: Cost, Benefits & Provider Selection sets out the full evaluation.
Frequently Asked Questions
What does payroll in Turkey involve for a company with 200+ employees?
It involves monthly gross-to-net calculation, payslips that itemize every addition and deduction, SGK start and exit notifications, and a combined monthly withholding tax and SGK premium return. At 200+ employees, the harder part is control: collecting inputs from several sites on time, validating them, reviewing variances, and getting approval before payment.
What should stay in-house when you outsource payroll in Turkey?
Keep pay policy, approvals, and payment release in-house. Your HR team should also own the source data for employees, such as contracts, salary changes, and terminations. The provider should calculate, file, produce payslips, and supply evidence. This split keeps the people who decide pay separate from the people who calculate it.
How is payroll outsourcing priced for a large Turkish entity?
Pricing usually starts with headcount and then reflects scope: number of entities and SGK workplace files, pay complexity, off-cycle runs, leaver volume, integrations, reporting, and employee services. Implementation is often priced separately. Ask every provider to list the drivers its quote assumes, so you can compare like with like.
Who is responsible when an outsourced payroll calculation is wrong?
The employer remains the legal employer toward employees and authorities, so the obligations do not transfer. The contract decides how the provider corrects its own errors, who pays for reruns, and what liability it accepts. Agree this before signing, together with an exception table that names the first owner for each type of error.
How long does a 200+ employee payroll migration take?
There is no fixed timeline. It depends on data quality, the number of entities and integrations, how quickly the outgoing provider hands over history, and whether you run parallel payrolls. Plan in phases: data migration, parallel testing, and go-live, and avoid committing to a start month before data quality has been checked.
Key Takeaways
- At 200+ employees, payroll in Turkey is an operating model with many inputs and owners.
- A written scope matrix with provider, client, and shared owners prevents most disputes before they start.
- Ask each provider to name its relationship manager, independent reviewer, and legislation expert.
- Cutoffs, validation, variance review, and approval before payment are the controls that keep a large payroll accurate.
- Quotes become comparable only when providers show the cost drivers they assume and price implementation separately.
Payroll in Turkey at 200+ Employees: The Bottom Line
The plant that sends overtime late and the leaver paid twice come down to ownership, and so does the fix. Settle the scope, name the people, write down the controls, and agree who owns each exception, and payroll in Turkey becomes predictable even at several hundred employees.
Datassist’s Payroll Outsourcing service gives Turkish entities a named relationship manager, a reviewed monthly run, and filings handled by a team with more than 25 years of Turkish payroll. Datassist has twice been named Best In-Country Payroll Provider of the Year by the Global Payroll Association. We work under ISO 27001 and ISAE 3402 controls, and our quotes show the scope and drivers behind every line. Discuss payroll requirements with Datassist.
This article is for informational purposes only and does not constitute legal advice. For up-to-date Turkish regulations, consult official sources or contact a qualified advisor.
Related Reading
- Payroll Outsourcing in Turkey: In-House vs Outsourced Cost and Risk – How to decide whether Turkish payroll should stay in-house or move to a provider.
- Payroll Outsourcing Cost: Pricing Drivers and Scope Gaps – The pricing models and scope gaps that distort international payroll quotes.
- Payroll Outsourcing Services for Multinational Companies: Scope, Pricing, and SLAs – What multinational buyers should expect from scope, pricing, and service levels.
