Accounts Payable Interview Questions and Scorecard
Six question sets written for the employer side: core process, matching and exceptions, vendor fraud, month-end close, behavioral, and a scorecard with a twenty-minute match exercise. Every question comes with why it is worth asking and what a good answer sounds like. Download as DOCX.
The first time I sat in on an accounts payable interview at a small company, the candidate answered every question well and got the job. Four months later the business had paid the same equipment invoice twice, because the vendor had sent it once by mail and once by email under a slightly different reference. Nobody had asked her how she catches duplicates. She was not careless. She had simply never been asked the question, so nobody knew she had no method.
That is the pattern with this role. Accounts payable interviews go wrong not because the questions are hard but because the ones that matter never get asked. The person at this desk decides what your business pays, when, and to which bank account, and most interviews for it never test a single exception.
At FirstHR we build for small businesses that hire without an HR department, where the person running this interview has usually never matched an invoice to a receiving record. This page is written from the employer side: six question sets, and for every question, the reason it is worth asking and what a good answer actually sounds like. The accounts payable job description templates cover the posting side of the same hire.
TL;DR
Interview accounts payable on five things: the invoice-to-payment cycle, matching and exceptions, vendor and payment fraud controls, month-end close, and accuracy under volume. The two questions that decide most hires are what they do when an invoice and a receiving record disagree, and what they do when a vendor emails that their bank details changed. Score on a rubric, and run a twenty-minute match exercise with a planted duplicate.
What an AP Interview Has to Prove
An accounts payable interview has to prove five things: that the candidate has run the full invoice-to-payment cycle, that they investigate exceptions rather than forcing them away, that they will not move money on an unverified request, that they can close the period, and that they stay accurate when the volume spikes. Everything else is secondary.
The reason to be explicit about this is that payables is easy to interview badly. The work looks like data entry from the outside, so the conversation drifts toward speed and software. Speed is the cheapest thing you are buying. The expensive thing is judgment at the ten percent of invoices that do not match, because that is where a business pays for goods it never received, pays the same bill twice, or wires money to a criminal.
What to prove
The question that proves it
What a weak answer looks like
Owns the full cycle
Walk me through an invoice from arrival to payment
Jumps from invoice to payment with nothing between
Investigates exceptions
Invoice says $1,240, the PO says $1,180
Adjusts the purchase order so it matches
Pays what was received
Invoice says 100 units, receiving logged 92
Pays the invoice to keep the vendor happy
Catches duplicates
How do you stop an invoice being paid twice?
The software handles it, with no method described
Verifies before paying
A vendor emails that their bank details changed
Confirms by replying to the same email
Can close the period
What does closing payables at month end involve?
I finish entering everything, with no cutoff or accrual
Notice that four of those six are scenarios rather than knowledge questions. A candidate can memorize the definition of a three-way match in ten minutes. Nobody can fake a considered answer to what they do when the three documents disagree, which is why the sets below lead with situations and keep the definitions short.
The Six Question Sets
The six sets split the role into the areas that actually predict performance, so you can weight them to your opening rather than reading a single undifferentiated list of forty questions. Ask the core set of everyone, then add the sets that match the scope you are hiring for.
Core AP Process
Ask every candidate
Invoice to payment, the three-way match, coding, approval routing, payment terms, systems, and real invoice volume. Start here and only continue if it holds up.
Matching and Exceptions
Where the value is
Price variances, short receipts, duplicates, invoices with no purchase order, tolerances, and freight and tax lines. Clean invoices process themselves; exceptions are the job.
Vendor Master and Fraud
The set most lists skip
Bank-change requests, separation of duties, W-9 collection before first payment, vendor list hygiene, and pressure from a senior manager to skip approval.
Close and Reconciliation
If they own the period
Cutoff and accruals, vendor statement reconciliation, the aging report, tying the sub-ledger to the general ledger, credit memos, and 1099 preparation.
Behavioral and Vendors
Accuracy and temperament
Reporting your own mistake, handling a vendor who is 45 days past due, staying accurate at month end, and saying not yet to someone senior.
Scorecard and Exercise
Decide on evidence
A six-area 1-to-5 rubric, a red-flag checklist, and a twenty-minute live match exercise with four invoices, one of which is a planted duplicate.
Which Sets to Use for Your Opening
Hiring a processor who will work under a bookkeeper or an outside accountant: core, exceptions, behavioral, and the scorecard. Hiring someone who will own payables alone: all six, with the fraud and close sets weighted heavily. Replacing a departing AP person: add the close set regardless of level, because you will find out during the interview what the last person was quietly not doing.
These sets sit alongside our bookkeeper interview questions and accounting clerk interview questions, which cover broader finance hires. Use this page when the opening is specifically payables. FirstHR is an onboarding and HR platform rather than accounting software, so it handles the hire and the paperwork rather than the ledger. Applicant tracking is coming soon to FirstHR.
40+ Questions and a Scorecard to Download
Download all six sets as a single Word document, or copy the ones you need. Each set follows the same structure: when to use it, the questions with the reason to ask and the good answer, what to listen for, and space for notes. The scorecard adds a rating grid, a red-flag checklist, and the match exercise.
Download All 6 Accounts Payable Question Sets
Core process, matching and exceptions, vendor fraud, month-end close, behavioral, and a scorecard with a match exercise. All in one DOCX.
Set 1: Core Accounts Payable Process Questions
Ask this set of every candidate. Invoice to payment, the three-way match, coding, approval routing, payment terms, systems, and real invoice volume, each with the reason to ask it and what a good answer sounds like.
Core Accounts Payable Process Questions
CORE ACCOUNTS PAYABLE PROCESS QUESTIONS
Candidate: __
Business: __
Interviewer: __
Date: __
WHEN TO USE THIS SET
Ask this set of every accounts payable candidate, no matter the title. It tests
whether the person has actually run an invoice from arrival to payment, or has
only watched someone else do it. Every question below carries the reason it is
worth asking and what a good answer sounds like, so an owner who has never
processed a payables run can still grade the response.
QUESTIONS
1. Walk me through what happens to an invoice from the moment it arrives until
the vendor is paid.
Why ask: this is the whole job in one question, and it separates people who
own the cycle from people who only did data entry inside it.
Good answer: receive and log the invoice, verify it against the purchase
order and the receiving record, code it to the right account and cost center,
route it for approval, enter it, schedule payment by terms, then file the
backup. Weak answers jump straight from invoice to payment.
2. What is a three-way match, and what do you do when the three documents
disagree?
Why ask: it is the single control that stops you paying for goods you never
received, and every real AP person can define it cold.
Good answer: matches the purchase order, the receiving report, and the
invoice on quantity and price. On a mismatch they hold the invoice and go
back to purchasing or receiving to resolve it, rather than paying it anyway.
3. How do you decide the date an invoice actually gets paid?
Why ask: payment timing is cash flow, and you want someone who thinks in
terms, not in whoever calls loudest.
Good answer: pays to terms, watches early-payment discounts such as 2/10 net
30, groups payments into a scheduled run rather than paying ad hoc, and
escalates when cash is tight instead of silently going late.
4. How do you code an invoice when it is not obvious which account it belongs
to?
Why ask: miscoding is invisible until the books are wrong at year end.
Good answer: checks how similar invoices were coded before, looks at the
chart of accounts, and asks the person who requested the purchase rather than
guessing. Says plainly that they ask when unsure.
5. What is the difference between a PO invoice and a non-PO invoice, and how do
you handle each?
Why ask: most small businesses run a mix, and the non-PO path is where
unapproved spend hides.
Good answer: PO invoices go through the match. Non-PO invoices need a named
approver and a coding decision before entry, with a rule for who can approve
what amount.
6. What accounting or payables systems have you used, and what did you do in
them?
Why ask: the tool is where the work happens, and vague software answers
usually mean thin experience.
Good answer: names the systems and the actual tasks: entering vouchers,
running payment batches, pulling an aging report, uploading vendor files.
7. How many invoices did you handle in a typical week, and how did you keep up?
Why ask: it sizes their real volume against yours, and tells you whether they
will be bored or buried.
Good answer: gives a number and a method: a daily processing window, a queue,
batching by vendor or by due date.
WHAT TO LISTEN FOR
•A specific, ordered process, not a list of buzzwords
•Comfort saying "I would check" or "I would ask" instead of guessing
•Numbers: invoice volume, payment run frequency, terms
•Ownership of the full cycle rather than one step of it
NOTES
__
__
Set 2: Invoice Matching and Exception Questions
Price variances, short receipts, duplicates, invoices with no purchase order, tolerance thresholds, and the freight and tax lines that break a clean match at almost every small business.
Invoice Matching and Exception Questions
INVOICE MATCHING AND EXCEPTION QUESTIONS
Candidate: __
Interviewer: __
Date: __
WHEN TO USE THIS SET
Clean invoices process themselves. The value of an accounts payable hire shows
up entirely in the exceptions: the price that does not match, the quantity that
is short, the invoice with no purchase order, the second copy of a bill you
already paid. Use this set once the core process answers have held up.
QUESTIONS
1. The invoice says $1,240 and the purchase order says $1,180. What do you do?
Why ask: it is the most common exception in payables and the answer reveals
whether they investigate or absorb.
Good answer: holds the invoice, finds out whether the price changed with
approval, whether freight or tax was added, or whether the vendor billed
wrong. Contacts purchasing or the vendor, documents the outcome, and only
then pays or requests a corrected invoice. Never quietly adjusts the PO to
match.
2. The invoice quantity is 100 but the receiving record shows 92. Which one do
you pay?
Why ask: paying the invoice instead of the receipt is how a business pays for
goods that never arrived.
Good answer: pays for what was received, holds the difference, and works with
receiving and the vendor to confirm a short shipment, a backorder, or a
damaged return.
3. How do you catch a duplicate invoice before it gets paid twice?
Why ask: duplicate payments are a real and recoverable loss, and most people
have a system for this or have never thought about it.
Good answer: enters the vendor invoice number exactly so the system flags a
repeat, watches for the same amount and date under a slightly different
number, and checks before paying anything that arrives by email after already
arriving by mail.
4. A vendor sends an invoice with no purchase order and nobody remembers
ordering it. Walk me through what you do.
Why ask: this is where a weak AP hire either pays it to make it go away or
sits on it silently for two months.
Good answer: does not pay it, traces it to a requester, asks the vendor for
proof of the order or delivery, and escalates if no one owns it. Communicates
with the vendor while it is being resolved.
5. What tolerance would you set before an invoice needs manual review, and why?
Why ask: it tests whether they can think about control design, not just
follow a rule someone else wrote.
Good answer: proposes a small dollar or percentage tolerance so pennies of
freight rounding do not stop a payment, while anything material gets human
eyes. Ties the threshold to the size of the business.
6. How do you handle sales or use tax and freight lines that the purchase order
did not include?
Why ask: these are the two lines that break a clean match at almost every
small business.
Good answer: knows these are usually expected variances, codes them
correctly, and knows when use tax has to be accrued rather than paid to the
vendor.
7. Tell me about the worst invoice mess you inherited and how you cleared it.
Why ask: past behavior beats hypotheticals, and payables people always have
one of these stories.
Good answer: a specific situation, a specific method (sorting by vendor,
pulling statements, working oldest first), and a specific result.
WHAT TO LISTEN FOR
•Holds and investigates rather than paying to end the argument
•Never forces a match by editing the purchase order
•Pays what was received, not what was billed
•Documents the resolution so the next person can follow it
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Bank-change requests, separation of duties, what gets collected before a new vendor is paid, vendor list hygiene, and what happens when a senior manager pushes to skip an approval.
Vendor Master and Payment Fraud Questions
VENDOR MASTER AND PAYMENT FRAUD QUESTIONS
Candidate: __
Interviewer: __
Date: __
WHY THIS SET MATTERS MOST
Accounts payable is the desk criminals aim at. A convincing email that changes a
vendor bank account, or an urgent invoice that looks routine, moves money out of
a small business faster than any other attack. This set tests whether the
candidate treats verification as part of the job or as an obstacle to it. It is
the set most interview lists skip entirely.
QUESTIONS
1. A vendor emails to say their bank details have changed and asks you to update
them before the next payment. What do you do?
Why ask: this is the single highest-value question on the page, and the wrong
answer costs real money.
Good answer: does not use any contact detail in that email. Calls the vendor
back on a phone number already on file, speaks to a known contact, requires
written confirmation on the vendor letterhead, and has a second person
approve the change. Treats urgency in the request as a reason to slow down.
2. Who at your last employer could add a new vendor, and who could release a
payment?
Why ask: it tests whether they understand separation of duties without you
having to use the phrase.
Good answer: different people, or at minimum an owner approval on new vendors
and on payments over a threshold. A candidate who says they did all of it
alone should at least say it made them uncomfortable.
3. What do you collect before a new vendor is paid the first time?
Why ask: it catches both fraud control and tax compliance in one answer.
Good answer: a completed Form W-9 with the legal name and taxpayer
identification number, a verified address, banking details confirmed by
phone, and a note of who requested the vendor. Knows this feeds 1099
reporting at year end.
4. How do you keep the vendor list from filling up with duplicates and dead
accounts?
Why ask: a messy vendor master is where duplicate payments and ghost vendors
live.
Good answer: searches before creating, uses a consistent naming standard, and
deactivates vendors that have gone unused rather than leaving them open.
5. Your manager tells you to push a payment through today, skipping the usual
approval. How do you handle it?
Why ask: it tests whether the control survives pressure from someone senior.
Good answer: asks for the approval in writing, offers to process it the
moment it arrives, and escalates to the owner if pushed. Does not just comply
quietly, and does not turn it into a confrontation.
6. Have you ever spotted something that turned out to be fraudulent or wrong?
What happened?
Why ask: people who have caught something remember it in detail.
Good answer: a concrete story with what tipped them off and who they told. If
they have never caught anything, listen for whether they can describe what
they would look for.
7. How comfortable are you with the owner reviewing the payment register every
week?
Why ask: openness to oversight is a character signal in a money role.
Good answer: welcomes it and treats it as normal. Discomfort, or an argument
that it wastes the owner’s time, is a meaningful flag.
WHAT TO LISTEN FOR
•Verification through a channel the requester did not supply
•Urgency treated as a warning sign, not a reason to hurry
•Comfort with a second approver and with owner review
•Knows the W-9 and 1099 side of vendor setup
NOTES
__
Set 4: Month-End Close, Aging, and Reconciliation Questions
Cutoff and accruals, vendor statement reconciliation, reading the aging report, tying the sub-ledger to the general ledger, credit memos, and preparing for 1099 season through the year.
Month-End Close, Aging, and Reconciliation Questions
MONTH-END CLOSE, AGING, AND RECONCILIATION QUESTIONS
Candidate: __
Interviewer: __
Date: __
WHEN TO USE THIS SET
Use this set when the accounts payable hire will own more than data entry:
closing the payables sub-ledger each month, reconciling vendor statements, and
producing an aging report the owner can act on. If your candidate will be the
only finance person, every question here is required rather than optional.
QUESTIONS
1. What does closing accounts payable at month end involve for you?
Why ask: it separates a processor from someone who can close a period.
Good answer: cuts off invoice entry on a set date, accrues for goods received
but not yet invoiced, ties the sub-ledger to the general ledger control
account, reviews the aging, and hands a clean number to whoever prepares the
statements.
2. Goods arrived on the 29th and the invoice has not shown up. What do you do at
close?
Why ask: unvouchered receipts are the most common way payables understates
expense.
Good answer: accrues the estimated amount in the period the goods were
received and reverses the accrual when the invoice arrives.
3. Walk me through reconciling a vendor statement to your records.
Why ask: it is the routine that finds missing invoices, unapplied credits,
and duplicate payments before the vendor does.
Good answer: compares open items line by line, identifies invoices the vendor
shows and you do not, chases credit memos that were never applied, and
documents every difference rather than writing it off.
4. What does the accounts payable aging report tell you, and what would you show
the owner?
Why ask: a good AP hire turns the aging into a decision, not a printout.
Good answer: reads the buckets, flags anything past due and why, separates
disputes from cash-timing delays, and brings a short list of what needs to be
paid this week.
5. The payables sub-ledger does not tie to the general ledger. How do you find
the difference?
Why ask: the method is the answer, and a methodical person will describe one.
Good answer: narrows by period, then by vendor, checks manual journal entries
posted straight to the control account, and looks for timing differences
before assuming an error.
6. How do you handle a credit memo or a vendor refund?
Why ask: credits get lost more often than invoices do.
Good answer: records it against the vendor, applies it to the next payment,
and follows up if a refund was promised and never arrived.
7. How do you prepare for 1099 season?
Why ask: it is an annual deadline that lands on the payables desk.
Good answer: keeps W-9 data current through the year rather than scrambling
in January, tracks reportable payments by vendor, and knows which vendor types
are reportable.
WHAT TO LISTEN FOR
•A close with a cutoff date and an accrual step, not just "I finish entering"
•Differences investigated to their cause, never forced away
•The aging used as a cash-flow tool for the owner
•Year-end reporting treated as a rolling task
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Set 5: Behavioral, Volume, and Vendor Relations Questions
Reporting your own mistake, handling a vendor who is 45 days past due, staying accurate at month end, improving a process, and telling someone senior that a payment is not ready yet.
Behavioral, Volume, and Vendor Relations Questions
BEHAVIORAL, VOLUME, AND VENDOR RELATIONS QUESTIONS
Candidate: __
Interviewer: __
Date: __
WHEN TO USE THIS SET
Accounts payable is a deadline job with an audience. Vendors call, the owner
wants cash preserved, and the person at the desk is in the middle. This set uses
past behavior to test accuracy under volume, the ability to say no politely, and
the willingness to raise a problem early. Ask for the situation, the action, and
the result on every answer.
QUESTIONS
1. Tell me about a time you found your own mistake after a payment went out.
Why ask: everyone makes errors in payables. What matters is whether they
report them.
Good answer: names the error, says who they told and how fast, and describes
the recovery and the change they made afterward. A candidate who has never
made a mistake is either new or not honest.
2. A vendor calls angry about an invoice that is 45 days past due. What do you
say?
Why ask: the person on the phone is representing your business.
Good answer: acknowledges it, looks it up while the vendor is on the line,
gives a real status and a real date rather than a vague promise, and follows
up in writing. Does not blame a colleague or the system.
3. How do you stay accurate when the volume spikes at month end?
Why ask: accuracy under pressure is the actual skill you are buying.
Good answer: a concrete method: batching, a checklist, entering in one focused
window, self-review of high-value items before release.
4. Describe a process you improved in accounts payable.
Why ask: it shows whether they think about the work or only perform it.
Good answer: a small, specific change with a before and after: a filing
standard, a weekly payment run instead of daily one-offs, a template for
requesting approvals.
5. Tell me about a time you had to tell someone senior that you could not
process something yet.
Why ask: the whole control environment depends on this being possible.
Good answer: calm, specific, offers the path to yes. No story here at all is
worth probing.
6. What part of accounts payable do you find most tedious, and how do you handle
it?
Why ask: honest answers here predict retention better than enthusiasm does.
Good answer: names something real (filing, chasing approvers, statement
reconciliation) and describes how they get it done anyway.
7. Why accounts payable, and where do you want to be in three years?
Why ask: a small business often cannot promote quickly, and it is better to
know now.
Good answer: a realistic path. Someone aiming to be a controller in eighteen
months may not stay, and that is a decision to make with open eyes.
WHAT TO LISTEN FOR
•Specific situations with named outcomes, not general claims
•Errors reported quickly rather than hidden
•Professional, factual handling of a frustrated vendor
•A realistic view of the role and of your business size
NOTES
__
Set 6: AP Scorecard, Red Flags, and Match Exercise
A six-area 1-to-5 rubric with space for evidence, a red-flag checklist, and a twenty-minute live exercise built around four invoices, one of which duplicates another under a different reference number.
AP Scorecard, Red Flags, and Match Exercise
ACCOUNTS PAYABLE SCORECARD, RED FLAGS, AND MATCH EXERCISE
Candidate: __
Interviewer: __
Date: __
HOW TO SCORE
Score each area from 1 to 5 immediately after the interview, while the answers
are fresh, and anchor every score to something the candidate actually said. If
more than one person interviews, score independently first and compare written
evidence before discussing. Use the same rubric for every candidate for the same
opening.
Rating scale:
5 = Strong, specific evidence 4 = Solid evidence 3 = Some evidence
2 = Weak or mixed evidence 1 = No evidence or red flags
SCORING AREAS
Process command: invoice to payment, coding, approval routing, payment terms
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Matching and exceptions: three-way match, variances, duplicates, no-PO invoices
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Controls and fraud awareness: bank-change verification, separation of duties
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Close and reconciliation: cutoff, accruals, vendor statements, aging
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Accuracy under volume: method, self-checking, error handling
If you only have thirty minutes, ask these four. Between them they cover process ownership, fraud judgment, matching discipline, and duplicate control, which is most of what goes wrong in payables. Each one is written below with the reason it earns its place and what separates a strong answer from a weak one.
Walk me through what happens to an invoice from arrival to payment.
Why ask it: It is the entire job in one question, and it exposes whether the candidate owned the cycle or only typed inside it.
Strong answer: An ordered sequence: log the invoice, match it to the purchase order and the receiving record, code it, route it for approval, enter it, schedule payment to terms, file the backup. A strong candidate names who approves what and at which dollar level.
Weak answer: A weak answer jumps from invoice to payment with nothing in between, or describes only the step they personally performed.
A vendor emails that their bank details changed. What do you do?
Why ask it: Payment redirection is the attack aimed squarely at accounts payable, and this answer is the cheapest fraud control you will ever buy.
Strong answer: Calls the vendor on a number already on file, never a number in the email, confirms with a known contact, requires written confirmation, and routes the change for second approval. Treats the urgency in the request as a reason to slow down.
Weak answer: Any version of updating the record from the email, replying to the sender to confirm, or calling the number in the signature block.
The invoice says 100 units, receiving logged 92. Which do you pay?
Why ask it: Paying the invoice rather than the receipt is exactly how a business pays for goods that never arrived.
Strong answer: Pays for the 92 received, holds the balance, and works with receiving and the vendor to confirm a short shipment, a backorder, or a return before releasing anything else.
Weak answer: Paying the full invoice to keep the vendor happy, or adjusting the receiving record so the numbers agree.
How do you catch a duplicate invoice before it is paid twice?
Why ask it: Duplicate payments are a quiet, recurring loss at small businesses, and the answer shows whether the candidate has a system or has never considered it.
Strong answer: Enters the vendor invoice number exactly so the system flags a repeat, watches for the same amount and date under a slightly different reference, and checks anything that arrives by email after already arriving by mail.
Weak answer: I would notice, or the software handles it, with no description of how.
The pattern across all four is the same, and it is the thing to listen for even in questions not on this list. A strong payables candidate treats a discrepancy as something to chase to its cause. A weak one treats it as something to make disappear. That single distinction predicts more about how this hire will go than any credential on the resume.
The Vendor Fraud Question Most Interviews Skip
Ask every accounts payable candidate what they would do if a vendor emailed to say their banking details had changed, because payment redirection is the fraud aimed specifically at this desk. The only acceptable answer involves verification through a channel the requester did not supply: a callback to a phone number that was already on file before the request arrived.
Business Email Compromise: $3.05 Billion in a Single Year
The FBI Internet Crime Complaint Center recorded $3,046,598,558 in reported business email compromise losses in 2025, the second-costliest category in a year with $20.877 billion in total reported losses across 1,008,597 complaints (FBI IC3, 2025 Internet Crime Report). The typical version of this scam is an email that looks like a known vendor asking accounts payable to update a bank account.
Small businesses are the easiest targets for this, not because they are careless but because one person often sets up the vendor, enters the invoice, and releases the payment. The interview is your cheapest chance to find out whether the person at that desk will slow down under pressure. Four checks tell you almost everything.
Verify on a number already on file
The correct answer to a bank-change request is a callback to a number you had before the request arrived. A candidate who would reply to the email, or call the number in the signature, has failed the most expensive question on the page.
Someone else approves the change
Ask who could add a vendor and who could release payment at their last job. You are testing separation of duties without using the phrase. If they did all of it alone, listen for whether that bothered them.
Urgency is the tell
Every payment-redirection attempt comes with a deadline attached. Ask what they do when a request is urgent and the approver is unreachable. The answer you want is that urgency makes them slower, not faster.
W-9 before the first payment
Ask what they collect before a new vendor is paid at all. A strong answer includes a completed W-9 with the legal name and taxpayer identification number, a verified address, and a record of who requested the vendor.
The vendor setup answer matters for a second reason beyond fraud. A candidate who collects a completed Form W-9 before the first payment is also the candidate who will not be reconstructing taxpayer identification numbers in January. Ask what they collect, in what order, and who approves it.
How to Score the Answers
Score six areas from 1 to 5 immediately after each interview, anchored to something the candidate actually said, and use the same rubric for every candidate for the same opening. Scoring from memory a day later is scoring your impression, not their answers.
Scoring area
What a 5 sounds like
Process command
An ordered cycle with named approvers and dollar thresholds
Matching and exceptions
Holds and investigates; never edits the PO to force a match
Controls and fraud awareness
Callback verification, second approver, urgency as a warning
Close and reconciliation
A cutoff date, an accrual step, and a reconciled sub-ledger
Accuracy under volume
A concrete method: batching, checklists, self-review
Vendor communication
Factual status and a real date, followed up in writing
The match exercise in the scorecard set is worth the twenty minutes it costs. Hand the candidate a purchase order, a receiving record, and four invoices, and ask which they would pay today. Catching the planted duplicate is the single best predictor in the whole process, and you do not need any accounting background to grade it. Use an evaluation form to keep the scores in one place.
If two people interview, each should score alone before either speaks, and the disagreements are the useful part. Then close the loop with a reference check that asks specifically about accuracy and about whether the person raised problems early or late.
Fair, Legal, and Structured Interviewing
Ask the same job-related questions of every candidate and score them on the same rubric. That single habit keeps you inside the law, reduces bias, and produces better hires at the same time, which is why a structured interview beats a free conversation on every measure that matters.
Ask about the job, not the person
Federal anti-discrimination law, enforced by the EEOC, prohibits basing a hiring decision on protected characteristics, and questions that touch them create risk even when they are asked as friendly small talk. Keep away from age, race, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. In a payables interview the specific traps are money-adjacent: do not ask about the candidate’s own debts, credit history, bankruptcies, or garnishments as a proxy for trustworthiness. If your role genuinely warrants a credit or background check, run it as a formal check under the applicable rules, with disclosure and consent, rather than as an interview question. This is general information, not legal advice.
Same core questions, every candidate
Ask every candidate for the same opening the same core set, in the same order, and score them on the same rubric. This is not bureaucracy for its own sake: a structured interview predicts on-the-job performance considerably better than a free-flowing conversation, and it makes your decision defensible because you can show what each person was asked and how they were rated. For a small business it is also the cheapest quality control available, because it stops the interview from drifting into whoever was easiest to talk to. Write the questions before you meet anyone.
Score independently, then discuss
When two people interview, have each fill in the scorecard alone before either speaks. Otherwise the more senior or more talkative voice anchors the other, which is how strong candidates get talked out of and weak ones get talked into. Compare written evidence first, then discuss where the scores disagree. Those disagreements are usually the most useful part of the whole process, because they point at the areas where you actually need a follow-up question or a second conversation.
Weight the sets to your real opening
A payables hire who will process forty invoices a week under a bookkeeper is a different person from the one who will own the vendor master, the payment run, and the month-end close alone. Weight the core and exception sets for the first, and add the close and fraud sets in full for the second. Deciding this before the first interview keeps you from hiring a processor for an owner’s job, which is the most common and most expensive mismatch in this role.
One caution is specific to money roles. It is tempting to probe a payables candidate about their own debts or credit history as an informal trustworthiness test, and that is a mistake: it is not job-related, it invites a discrimination claim, and it tells you nothing. Federal rules on what you may base a decision on are set out in the EEOC guidance on prohibited practices. If the role genuinely warrants a credit or background check, run it formally with disclosure and consent. This is general information, not legal advice.
Accounts Payable Pay
There is no separate federal occupation for accounts payable, so benchmark against bookkeeping, accounting, and auditing clerks, the classification that AP roles sit inside. Then adjust for invoice volume, systems, and whether the person owns the month-end close.
Median $50,670 a Year (BLS OEWS, May 2025)
Bookkeeping, accounting, and auditing clerks reported a median wage of $50,670 a year, about $24.36 an hour, in the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025). The lowest 10 percent earned about $36,000 and the highest 10 percent about $74,550, with the middle half between $43,520 and $61,470 (U.S. Bureau of Labor Statistics).
Where a candidate should sit in that range depends almost entirely on scope, and scope is the thing most small businesses have not decided before they post the opening. The comparison below is the split worth settling first, because it changes both the questions you ask and the number you offer.
Responsibility
Processing-level AP
Function-owning AP
Enters, codes, and files invoices
Runs the three-way match on PO invoices
Resolves price and quantity exceptions independently
Owns the vendor master file and new vendor setup
Reconciles vendor statements and produces the aging
Closes the payables sub-ledger at month end
A processing-level role sits low in the federal range and can reasonably be part-time at a small business. A role that owns the vendor master, exception resolution, and the close sits above the median and deserves the full six sets in the interview. Related openings you may be filling at the same time are covered by our accounts payable clerk and accounts payable specialist job descriptions.
Interviewing for AP Without an HR Department
At a company with a finance department, a controller runs this interview and a recruiter manages the scorecards. At a small business the owner runs it alone, between everything else, and usually has never done the job being interviewed for. Three problems follow from that, and each has a fix that costs nothing.
The interviewer has never processed a payables run
At a company with a finance department, a controller interviews the payables candidate and knows within two answers whether the person is real. At a small business the interviewer is the owner or an office manager who has never matched an invoice to a receiving record, and the technical answers are genuinely hard to grade. That is why every question in these sets carries the reason it is worth asking and what a good answer sounds like, and why the match exercise exists. You do not need to know the correct tolerance for a freight variance. You need to hear whether the candidate investigates a difference or forces it away, and you need to see whether they catch the duplicate invoice sitting in a stack of four.
One person will do the whole cycle, with nobody checking
In a small business the payables hire often sets up the vendor, enters the invoice, and releases the payment, which is the exact arrangement every fraud control exists to prevent. You usually cannot fix that by hiring a second person, so fix it with structure instead: the owner keeps read-only access to the bank, the owner approves any new vendor and any bank-detail change, and the owner reviews the payment register weekly. Ask the candidate directly how they feel about that. A strong payables person is relieved by it, because the controls protect them as much as they protect you. Resistance to owner review is the clearest red flag in the whole interview.
The role gets defined after the hire, not before
Most small businesses post an accounts payable opening without deciding whether the person is a processor or an owner of the function, and then discover the gap in month three. Decide first: will this person close the payables sub-ledger, reconcile vendor statements, and prepare the aging, or will they enter invoices while a bookkeeper or an outside accountant handles the period? The answer decides which of the six sets you weight and what you pay. Once you have chosen someone, the work shifts to onboarding, which is where FirstHR fits: e-signature for the offer and the confidentiality agreement, document management for the signed paperwork, and task workflows for system access and policy sign-off. FirstHR is an onboarding and HR platform, not accounting or payables software, and it does not run payroll, so pair it with those. Applicant tracking is coming soon to FirstHR.
Once you choose someone, onboarding an accounts payable hire has extra steps because of the access involved. The offer and confidentiality agreement come first, then system access with approval limits already decided, alongside the standard I-9 and W-4 paperwork.
Offer and confidentiality agreement
Confirm the role, the hourly rate or salary, and the start date in writing, and have the new hire sign a confidentiality agreement, since they will see vendor terms and banking data.
Set access and approval limits first
Decide before day one who can add a vendor, who can release a payment, and above what amount the owner approves. Grant the narrowest system access that lets the job get done.
Sign the controls policy
Put the bank-change verification rule and the payment approval thresholds in a short written policy and have it acknowledged on day one, so the standard is not folklore.
Store the records in one place
Keep the signed offer, the confidentiality agreement, the I-9 and W-4, and the policy acknowledgments together and easy to find when you need them.
Setting the approval thresholds before day one is the part small businesses skip, and it is the part that matters most. Decide who can add a vendor, who can release a payment, and above what amount you personally sign off, then write it down and have the new hire acknowledge it. That document is your first internal control, and it is far easier to establish on day one than to introduce in month six.
FirstHR connects the offer letter, the confidentiality agreement, e-signatures, the new hire paperwork, and the access-and-policy checklist in one place, so a small business can onboard a payables hire with the controls built in from the start. FirstHR is an onboarding and HR platform, not accounting or payables software, and it does not run payroll, so pair it with those. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Prove five things: the full invoice-to-payment cycle, exception judgment, fraud controls, month-end close, and accuracy under volume.
Open with walk me through an invoice from arrival to payment; an ordered, specific answer is the fastest signal of real ownership.
Ask what they would do if a vendor emailed that their bank details changed; only callback verification on a number already on file passes.
Watch for candidates who force a match by editing the purchase order or pay the invoice quantity instead of the received quantity.
Run a twenty-minute exercise with four invoices, one a planted duplicate; catching it is the best single predictor you can get.
Benchmark pay against bookkeeping, accounting, and auditing clerks, which reported a median of $50,670 a year in May 2025.
Frequently Asked Questions
What questions should I ask in an accounts payable interview?
Ask across five areas: the core invoice-to-payment process, invoice matching and exceptions, vendor master and payment fraud controls, month-end close and reconciliation, and behavioral evidence. The strongest single question is to have the candidate walk you through what happens to an invoice from the moment it arrives until the vendor is paid, because it is the whole job in one answer. Follow it with a three-way match question, a price-variance scenario, a short-receipt scenario, and a duplicate-invoice question. Then ask what they would do if a vendor emailed to say their bank details had changed. Skip generic questions about strengths and weaknesses in favor of these, and use the same set for every candidate so you can compare them on the same evidence.
What is a three-way match and how do I know if a candidate understands it?
A three-way match compares the purchase order, the receiving record, and the vendor invoice on quantity and price before a payment is released. It is the control that stops a business paying for goods it never received or paying more than it agreed. A candidate who really understands it can define it without hesitation and, more importantly, can tell you what they do when the three documents disagree: hold the invoice, find out why, and resolve it with purchasing, receiving, or the vendor before paying. The wrong answers are just as revealing. Anyone who says they would edit the purchase order so the invoice matches, or pay the invoice quantity rather than the received quantity, has told you they will force a match rather than investigate one.
How do I test accounts payable skills if I am not an accountant?
Use a live exercise instead of trying to grade technical vocabulary. Hand the candidate a purchase order, a receiving record, and four printed invoices, then ask which ones they would pay today and why. Build the stack so one invoice is clean, one is priced higher than the purchase order, one bills more units than were received, and one duplicates the clean invoice under a different reference number. You do not need accounting knowledge to see whether they catch the duplicate and hold the two exceptions. The exercise takes about twenty minutes and tells you more than an hour of conversation. Pair it with the good-answer notes in each question set, which describe what a strong response sounds like so you have a reference point while you listen.
What are the red flags in an accounts payable interview?
The clearest red flag is a candidate who would update a vendor’s bank details from an emailed request, or who would confirm the change by replying to that same email. Others follow the same pattern of forcing a result rather than investigating one: adjusting the purchase order so the invoice matches, paying the invoice quantity instead of the quantity actually received, or paying an invoice with no purchase order simply to end the vendor’s calls. Watch also for discomfort with oversight. A candidate who argues that owner review of the weekly payment register is unnecessary is telling you something important about a role that moves money. Finally, treat vagueness as a flag: no invoice volume, no named systems, and no clear account of what they personally did rather than what their team did.
What is the difference between an accounts payable clerk and an accounts payable specialist?
The titles are not standardized, so define the scope rather than trusting the label. In most small businesses a clerk processes invoices inside a system someone else owns: entering, coding, filing, and preparing payments for approval. A specialist typically owns more of the function: the vendor master file, exception resolution, vendor statement reconciliation, the aging report, and the month-end close of the payables sub-ledger. The practical test is whether the person will close the period and hand a clean number to whoever prepares the financial statements. If yes, you are hiring at the specialist level and should interview with the close and reconciliation set in full. If a bookkeeper or an outside accountant handles the period, the core and exception sets carry most of the weight.
How much does an accounts payable hire cost?
Accounts payable roles sit inside the federal occupation for bookkeeping, accounting, and auditing clerks, which reported a median wage of $50,670 a year, about $24.36 an hour, in the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey for May 2025. The lowest 10 percent earned about $36,000 and the highest 10 percent about $74,550. There is no separate federal occupation for accounts payable specifically, so treat that range as the benchmark and adjust for your market, your invoice volume, and whether the role owns the month-end close. A pure processing role sits low in the range; a role that owns the vendor master, exception resolution, and the close sits well above the median. Post an hourly rate for an hourly role and an annual figure for a salaried one, and keep both consistent through the offer.
Are these accounts payable interview questions legal to ask?
Yes. Questions about a candidate’s payables experience, systems, how they handle a specific invoice scenario, and how they respond to a bank-change request are job-related and permitted. The general caution applies to any interview: keep away from protected characteristics such as age, race, religion, national origin, sex, pregnancy or family status, disability, and genetic information, and ask the same job-related questions of every candidate. One caution is specific to money roles. Do not use the interview to probe the candidate’s own debts, credit history, or bankruptcies as an informal trustworthiness test. If the role genuinely warrants a credit or background check, run it as a formal check with the required disclosure and consent under the applicable federal and state rules. This is general information, not legal advice.
