Zettaz (PayTime) Caribbean payroll audit: the 20-territory statutory engine and how to test it

What Zettaz PayTime is and how wide its coverage is

Zettaz builds PayTime, a cloud payroll system aimed at Caribbean employers. Its stated coverage of 20+ territories is one of the widest among regional products, spanning English-speaking islands such as Jamaica, Barbados, Trinidad and Tobago and Antigua, and Dutch-heritage territories such as Sint Maarten. For a group with entities on many islands, one engine with local rules built in is a real advantage over stitching together several local bureaus.

PayTime does not employ anyone. You remain the employer: you hold the registrations, fund payroll, and are responsible for filings and penalties. Before buying, confirm in writing:

• The exact territory list, and for each one which statutory outputs are produced (for example the Jamaica S01, Barbados NIS returns, Trinidad NIS and PAYE).
• Whether bank payment files are generated for your local banks.
• Multi-currency support, including running payroll in local currency while reporting in USD.
• Release practice for rate changes and who tests them.

Ask also about support coverage for territories where your group has few staff. Wide coverage is valuable only if each territory has someone who answers statutory questions on payroll day.

Pricing tiers and what to benchmark them against

Zettaz does not publish a single price list for all configurations; quotes depend on headcount, territories and modules. Ask for each line separately.

Use the fee audit calculator to see where software and bureau sit against an EOR for your headcount.

When you request the quote, give Zettaz your headcount per territory, pay frequency per entity (weekly, fortnightly, monthly) and the modules you need. Payroll software for multi-island groups is often priced on the number of entities and pay groups as well as headcount, so the same 25 people can be priced very differently depending on structure. Ask for a three-year total cost including setup, so year-one and steady-state costs are both visible. Then compare it with the bureau figures in the worked example below.

Worked example: three test payslips and a 25-seat cost benchmark

Ask for a sandbox and run these employer-side test cases, using 2026 rates from research and the authorities. Confirm each rate with TAJ, NIBTT and the Barbados NIS before relying on it. Any engine you buy should reproduce these numbers exactly.

The Jamaica PAYE line uses the April 2026 threshold for a full fiscal year; a payroll spanning January-March applies the older JMD 1,799,376 figure, which is itself a good test of the engine. The Zettaz subscription plus your internal labor should be compared with the $9,000-$27,000 bureau range.

Contract clauses to check

1. Entity. The license should be in the name of the group or each local entity; confirm adding entities later is priced in advance.
2. Calculation warranty. A remedy for penalties caused by a confirmed software defect, and a fix timeline.
3. Severance. The engine should calculate Trinidad RSBA severance (2 weeks per year for years 1-4, 3 weeks from year 5) and Jamaica ETRPA redundancy, but you fund them. Cross-check with the severance calculator.
4. Data. Hosting region, access controls, sub-processors, breach notice.
5. Exit. Full export of history and year-end data, and read-only access for statutory record retention after termination.

Because PayTime covers many territories, ask for a coverage schedule in the contract listing each territory, the statutory outputs supported and the update commitment for each. If a territory is supported only partially, for example payroll calculation without filing reports, it should say so. This avoids a dispute about scope after you have migrated. Also confirm the support hours on payroll days and whether a named contact covers your group.

When Zettaz PayTime fits, and when it does not

It fits when you own entities in several territories, including smaller ones that many products skip, and you have finance or HR staff who can run payroll. Its breadth makes it a natural candidate for retail, hospitality and distribution groups spread across the Eastern and Southern Caribbean.

It does not fit when you have no local entity, have only a handful of staff on one island, or want someone else to own filing risk. Then an EOR or bureau is the better route. See TriblockHR vs Zettaz PayTime, legacy payroll migration and the bank payroll dispersal playbook.

A typical decision rule: if your group has at least one experienced payroll officer and 50+ employees across three or more territories, a regional engine like PayTime is usually cheaper than several bureaus and gives more control. Below that, the bureau route is often simpler. Use your test payslips as the deciding step: a product that reproduces all three cases first time, including the Jamaica threshold change in April, is ready for a parallel run.

Negotiation levers

• Territory bundles. Ask for a flat price covering all your current territories plus one or two future ones.
• Setup per group, not per island, where configuration is shared.
• Parallel run support for two cycles at no charge.
• Price lock for 24-36 months and an uplift cap.
• Test-case acceptance. Make go-live conditional on the engine matching your test payslips.

Share your test payslips with Zettaz before the demo so the presentation uses your real cases. Ask for a fixed implementation price with a defined scope (data migration, configuration per territory, bank files, two parallel runs) and a date. If you are migrating from legacy software, ask for help mapping historic year-to-date figures so mid-year migration does not break annual reporting. And ask for the price of each additional territory up front, so future expansion is predictable.

Finally, ask what happens to pricing if you close a territory: a subscription that drops the entity at the next renewal, without penalty, keeps the contract aligned with your footprint.