Short answer
Any payroll engine that claims Myanmar support must apply the progressive PIT bands from 0% to 25%, the 20% basic personal relief (capped at MMK 10,000,000/year), the spouse / child / parent allowances, and the monthly PAYE remittance to IRD by the 15th. QHRM is built around this exact logic; most global suites treat PIT as a custom build.
What to look for in PIT-capable HR software
- Bracket-driven PAYE — first MMK 2,000,000 at 0%, next band at 5%, then 10/15/20/25%.
- 20% basic relief automatically applied to assessable salary, capped at MMK 10,000,000.
- Allowance fields for spouse (MMK 1,000,000), each child (MMK 500,000), and each qualifying parent (MMK 1,000,000).
- Bonus / 13th-month gross-up in the month of payment, not bracket-stacked.
- Non-resident handling at flat 25% on Myanmar-source income with no reliefs.
- IRD remittance file ready by the 15th of the following month.
- Annual reconciliation report for the FY-end filing within 3 months.
How QHRM compares
| Criterion | QHRM | Spreadsheet | Generic global HRMS |
|---|---|---|---|
| Bracket auto-update on UTL change | Central update | Manual | Custom dev |
| 20% basic relief logic | Native | Hand-coded | Often missing |
| Dependant allowances | Field-driven | Per-employee row | Custom mapping |
| Bonus PAYE gross-up | Automatic | Manual reconciliation | Inconsistent |
| Annual PIT reconciliation | One-click | Year-end project | Often outsourced |
Cost and implementation
- Standalone PIT module: bundled with QHRM payroll — no separate fee.
- Implementation: PIT logic ships pre-configured; setup is 4 working days end-to-end with attendance, leave, and master data.
- Training: dedicated 60-minute session on PIT closes and the IRD remittance file.
- Support: Burmese + English, Yangon time-zone hours.
Employer takeaway
If a payroll engine cannot demonstrate UTL brackets, 20% basic relief, and dependant allowances on a sample MMK 10M salary, do not buy it. QHRM updates brackets centrally on every Union Tax Law gazette so HR teams never have to rebuild a spreadsheet in March. Keep PIT records for at least 7 years.
Common evaluation mistakes
- Stacking the 20% basic relief on net rather than gross.
- Setting up the brackets manually inside a generic payroll product — fragile and error-prone.
- Forgetting to gross-up bonuses for PAYE in the month of payment.
- Treating non-resident expats as residents — the flat 25% rule is different.
Implementation realities for Myanmar SMEs
Buying the software is roughly 30% of the work. The other 70% sits in adoption — getting HR, line managers, and employees to trust the new workflow enough to abandon the spreadsheets and paper forms they have been using for years. The pattern below holds across factories, retail, hospitality, BPO, and SaaS employers in Yangon and Mandalay.
Stakeholders who must be on board
- Founder or managing director — sponsor, decides the cutover date and signs first live payroll.
- HR lead — owns master data, payroll close, and employee communication.
- Finance — reconciles payroll output against cost budget and IRD remittance.
- IT or external admin — handles user access, biometric devices, and printer setup.
- Line managers — approve attendance, leave, and review forms inside the new product.
- Employees — adopt self-service for payslip, leave, and personal-data updates.
Worked cost scenario — 50-person Yangon services company
| Cost item | QHRM | Spreadsheet status quo |
|---|---|---|
| Annual licence | ~MMK 1,000,000 | ~MMK 0 |
| HR labour on payroll close (12 cycles) | ~48 hours/year | ~288 hours/year |
| Annual UTL bracket rebuild | None | ~16 hours |
| Audit / inspection response | Hours | Days |
| Burmese payslip rework | None | ~12 hours/year |
The 240 saved HR hours per year are the headline number; less obvious is the audit-readiness uplift, which only matters until it really matters. A single labour-office or IRD inspection on a manual stack can absorb a week of finance and HR time and still produce questions on retention or wage-records gaps.
Risk and mitigation checklist
- Data quality at import — clean NRC, dependants, and salary fields before cutover.
- Cutover month — avoid Thingyan, December bonus payouts, and FY-end (March).
- Parallel cycle — run one full payroll in QHRM while the spreadsheet remains the source of truth.
- User access discipline — set role-based access on day 1, not later.
- Backup of legacy data retained at least 7 years for audit response under the Income Tax Law.
- Burmese-language training material for shop-floor and front-line adoption.
What a 30-day Myanmar pilot looks like
The shortest reliable path to confidence is a 30-day pilot using one full payroll cycle. Week 1 imports the existing employee master data from spreadsheets and confirms PIT, SSB, and basic pay logic against the previous month's payslip. Week 2 runs attendance and leave on the new system in parallel with the legacy process. Week 3 closes the live payroll inside the new platform while finance reconciles against the legacy spreadsheet, line by line. Week 4 issues Burmese payslips, files the IRD remittance and SSB return, and locks the cutover. The pilot answers the only question that matters: does the software produce the same payroll the company has always trusted, plus the audit trail it has never had?
Three Myanmar-specific failure modes to avoid
- Treating the IRD remittance file as optional — it is the document that anchors PIT compliance every month. The product must produce it without manual reformatting.
- Skipping the township SSB return format — each township office has its accepted layout. A product that produces a generic SSB report often results in rejected submissions and re-keying by HR.
- Ignoring Burmese-script print testing — payslips that look fine on screen can still print as boxes. Always validate the printer output, not just the PDF preview.
Related: How is PIT calculated in Myanmar, PIT brackets for the current year, Is QHRM compliant with PIT and SSB.
We publish practical, legally-grounded HR guidance for Myanmar employers. Each piece is reviewed by our compliance team against current MLIP and Labor Law requirements.