Auditor interview questions

I structure the engagement so each phase turns assessed risk into supported conclusions.

• Planning establishes the reporting framework, scope, materiality, timetable, and team responsibilities.
• Risk assessment links the entity, controls, accounts, and assertions to the planned audit response.
• Execution gathers evidence through control testing and substantive procedures, while completion resolves findings, subsequent events, and reporting.

Assertions define what could be wrong in each account and therefore what evidence the audit needs.

• Existence and occurrence address whether recorded assets or transactions are real, while completeness addresses what may be omitted.
• Rights and obligations, valuation, accuracy, cutoff, classification, and presentation identify different possible misstatements.
• I map each relevant assertion to the assessed risk, key controls, and a procedure designed to answer that specific risk.

A significant risk is one that requires special audit consideration because of its nature or assessed risk of material misstatement.

• Factors include fraud, unusual transactions, complexity, subjectivity, uncertainty, and significant related-party activity.
• I document why the risk is significant and understand the controls that address it, even when the audit remains primarily substantive.
• The response uses procedures specifically responsive to that risk and does not rely only on broad analytical procedures.

I scope the audit around where a material misstatement could arise, not simply around the largest balances.

• I consider account size, transaction volume, susceptibility to fraud or error, complexity, change, and relevant disclosures.
• For locations, I assess both financial significance and specific risks that could be concentrated in a smaller component.
• I document why each area is subject to controls testing, substantive work, analytical procedures, or no further work.

I select materiality from an appropriate benchmark and percentage, then apply qualitative judgment.

• The benchmark should reflect what users focus on, such as profit before tax, revenue, assets, or expenses, and should be normalized when results are volatile.
• The percentage depends on the entity, ownership, financing, stability, and the sensitivity of users rather than a fixed firm default.
• I document the benchmark, adjustments, percentage, and qualitative factors that could make a smaller misstatement material.

Performance materiality reduces the chance that uncorrected and undetected misstatements together exceed overall materiality.

• It is set below overall materiality based on prior errors, control quality, transaction complexity, and expectations about current-period misstatements.
• A higher assessed risk or history of adjustments generally supports a lower performance materiality amount.
• It drives the extent of testing, but it does not replace evaluation of qualitative misstatements.

Tolerable misstatement is the amount applied to a particular sampling application or account so the audit stays within performance materiality.

• Some methodologies use the terms similarly, but the engagement must follow the definitions in its applicable standards and firm guidance.
• Allocations consider account risk, expected error, population size, and whether misstatements could accumulate across several areas.
• The sum of account allocations may exceed performance materiality because simultaneous maximum errors are unlikely, but the rationale must be controlled and documented.

The clearly trivial threshold filters out items that are inconsequential individually and in aggregate.

• It is set well below overall and performance materiality and is not another form of materiality.
• Items above it are accumulated for evaluation even when management initially expects no adjustment.
• Qualitative matters such as fraud, covenant effects, or management compensation are considered regardless of amount.

Materiality is revised when actual results or new information would have changed the original judgment.

• A large change in profit, disposal of a business, financing event, or shift in user focus can make the original benchmark inappropriate.
• I assess whether performance materiality and clearly trivial thresholds must also change.
• If the threshold falls, I reconsider scope, sample sizes, completed procedures, and the evaluation of recorded and uncorrected differences.

I assess estimation uncertainty, complexity, subjectivity, and susceptibility to management bias before designing procedures.

• I understand the method, significant assumptions, data, controls, model changes, and the expertise used by management.
• I consider the range of reasonably possible outcomes and whether a small change in an assumption could create a material difference.
• Higher uncertainty or weak controls leads to more persuasive evidence and greater involvement from experienced team members or specialists.

I choose among testing management's process, developing an independent estimate or range, and evaluating subsequent events.

• Testing management's process covers the method, assumptions, source data, mathematical accuracy, and relevant controls.
• An auditor-developed point estimate or range needs support from reliable data and assumptions that are consistent with the reporting framework.
• Events after the measurement date can provide strong evidence only when they reflect conditions that existed at that date.

I look for a pattern of directional judgments rather than treating each estimate in isolation.

• Retrospective review compares prior estimates with actual outcomes while separating hindsight from information available at the earlier date.
• Consistently optimistic assumptions, selective model changes, or values clustered at a favorable edge of a reasonable range may indicate bias.
• Bias affects the fraud risk assessment and the evaluation of estimates collectively, even when each estimate is individually supportable.

The hierarchy indicates the observability of inputs, so evidence becomes more judgmental from Level 1 to Level 3.

• Level 1 quoted prices in active markets can often be tested to independent market data and ownership records.
• Level 2 testing focuses on observable inputs, adjustments, and whether the market and instrument are genuinely comparable.
• Level 3 requires deeper work on valuation models, significant unobservable inputs, sensitivity, disclosures, and possible management bias.

A specialist strengthens technical work but does not transfer the auditor's responsibility for the conclusion.

• The team evaluates the specialist's competence, capability, objectivity, and whether the planned scope addresses the audit risk.
• The auditor provides complete facts, defines the question, and understands enough of the method and assumptions to evaluate the work.
• Differences between the specialist and management are resolved and documented before the team concludes on the estimate.

Both frameworks use a five-step model that recognizes revenue as promised goods or services transfer to the customer.

• Identify the contract and its performance obligations, then determine the transaction price, including variable consideration and financing effects.
• Allocate the price to performance obligations using relative standalone selling prices.
• Recognize revenue when or as each obligation is satisfied, based on whether control transfers at a point in time or over time.

Auditing standards presume a fraud risk in revenue because reported performance can create strong incentives and multiple opportunities for manipulation.

• The team identifies which revenue streams, assertions, or transaction types create the risk instead of labeling all revenue identically.
• If the presumption is rebutted, the reasons must be specific, persuasive, and documented under the applicable standards.
• The response commonly emphasizes occurrence, cutoff, side agreements, returns, and unusual entries based on the identified scheme.

Both areas can accelerate revenue through optimistic estimates or recording activity in the wrong period.

• Variable consideration requires evidence for rebates, returns, bonuses, penalties, and the constraint on amounts that may later reverse.
• Cutoff testing links shipping or service evidence, contract terms, acceptance, invoices, and ledger dates around period end.
• Subsequent credits, returns, cash receipts, and contract modifications can corroborate or contradict the year-end conclusion.

Lease auditing starts with completeness because an accurate calculation cannot correct an omitted contract.

• I assess the process for identifying leases and embedded leases across procurement, property, and service arrangements.
• Testing covers lease term, discount rate, payments, options, modifications, classification, and the mathematical accuracy of right-of-use assets and liabilities.
• I reconcile the lease population to contracts, expenses, cash disbursements, and disclosures rather than relying only on the lease system export.

Consolidation scope follows the applicable control model, not simply legal ownership above a fixed percentage.

• Under voting-interest models, the analysis considers voting rights and the ability to direct relevant activities.
• Variable-interest or structured-entity models also examine economic exposure and who has power over the activities that drive returns.
• Changes in agreements, protective rights, de facto control, acquisitions, and disposals are evaluated at the date control changes.

I test both the completeness of reporting units and the mechanics that turn their records into consolidated statements.

• Procedures cover reporting packages, consistent accounting policies, currency translation, mapping, and consolidation system access.
• Intercompany balances and transactions are matched and eliminated, while unrealized profit and noncontrolling interests are recalculated.
• Top-side entries and late adjustments receive focused testing because they may bypass normal transaction controls.