Accounts Payable Interview Questions: Role-Specific Prep for Invoice Processing, Vendor Reconciliation, and Payment Runs

Accounts payable interviews test a specific operational cycle: receiving invoices, matching them to purchase orders and goods receipts, coding them to the right expense accounts, getting them approved, and paying vendors on the right terms at the right time.

Interviewers care about two things above everything else. First, accuracy. A wrong GL code, a missed three-way match exception, or a duplicate payment has real financial consequences — not just for the company's books but for vendor relationships and audit readiness. Second, discipline. AP is a control function. The processes around it — approval workflows, payment batch schedules, vendor master data governance — exist to prevent fraud and error. Interviewers want to see that you take those controls seriously rather than treating them as friction.

Most accounts payable interview questions fall into six categories:

**Three-way match and invoice exceptions** — Do you understand the match process, and what do you do when an invoice doesn't match the PO or the goods receipt?

**Invoice coding and GL allocation** — Can you assign the right expense accounts and cost centers, and what do you do when coding instructions are ambiguous?

**Vendor statement reconciliation** — When a vendor's statement and your AP ledger disagree, how do you find and resolve the difference?

**Payment runs and terms management** — How do you schedule payment batches to capture early-pay discounts, pay on time, and support cash flow planning?

**Duplicate invoice prevention** — What controls do you use to catch duplicates before they become duplicate payments, and what happens if one slips through?

**Month-end accruals and close support** — How do you handle uninvoiced receipts at period end, and how do you hand off accrual detail to the accounting team?

Before the interview, prepare concrete numbers: how many invoices did you process per week, what ERP did you use, how many vendor accounts did you manage, and what was your role during month-end close? Specific figures make your answers credible in a way that process descriptions alone cannot.

Three-way matching is the foundational control in accounts payable, and virtually every AP interview covers it. The three documents are the purchase order (what was ordered and at what price), the goods receipt note or delivery confirmation (what was actually received), and the vendor invoice (what the vendor is billing). All three must agree within tolerance before an invoice can be approved for payment.

**'Walk me through your three-way match process.'**

This is often the opening accounts payable interview question after introductions, and a vague answer is an immediate red flag to interviewers.

Sample answer: 'When I receive a vendor invoice, I pull the corresponding purchase order — either from the invoice reference or from our vendor record in the ERP. I compare the vendor name, PO number, invoice number, line items, quantities, and unit prices against both the PO and the goods receipt confirmation. If all three documents agree within our tolerance threshold, I approve the invoice for payment and code it to the GL accounts specified on the PO. If there's a discrepancy, I put the invoice on hold. Quantity differences go to the purchasing team to investigate against the receiving record. Price discrepancies go to the vendor with a copy of the agreed PO terms. I document the hold reason in the system and follow up within 48 hours.'

**'What do you do when an invoice arrives without a purchase order number?'**

Sample answer: 'It depends on the vendor and the expense type. For a recurring service vendor with a standing agreement, I verify the charge against the contract and route it through our non-PO approval workflow — typically a written approval from the relevant department manager above a certain dollar threshold. For a new or unfamiliar vendor, I hold the invoice and contact the department head who supposedly requested the service, because a non-PO invoice from an unrecognized vendor is also a fraud risk I take seriously. I never approve a non-PO invoice on my own authority above our stated limit.'

**'How do you handle invoice coding when the expense description is vague?'**

GL coding is where many AP candidates give weak answers. Interviewers want to see judgment, not just rule-following.

Sample answer: 'My first step is to check whether the vendor has an established coding pattern in our system — most recurring vendors have a default GL account and cost center already set up. If it's a new vendor or an unusual expense type, I compare the invoice description against the chart of accounts and select the expense category that most closely fits the nature of the purchase. For any non-standard coding above $500, I send a brief note to the relevant department manager for confirmation before posting. It takes two minutes and prevents month-end corrections. I keep a log of coding decisions for new vendors so my manager can review them during account reconciliation and set permanent defaults going forward.'

Vendor statement reconciliation separates AP specialists who understand their ledger from those who only process transactions. Most vendors send monthly statements; reconciling those statements to your AP subledger is a core skill that comes up in almost every accounts payable interview for roles above entry level.

**'Walk me through how you reconcile a vendor statement.'**

Sample answer: 'I start by pulling our AP subledger for that vendor — all open invoices, credit memos, and payments within the statement period. Then I compare the vendor's closing balance to our open AP balance for that vendor. If they match, I document it and move on. If they don't, I work through the differences line by line. The most common gaps are: invoices on the vendor's statement that we haven't received yet, payments we've sent that haven't cleared their records yet, credit memos that haven't been applied on one side, and invoices we've put on hold pending a dispute. I note each difference with an explanation and resolve anything I can — applying unapplied credits, chasing missing invoices from the vendor. Differences I can't close within 48 hours get escalated to my manager with a summary of what I've already checked.'

**'How do you decide which invoices to pay in a payment run?'**

This tests whether you understand cash management, not just AP processing mechanics.

Sample answer: 'I run payments on our standard schedule — we had weekly ACH batches and biweekly check runs. For each batch, I prioritize by payment terms and due date. Invoices with early-pay discount terms (such as 2/10 net 30) come first — I always check whether the discount savings outweigh the cash flow cost before capturing them, but for most vendors the math favors paying early. Then I sort remaining invoices by due date: anything falling due before the next payment cycle gets included in that batch, anything not yet due stays off the run. I also maintain a list of critical vendors — utilities, key suppliers, anyone whose service interruption would affect operations — and confirm those are processed even when amounts are still being verified. Before releasing any batch, I review it for holds, duplicate flags, and amounts that look out of pattern for that vendor.'

**'How do you handle a situation where a vendor claims they never received a payment?'**

Sample answer: 'I check our records first: payment date, method, amount, and the check number or ACH trace number. If a check has cleared our bank, I pull the cleared copy and send it to the vendor with the remittance detail — that resolves most claims immediately. If the payment went by ACH, I provide the trace number so their bank can locate the deposit. If the payment genuinely hasn't gone out — if it's sitting unprocessed on our side — I investigate why: was it stuck in an approval queue, or did our bank reject it because of an incorrect routing number on file? I fix the root cause and process the payment. I update the vendor only once I have a complete answer, not while I'm still investigating — giving a vendor three partial updates creates more confusion than the original missed payment.'

Duplicate payments are one of the most common and expensive AP errors, and interviewers want to see that you take prevention seriously rather than relying on the ERP to catch everything.

**'What controls do you use to prevent duplicate invoice payments?'**

This is one of the most important accounts payable interview questions for any AP role, and a superficial answer will cost you the offer.

Sample answer: 'The primary control is system-level: our ERP flagged any invoice with the same vendor number, invoice number, and amount that already existed. Before posting a new invoice, I confirmed those match fields were unique. But I don't rely on the system alone. Vendors sometimes re-submit invoices with slightly modified invoice numbers — adding a suffix or transposing a digit — so the exact-match filter passes while the underlying invoice is the same. I watch for invoices with the same vendor, same amount, and same invoice date even when the invoice number differs slightly. I also pay attention to invoices that arrive through different channels on the same day — the same PDF arriving by email and by fax is a common duplicate pattern. For high-volume vendors, I run a periodic spot check: pulling 60 days of invoices and scanning for matching amounts and dates regardless of invoice number.'

**'What do you do if you discover a duplicate payment after it has already been made?'**

Sample answer: 'I document the duplicate immediately — original invoice number, duplicate invoice number, payment dates, amounts, and payment method. I notify my manager the same day. Then I contact the vendor and request a credit memo for the duplicate amount, or ask them to apply it as a credit against their next open invoice. I track that credit until it appears as an offset in our AP subledger — I do not close the issue until the credit is in the system and confirmed. If a vendor does not respond within a week, I escalate to our controller, because a duplicate payment is money we are owed and it needs to be pursued formally. I also document the root cause: did the vendor submit twice? Did the invoice arrive by two channels? I recommend a process change to prevent the same situation, not just accept it as a one-time error.'

**'How do you maintain vendor master data to support duplicate prevention?'**

Sample answer: 'Vendor master integrity is foundational. If the same vendor has two vendor records in the system, the ERP's duplicate controls will fail because it compares vendor numbers, not vendor names. My onboarding process for new vendors requires a completed W-9 before the record is created, direct confirmation of banking details through a call-back process — I never update bank routing information based solely on an email — and manager review of any banking changes before they go live. I also do a periodic cleanup of the vendor master: merging duplicate records, inactivating vendors with no activity in 24 months, and confirming that vendor names match their tax ID on file. A clean vendor master is one of the most effective fraud prevention controls available in AP.'

Month-end is when AP teams feel the most pressure and when errors have the most visibility. Accounts payable interview questions about close procedures are common for any role with reporting responsibility, and weak answers here are disqualifying for senior AP positions.

**'How do you handle uninvoiced receipts at month-end?'**

This is a core question for AP roles that support the accounting close cycle.

Sample answer: 'I pull a report of goods that have been received in the warehouse — confirmed on a goods receipt note — but for which no vendor invoice has posted yet. For each open goods receipt, I calculate the accrual: the PO unit price multiplied by the received quantity. I prepare a journal entry debiting the relevant expense accounts and crediting an accrued liabilities account, which records the expense in the period it was incurred even though the invoice hasn't arrived. I set those accruals to reverse on the first business day of the following period — when the actual invoice posts, it replaces the accrual without double-counting. Before the close deadline, I provide the accounting team a summary organized by department and dollar amount so they can reconcile against their own estimates and flag anything unexpected before the books close.'

**'How do you ensure clean AP cutoff at period end?'**

Sample answer: 'Cutoff means invoices dated on or before the last day of the period are posted to that period, and invoices dated in the new period are held out. I run through a close checklist: I stop posting new invoices after the cutoff time on the final day, clear any backlog from the prior few days, and hold invoices dated in the new month even if they are sitting in the approval queue. I also coordinate with the receiving team to confirm which deliveries came in before period end — sometimes the invoice from a vendor arrives a week later, but if the goods were received before month-end, those need to be accrued in the current period. I document the cutoff log so my manager can review it and so anyone covering for me follows the same consistent process month to month.'

**'What happens if a month-end accrual you posted turns out to be materially wrong?'**

Sample answer: 'The first thing is to determine when the error came to light. If I catch it before the books close, I correct the accrual entry directly and flag it to my manager immediately. If it's discovered after close, the question of whether to restate the prior period or record an adjustment in the current period is an accounting judgment call that goes to the controller — not something I make unilaterally. My job at that point is to document exactly what went wrong: was the PO price different from the actual invoice price, or did the goods receipt quantity differ from what was invoiced? I also identify what data I would need to make a better estimate next time. Accruals are estimates by nature, but a material miss usually signals a process gap worth fixing at the source.'

Most accounts payable interviews will include questions about your ERP experience and whether you have improved processes in previous roles. These questions are a genuine opportunity to stand out, because most candidates can describe tasks but few can describe making the work better.

**'What AP or ERP systems have you used, and how do you pick up a new system?'**

Sample answer: 'I have worked in SAP, Oracle NetSuite, and Microsoft Dynamics. When I transitioned from SAP to NetSuite, I went through the basic certification training the company provided, then spent my first two weeks processing test transactions alongside my supervisor before handling live vendor invoices. The biggest adjustments were the vendor master structure and the way NetSuite handles three-way match exceptions — both systems have different interfaces for the same underlying logic. I built a personal quick-reference guide that mapped my SAP workflow to the equivalent NetSuite steps, which helped me reach full speed faster than just reading documentation. In my experience, the underlying AP concepts transfer across any system; the learning curve is always the interface, not the process.'

**'Describe a specific improvement you made to an accounts payable process.'**

Sample answer: 'At my previous company, we were processing around 280 invoices per week and losing significant time re-keying data from vendor PDF invoices. Our ERP already had an OCR capture module that we were not using. I proposed a pilot: six weeks using OCR for our top 20 vendors by volume, with a manual comparison of error rate and processing time against our existing baseline. The results were clear — OCR processing was measurably faster and had a lower data-entry error rate once we corrected the vendor master records it depended on. We expanded it to all vendors that submitted invoices electronically. OCR didn't eliminate manual review, but it shifted my time from keying numbers to reviewing exceptions — which is where AP judgment actually adds value.'

**'How do you prioritize early-pay discounts versus cash flow when managing payment terms?'**

Sample answer: 'I evaluate each discount offer on its annualized return. A 2/10 net 30 term means we save 2% by paying 20 days early — annualized, that's roughly 36% return on the cash used. For any vendor offering terms like that, I pay on day 10 unless the company is in a cash constraint period and the controller has directed otherwise. For smaller discounts — 0.5% for 15 days early — I check with my manager because the cash flow trade-off may not be worth it depending on our current position. I track discount opportunities in our payment run review so nothing expires unnoticed, and I report on captured versus missed discounts quarterly.'

Reading strong sample answers for accounts payable interview questions is a useful foundation. The real preparation happens when you say them out loud.

AP interview answers require you to walk through multi-step processes clearly and quickly — the three-way match, the payment run prioritization, the vendor reconciliation workflow. That kind of fluency does not come from reading. It comes from rehearsing with your actual voice until the sequence feels automatic rather than recalled under pressure.

The sections that trip most AP candidates are the exception-handling questions: what do you do when the match fails, what do you do when a duplicate slips through, how do you support a restatement conversation. These require you to explain a judgment process calmly while an interviewer watches for hesitation. That composure is built through practice, not through reading.

SayNow AI's job interview scenario lets you practice AP 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 clarity and confidence that reading alone cannot produce. Work through the process questions first — three-way match, payment runs, vendor reconciliation — until they flow without hesitation. Then move to the behavioral questions about errors and exceptions, which are where most AP candidates leave points on the table.