2026 Payroll and TaRMS Variances: What We Have Seen So Far

2026 Payroll and TaRMS Variances: What We Have Seen So Far

Over the past few weeks, our team has been conducting an on-going analysis of the 2026 payroll cycles, specifically comparing the TaRMS Earning Template output file from Belina, with actual results after having uploaded into TaRMS.

Based on our findings, we want to advise all clients to pay close attention to the following critical areas

1. Belina Version 3.2

To ensure your payroll aligns with current ZIMRA logic, inside Belina ensure you are on Belina Payroll Version 3.2as highlighted on the image below.

• Why: This version introduces the NON_FDS logic (formerly referred to as PAYE). This logic is specifically engineered to mirror exactly how ZIMRA calculates tax for non-FDS employees within the TaRMS environment.
• Action: Version 3.2 and the accompanying update instructions are available for download on our website resources page. Please ensure you have performed this update if you have not already done so.

2. Critical Review: TaRMS Field Allocations

Following our email communication on February 5th, titled “TaRMS Field Allocation Review,” we have noted that incorrect field mapping is the leading cause of variances between Belina and TaRMS.

Please verify your TaRMS PAYE Field allocations every time before exporting from Belina:

1. Go to the Setup menu.
2. Select Tax, then Existing.
3. Navigate to the TaRMS Fields tab. (or select the TaRMS Field option, which is available just before you export your TaRMS report)

Key areas to check:

• APWCS & Other Employer Transaction Codes: These should have a blank TaRMS PAYE field allocated as per screenshot below.

• Irregular Benefits and Irregular Benefit Allowances (used when grossing up): These must be specifically assigned to the TaRMS field: “Current Other Irregular Earnings.”
• Regular Overtime and Regular Allowance Benefit codes: These must be specifically assigned to the TaRMS field: “Current Salary, Wages, Fees, Commissions, etc. (regular earnings).”

Note: If you identify a misallocation after a return has already been filed, remember that ZIMRA allows for the amending of previously submitted returns. We encourage you to amend your Earnings Template in TaRMS if a payroll misallocations were discovered post-filing.

3. Deductions and Taxable Income

Outside of field mapping, variances often arise from how deductions are treated. Please verify that your NEC levy, Professional Subscriptions and Trade Union Codes have the “Tax Deductible” box ticked in your setup:

These deductions reduce an employee’s taxable income. If they are not marked as deductible in Belina, your internal tax calculation will be higher than the TaRMS calculation, leading to unnecessary tax overpayments.

4. 2026 Tax Tables & ZiG Payroll Requirements

Please ensure your 2026 Tax Tables are set up according to our year-end notes. For ZiG payrolls, you must:

• Convert Tax Credits/Benefits: Update these to ZiG monthly using the prevailing interbank rate.
• Sync Exchange Rates: Use the exact same rate in both Belina and TaRMS to avoid tax variances.

5. What’s Next?

We are continuously monitoring TaRMS behaviour to ensure our software remains the most accurate tool for Zimbabwean payrolls.

• New Update Coming: A further Belina update is scheduled for release in the coming weeks to further refine these integrations.