The Inventory Count Timing Conflict
You are the engagement manager for the audit of Kestrel Manufacturing, a private company with a 31 December year-end and a $48 million loan covenant requiring inventory turnover above 4.0. The client insists on counting inventory on 27 December because its warehouse staff take leave from 28 December. The warehouse holds 6,200 pallets; 900 pallets are scheduled to ship on 29–30 December and 1,100 pallets of raw material are expected to arrive on 30 December. The client's controller says the 27 December count can simply be rolled forward to year-end using the shipping and receiving logs. Last year's audit found a $310,000 cutoff error in the same warehouse. Materiality is $240,000. The client has offered to let your team observe the count but will not permit a second visit on 31 December.
1. Assess the audit risk arising from the proposed count date and recommend a response that addresses both the roll-forward and the prior-year cutoff issue.
Read the worked answer
The count date creates a roll-forward risk rather than a pure existence risk. The 27 December count itself can provide evidence of existence at that date, but the 900 outbound pallets and 1,100 inbound pallets mean roughly 32% of the pallet population moves between count and year-end. Roll-forward procedures are therefore not a formality; they are the main evidence for the year-end balance.
Prior-year cutoff error of $310,000 exceeds materiality of $240,000, so the risk is elevated, not normal. The response should be:
- Observe the 27 December count with adequate coverage, including test counts and recording of the last receiving and shipping documents.
- Obtain complete shipping and receiving logs for 28–31 December and vouch a sample of movements to shipping documents, bills of lading and receiving reports.
- Test the 29–30 December shipments specifically: confirm goods left, confirm title transfer terms, and check that revenue and cost of sales were recorded in the correct period.
- Test the 30 December receipts by agreeing receiving reports to supplier invoices and confirming the goods were not recorded as inventory before receipt.
- Perform a 31 December roll-forward and reconcile the resulting balance to the ledger, investigating any unexplained difference.
- Escalate the access restriction to those charged with governance and document the limitation; if the roll-forward cannot be substantiated, consider a modified opinion.
2. The controller argues the roll-forward is sufficient and a second visit is unnecessary. How should you evaluate that assertion against the auditing standards?
Read the worked answer
The controller's assertion is partly right and partly wrong. Attendance at the count is not mandatory in every audit; the standards require attendance when inventory is material and there is a risk of material misstatement. Here inventory is material and the prior-year cutoff error shows the risk is real, so attendance at the 27 December count is expected.
The roll-forward is acceptable only if it provides sufficient appropriate evidence. That requires:
- reliable shipping and receiving records, tested for completeness;
- a reconciliation of count to ledger with no unexplained gap;
- evidence that movements were recorded in the correct period.
What is not acceptable is treating the roll-forward as a substitute for testing. The client's refusal of a 31 December visit is a scope limitation imposed by the client. If alternative procedures cannot reduce the risk to an acceptable level, the auditor should communicate with those charged with governance and consider a qualified opinion on inventory.
The key judgement is that the auditor, not the client, decides whether evidence is sufficient. The controller's convenience is not an audit argument. Document the discussion, the alternative procedures performed, and the conclusion reached.