Payroll service in Estonia: monthly workflow, inputs, controls, TSD filing, and vendor checklist for stable salary processing.
Payroll is a calendar process before it is a calculation process
A stable payroll service starts with a calendar, not with formulas. Every month the company needs the same sequence: employee changes confirmed, working time or bonus inputs approved, draft payroll reviewed, payments released, and TSD filed without unresolved questions.
When payroll fails, the cause is usually upstream. HR changes arrive late, founders approve bonuses after the cut-off, or reimbursements are mixed with salary logic. The service provider can process only what the company controls in time.
That is why payroll should be designed as one operating cycle alongside accounting close and tax filing, not as a side task that gets attention only on salary day.
Define the inputs the provider must receive
Before the payroll month starts, document who sends and who approves each input:
- new hires, departures, and contract amendments;
- salary changes, bonuses, and board remuneration;
- leave, sickness, and unpaid absence data;
- benefits, reimbursements, and one-off taxable items;
- payment date, funding confirmation, and cost-centre requirements.
If one of these items is still informal, expect last-minute corrections. Payroll quality is built on input discipline, not on last-minute spreadsheet fixes.
What a real payroll service should deliver
A credible payroll service produces more than net salary numbers. The deliverables should include draft payroll for approval, payment file or payment list, payslips, TSD-ready filing data, explanation of unusual items, and a clean audit trail of what changed since the previous month.
Management should also know what the provider will not do without an explicit request. For example, board-pay decision drafting, employment-law advice, or benefit classification often sit outside routine processing unless agreed in scope.
The cleaner the deliverable list, the easier it is to compare providers and the easier it is to hold the current setup accountable.
Control the TSD and edge-case risks explicitly
Payroll risk in Estonia is rarely about standard salary calculation. It is about edge cases: board fees, mixed reimbursement policies, benefits in kind, non-resident cases, termination timing, and manual overrides. These items need a review rule before filing, not after.
Use one short monthly risk check: what changed in people, pay components, or benefits this month, and which items need confirmation before TSD is filed? If the answer depends on memory, the process is too fragile.
Pair this check with your broader deadline calendar and your first-90-days operating plan if the company is still young.
Questions to ask a payroll provider before signing
Ask practical questions, not marketing ones:
- What is the cut-off for employee changes and bonus approvals?
- Who reviews non-standard items before TSD filing?
- What happens if funding or approvals arrive late?
- How are payslips delivered and archived?
- Who keeps the history of calculations, approvals, and changes?
- What is the escalation path during absences or urgent corrections?
These answers matter more than the headline monthly fee because they determine whether payroll is predictable under pressure.
A practical first-month implementation plan
Week 1: collect employee master data, contracts, tax settings, and approval owners. Week 2: test the cut-off calendar and define the draft payroll review sequence. Week 3: run a sample month with one or two edge cases. Week 4: approve the first live payroll and archive every output in one place.
The first month should produce a documented process, not just a correct salary run. If nobody can explain who sends what by which date, the next month will rely on luck again.
When payroll is embedded into the month-end close, salaries stop being a recurring emergency and become part of a controlled finance routine.
Frequently Asked Questions
What usually causes payroll delays?
Late people-data changes, unclear approval of bonuses or reimbursements, and missing ownership of the monthly cut-off.
What should management approve every month?
At minimum: employee changes, non-standard payments, and the draft payroll before payment and TSD filing.
Does payroll service include tax advice?
Routine processing usually does, but non-standard tax treatment should be explicitly agreed and escalated.
Who should own the payroll calendar?
The company should own the calendar even if a provider runs the calculations. Vendor dependence should not replace internal accountability.
When do we need a more advanced payroll setup?
As soon as benefits, international staff, board fees, or frequent payment changes become normal rather than exceptional. You may also find useful: monthly accounting documents Estonia.