Payroll you can explain to the person asking

Payroll has an unusual property: a small error is a large problem. A one percent mistake in a stock report is noise. A one percent mistake in someone salary is a conversation, and the conversation is not really about the money - it is about whether anyone can explain where the number came from.

Store how it was calculated, not just the result

The temptation is to store the net figure and recalculate the detail on demand. It does not work, because by the time anyone asks, the inputs have moved: the salary was raised, the policy changed, the attendance record was corrected. Recalculating in November produces a different answer than the one paid in March, and both are defensible, which is the worst outcome.

So a payslip should record its own derivation at the moment it is produced: the base used, the days counted, each allowance and deduction with the rule that generated it, and the rates in force. That record is then frozen. It is not a report of how the calculation would run today; it is a statement of how it ran.

Proration is where the disputes live

An employee who joined on the 10th, or took unpaid leave, or left mid-month, is paid for part of a month - and nearly every argument about payroll is an argument about how that part was measured. Thirty days, or the actual days in the month? Working days or calendar days? Are weekends inside an unpaid period deducted?

There is no universally correct answer, but there is a correct practice: pick a rule, write it down where employees can read it, and apply it identically every time. A system that uses calendar days in one place and working days in another will produce two defensible numbers for the same month, and no way to say which is right.

Watch the rounding, too. A daily rate is a division, and a month built from rounded daily rates does not always add up to the monthly salary. The difference is small and extremely visible to the person receiving it.

Deductions need a start date

A loan instalment, a benefit contribution, a disciplinary deduction - each applies from a date, not forever. A deduction with no start date applies to historical payslips if anyone ever reruns one, and that is how a closed month changes after the fact.

The ledger side, and why it should be optional

Payroll produces journal entries: salary expense, accrued liabilities, the employer share of contributions. For businesses with an accountant inside the system, posting automatically is right. For businesses whose accountant works outside it, automatic posting produces entries nobody expected and a trial balance nobody recognises.

Make it a deliberate setting, off until someone turns it on, and make the entries reviewable before they post. The cost of posting payroll into a ledger that was not ready for it is a cleanup across every period affected.

A practical test

Take a payslip from six months ago, hand it to the employee it belongs to, and see whether they can follow it line by line without help. If they cannot, the problem is not that they lack accounting knowledge. It is that the payslip is a result without a derivation, and a result you cannot check is a result you have to take on trust.