Learning Unit1 | US:110008, NQF Level 5 Worth 45 Credits DETERMINE INDIVIDUAL AND AGGREGATE PAYMENTS |
Unit Standard Purpose | This Unit Standard is for all people working in a payroll environment, particularly those who have to determine aggregate and individual payments. Persons credited with this Unit Standard are able to: · Identify and record deductions · Perform basic tax calculations · Calculate and verify net pay · Ascertain and reconcile aggregate payroll totals · Generate and distribute pay slips. This means that such learners will be able to establish the range of deductions to be applied to gross pay, in order to arrive at net pay entitlement and produce supporting documentation. |
Learning Assumed to be in Place | Persons attempting this Unit Standard should be competent in: · Communication at NQF Level 4 · Mathematical Literacy at NQF Level 4 · The Unit Standards entitled: · “Ascertain gross pay” · “Demonstrate an understanding of statutory legislation and requirements relevant to Payroll Administration”. |
Session 1 SO 1 | Identify and record deductions. |
Learning Outcomes (Assessment Criteria) | All relevant temporary deductions are identified and correctly applied to employees affected. Temporary deductions are checked for proper authorisation in accordance with organisational and legal requirements. Permanent deductions are identified by reference to core payroll data. Income subject to statutory contributions is correctly identified for all eligible employees. Retirement funding income is correctly identified for all eligible employees. All deductions are compared with payroll requirement parameters and any that fall outside the parameters are referred to the appropriate person for resolution. All time scales and cut-off dates are complied with in terms of organizational and statutory requirements. |
Session 1 SO 1 | Identify and record deductions. |
Compulsory deductions include tax and Unemployment Insurance Fund contributions.
Deductions related to benefits, such as pension, medical aid, life cover and income protection, are usually voluntary but can be compulsory depending on your employer’s policy.
Deduction forms and the remuneration of employees are addressed in section 34 of the Basic Conditions of employment Act.
4(1) “An employer may not make any deduction from an employee’s remuneration unless”
This means that a deduction in terms of section 34(1) may not be made unless the requirements set out in 34(1)(a) and (b) are met. A deduction from an employee’s remuneration would therefore only be possible if the employee agreed to such a deduction in writing or the deduction is allowed in terms of legislation, a court order or an arbitration award.
34(1) and 34(1)(a) states – “An employer may not make any deduction from an employee’s remuneration unless, subject to subsection (2), the employee in writing agrees to the deduction.”
In terms of subsection 2 an employer may deduct from an employee’s remuneration an amount equal to the damage suffered or a loss incurred as a result of the negligent or deliberate behavior of an employee. There are however certain requirements that must be fulfilled before such a deduction may be made. Section 34(2) clearly states “..only if-“, meaning that all of the requirements of subsection 2 must be satisfied. This is amplified by the use of the word “and” at the end of 34(2)(c).The requirements of subsection 2 are:
In terms of schedule 8 of the Labour Relations Act a fair procedure means that:
Section 34(1)(a) states “subject to subsection (2), the employee in writing agrees to the deduction in respect of a debt specified in the agreement”. The DoL’s interpretation of this is that the two sections cross reference each other. In other words, in addition to the requirements of subsection 2 an agreement in writing must be obtained from the employee in terms of 34(1)(a). This would mean that an employer will not be able to deduct without the employee’s permission even if all the requirements of subsection 2 have been met.
Session 2 SO 2 |
Perform basic tax calculations. |
Learning Outcomes (Assessment Criteria) | · The concept of SITE is explained orally and SITE calculations are done for all employees on the payroll/ for at least ten employees · The concept of PAYE is explained orally and PAYE calculations are done for all employees on the payroll/ for at least ten employees. · Taxable income is correctly identified and calculated for each employee on the payroll/for at least ten employees. · The difference between non-cumulative and cumulative tax is explained in tabular form with at least five examples given of each. · The correct calculation of tax for employees working for various tax periods is performed for at least two employees falling into each category. |
SITE – Standard Income Tax on Employees is deducted by the employer from an employee’s salary (usually at the end of every month). All employees are liable for this tax. Where an employee’s net remuneration is R87 300 (TYE 2022) or less, PAYE does not have to be deducted.
Employees’ tax, which comprises of Pay-As-You-Earn (PAYE) and Standard Income Tax on Employees (SITE), refers to the tax required to be deducted by an employer from an employee’s remuneration paid or payable. The SITE element is not applicable with effect from 1 March 2012.
Employees’ Tax refers to the tax required to be deducted by an employer from an employee’s remuneration paid or payable. The process of deducting or withholding tax from remuneration as it is earned by an employee is commonly referred to as PAYE. See How to register for PAYE on eFiling.
An employer who is registered or required to register with SARS for PAYE and/or Skills Development Levy (SDL) purposes, is also required to register with SARS for the payment of Unemployment Insurance Fund (UIF) contributions to SARS. You can register once for all different tax types using the client information system.
Top Tip: The Employment Tax Incentive encourages employers to employ young workers by providing a tax incentive to the employers. Read more.
The amount withheld and paid by the employer to SARS is applied as a prepayment of income taxes and is refundable if it exceeds the income tax liability determined upon filing individual income tax returns.
The amounts deducted or withheld must be paid by the employer to SARS on a monthly basis, by completing the Monthly Employer return (EMP201). The EMP201 is a payment return in which the employer declares the total payment together with the allocations for PAYE, SDL, UIF and/or Employment Tax Incentive (ETI), if applicable. A unique Payment Reference Number (PRN) will be pre-populated on the EMP201 and will be used to link the actual payment with the relevant EMP201 payment declaration.
It must be paid within seven days after the end of the month during which the amount was deducted. If the last day for payment falls on a public holiday or weekend, the payment must be made on the last business day before the public holiday or weekend.
1 | Are you on the latest version of your Payroll Software? | Y |
2 | Have you reinstated your employees on maternity leave? | Y |
3 | Have you cleared all exceptions? | Y |
4 | Have you done your February payroll run? | N |
5 | Have you printed your monthly statutory reports? | Y |
6 | Have you made a backup of your February period? | Y |
7 | Have you done a pay period update into year end? | Y |
8 | Have you checked your exception report again to make sure it is still clear? | Y |
9 | I have rolled over from year end to March
| Axiomatic N |
10 | Have you Re-terminate the employees on maternity leave (if any)? | N |
11 | Have you installed a new legislative upgrade and ran a legislative release? | N |
12 | Have you installed the latest version of E@syfile? | Y |
13 | I have opened my year end copy company and checked exceptions reports | Y |
14 | I have generated my electronic certificates
| Y |
15 | I have imported my IRP5.21 file into E@syfile | Y |
16 | I have successfully submitted the EMP 501 to SARS via E@syfile | Y |
A Warning Exception won’t stop you from generating and/or importing your IRP5 Electronic certificates. You will not need to clear this exception as it is merely there to notify you of a change.
All transactions on the Exception Report that don’t have the word WARNING in front of the exception need to be cleared in order to generate your IRP5 Electronic certificates.
It is important to note, that your IRP.# may be generated once all exceptions are cleared, but can still be rejected by E@syfile.
In this case, view and export the error report which will contain the Employee Code and detailed error to be rectified before the file is imported.
One error will prevent your entire file from being imported into E@syFile.
Be diligent.
This exception is merely a warning to notify you that code 3615 will no longer display on a director’s IRP5. The income that has been entered on transaction code 5007 (Directors Remuneration) during your periodic processing will be added to Tax Total 3601 and will no longer display under Tax Total 3615 on the employees IRP5. As a Warning Exception it won’t stop you from generating and/or importing your IRP5 Electronic certificates. You will not need to clear this exception as it is merely there to notify you of this change.
In the 2019 tax year, certain council contributions became taxable – therefore Payroll Software Systems created fringe benefits to align with this new legislation.
As each council is different, the resolution for each council is different. Please review the applicable Main Agreement Amendment and council resolution guide for a resolution and apply it accordingly to your benefit and deduction lines.
This exception is due to the fact that not all of your income codes are equal to correct tax total.
This exception can be due to various reasons, like a transaction template being setup incorrectly or a discrepancy in the database tables.
NOTE: In order to attempt any of the below resolutions, your employees will have to have a status of on Not Processed, so if your employees are processed you will have to do a clear run flags.
The standard transactions in Pastel Payroll have been pre-set with their own relevant tax totals, so they shouldn’t be the cause of this exception. You will have to double check that all your custom templates have been setup for the correct Tax Totals.
TIP: Usually tax totals for incomes will consist out of two codes. 3699 OR 3696 will be one of these codes. Both cannot be selected. In most cases you shouldn’t have more than two tax totals of the same type on a transaction – please confirm with your tax practitioner for more information.
Rebuilding database entries:
We would advise that you make a backup, complete a Pay Period Update into the next period and then run a rebuild totals.
This exception states that the total value that has been paid by the company toward your medical aid does not match the fringe benefit of that value. Therefore the total amount and year to date amounts on 9090 and the total amount on 6172 does not match.
NOTE: If you are doing your Bi-Annuals or Year End submission you will need to be in August (Bi-Annuals) or February (Year End) to do this correction. If you are not in these periods, you can restore a backup to these periods but remember you will need to then recapture all of the months between the month you are restoring to and the one you are currently in.
If code 9090 has a total of let’s say R10000, but code 6172 has a total of R9000 and according to your records transaction code 6172 was processed incorrectly in one month, then you will need to fix code 6172 in your current period:
The difference between these two amounts are (R10000-R9000) a R1000.
As According to your records 6172 is wrong, you will have to change the current value of 6172 in order to increase your YTD to the amount that matches 9090.
You will make a note of the current amount for 6172 (Example a R500) then click on the override box next to code 6172 on the benefits tab. You will now add the amount that 9090 and 6172 differs with to the current amounts value (so 6172 will change to R1500). This will push your YTD value for transaction 6172 up to R10000 that matches the YTD value on transaction 9090.
In an example where the code 9090 is the wrong amount:
If code 6172 has a total of let’s say R10000, but code 9090 has a total of R9000 and according to your records transaction code 9090 was processed incorrectly in one month, then you will need to fix code 9090 in your current period:
In the current period, you will navigate to the Process, Payslip screen of the employee in question.
This exception states that there are transactions linked to the calculation total “Retirement Funding Income” with negative amounts where the cumulative negative total for these transactions exceeds the cumulative positive total of the transactions with positive amounts linked to this calculation total.
NOTE: A progress indicator will run through. If this does not clear the exception, your employee probably has a RFI profile. If this is the case, you will have to add the negative income code to your RFI profile with the same percentage as your Basic Salary.
TIP: The negative income transaction (code 5020, 5018 or 5014 etc.) must always match the RFI or Non-RFI of the basic salary used. If both are the same, please check if the employee has an RFI Profile, and make sure to add this code to the profile.
This exception states that there are transactions linked to the calculation total “Non-Retirement Funding Income” with negative amounts where the cumulative negative total for these transactions exceeds the cumulative positive total of the transactions with positive amounts linked to this calculation total.
NOTE: A progress indicator will run through. If this does not clear the exception, your employee probably has a RFI profile. If this is the case you will have to add the negative income code to your RFI profile with the same percentage as your Basic Salary
TIP: The negative income transaction (code 5020, 5018 or 5014 etc.) must always match the RFI or Non-RFI of the basic salary used. If both are the same, please check if the employee has an RFI Profile, and make sure to add this code to the profile.
This problem was mostly due to the fact that unpaid leave was processed, where the client used a different code for the basic salary that was not code 5000, 5001 or 5002. Because the transaction used for basic salary was not ticked for this tax total, but unpaid leave was, it created a negative of the total for 7008.
If you are doing your Bi-Annuals or Year End submission when you get this error/exception you will need to Restore back to the last period for that reporting phase. The last period will be August (Bi-Annuals) or February (Year End) to do this correction. If you restore you will need to then recapture all of the months between the month you are restoring to and the one you are currently in.
If this employee does not have medical aid and the codes have been processed in error, this will need to be reversed on the payslip.
If you wish to not restore a backup and rather have a consultant do a data fix for you.
This exception states that the total value that has been paid by the company toward your pension fund, but the fringe benefit was never processed.
If you are doing your Bi-Annuals or Year End submission when you get this error/exception you will need to Restore back to the last period for that reporting phase. The last period will be August (Bi-Annuals) or February (Year End) to do this correction. If you restore you will need to then recapture all of the months between the month you are restoring to and the one you are currently in. If you do not wish to recapture, then you can have a chargeable data fix done.
If the code 6410 does not populate with a value, please check the Setup of the funds tab on this employees Edit, Employee Masterfile screen.
NOTE: It is important to note that 6410 won’t automatically back calculate. If you are only adding in this code in the August/February period, but you have been using it from the March period, you will have to override the amount on the benefits tab and calculate what the value should be in order to take in all of the months from March up to the current period.
This exception states that the total value that has been paid by the company toward your Provident fund, but the fringe benefit was never processed.
If you are doing your Bi-Annuals or Year End submission when you get this error/exception you will need to Restore back to the last period for that reporting phase. The last period will be August (Bi-Annuals) or February (Year End) to do this correction. If you restore you will need to then recapture all of the months between the month you are restoring to and the one you are currently in. If you do not wish to recapture, then you can have a chargeable datafix done.
NOTE: If this is for a Terminated employee, you will have to either restore back to the period that the employee was terminated in and recapture, exclude the employee from the IRP5 export and create a manual IRP5 in the e@syfile system for the employee, or reach out to your business partner to get a data fix done.
NOTE: It is important to note that 6411 won’t automatically back calculate. If you are only adding in this code in the August/February period, but you have been using it from the March period, you will have to override the amount on the benefits tab and calculate what the value should be to take in all of the months from March up to the current period.
If you wish to not restore a backup and rather have a consultant do a data fix for you, you can make a booking using the online platform here.
TIP: If this is for a Terminated employee, you will have to either restore back to the period that the employee was terminated in and recapture, exclude the employee from the IRP5 export and create a manual IRP5 in the e@syfile system for the employee, or reach out to your business partner to get a data fix done.
If you are doing your Bi-Annuals or Year End submission when you get this error/exception you will need to Restore back to the last period for that reporting phase. The last period will be August (Bi-Annuals) or February (Year End) to do this correction. If you restore you will need to then recapture all of the months between the month you are restoring to and the one you are currently in. If you do not wish to recapture, then you can have a chargeable data fix done.
If the codes have been processed incorrectly and this employee does not have medical aid these codes will have to be removed from the payslip. Click on the deductions tab. Click on the code 8000. Click to override checkbox and make the period value for 8000 a zero. Make a note of the YTD (Year to Date) value. Process a negative YTD (year to date) of code 8000 under period amount. If the nett salary has already been paid to this employee, you will have to counter the amount processed on code 8000 against code 8005. Changing the amount of 8000 will change the PAYE amount on your EMP201 and you will have to file for a correction.
NOTE: If the initial amount processed on the code 8000 was a negative, you will have to process the corrective value as a positive. If this person is terminated a data fix can be done to correct this exception at a chargeable fee. You can make a booking using the online platform here.
This is an exception on your Statutory Exception report that needs to be corrected before you can continue with your Bi-Annual or Year End process.
This is caused by the transaction 5540 (Reimbursive travel non-taxable) being processed along with the code 5501 (Travel Allowance) or 5520 (Reimbursive travel taxed on assessment).
If you are doing your Bi-Annuals or Year End submission when you get this error/exception you will need to restore back to the last period for that reporting phase. The last period will be August (Bi-Annuals) or February (Year End) to do this correction. If you restore you will need to then recapture all of the months between the month you are restoring to and the one you are currently in. If you do not wish to recapture, then you can have a chargeable data fix done.
Example:
The code 5540 has an amount of R200 in the period amount on the income tab and an amount of R1500 in the YTD tab. Make the period amount a 0 and your YTD would have changed to R1300. You will now capture an amount of –R1300 (Negative R1300) in the period value tab that will change your YTD to 0.
You will now add the code 5520 to the income tab and process the amount or R1300 in the period value.
Note: If this person is to receive Reimbursive Travel in this period you will have to add it to the amount on 5520.
If this is due to a Bi-Annual/Year End Exception and you wish to not restore a backup and rather have a consultant do a data fix for you, you can make a booking using the online platform here.
TIP: If this is for a Terminated employee, you will have to either restore back to the period that the employee was terminated in and recapture, exclude the employee from the IRP5 export and create a manual IRP5 in the e@syfile system for the employee, or reach out to your business partner to get a data fix done.
You have been processing SDL but during the year your company has become SDL exempt.
NOTE: If you are in March or your first processing period – please ensure that you have checked the SDL Exempt has been checked. This will ensure that even if transaction code 9150 is on the payslip it won’t calculate a value.
How to remove the SDL if the transaction code has been processed throughout the year:
TIP: If you are removing this for a Bi-Annual submission, please restore the August backup and recapture the periods in between. If you are removing this at year end for the entire year, please restore the February backup and redo the Year End Company if necessary. If you restore you will need to then recapture all the months between the month you are restoring to and the one you are currently in. If you do not wish to recapture, then you can have a chargeable data fix done.
NOTE: Roll over into the next period and ensure that you tick SDL Exempt by navigating to Setup, Company Parameters. Click on the statutory tab (remove the SDL Reference number if applicable) and check SDL Exempt.
Session 2 SO 2 |
Reconcile balances to produce year-end returns. |
Learning Outcomes (Assessment Criteria) | Cumulative pay records are reconciled to year-end balances. Totals of statutory returns are calculated and reconciled as per requirements. The value of pension deductions from each employee by way of basic, supplementary and Actuarial Value Calculations (AVC) contributions is totaled and reconciled with cumulative net taxable pay prior to completion of year-end returns to the South African Revenue Services. The value of taxable benefits is identified and collated correctly. Internal year-end summaries required for accounting purposes by management are completed in an accurate and timely manner. |
Session 3 SO 3 |
Complete and submit year-end returns. |
Learning Outcomes (Assessment Criteria) | All statutory and non-statutory year-end returns are completed accurately. All statutory and non-statutory year end returns are dispatched to outside bodies by due dates Year-end information for employees is submitted accurately by the statutory dates. Year-end information for employees is calculated accurately and made available by the applicable statutory date. |
The definition of Reconciliation: “an accounting process that compares two sets of records to check that figures are correct and in agreement. Account reconciliation also confirms that accounts in the general ledger are consistent, accurate, and complete.”
End