One Market Maintained, the Rest Configured
Payroll here is maintained for one market and configurable for every other. Those are not two grades of the same feature — they are different products, and the difference is who is responsible on the day a rate changes.
Every payroll vendor will tell you they support your country. The word doing the work in that sentence is "support", and it means at least three different things.
The position, stated first
One market is maintained: the rules are ours to keep current. Everywhere else the engine is configurable and the rules are yours. Both are legitimate products; only one of them is what most buyers hear. If you are outside the maintained market, budget for somebody owning those rules — that is the real cost, and it recurs.
Three meanings of "supported"
What each one commits the vendor to
Claim Who owns the rule
Maintained The vendor
Rates, bands and thresholds are kept current by whoever sells you the software. When a budget changes them, an update arrives. This is the expensive promise and very few vendors make it for many countries.
Configurable You
The engine can express your rules and somebody has to enter them and keep them right. Perfectly workable, and it is a recurring job rather than a setup task.
Filed Nobody, here
The figures are computed and a person submits them. This product does not transmit a payroll return anywhere, including in the maintained market.
A vendor saying "we support forty countries" is almost always making the second claim. The question that separates them is: when the rate changes next year, who changes it?
The question is not whether the software can express your rules. It is who is at fault when it expresses last year's.
What configurable actually asks of you
More than a setup afternoon, and the recurring part is what people underestimate.
-
Somebody has to know the rules
Not approximately. Bands, thresholds, ceilings, reliefs, which components are subject to what, and how rounding is handled. This is a named person's responsibility or it is nobody's.
-
Somebody has to notice when they change
The software will not. There is no feed, no alert and no update that arrives on its own for an unmaintained market. A rate that changed in a budget six months ago is still whatever you entered.
-
Somebody has to enter them without breaking history
Changing a rate must not restate payslips already issued. Rule sets are versioned in intent here — a rule version referenced by a payslip is meant to be fixed — and that is the property to test before you rely on it.
-
Somebody has to check the first run against a known-good calculation
Once, properly, by hand, for a handful of employees across the band boundaries. This is the step that gets skipped and it is the only one that finds a misconfiguration before an employee does.
And it stops short of submission everywhere
Worth stating plainly, because it is true even in the maintained market: this product computes payroll figures and does not submit them. There is no portal integration for any authority anywhere.
What differs is the file. In the maintained market a calculated run now produces the return files — in the published layout for two of its three authorities, and as a schedule to work from for the third, which publishes no upload layout we could verify — carrying the scheme identifiers held on each employee record, with a readiness list naming anybody whose number is missing — and somebody uploads them. Everywhere else the output is an export that somebody works from and reshapes into whatever their authority accepts. An earlier version of this page said the identifiers were not stored at all; that came from an audit that searched two legacy columns rather than the store that replaced them, and it was wrong.
The payroll chain, and where the product stops
| Step | Maintained market | Everywhere else |
|---|---|---|
| The engine computes | Yes | Yes |
| The rules are kept current for you | Yes | No |
| Rule changes arrive as an update | Yes | No |
| Scheme identifiers are stored | Yes | Yes |
| A prescribed return is produced | Yes | No |
| The return is submitted | No | No |
Built and maintained Configurable by you, not maintained by us Not built
Three rows differ, and the last is identical everywhere — the submission stays yours even in the maintained market, which is the part most evaluations never reach.
Two, and the first is how the maintained market came to exist
A maintained market is not a technical achievement, it is a standing commitment. That is why it is commissioned rather than assumed.
Your market, maintained
The rule set built, verified against a known-good calculation, and kept current as an ongoing obligation rather than a delivery. The one market that is maintained today exists because clients there commissioned exactly this, and the same door is open elsewhere — it is a subscription to somebody watching, not a feature.
A return in the prescribed format
The file your authority actually accepts, with the identifier fields it requires, produced from the payroll run — as the maintained market’s returns now are. This is separate from and cheaper than portal submission, and it is usually where most of the month-end hours actually go.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. For a maintained rule set, the maintenance is the deliverable — say so in the conversation.
Talk to us about your payroll marketWhat AWRA OpsHub does today
- A payroll engine that computes gross, deductions, employer contributions and net from configured rules.
- A maintained statutory rule set for one market, kept current as rates and thresholds change.
- Rule sets versioned in intent, so a payslip referencing a rule version is meant to be insulated from later changes.
- Payslip generation and distribution, and payroll posting into the cross-module payments register.
- A configurable working week and holiday calendar driving leave arithmetic.
- Statutory identifiers per employee, labelled per country and encrypted at rest.
- In the maintained market, return files produced from a calculated run, ready for you to upload, with a readiness list for missing identifiers.
More we can add to your workspace
- A maintained rule set for any market other than the home one. Everywhere else is configured and owned by you.
- An alert, feed or update when statutory rates change in an unmaintained market.
- Portal submission to any authority, in any market including the maintained one.
- Return files in the prescribed format of any authority outside the maintained market.
Where we point you to a specialist
- Configurable is a legitimate product and a large share of payroll software worldwide is exactly this. What is not legitimate is letting a buyer hear "maintained" when the answer is "configurable", which is why the distinction leads this page.
- The one maintained market exists because clients there paid for it to. That is the honest reason and it is also why the same is available elsewhere as commissioned work rather than as a roadmap item.
- This page names no country other than by implication and asserts nothing about any Central African statute, rate or authority. Central Africa is here as an operating context where multi-country employment is ordinary.
Four questions for any payroll vendor
When the rate changes next year, who changes it?
A good answer sounds like
A direct answer.
What it actually means
The single question that separates maintained from configurable, and almost nobody asks it in those words.
Which markets are maintained, by name?
A good answer sounds like
A short list.
What it actually means
A long list is usually a list of markets the engine can be configured for, which is a different claim.
Do you produce the prescribed return file?
A good answer sounds like
Yes, or an honest no.
What it actually means
Ours is a no everywhere. This is where the month-end hours actually go.
How do I verify the first run?
A good answer sounds like
A recommended method.
What it actually means
A vendor with no answer has not thought about the one step that catches a misconfiguration before an employee does.
Name the person who owns the rules
If you are outside a maintained market, that person exists whether or not you have appointed them. Appointing them is the whole of payroll risk management.
Talk about payroll ownershipFrequently asked questions
Can the engine express my country's rules?
In most cases yes — it is a configurable engine and the usual structures of bands, thresholds and ceilings are expressible. The question to settle is not whether it can, but who verifies that it does and who updates it next year.
What happens to old payslips when I change a rate?
Rule sets are versioned in intent, and a payslip referencing a version is meant to stay fixed. Test that behaviour deliberately on your own data before you rely on it, because it is the property that decides whether a rate change is safe.
Is a maintained market expensive?
It is a standing commitment rather than a one-off build, which is exactly why it is priced as ongoing work. The alternative is not free either — it is a person in your organisation doing the same watching, usually without it being anybody's named job.
