Accountant
Structured interview questions for Accountant, with what a strong answer surfaces for each one.
BehavioralVigilance and internal control Describe the last significant accounting anomaly you discovered. How did you escalate it?
What a strong answer surfacesVigilance and the ability to structure an escalation: the candidate describes the detection, the quantification of the effect and the communication to superiors (management, tax advisor, auditor depending on severity). Bonus: a control proposal to prevent a recurrence. Candidates who have never seen an anomaly work in heavily siloed structures or bring no critical eye.
BehavioralAutonomy under pressure Tell me about a particularly intense month-end or year-end close. What happened, and what did you learn from it?
What a strong answer surfacesCalm under pressure: the ability to prioritize under a deadline (accruals, clearing of account balances, P&L preparation) and to ask for help when needed. Bonus: the candidate built a checklist or schedule for subsequent closes afterward. Someone who describes a close where everything went smoothly is either lying or has never closed autonomously.
BehavioralCross-functional communication Describe a situation where you had to explain an accounting topic to a non-finance person (sales, management, operations).
What a strong answer surfacesAbility to translate: rendering a technical concept in operational vocabulary without condescension or unnecessary jargon. Bonus: a concrete example (e.g. explaining why a payment received does not yet appear as revenue, or why an investment is not an expense entry). At an SMB the accountant is often the only financial point of contact; pedagogy is therefore critical.
SituationalTax compliance During the current month you notice that the previous month's VAT return (Umsatzsteuer-Voranmeldung) was understated by €8,000. What do you do?
What a strong answer surfacesA structured plan: (1) quantify the difference precisely by tracing the invoices, (2) identify the cause (incorrect coding, wrong tax rate, omission), (3) immediate escalation to management and to the tax advisor, (4) correction via an amended VAT return under § 153 AO within the deadline, or a correction in the current return depending on the situation. Anyone who proposes quietly catching up the difference in the next VAT return is an immediate exclusion: a high risk of tax evasion (§ 370 AO).
SituationalVigilance and internal control A salesperson urgently requests a €5,000 credit note to a customer with no supporting documents. How do you react?
What a strong answer surfacesThe ability to uphold the procedure without alienating the salesperson: request the document, briefly explain why (GoBD traceability, tax audit, commercial documentation), propose a pivot solution (a provisional credit note with a deadline to provide the document within 48 hours). Candidates who accept without discussion show a weakness in internal control; whoever refuses curtly shows a weakness in cross-functional communication.
SituationalTax compliance The tax advisor announces a GoBD audit in four weeks. How do you structure your preparation?
What a strong answer surfacesA structured plan: (1) an inventory of the procedural documentation (is there one, is it current?), (2) a sample audit against the ten GoBD requirements (traceability, completeness, accuracy, timely posting, order, immutability), (3) a check of the archiving situation (10-year retention obligation under § 257 HGB and § 147 AO), (4) documentation of the internal control system. Whoever reduces GoBD to audit-proof filing understates it; whoever treats it as a pure IT topic overlooks the process and documentation share.
CaseTechnical rigor Period accrual: an incoming invoice of €12,000 net arrives on 5 February for services performed in January. You close the financial year on 31 January. Which accrual entry do you make, and what effect on the annual result?
What a strong answer surfacesExpected answer: create an other liability (accrual on the liabilities side) as of 31 January, post expense €12,000 (debit) to other liabilities €12,000 (credit) (input VAT is only recognized when the invoice arrives, § 15 UStG). Result effect: -€12,000 in expense. Reversal in year N+1 when the invoice arrives. Someone who cannot book this standard accrual does not master the fundamentals.
CaseTechnical rigor Bank reconciliation: your bank account balance in the books is €45,000 as of 31 December; the bank statement shows €38,500. You identify: an issued check not yet cashed (€3,200), a deposited check still pending (€2,100), unposted bank charges (€180). Does the reconciliation hold? Where is the break in the balance?
What a strong answer surfacesMethod: book balance €45,000 - outstanding check €3,200 + pending deposit €2,100 = €43,900. Bank balance €38,500 + charges to post €180 = €38,680. Difference of €5,220 that must be investigated (probably miscoding, an unposted movement or a missing bank item). Candidates who declare the reconciliation correct without explaining the difference show a critical weakness.
CaseTechnical rigor Asset disposal: in May of year N you sell a company vehicle for €8,000 net. Acquisition cost €25,000 (May N-3), straight-line depreciation over 5 years, accumulated depreciation €15,000. Which entry do you make, and what is the gain or loss on disposal?
What a strong answer surfacesExpected answer: derecognize the asset (debit accumulated depreciation €15,000 + debit residual book value / disposal €10,000 / credit fixed assets €25,000), record the proceeds (debit receivable or bank €8,000 / credit gain on disposal €8,000, plus VAT if applicable). Gain or loss on disposal = €8,000 - €10,000 = -€2,000 (a loss). Someone who fails on this standard entry does not have the technical maturity for an autonomous mid-level role.
TechnicalTool command Which accounting software and which ERP did you use most recently? Describe the module you are most confident in, and one that gave you the most trouble.
What a strong answer surfacesConcrete familiarity with at least one modern accounting software (DATEV, SAP FI, Sage 100, Lexware, sevDesk) and the ability to talk about the module in detail (e.g. generate a balance-confirmation list, configure a bank journal, clear a vendor account). Admitting a difficulty shows honesty: candidates who claim to master every module are suspect.
TechnicalTool command You take over a role where the chart of accounts is poorly maintained: 1500-series and 1600-series payable/receivable accounts mixed up, clearing accounts never cleared. Which 60-day plan restores order?
What a strong answer surfacesA systematic method: (1) a complete audit of the general ledger and the trial balance, (2) identification of the dirtiest accounts with a material effect, (3) a plan to clear and recode in tranches with sign-off from management or the tax advisor, (4) a weekly control to prevent recurrence. Whoever answers I keep it clean without explaining how shows a lack of method.
TechnicalTechnical rigor Difference between HGB and IFRS in accounting for a lease? In which cases does a German SMB have to deal with it?
What a strong answer surfacesAnswer: under HGB an operating lease is recognized as an expense, a finance lease is capitalized as a fixed asset with a corresponding liability (IDW guidance). Under IFRS 16, virtually all leases are capitalized with a corresponding liability. A German SMB is affected if it has a parent or subsidiary in IFRS consolidation (a listed group or an IFRS-auditing firm). Candidates who know the HGB-IFRS logic without having applied IFRS are suitable for a mid-level role at a pure SMB; whoever has never heard of it is a warning sign at a group subsidiary.
ValuesCross-functional communication How do you take critical feedback from a tax advisor or auditor who points out a mistake on your side?
What a strong answer surfacesA learning posture: the candidate describes that they integrated the feedback (not just listened to it) and changed their own practice. Bonus: the candidate shared the learning with a colleague or documented a new control. Whoever describes having justified their own logic instead of accepting the comment shows a coachability weakness that creates problems in a tax audit.
ValuesCross-functional communication Describe your relationship with the tax advisor or auditor. What role do you play in that relationship?
What a strong answer surfacesA partnership posture: preparatory files, anticipation of audit points, structured communication of identified risks. Whoever describes the tax advisor as a cost item or the auditor as a burden shows a defensive posture that makes audits harder. Bonus: a concrete case where the candidate pushed through a recommendation against the firm's initial position.
ValuesVigilance and internal control An entry has an ambiguous effect: management asks you to treat a transaction in a way you find borderline. How do you react?
What a strong answer surfacesThe ability to say no without accusation by involving the tax advisor or auditor. Bonus: the candidate proposes a legal alternative that addresses management's actual need. Whoever answers I just do it without questioning does not protect the company in the event of a tax audit. Whoever refuses curtly shows a weakness in cross-functional communication.
Evaluation playbook
The Accountant role reveals itself across five evaluation stages. Stage 3 (technical case work) is the central filter: without proven technical reliability the other competencies have no foundation. This stage must not be cut short.
Stage 1: CV review
Look for: sector coherence (an accountant from wholesale works differently from one in industry or services), tenure (at least 24 months on previous accounting roles) and concrete tool mentions. A candidate who names DATEV, SAP FI or Sage 100 without detailing the modules (fixed-asset accounting, accounts receivable, banks) is a flag. Frequent moves are less of a problem in accounting than in sales, but 3 roles in 5 years require an explanation. Check whether the candidate mentions a certified-accountant qualification (Bilanzbuchhalter:in, IHK): that shifts the compensation and responsibility level.
Stage 2: Phone interview (30 min)
Three questions only: (1) Describe your current scope (monthly, annual, accounts receivable or payable, payroll included?), (2) Which accounting software and which ERP did you use most recently? Describe the module you are most confident in, (3) Why are you looking for a change now? (a clear narrative vs. scattered). Outcome: go/no-go in a 5-minute debrief.
Stage 3: Structured interview (90 min)
Work through the 15 questions below, alternating behavioral, situational, case, technical, values. On the case questions, have the candidate compute at the board or whiteboard (cut-off, a VAT accrual, the GoBD compliance of a document). At least 2 interviewers, ideally management or the tax advisor plus an experienced accountant. Independent scoring before the debrief.
Stage 4: Technical case (60-90 min)
Hand the candidate a concrete case in advance: a batch of accounting documents (incoming invoices, travel expenses, bank statements) to be coded independently, or a situation to analyze (e.g. an unexplained difference on a clearing account). Assess the method more than the speed: a good accountant names their own zones of uncertainty and asks targeted follow-up questions before proposing an entry. This stage is not optional: without it, you buy blind.
Stage 5: References (structured check)
Call two references: a former manager (management, commercial leadership) and a tax advisor (Steuerberater:in) or auditor (Wirtschaftsprüfer:in) who has worked with the candidate. Ask both the same four questions: What is she/he strongest at? Where would you hire someone complementary? Would you hire them again tomorrow? A concrete example of a technically complex problem they solved autonomously? The fourth question delivers the real signal: autonomy on non-routine technical topics.
How to recognize a great hire
| Trait | Below bar | On bar | Above bar |
|---|---|---|---|
| Technical rigor | Fails on period accruals, bank reconciliations or asset disposals at a standard level. Needs help for non-routine entries. May overlook a significant anomaly within their own scope. | Masters routine entries autonomously (accruals, fixed assets, VAT, payroll where applicable). Identifies anomalies within their scope and escalates them. Can justify accounts in an audit. | A technical reference on the team for non-routine topics (consolidation, merger, HGB-IFRS reconciliation). Anticipates risk areas before they become a problem. Trains juniors and structures the team's procedures. |
| Tool command | Uses a single, only partly mastered software. Slow or hesitant on advanced functions (journal parameters, automatic account clearing, balance lists). Spreadsheets at a basic level. | Masters one accounting software in full autonomy (typically DATEV, SAP FI, Sage 100 or Lexware), can extract and analyze data. Advanced spreadsheets (VLOOKUP, pivot tables, control formulas). | Able to set up new software or migrate a chart of accounts. Automates recurring tasks (scripts, macros, light SQL queries) and structures imports and exports with other systems (ERP, payroll, CRM). |
| Vigilance and internal control | Posts what is asked without questioning. No weekly or monthly control routine; anomalies are discovered only at the close, not earlier. | A structured control routine (reviewing clearing accounts, unusual entries, dormant accounts). Identifies and escalates anomalies within their scope during the month. | Builds and develops the function's internal control system: segregation matrices, written procedures, quality indicators. Anticipates risks before they materialize. |
| Cross-functional communication | Communicates only with the finance function. Avoids exchange with operations or uses inaccessible accounting jargon. Defensive on follow-up questions. | Can explain technical topics to a non-finance person in operational vocabulary. Maintains an accessible relationship with sales, operations and management. | A recognized financial point of reference in the company: other functions consult them spontaneously to anticipate the accounting impact of their decisions. Trains other functions in the key concepts (revenue vs. payment received, expense vs. investment, gross margin). |
| Autonomy under pressure | Frequently needs sign-off from a superior for non-routine entries. Visible stress under a deadline; an unforeseen case leads to a block. Defers ambiguous topics. | Autonomous on most entries and on the monthly close. Handles standard imponderables (a software outage, a missing document at the close) without unnecessary escalation. | Runs the close like a project manager: a documented checklist, anticipation of dependencies with other functions, a plan B for imponderables. Calm and decisive under pressure. |
30 / 60 / 90 day success plan
By day 30
- Understanding of the complete accounting scope (accounts receivable, payable, payroll where applicable, fixed assets, treasury)
- Audit of the chart of accounts and the trial balance; identification of the three to five dirtiest topics (poorly cleared accounts, hanging items, recurring problems)
- Autonomous handling of routine entries (incoming invoices, payments received, travel expenses)
- First documented 1:1 with management or commercial leadership on the priorities of the role
By day 60
- First month-end close performed autonomously, meeting the deadline
- Bank reconciliations automated or structured; clearing accounts cleaned up in under 30 days
- Dunning procedure formalized and held (D+15, D+30, D+45)
- Documented exchange with the tax advisor on current topics and identified risk areas
By day 90
- A stable month-end cadence maintained (2-3 consecutive closes without missing a deadline)
- First structured monthly financial reporting shared with management (revenue, margin, cash, points of attention)
- Documentation of the central procedures (month-end close, payroll, current tax filings, GoBD reference)
- Formal review with management or commercial leadership: development areas set for the next 90 days