Planned: An Audit-Ready Business Platform on Open-Source ERP for a Media Group
Two entities, one platform, an annual IT-controls audit and statute-driven payroll. This programme is scoped and priced: ~80% configuration of open-source ERP, with a bespoke payroll engine, mobile apps and built-in audit evidence.
- Service
- Business Transformation
- Industry
- Media & Communications
- Region
- Pakistan
- Engagement
- Lab-type ODC (dedicated team)
Outcomes
- Target: audit in 8–15 days
- Continuous audit evidence
- Full platform & data ownership
Stack
Odoo Community · PostgreSQL · Python · iOS & Android · GitHub Actions · OCA audit-log
Written byOriental Nippon Team
This engagement is being initiated. What follows is the plan we proposed, not completed work.
An advertising and communications group in Pakistan, roughly 100–250 staff across three offices and two related legal entities, belongs to a larger international parent and is in scope for an annual IT-controls audit. It runs on a vendor-hosted product and wants its own on-premise platform, with no proprietary licence that would block a future hand-over.
The problem
- Vendor control. Hosting, data and releases all sat with the vendor.
- Two entities, one system. Payroll, financial reporting and employer branding must separate cleanly.
- Statutory payroll. Rules change with the law, and finance wants to update rates without a developer.
- Controls not built in. Separation of duties, privileged-user registers, append-only audit trails and "developer is not deployer" were not system capabilities.
- Evidence by hand. Audit evidence was assembled once a year.
| Today | Proposed | |
|---|---|---|
| Hosting | Vendor | Client's own server |
| Licensing | Proprietary | Odoo Community, no transfer blocker |
| Audit evidence | Assembled yearly | Produced continuously by the pipeline |
| Audit effort | About a month | 8–15 days in a normal year |
What we proposed
Configuration first
Roughly four-fifths of the platform is configuration of standard open-source modules: HR, accounting, projects and timesheets, assets and access control.
A bespoke fifth
A jurisdiction-specific payroll engine, a desktop activity agent, native mobile self-service apps and a built-in audit reporting pack.
Payroll engine
Slab tables with valid-from dates, change logging and maker-checker approval.
Controls in wave one
Record-level permissions, an inspectable permissions matrix and an append-only audit trail.
An evidence pipeline
Three environments, approval-gated deployment where developers cannot approve their own changes, and seven built-in audit reports.
Technology and the role it played
| Technology | Role in this project |
|---|---|
| Odoo Community | HR, accounting, projects, assets and access control |
| PostgreSQL | Data for both entities, cleanly separated |
| Python | The payroll engine and audit reporting |
| Native iOS and Android | Self-service for leave, timesheets and payslips |
| GitHub Actions with approval gates | Developers cannot approve their own releases |
| OCA audit-log | Append-only audit trail |
How we would deliver it
Controls come first, before any business module, so every later wave inherits them.
- Foundations. Environments, repositories, approval-gated pipeline, role matrix, permissions and audit trail.
- HR pilot. One entity on top of that machinery.
- Overlapping module waves. The next module in discovery while the previous one stabilises.
- Accounting at a period boundary. Opening balances migrated and one parallel period run.
- Parallel payroll. Old and new calculated side by side before the old one is retired.
- Audit support as a service. One named technical lead across all three audit years.
01Discovery and foundations
M1
Environments, CI/CD with approval gates, access control, audit trail
02HR and payroll
M1–M3
Pilot, build, parallel payroll run, stabilise
03Finance and accounting
M2–M4
General ledger, chart of accounts, statements, opening balances
04Resource planning
M3–M5
Briefs, milestones, allocation and utilisation from real timesheets
05IT and administration
M4–M5
User lifecycle, asset register, access recertification
06Mobile apps
M4–M6
Native iOS and Android self-service
07Stabilisation and hand-over
M5–M6
Go-live, recovery plan, documentation
Risks and how we handled them
| Risk | How we handled it |
|---|---|
| Controls added too late | Permissions, audit trail and approval gates built in wave one |
| Payroll errors at go-live | Old and new payroll calculated side by side |
| Accounting migrated mid-period | Finance switch-over timed to a fiscal boundary |
| Audit findings becoming change requests | Audit support priced in as an ongoing service |
What it would change
The group would own its platform, data and release schedule on hardware it controls, with no licence blocking a future transfer. Audit evidence would come from the pipeline continuously, and a controlled release cadence keeps the auditors' change sample small.
We priced audit support at the top of the client's own range, not the bottom. A finding in year two should not become a change request.
What the client would keep
- The platform on its own servers, with all source in its own repositories
- The permissions matrix and control documentation
- The seven audit reports
- The payroll rule set and its change history
- Every log and repository, transferable on exit
Sources and further reading
- Guidance on internal control, COSO
- COBIT, ISACA
- Odoo Community Association, OCA
- GitHub Actions documentation, GitHub
Facing something similar? This is the kind of work our Enterprise & Digital Transformation team delivers every day. Talk to us about your stack.
