Accounts Receivable Interview Questions & Answers

Model answer

"Accrual accounting records revenue when it's earned, not when cash is received. For AR, that means we recognise revenue at the point of sale and create a receivable representing the future cash inflow. It matches revenue to the period in which it was earned, giving a more accurate picture of performance than cash-basis accounting."

Why they ask

It tests whether you understand stating receivables at net realisable value.

Model answer

"It's an estimate of the portion of receivables we don't expect to collect, so the balance sheet shows AR at its realistic value. I usually calculate it with the aging method — applying loss rates to each age bucket based on history (say 1% on 0–30 days, rising to 25–50% on 90+ days) — supplemented by specific identification for known problem accounts."

Model answer

"Through a few core practices: accurate transaction records with supporting documentation, regular assessment of collectability using history and current conditions, an appropriate allowance based on aging analysis, monthly reconciliation between the AR subledger and the general ledger, and correct revenue-recognition timing with a clear audit trail for adjustments."

Model answer

"I follow ASC 606: identify the performance obligations, determine the transaction price, and recognise revenue as each obligation is satisfied. For long-term work I use milestone-based or percentage-of-completion recognition, keep a detailed contract register, and work with project managers to ensure progress is reported accurately and revenue is allocated to the right periods."

Model answer

"Through strong internal controls: segregation of duties across AR, documented approval hierarchies for write-offs and adjustments, supervisor review of journal entries, and monthly certification. I make sure system access is authorised and reviewed, keep thorough process documentation, and support quarterly testing with internal and external auditors."

Model answer

"I've worked with SAP (S/4HANA), Oracle NetSuite and Microsoft Dynamics 365. In SAP I've configured payment terms and dunning procedures and used the dispute-management module; in NetSuite I've customised aging reports and automated revenue-recognition workflows. I'm comfortable learning new systems quickly." (Freshers: name any system from coursework or an internship, and stress you learn tools fast.)

Model answer

"I use pivot tables for dynamic aging analysis, VLOOKUP and INDEX-MATCH for account reconciliations, and Power Query to consolidate data from multiple sources. I build dashboards with conditional formatting that flag exceptions, and macro-enabled templates that standardise reporting and cut preparation time significantly."

Model answer

"Electronic invoicing that cut processing time, automated cash-application matching that removed most manual application, automated dunning sequences that lifted collection rates, and bank-feed integration for real-time payment updates. The aim is always to automate the routine work so the team can focus on exceptions and customer relationships."

Model answer

"Carefully and in stages. I start with a data audit — cleaning duplicates and standardising formats — then create mapping documents between old and new systems, test the migration on a small data set first, run parallel systems during transition, validate key reports post-migration, and keep rollback procedures and full backups throughout."

Model answer

"I verify the order against delivery confirmation and the contract, validate pricing, terms and tax, then generate the invoice in the ERP. Each one gets a quality check for accuracy and completeness, routes through the right approval based on amount, and is delivered via the customer's preferred channel (EDI, email, portal) with delivery confirmation tracked throughout."

Model answer

"Automated matching for exact invoice matches, then manual handling of exceptions using remittance advice and payment references. For complex applications — multiple invoices or partial payments — I follow a clear priority order (exact matches first, then oldest invoices, then largest balances) and hold unidentified receipts in an unapplied-cash account until I can resolve them."

Why they ask

Collections is the heart of AR; they want a method that protects both cash and the relationship.

Model answer

"I segment accounts by risk and payment history, then apply the right intensity. Low-risk accounts get automated reminders from a few days past due; medium-risk get a personal call around 15 days; high-risk get immediate attention. I document every contact, track promises to pay, and escalate to management or legal only when appropriate. The goal is to keep collection rates high without damaging good customers."

Model answer

"I assess their situation honestly — through payment history or financials — then propose a realistic schedule that fits their cash flow while meeting our collection goals. I document the terms clearly, secure guarantees or progress payments where appropriate, and put monitoring in place with a contingency plan if payments slip. A workable plan recovers more than an aggressive one that defaults."

Model answer

"I log every dispute with response times and resolution. I acknowledge receipt within 24 hours, gather the documentation (contract, delivery receipt, correspondence), work with the customer to understand the concern, and provide supporting evidence. If an adjustment is warranted I ensure it's authorised and documented. A structured process resolves most disputes within a few business days."

Model answer (STAR)

"Situation: a large variance between the AR subledger and the general ledger had persisted for months. Task: find and fix it. Action: I mapped every possible source, ran a transaction-by-transaction analysis on high-volume periods, and found credit-memo reversals weren't updating the subledger due to a configuration error. Result: I corrected the technical issue, adjusted the historical entries, and put daily reconciliation and automated variance reports in place to prevent recurrence."

Model answer

"I compare the payment against open invoices, checking for discounts, returns or disputes, then contact the customer for clarification — often they've taken a deduction or applied the payment differently than intended. I document their reasoning, decide whether an adjustment is warranted, and set clear application instructions. Then I look at whether clearer invoicing could prevent it next time."

Model answer (STAR)

"Situation: I had to place a long-term customer on credit hold for repeated late payments. Task: protect the company without losing the relationship. Action: I prepared the full payment history, presented the facts objectively, acknowledged their position, and offered a path back — a payment plan and clear conditions to lift the hold. Result: we recovered the full amount and kept the relationship intact."

Model answer

"With data and collaboration. When sales felt our credit-approval process was costing deals, I brought everyone together, showed the link between credit checks and collection success, and acknowledged their revenue pressure. We agreed a compromise — expedited reviews for strategic accounts and provisional limits for urgent cases — that cut credit losses while keeping sales moving."

Model answer

"I track DSO monthly and segment it by customer, product line and region to find the problem areas, then look at the aging composition to see whether an increase is a sales-timing issue or a collection issue. From there I optimise invoice delivery timing, tighten terms where possible, automate reminders, and focus collection effort on the highest-impact accounts — measuring the effect of each change."

Model answer (STAR)

"Situation: manual invoice approval was adding days to billing and hurting cash flow. Task: speed it up without losing control. Action: I built an automated approval workflow in the ERP that routes by amount, customer type and product while keeping the right controls. Result: approval time fell sharply, most invoices now process automatically with exception-based review, and cash flow improved as billing accelerated."