How should Singapore audit firms operationalise the revised ACRA Code requirements when using external experts?

The 2026 update to the ACRA Code (implementing IESBA’s external expert ethics revisions) turns “we used a specialist” into an inspection-facing workflow that must be evidenceable on file. For many firms, the gap is not technical knowledge—it is execution: choosing an expert fast enough for engagement timelines while still documenting competence, capabilities and resources for the specific assignment, assessing objectivity threats and safeguards, and then supervising and evaluating the expert’s work without over‑reliance. This guide is written for partners, EQCRs and quality leaders who need an inspection-ready operating model for ACRA Code external expert Singapore engagements: what to build into methodology, what reviewers should gate, and what documentation packs should exist before sign-off.

Where in the audit workflow do the revised external expert requirements need to “land” so they are inspection-ready?

Treat the 2026 ACRA Code update as a workflow redesign, not an extra form at completion. The firms that struggle in inspections usually have two symptoms:

• Late expert engagement (scoping and objectivity checks are rushed, documentation is backfilled).
• Thin on-file rationale (the audit team “felt comfortable” with the expert, but the file cannot demonstrate why).

A practical way to embed the requirements is to attach them to existing audit milestones with clear ownership.

A minimum “inspection-ready” workflow map

Stage 1 — Need identification (planning):

• Trigger: management uses complex estimates, unusual assets/liabilities, or specialised regulations; or the audit team lacks capability.
• Output: decision memo confirming why an external expert is needed and what the auditor will use the expert for.

Stage 2 — Selection and onboarding (planning/early fieldwork):

• Competence/capability/resources assessment for the specific assignment.
• Objectivity/independence threats assessment and safeguards.
• Engagement scope, deliverables, and communication protocol.

Stage 3 — Direction and supervision (fieldwork):

• Auditor instructions to expert documented.
• Defined interaction points (kick-off, interim check, final review).

Stage 4 — Evaluation of expert output (fieldwork/completion):

• Assess relevance and reasonableness of assumptions and methods at a governance level.
• Corroborate with other audit evidence.
• Resolve exceptions; consider the impact on audit opinion if unresolved.

Stage 5 — File completion and review gates (completion):

• Partner and EQCR confirm the file evidences: (i) why expert was needed, (ii) competence and objectivity evaluation, (iii) auditor supervision, (iv) evaluation and corroboration, and (v) conclusions.

Ownership that works in practice

• Engagement Partner: approves expert appointment, safeguards, and reliance conclusions.
• Engagement Manager: executes competence/objectivity evaluation pack; maintains audit trail.
• Specialist/Technical Partner (where applicable): supports scoping and review for high-risk topics.
• EQCR: tests whether the file demonstrates auditor responsibility and not mere acceptance of expert work.

The key design principle: the audit file must show the team made informed decisions before relying on the expert’s work—not after issues arise.

How do you decide early whether you need an external expert—and define the boundary of auditor vs expert responsibility?

The revised expectations tighten scrutiny on why the auditor used an external expert and what exactly the expert was engaged to do. If that boundary is vague, two problems follow:

• The expert may deliver something that is not auditable or not aligned to your risk assessment.
• The audit team may drift into over-reliance (“the expert signed off, so we’re covered”).

A practical decision test (use at planning)

Document answers to these questions in a short “Expert Use Decision Note”:

1. What audit assertion/risk requires expertise? (e.g., valuation of unquoted investment; impairment model; provision with specialist assumptions)

2. What does management already have? (management expert report? internal team calculations?)

3. Why can’t the audit team address it without an external expert? (capability gap; complexity; need for independent challenge)

4. What will the expert’s output be used for?

• As audit evidence (e.g., independent estimate/range)
• To assist the auditor (e.g., assessing management method and assumptions)

5. What will remain the auditor’s responsibility?

• Risk assessment, audit strategy, sufficiency/appropriateness of evidence, final conclusions.

Define scope so it can be audited

In your scope definition, avoid broad statements like “provide valuation support.” Instead, specify:

• Subject matter: exactly what asset/liability/estimate.
• Standard of value / basis: if relevant (e.g., fair value considerations), without turning the audit file into a technical valuation manual.
• As-of date and reporting unit: aligns with financial statements.
• Outputs required: report, workings, key assumptions, sensitivity, management representations relied on.
• Limitations: what the expert is not doing (e.g., not opining on financial reporting compliance).

This boundary-setting is a control: it shows ACRA inspectors that the auditor directed the work and retained responsibility.

What does a “specific-assignment” competence and capability assessment look like (beyond a CV check)?

A common inspection weakness is a generic file note: “Expert is qualified; has X years of experience.” The revised expectations push firms to assess competence, capabilities and resources for the actual assignment.

Build a competence assessment that answers four questions

1) Does the expert have the right technical competence for this subject matter? Evidence examples:

• Relevant professional qualifications/registrations.
• Recent assignments of similar type and complexity.
• Demonstrated knowledge of the relevant industry and valuation/measurement context.

2) Do they have the capability to perform the work to audit timelines and quality? This is operational, not academic. Evidence examples:

• Proposed team composition (who is doing the work vs who is reviewing).
• Project plan, milestones, and turnaround times.
• QA processes inside the expert’s firm (peer review, second partner review).

3) Do they have sufficient resources and access to data/tools? Evidence examples:

• Ability to access required market data or benchmarks.
• Tools/models used (high level—do not attempt to validate proprietary modelling in detail, but document what is used and why it is suitable).
• Data requirements list issued to management and the auditor.

4) Is their relevant experience aligned to the “risk point” of this engagement? This is where specificity matters:

• If the risk is management bias, assess whether the expert can challenge management assumptions.
• If the risk is complex instruments, assess whether the expert has instrument-specific experience.
• If the risk is high estimation uncertainty, assess whether they can produce ranges and sensitivity.

A competence assessment template (what to include on file)

• Expert identification and role.
• Scope summary.
• Competence evidence summary (qualification + relevant engagements).
• Capability/resources summary (team, plan, QC).
• Prior experience with the audit client (if any) and how threats are managed.
• Conclusion: why the expert is suitable for this assignment.

Proportionality: scale the work to the risk

Not every engagement needs the same depth. Use a simple risk tiering:

• Tier 1 (high risk / material / complex / judgemental): enhanced assessment, partner approval, and EQCR attention.
• Tier 2 (moderate): standard assessment and manager-level execution.
• Tier 3 (low): lightweight assessment but still documented.

This prevents “checkbox inflation” while still meeting the expectation that the evaluation is tailored and evidenceable.

How should audit firms assess and document objectivity threats and safeguards for external experts?

Competence alone is not enough. The 2026 ACRA Code update (implementing IESBA revisions) raises the bar on identifying objectivity threats and documenting safeguards—especially where the expert has relationships that could bias their work.

Start with a structured threat scan

Use a consistent objectivity checklist that covers the most common threats:

• Financial interests: any direct/indirect interest in the audit client.
• Business relationships: other services provided to the client (or key management) that create self-interest or advocacy threats.
• Employment relationships: former employees/partners of the client; family relationships with management.
• Fee dependence: expert’s fees from the client (or group) represent a significant portion of their revenue.
• Contingent fees / success-based arrangements: particularly problematic for objectivity.
• Advocacy: the expert is acting to promote the client’s position (e.g., for fundraising, disputes) and then is asked to provide work used in the audit.
• Self-review: the expert is evaluating their own prior work (e.g., they produced the valuation for management, then are used by the auditor).

Document safeguards that are real (not symbolic)

Safeguards must change how the work is done or reviewed. Examples:

• Engage a different expert/team from the same firm (separation from management advisory work).
• Independent review by a second expert within the provider (document who and what they reviewed).
• Enhanced auditor supervision and corroboration, including challenging key assumptions and testing inputs.
• Limit the use of the expert’s work (use it to inform audit procedures rather than as primary evidence) where threats cannot be reduced sufficiently.
• Change commercial terms (remove contingent fees; clarify no advocacy role).

Practical documentation: the “Objectivity & Conflicts Memo”

Include:

• Declared relationships and services.
• Threats identified (by type).
• Safeguards applied and why they are sufficient.
• Partner approval and (if high-risk) EQCR acknowledgement.

Watch-outs that often surface in reviews

• The expert is management’s expert and the auditor assumes objectivity without documenting threats.
• The expert is used across multiple engagements and teams copy-paste last year’s objectivity memo.
• The expert’s engagement terms are negotiated by management, creating perceived dependence; the auditor needs to consider how that affects reliance.

The goal is not to eliminate all threats; it is to show you identified them, responded appropriately, and adjusted reliance accordingly.

How do you structure the engagement with the external expert so the auditor is directing the work (and not inheriting it)?

Many problems are created at engagement set-up: unclear deliverables, no agreement on access to workings, and no defined communication protocol. Inspection issues then appear as “insufficient documentation” or “over-reliance.”

What your expert engagement letter (or terms) should operationally cover

You are not drafting a legal contract here; you are creating an auditable working arrangement.

Include these operational clauses:

• Scope and purpose: what the expert will do; that it supports the auditor’s work.
• Deliverables: report format; list of key assumptions; sensitivity; reconciliation to financial statement figures.
• Access to workings: expectation that the auditor can review underlying schedules/inputs used to reach conclusions.
• Data sources: what information is obtained from management vs independent sources.
• Timing and milestones: dates for draft and final outputs.
• Confidentiality and data handling: aligned to audit client confidentiality.
• Objectivity declarations: conflicts and independence declarations.
• Use of work: clarify the report is for audit purposes (where relevant) and any restrictions.

Set up three touchpoints as a default control

• Kick-off call (before work starts): confirm scope, data needs, timelines, and the “risk point” to focus on.
• Interim checkpoint: confirm progress, preliminary findings, and emerging issues.
• Final readout: walk-through key assumptions, limitations, and sensitivities.

Document each touchpoint in a short call note on the audit file.

Align the expert’s output with your audit plan

Before the expert begins, the audit manager should map:

• Which audit assertions the expert’s work supports.
• What corroborative procedures will still be required.
• How the expert’s output will be evaluated.

This avoids a common failure mode: receiving a technically competent report that does not address the audit question you need to answer.

What does “direction and supervision” look like in practice for audit teams using external experts?

Direction and supervision is where firms can demonstrate auditor responsibility. It does not mean re-performing specialist work; it means making sure the expert’s work is targeted, complete, and usable as part of your audit evidence.

A workable supervision approach for managers

Create a “Supervision & Review Log” with:

• Instructions given to the expert (scope, assumptions to consider, format required).
• Documents and data provided (and by whom).
• Issues raised by the expert and how they were resolved.
• Changes to scope and rationale.
• Review steps performed by the audit team.

Supervision should intensify when any of these are true

• The matter is material or high judgement.
• There is high estimation uncertainty.
• Management is aggressive on assumptions or outcomes.
• The expert is new to the firm, or the team is relying on them for the first time.
• Objectivity threats exist even after safeguards.

Partner-level supervision: what partners should actually do

Partners are not expected to validate technical modelling. Practical partner actions include:

• Confirm the competence/objectivity pack is complete before reliance.
• Challenge whether the scope addresses the engagement risk.
• Review the key assumptions and ensure they are consistent with the auditor’s understanding of the business.
• Ensure that limitations are understood and that the audit response is adjusted.

EQCR focus: what an EQCR should look for

EQCR reviews should test “audit ownership”:

• Is there evidence the auditor evaluated the expert, not just used them?
• Is reliance proportionate to objectivity and competence assessment?
• Does the file show corroboration and resolution of inconsistencies?

A firm that operationalises these controls will look consistent across engagements—something that matters in practice during ACRA practice monitoring.

How should auditors evaluate the expert’s output without drifting into technical re-performance?

The evaluation step is often where files fail: either the team does too little (“accepted the report”), or tries to do too much (pseudo re-performance without competence). A practical approach is to evaluate at the level of reasonableness, consistency, completeness, and linkage to audit evidence.

A five-part evaluation checklist that is inspection-friendly

1) Does the output answer the scoped audit question?

• Is it for the correct entity, date, and subject matter?
• Are conclusions clearly stated and tied to deliverables?

2) Are methods and assumptions described and internally consistent?

• High-level consistency checks: are assumptions aligned to business realities (e.g., growth vs actual performance; discount rates vs market conditions)?
• Are sensitivities provided where uncertainty is high?

3) Are the inputs supported and sourced appropriately?

• What came from management? What was independently sourced?
• Are management-provided inputs tested elsewhere in the audit (e.g., forecasts, contracts, capex plans)?

4) Are limitations and caveats understood and addressed?

• If the expert caveats reliance on certain data, what did the audit team do to validate it?
• If the expert excludes certain scenarios, is that appropriate?

5) Do the conclusions reconcile to the financial statements and other evidence?

• Reconcile figures to the trial balance and disclosures.
• Check consistency with events after reporting period where relevant (without turning into a deep technical exercise).

Handling disagreement or “unusable” reports

When expert conclusions conflict with management or other evidence:

• Document the inconsistency and root cause.
• Request clarification or additional procedures from the expert.
• Perform additional audit work (or engage a second expert) if necessary.
• Consider implications for financial statement adjustments, disclosures, or audit opinion.

The audit file should show a clear story: what was received, what was questioned, what was resolved, and what was concluded.

How do you avoid over-reliance and still meet audit evidence expectations in Singapore engagements?

A recurring inspection theme is over-reliance: the audit team treats the expert report as a substitute for audit judgement. The revised ethics expectations sit alongside the broader requirement that the auditor obtains sufficient appropriate audit evidence and remains responsible for the conclusion.

Practical controls to prevent over-reliance

Control 1 — “Two-source” mindset for critical inputs For key inputs that drive the expert’s conclusion (e.g., management forecasts, contract terms, asset condition), ensure the audit team corroborates them elsewhere:

• Board papers/budgets approved by governance.
• Post-year-end performance trends.
• Signed contracts, customer concentration, renewal history.
• Independent market data where feasible.

Control 2 — Link expert work to your audit risk assessment Document explicitly:

• Which risk is being addressed.
• How the expert’s work reduces uncertainty.
• What residual risk remains and what other procedures address it.

Control 3 — Restrict reliance where objectivity is weaker If threats cannot be reduced to an acceptable level, adjust how you use the work:

• Use it to inform challenge of management rather than as primary evidence.
• Increase corroborative audit procedures.
• Consider engaging an alternative expert.

A CFO-facing implication (why this matters to management)

CFOs should expect auditors to ask earlier, more structured questions about:

• Data availability and quality for expert work.
• Access to management’s models and assumptions.
• Timelines for producing auditable support.

If management cannot provide reliable inputs, the audit will either slow down or require expanded procedures—both of which affect closing timetables.

What documentation pack should be standardised across the firm for external experts by 2026?

Standardisation is the fastest way to make implementation consistent across partners and teams. Aim for a small set of templates that are easy to complete and easy for EQCRs to review.

The core “External Expert Documentation Pack” (recommended)

1) Expert Use Decision Note (1–2 pages)

• Why expert is needed; audit risks; intended use.

2) Competence/Capabilities/Resources Assessment

• Assignment-specific competence evidence; team and QC; conclusion.

3) Objectivity & Conflicts Memo

• Threat scan; safeguards; approval.

4) Scope & Instructions Summary

• Deliverables; dates; data sources; access to workings.

5) Supervision & Interaction Log

• Touchpoints; issues; scope changes; resolution.

6) Expert Output Evaluation Memo

• Five-part evaluation; reconciliation; corroboration performed; conclusion on reliance.

7) Review Gate Sign-offs

• Manager completion; partner approval; EQCR prompts (where applicable).

Design your templates for how people actually work

To drive adoption:

• Use checkboxes sparingly; require short narrative fields where judgement is required.
• Include “examples of acceptable evidence” in footnotes.
• Build in prompts for common threats (fee dependence, advocacy, self-review).

Paul Hype Page & Co. can support firms by converting these into methodology-aligned templates and reviewer checklists that match Singapore inspection expectations, including EQCR prompts and file-indexing conventions.

How should partners and quality leaders implement this across all engagements without slowing the audit cycle?

Implementation fails when it is treated as training-only. The practical objective is to make the right actions happen at the right time with minimal friction.

A 60–90 day implementation roadmap (practical sequencing)

Week 1–2: Methodology decisions

• Define when an expert is mandatory vs discretionary.
• Set risk tiers and required approvals.
• Decide documentation pack structure and where it sits in the file.

Week 3–5: Template build and pilot

• Draft the documentation pack.
• Pilot on 2–3 engagements (different partners; different expert types).
• Capture friction points (what teams struggled to evidence).

Week 6–8: Reviewer enablement

• Train partners/EQCRs on what “good” looks like.
• Introduce review gate questions (see below).
• Update internal cold/hot file review programmes to include expert usage.

Week 9–12: Rollout and monitoring

• Roll out templates firmwide.
• Track completion rates and exceptions.
• Conduct a targeted internal review of first-wave files.

Review gate questions (partner/EQCR prompts)

At completion, reviewers should be able to answer:

• Did the team document why an expert was needed and how the work is used?
• Is competence assessed for this assignment (not generic)?
• Are objectivity threats identified with safeguards and approvals?
• Is there evidence of direction/supervision and issue resolution?
• Is the expert output evaluated and corroborated, with clear reliance conclusion?

Keep cycle time under control

• Maintain a pre-approved panel of experts (with annual baseline due diligence), but still require assignment-specific add-ons.
• Require early expert triggers in planning checklists so teams don’t engage specialists late.
• For repeat experts, roll forward baseline competence/objectivity information—but force refresh of assignment-specific factors and new conflicts.

The goal is consistency and timeliness: a process that produces reliable files without turning every engagement into a bespoke compliance project.

Conclusion

The 2026 ACRA Code changes around external experts will be tested in practice through your files: whether you can demonstrate early decisions, assignment-specific competence and objectivity evaluations, active supervision, and a clear, corroborated reliance conclusion. The most effective response is to redesign the workflow with review gates, not to add end-stage documentation. Partners and EQCRs should prioritise a standard documentation pack, risk-tiered approvals, and a supervision/evaluation routine that can be executed under real audit timelines. If you need implementation support, Paul Hype Page & Co. can help quality leaders translate the revised requirements into working templates, reviewer prompts, and internal QA procedures that are consistent across engagements and ready for inspection.