1.Discussion 1 Sufficiency of Audit Documentation

What are your observations regarding the sufficiency of the audit documentation?

2.Discussion 2 Improvements to Audit Documentation

What specific improvements would you make to the audit documentation?

3.Discussion 3 Key Considerations

What are some key points to remember when performing and documenting control procedures specific to each component

Case 18-10- Handout 1 Antelope Run Inc. - Controls With a Review Element Note: This handout is based on a form that audit teams can use to document their tests and evaluation of the design and operating effectiveness of controls in accordance with PCAOB standards. Although the form is presented in its entirety for informational purposes, certain input boxes of the form have been shaded gray because they are cither given as case facts or are otherwise not applicable to this activity in the case. Component A - Control Description Control Activity - Summary Description C-5: Antelope Run Inc.'s (Antelope's) fitness trackers business planning committee (the "BPC") meets to review, challenge, and approve the revenue forecast for the fitness trackers reporting unit (Fit Stride) for appropriateness using historical performance and its knowledge of the company's strategic plans as well as industry projections and peer-company data. Control Description - Detailed Description of How the Control Is Expected to Be Performed To review, challenge, and approve the revenue forecast for each fitness tracker product and for the fitness trackers reporting unit overall, the BPC performs the following procedures: Step 1-Sales Volume Step 1a: For sales volume, the BPC will compare the historical sales volumes for each product to the forecasted sales volume by comparing (based on judgment) the year-to-year percentage change in volume to identify any anomalies. The BPC will pose questions to the Fit Stride director of sales and marketing (the "Director") for further explanation to understand what is driving the forecasted sales volume. Step 1b: For sales price, the BPC will compare the historical sales price to the forecasted sales price by comparing the year-to-year percentage change in price to identify anomalies. The BPC will pose questions to the Director for further explanation to understand what is driving the forecasted sales price changes. Step 1c: The BPC will compare the forecasted price of each product to competitor prices and, based on judgment, identify differences to investigate. To complete this review, the BPC uses the following report: Forecasted sales price per unit vs. competitor sales prices per unit for cach fitness tracker product. Step 1d: The BPC will also perform a retrospective review by comparing the forecasted revenues by product for cach of the past three years to actual sales revenue in those years to evaluate (based on judgment) the reasonableness of the forecast. Step 2 - Revenue The BPC reviews the revenue forecast for the fitness trackers reporting unit. Step 2a: The BPC will (1) compare the historical revenues to the forecasted revenues for the fitness trackers reporting unit overall and (2) compare the most recent three years' revenues to the annual percentage change in forecasted revenues to identify anomalies. The BPC will pose questions to the Director for the respective reporting units for further explanation to understand what is driving the forecasted revenue. Step 2b: The BPC will also compare the forecasted revenues to the prior-year forecast for the fitness trackers reporting unit overall to identify any anomalies. Step 2c: The BPC will also compare the percentage change in forecasted revenues to industry forecasts (c.g. Heart Healthy Quarterly publication and peer-company forecasts published by industry analysts) to identify any anomalies. Step 2d: Lastly, the BPC will also perform a retrospective review by comparing the forecasted revenues for the fitness trackers reporting unit for each of the past three years to actual sales revenue in those years to evaluate the reasonableness of the revenue forecast. Step 3: The revenue forecast for the fitness trackers reporting unit is revised. Risk of Material Misstatement Addressed by the Control ROMM Classification Significant Management's revenue projections and revenue growth rate assumptions that are used in various estimates may not be based on the best and most supportable information and contain a high degree of estimation uncertainty. Specifically, management's estimates of revenue growth are not only aggressive when compared to the historical performance of the Fit Stride products, but also incorporate subjective assumptions associated with revenue growth of the new Fit Belt product line. Significant Account(s) and Related Assertion(s) Addressed Significant Account: Goodwill Related Assertion: Valuation and Allocation Component B- Test of Design Procedures Performed to Test the Design of the Control Test of design for each step of the review: Step 1: Inquiry x Observation x Inspection To evaluate the design effectiveness of this control, we attended the annual BPC review meeting that took place on September 15 of the current year. The meeting included an evaluation of the revenue forecast assumptions used in management's projections on a product-by-product basis. We attended the meeting to observe the nature of the review performed by the BPC of the revenue forecast for the fitness trackers reporting unit by product. We also inspected the revenue forecast detail schedules (see working paper XXXX for each schedule used). We noted that each schedule included fluctuation analyses for each of the fitness tracker products, and that detail was at an appropriate level to facilitate the discussions that took place at the meeting. All variances outside management's established thresholds were discussed by the BPC. Step 2: Inquiry x Observation x Inspection To evaluate the design effectiveness of this control, we attended the annual BPC review meeting that took place on September 15 of the current year. The meeting included an evaluation of the revenue forecast assumptions used in management's projections for the fitness trackers reporting unit on an overall basis. We attended the mecting to observe the nature of the review performed by the BPC over the fitness trackers reporting unit revenue forecast. We also inspected the revenue forecast schedules (see working paper XXXX for each schedule used). We noted that cach schedule included fluctuation analyses for each of the fitness tracker products, and that detail was at an appropriate level to facilitate the discussions that took place at the meeting. All variances outside management's established thresholds were discussed by the BPC. Step 3: Inquiry X Observation Inspection During the annual review meeting, in addition to observing the BPC's decision and agreement to reduce the fitness tracker reporting unit revenue forecast, we also inspected the meeting minutes and subsequent c-mail communications among the members of the BPC (dated October 10) to obtain evidence that the appropriate actions were taken after the meeting to adjust the forecast. We inquired with Antelope's controller and director of financial planning and analysis (FP&A), who corroborated that the forecast was adjusted for the recommendations that were made at the mecting. Component C-Evaluation of Design How the Control Satisfies the Control Objectives Document whether the control satisfies the corresponding control objective, including whether it addresses terial misstatement to the relevant assertion of the significant account or disclosure. Risk Addressed by the Control On the basis of our understanding of the detailed description of this control above, we have determined that the entity has a sufficiently precise control process to ensure that the revenue forecast for the fitness trackers reporting unit is reviewed, challenged, and approved. As such, the purpose of the control is appropriate given the risks associated with it. Competence and Authority of the Person(s) Performing the Control Document the person(s) who performs the control, including the competence and authority of the person(s). This content is not included for purposes of the case study; please do not consider. Frequency and Consistency of the Performance of the Control Document the frequency and consistency of performance of the control, that is, whether the review occurs often enough to prevent or detect misstatements before they have a material effect on the financial statements. This content is not included for purposes of the case study; please do not consider. Level of Aggregation and Predictability Document the appropriateness of the level of aggregation and predictability of the control. This content is not included for purposes of the case study; please do not consider. Criteria for Investigation (i.e., threshold) and Process for Follow-Up Document the factors affecting the precision of the review, including the objective of the review and the appropriateness of the expectations, level of aggregation, and criteria for investigation for identifying potentially material misstatements. Also document the steps involved in identifying, investigating, and resolving significant differences from expectations. As noted in the detailed steps of the control, the BPC investigates the reasonableness of forecasted results as compared to historical, peer, and industry performance, with consideration of entity- specific events. If any variances are noted between the forecasted results and these other data points, the BPC will discuss and evaluate whether an adjustment to the forecast is necessary. If an adjustment is deemed necessary, the forecast will be adjusted in the Hyperion Financial Management software (Hyperion) Dependency on Other Control(s) or Information This content is not included for purposes of the case study; please do not consider. Is the control dependent on other controls? If yes, indicate which other control(8), where the other control(s) is (are) tested, and the conclusion reached on the design and operating effectiveness of the control(s). Information Used in the Review This content is not included for purposes of the case study, please do not consider. Is the effectiveness of the control dependent on information used in the review? If yes, identify the controls that address the accuracy and completeness of the information used in the review, where this information is tested, and the conclusions reached as a result of that testing Design Effectiveness Conclusion Effective If design effectiveness conclusion is deemed ineffective, document the basis for this conclusion N/A Risk Associated with the Control Considering the factors in PCAOB AS 2201.47, conclude on the risk associated with the control. Higher Document the basis for the conclusion on the risk associated with the control