Dominican Republic 6 min read Social security

The TSS: what's deducted, what the employer contributes and where everyone gets it wrong

TSS errors are hardly ever about the rate: they're about the salary it's applied to. What counts towards the contribution base and why the cap changes the calculation.

They're two costs, not one

The first confusion is conceptual, and plenty of people who've run payroll for years have it: Dominican social security is paid by both sides. One part is deducted from the employee's salary; the other is contributed by the company on top of that salary.

That means an employee's real cost isn't their salary. It's their salary plus the employer contribution, and the difference isn't small. Budgeting a hire on the gross salary falls short systematically.

There are three schemes: family health insurance, pensions and occupational risks. On top comes the technical training levy, which is employer-only.

The real error: the base, not the rate

The rates are published and almost nobody gets them wrong. Where almost everybody does get it wrong is what they're applied to:

  • Not everything paid to an employee counts. Some items form part of the contributory salary and others don't. Putting an item in the wrong group skews the contribution every month.
  • There are caps. Above a certain salary, the contribution stops rising. A system that doesn't apply the cap overcharges the employee and overpays for the company, month after month.
  • The caps aren't the same for the three schemes. Applying one to all is an error that gives nearly-right figures, which is the worst kind of error.
  • An employee joining or leaving mid-month contributes for those days, not for the whole month.

A miscalculated contribution doesn't bounce: the TSS accepts it. The problem shows up when the employee goes to use their insurance or claim their pension and the weeks don't add up, and then the correction is retroactive.

Change reporting is half the work

What really eats the time each month isn't calculating: it's reporting changes. Joiners, leavers, salary changes, leave, benefits. If that's done by hand on the portal, it's done twice: once in the payroll system and once at the TSS.

And when it's done twice, sooner or later one of the two gets forgotten. The classic symptom: an employee who left three months ago and is still being paid contributions for, or one who joined and doesn't appear.

What the system should do

  • Classify every pay item as contributory or not, once, when it's defined, and not on every payslip.
  • Apply the cap that belongs to each scheme, with the current year's values.
  • Pro-rate mid-month joiners and leavers without anyone counting days by hand.
  • Generate the change file from the same data used to pay, not from a separate entry.

If you also handle severance, it's worth reading how severance and notice pay are calculated: they share the same salary base and the same classification errors.

Rates, caps and contributory items are updated by resolution, usually every year. Confirm the current ones with the TSS or your employment adviser: what's explained here is the mechanism, not the figures.

Payroll and labour obligations

On the same topic

The TSS, calculated and filed from one place

In Zyntello the contribution comes out of the payroll you already calculated, with items classified once and caps applied automatically.