Integrate role-specific and common competency issues without losing response focus.
Integration on CFE Day 2 means connecting role-specific issues with common case facts when the facts genuinely interact. The declared role still controls depth, but a role conclusion may be changed by financing, tax, governance, strategy, stakeholder, or implementation facts that appear outside the narrow technical issue.
Synthesis is the written expression of that connection. It explains how one result affects another consequence and what the decision maker should do.
This lesson focuses on linking role-specific analysis with common issues while keeping the answer focused. Integration does not mean writing about every competency area. It means connecting the areas that matter to the role recommendation.
| Integration type | Example connection |
|---|---|
| Reporting and finance | An accounting adjustment affects covenants or financing capacity. |
| Assurance and strategy | Growth pressure increases management bias or going-concern risk. |
| Tax and cash flow | A tax position changes after-tax proceeds or financing need. |
| Performance and governance | Incentives create behaviour that undermines controls or strategy. |
| Finance and implementation | A project is attractive but cannot be funded or staffed. |
| Ethics and role advice | Professional duties limit what management can recommend or disclose. |
Day 2 candidates sometimes ignore common facts because they are not in the role exhibit. That can weaken the answer if a common fact changes the role conclusion. The opposite error is trying to force every common fact into every role response. Integration requires judgment.
Use common facts when they:
| Common fact does this | How to integrate |
|---|---|
| Changes a calculation or assumption | Adjust the analysis or state the sensitivity. |
| Creates a risk | Explain the risk and its effect on the recommendation. |
| Affects implementation | Add a condition, staged approach, or follow-up. |
| Changes stakeholder impact | Identify the stakeholder consequence and response. |
| Creates an ethical or governance constraint | State the duty, approval path, or escalation. |
If a common fact does not affect the role issue, leave it out.
A summary repeats what has already been said. Synthesis creates a conclusion from connected facts. A strong Day 2 answer may need both, but synthesis is what shows judgment.
| Summary | Synthesis |
|---|---|
| “The project has a positive return and there are covenant issues.” | “Although the project return is positive, the new debt would breach covenants unless the lender approves an amendment, so the project should be deferred until financing is resolved.” |
| “Revenue and audit evidence are issues.” | “Because delivery has not occurred, revenue should be deferred and audit work should focus on contracts, shipping terms, and subsequent collection.” |
| “The tax plan saves cash and has documentation risks.” | “The tax plan should not be implemented until valuation and related-party support are obtained because unsupported tax savings create compliance exposure.” |
Synthesis names the controlling consequence and action.
Day 2 cases often place relevant facts in separate exhibits. A finance exhibit may show a covenant, while a reporting exhibit shows the adjustment that changes the covenant ratio. A tax exhibit may show cash consequences, while a strategy exhibit explains why timing matters. The candidate must connect the exhibits rather than treating each as a separate answer.
When exhibits interact, write the link explicitly:
This can often be done in one paragraph.
Integration should not dilute role depth. If the declared role is assurance, the answer still needs assurance depth. A tax or finance consequence may be relevant, but it should support the assurance recommendation rather than replace it. If the declared role is finance, assurance or reporting facts may matter because they affect risk, covenants, valuation, or cash.
Use integration to strengthen the role answer, not to create a broad essay.
Use this sequence:
| Pitfall | Correction |
|---|---|
| Treating each competency area as separate. | Link facts when one conclusion changes another consequence. |
| Forcing integration without case support. | Integrate only when facts create a real connection. |
| Losing role depth in broad synthesis. | Keep the declared role as the main lens. |
| Summarizing rather than deciding. | State the controlling consequence and recommendation. |
| Ignoring exhibit interactions. | Cross-reference facts that affect the same decision. |