Why Copying a Master Sheet Fails
Copying a payroll file from head office to three branch folders appears efficient. It is faster than typing. It is also the exact moment the business creates two versions of the truth.
The copies drift because of ordinary, unavoidable reasons:
- Adjustments happen locally. A staff member is absent, a duty allowance is claimed, someone leaves mid-month. The branch file changes. The master does not, because nobody sent an email.
- Staff lists diverge. A new hire in Lagos appears in the Lagos file. Does anyone add them to the master? Usually not until the next pay run, when the amount is wrong.
- Different allowances, same title. A driver in Port Harcourt and a driver in Lagos are not paid the same. If the master encodes one number, one branch is always wrong.
- The approver differs. A branch manager approves their own staff. That is normal and reasonable, but the control only works if the approval is recorded rather than assumed.
- Nobody reconciles. At month end, nobody compares branch files to the master, because comparing them takes longer than the error takes to become permanent.
|
Key Takeaway: The problem is not that people are careless. It is that copying creates two records and no reconciliation step. Any system without the reconciliation step will drift, regardless of how careful the people are. |
The Seven Components of a Working Multi-Branch Payroll
1. One staff record per person
A single record holding identity, role, branch, start date, salary structure and status. Not a copy in each branch. One record, with branch as an attribute. When someone transfers from Lagos to Abuja, you change one field and every past pay run still makes sense.
2. Branch as structure, not as filename
Branches should exist in the system as entities, with configuration and cost centres attached. A branch that exists only as a folder name cannot hold a budget, cannot be measured, and cannot be blocked from approving its own errors.
3. Structured earnings and deductions
Salary is not one number. Base, housing, transport, duty, utility, and whatever your policy actually says, defined as named components per role. Ad hoc deductions need a reason code. Without reason codes, a deduction list is a list of accusations.
4. Time and attendance that feeds payroll
Leave, absence, lateness, overtime. This does not need to be a biometric system. It needs to be a record that the payroll run can read, so that adjustments are inputs rather than manual corrections applied after the fact.
5. Approval with a named approver
Each branch approves its own staff, and the approval is recorded: who, when, for whom, at what amount. The person who prepares the run and the person who approves it should not be the same person at branch level. This is the cheapest internal control you will ever install.
6. Payments recorded against the run
Once paid, the run is closed and the amounts are recorded. The finance team can then reconcile payroll to the bank outflow and to the ledger, in the same way they reconcile any other payment.
7. A single report across all branches
The whole point. One view of total payroll cost, headcount and variance by branch and by month, computed from the recorded data rather than assembled from files.
|
Key Takeaway: Component seven is the reason to do this. Once the data is recorded properly, a consolidated payroll report is a click, not a fortnight of copying. |
What Changes When Payroll and Branch Structure Are Connected
|
Question |
Three Branch Folders |
Connected System |
|
What is total payroll cost this month? |
Add three files, hope they agree |
One report, by branch and by month |
|
Who took a deduction and why? |
Check the note column, if it exists |
Reason code recorded at entry |
|
How many staff does each branch have? |
Count rows in three files |
Headcount from live staff records |
|
Who approved this run? |
Whoever signed the email |
Named approver with a timestamp |
|
Did Lagos headcount change since last month? |
Compare two files by eye |
Movement report from the staff ledger |
|
What is the variance against budget for Abuja? |
Manual comparison |
Computed from branch budget lines |
|
Can a leaver's final pay be reconstructed? |
Assemble from emails |
Staff record history with pay runs |
|
Key Takeaway: Notice what did not appear in the right-hand column: anything about biometric devices, or attendance hardware. Structured records beat clever hardware almost every time in a first payroll migration. |
The Order to Do It In
If you are doing this yourself, with or without software, the sequence matters. Doing it in the wrong order is how people end up paying twice.
1. Clean the staff list first. One row per person, with branch and status. Reconcile it against the bank instructions and the last pay run. Do this before touching structure.
2. Define your earnings components. Write them down. Every allowance gets a name and, if it varies, a rule.
3. Set one approver per branch, with a deputy. Record the appointment somewhere durable.
4. Run one month in parallel. Old method and new method side by side. Compare totals line by line before you trust the new one.
5. Cut over only when the parallel run agrees, and keep the old files as read-only archive, not as a live alternative.
6. Add the reports last, once the data is right. Reporting on wrong data produces confident nonsense.
|
Key Takeaway: Payroll migrations fail on data, not on software. One clean staff list, one agreed set of components, one named approver per branch, and one parallel run is the whole method. |
The Honest Limit
We are not going to pretend payroll software settles labour law questions, contract drafting or tax treatment. Those need professionals who know your specific situation, and no platform replaces that advice.
What a system does reliably is make the arithmetic consistent, make the approval visible, and make the result reproducible six months later. In a business with three branches, that is most of the risk, and it is the part that spreadsheets genuinely cannot deliver.
What to Do This Month
1. Print your current staff list. Find the people who appear twice, and the people who left but are still being paid. Those two errors pay for the rest of the exercise.
2. Write your earnings components on one page. If you cannot, payroll is being calculated from memory.
3. Name one approver per branch and one deputy.
4. Total your last three months of payroll by branch. If the three months tell the same story, good. If the branch numbers jump around for no visible reason, you have found the leak.
5. Decide what *consolidated payroll reporting* will need to answer, then build only what answers it.
|
Key Takeaway: You do not need a payroll transformation. You need one staff list, one component list, one approver per branch, and one consolidated report. The rest is detail. |
|
SEE IT IN ACTION estatixX is a Real Estate ERP for Nigerian developers, property managers and brokerages: four connected portals covering estate and plot inventory, subscriber lifecycle, invoicing and receipts, treasury and voucher approvals, payroll, projects and tasks, marketer networks, role-based access and audit logs. Visit estatixx.com and book a demo. We will show you one consolidated payroll report across every branch. https://estatixx.com |
