Stipend arithmetic that survives a dispute

When a learner disputes a stipend, the useful question is not “what was the total?”. It is “show me the days, the rate and the rule that produced the total.” If the answer is a spreadsheet with a formula someone has since overwritten, the provider is negotiating from weakness.

Three inputs, one output

A defensible stipend calculation has three inputs:

1. Payable days — derived from the attendance and leave record, not typed in.
2. The applicable rate — the programme policy and the National Minimum Wage learnership floor for the period.
3. Adjustments — approved deductions, top-ups or post-lock corrections, each with a reason and an approver.

The output is a line-level breakdown. The total is the sum, not the starting point.

Payable days are the hard part

A month has calendar days, working days, public holidays and days the learner was absent with or without leave. Sectoral Determination 5 and the provider’s programme rules determine which days count. Public holidays move every year, and a provider with sites in different provinces can have different observed days.

This is why the calculation should be deterministic and stored with the run. Recomputing next year with a new holiday table must not silently change last year’s locked run.

The NMW floor

The 2026 National Minimum Wage determination (GN R.7083) sets learnership floor tiers. The engine applies the tier that matches the learner’s programme and year, then tops up if the calculated stipend falls below the floor. The top-up is a line, not a rounding adjustment.

The floor is a statutory minimum, not a target. A provider can pay more; the evidence should show the policy that produced the amount.

Lock, then adjust

A pay run should move through explicit states: draft, calculated, locked, paid. Locking creates an immutable snapshot. Corrections after the lock are new adjustment lines linked to the original run, with an approver and a reason.

This is also where separation of duties matters. The person who calculates the run should not be the only person who approves an exception above the configured threshold. Dual sign-off is not bureaucracy; it is the evidence that two people looked.

What to test

• Change one attendance day and confirm the calculation changes by exactly one payable day.
• Add a public holiday and confirm the run reflects the correct rule.
• Lock a run, then attempt to edit a line; the attempt should fail and be logged.
• Create a post-lock adjustment and confirm it appears as a linked line, not an overwrite.
• Export the bank file and confirm the reference matches the run.

The point

A stipend engine is not valuable because it calculates quickly. It is valuable because it can explain itself months later, to a learner, a finance manager or an auditor, without relying on the person who ran it.