Accountant interview questions

I treat them as three layers with a clear order of authority.

• GAAP or IFRS and applicable regulator rules define the accounting that is permitted; an internal policy cannot override them.
• Company policy selects and documents the method used where guidance allows judgment, such as an inventory cost method or capitalization threshold.
• Procedures turn that policy into named data sources, entries, controls, owners, and evidence for the close.

I run the policy library as a controlled source of truth, not a folder of static documents.

• Every policy has a scope, technical owner, approver, effective date, version history, and links to the relevant guidance.
• New standards, transactions, audit findings, and changes in business models trigger review rather than waiting for an annual refresh.
• Approved changes flow into training, ERP configuration, close instructions, controls, and disclosures so practice stays aligned with the policy.

I classify the change by what actually changed because the reporting treatment is different.

• A change in principle replaces one acceptable accounting method with another and is generally applied retrospectively under ASC 250 or IAS 8.
• A change in estimate reflects new information about an existing uncertainty and affects the current and future periods prospectively.
• An error means prior financial statements misapplied guidance or used information that was available, which may require revision or restatement.

A decision-ready memo makes the conclusion reproducible from the facts and authoritative guidance.

• It states the accounting question, relevant contract terms, transaction timeline, and assumptions without mixing facts with conclusions.
• It compares the credible alternatives, cites the controlling paragraphs, and explains why the selected view fits the substance of the transaction.
• It finishes with the entries, disclosures, control implications, approvers, and any judgments that must be reassessed later.

COSO works as an integrated system, so transaction controls alone are not enough.

• The control environment sets authority, accountability, competence, and tone; risk assessment identifies what could prevent reliable reporting.
• Control activities respond to those risks, while information and communication get reliable data and exceptions to the right people.
• Monitoring uses ongoing review and separate evaluations to determine whether the other components still operate and deficiencies are corrected.

Entity-level controls shape the organization broadly, while process controls address specific transaction and reporting risks.

• Board oversight, the code of conduct, delegation of authority, and management's risk assessment can affect many accounts and locations at once.
• A three-way match, bank reconciliation, or revenue approval is tied to a defined process, assertion, population, and frequency.
• A precise entity-level review can reduce reliance on lower-level controls, but a general tone or policy cannot replace a control over a specific material risk.

I start with the reporting risk and assertion, then choose a control that can actually prevent or detect that misstatement.

• Revenue occurrence calls for evidence that recorded sales are valid, while revenue completeness calls for evidence that the full population reached the ledger.
• The control description names the population, performer, frequency, review threshold, source data, and evidence retained.
• I challenge the control's precision against the possible size of error; a high-level variance review may not detect a material issue hidden inside an aggregate balance.

Those labels describe when a control acts and how it is performed, and each combination has different dependencies.

• Preventive controls, such as an ERP approval block, stop an invalid transaction before posting; detective controls, such as a reconciliation, find an error afterward.
• Automated controls can cover every transaction consistently but depend on configuration, access, change management, and reliable inputs.
• Manual controls handle judgment and unusual items well, but their quality depends on reviewer competence, precision, and retained evidence.

Automated accounting controls are reliable only if the systems supporting them are controlled.

• Access controls protect who can post, approve, change configurations, or alter reports, including privileged and emergency access.
• Program-change controls establish that tested and approved code or configuration reaches production without unauthorized changes.
• Computer operations controls cover interfaces, scheduled jobs, backups, and incident handling, so a failed feed or batch does not silently produce incomplete accounting.

Materiality is whether an omission or misstatement could influence a reasonable user's decision, not a universal percentage.

• A quantitative benchmark based on profit, revenue, assets, or equity is a starting point chosen for the entity and reporting context.
• Qualitative factors can make a smaller item material, such as changing a trend, hiding covenant failure, affecting compensation, or involving fraud.
• I assess individual items and their aggregate effect across statements, disclosures, periods, and business segments.

I evaluate the error against the financial statements as a whole and document both amount and nature.

• I determine whether it is a factual error, a judgmental difference, or a projected error from a tested sample, and identify every affected account and disclosure.
• I assess current-period and prior-period effects, including tax, covenant, segment, trend, and management-compensation consequences.
• The conclusion states whether to correct, revise, restate, or leave unadjusted, with the qualitative factors and governance approvals made explicit.

I keep a complete roll-forward and evaluate errors under both the rollover and iron-curtain views where US GAAP applies.

• The rollover method focuses on the amount by which the current-period income statement is misstated.
• The iron-curtain method focuses on the cumulative misstatement remaining on the current balance sheet.
• I include reversals, tax effects, similar errors, and qualitative factors so individually small items do not escape evaluation through fragmentation.

Effective close governance makes dependencies, ownership, review, and escalation visible before the deadline.

• The calendar links each deliverable to a preparer, reviewer, source dependency, due time, and downstream reporting impact.
• Stable work moves into pre-close, while critical estimates and interfaces receive earlier checkpoints and named contingency owners.
• Late entries, missed reviews, reopened periods, and unresolved reconciliations follow defined approval and escalation rules rather than informal exceptions.

Certifications create explicit accountability for the completeness and quality of a reporting package, but they do not replace evidence.

• Each signer confirms a defined scope, such as an entity, account group, disclosure, control set, or known exception.
• The certification references completed reconciliations, control results, representation questions, and unresolved matters rather than asking for a blanket sign-off.
• Exceptions remain visible with owners and disposition, and false or unsupported certification is escalated through the controller and disclosure process.

A quality close produces supportable balances and disclosures without relying on late cleanup.

• Reconciliations prove the composition and validity of balances, including aged items, estimates, and subledger-to-ledger agreement.
• Journal controls establish a valid source, appropriate approval, correct period and entity, and a clear audit trail for manual entries.
• Analytical review connects movements across the income statement, balance sheet, cash flow, and operating drivers, with unusual relationships resolved before release.

A sound consolidation architecture creates one controlled path from local books to group financial statements.

• A common chart or governed mapping translates local accounts, entities, currencies, and movement types into group reporting dimensions.
• Submission packages pass validation for balance, ownership, periods, intercompany counterparties, and required disclosures before consolidation.
• The consolidation engine records eliminations, ownership changes, currency translation, top-side entries, and approvals with a reproducible audit trail.

I base the scope on control and the applicable consolidation model, not legal ownership percentage alone.

• Under the voting-interest model, I assess power over relevant activities and exposure to returns, including substantive rights held by other parties.
• For variable-interest entities, I assess whether the company has both power over the significant activities and potentially significant economics.
• The entity register documents subsidiaries, equity-method investments, joint arrangements, acquisitions, disposals, and scope conclusions with reassessment triggers.

Intercompany activity should be matched at the source and eliminated without hiding genuine differences.

• Both sides use a common counterparty, transaction identifier, currency, and cutoff so receivables, payables, revenue, expense, and funding can be paired.
• Consolidation eliminates matched balances and transactions plus unrealized profit in assets that remains inside the group.
• Timing, foreign-exchange, classification, and missing-entry differences stay visible with owners; a top-side plug is not a substitute for resolution.

Functional currency reflects the primary economic environment, while remeasurement and translation solve different reporting problems.

• Foreign-currency transactions are remeasured into an entity's functional currency, with exchange effects generally recognized in earnings.
• A foreign operation's functional-currency statements are translated into the group's reporting currency, with translation effects generally recorded in OCI.
• The functional-currency conclusion follows cash flows, pricing, financing, and operating autonomy and is reassessed when underlying economic facts change.

I preserve one controlled transaction base and maintain explicit adjustments for each reporting framework.

• A differences register maps topics such as leases, development costs, impairment, provisions, and presentation to the affected accounts and disclosures.
• Separate adjustment ledgers or consolidation layers retain framework-specific entries without overwriting local statutory books or the primary GAAP view.
• Every difference has a policy owner, recurring close control, tax assessment, disclosure consequence, and reconciliation between the two reported results.