Building an IFRS PMO: Governance, Workstreams, Timelines, and Change Control

Executive Summary

IFRS conversion succeeds when it’s run as a program—not a set of disjointed accounting tasks. A Project Management Office (PMO) provides the governance, cadence, documentation, and risk management to steer policy decisions, data remediation, ERP configuration, and stakeholder alignment toward an on-time, audit-ready go-live. This guide lays out a plug-and-play IFRS PMO blueprint you can adopt immediately.

What you’ll take away

• A clear PMO governance model (roles, cadence, decision rights)

• Standard workstreams and how to staff them

• A realistic timeline with phase gates and deliverables

• Change control, risk management, and audit-readiness routines

• Reusable templates: RACI, RAID, decision log, status pack, and comms plan

Call to Action
Ready to simplify IFRS?
WhatsApp: +1 555 795 9071 | Email: [email protected]

1) Why an IFRS PMO?

IFRS is multidisciplinary. Policy choices (IFRS 15/16/9) ripple into ERP/COA design, data models, internal controls, tax, covenants, and investor messaging.
Execution beats intention. An IFRS PMO orchestrates scope, resources, and critical-path dependencies across Finance, IT, Tax, Legal, Procurement, HR, and Operations.
Audit-ready outcomes. Structured governance produces a clean evidence file, stable mock closes, and smoother external audit.

Without a PMO you risk: late policy reversals, spreadsheet chaos, missed data fields, unstable close cycles, and lender surprises.

2) PMO Governance: Roles, Decision Rights, and Cadence

Executive Sponsor (CFO): Owns objectives, signs elections and budgets, clears roadblocks, leads board and lender updates.
Program Director / PMO Lead: Runs the plan, dependencies, RAID (Risks, Assumptions, Issues, Decisions), change control, and reporting.
Workstream Owners:

• Policy & Technical Accounting (IFRS 1, IFRS 15/16/9, IAS 12/36/21, IFRS 13)

• Systems & Data (ERP, COA, subledgers, integrations, migration)

• Controls & Close (close calendar, reconciliations, journals, documentation)

• People & Change (training, comms, adoption metrics)

Decision Rights (simplified)

• Tier 1 (Sponsor): Scope, budget, go-live date, IFRS 1 elections, major policy choices.

• Tier 2 (SteerCo): Priority trade-offs, timeline shifts, risk acceptance, auditor escalations.

• Tier 3 (PMO): Resource allocations, detailed plan updates, issue triage.

Cadence

• Daily: Workstream stand-ups (15–20 min).

• Weekly: PMO sync (status, blockers, risks).

• Bi-weekly: Steering Committee (SteerCo) with KPIs and go/no-go gates.

• Monthly: Board/Lender brief (KPI bridges, decisions, risks).

3) Workstreams and Core Deliverables

A) Policy & Technical Accounting

• Position papers with alternatives, judgements, citations, and quantified impacts

• IFRS 1 elections matrix and documentation

• Draft financial statements and disclosure shell

• Equity & P&L bridges from prior GAAP to IFRS

B) Systems & Data

• IFRS-aligned COA blueprint and mapping workbook

• Subledger configurations (leases, revenue, ECL)

• Data dictionaries, cleansing rules, and migration scripts

• Integration test packs and reconciliations

C) Controls & Close

• Close calendar with day-by-day RACI and quality gates

• Journal policy, reconciliation framework, maker-checker controls

• Audit evidence index and cross-references

• Mock close playbook and cutover checklist

D) People & Change

• Role-based training (Finance, IT, Tax, Legal, Procurement, FP&A)

• Comms plan for staff, board, lenders, and regulators

• Adoption metrics (training completion, close days, error rates, audit points)

4) Timeline: Phases, Milestones, and Gates (6–18 Months)

Phase 0 – Mobilize (Weeks 1–4)

• Charter, scope, resource plan, and high-level timeline

• Readiness assessment (policy, systems, data, controls, people)

• Gate M0: Charter approved, scope frozen, risk baseline set

Phase 1 – Design (Months 2–4)

• Position papers, IFRS 1 elections, target COA, disclosure prototypes

• Gate D1: Policy lock-in; auditor alignment; systems design approved

Phase 2 – Build & Mock Closes (Months 4–9)

• ERP/COA build, subledgers, data remediation, UAT

• Mock Close #1: Opening IFRS Balance Sheet (OIB)

• Mock Close #2: Restated comparatives + draft notes

• Gate B2: Reconciliations stable; evidence file audit-review ready

Phase 3 – Go-Live & Stabilize (Months 9–18)

• First IFRS financials; lender communications; close acceleration

• Gate G1: Go-live criteria met (KPI thresholds, zero critical issues)

5) RACI: Who Does What (Illustrative)

• Sponsor (CFO) – A (Accountable) for elections, budget, go-live dates

• PMO Lead – R (Responsible) for plan, RAID, change control; C (Consulted) on policy

• Policy WS Lead – R for position papers, disclosures; C on systems/data needs

• Systems/Data WS Lead – R for COA, subledgers, integrations, migration

• Controls/Close WS Lead – R for calendar, journals, reconciliations, evidence file

• People/Change WS Lead – R for training, comms, adoption KPIs

• Auditors – C/I (Informed) on decisions; C on evidence sufficiency

6) PMO Toolset: The Minimum Viable Artefacts

Status Pack (weekly):

• Milestone traffic lights; critical path; burn-down of issues

• KPI dashboard: % policies locked, mock close pass rate, reconciliation completeness, UAT defects, close days, audit points

RAID Register:

• Risk ID, owner, probability/impact, mitigation, due date, status

Decision Log:

• Decision, rationale, options considered, data used, approver, effective date, downstream impacts (systems/data/controls)

Change Request (CR) Form:

• Description, driver, scope/timeline/cost impact, alternatives, recommendation, approval route (Tier 2/3)

Evidence Index (for Audit):

• Cross-reference of every note/line item to working papers, data extracts, and approvals; version control

7) Change Control: Keep Scope Creep in Check

1. Freeze policy design at Gate D1—later changes require SteerCo approval.

2. Quantify impacts before approving a CR (timeline, cost, rework).

3. Batch low-risk tweaks into scheduled releases to protect mock closes.

4. Communicate decisions (who, what, why, when) to all impacted teams.

8) Risk Management: What to Watch—and How to Treat It

Top IFRS PMO Risks

• Late IFRS 1 or policy decisions → rework across systems and data

• Poor lease/contract data → unstable balances and disclosures

• Under-scoped testing → surprises during cutover and audit

• Resource contention (month-end vs. project) → slippage

• Auditor misalignment → repeat queries and delays

Treatments

• Early policy lock-in, auditor pre-clearance of judgement areas

• Data governance owners with measurable SLAs

• Test strategy (unit → integration → UAT → mock closes) with acceptance criteria

• Resource calendar that protects close; dedicated tiger teams for data

• Monthly sponsor reviews of “red” risks with specific actions and dates

9) Audit-Ready by Design: Build the Evidence as You Go

• Prototype disclosures early to reveal missing data fields.

• Tie-out discipline: each number has a source, a reconciliation, and an approver.

• Walkthroughs during mock closes; rehearse sample selections and control evidence.

• Version control for all working papers; freeze cutover packs before go-live.

10) Communications & Stakeholder Management

Auditors: cadence of pre-clear meetings and document drops; single point of contact.
Board/Lenders: KPI bridges (EBITDA, leverage, interest cover, ROA/ROE), covenant impacts, waivers if needed.
Internal Teams: simple “what changes for me” one-pagers per function; training schedule and job aids.

Comms Pack (one-pager outline)

• Purpose of IFRS conversion

• What’s changing (policy, process, systems)

• Impacts by role/team

• Timeline and how to get help

11) Metrics That Matter (Adoption & Readiness)

• Policies locked: target ≥ 95% by end of Design

• Data readiness: ≥ 98% completeness for lease/contract/asset masters

• UAT pass rate: ≥ 90% critical tests passed; 0 Sev-1 defects at cutover

• Mock close duration: trending to target close days (e.g., 5–7 working days)

• Audit points: declining trend; all “high” items closed pre go-live

12) Sector Notes (Snapshots)

Financial Services: ECL models and staging increase testing burden—add validation and model governance workstream.
Telecom & Media: Bundled contracts and content assets—ensure product/offer catalogs align to IFRS 15 data fields.
Energy & Resources: Decommissioning provisions and joint arrangements—early coordination with engineering and legal.
Retail & Hospitality: High-volume leases—invest early in a lease engine and data capture discipline.

13) Frequently Asked Questions

Do we need a “big” PMO tool?
No—start with disciplined spreadsheets plus a weekly status pack; scale tooling as complexity demands.

How do we avoid timeline slippage?
Lock policies early, protect testing windows, and restrict late scope changes to formal CRs.

What makes auditors comfortable?
A consistent evidence index, rehearsed walkthroughs, clear decision logs, and stable mock close results.

Can we run IFRS during busy season?
Yes—with a resource calendar that shields close and batches project work outside peak periods.

14) Your Next Step

Dawgen Global can stand up your IFRS PMO, provide experienced workstream leads, and deliver the artefacts and cadence that get you to audit-ready on time.

Call to Action
Ready to simplify IFRS?
WhatsApp: +1 555 795 9071 | Email: [email protected]

About Dawgen Global