Journal entries problems

Since January 2019, workers in South Africa have been entitled to a minimum wage of R20 per hour, which translates to around R3,500, based on a 40-hour working week.
The new rules apply to all workers in South Africa, with the exception of National Defence Force, National Intelligence Agency and Secret Service employees, as well as volunteers.
Three other groups have different minimum wage standards. Farm workers are now entitled to a minimum wage of R18, domestic employees to R15, and workers on expanded public works programmes to R11.
Employers in South Africa can apply to be made exempted from the minimum wage for up to a year, though at this stage it's unclear as to the circumstances of when an exemption may be granted. If a company fails to pay the minimum wage (without an exemption being granted), they'll face significant fines.
The wage will be reviewed each year to assess whether it's having the desired effect on alleviating poverty and reducing wage inequality.

Under the category Vehicle Parts & Accessories, come on now, you've got to be kidding me(((((

You would need to ask an acountant.

How to Create in Payroll in Tally 9? Please Explain neatly

Firstly you need to determine/state whether you are using a database application, such as Access, MtSQL or MS SQL and programming them to do create this application, or are you using a programming development tool such as Visual Studio, ASP.NET, PHP or the like, as the solution and guidance will be different for each.
In terms of the data design, you should store the data necessary to identify each employee uniquely and each data point per employee needed to calculate their payroll. You should then store the generic (applys to all employees) such as tax rates, in separate tables and call on it to calculate wages and other paystub data.
For instance, the employee first and last names and tax ID should be a sufficient unique identifier. Create a table for just employees, their names, tax ID, start date, schedule, pay rate, number of deductions, direct bank payment data, etc., and whatever else you decide you need for each employee. You can calculate their wages by multiplying their rate by their schedule and applying the appropriate tax rate and medical/witholding deductions as you go, so calculated data does not need to be stored and consume database space. 
You'll likely need a separate table for common data such as tax rates, one for deductions/witholdings, one for holidays, one for vacation accrual rates, one for medical rates, etc. This data if common to employees does not need to be stored per individual, as that would cause redundant replication of data. If the employees are on an hourly rate, rather than a set salary/wage, then you'll need a table of worked hours per employee, akin to their timesheet data. If you use a timesheet/timecard, the entering and storing only the totals and keeping the physical timesheet for backup records should suffice.
Once you design and populate your database as suggested above, then it's a relatively-simple task of calculating the computed paystub data and storing the salient resulting datapoints for the record.
Consider a reporting application, such as Crystal Reports, for your printing needs, as its far easier to configure Crystal or similar product to format reports, paystubs, checks, etc., than coding these from scratch.
Hope this helps.

QuickBooks will set up both sides of a simple plan if you use the EZ set up.
OPen the payroll item list, click on Payroll item (at the bottom of the window) and then new item. Chose the EZ set up and it will walk you right through it. You can then go in and edit each item (employee and company) as you need to.

PS Please rate my answer as I am attempting to become a premium expert.

Thank you