Suzie Pickering has experience in the clothing and retail industry, which is why she was assigned to the Cloud 9 audit. Suzie is mentoring Ian Harper, a first-year staff on the audit team, and they are working together on the detailed substantive test program. Ian remembers that Suzie used analytical procedures in the risk assessment phase and she explained to Ian how useful they could also be in the risk response phase. Ian suggests that they plan to rely extensively on analytical procedures for Cloud 9's substantive tests. He is very enthusiastic and wants to put analytical procedures in the plan for all transaction processes and major balances because he believes analytical procedures are very efficient for the audit team to perform. Suzie is more cautious. Although she will definitely plan to use some analytical procedures, she knows they will also need other types of tests. "Why?" asks Ian. "How do I know when to only use analytical procedures? What other tests do we need?" Ian is starting to realize that the standards and professional practice would not allow him to rely exclusively on analytical procedures. Cloud 9 has significant inventory balances (around 25% of total assets) and receivables (around 28% of total assets), so the auditors will need to gather persuasive evidence about the existence, valuation and allocation, and rights and obligations assertions for these accounts. Procedures such as confirming receivables balances and observing inventory counts are definitely going to be included in the detailed audit program. Suzie warns Ian that it is not always the size of the account that determines the use of analytical procedures or other procedures. For example, in Cloud 9's trial balance there is a derivatives investment account that is around 5% of total assets. It is a smaller portion of total assets, but since accounting for derivative investments is complex, they probably cannot rely solely on analytical procedures, particularly regarding the valuation and allocation assertion. an and Suzie continue their discussion about using analytical procedures. Ian is starting to feel more confident and suggests that there are some factors to consider about the Cloud 9 audit that would affect the use of the various procedures. "We could use all of the usual techniques in the Cloud 9 audit, although we have to be careful in making comparisons across years for a couple of reasons. We have only just taken over the audit, so although prior-year data was audited, we are still building up our level of familiarity with the data and don't really understand all the conditions that applied to the previous years. Also, the changes at Cloud 9, in particular the opening of the retail store and the additional borrowing to finance the purchase of the delivery trucks that we discovered during our preliminary work, will impact the data." Ian and Suzie have decided that analytical procedures will not be sufficient for all accounts. For each major transaction process and account balance they will also conduct tests of details of transactions. For vouching tests, the auditors will sample transactions and balances in the accounting records and go to the underlying documentation (or physical assets) to confirm the recorded details. For example, for sales recorded as being made prior to the fiscal year-end, they will examine the invoices and shipping documents to gather evidence on the date, amount, and other details of the transactions. If they find a sales invoice with a February date has been included in the sales for the year ended January 31, they have evidence of a misstatement in the occurrence and cutoff assertions for sales. They will also trace the details in a sample of documents through to Cloud 9's accounting records. This means that they will start with the documents and then test how that transaction (or asset or liability) is recorded in the client's accounts. For example, if they find a sales invoice with a January date that is not included in the sales for the year, they will have evidence of a misstatement in the completeness and cutoff assertions for sales. Suzie advises Ian that the sample sizes and approach to sampling are determined by the results of the controls testing and the resulting expectations for errors. Suzie also asks Ian to include tests of details of accounts, such as accounts receivables and property, plant, and equipment (PPE), in the detailed audit program. Where the risk is low, such as PPE, they will perform these tests at an interim date. Finally, Suzie informs Ian that the IT audit manager, Mark Batten, is writing the ADA program. Suzie asks Ian to consider Cloud 9's estimated warranty liability. The estimated warranty liability is included in accrued liabilities on the balance sheet and trial balance. Included in accrued liabilities on the October 31, 2022 trial balance is an estimated warranty liability of $832,015, which is slightly higher than the liability on the prior year's October 31, 2021 trial balance of $808,326. Suzie asks, "What is the likelihood that the liability is understated? Are there any reasons to believe there are unidentified claims, and how would auditors detect such claims?" Ian does not know of any change in manufacturing conditions that would affect the quality of Cloud 9's product, and thus the obligation under the warranty program. However, a new product was introduced at the start of the previous year. "Because sales of the new 'Heavenly 456' walking shoe are now 20% of total sales, we should consider any possible effects on the warranty liability. I recommend specific work be done to assess the claims from this new product." "However, if we remove this product from the analysis, the relationship between the warranty liability and sales is likely to be similar to past years. Because warranties apply to products, the amount of the warranty liability is determined by sales volume and product quality. Therefore, if conditions affecting product quality have not changed, and there is no change to the warranty program, substantive analytical procedures are a useful way of testing the reasonableness of the warranty liability." "Finally," Ian concludes, "relying on substantive analytical procedures to test the warranty liability is more justified if control testing suggests that Cloud 9 has effective controls over warranty claim estimation and identification of pending claims." During their conversation about Cloud 9's warranty liability, Suzie asks Ian about how they would use other substantive procedures to obtain evidence about the completeness assertion for the liability balance. "For example," Suzie asks, "would inspecting documents using vouching and tracing be useful and, if so, how would you use them?" Ian is still keen on using substantive analytical procedures but considers the question carefully. "I think we would use vouching to get evidence about transactions or balances that are recorded as warranty claims by Cloud 9. We could do this by selecting transactions or items in the account balance and obtaining the documentary evidence to support each one. However, it might be more useful to consider tracing because this would allow us to start with the documents and get evidence about how and whether the transactions are recorded in the accounts. If we find a document relevant to a warranty claim has not been recorded in the accounting system, we would be concerned that the liability is understated, or not complete. Additionally, we would like to examine transactions around the balance sheet date and make sure they are recorded in the correct accounting period. This evidence relates to the cutoff assertion and is part of considering completeness." Suzie asks Ian to set up the working papers for the tests they will perform. W&S Partners uses electronic working papers and there are examples available for Ian to use as a base for the Cloud 9 working papers. The priorities for Ian are to ensure that each test is described in sufficient detail in the audit program so the audit staff can perform the test correctly and identify any misstatements. The working papers also have to provide for comments to be included as the work is completed and reviewed by senior staff. Scan the line items on the prior-year financial statements and the current-year trial balance for Cloud 9. Using your knowledge of financial accounting, identify line items that require estimates or fair value measurements. For each item, state whether estimation uncertainty is low or high and briefly explain why.

Cloud 9 Consolidated Statement of Income For the year ended For the year ended January 31, 2022 January 31, 2021 Revenues $364-953,846 $345-965-385 Costs and expenses: Cost of sales $222,496,154 $207,838,462 Selling and administrative 104,450,000 100,246,154 Interest expense 1,257,692 1,730,769 Other (income)/expense, net 1,311.539 796.154 Total costs and expenses 329-515.385 310,611-539 Income before income taxes 35:438,461 35:353,846 Income taxes 12,757,692 13,080,769 Net income $ 22,680,769 $ 22,273,077\fCloud 9 Condensed Cash Flow Statement For the year ended January 31, 2022 January 31, 2021 Cash provided by operations $ 25,250,000 $ 26,907,692 Cash used by investing activities (13,165.385) (16,923,077) Cash used by financing activities * (13.457,692) (9,696,154) Effect of exchange rate changes on cash 3,284,616 1,873-077 Net increase in cash and cash equivalents 1,911,539 2,161,538 Cash and cash equivalents, beginning of year 9,780,769 7,619.231 Cash and cash equivalents, end of year $ 11,692,308 $ 9.780.769 Includes dividends paid of $4-988,462 in 2022 and $5,119, 231 in 2021.Cloud 9 Trial Balance October 31. 2020 October gi, Sozi Debit Credit Debit Credit Cash and cash equivalents $ 19-446,154 6,123.484 Accounts receivable 70-485.625 64,867-910 Allowance for doubtful accounts 704.856 648.679 Inventory 55-100-000 57,9080-000 Investments (derivatives) 19.419,231 13.805.769 Deferred income taxes (current) 2.457-692 3-594.615 Prepaid expenses and other current assets 9-265.345 6-446,154 Property, plant, and equipment 103.409.846 97.576,923 Accumulated depreciation 39,761.538 35-207,692 Identifiable intangible assets and goodwill 3-723-007 3.851,923 Accumulated amortization Deferred income taxes and other assets (noncurrent) 9.557-692 4.410.849 Current portion of long-term debt 2,115.345 go0-125 Notes payable 21,376.923 34.623-077 Accounts payable 14-946,457 22 561.538 Accured liabilities 25-809 846 Income taxes payable 2,211.539 3.726.923 Long-term debt 29.601,538 17.119,106 Deferred income taxes and other liabilities (noncurrent) 4-915-384 4-3:30.769 Common stock at par value 111,538 107,692 Capital stock in excess of par value 19.415-345 16.484-615 Unearned stock compensation 259-846 480,769 Accumulated other comprehensive income 5,011.538 4.746,154 Beginning retained earnings 122,857,692 98,150-473 Dividends 3.866,848 3.299,423 Repurchases of common stock 4-627.381 2.939.393 Revenue 277.398,461 269,442 308 Cost of sales 169-346,154 163.009-846 Selling and administrative 79.092.304 78.246,154 Interest expense 1,438,461 1,773.077 Other expense 459-446 757-692 Income tax expense 9-511.534 9.238,462 TotalsPresent: Dazed Colfer, chart financial officer, Cloud 9 Inc. Jos 1 Thomas, audit senior, Was Farmers JT: Thanks for seeing me, David. DC: You're welcome, Josh. What can I do for you? JT: I need to ask you some questions about Cloud 9's process for recording wholesale revenue transactions, including the trade receivables and cash receipts aspects. After I understand the process, I will be doing a system walkthrough and confirming my understanding by talking to the individuals who are involved in each step of the process. DC: We've got a pretty complex inventory management software system called Swift. It was designed by some of our tech guys. It tracks inventory and it integrates with our sales system. JT: How do customers decide the quantity and know the price? DC: The customers complete a purchase order online through a site that is linked to Swift. The site will tell customers the price for each item in inventory, as well as the quantity we have in stock. JT: How often are prices changed? DC: Price changes really depend on the market. While they don't change that often, our marketing management meets weekly to discuss price changes. Price changes are initiated after that meeting. Only the marketing manager and a few of her staff members have access to update the master price list. JT: What if a customer logs on and you don't have the products? DC: The system doesn't allow a customer to place an order greater than our current inventory levels. If a customer needs more inventory, the customer should fill out a separate request for inventory not on hand. The request gets e- mailed to our production manager and our marketing manager, who determine if we need to manufacture more goods. The decision about manufacturing more goods is complex as it integrates with our production decisions, or whether we can purchase additional inventory from a subcontractor that manufactures for JT: OK. This is helpful. Let's stay focused on the sales process. Once a customer's purchase order is complete, then what? DC: The submitted purchase order goes through a credit check and then becomes a sales order. If a customer exceeds his or her credit limit, there are a few people in my office that can approve a credit override, on a case-by-case basis. We tend to allow this only for good customers with good payment history. Then, the purchase order becomes our sales order. JT: I guess this electronic process saves a lot of time and trees! DC: Yes, there's so much that we rely on the system to do for us, it's scary. I worry about things like what happens if we are hit by a storm or lose power. We do have the whole system backed up off-site. IT: That is nice to know, and probably gives you some comfort. What happens to the sales order - how does it get filled? DC: Every day, the system assigns shipments to the warehouse location nearest to the customer's location that can fulfill the entire order. The warehouse manager then downloads the outstanding sales orders to these little handheld computer/scanners. It's very Star Trek. Warehouse personnel use these to identify inventory in the warehouse, then the warehouse personnel put boxes of ordered shoes onto pallets. The pallets are taken to a staging area where each product is then scanned. JT: Are the shipping documents approved before the goods go out the door? How do you know that what got sent is what was ordered? DC: Swift matches the quantities and products on the packing slip to the sales order. If they don't match, the order is set aside for follow-up to ensure that the order is accurately filled. Once they match, the approval box is activated, and the shipping supervisor can enter his or her passcode. This officially approves the packing slip and bill of lading, and each gets printed. JT: OK, so once the goods are shipped to the customer, how do you bill for this shipment? DC: We go into the billing system and pull up a draft invoice that was generated when the shipping document was approved. At this point, Swift performs a number of checks. The system matches the quantities in the invoice against the packing slip and sales order. Prices are also matched to the sales order. The customer number should also match on the sales order, shipping documents, and draft invoice. A report is run daily of any shipments that have not resulted in invoices. The reverse is also true. A report is run of any invoices that are not supported by shipping documents. At month-end, we run a report to compare dates on shipping documents with the month that transactions are recorded in the sales journal. If there are any discrepancies, the transaction is reported for manual follow-up. I believe discrepancies are rare as the system is very tight, and we ship only what was ordered. Then, the sales invoice is processed. Processing the sales invoice enters the transaction in a database from which we build the sales journal and accounts receivable subsidiary ledger. Also, at the end of each day, we compare the totals for accounts receivable with the total of each customer's balance in the accounts receivable subsidiary ledger. IT: When you do have discrepancies, who follows up on them and how are they cleared? DC: We have a data control group that follows up on discrepancies in a variety of systems. Discrepancies have to be cleared daily. Once the reason for the discrepancy is identified, changes to the underlying data must be approved by a manager in the data control group. The data is then corrected, and the invoice is processed. As I noted, discrepancies are very rare. We don't ship goods unless the order is completely filled. JT: Does finance ever go back to the sales order? DC: No. Since the shipping document can't be generated unless it agrees to the sales order, Swift only looks at the sales order for prices. Do you think we should do otherwise? JT: I wouldn't say so at this stage. But you'd have to be sure to have some tight controls around Swift, given that it seems to do everything. DC: Yes, good IT general controls over the Swift program, and other programs, are extremely important. I meet with the IT manager monthly, to talk about the few discrepancies found, reasons for discrepancies, and the importance of controls. I think you will find that our IT manager understands the importance of strong IT general controls, and strong controls over clearing any discrepancies identified in transaction streams. JT: Let's talk about accounts receivable. Who follows up on past-due receivables? DC: That is the sales manager's responsibility. In my opinion, we do a good job of screening credit upfront so we don't have a significant problem with past-due receivables. We send statements to customers with their receivable balances monthly. The sales manager and I discuss past-due accounts on a regular basis. The sales manager, controller, and I review the allowance for doubtful accounts monthly. A monthly adjusting journal entry is made by the controller, which I review and approve. You will find that our allowance for doubtful accounts is only about 19% of outstanding receivables as we do a good job of screening customer's credit upfront. JT: What is the cash receipts process