Apply acceptance, retention, ethics, independence, competence, resources, and engagement letter judgment.
Engagement acceptance is an assurance quality decision. Before accepting or continuing work, the practitioner must decide whether the client, engagement terms, ethical conditions, competence, timing, resources, and reporting expectations support a high-quality engagement.
The practical question is not simply whether the client wants the work. The question is whether the practitioner can perform the work objectively, competently, and with clear terms that users will understand.
This lesson focuses on how to:
Acceptance should be decided before detailed work begins. If the engagement is accepted with unresolved independence, scope, competence, or reporting problems, the practitioner may not be able to obtain sufficient appropriate evidence or issue an appropriate report.
| Gate | Question | Possible response |
|---|---|---|
| Client integrity | Are management and those charged with governance trustworthy? | Decline or perform more due diligence if integrity is doubtful. |
| Ethical compliance | Are independence, objectivity, confidentiality, and professional competence protected? | Apply safeguards or decline if threats cannot be reduced. |
| Engagement risk | Are scope, reporting, fraud, litigation, reputation, or user-expectation risks acceptable? | Modify terms, expand procedures, involve senior review, or decline. |
| Competence and resources | Does the firm or team have expertise, time, specialists, and supervision? | Add resources or decline if quality cannot be maintained. |
| Suitable criteria | Can the subject matter be evaluated against suitable criteria? | Clarify criteria or decline assurance if criteria are unsuitable. |
| Clear terms | Are responsibilities, objective, scope, timing, report, and limitations agreed? | Use an engagement letter before work begins. |
The gate should lead to a conclusion. A response that lists concerns but never says whether to accept, accept with safeguards, defer, or decline is incomplete.
Name the threat and the safeguard. If no safeguard is strong enough, the correct conclusion may be to decline or not continue.
| Threat | Case signal | Possible safeguard or conclusion |
|---|---|---|
| Self-interest | Large overdue fees, financial interest, or dependence on client fees. | Collect fees, remove interest, add review, or decline. |
| Self-review | Practitioner would assure work they prepared. | Separate teams, independent review, or decline if the threat remains. |
| Advocacy | Practitioner promotes the client’s position or financing. | Avoid the advocacy role or separate it from assurance work. |
| Familiarity | Long association or close personal relationship. | Rotate personnel, add independent review, or remove the affected team member. |
| Intimidation | Client pressures deadline, fee, scope, evidence access, or conclusion. | Escalate, document, modify terms, or decline. |
| Management participation | Practitioner makes decisions that belong to management. | Keep management responsible for decisions, judgments, approvals, and implementation. |
Safeguards should fit the threat. An independent review may help with familiarity or self-review, but it will not fix management’s refusal to provide evidence or a lack of suitable criteria.
Even when independence is protected, the engagement may be inappropriate if the practitioner cannot perform it properly. Competence includes technical knowledge, industry understanding, IT capability, specialist access, supervision, and enough time to complete the work.
| Resource issue | Assurance implication |
|---|---|
| Highly specialized subject matter | The team may need a specialist or should decline if competent work is not possible. |
| Compressed reporting deadline | Procedures may be insufficient unless timing, scope, or resources change. |
| Weak client records | More work may be needed, and acceptance may depend on access and management cooperation. |
| New engagement type | Consultation, training, quality review, or different staffing may be required. |
| Remote locations or systems | Travel, component work, IT access, or alternative procedures may affect acceptance. |
Time pressure is not just an operational inconvenience. If the deadline prevents appropriate evidence gathering, it becomes an engagement quality issue.
Communication with a predecessor auditor or practitioner is not a formality. It may reveal reasons the engagement should not be accepted.
| Possible issue | Acceptance implication |
|---|---|
| Disagreements over accounting, scope, or fees. | May indicate management integrity or expectation risk. |
| Restricted access to information. | May indicate future evidence limitations. |
| Unresolved fraud or illegal acts. | May create unacceptable engagement risk. |
| Frequent auditor changes. | May signal opinion shopping or governance weakness. |
| Permission denied by management. | May itself be a warning sign requiring caution or decline. |
If management refuses permission to communicate with the predecessor, the refusal should be evaluated as an acceptance risk. It may indicate that the client is trying to hide disputes, scope limits, fraud concerns, or fee problems.
The engagement letter manages expectations and documents the basis for acceptance. It should be clear enough that management, the practitioner, and relevant users understand the work before it begins.
| Term | Why it matters |
|---|---|
| Objective and assurance level | Prevents confusion about audit, review, other assurance, or non-assurance work. |
| Scope and subject matter | Defines what is included and excluded. |
| Criteria | States the basis for evaluating the subject matter. |
| Responsibilities | Separates management responsibilities from practitioner responsibilities. |
| Access to information | Supports evidence gathering and reduces scope limitation risk. |
| Report form and distribution | Clarifies users, wording, and any restriction on use. |
| Timing and fees | Reduces deadline pressure and fee disputes. |
When a case includes expectation-gap facts, the engagement letter is often part of the answer. For example, if management expects the practitioner to guarantee fraud detection, the terms should clarify the objective, inherent limitations, responsibilities, and report form.
| Step | Question | Output |
|---|---|---|
| 1. Barrier | What acceptance or retention concern appears? | Ethics, independence, competence, resource, client, scope, or criteria issue. |
| 2. Risk | Why does it matter for engagement quality or users? | Engagement risk consequence. |
| 3. Safeguard | Can the risk be reduced to an acceptable level? | Safeguard or reason to decline. |
| 4. Decision | Should the practitioner accept, continue, defer, modify terms, or decline? | Acceptance conclusion. |
| 5. Documentation | What should be documented or included in the engagement letter? | Rationale and term. |
Use this sequence when a case includes a new client request, a continuing engagement with new risk, an independence issue, a predecessor concern, a time constraint, or unclear engagement terms.
| Pitfall | Correction |
|---|---|
| Accepting first and solving independence later. | Resolve ethics and independence before undertaking the engagement. |
| Naming a threat without a safeguard or conclusion. | State whether safeguards reduce the threat or whether decline is required. |
| Ignoring competence and resources. | Consider expertise, timing, supervision, and specialist needs. |
| Treating predecessor communication as optional background. | Use it to assess integrity, scope, disputes, and risk. |
| Omitting engagement terms. | Identify the letter term needed to align expectations. |