Oriental Nippon Development
Back to portfolio
Case studyAdvertising & communications group (100–250 staff)Initiating: not yet delivered

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.

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.
TodayProposed
HostingVendorClient's own server
LicensingProprietaryOdoo Community, no transfer blocker
Audit evidenceAssembled yearlyProduced continuously by the pipeline
Audit effortAbout a month8–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

TechnologyRole in this project
Odoo CommunityHR, accounting, projects, assets and access control
PostgreSQLData for both entities, cleanly separated
PythonThe payroll engine and audit reporting
Native iOS and AndroidSelf-service for leave, timesheets and payslips
GitHub Actions with approval gatesDevelopers cannot approve their own releases
OCA audit-logAppend-only audit trail

How we would deliver it

Controls come first, before any business module, so every later wave inherits them.

  1. Foundations. Environments, repositories, approval-gated pipeline, role matrix, permissions and audit trail.
  2. HR pilot. One entity on top of that machinery.
  3. Overlapping module waves. The next module in discovery while the previous one stabilises.
  4. Accounting at a period boundary. Opening balances migrated and one parallel period run.
  5. Parallel payroll. Old and new calculated side by side before the old one is retired.
  6. Audit support as a service. One named technical lead across all three audit years.
Delivery timelineIndicative total: 6 months
  1. 01Discovery and foundations

    M1

    Environments, CI/CD with approval gates, access control, audit trail

  2. 02HR and payroll

    M1–M3

    Pilot, build, parallel payroll run, stabilise

  3. 03Finance and accounting

    M2–M4

    General ledger, chart of accounts, statements, opening balances

  4. 04Resource planning

    M3–M5

    Briefs, milestones, allocation and utilisation from real timesheets

  5. 05IT and administration

    M4–M5

    User lifecycle, asset register, access recertification

  6. 06Mobile apps

    M4–M6

    Native iOS and Android self-service

  7. 07Stabilisation and hand-over

    M5–M6

    Go-live, recovery plan, documentation

Risks and how we handled them

RiskHow we handled it
Controls added too latePermissions, audit trail and approval gates built in wave one
Payroll errors at go-liveOld and new payroll calculated side by side
Accounting migrated mid-periodFinance switch-over timed to a fiscal boundary
Audit findings becoming change requestsAudit 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

  1. Guidance on internal control, COSO
  2. COBIT, ISACA
  3. Odoo Community Association, OCA
  4. 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.