Accounts Payable Specialist Assessment

Why Accounts Payable Specialists are hard to hire well

Accounts payable is one of the few finance roles where the whole job is judged on the absence of events. When it is done well, nothing happens: invoices are paid, suppliers stay quiet, the ledger reconciles, and nobody in the business thinks about it. That makes it very difficult to hire for, because the candidate in front of you can only describe an uneventful history, and an uneventful history is produced equally by someone with excellent controls and someone who has simply not yet been tested.

The role has also changed faster than its job description. Capture tools, automated matching and supplier portals have taken most of the keying out of the work. What is left is the exceptions: the invoice that will not match, the goods receipt nobody posted, the credit note that never arrived, the supplier who is threatening to stop supply. The routine part has been automated away and the difficult part has been concentrated. Hiring processes that still screen for processing volume are selecting for the part of the job that no longer exists.

Then there is the risk profile, which is genuinely unusual. This is one of the only seats in a finance function where one person acting on a plausible instruction can move real money out of the business. Invoice redirection fraud does not look like fraud from inside the queue; it looks like a routine administrative request from a familiar contact under mild time pressure. The competency that stops it is not vigilance in the abstract but a specific willingness to hold a payment and make somebody wait, which cuts directly against every other incentive in the role.

What separates the best from the rest

The best specialists treat the queue as a set of decisions rather than a backlog. They know which invoices carry an early settlement discount, which suppliers are on stop, and which one is holding up a production line, and they work the queue in that order rather than in the order it arrived. Weaker ones process front to back, hit the same throughput, and let a discount lapse or a critical supplier escalate to somebody else’s problem.

They also chase the root cause of exceptions instead of clearing them. A price variance is a symptom: the purchase order was raised at the wrong price, or the supplier has changed their rates, or somebody agreed something outside the system. A strong specialist closes the underlying issue and the exception stops recurring. A weaker one resolves the same mismatch with the same supplier every month for a year and reports it as a heavy workload, which it is.

The third difference is comfort with friction. Good AP people say no to their own colleagues regularly, and they do it without turning it into a conflict. They will hold a payment that lacks approval even when the requester is senior and irritated, and they will explain why in a way that does not read as obstruction. This is a social skill more than a technical one, and it is the single best predictor of whether your controls will survive contact with a busy month.

Why interviews alone fall short

The standard AP interview asks about volume and systems: how many invoices a week, which ERP, whether they have used three-way matching. Every credible candidate answers those questions well, because they are questions about exposure rather than judgement. Nobody has ever failed an interview by saying they processed four hundred invoices a week in SAP. The answers do not separate the field, they just confirm the CV.

What the format cannot reach is what the candidate does under the specific pressures that cause AP failures: a deadline, a plausible request, an incomplete document, and a senior person waiting. Those situations are resolved in a few minutes by one person with no witness, which is exactly why they cannot be evaluated by asking someone to describe their approach in general terms. Situational scenarios put every candidate through the same set of them and show you the decision rather than the description of the decision.

Common hiring mistakes in accounts payable recruitment

• Screening on ERP experience - the difference between Coupa and Ariba is a fortnight of training, and the difference between a specialist who verifies bank changes and one who does not is unbounded
• Selecting for throughput - the highest-volume processor in a manual environment is often the fastest at creating exceptions in an automated one
• Never testing the payment fraud scenario - it is the highest-value failure mode in the role and it appears in almost no hiring process
• Ignoring supplier communication - most AP escalations reach the finance director because a query was answered badly, not because a payment was late
• Treating vendor master maintenance as clerical - duplicate and stale supplier records are where duplicate payments and misdirected funds actually originate

The work this role is assessed against

• Intake and validate invoices from EDI, email, and portals, code to GL and cost centres, and route for approval
• Perform 2-way and 3-way matching against purchase orders and receipts, and resolve price and quantity discrepancies
• Prepare and execute ACH, cheque, and wire payments, and manage payment calendars and remittance advice
• Maintain vendor master data, collect tax forms, and support withholding and year-end reporting readiness
• Produce AP aging, GR/IR, and KPI reports, research duplicates and unmatched items, and clear holds

Tools and outputs this role works with

Microsoft Excel, Google Sheets, SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365 Finance, QuickBooks Online, Sage Intacct, Coupa, SAP Ariba, Tipalti, Bill.com, Basware, Concur Expense, Kofax, ABBYY FlexiCapture, banking portals for ACH and wire payments, Power BI, Tableau, ServiceNow, and Zendesk.