The monthly payroll routine in Morocco: a repeatable method

Payroll does not go wrong on the calculation, it goes wrong on the variables. What is collected late gets corrected next month.

By BelloCommerce

·

September 10, 2026

Payroll rarely goes wrong on a rate. It goes wrong on an absence reported too late, a bonus agreed verbally, an advance forgotten. Most of the work happens before any calculation: it consists of freezing what changed during the month, on a date everybody knows. A month spent chasing variables produces a payroll that will need correcting the month after.

Preparing the monthly payroll at a desk.

The essentials in five points

The variable cut-off date is the structural decision: without it, payroll waits indefinitely for one last item.
Variables are collected, not guessed: absences, overtime, bonuses, advances.
Checking happens before issuing, on the differences from the previous month.
A correction is regularised, not hidden: an owned catch-up costs less than a gap found later.
Archiving is part of payroll: payslips, absence documents and proof of transfer.

1. Set the cut-off, and hold it

This is the one decision that genuinely changes payroll quality. While no date is fixed, every item arriving late pushes the whole thing back, and the social declaration in turn comes under pressure.

Choose a cut-off date for variables, around the 25th, and tell everyone.
Announce the rule: anything arriving after that date goes on next month’s payroll.
Issue and check the payslips in the last days of the month.
Pay salaries on the contractual date, without making it depend on the close.
Move straight on to the social declaration in the first days of the following month.

The second line holds the whole structure up. Deferring a late item to the following month is not a sanction: it is what lets you avoid ever holding up thirty people’s pay for one missing document.

The social deadline that follows does not move: it is set out in our guide to the CNSS declaration calendar.

2. The variables to collect

A variable is anything that is not base salary. Drawing up the list once and reusing it each month beats relying on memory, because it is always the same ones that go missing.

Absences: Leave taken, sickness, unjustified absence. Each has its own payroll treatment, and confusing them distorts both net pay and the leave counter.
Overtime: The number of hours and the uplift. They must appear separately on the payslip, not folded into base salary.
Bonuses and gratuities: Agreed during the month, each raising the question of whether it is subject to contributions.
Advances and deductions: Salary advances, attachments, staged repayments. They carry from month to month and must be cleared.
Staff movements: Arrivals and departures with their exact dates, which govern the month’s apportionment and the declaration.

The last line deserves particular attention because it reaches beyond payroll: an arrival or departure with the wrong date propagates to the social schedule and the leave balance, where it is harder to put right.

3. Check before issuing

Useful checking is not recalculating every payslip: it is looking at what moved. A payroll run closely resembles the previous month’s, and that is precisely why the differences stand out when you look for them.

Check	What it reveals
C	o	m	p	a	r	e		t	o	t	a	l		g	r	o	s	s		w	i	t	h		t	h	e		p	r	e	v	i	o	u	s		m	o	n	t	h
A		f	o	r	g	o	t	t	e	n		b	o	n	u	s	,		a	n		a	r	r	i	v	a	l		n	o	t		e	n	t	e	r	e	d	,		a		d	e	p	a	r	t	u	r	e		n	o	t		r	e	m	o	v	e	d

Those four checks take about ten minutes and catch almost every error that would otherwise surface during an inspection or a departure. They beat an exhaustive review that nobody actually performs.

Never hold up the whole payroll for one missing variable

That is the reflex that delays the social declaration and, with it, triggers surcharges. A document that does not arrive in time is handled on the following month’s payroll, with an explicit regularisation line. Paying thirty people on time beats waiting for a sick note that may arrive tomorrow.

4. Regularise, archive, start again

An error found after issuing is regularised on the next payroll, with an explicit line. The temptation to compensate quietly by adjusting another item produces an unverifiable payslip and an extra difficulty the day somebody traces the history.

Archiving closes the cycle: payslips, absence documents, proof of transfer and filing receipts. These are the records establishing that salary was paid and deductions made; without them payroll happened but cannot be proved.

BelloPOS Pro handles staff and payroll — employee records, leave and payslips — which puts the routine on the variables rather than the arithmetic. The software does not collect absences for you: the discipline of the cut-off stays human, and it is what separates a calm payroll from a rescued one.

BelloPOS

All the features

Mistakes to avoid

Setting no cut-off date, which leaves payroll waiting for one last item every month.
Relying on memory for the variables rather than a list reused unchanged.
Folding overtime into base salary, which makes the payslip impossible to verify.
Quietly offsetting an error against another line instead of passing a visible regularisation.
Treating payroll as finished at the transfer, without archiving payslips and supporting documents.

Frequently asked questions

Which cut-off date should I choose?

Around the 25th suits most organisations: it leaves time to issue and check before month end, then to file in the first days of the next month.

What do I do with an absence reported after the cut-off?

Handle it on the following month’s payroll with an explicit regularisation. Deferring it is normal; handling it quietly by adjusting another line is not.

Should a second person check the run?

It is advisable once you have more than a few employees, if only on the differences. In a very small business, comparing with the previous month already plays that role.

How long should payroll records be kept?

As long as your other social and accounting records. They prove payment of salary, the deductions made and the rights the employee accrued.

What to take away

Set a cut-off for variables and hold it, collect from a list rather than from memory, check the differences before issuing, and regularise visibly rather than quietly. The calculation is almost never the problem; the collection almost always is.