Accounts Receivable Interview Questions: Role-Specific Prep for Collections, Cash Application, and Aging Reports

Accounts receivable interviews are not general accounting interviews. They focus on a specific operational cycle: issuing invoices, tracking open balances, collecting payment, applying cash, and resolving exceptions. Interviewers in this role care less about GAAP theory or journal entry mechanics and more about whether you can keep the AR ledger clean while maintaining functional relationships with customers and the sales team.

Most AR interview questions fall into five categories:

**Collections process** — Can you follow up on overdue invoices systematically and professionally? Can you escalate when necessary without burning a customer relationship?

**Cash application** — Do you understand how to match incoming payments to open invoices, and what to do when a payment doesn't match?

**Aging report analysis** — Can you read an AR aging report, prioritize your workbook, and explain DSO trends to a manager?

**Dispute and deduction handling** — When a customer disputes an invoice amount or takes an unauthorized deduction, what is your process?

**Credit memo and adjustment workflow** — Do you understand when a credit memo is appropriate and how it affects the AR balance?

Before your interview, inventory your own experience against each of these areas. Numbers matter: how many accounts did you manage, what was the average open balance, what was DSO when you arrived versus when you left? Concrete figures tell interviewers far more than descriptions of process.

Collections questions are the centerpiece of most accounts receivable interviews. Interviewers are evaluating two things simultaneously: whether you have a consistent, systematic process, and whether you can be persistent without being adversarial.

**'Walk me through your process for following up on an overdue invoice.'**

This is the most common accounts receivable interview question, and a vague answer kills your chances immediately. Describe a specific escalation ladder, not a general intention to follow up.

Sample answer: 'My process had three defined stages. At 30 days past due, I sent a written reminder — email with the original invoice attached and a clear remittance address. If no response by day 45, I called directly. I always referenced the invoice number, confirmed they had received it, and asked for a specific payment commitment date rather than a general "we'll take care of it." I logged that date in the system. If the commitment date passed without payment, I escalated: I sent a formal notice and looped in our credit manager, who could put an account on hold pending sales team review. I never threatened hold status directly with the customer — that's a credit decision, not a collections conversation.'

**'How do you handle a customer who always pays late but never responds to follow-up?'**

Sample answer: 'I would document the pattern first — three or four cycles of late payment with non-response creates a clear record. Then I would flag the account to the credit manager and the account's sales rep. Sales often has context that collections doesn't: maybe the customer is going through a restructuring, or maybe their AP contact changed. Once I have that context, I adjust the approach — sometimes a call from the sales rep to their relationship contact moves a payment faster than anything I can do directly. If the pattern continues with no business justification, the credit manager makes a hold decision. I support that process with documentation, not with pressure tactics.'

**'Tell me about a time you collected a significantly overdue balance.'**

This is a behavioral accounts receivable interview question. Answer with a specific story: the account, the age of the balance, what you tried, and the outcome.

Sample answer: 'At my last job, I inherited an account that was 120 days past due on $28,000 — the previous AR rep had stopped following up because the customer kept promising payment and not delivering. I started by getting the account's sales rep on a joint call with the customer's AP director. We discovered their AP system had flagged our invoices as disputed because of a PO number mismatch from eight months earlier — a paperwork issue, not a genuine dispute. I worked with our billing team to reissue the corrected invoices, then tracked the customer's AP cycle and called two days before each check run. We collected the full balance over six weeks. The root cause was a documentation error, not a payment problem — but nobody had dug in far enough to find it.'

Cash application is where many AR candidates struggle in interviews because it requires specific process knowledge, not just general familiarity. Interviewers want to know what you do when a payment arrives and does not match an open invoice cleanly.

**'Walk me through how you apply an incoming payment.'**

Sample answer: 'When a payment comes in — whether by check, ACH, or wire — I first pull the remittance advice. If the customer sends a remittance, matching is straightforward: I apply the payment to the invoices listed and clear those items from the aging. If no remittance arrives, I reference the payment amount against open invoices. For an exact match I apply immediately. For a partial payment I check whether the customer has communicated about a dispute or deduction — if they have, I apply the undisputed amount and log the deduction for follow-up. If there is no explanation, I put the unmatched portion in a suspense account and contact the customer the same day for remittance detail. I never leave an unmatched payment sitting in suspense for more than 48 hours.'

**'What do you do when a customer takes a deduction you don't recognize?'**

This is one of the most important AR questions for anyone handling complex B2B accounts.

Sample answer: 'First I check whether the deduction corresponds to an approved credit memo, a pricing adjustment, or a freight claim in our system. If I find a match, I close it. If I don't, I look at the customer's remittance note — customers will often write "less shortage claim" or "promo deduction 2145" on the check stub. If it's a valid-sounding code but nothing is in our system, I contact the customer for backup documentation. If they can't support it, I re-invoice for the deduction amount and note it in the account. Large or recurring unsubstantiated deductions go to the sales team and credit manager — deduction management is a shared responsibility between AR and commercial.'

**'How do you handle short payments where the customer claims a discount they were not entitled to?'**

Sample answer: 'I verify the payment terms on the original invoice and purchase order. If the discount period expired and the customer paid late but deducted the early-pay discount anyway, I contact their AP team, explain the terms, and re-invoice for the difference. I keep the tone informational — "based on the invoice date and your payment date, the discount window was July 3rd, and your payment posted on July 9th" — rather than accusatory. If the customer disputes the terms themselves, that becomes a conversation between our sales rep and their procurement team, not an AR call.'

Billing disputes are an unavoidable part of accounts receivable work. Interviewers want to see a structured process — not someone who either rolls over on every dispute or argues every claim to the mat.

**'What is your process when a customer disputes an invoice?'**

Sample answer: 'The first thing I do is get the specifics in writing — what invoice, what amount, and what the customer believes the correct amount should be. Then I review our records: does the invoice match the contract or purchase order? Was the goods receipt confirmed? Is there a pricing discrepancy? If the dispute is valid — we billed incorrectly — I issue a credit memo and send a corrected invoice the same day. If the dispute is not valid — the customer received what they ordered at the agreed price — I pull the documentation and respond with specifics: the signed delivery confirmation, the agreed pricing schedule, or the PO reference. I give the customer three business days to review and respond before following up. I track all open disputes in a separate log so nothing ages without action.'

**'How do you handle a customer who disputes frequently and often incorrectly?'**

Sample answer: 'Frequent unfounded disputes are a signal, not just an annoyance. I would flag the pattern to my manager and the account's sales rep. Sometimes it's a trained behavior — the customer has learned that disputing invoices buys them 30-60 extra days. Sometimes it's a process issue on their side that's generating incorrect purchase orders. Once I understand the root cause, I can respond appropriately: tighter documentation on our end, more specific remittance requirements, or a conversation with their management depending on how strategic the account is.'

**'Tell me about a dispute you resolved that required coordinating with other departments.'**

Sample answer: 'We had a retail customer disputing $14,000 in invoices across about six SKUs, claiming they had received damaged goods. The dispute sat unresolved for 90 days before I inherited it. I got with our logistics team and pulled the shipping records — all items had been confirmed received without a freight claim noted at delivery. I also contacted their receiving department directly (with our sales rep's intro) and found out the damage claims had been filed internally by their merchandising team, not their AP team, and the two departments had not connected. I got the freight claims submitted properly, we processed a partial credit for the genuinely damaged quantity, and the customer paid the remainder within two weeks. The account had been a non-payer for three months over an internal miscommunication on their end.'

Accounts receivable interview questions about disputes test your ability to be assertive without being confrontational, and to distinguish between valid customer issues and delay tactics.

If you're applying for an accounts receivable role above entry level, expect analytical questions about aging reports and Days Sales Outstanding. These come up in almost every AR interview for roles that own reporting responsibilities.

**'How do you use an AR aging report in your day-to-day work?'**

Sample answer: 'The aging report is my primary workbook. Every Monday I pull it sorted by days past due, and I work the buckets from oldest to newest. Anything 90+ days gets priority contact that day — those balances are at risk of write-off and require either a payment plan or a credit decision. The 60-90 day bucket gets a same-day call or written notice depending on the account history. For 30-60 days, I send a written reminder with the invoice attached. Current and 0-30 days I monitor weekly rather than actively working unless there's a pattern I've flagged. I reconcile the aging total to the general ledger at month end to confirm they match before close.'

**'How would you explain DSO to a non-finance manager?'**

Sample answer: 'Days Sales Outstanding measures how long on average it takes us to collect payment after a sale. If our DSO is 45, it means we're waiting an average of 45 days from invoice date to collected cash. Lower DSO means we're collecting faster, which is better for cash flow. If DSO is rising, it usually means either customers are paying later, we're giving longer terms, or our collections process is less effective. I'd frame it as a cash flow efficiency number — how quickly is our revenue turning into money we can actually use?'

**'What would you do if you noticed DSO increasing over three consecutive months?'**

Sample answer: 'I would start by segmenting the increase. Is it one large account pulling the average up, or is it broad-based across many accounts? If it's concentrated, that's an account management issue — I'd focus there. If it's broad, I'd look at whether our invoice-to-issue timing has changed (are invoices going out later?), whether our terms have shifted, or whether there's a collections process issue. I'd also look at whether new customer segments with different payment behaviors have grown as a share of our mix. I'd bring the analysis to my manager with a recommendation, not just the observation that DSO went up.'

Being able to talk fluently about aging reports and DSO in your accounts receivable interview tells interviewers you understand the function's business purpose, not just its day-to-day mechanics.

Credit memos and balance adjustments are a regular part of accounts receivable work, and interviewers want to see that you understand when they're appropriate, how they affect the ledger, and what controls should govern them.

**'When is a credit memo appropriate, and what is your process for issuing one?'**

Sample answer: 'A credit memo is appropriate when we've billed a customer for something they should not owe — a return, a pricing error, a duplicate invoice, or an approved rebate. It reduces the open balance on their account. My process: I verify that an authorized approval exists before issuing. For small amounts (we used $500 as a threshold), I could issue within my authority with documentation. Above that threshold, my supervisor approved. I'd pull the original invoice, note the reason in our system with the approval reference, issue the credit memo, and send a copy to the customer. I'd also make sure the credit memo was applied or available for offset on their next invoice — leaving an unapplied credit memo sitting on the account creates reconciliation confusion.'

**'What is the difference between a credit memo and a write-off, and when would you recommend each?'**

Sample answer: 'A credit memo is a billing correction — it acknowledges we owe the customer something, usually because of an error on our end or an agreed adjustment. A write-off is a business decision to stop pursuing a balance that is legitimately owed but uncollectible — typically after all reasonable collection efforts have been exhausted or the customer has closed. Write-offs hit the income statement as bad debt expense; credit memos reduce revenue. I would recommend a credit memo when the dispute is valid or when a pricing error is confirmed. I would escalate a write-off recommendation to my manager and credit team — it's not a unilateral AR decision, and it requires documentation of what was tried before concluding the balance is uncollectible.'

**'How do you handle a situation where a customer's account has a credit balance?'**

Sample answer: 'A credit balance on a customer account means we owe them money. I check the source — is it an overpayment, an unapplied credit memo, or a refund that should have gone out? If it's an overpayment, I notify the customer and offer to either refund or apply it to their next invoice. I document the customer's choice and process accordingly. I review credit balances as part of my monthly aging review — unapplied credits sitting longer than 60 days usually indicate a reconciliation gap or a customer who doesn't know the credit exists. Neither is acceptable in a clean AR ledger.'

Reading strong sample answers for AR interview questions is a useful starting point. The real preparation happens when you say them out loud.

AR interview answers require you to deliver specific details — invoice amounts, aging buckets, DSO figures, software names — fluently and without hesitating. That kind of fluency does not come from reading. It comes from rehearsing with your actual voice until the answers feel less like recall and more like professional conversation.

The sections that trip candidates up most in accounts receivable interviews are the process walkthroughs (collections escalation, cash application) and the analytical questions (DSO trends, aging report interpretation). These require you to sequence multiple steps clearly while staying conversational — that's harder than it sounds under interview pressure.

SayNow AI's job interview scenario lets you practice common AR interview questions in a spoken format with dynamic follow-up responses. You speak, the AI responds in character as an interviewer, and you build the composure and clarity that reading alone cannot produce. Work through the questions that feel shakiest first — collections process and dispute resolution are where most AR candidates leave confidence on the table.