About Accounts Assistant interviews
Accounts Assistant interviews are usually short and practical — most processes run to two stages. The first is typically a screen with a recruiter or finance team lead checking your eligibility, notice period, salary expectation, software familiarity (Sage, Xero, QuickBooks, SAP, NetSuite or similar) and whether you've handled purchase ledger, sales ledger or both. The second stage is conducted by the Finance Manager or Financial Controller and is more hands-on: expect detailed questions about invoice processing, supplier statement reconciliations, bank reconciliations, expense claims and how you spot and resolve discrepancies. Many employers add a short Excel test or a paper-based exercise where you match invoices to purchase orders or identify a coding error. Hiring managers are screening for accuracy under volume, comfort with high-frequency repetitive tasks, and the judgement to query something rather than process it blindly. The most common stumble is candidates talking only in general terms — 'I'm good with numbers and detail' — without being able to walk through a reconciliation step by step or explain what they'd do when a supplier statement doesn't agree to the ledger. The second stumble is underselling soft skills: chasing suppliers, handling internal queries and meeting month-end deadlines all require communication and composure. Candidates who quantify their workload (invoices per week, ledgers managed) and show curiosity about controls tend to stand out in an otherwise interchangeable field.
Typical stages
- Recruiter / finance team screen
- Finance Manager interview
- Excel or accounts processing test
- Final values / team fit
Common formats
- Behavioral STAR
- Excel / spreadsheet test
- Paper-based reconciliation exercise
- Competency questioning
- Scenario / situational discussion
What hiring managers screen for
- Accuracy and attention to detail under high transaction volume
- Hands-on familiarity with named accounting software and ledgers
- Willingness to query and escalate discrepancies rather than process blindly
- Ability to meet month-end and payment-run deadlines
- Clear communication with suppliers and internal stakeholders
Red flags to avoid
- Cannot walk through a bank or supplier statement reconciliation step by step
- Vague claims of being 'good with numbers' without concrete examples
- No awareness of basic controls (duplicate payments, fraudulent invoices, segregation of duties)
- Casual attitude to errors or no method for checking their own work
- Inability to name or describe the accounting systems they've actually used
Primary questions (15)
Behavioural
Tell me about a time you found an error in an invoice, ledger or payment before it was processed.
Why this comes up: Catching errors before they become incorrect payments is the core value an Accounts Assistant adds.
Prep pointers
- Pick an example where the error had real financial consequence if missed (duplicate payment, wrong amount, wrong supplier).
- STAR: Situation — what you were processing; Task — what you were checking against; Action — exactly how you spotted and verified it; Result — what was prevented and any process change.
- Show the checking habit, not luck — explain the routine that surfaced it.
- Avoid framing it as a colleague's blunder; focus on your detection and resolution.
Behavioural
Describe a time you had to meet a tight month-end or payment-run deadline with a heavy workload.
Why this comes up: Month-end and payment runs are immovable deadlines that define the rhythm of the role.
Prep pointers
- Quantify the volume — invoices processed, ledgers closed, hours worked.
- STAR: Action should show how you prioritised and what you did to protect accuracy under time pressure.
- Mention how you communicated progress or risk to your manager.
- Avoid suggesting you simply worked late and rushed — show method, not heroics.
Behavioural
Tell me about a time a supplier disputed a payment or chased an overdue invoice. How did you handle it?
Why this comes up: Supplier relationships and query resolution are a daily part of the accounts function.
Prep pointers
- Choose an example that shows composure and investigation, not just appeasement.
- STAR: Action should cover how you traced the discrepancy in the ledger and what evidence you gathered.
- Highlight balancing the supplier relationship with protecting the business from incorrect payment.
- Avoid stories where you escalated immediately without doing your own checks first.
Behavioural
Give an example of a repetitive, high-volume task you improved or made more efficient.
Why this comes up: Employers want to see initiative within an otherwise routine, transactional role.
Prep pointers
- Pick a tangible improvement — a template, a reconciliation tweak, a filing or coding routine.
- STAR: Result should quantify time saved or errors reduced where possible.
- Show you respected existing controls while improving the process.
- Avoid changes that sound like you bypassed approval steps for speed.
Technical
Walk me through how you would perform a supplier statement reconciliation.
Why this comes up: It is a fundamental purchase ledger task and a quick test of whether you actually do the work hands-on.
Prep pointers
- Describe the steps end to end: obtain statement, match to ledger, identify open items, investigate differences.
- Name common reasons for differences — missing invoices, timing, credit notes, unallocated payments.
- Explain how you resolve each type of difference and when you'd escalate.
- Avoid jargon-only answers; show the practical sequence you actually follow.
Technical
How would you carry out a bank reconciliation and what do you do when it doesn't balance?
Why this comes up: Bank reconciliations are a core control check that an Accounts Assistant is often trusted with.
Prep pointers
- Explain matching the bank statement to the cash book and identifying outstanding items.
- Cover the systematic approach to an out-of-balance reconciliation — checking transposition, timing, duplicates.
- Mention not forcing a balance and the importance of explaining every difference.
- Reference the accounting software you've used to do this.
Technical
Which accounting systems and Excel functions do you use day to day, and how?
Why this comes up: Software fluency directly affects how quickly you can be productive in the role.
Prep pointers
- Name specific systems (Sage, Xero, QuickBooks, SAP, NetSuite) and the modules you used.
- Mention Excel functions you genuinely use — VLOOKUP/XLOOKUP, SUMIF, pivot tables, filters.
- Tie functions to real tasks, e.g. matching ledger data or summarising aged creditors.
- Avoid overstating proficiency you can't demonstrate in a test.
Technical
Explain the difference between accounts payable and accounts receivable, and the typical process flow for each.
Why this comes up: It confirms foundational understanding of the ledgers an Accounts Assistant supports.
Prep pointers
- Clearly distinguish purchase ledger (money out) from sales ledger (money in).
- Outline the lifecycle: PO/invoice receipt, coding, approval, payment for AP; invoicing, credit control, receipt allocation for AR.
- Mention controls like three-way matching and credit limits.
- Avoid mixing up debits and credits — be precise.
Situational
You receive an invoice with no purchase order and no obvious approver. What do you do?
Why this comes up: Tests judgement around controls and whether you'll process something without proper authorisation.
Prep pointers
- Show you would not pay without authorisation — controls come first.
- Describe tracing the goods/service to a likely budget holder or department.
- Mention logging it on hold and escalating if it can't be substantiated.
- Avoid answers that prioritise keeping the supplier happy over due process.
Situational
You spot what looks like a duplicate payment that has already gone out the door. What's your next step?
Why this comes up: How you handle an error already made reveals integrity and escalation judgement.
Prep pointers
- Emphasise reporting it immediately rather than hiding it.
- Describe verifying it's genuinely a duplicate using the ledger and bank records.
- Mention recovering funds from the supplier and adding a control to prevent recurrence.
- Avoid any hint of covering up or delaying disclosure.
Situational
It's the busiest day of month-end and your system goes down. How do you keep things moving?
Why this comes up: Resilience and prioritisation under disruption are valued in a deadline-driven function.
Prep pointers
- Show calm prioritisation — identify what's deadline-critical versus what can wait.
- Mention preparing offline (logging invoices, drafting reconciliations) ready to input later.
- Cover communicating status and revised expectations to your manager.
- Avoid implying you'd simply stop working until IT fixed it.
Competency
How do you ensure accuracy and check your own work when processing high volumes of transactions?
Why this comes up: Accuracy under volume is the single most important competency for the role.
Prep pointers
- Describe concrete self-checking routines — batch totals, control accounts, second-pass reviews.
- Mention how you stay accurate when tired or rushed during peaks.
- Give a sense of your error rate or how you track and learn from mistakes.
- Avoid generic claims like 'I'm just naturally careful' with no method behind them.
Competency
How do you prioritise when invoices, queries, reconciliations and chasing all land at once?
Why this comes up: The role constantly juggles competing demands and visible prioritisation skills matter.
Prep pointers
- Explain a clear framework — deadlines, payment-run dates, escalation risk.
- Mention how you handle interruptions without losing track of routine tasks.
- Show you'd flag conflicts to your manager rather than silently miss something.
- Avoid implying you treat everything as equally urgent.
Culture fit
What attracts you to an Accounts Assistant role and where do you see it leading?
Why this comes up: Employers want commitment to finance and a realistic view of progression (e.g. towards AAT or part-qualified roles).
Prep pointers
- Connect your interest to the practical, structured nature of transactional finance.
- Mention any study ambitions (AAT, ACCA) if relevant and genuine.
- Show enthusiasm for the specific business or sector, not just any accounts job.
- Avoid sounding like you see it purely as a stopgap.
Culture fit
How do you work as part of a small finance team where everyone covers for each other?
Why this comes up: Most Accounts Assistant roles sit in tight-knit teams where flexibility and reliability are essential.
Prep pointers
- Give an example of stepping in or covering a colleague's tasks.
- Show you document and hand over work cleanly so others can pick it up.
- Mention being approachable for queries from non-finance colleagues.
- Avoid presenting yourself as a strict 'that's not my job' type.
More practice questions (14)
Technical
What is a three-way match and why does it matter in purchase ledger processing?
Why this comes up: It's a key purchase-to-pay control an Accounts Assistant applies regularly.
Technical
How do you handle and record a credit note from a supplier?
Why this comes up: Credit notes are routine and mishandling them distorts the ledger.
Technical
What's the difference between gross, net and VAT on an invoice, and how do you code VAT correctly?
Why this comes up: Correct VAT treatment is essential and a common source of errors.
Technical
How would you prepare and interpret an aged creditors or aged debtors report?
Why this comes up: Aged reports drive payment runs and credit control decisions.
Technical
How do you allocate a customer receipt that doesn't match any single outstanding invoice?
Why this comes up: Part-payments and unallocated cash are everyday sales ledger challenges.
Behavioural
Tell me about a time you had to learn a new accounting system or process quickly.
Why this comes up: Employers want confidence you'll get up to speed on their software fast.
Behavioural
Describe a mistake you made in your work and how you dealt with it.
Why this comes up: Honesty and corrective action reveal integrity in a controls-sensitive role.
Situational
A budget holder pressures you to pay an invoice before it's been approved. How do you respond?
Why this comes up: Tests whether you hold the line on controls under internal pressure.
Situational
You notice the same supplier keeps submitting invoices with incorrect details. What would you do?
Why this comes up: Shows whether you fix root causes rather than just re-keying corrections.
Competency
How do you keep your filing and record-keeping organised for audit purposes?
Why this comes up: Audit-ready documentation is a baseline expectation in finance.
Competency
How do you communicate a finance issue clearly to a non-finance colleague?
Why this comes up: Accounts Assistants regularly explain coding, approvals and queries to other departments.
Culture fit
How do you stay motivated when the work is detailed and repetitive?
Why this comes up: Resilience to routine work predicts retention in transactional finance roles.
Technical
What controls help prevent fraudulent or duplicate invoice payments?
Why this comes up: Awareness of payment fraud risks is increasingly expected.
Situational
Your reconciliation shows a small unexplained difference and the deadline is in an hour. What do you do?
Why this comes up: Tests whether you'll investigate properly or simply force a balance under pressure.
Researching the Accounts Assistant role?
See the full skills, salary and market breakdown — what employers
actually want, and the biggest skills gaps.
Accounts Assistant skills & salary →
Get a prep pack tailored to your experience
describe.me matches these questions against your real work history,
flags your prep priorities, and gives you a STAR scaffold per question.
Start free →