Technical Accounting Interview Questions: Revenue Recognition, Leases, Consolidations, and ASC/IFRS Judgment

A general accountant interview checks whether you can define debits and credits, walk through the month-end close, and describe your software experience. Technical accounting interview questions start one level deeper: the interviewer already assumes you know the mechanics, and they are testing whether you can apply judgment to a transaction that does not fit a template.

These interviews are common for technical accounting manager, SEC reporting, senior auditor, and controller roles, but they also show up as a dedicated "technical round" inside broader staff or senior accountant interview loops at companies with complex transactions — software contracts, real estate leases, acquisitions, or multiple entities that need to be consolidated.

Expect the interviewer to give you a fact pattern rather than a definition question. Instead of "what is revenue recognition," you will hear something closer to: "We sold a three-year software license bundled with implementation services and ongoing support. Walk me through how you would recognize revenue." The interviewer is listening for your process — how you identify the relevant guidance, how you break the transaction into its components, and how you land on a conclusion — not just the final number.

Before the interview, review the standards most relevant to the company's business model. A SaaS company will lean on ASC 606; a retailer with store leases will lean on ASC 842; a company that has made acquisitions will expect consolidation and purchase accounting questions. Map your own transaction history to these areas so you have a specific example ready, not just the textbook rule.

Revenue recognition is the single most common topic in technical accounting interview questions, because nearly every company has revenue and the five-step model gives interviewers an easy framework to test judgment against.

**"Walk me through the ASC 606 five-step model."**

Interviewers ask this to confirm you have the framework memorized before they hand you a scenario that requires applying it.

Sample answer: "The five steps are: identify the contract with the customer, identify the distinct performance obligations in the contract, determine the transaction price, allocate the transaction price to each performance obligation based on standalone selling price, and recognize revenue as each performance obligation is satisfied — either at a point in time or over time. The judgment calls usually show up in steps two, three, and four: whether a good or service is distinct, how to estimate variable consideration, and how to allocate price when you do not have observable standalone selling prices."

**"We sold a bundled contract with a software license, implementation, and one year of support. How do you recognize the revenue?"**

Sample answer: "First I would determine whether the license is distinct from the implementation. If the implementation is highly customized and the customer cannot use the license without it, they may not be distinct and should be combined into a single performance obligation recognized over time. If the license is functional on its own and implementation is more of a setup service, I would treat them as separate performance obligations. Support is almost always distinct and recognized ratably over the contract term. I would allocate the total transaction price across the performance obligations based on standalone selling price — using observable prices if we sell any of these separately, or an estimation method like expected cost plus margin if we do not. Then each obligation recognizes revenue as it is satisfied: the license typically at a point in time when control transfers, support ratably over the year, and implementation either over time or at completion depending on the pattern of benefit."

**"How do you handle variable consideration, like a volume rebate or a performance bonus?"**

Sample answer: "I estimate variable consideration using either the expected value method — a probability-weighted average of possible outcomes — or the most likely amount method, whichever better predicts the amount we are entitled to. Then I apply the constraint: I only include variable consideration in the transaction price to the extent it is probable that a significant reversal will not occur when the uncertainty resolves. For a volume rebate, I would look at historical customer purchasing patterns to estimate the expected rebate, true it up each period as actual volumes become clearer, and document the basis for the estimate so it holds up under audit review."

When you answer revenue recognition interview questions, resist the urge to recite the standard from memory. Interviewers can tell the difference between a candidate who memorized ASC 606 and one who has actually applied it to messy, real contracts.

Lease accounting is a reliable source of technical accounting interview questions, particularly since ASC 842 brought operating leases onto the balance sheet and created a steady stream of judgment calls around classification, discount rates, and modifications.

**"What changed under ASC 842, and how do you classify a lease?"**

Sample answer: "Under ASC 842, both finance and operating leases go on the balance sheet as a right-of-use asset and a corresponding lease liability, which is the biggest change from the prior standard. Classification still matters for the income statement pattern: a finance lease front-loads expense through separate interest and amortization, while an operating lease produces a single straight-line expense. I classify a lease by testing the five finance-lease criteria — transfer of ownership, a purchase option the lessee is reasonably certain to exercise, a lease term covering the major part of the asset's remaining economic life, the present value of payments approximating substantially all of the asset's fair value, or the asset being so specialized it has no alternative use to the lessor. If none of those are met, it is an operating lease."

**"How do you determine the discount rate for a lease when the rate implicit in the lease is not readily determinable?"**

Sample answer: "Most lessees cannot determine the rate implicit in the lease because they do not have visibility into the lessor's residual value assumptions or initial direct costs. In that case, ASC 842 has us use the incremental borrowing rate — the rate we would pay to borrow, on a collateralized basis, an amount equal to the lease payments over a similar term. I would work with treasury or use a rate derived from our existing borrowing facilities, adjusted for the lease term and the fact that the asset itself provides collateral. Private companies can elect a risk-free rate as a practical expedient instead."

**"A lease gets modified midterm — the customer adds five thousand square feet to an existing office lease. How do you account for it?"**

Sample answer: "The first question is whether the modification is a separate contract. If the additional space is priced at its standalone value and the modification grants an additional right of use, it is accounted for as a separate new lease. If it is not priced at standalone value, I would remeasure the original lease: recalculate the lease liability using the revised payments and an updated discount rate as of the modification date, and adjust the right-of-use asset by the same amount. I would also reassess the lease classification as of the modification date, since a significant change in scope or term can shift a lease from operating to finance or vice versa."

Employers ask lease accounting interview questions to see whether you understand the reasoning behind classification and remeasurement, not just the mechanical steps — so narrate your logic, not just your conclusion.

Consolidation questions show up in technical accounting interviews at companies with subsidiaries, joint ventures, or an active acquisition strategy. Interviewers use them to test whether you understand control, not just mechanical elimination entries.

**"How do you determine whether to consolidate an entity?"**

Sample answer: "The starting point is whether the entity is a variable interest entity or a voting interest entity. For a voting interest entity, control is generally established by owning more than fifty percent of the voting shares. For a VIE, the analysis is different — I would look at which party has the power to direct the activities that most significantly affect the entity's economic performance, and which party absorbs the majority of the expected losses or benefits. If we hold that combination of power and economic exposure, we consolidate even without majority ownership. This distinction matters a lot in structures involving special purpose entities or entities with disproportionate voting versus economic rights."

**"Walk me through the basic mechanics of consolidating a subsidiary."**

Sample answer: "We combine the parent and subsidiary financial statements line by line, then eliminate intercompany transactions and balances — intercompany receivables and payables, intercompany revenue and cost of sales, and any unrealized profit sitting in inventory from intercompany sales. If the subsidiary is not wholly owned, we recognize noncontrolling interest for the portion of equity and net income attributable to outside shareholders, presented separately within equity and net income on the consolidated financial statements."

**"How do you account for a business combination on the acquisition date?"**

Sample answer: "Under the acquisition method, I would first determine the acquisition date and the consideration transferred, including any contingent consideration measured at fair value. Then I identify and measure the identifiable assets acquired and liabilities assumed at fair value as of the acquisition date — this often requires a valuation specialist for intangibles like customer relationships, developed technology, or trade names. Any excess of consideration transferred over the net fair value of identifiable assets and liabilities gets recorded as goodwill. If the fair value of net assets exceeds the consideration, that is a bargain purchase, and the difference is recognized as a gain — though that outcome is rare and worth double-checking the valuation before concluding."

Consolidation and business combination questions reward candidates who can explain the underlying logic of control and fair value measurement in plain terms, since these topics often need to be communicated to non-technical stakeholders like the audit committee.

Interviewers often ask you to draft or narrate journal entries live, both to confirm mechanical competence and to see how you handle a transaction that requires judgment before you can even post the entry.

**"Record the journal entry for a $2 million impairment of goodwill."**

Sample answer: "I would debit impairment loss for $2 million and credit goodwill for $2 million. Before I get to that entry, though, I would confirm the impairment testing methodology — comparing the reporting unit's carrying value, including goodwill, to its fair value, and recognizing an impairment loss for the excess of carrying value over fair value, limited to the amount of goodwill allocated to that reporting unit. I would also document the triggering event and the valuation approach used, since goodwill impairment is a heavily scrutinized area in an audit."

**"How do you account for a change in accounting estimate versus a correction of an error?"**

Sample answer: "A change in estimate — like revising the useful life of an asset based on new information — is accounted for prospectively. You do not restate prior periods; you simply apply the new estimate going forward. A correction of an error, on the other hand, means the prior financial statements were wrong based on information available at the time. That requires evaluating materiality and, if material, restating prior period financial statements or disclosures. The distinction matters because misclassifying an error correction as an estimate change, or vice versa, can misstate how the change is presented and disclosed."

**"How do you decide between GAAP and IFRS treatment when a parent company reports under one framework and a subsidiary operates under the other?"**

Sample answer: "The consolidated financial statements need to be prepared under a single framework, so I would identify the material differences between GAAP and IFRS for the subsidiary's significant transactions — commonly around revenue recognition timing, lease classification, inventory costing methods like LIFO, which IFRS does not permit, and development cost capitalization. I would work with local finance teams to convert the subsidiary's IFRS-based trial balance to GAAP through a reconciliation, document each adjustment with its rationale, and keep a standing conversion schedule since many of these differences recur every period."

These ASC and IFRS judgment questions are less about reciting a rule and more about showing you can identify which rule applies and defend the conclusion if someone in the room pushes back.

Some technical accounting interview questions are not about a specific standard at all — they test your research process when you encounter a transaction you have not seen before.

**"You come across a transaction that is not clearly addressed by existing guidance. What do you do?"**

Sample answer: "I start by searching the FASB Accounting Standards Codification for the closest analogous guidance, using the codification's topic structure to narrow down where the transaction likely fits. I look at whether other companies with similar transactions have disclosed their accounting policy in public filings, which I can find through the SEC's EDGAR database. If the guidance is genuinely ambiguous, I would draft a technical accounting memo laying out the fact pattern, the relevant authoritative guidance, alternative views, and a recommended conclusion, and I would route that memo to the controller or an external technical accounting advisor before finalizing the position."

**"What does a good technical accounting memo look like?"**

Sample answer: "It starts with a clear statement of the issue and the background facts — enough detail that someone unfamiliar with the transaction can follow the analysis. Then it lays out the relevant authoritative literature, walks through the application of that literature to the specific facts, addresses any reasonable alternative interpretations and why they were not selected, and ends with a clear conclusion. I keep the tone objective rather than advocacy-driven, because the memo needs to hold up if an auditor or regulator reviews it later."

**"How do you stay current on new accounting standards before they take effect?"**

Sample answer: "I follow FASB exposure drafts and final standards directly, and I read the transition disclosures other companies in our industry include in their 10-Ks, since those often preview how peers are interpreting ambiguous areas. For a major standard like a new revenue or lease standard, I build an implementation timeline well before the effective date — assessing the population of affected contracts or leases, documenting policy elections, and running parallel calculations before go-live so there are no surprises at the first reporting period under the new guidance."

Accounting research questions reward candidates who can describe a repeatable process, not just a one-off answer, because interviewers want confidence you can handle whatever transaction shows up next, not just the ones covered in this interview.

Reading model answers builds recognition. Speaking them out loud, under time pressure, with an interviewer waiting for your next sentence, is a different skill entirely.

Technical accounting interview questions are especially unforgiving to practice on paper alone, because the answers require you to sequence a multi-step analysis correctly — identify the issue, cite the relevant guidance, apply it to the facts, state your conclusion — while an interviewer may interrupt with a follow-up that changes the fact pattern midway through. A candidate who has only read about the five-step revenue model on a study guide often stumbles the moment the interviewer adds a wrinkle, like a right of return or a material right for a future discount.

The most common breakdown points are the scenario-based questions: "walk me through how you would account for this transaction," or "what would you do if the auditor disagreed with your conclusion." These require you to think out loud and stay organized without notes, and that gets noticeably harder under real interview pressure.

Practice helps with three things specifically: recall speed for the right standard and its key criteria, delivery fluency so a multi-step analysis flows without backtracking, and composure when a follow-up question changes the scenario.

SayNow AI's job interview scenario gives you a realistic spoken practice environment for technical accounting interview questions. You answer out loud, and the AI follow-up questions probe the way a real interviewer would — asking you to justify a judgment call or handle a variation on the original fact pattern. Run through revenue recognition, lease accounting, consolidations, and journal entry scenarios until your explanations sound like a conversation with a colleague, not a recitation from a textbook.