Payroll and compliance: why I built Émarge

Émarge came from a simple observation made in the field: in many private organisations in Benin, payroll relies on spreadsheets, goodwill and one person who knows every rule by heart. As long as that person is there, everything is fine. The day they leave, everything becomes fragile.

A process more complex than it looks

Fair payroll isn't just a base salary. It's recurring bonuses, hourly teaching sessions, advances to deduct without ever making net pay negative, leave, social security contributions and income tax withholdings. Every mistake costs money, time and, above all, trust.

Compliance as the foundation

I wanted the tool to follow Benin's Labour Code from the design stage: salary sign-off sheets, rules on advances, the employer register, contract durations. Legal parameters are versioned with their effective date and source. Nothing is hard-coded: when the law changes, you update a parameter, not the program.

What it changes day to day

• Payslips generated in a few clicks, printable and sent by email.
• Reports ready to file: payroll ledger, tax and social security declarations, annual summary.
• Contracts and certificates generated from each employee's record.
• Role-based access and an activity log, because salary data deserves real protection.

What I take away from it

Building Émarge reminded me of a rule I apply to every project: good business software starts from the reality of the people who use it, not from a feature list. The best decisions came from conversations with people who had been running payroll by hand for years.

Is your organisation still running payroll on spreadsheets? Write to me, I'd be happy to talk about it.