Key steps and distinctions
Software should support all mandatory and optional specification fields without automatically classifying remuneration as non-taxable. Map pay components correctly and transfer Appendix 8A/8B totals to the corresponding IR8A fields. Corrections should be made in payroll records and regenerated, rather than editing final forms. CPF controls compute compulsory contributions by current rates, age and residence and distinguish excess employer or voluntary employee amounts. Provide limited user access, login controls and audit trails, and allow only authorised API submitters. Employers need submission summaries, payroll-to-tax reconciliations, classification reports and clear record-level errors or warnings. A success display should include acknowledgement, entity and tax number, year, file type, count, date, time and user; logs and portal-status checking are also useful. Prompts can flag duplicates, preserve pre-submission copies, request benefits appendices or identify tax-clearance cases. The recommended amendment facility supports current-year, four-back-year and one-advance-year records. These are reference recommendations, not a certification that a vendor or every suggested feature guarantees tax compliance. Assess controls against actual payroll and review the final accepted submission.
Official source
A concise, independent Apex Gateway guide based on the official English source, not a reproduction of the complete document. Consult the original for full conditions, exceptions and subsequent updates.
Read the official PDF ↗
