Employee advances: from request to deduction
Every company gives advances, and most manage them on a slip of paper in a drawer or a WhatsApp message. The problem shows up two months later: the employee remembers paying two instalments, the accountant remembers one, nobody knows exactly what is left, and the advance given to somebody who has since resigned was never recovered. The answer is not stricter rules — it is making the advance a record with a schedule that deducts itself.
The idea in a minute
While it is outstanding, an advance is recorded as money owed to the company, not as an expense. It only becomes an expense if you decide to write it off.
How it works
- 1
1. A request with a number and a reason
The advance is recorded as a request with its amount, date and reason, and gets its own number. So instead of “he took five thousand last month”, there is a record saying who, how much, when and why — which ends the arguments before they start.
- 2
2. Approval before the money moves
The request waits for approval, and can be rejected with a written reason or cancelled. Disbursement only happens after approval, so money never leaves the treasury on the strength of a conversation. And the record keeps who approved it and when.
- 3
3. An instalment schedule from day one
As you record the advance you set how many months it is spread over and when the first deduction falls. The system builds the schedule: every instalment with its date and amount. So the employee knows up front how much comes off and for how long, and the company knows when the money returns.
- 4
4. The deduction happens with payroll, by itself
When you run the month's payroll, the system pulls the instalments due in that period and adds them as a deduction on the payslip — including any shortfall carried over from earlier months. Nobody has to remember, and nobody checks a schedule on the side. The payslip names the deduction and its advance number, so the employee sees why the money came off.
- 5
5. Net pay can never fall below zero
A month with a lot of absence can make deductions exceed the salary. Zemam caps deductions at gross pay — an employee never ends up owing the company their own wages. And the order is deliberate: statutory withholding and absence adjustments are taken first, and the advance instalment is the first thing to give way.
- 6
6. An instalment that could not be taken is not lost
When an instalment cannot be taken in full, what was deducted is recorded and the remainder stays open on the schedule to be picked up next month. So the company does not lose its money and the employee is not squeezed beyond what one month can carry.
In short
An advance is money owed to the company, not an expense — which keeps your profit honest.
An instalment schedule with a date and amount for each, known to the employee from day one.
The deduction happens with payroll automatically and shows on the payslip with the advance number.
Net pay never falls below zero, and a short instalment stays open for next month.
Why this matters
Your profit is not distorted
If advances are booked as expenses, a month with a lot of them looks like a loss — and it is not one. The money is with your staff and it is coming back.
Nobody leaves with a forgotten advance
What each employee still owes is a number available at any time. So at end of service you can settle it, instead of discovering a month later that an advance was never recovered.
The employee is reassured
What worries an employee most is not knowing how much will be taken. A clear schedule and a payslip that names the deduction put an end to that.
Management decides on numbers
Seeing total outstanding advances lets you set a policy with numbers: a cap per advance, a maximum number of instalments, or a temporary pause if the total has grown too large.
Are your advances on a slip in a drawer?
Talk to us and we'll walk you through the whole cycle — request, approval, disbursement and a schedule that deducts itself from payroll.