Odoo 20 brings South African payroll localisation into the ERP, giving local businesses another reason to reconsider running separate HR, payroll and accounting systems.
For South African businesses looking at Odoo, there has always been a fairly predictable conversation around payroll.
You could run your CRM, Sales, Purchasing, Inventory, Manufacturing, Accounting, HR and Leave in Odoo, but payroll would often remain in a separate South African payroll package.
For some companies that worked perfectly well. For others, it meant maintaining another system, keeping employee information in more than one place and then getting the payroll results back into Accounting every month.
Odoo 20 changes that conversation.
AP Systems has received confirmation directly from Odoo that the South African payroll localisation is ready for Odoo 20.
That means we're no longer talking about whether South African Payroll is coming to Odoo. We can start looking at whether it makes sense for South African companies to actually use it.
And that's a much more interesting discussion.
Why Would You Move Payroll Into Odoo?
We wouldn't recommend replacing an established payroll system simply because Odoo now has a South African localisation.
There needs to be a reason.
For many companies, that reason will be integration.
Take a business already running Odoo for Accounting and HR.
Employee details are in Odoo. Leave is being requested in Odoo. Contracts and working schedules may already be maintained there.
Then, once a month, payroll is processed somewhere else.
The payroll information ultimately has to find its way back into Odoo Accounting.
That works, but it isn't particularly elegant.
With South African Payroll available in Odoo 20, businesses can start considering a much more integrated process:
Employees → Contracts → Leave → Attendance/Work Entries → Payroll → Accounting
That's the part we think has real commercial value.
It isn't about having another application inside Odoo. It's about potentially removing an application outside it.
Could Odoo Replace Your Existing South African Payroll Package?
For some businesses, potentially yes.
But we'd look at the existing payroll before answering that question.
South African payrolls can become complicated very quickly.
A business may have straightforward monthly salaries, or it may have hourly-paid employees, overtime, shifts, commissions, bonuses, allowances, company contributions, deductions and benefits.
A manufacturing business with 300 employees can have a completely different payroll requirement from a consulting company with 30 salaried staff.
That's why the first step shouldn't be installing the Payroll module.
It should be understanding the existing payroll.
At AP Systems we'd want to look at the earnings and deductions being used, employee categories, contracts, working schedules, leave, attendance requirements, overtime and the way payroll currently feeds into Finance.
Then we can establish how those requirements should work in Odoo 20.
PAYE, UIF and SDL Are Obviously Part of the Conversation
Any South African company evaluating payroll software is going to ask about PAYE, UIF and SDL.
And rightly so.
South African payroll localisation isn't useful if it doesn't address the local statutory environment.
Odoo's payroll localisation framework is specifically designed to adapt Payroll to country requirements, while the South African localisation brings that approach into Odoo 20 for local companies.
But we'd still validate the customer's actual payroll before going live.
If the current payroll calculates an employee's net salary as R28,742.36 and Odoo produces a different result, we're not going to assume the new system is right simply because it's Odoo.
We're going to find the difference.
It could be configuration.
It could be a benefit.
It could be an allowance.
It could be the way something was configured in the old payroll.
Whatever the reason, it needs to be understood before that employee gets paid.
That's why we'd normally expect parallel payroll testing to form part of a migration.
Run the existing payroll.
Run Odoo.
Compare them.
Investigate the differences.
Then move across once the results have been properly validated.
Where We Think This Gets Particularly Interesting
Manufacturing, distribution and other employee-intensive businesses are likely to be worth looking at closely.
These businesses don't necessarily have a simple workforce.
There may be office employees, factory workers, warehouse staff, supervisors and managers all interacting with the business in different ways.
Some are salaried. Some may work shifts. Others may have overtime or different working schedules.
Odoo may already be running Manufacturing, Inventory, Maintenance, Quality, Planning, Leave and Attendance for the same company.
Putting Payroll into that environment potentially removes another boundary between the factory floor, HR and Finance.
It also ties into another significant Odoo 20 change: Light Users.
Not every employee needs the same level of Odoo access as the financial manager or sales team.
The combination of Odoo 20 Light Users and South African Payroll therefore becomes particularly interesting for businesses with larger workforces.
Instead of asking, “How many office employees need an Odoo licence?”, we can start looking at how the wider workforce should interact with the ERP.
That's a different conversation.
The Accounting Side Could Be Just as Valuable
One of the first things we'd look at during an implementation is what currently happens after payroll is completed.
How does Finance get the information?
Is there an integration?
Does somebody import a file?
Is a journal generated?
Or does somebody receive a payroll report and manually capture the totals?
There's nothing inherently wrong with an external payroll system feeding an ERP. We've built and worked with plenty of integrations where that approach makes sense.
But every separate system creates another hand-off.
If Payroll and Accounting are both operating inside Odoo, there's an opportunity to simplify that process.
For a financial manager evaluating Odoo 20, we'd therefore look beyond the payslip.
The better question is:
What work disappears from Finance if payroll is moved into Odoo?
That's where the business case starts becoming measurable.
When Would We Keep an Existing Payroll System?
This is equally important.
If your existing payroll works well, handles a particularly complicated requirement and already integrates cleanly with Odoo, replacing it may not be the first project we'd recommend.
There's no prize for having every possible module running in one system.
The change needs to produce a benefit.
That might be lower system costs.
It might be less duplicate capturing.
It might be better integration with HR.
It might simplify the accounting process.
Or it might allow the business to retire an ageing payroll system it was going to replace anyway.
For a new Odoo 20 implementation, however, we'd certainly evaluate Odoo Payroll before automatically specifying a separate payroll package.
That's probably the biggest change for us.
Previously, a separate South African payroll product could almost be treated as a given.
It shouldn't be anymore.
What Would an Odoo Payroll Migration Actually Involve?
This is where the project becomes more practical than the marketing material.
We'd start with the current payroll, not Odoo.
We need to understand how people are currently being paid and why.
That includes employee information, salary structures, earnings, deductions, benefits, leave, working schedules, overtime and whatever other rules apply to that company.
Then we'd configure the equivalent process in Odoo 20 and test it.
Historical information also needs to be considered. Companies need to decide what payroll history needs to be brought across, what can remain archived in the previous system and what opening information is required for the new environment.
The cutover date matters too.
Changing payroll halfway through a reporting period or tax year can introduce considerations that don't exist with a clean start.
There isn't one migration plan that suits every business.
A 20-person company with straightforward monthly salaries is not the same project as a factory with several hundred employees.
Does Odoo 20 Payroll Make Financial Sense?
That's something we can now assess as part of the wider Odoo business case.
Don't only compare the price of one payroll package with the price of another.
Look at the whole process.
What are you paying for the existing payroll software?
Is there an integration that has to be maintained?
How much duplicate employee administration takes place?
Does Finance have manual work after every payroll run?
Is leave maintained in another system?
Is attendance somewhere else again?
How much time is spent reconciling information between those systems?
Sometimes the existing payroll package will still make sense.
In other cases, moving payroll into Odoo could remove software, integration and administrative costs that aren't obvious when you only compare licence prices.
Does Odoo 20 Have South African Payroll?
Yes. AP Systems has received confirmation directly from Odoo that the South African payroll localisation is ready for Odoo 20.
The more important question for a business is whether its particular payroll requirements are suitable for an Odoo Payroll implementation.
That's something we'd establish through a payroll assessment rather than making assumptions based purely on employee numbers.
Can Odoo Payroll Work With Odoo Accounting?
Yes. This is one of the main reasons we see value in bringing Payroll into the Odoo environment.
Payroll isn't an isolated process. The financial consequences eventually need to be reflected in Accounting, so having the two processes within the same ERP can remove some of the integration and manual work associated with separate systems.
Should Existing Odoo Customers Move Their Payroll?
Not automatically.
We'd look at what the existing payroll does, how much it costs, how well it integrates with Odoo and what problems the business is actually trying to solve.
If there isn't a meaningful benefit to changing, leave it alone.
But if the company is already trying to consolidate systems, improve HR integration or remove manual payroll-to-accounting processes, Odoo 20 South African Payroll is now worth evaluating properly.
What This Means for Odoo in South Africa
We think South African Payroll fills an important gap in the Odoo offering.
For years, we've been able to show businesses how Odoo can connect Sales, Purchasing, Stock, Manufacturing and Accounting.
HR could sit in the same environment too.
Payroll was frequently the system sitting on the outside.
With Odoo 20, we can now have a very different discussion with a South African customer:
Do you actually need a separate payroll system anymore?
Sometimes the answer will still be yes.
Sometimes it won't.
Our job at AP Systems is to work that out before changing anything.
For businesses implementing Odoo 20, or existing Odoo customers considering an upgrade, we'd now include South African Payroll as part of that assessment.
Not because it's another new Odoo feature.
Because if it allows the business to remove another standalone system, eliminate duplicate work and bring HR, Payroll and Accounting closer together, there's a real business case for looking at it.
Considering Odoo 20 Payroll?
If you're already using Odoo and want to understand whether your existing South African payroll can be moved into Odoo 20, AP Systems can assess the current payroll, integration requirements and Odoo environment before recommending a migration approach.
For businesses considering Odoo for the first time, Payroll can now be included when designing the wider ERP solution rather than automatically being treated as a separate system.Start writing here...