Accounts payable interviews should reveal whether a candidate can protect cash while recording supplier obligations completely and accurately. A strong analyst knows more than debit and credit definitions: they can trace an invoice to the right supplier, purchase authorization, delivery evidence, accounting period, and approved payment destination. Recruiters should look for practical judgment when documents disagree, a supplier changes bank details, or an urgent request conflicts with an established control.

This guide to 100+ Accounts Payable Interview Questions and Answers contains 120 prompts across beginner, intermediate, and experienced levels. It concentrates on invoice-to-pay execution, reconciliation, close support, and control design rather than general accounting theory, customer collections, or SAP MM configuration. Worked entries and calculations help interviewers test whether candidates can explain the financial consequences of their decisions.

How can recruiters assess genuine accounts payable judgment when interview assistance can hide gaps in payment controls and accounting reasoning?

Ask candidates to work through a partial receipt, explain a balanced entry, or respond to an urgent bank-change request. Change one fact and ask what must be verified before payment. Their explanation should reveal both what they know and where they would seek authorized tax or accounting guidance.

Sherlock AI helps recruiters assess signals of potential AI cheating, deepfakes, impersonation, and unauthorized assistance during interviews.

Use those signals alongside practical work and follow-up discussion, not as conclusive proof of misconduct. An invoice scenario with incomplete evidence is often more revealing than a memorized list of accounting terms.

Accounts Payable Interview Questions

Use this complete question bank to select prompts for the role before consulting the answers. Establish the entity, currency, accounting framework, and relevant business policy when a scenario depends on them. The progression moves from accurate invoice handling to exception resolution and end-to-end control ownership.

Accounts Payable Interview Questions for Beginners

These questions test invoice documents, basic journal entries, payment terms, supplier records, matching, and the everyday controls that prevent avoidable AP errors.

1. What is accounts payable, and what does the AP team control?

2. How does accounts payable differ from accounts receivable?

3. What are the main steps in an invoice-to-pay process?

4. What information should you check on a supplier invoice?

5. What is the difference between a purchase order, receipt, and invoice?

6. What is two-way matching?

7. What is three-way matching?

8. How do you record a simple expense invoice and its payment?

9. Why is accounts payable normally a credit balance?

10. How is an accounts payable balance different from an expense?

11. What is a non-PO invoice, and how should it be approved?

12. What do payment terms such as net 30 and 2/10 net 30 mean?

13. How do invoice date, posting date, and due date differ?

14. What is a supplier credit memo?

15. What is a debit memo in an accounts payable process?

16. How do you handle an invoice that appears to be a duplicate?

17. What information belongs in a vendor master record?

18. What should you check before onboarding a new supplier?

19. What is segregation of duties in accounts payable?

20. Why should a supplier bank-account change be verified independently?

21. What is an accounts payable aging report?

22. How do you reconcile a supplier statement?

23. What is a payment run?

24. What is remittance advice, and why is it useful?

25. What should you do when an invoice total does not add up?

26. How should you handle an invoice sent to the wrong legal entity?

27. What is an accrual, and why might AP support it?

28. What is a prepaid expense, and how is it different from an unpaid invoice?

29. What does goods received not invoiced mean?

30. What is the AP subledger, and how does it relate to the general ledger?

31. What is an invoice hold?

32. How should you prioritize your daily AP workload?

33. What would you say to a supplier asking when an invoice will be paid?

34. What documents should be retained for an AP audit trail?

35. Why does AP collect Form W-9 from some US suppliers?

36. How should AP treat sales tax, use tax, VAT, or GST on invoices?

37. What is the difference between a partial payment and a short payment?

38. How do you correct an invoice posted to the wrong expense account?

39. Which basic AP metrics are useful for an analyst?

40. What checks should you perform before marking an invoice as paid?

Accounts Payable Interview Questions for Intermediate

These questions examine partial receipts, credits, discounts, month-end accruals, foreign currency, tax handling, reconciliations, and practical ERP exception resolution.

41. How would you resolve a quantity mismatch on a partially received PO?

42. How would you investigate an invoice price above the PO price?

43. How should freight and other additional charges be handled during matching?

44. How do unit-of-measure differences cause invoice exceptions?

45. How would you control service invoices without physical goods receipts?

46. How do you process an invoice when only part of the amount is disputed?

47. How should a supplier credit be applied across multiple invoices?

48. How would you account for an advance paid to a supplier?

49. How do you calculate and record an early-payment discount?

50. How would you compare an early-payment discount with financing cost?

51. How do you build a short-term cash forecast from AP data?

52. How would you reconcile AP to the GL at month end?

53. What would you do if a payment appears in the bank but not in AP?

54. How would you handle a rejected or returned electronic payment?

55. What is the correct response to a lost supplier check?

56. How do you investigate old debit balances in supplier accounts?

57. How would you prepare a reliable month-end accrual for uninvoiced services?

58. How do you prevent an accrual and a later invoice from duplicating expense?

59. How do you investigate an aged GRNI balance?

60. How should AP handle an invoice received after the reporting period closes?

61. How do you record and remeasure a foreign-currency payable?

62. How do you calculate the exchange difference when a foreign payable is settled?

63. How would you review US information-reporting data before year end?

64. How should AP handle US backup withholding when it applies?

65. What should AP do when a US supplier invoice has no sales tax?

66. How do you distinguish recoverable input VAT from a supplier payment obligation?

67. How do you diagnose an ERP invoice that will not validate?

68. Why might an approved invoice be missing from a payment proposal?

69. How would you improve duplicate detection beyond exact invoice numbers?

70. What controls are needed for recurring invoices and templates?

71. How do you validate invoices captured by OCR or AI?

72. What should an AP approval workflow do when the usual approver is absent?

73. How should AP process employee expense reimbursements without duplicate supplier payments?

74. How do corporate-card purchases affect AP reconciliation?

75. How would you manage a supplier dispute that threatens a critical service?

76. How can AP support a search for unrecorded liabilities?

77. How would you calculate an AP on-time payment rate fairly?

78. What is days payable outstanding, and what are its limitations?

79. How would you reconcile intercompany invoices handled by AP?

80. How would you organize and resolve an AP exception backlog?

Accounts Payable Interview Questions for Experienced

These questions assess control design, fraud response, financial-reporting judgment, supplier financing, automation, migration, leadership, and complex cross-functional decisions.

81. How would you design an end-to-end AP control framework?

82. How would you maintain segregation of duties in a small AP team?

83. How would you investigate suspected vendor-master fraud?

84. What would you do immediately after discovering a payment-diversion incident?

85. How would you design controls over supplier bank changes and pending payment files?

86. How would you choose invoice matching tolerances?

87. How would you detect invoice splitting designed to avoid approval limits?

88. How would you build a duplicate-payment recovery program?

89. What controls are required when AP processing is outsourced?

90. How would you assess whether an AP control is operating effectively?

91. How would you distinguish a completeness problem from an AP reconciliation problem?

92. How would you evaluate a material cutoff error discovered before financial statements are issued?

93. How would you assess whether an old unpaid invoice can be written off?

94. How would you distinguish a routine accrual from a provision or contingency?

95. How would you account for a supplier rebate that affects purchased inventory?

96. What should AP understand about supplier-finance arrangements?

97. How would you build an AP cash forecast under financial stress?

98. How would you explain a rising DPO alongside worsening supplier relationships?

99. How should AP handle foreign-currency advances differently from monetary payables?

100. How would you control exchange rates used in AP across multiple entities?

101. How would you prevent duplicate payments after an integration timeout?

102. What should be tested before migrating open AP balances to a new ERP?

103. How would you test a change to AP payment configuration?

104. How would you govern straight-through invoice processing?

105. How would you manage AP operations during an ERP outage?

106. How would you make AP analytics reliable enough for control decisions?

107. How would you design AP access reviews and privileged-access controls?

108. How would you reduce AP processing costs without weakening controls?

109. How would you design AP responsibilities in a shared-service center?

110. How would you assess a global e-invoicing rollout from an AP perspective?

111. How would you investigate a clean AP reconciliation with an unexpectedly large expense increase?

112. How would you diagnose payment complaints when the ERP shows invoices as settled?

113. What would you do if management asked you to delay recording valid invoices to improve results?

114. How would you handle a request to bypass AP controls for an executive’s urgent payment?

115. How would you resolve repeated late payments caused by missing receipts?

116. How would you evaluate an AP automation vendor’s business case?

117. What should an AP leader include in a monthly management review?

118. How would you prioritize AP improvements during your first 90 days?

119. How would you assess an AP candidate using a practical invoice scenario?

120. How would you resolve a combined receipt, credit, bank-change, and cutoff exception?

Accounts Payable Interview Questions and Answers

The answers follow the bank in the same order and begin with the decision or principle a candidate should explain. Examples make the reasoning concrete while identifying important policy and jurisdiction limits. The focus is invoice-to-pay work in commercial businesses, with US-oriented tax examples and globally relevant controls. Journal entries use simplified accrual-accounting assumptions and omit tax, fees, or prior entries unless stated. Apply the relevant US GAAP, IFRS, local tax law, contract, and controller-approved policy rather than treating an example as a universal rule. Microsoft Dynamics 365 Finance and explicitly labeled Oracle Fusion Cloud releases illustrate ERP behavior; permissions, enabled features, configuration, and release affect actual results. Mathematical examples are illustrations, not financial advice or executed ERP transactions.

Accounts Payable Interview Questions and Answers for Beginners

The beginner answers connect core terminology to actual invoices and payments. Notice the separation between recognizing an obligation, approving it, and settling it.

1. What is accounts payable, and what does the AP team control?

Accounts payable is the amount owed to suppliers for goods or services already received or otherwise recognized as obligations under the applicable accounting policy. The AP team controls the route from an incoming supplier invoice to an authorized, accurately recorded payment. That includes identifying the supplier, checking supporting evidence, coding the transaction, resolving exceptions, and preserving the audit trail. For example, an approved invoice for consumed cleaning services creates an expense and a payable; paying it later clears the payable rather than creating the expense again. AP should not independently approve its own purchases or invent evidence of receipt.

2. How does accounts payable differ from accounts receivable?

Accounts payable tracks obligations to suppliers, while accounts receivable tracks amounts customers owe the business. AP focuses on liability completeness, legitimate purchasing, and controlled cash outflows; AR focuses on billing, collection, and customer credit. If a company buys packaging for $900 on credit, it records AP. If it sells finished products to a customer on credit, that is an AR transaction. A supplier can also be a customer, but the balances should remain separately identifiable. Do not net them merely because the names match; settlement rights, agreements, accounting requirements, and authorized procedures determine whether offsetting is appropriate.

3. What are the main steps in an invoice-to-pay process?

The main steps are invoice capture, supplier and document validation, matching or business approval, accounting, payment approval, payment execution, and reconciliation. An effective process also has explicit exception queues and owners. For a goods invoice, AP checks the supplier record and duplicate indicators, compares the invoice with the purchase order and receipt, and routes unresolved differences before including it in a payment run. After payment, the team reconciles the bank outcome and supplier balance. Recording an invoice, approving it, and successfully transferring funds are separate events; a status such as “processed” should never conceal which event actually occurred.

4. What information should you check on a supplier invoice?

Check the supplier identity, invoice number, invoice date, billed legal entity, currency, line descriptions, quantities, prices, tax, total, and payment terms against the supporting records. Where required, also validate a purchase order reference, tax registration details, and legally required invoice fields. Recalculate totals rather than assuming a polished PDF is correct. For example, ten units at $45 plus $20 freight total $470 before applicable tax. A newly printed bank account should trigger the controlled supplier-change process, not overwrite the approved master data. Requirements differ by jurisdiction, and an invoice’s appearance alone does not establish its legitimacy.

5. What is the difference between a purchase order, receipt, and invoice?

A purchase order documents an authorized commitment to buy, a receipt records goods received or services accepted, and an invoice states the supplier’s claim for payment. They answer different questions: what was ordered, what was delivered, and what was billed. A PO for 50 monitors is not evidence that all 50 arrived. If receiving confirms only 30, AP should investigate an invoice for 50 rather than treating the PO as proof of delivery. Service acceptance may use an approved milestone or timesheet instead of a warehouse receipt. The document chain must reflect the actual transaction, not merely satisfy system fields.

6. What is two-way matching?

Two-way matching compares an invoice with the purchase order, commonly checking price and other configured commercial details. It does not independently prove that goods were received. For example, an invoice unit price of $24 against a PO price of $20 creates a price exception, even if both documents show the same quantity. A business may use two-way matching for selected categories when other evidence supports performance, but that is a risk decision. In Dynamics 365 Finance, two-way matching is price based; exact checks and tolerances depend on configuration. Do not describe every ERP’s two-way match as an identical control.

7. What is three-way matching?

Three-way matching compares the invoice, purchase order, and receipt or service-acceptance evidence. Its purpose is to identify billing that does not agree with authorized prices or recorded delivery. Suppose a PO authorizes 100 units at $12, receiving records 80 units, and the supplier bills 100. The price may agree, but the receipt quantity does not support the full invoice. Route the exception to receiving and procurement, then resolve it through accurate receipts, a supplier correction, or an authorized treatment. A matching pass is not a guarantee against fraud, because collusive or fabricated source documents can still agree.

8. How do you record a simple expense invoice and its payment?

For services already consumed, debit the relevant expense and credit accounts payable when the liability is recognized; when paid, debit accounts payable and credit cash. For example, a $1,250 cleaning invoice with no tax, discount, or prior accrual is Dr Cleaning expense $1,250 / Cr AP $1,250. Settlement is Dr AP $1,250 / Cr Cash $1,250. The second entry does not debit cleaning expense again. Real ERP postings may use payment-clearing accounts before bank reconciliation. If the invoice relates to inventory, a fixed asset, prepaid services, or a previously recorded accrual, the debit and clearing path must change accordingly.

9. Why is accounts payable normally a credit balance?

A credit increases a liability, so unpaid supplier obligations normally produce credit balances in AP. Debits reduce that liability through payments, supplier credits, or corrections. Starting with no balance, a $700 invoice produces a $700 credit; a $500 payment leaves a $200 credit outstanding. A debit supplier balance is possible, but it deserves investigation rather than automatic write-off. It might represent an advance, an overpayment, an unapplied credit, or an incorrect posting. The individual supplier position and financial-statement presentation may differ from the net total of the control account, so inspect the underlying open transactions.

10. How is an accounts payable balance different from an expense?

AP is a balance-sheet obligation, while an expense records consumption or another expense-recognition event in the income statement. The two often arise together, but not always. An unpaid equipment purchase can create a payable with a debit to an asset rather than immediate expense. Conversely, an accrued utility expense may be recognized before a supplier invoice enters AP. Paying a valid invoice normally reduces cash and the payable without creating a second expense. In an interview, first establish what was purchased, when it was received or consumed, and whether a previous accounting entry already recognized the obligation.

11. What is a non-PO invoice, and how should it be approved?

A non-PO invoice has no purchase order to support the usual PO match, so it needs an alternative authorized approval path. AP should establish business purpose, receipt of the goods or services, correct coding, and approval by someone with the necessary authority. For example, a permitted utility invoice might be checked against the account location and consumption history, then approved by the responsible manager. “Non-PO” is not the same as “uncontrolled.” Record the exception category and supporting evidence, and avoid creating a retrospective PO solely to make an unauthorized purchase appear preapproved.

12. What do payment terms such as net 30 and 2/10 net 30 mean?

Net 30 generally means the full amount is due 30 days after the contractually defined baseline date. Terms of 2/10 net 30 offer a 2% discount for qualifying payment within ten days, otherwise the full amount is due within 30 days. On a discount-eligible $5,000 balance, that is a $100 discount and $4,900 payment. Confirm whether freight, tax, or other charges are included in the discount base. The starting date and whether timely payment means initiation or receipt of funds depend on the agreement; do not assume every supplier calculates terms from invoice entry into the ERP.

13. How do invoice date, posting date, and due date differ?

The invoice date is the date on the supplier’s document, the posting or accounting date determines the ledger period, and the due date determines contractual payment timing. They can legitimately differ. A September service invoice dated October 3 may require a September accrual even though the invoice is entered in October. Its payment due date follows the agreed terms, not necessarily the accrual date. Preserve the actual source-document date and follow controlled period rules rather than changing dates to force a desired result. Incorrect date mapping can distort both month-end expense recognition and overdue-payment reporting.

14. What is a supplier credit memo?

A supplier credit memo reduces an amount owed, usually because of a return, pricing correction, allowance, or overbilling. AP should verify the reason and connect it to the relevant transaction rather than simply entering a negative amount with no context. If a $1,000 expense invoice is reduced by a valid $150 price correction before payment, an illustrative entry is Dr AP $150 / Cr the original expense $150, leaving $850 due, assuming no tax or inventory complications. Apply or settle the credit correctly so the payment proposal does not pay the original gross invoice while leaving the credit unused.

15. What is a debit memo in an accounts payable process?

A buyer’s debit memo commonly documents a requested reduction in what it owes a supplier, such as a charge for returned goods. Terminology differs by ERP and jurisdiction, so establish who issued the document and its accounting direction. A buyer claiming a $200 allowance should retain return or dispute evidence and obtain the required approval or supplier acknowledgment. Do not assume a self-issued deduction automatically extinguishes an enforceable obligation. When the reduction is valid and recorded, AP is debited; the credit follows the original cost, inventory, or other appropriate account. Tax-document requirements may require separate supplier action.

16. How do you handle an invoice that appears to be a duplicate?

Place the suspected duplicate in an exception workflow and compare it with existing invoices and payments before posting or paying it. Check supplier identity, normalized invoice number, amount, currency, dates, PO references, and document images. A scan labeled “copy” may be a reminder of an unpaid original, not a new liability; two equal monthly invoices may be legitimate recurring charges. Record the decision and retain the rejected copy’s audit trail. Never add a suffix merely to bypass a duplicate-number warning. That can turn a useful preventive control into a second authorized payment for the same obligation.

17. What information belongs in a vendor master record?

A vendor master normally holds the legal supplier name, addresses, tax identifiers where applicable, approved payment terms, currency, payment method, bank details, contact information, and entity or site relationships. It should also retain status and change history. For example, the legal supplier may have several remittance sites, so choosing the right site matters as much as choosing the right name. Sensitive data needs restricted access and controlled changes. Avoid treating master-data creation as clerical transcription: an inaccurate or fraudulent record can redirect every otherwise correctly matched invoice to the wrong recipient.

18. What should you check before onboarding a new supplier?

Confirm the supplier’s legal identity, business relationship, appropriate approvals, payment details, and relevant tax documentation before enabling payment. Search for existing records to avoid duplicates, including alternate names and tax identifiers where permitted. Apply the organization’s risk-based compliance checks through the responsible teams rather than claiming AP alone performs legal clearance. A supplier’s email is evidence to validate, not sufficient authority to create a bank account. Record who requested onboarding, who checked it, and who approved it. The checks should be proportionate, but urgency should not eliminate independent verification of the destination for funds.

19. What is segregation of duties in accounts payable?

Segregation of duties separates actions that would otherwise allow one person to create and conceal an improper payment. Important combinations include supplier creation, bank-detail changes, invoice approval, payment preparation, payment release, and reconciliation. For example, the person changing a supplier’s bank account should not independently release the next payment to that account. System roles and bank permissions both matter; separate job titles do not help if everyone shares a privileged login. Small teams may need documented compensating reviews by an independent owner, but those reviews must examine actual evidence and exceptions rather than simply sign a cover sheet.

20. Why should a supplier bank-account change be verified independently?

Bank-account changes can redirect legitimate payments to an attacker, including when the request comes from a compromised real supplier mailbox. Verify the request through a trusted contact channel established independently of the change request, and obtain the required separate approval before updating the master. Do not call a phone number supplied only in the suspicious message. Preserve verification evidence, restrict access to banking details, and ensure pending payment files use the intended approved account. A convincing signature, familiar email thread, or urgent senior-person request is not a substitute for the control; those details can be part of the deception.

21. What is an accounts payable aging report?

An AP aging report groups open supplier balances into time buckets, often based on due date, to show what is current and overdue. For example, a report might separate not-yet-due invoices from 1–30, 31–60, and more-than-60-day overdue balances. Confirm the report’s basis: aging from invoice date answers a different question from aging from due date. Review credit balances, disputed invoices, and unallocated payments separately so a net total does not hide problems. An aging report supports payment planning and escalation, but it is not automatically a reconciled general-ledger balance or a complete list of unrecorded obligations.

22. How do you reconcile a supplier statement?

Compare the supplier’s statement line by line with your open-item ledger, investigating missing invoices, credits, payments in transit, and allocation differences. Start with matching supplier identity, currency, and statement date. If the supplier shows $8,400 due while your ledger shows $7,900, a missing $500 invoice is one possibility, but so is an unapplied payment or an incorrect supplier charge. Request documents and verify receipt before recording a new liability. Document each reconciling item, its owner, and resolution. A statement is useful completeness evidence, but should not replace the original invoice and approval controls.

23. What is a payment run?

A payment run selects eligible liabilities and prepares payments according to approved criteria such as due dates, discount opportunities, payment methods, and available funding. AP reviews the proposal for holds, credits, duplicate risks, unusual suppliers, and bank-detail changes before authorized release. For example, a weekly run can include invoices due before the next run while excluding a disputed invoice with an active hold. Creating a proposal does not prove money has moved. Distinguish proposal, approval, file generation, bank acceptance, settlement, and ledger reconciliation so rejected or delayed payments are not incorrectly reported as completed.

24. What is remittance advice, and why is it useful?

Remittance advice tells a supplier which invoices, credits, and deductions a payment is intended to settle. It helps the supplier allocate cash accurately and reduces statements showing invoices as unpaid after the buyer has sent funds. For example, a $2,700 payment might settle a $3,000 invoice less a $300 credit; the advice should identify both documents. Send it through an approved channel and avoid unnecessary sensitive banking information. It is a communication record, not proof that the bank successfully settled the payment. If a supplier disputes receipt, trace the payment status rather than resending money based only on the advice.

25. What should you do when an invoice total does not add up?

Recalculate line extensions, discounts, freight, and tax, then identify whether the difference comes from arithmetic, rounding, missing lines, or data capture. Compare the source document with the ERP entry before contacting the supplier. For example, three items at $120 and $25 freight total $385 before tax; a captured subtotal of $835 suggests an entry or recognition error. Correct your own input with an audit trail, but obtain an appropriate supplier correction when the invoice itself is wrong. Do not force a balancing distribution into an unrelated expense account merely to make validation pass.

26. How should you handle an invoice sent to the wrong legal entity?

Hold and route it for correction rather than booking it wherever a convenient supplier record exists. Confirm which entity contracted for and received the goods or services, then determine whether the supplier must reissue the invoice or an authorized intercompany arrangement applies. Tax recovery, reporting, and legal liability may depend on the entity named. For example, a subsidiary’s purchase billed to the parent cannot automatically be treated as a parent expense. Preserve the original and corrected documents and prevent both from being paid. Shared-service processing does not remove the need for accurate entity-level accounting and authorization.

27. What is an accrual, and why might AP support it?

An accrual recognizes an obligation for goods or services received before the corresponding invoice has been recorded. AP helps by identifying late invoices, unmatched receipts, recurring supplier costs, and held documents that may belong in the closing period. For example, a supported $2,400 estimate for September maintenance can be Dr Maintenance expense $2,400 / Cr Accrued liabilities $2,400. The later invoice must clear or be coordinated with that accrual, not create an unnoticed second expense. Estimation, classification, materiality, and reversal policy belong to the applicable accounting framework and controller-approved process; an open PO alone does not prove an accrual is required.

28. What is a prepaid expense, and how is it different from an unpaid invoice?

A prepaid expense represents a benefit paid for or recognized in advance of consumption, whereas an unpaid invoice represents a liability. They can coexist when an invoice for a future benefit is recognized before settlement. For example, under an appropriate recognition policy, a $12,000 annual insurance invoice can debit prepaid insurance and credit AP; payment clears AP, and subsequent monthly recognition debits insurance expense and credits the prepaid asset by $1,000. Confirm the coverage dates and policy rather than assuming every advance invoice immediately creates an asset and liability. Prepaid schedules should reconcile to the ledger and avoid duplicate amortization.

29. What does goods received not invoiced mean?

Goods received not invoiced, often called GRNI or a receipt accrual, represents received goods for which supplier invoicing has not yet completed the accounting chain. In a simple receipt-accrual design, receiving $6,000 of inventory debits inventory and credits GRNI; the matching invoice then debits GRNI and credits AP. Actual postings depend on the ERP and valuation configuration. A GRNI balance can reveal genuine unbilled receipts, missing invoices, incorrect receipt quantities, returns, or mismatches. Aging and investigating it is important because simply paying invoices correctly does not ensure the receipt accrual account is accurate.

30. What is the AP subledger, and how does it relate to the general ledger?

The AP subledger holds supplier-level invoices, credits, payments, and open-item detail; the general ledger summarizes the accounting by control account and other dimensions. Their balances should reconcile for the same entity, currency basis, account scope, and accounting date. If a subledger shows $90,000 while its GL control account shows $92,000, investigate unposted transfers, direct journals, timing, or report scope rather than inserting a $2,000 plug. A supplier aging can assist the reconciliation but may use different inclusion rules. Maintain traceability from the GL total back to individual supplier transactions and their accounting events.

31. What is an invoice hold?

An invoice hold prevents an invoice from progressing through a specified step until an exception is resolved. Depending on the hold and ERP, it may block payment, accounting, or both. Typical reasons include a quantity mismatch, missing approval, invalid account, or supplier dispute. AP should identify the exact hold, responsible owner, and evidence needed for release. A hold does not automatically mean no liability exists: received services may still require recognition at period end. Do not remove a hold simply because an invoice is overdue; resolve the underlying issue or obtain a documented exception through authorized policy.

32. How should you prioritize your daily AP workload?

Prioritize by payment deadlines, business impact, risk, and close requirements rather than processing the easiest invoices first. Separate urgent valid payments from requests that only sound urgent. For example, a verified critical-service invoice due today may need immediate escalation, while a new bank-change request needs verification even if the requester demands same-day payment. Track approaching discount dates, unresolved holds, aging receipts, and supplier queries with named owners. A visible queue makes trade-offs explicit and prevents high-risk exceptions from disappearing beneath routine volume. Speed matters, but not at the cost of duplicate payments or unsupported entries.

33. What would you say to a supplier asking when an invoice will be paid?

Give a factual status, explain any missing requirement, and provide a realistic next step without promising an unapproved payment. First confirm the supplier and invoice through the approved communication process. For example, explain that the invoice is recorded but awaiting confirmation of delivery, identify the internal owner, and give the next update time. If payment has been released, provide permitted remittance or tracing details and distinguish release from bank settlement. Log the conversation so another analyst can continue it. Avoid revealing unrelated supplier data or changing banking instructions during an ordinary status call without the separate verification process.

34. What documents should be retained for an AP audit trail?

Retain the invoice, relevant PO or contract, receipt or service acceptance, coding and approval evidence, exception decisions, supplier-change verification, payment authorization, and settlement or reconciliation records. The trail should show who did what and when, including edits and reversals. For a disputed price, retain the authorized resolution rather than only the final corrected amount. Use the organization’s applicable retention schedule, tax requirements, litigation holds, and access controls; there is no universal retention period for every country and document. A folder of PDFs is insufficient if it cannot link each document to the accounting and payment transaction.

35. Why does AP collect Form W-9 from some US suppliers?

Form W-9 supplies a US payee’s taxpayer identification information and certifications for relevant information-reporting purposes. AP collects it through a controlled process so the tax team can classify reportable payments and identify missing or inconsistent information. It is not proof that the supplier delivered goods, owns a bank account, or is exempt from every reporting requirement. Foreign payees may require an appropriate Form W-8 instead, subject to tax review. Do not apply a blanket 1099 threshold or exemption from memory; use current payment-year instructions and the payee’s circumstances, and protect the form’s sensitive information.

36. How should AP treat sales tax, use tax, VAT, or GST on invoices?

AP should validate tax using the transaction’s jurisdiction, supply type, entity status, and approved tax configuration rather than treating all invoice tax as the same expense. US sales and use tax differs from creditable VAT or GST regimes. Missing supplier tax does not necessarily mean nothing is due, and tax shown on an invoice is not automatically recoverable. For example, an eligible input-tax amount may debit a tax-recoverable account, while nonrecoverable tax may form part of cost under the applicable policy. Route uncertain cases to tax specialists and retain the evidence supporting the selected treatment.

37. What is the difference between a partial payment and a short payment?

A partial payment deliberately settles only part of an invoice, leaving a recognized balance outstanding; a short payment often describes paying less than the supplier expects, sometimes because of an asserted deduction. The commercial reason and accounting treatment matter more than the label. Paying $600 against a $1,000 invoice normally leaves $400 open unless a valid credit, discount, or other approved adjustment clears it. Record any dispute separately and communicate the allocation. Do not automatically write off the difference or close the invoice merely because cash was sent; otherwise both the liability and supplier relationship can be misstated.

38. How do you correct an invoice posted to the wrong expense account?

Use an authorized correction that preserves the original transaction and audit trail, with the appropriate period and dimensions. If a $900 invoice was charged to office supplies instead of repairs, a reclassification may be Dr Repairs expense $900 / Cr Office supplies expense $900, leaving AP unchanged. If tax, entity, asset capitalization, or supplier data is also wrong, a simple reclassification may not be sufficient; reversal and re-entry through the subledger may be required. Check whether the period is closed and obtain the necessary approval. Never delete supporting evidence or create a second payable just to repair coding.

39. Which basic AP metrics are useful for an analyst?

Useful metrics include invoice cycle time, on-time payment rate, exception aging, first-pass processing rate, duplicate-payment incidents, and unreconciled balances. Define the start, end, population, and exclusions before comparing results. For example, cycle time from invoice receipt to approval should not silently exclude time spent in a shared mailbox. Track both volume and value: a small count of high-value failures may matter more than many minor corrections. Metrics should drive investigation and ownership, not encourage hiding disputed invoices or paying unsupported documents to improve a dashboard. Pair efficiency measures with control-quality measures.

40. What checks should you perform before marking an invoice as paid?

Confirm the payment is linked to the correct invoice and that the relevant payment outcome supports the status. Check amount, currency, payee, applied credits or discounts, and bank or payment-provider result, then reconcile remaining open items. An ERP entry or generated file alone may represent only an instruction. For example, a rejected bank file can leave an invoice incorrectly shown as settled unless the payment is reversed or reopened through the controlled process. Retain the reference needed to trace funds and distinguish paid, sent, pending, and failed statuses. That separation helps prevent accidental duplicate resubmission.

Accounts Payable Interview Questions and Answers for Intermediate

The intermediate answers show how to investigate discrepancies and preserve a consistent accounting trail. Worked amounts state their assumptions; real tax, valuation, and period decisions require the applicable policy.

41. How would you resolve a quantity mismatch on a partially received PO?

Reconcile cumulative ordered, received, returned, and invoiced quantities before deciding what is payable. Suppose a PO covers 200 units, receipts show 120, and an invoice bills 150. Ask receiving whether 30 units are genuinely missing or only unrecorded, and check whether earlier invoices already consumed part of the receipt. Do not create a false receipt to clear the hold. If only 120 were received, obtain a corrected invoice, approved partial-payment arrangement, or other documented resolution. Track the remaining order separately so later receipts and invoices do not reuse quantities already matched or paid.

42. How would you investigate an invoice price above the PO price?

Determine whether the difference is a supplier error, an authorized contract change, a unit-of-measure issue, or an incorrectly captured charge. For 80 units invoiced at $27 against a $25 PO, the difference is $160, or 8% of the $2,000 PO value for those units. Compare that with the configured tolerance and approval policy, but do not treat a tolerance as permission to ignore an unauthorized change. Procurement should substantiate any agreed increase. Correct the source record or obtain a credit as appropriate, retain the approval, and rerun validation rather than quietly overwriting the invoice amount.

43. How should freight and other additional charges be handled during matching?

Separate legitimate contractually supported charges from capture errors or unapproved additions, then allocate them according to the accounting policy and ERP design. A $300 delivery charge may require a distinct PO charge, a purchasing approval, and allocation to inventory cost rather than a generic expense. Verify whether freight is included in the unit price before adding it again. Matching rules for charges can differ from line-price rules, so a passing unit-price check does not prove total invoice validity. Document the allocation basis and tax treatment, and avoid spreading an unexplained variance across lines merely to stay below tolerance thresholds.

44. How do unit-of-measure differences cause invoice exceptions?

An invoice may price a case, pack, kilogram, or service hour while the PO and receipt use another unit. Compare the conversion and price basis before concluding that the supplier overbilled. If one case contains 12 units and the PO is $5 per unit, a case price of $60 is consistent; treating it as $60 per unit would overstate cost twelvefold. Validate conversion master data and actual delivered quantities, particularly when pack sizes change. Corrections should preserve the commercial document and approved mapping. Do not force quantities to match without checking the resulting inventory quantity and valuation.

45. How would you control service invoices without physical goods receipts?

Require evidence that the service or milestone was performed, approved by someone able to assess it. Depending on the contract, evidence might include accepted deliverables, approved hours, a service-entry record, or confirmation of coverage for a recurring service. A consulting invoice for 60 hours should be checked against authorized rates and approved work, not simply the remaining PO balance. Separate the person benefiting from the service from final payment release where practical. If acceptance is disputed, track the exception and assess period-end recognition separately; a warehouse-style receipt should not be fabricated to make a service invoice pass.

46. How do you process an invoice when only part of the amount is disputed?

Identify the undisputed obligation and disputed portion, then use an approved method that preserves both the accounting and the payment restriction. For a $10,000 invoice with a supported $1,500 dispute, the business may authorize paying $8,500 while holding the remainder, subject to the contract and local requirements. Use installments, line-level holds, or another supported ERP method rather than editing the supplier’s invoice to pretend it was always smaller. Maintain the dispute reason, evidence, owner, and review date. Evaluate whether the full liability or an adjusted amount should be recognized under the applicable accounting assessment.

47. How should a supplier credit be applied across multiple invoices?

Apply it according to the credit’s commercial purpose and the agreed settlement rules, retaining clear links to the affected invoices. Suppose a $600 credit relates to two price adjustments of $250 and $350. Allocate those amounts to the relevant open items rather than allowing the payment run to pay both invoices in full. Check currency, entity, tax consequences, and any restrictions on cross-site settlement. If the originating invoices are already paid, seek a refund or an agreed application to future purchases. An unused credit is an asset-recovery issue, not a reason to create an unsupported negative payment.

48. How would you account for an advance paid to a supplier?

An authorized advance for future delivery generally uses a supplier-advance or prepayment account until the related goods or services are recognized. In a simplified $4,000 example, paying the advance is Dr Supplier advances $4,000 / Cr Cash $4,000. A later $10,000 recognized invoice credits AP for $10,000, with the debit based on the purchase. Applying the advance is Dr AP $4,000 / Cr Supplier advances $4,000, leaving $6,000 payable. Confirm contract rights, recoverability, tax timing, and ERP treatment. Reconcile advances by supplier and agreement so they are neither expensed prematurely nor forgotten when final payment is prepared.

49. How do you calculate and record an early-payment discount?

First verify the eligible base, contractual deadline, and supplier entitlement. For an eligible $8,000 invoice with a 2% discount, the reduction is $160 and cash paid is $7,840. Under a simplified gross-recording example, settlement is Dr AP $8,000 / Cr Cash $7,840 / Cr the appropriate purchase-cost adjustment $160. The account credited depends on the underlying purchase and applicable accounting policy; it is not universally other income. Tax adjustments and inventory costing can complicate the entry. Ensure the payment can actually meet the terms, and do not take a discount merely because the ERP still displays one.

50. How would you compare an early-payment discount with financing cost?

Compare the discount earned with the incremental cash committed and the number of days payment is accelerated, then consider liquidity and execution risk. For 2/10 net 30, paying $9,800 instead of $10,000 saves $200 for advancing cash by 20 days. A simple 365-day annualized equivalent is (200 / 9,800) × (365 / 20), about 37.24%; it is not a guaranteed investment return or an effective compounded yield. Compare that with the relevant marginal funding cost and cash constraints. Treasury approval, eligibility, supplier reliability, and bank timing still determine whether taking the discount is sensible.

51. How do you build a short-term cash forecast from AP data?

Start with validated open invoices by expected payment date, then adjust for approved holds, credits, discounts, payment calendars, and known unbilled commitments. Keep recorded liabilities separate from forecasts of future receipts or services to avoid double counting. If next week’s due invoices total $120,000, applicable credits are $8,000, and an authorized $12,000 payment is deferred, the base outflow is $100,000 before other adjustments. Confirm funding and foreign-currency assumptions with treasury. Reconcile forecast versus actual payments and explain whether differences arose from invoice timing, business decisions, bank cutoffs, or missing data rather than merely overwriting the next forecast.

52. How would you reconcile AP to the GL at month end?

Use a consistent cutoff, entity, ledger, account set, and currency basis, then compare the subledger’s accounted balance with the GL control accounts. Reconcile the roll-forward: opening liability plus posted invoices, less credits and settlements, plus or minus other legitimate adjustments. For example, $250,000 + $90,000 − $15,000 − $100,000 equals $225,000 before FX or other movements. Investigate differences by accounting event and journal source, including untransferred entries and direct GL postings. Do not assume one vendor aging report contains the same population as the GL. Retain a signed reconciliation with explained, aged differences and named resolution owners.

53. What would you do if a payment appears in the bank but not in AP?

Trace the bank transaction to its payment instruction and accounting record before creating another payment. Check manual wires, bank fees, interface failures, wrong entity postings, and unallocated cash-clearing entries. If a genuine $7,500 supplier payment bypassed normal AP posting, obtain authorization evidence and record or complete the appropriate settlement through the approved process, ensuring the original invoice is cleared once. If the payee is unknown, escalate immediately rather than forcing it against a convenient invoice. Reconcile both the bank and AP consequences; correcting only one side can leave an invoice available for duplicate payment.

54. How would you handle a rejected or returned electronic payment?

Identify the bank’s rejection or return reason and establish whether funds ever settled before reversing or retrying. Preserve the original payment reference and verify any replacement banking details through the normal change process. Reopen or reverse the AP settlement using the supported ERP workflow, account for legitimate fees, and create a separately authorized replacement only after the payment state is clear. A returned payment can be different from a file rejected before processing, so accounting may differ. Inform the supplier of a realistic timeline and retain the linkage between original, reversal, and replacement to prevent duplicate disbursement.

55. What is the correct response to a lost supplier check?

Investigate the check’s status with treasury and the bank before issuing a replacement. Confirm the supplier’s identity, check number, amount, and whether the check has cleared; initiate an authorized stop-payment process where appropriate. A request alone is not proof the original cannot still be paid. Once the bank and internal procedures support replacement, void or reverse the original through the ERP and issue a linked new payment. Document fees and approvals. If the check was cashed unexpectedly, escalate as a possible fraud or misapplication issue rather than treating it as a routine reprint.

56. How do you investigate old debit balances in supplier accounts?

Break each debit balance into its underlying transactions and determine whether it is an advance, duplicate payment, unapplied credit, refund due, or posting error. Contact the supplier through verified channels and reconcile the balance to contracts and statements. For example, a $2,200 debit left after a duplicate payment may require a refund request rather than indefinite netting against unrelated invoices. Evaluate collectibility, reclassification, and any write-off with the controller under applicable policy. Do not use a blanket aging cutoff to erase balances. Track recovery ownership and prevent further payments when usable credits or advances should first be considered.

57. How would you prepare a reliable month-end accrual for uninvoiced services?

Use evidence of services received, the relevant period, and a supported estimate, then reconcile that estimate to later invoices. For a contract priced at $120 per accepted hour with 35 unbilled September hours, an illustrative accrual is $4,200: Dr Service expense / Cr Accrued liabilities. Exclude hours already invoiced or covered by another accrual. Record the estimate’s source, preparer, approver, and reversal or clearing method. A vendor’s annual contract ceiling is not the same as work performed. Review large estimate-to-actual differences afterward so the accrual process improves rather than repeatedly carrying unsupported round amounts.

58. How do you prevent an accrual and a later invoice from duplicating expense?

Link the invoice to the original accrual and use either a controlled reversal-and-invoice method or a direct clearing method, consistently. Suppose September accrued $4,200 and October receives a $4,350 invoice for that same work. Under a direct-clearing example, Dr Accrued liabilities $4,200, Dr Expense adjustment $150, and Cr AP $4,350. The controller determines the appropriate period for the $150 difference, considering the close status and accounting requirements. If the accrual automatically reversed, do not also clear it a second time. Reconcile the accrual schedule to the ledger and preserve the invoice-to-estimate linkage.

59. How do you investigate an aged GRNI balance?

Analyze receipts, invoices, returns, valuation differences, and reversals at PO-line level rather than clearing the net account balance. A receipt may remain unmatched because the invoice went to a non-PO expense account, the supplier never invoiced, or the receipt was entered twice. Confirm whether the goods were actually received and whether the obligation remains. For a $3,000 receipt with a valid invoice incorrectly expensed elsewhere, repair the accounting and matching chain rather than write off GRNI into income. Use authorized adjustments, document the evidence, and separate genuine price or FX variances from operational errors.

60. How should AP handle an invoice received after the reporting period closes?

Determine when the underlying goods or services were received and whether the obligation was already recorded. A late invoice is evidence about the transaction, not automatic permission to post it to either the old or new period. Check existing accruals and materiality, then involve the controller if an adjustment to closed-period or reporting figures may be needed. For example, a January invoice for December services should be compared with December’s accrual rather than simply treated as January expense. Preserve the actual invoice date and follow controlled reopen or adjustment procedures; never backdate documents to conceal the late discovery.

61. How do you record and remeasure a foreign-currency payable?

Record the transaction using the rate required by the applicable framework and remeasure an unpaid monetary payable at the appropriate reporting-date rate. In a simplified USD-functional-currency example, a €10,000 invoice at $1.10 per euro creates $11,000 of AP. At a closing rate of $1.12, the liability becomes $11,200, producing a $200 exchange loss: Dr FX loss $200 / Cr AP $200. This is an ordinary unhedged payable example, not a rule for every foreign operation or advance. Verify the rate source, date, functional currency, and framework-specific exceptions; do not retranslate the original expense automatically alongside the payable.

62. How do you calculate the exchange difference when a foreign payable is settled?

Compare the functional-currency cash cost of settlement with the payable’s carrying amount immediately before settlement, accounting separately for fees. Continuing a €10,000 payable carried at $11,200, payment at $1.11 per euro costs $11,100. The simplified entry is Dr AP $11,200 / Cr Cash $11,100 / Cr FX gain $100. Combined with the earlier $200 remeasurement loss, the net exchange loss from the original $11,000 recognition is $100. Confirm how the ERP reverses or retains earlier revaluation entries so the gain is not counted twice. Hedging, multiple currencies, and bank spreads require additional analysis.

63. How would you review US information-reporting data before year end?

Reconcile supplier classifications and payment populations with the tax team’s current reporting rules, then investigate missing identifiers, inconsistent legal names, and excluded transactions. Separate payment date from invoice date and identify refunds, withholding, and payments processed through channels that may have different reporting responsibilities. Do not assume every vendor or every AP expense belongs on Form 1099-NEC. Use the instructions for the payment year, including current thresholds, exceptions, and correction procedures. Run exception reviews before the filing deadline so suppliers can resolve documentation issues. A spreadsheet export is not sufficient unless its scope reconciles to the underlying payment records.

64. How should AP handle US backup withholding when it applies?

AP should follow a tax-approved determination, withhold the required amount, remit it through the proper process, and retain reporting evidence. IRS guidance identifies a current 24% backup-withholding rate for covered circumstances; it is not a universal deduction from all vendor payments. For a fully subject $1,000 payment, a simplified settlement is Dr AP $1,000 / Cr Cash $760 / Cr Withholding tax payable $240. Later remittance clears that tax payable. Verify the triggering documentation, exemptions, notices, timing, and reporting with tax specialists. Never keep the withheld amount as company income or confuse backup withholding with foreign-payee withholding rules.

65. What should AP do when a US supplier invoice has no sales tax?

Check whether the purchase is taxable in the relevant jurisdiction and whether the supplier’s omission creates a purchaser use-tax obligation. For example, California guidance addresses taxable out-of-state purchases used in California when the seller has not collected the applicable tax. That does not mean all US services or all tax-free invoices are taxable. Identify delivery and use location, product category, exemptions, and any tax already paid, then apply the approved tax treatment. A hypothetical $2,000 taxable base at an assumed 6% rate would create $120 of tax, but the actual jurisdictional rate and base must be verified.

66. How do you distinguish recoverable input VAT from a supplier payment obligation?

The supplier payable is generally the gross amount owed, while eligible input VAT may be recorded separately as recoverable tax. For an illustrative fully eligible £1,000 net purchase plus £200 VAT, the entry is Dr Expense or asset £1,000 / Dr VAT recoverable £200 / Cr AP £1,200. The 20% rate and full recovery are assumptions, not universal rules. In the UK, valid supporting invoices and eligibility matter, and partial exemption or scheme-specific restrictions may change recovery. If VAT is not recoverable, the debit treatment follows the relevant cost policy. Payment approval and tax-recovery approval are related but distinct controls.

67. How do you diagnose an ERP invoice that will not validate?

Read the specific validation messages and inspect the affected records before changing configuration. Check distribution totals, account combinations, tax setup, currency rates, period status, matching details, and approval requirements. In Oracle Fusion Payables, some holds prevent accounting as well as payment, and some require correction and revalidation rather than manual release. For example, an invalid distribution account should be repaired through the approved account selection, not bypassed with an arbitrary suspense account. Retain the error and resolution evidence, rerun validation, and confirm the resulting status. A generic “system issue” explanation is inadequate if the cause is a legitimate control.

68. Why might an approved invoice be missing from a payment proposal?

Approval is only one eligibility condition. Check due and discount dates, payment holds, vendor or site status, currency, method of payment, selection filters, minimum or maximum amounts, existing settlement marks, and available credits. In Dynamics 365 Finance, payment proposals use configurable selection criteria; a date range can exclude an otherwise valid invoice. Reproduce the selection using the same parameters before making changes. If an invoice is already included in another pending run, adding it manually elsewhere risks duplication. Document the root cause and obtain approval for any exception rather than removing filters broadly to make one invoice appear.

69. How would you improve duplicate detection beyond exact invoice numbers?

Combine exact checks with normalized identifiers and risk-based comparisons of supplier identity, amount, currency, date, PO, and invoice image. Preserve the original number while using a separate normalized comparison that handles spaces, punctuation, or predictable prefixes. Test for duplicates across supplier aliases and intake channels, including unposted invoices, not just the posted ledger. A $4,500 invoice submitted by email and portal may have different filenames but the same obligation. Route probable matches to review because recurring invoices can share amounts. Measure false positives and missed duplicates; do not automatically reject every similar record or weaken native preventive controls.

70. What controls are needed for recurring invoices and templates?

A recurring template needs an approved agreement, correct period, amount logic, account coding, end date, and periodic owner review. It should not silently continue after a contract ends or overlap with separately submitted supplier invoices. For example, a monthly software subscription template should be checked when user counts, pricing, or renewal terms change. Maintain unique invoice references and reconcile expected periods with actual postings. Template creation and amendment should be controlled separately from ordinary processing, with audit history. Automation saves data entry, but it does not prove that the service remains necessary, was delivered, or is still authorized.

71. How do you validate invoices captured by OCR or AI?

Validate extracted fields against the source image and authoritative master or transaction data, using risk-based thresholds and exception review. Check supplier, legal entity, invoice number, currency, dates, line amounts, and bank details particularly carefully. An extraction confidence score measures a model’s estimate, not commercial validity or approval. For example, reading EUR as USD can produce internally consistent arithmetic but the wrong liability. Keep the source document, extraction version, edits, and reviewer evidence. Do not let text embedded in an invoice change workflow rules or authorize payment; treat document content as untrusted business data, not operational instructions.

72. What should an AP approval workflow do when the usual approver is absent?

Use a documented delegation or escalation path that retains appropriate authority and segregation of duties. Confirm the substitute’s approval limit, responsibility for the cost center, and effective dates. A request waiting on vacation should not automatically route back to the invoice preparer for self-approval. Record the delegation and decision in the system rather than relying on an unverifiable verbal instruction. For urgent valid invoices, use an authorized exception process with evidence and subsequent oversight. Review aging queues to identify bottlenecks early, but do not replace meaningful business review with automatic approval merely to meet cycle-time targets.

73. How should AP process employee expense reimbursements without duplicate supplier payments?

Define which channel owns the obligation and cross-check expenses that may also appear in supplier invoices or corporate-card feeds. An employee who personally paid a $300 hotel bill should not be reimbursed if the company already paid the same stay directly. Verify the business purpose, receipt, payment method, approval, and tax treatment under the expense policy. Separate employee reimbursements from ordinary supplier onboarding where the systems require different controls. If a duplicate is found, correct the appropriate channel and preserve the trail. Reconciliation across AP, expenses, and cards matters more than each system’s isolated duplicate check.

74. How do corporate-card purchases affect AP reconciliation?

Corporate-card activity can create obligations to the card issuer while individual receipts establish the nature of the underlying purchases. Reconcile the statement, card feed, employee coding, credits, and payment to the issuer without recording both each merchant invoice and the card settlement as separate expenses. For example, a $600 equipment purchase already captured through the card feed should not also generate an ordinary supplier payment. Investigate disputed charges and late credits separately. The precise clearing accounts depend on the setup, but the control objective is consistent: one recognized purchase, one correct issuer liability, and no duplicate cash disbursement.

75. How would you manage a supplier dispute that threatens a critical service?

Separate the operational continuity decision from the accounting and payment-control decision. Confirm the disputed facts, assess the service risk with the business owner, and involve procurement, treasury, or legal as appropriate. A temporary payment arrangement may be justified, but it needs explicit authority, documented terms, and a plan for recovery or resolution. Do not tell the supplier a disputed amount has been approved when it has not. Track the disputed and undisputed balances independently and keep forecasts current. Escalation should accelerate a controlled decision, not pressure AP to create false receipts or bypass banking verification.

76. How can AP support a search for unrecorded liabilities?

Provide evidence from subsequent payments, late invoices, supplier statements, open receipts, service confirmations, and unmatched or held documents. Trace relevant items back to the period when the goods or services were received and identify amounts already accrued. A payment made after year end can relate to either an old obligation or a new-period purchase, so payment date alone does not decide cutoff. Keep the population and selection method reproducible and route findings to the controller or auditors as appropriate. This work complements, rather than replaces, ordinary subledger reconciliation because an omitted liability may not appear in either AP or the GL.

77. How would you calculate an AP on-time payment rate fairly?

Define the unit of measurement, contractual due date, settlement event, and exception rules before calculating the rate. If 920 of 1,000 invoices due in a period met the agreed payment deadline, the invoice-count rate is 92%. A value-weighted result may differ, so label it separately. Do not improve the metric by changing due dates after the fact or removing difficult invoices without disclosure. Report disputed and legally blocked items as transparent categories rather than silently excluding them. Consider bank holidays, terms defining receipt versus initiation, and data completeness so the metric measures actual performance rather than convenient system statuses.

78. What is days payable outstanding, and what are its limitations?

Days payable outstanding estimates how long the business takes to pay for purchases using a defined payable balance and cost or purchase denominator. A common approximation is average trade AP divided by period cost of goods sold, multiplied by days in the period, but credit purchases may be a better aligned denominator when available. With average AP of $300,000 and annual relevant purchases of $3,650,000, a 365-day measure is 30 days. State the formula and scope. Seasonality, nontrade balances, inventory movements, and supplier financing can distort comparisons; a higher DPO is not automatically healthier or evidence of better AP execution.

79. How would you reconcile intercompany invoices handled by AP?

Match the counterparty, legal entities, currency, invoice reference, accounting period, and amount with the other entity’s records. Investigate timing, tax, FX, markup, and settlement differences before period close. If one entity records a $20,000 payable while the other records $18,000 receivable, determine whether a credit, missing charge, or wrong rate explains the gap rather than inserting an unexplained adjustment. Intercompany netting requires an approved process and should preserve gross transaction traceability. Consolidation eliminations do not excuse inaccurate local books. Coordinate with the intercompany accounting team because transfer pricing, tax, and legal documentation may sit outside AP’s authority.

80. How would you organize and resolve an AP exception backlog?

Classify exceptions by cause, value, age, payment urgency, and owner, then separate quick data corrections from decisions requiring procurement, receiving, tax, or controller input. Establish service expectations and visible escalation paths instead of repeatedly emailing an undifferentiated list. For example, fifty missing-receipt invoices from one warehouse may indicate a receiving-interface problem rather than fifty unrelated AP mistakes. Track arrivals, resolutions, and reopened items so apparent progress does not hide recirculation. Clear items only with supporting evidence and monitor control outcomes. A backlog reduction achieved by mass hold release or unsupported write-offs is not a successful improvement.

Accounts Payable Interview Questions and Answers for Experienced

The experienced answers focus on risk, evidence, authority, and measurable outcomes. Strong candidates distinguish a useful system feature from an effective end-to-end control and know when specialist judgment is required.

81. How would you design an end-to-end AP control framework?

Map risks to preventive and detective controls across onboarding, intake, matching, accounting, payment, and reconciliation, then assign accountable owners and evidence. For example, supplier-bank verification addresses payment diversion, receipt matching addresses unsupported quantities, and a search for unrecorded liabilities addresses completeness. Test interfaces between controls: an invoice can match correctly yet be paid to a fraudulently changed account. Define access restrictions, exception authority, monitoring, and remediation deadlines. Use the applicable financial-reporting and audit requirements as context rather than assuming one framework fits every business. A control inventory is useful only if it demonstrates operation and addresses the actual transaction population.

82. How would you maintain segregation of duties in a small AP team?

Identify the specific incompatible capabilities and introduce independent approval or monitoring where full separation is impractical. A two-person team may require the owner or controller to verify bank changes and release payments directly in the bank portal, with a separate review of the bank reconciliation. The reviewer needs original evidence and access to change logs, not only a list prepared by the person being reviewed. Restrict shared credentials and emergency access. Document residual risk and reassess as volume grows. Calling a review “compensating” does not make it effective if it occurs too late or cannot detect the relevant unauthorized transaction.

83. How would you investigate suspected vendor-master fraud?

Preserve records and involve the designated fraud, security, legal, and finance owners while limiting further exposure through authorized controls. Review supplier creation and change history, access logs, payment destinations, related approvals, and links to employee or other supplier data where permitted. A shared bank account is a risk indicator, not conclusive proof: legitimate factoring or group arrangements can exist. Avoid alerting suspected participants unnecessarily or altering evidence during investigation. Reconcile affected payments and potential liabilities, document facts separately from hypotheses, and follow incident-response authority for payment holds or recovery. AP should not conduct an improvised accusation-driven investigation.

84. What would you do immediately after discovering a payment-diversion incident?

Escalate through the incident-response chain and contact the bank immediately to request available recall, hold, or recovery actions. Preserve the payment reference, communications, account-change history, approvals, and system logs; coordinate with security to contain compromised access. Use the appropriate reporting process, including US IC3 reporting where relevant, without promising recovery. Verify the real supplier through a trusted channel and stop dependent payments through authorized controls. Accounting must assess the original supplier obligation and any recoverable or loss separately; paying an attacker may not settle the supplier. Do not make an unverified replacement payment simply to make the operational problem disappear.

85. How would you design controls over supplier bank changes and pending payment files?

Control both master-data approval and the payment instruction that will actually reach the bank. Require independent verification and approval, retain before-and-after values, and restrict who can alter approved files or payment journals. Determine whether a bank change updates already-created payments in the specific ERP configuration; never assume it does or does not. Compare high-risk changes with the next payment run and require reapproval when a material destination changes. Invalidate or regenerate stale files through a controlled process when necessary. A fully approved vendor master does not protect funds if someone can later edit the exported payment file without detection.

86. How would you choose invoice matching tolerances?

Base tolerances on transaction risk, purchasing patterns, currency, unit economics, and the cost of investigating legitimate small differences. Separate price, quantity, tax, freight, and cumulative invoice exposure where the system permits. A fixed $50 threshold has a very different effect on a $100 purchase than on a $100,000 purchase. Test absolute and percentage limits, rounding behavior, split invoices, and partial receipts in the actual ERP. Require controlled approval of changes and monitor overrides and repeated near-threshold variances. Tolerances should reduce immaterial noise without converting unauthorized purchasing or systematic overbilling into an accepted cost of automation.

87. How would you detect invoice splitting designed to avoid approval limits?

Analyze related invoices across supplier, requester, date, PO, project, description, and payment destination, not just individual invoice amounts. Three invoices of $4,900 shortly before a $5,000 approval threshold may warrant review, but similar amounts alone do not establish misconduct. Compare the underlying contract or purchase requirement and inspect approval history. Define aggregation rules and escalation responsibility, then test false positives such as genuine phased deliveries. Preventive controls can require approval of the total commitment rather than each bill in isolation. Preserve evidence and apply the organization’s investigation process rather than accusing a supplier or employee based on an analytics flag.

88. How would you build a duplicate-payment recovery program?

Start with a reconciled payment population and risk-based matching across invoice references, suppliers, bank destinations, amounts, currencies, and dates. Validate suspected duplicates against documents and actual bank outcomes before contacting suppliers. Distinguish a true second payment from an authorized installment, reversal, or legitimate recurring charge. Track confirmed recovery claims, supplier acknowledgments, refunds, and applied credits separately; a claim is not recovered cash. Accounting should assess recognition and collectibility under policy. Feed each root cause back into intake, master-data, and payment controls so the program prevents recurrence rather than generating the same recoveries every quarter.

89. What controls are required when AP processing is outsourced?

Retain clear ownership of policy, supplier data, payment authority, exceptions, and financial reporting even if a service provider performs processing. Define access, service levels, evidence retention, data handling, incident notification, and reconciliation responsibilities contractually and operationally. Evaluate relevant assurance reports and their scope, exceptions, periods, and customer responsibilities rather than treating a report’s existence as blanket assurance. For example, if the provider validates invoices but the company owns receipt evidence, that handoff needs a monitored control. Review actual exception quality and payment outcomes, not just turnaround time, and plan how records and access will be recovered on exit.

90. How would you assess whether an AP control is operating effectively?

Check whether the control addresses the stated risk, uses a complete and accurate population, is performed by an appropriate person at the required time, and leaves evidence of meaningful review. For example, a payment-run sign-off should show what was checked and how unusual items were resolved, not merely a timestamp. Sample transactions using a justified method and inspect exceptions, overrides, and follow-through. Evaluate report logic and access as well as the reviewer’s action. A control can be well designed but fail in operation, or run consistently while checking the wrong risk; those require different remediation.

91. How would you distinguish a completeness problem from an AP reconciliation problem?

A reconciliation problem means recorded populations do not agree; a completeness problem can exist even when AP and the GL agree perfectly because both omit the same obligation. If the subledger and GL each show $500,000, that does not establish that all received services are included. Investigate late invoices, receipts, subsequent disbursements, and supplier statements to assess completeness. Conversely, a $10,000 difference caused by an untransferred journal may be a timing or interface issue rather than an unrecorded purchase. Design separate controls for both objectives and avoid presenting a clean reconciliation as proof of every financial-statement assertion.

92. How would you evaluate a material cutoff error discovered before financial statements are issued?

Establish the facts, affected periods, existing accruals, amount, and qualitative significance, then escalate to the controller and relevant reporting or audit team. Determine the appropriate adjustment under the applicable framework and reporting timetable rather than assuming a closed ERP period makes correction impossible. For example, a large invoice for goods controlled before year end may reveal an omitted inventory and liability entry, not merely a late administrative document. Preserve evidence of delivery terms and receipt. Reassess related populations and the failed control, and use authorized adjustment or reopening procedures without manipulating invoice dates or concealing the error.

93. How would you assess whether an old unpaid invoice can be written off?

Require evidence that the obligation has been extinguished, released, invalidated, or otherwise qualifies for derecognition under the applicable framework. Age alone, lack of supplier contact, or a desire to improve earnings is insufficient. Investigate disputes, duplicate records, settlements, supplier dissolution, contractual terms, and legal requirements with the appropriate specialists. An uncashed payment may also trigger jurisdiction-specific unclaimed-property obligations rather than income recognition. Document the conclusion and authorization, retain the original trail, and consider tax implications. If uncertainty remains, maintain or appropriately reassess the liability instead of applying an automatic write-off rule to an aging bucket.

94. How would you distinguish a routine accrual from a provision or contingency?

Start with the nature and uncertainty of the obligation, not the label used in the spreadsheet. Routine accruals often concern goods or services already received with relatively limited estimation uncertainty, while provisions or contingencies may involve materially uncertain timing or amount and framework-specific recognition tests. IAS 37 explicitly distinguishes trade payables and accruals from provisions; US GAAP analysis uses the relevant Codification guidance, not an assumed identical threshold. A normal unbilled maintenance service differs from a disputed damages claim. AP should provide transaction evidence and involve technical accounting or legal specialists rather than independently applying one universal probability rule.

95. How would you account for a supplier rebate that affects purchased inventory?

Identify the contractual entitlement, whether the rebate is earned or estimated, which purchases it relates to, and how the applicable accounting policy allocates it between inventory and expense. A $30,000 rebate is not automatically miscellaneous income simply because a supplier sends a credit memo. Some related inventory may remain on hand while other units have been sold, requiring a supported allocation and later true-up. Confirm tax and settlement treatment and avoid reducing AP before the entitlement is adequately established. Coordinate with inventory and technical accounting teams, and reconcile rebate schedules to credits received so amounts are neither omitted nor recognized twice.

96. What should AP understand about supplier-finance arrangements?

AP must distinguish normal supplier settlement from arrangements in which a finance provider pays suppliers and the buyer later pays that provider. Capture program terms, balances, payment timing, and which obligations have been funded, because classification, cash-flow presentation, and disclosure require technical accounting assessment. IFRS supplier-finance disclosure requirements and US GAAP’s supplier-finance guidance are not interchangeable, and neither makes every arrangement ordinary trade AP. Track the original invoice through confirmation and settlement without duplicating liabilities. Evaluate concentration and liquidity exposure if the program is withdrawn; longer stated payment terms can mask dependency on external financing rather than operational improvement.

97. How would you build an AP cash forecast under financial stress?

Create a reconciled obligation schedule and model authorized scenarios for timing, supplier criticality, legal constraints, discounts, penalties, and financing availability. Distinguish contractual due dates from proposed deferrals so a forecast does not rewrite obligations. For example, show the cash effect of delaying $200,000 separately from service-disruption and late-payment consequences. Include disputed items and expected unbilled costs with explicit assumptions and confidence ranges. Treasury and leadership should approve prioritization; AP should not unilaterally favor suppliers or make promises it cannot fund. Update actual outcomes and communicate reliably with affected suppliers rather than hiding overdue balances to meet a target.

98. How would you explain a rising DPO alongside worsening supplier relationships?

A rising DPO may reflect deliberate negotiated terms, but it may also result from overdue invoices, unresolved exceptions, cash shortages, or denominator changes. Decompose the movement by supplier, category, contractual terms, overdue days, and purchasing volume. If DPO rises while on-time payment falls and service holds increase, the change likely includes operational or liquidity stress rather than only improved working capital. Quantify lost discounts, penalties, and disruption risk alongside cash retained. Confirm metric scope and supplier-finance effects before comparing periods. Recommend targeted fixes or renegotiation rather than celebrating a higher ratio in isolation.

99. How should AP handle foreign-currency advances differently from monetary payables?

Do not assume every foreign-currency supplier balance is a monetary item remeasured like an unpaid invoice. An advance that gives a right to receive goods or services can be nonmonetary, while a refundable cash claim may require different analysis. Under IFRS, the relevant IAS 21 and IFRIC 22 guidance can affect which transaction-date rate applies when advance consideration is involved. Identify the contractual rights, functional currency, dates, and accounting framework before configuring revaluation. Split advances from open invoices where needed and reconcile applications carefully. Escalate unusual refund or exchangeability terms instead of allowing a blanket AP revaluation job to determine policy.

100. How would you control exchange rates used in AP across multiple entities?

Define approved rate sources, rate types, effective dates, ownership, and permitted overrides for initial recognition, remeasurement, and settlement. Confirm each entity’s functional currency and distinguish it from invoice and reporting currencies. Reconcile imported rates for missing values, inverted quotations, and unusual changes; a USD-per-EUR rate cannot be used as EUR-per-USD without conversion. Restrict manual overrides and retain reasons and approval. Test whether the ERP’s revaluation reverses prior entries or adjusts the carrying balance cumulatively. Specialized issues such as lack of exchangeability or hedges require technical accounting input, not an arbitrary substitute rate chosen by the processor.

101. How would you prevent duplicate payments after an integration timeout?

Treat a timeout as an uncertain outcome, not proof that the payment failed. Use a durable business reference, supported idempotency controls where available, and bank or payment-provider status reconciliation before retrying. If the ERP loses the response after sending a $50,000 instruction, first establish whether that reference was accepted or settled. Do not create a fresh reference and resend blindly. Design explicit states for submitted, acknowledged, rejected, settled, and unresolved instructions, with authorized ownership of reconciliation. Integration reliability requires both technical retry logic and business-state evidence; a successful HTTP response alone is not settlement, and a failed response is not nonpayment.

102. What should be tested before migrating open AP balances to a new ERP?

Test supplier and site mapping, invoice identity, currencies, due dates, holds, credits, advances, payment status, and accounting dimensions, then reconcile counts and amounts to the approved cutover population. Preserve enough history to detect duplicates and explain opening balances. A $1 million control total can agree even if invoices are assigned to the wrong suppliers, so validate transaction-level details and stratify high-risk samples. Define which system owns payments during cutover and prevent both from selecting the same invoice. Rehearse reconciliation, rollback, and audit retrieval before go-live; migration success is not merely a file import with no technical errors.

103. How would you test a change to AP payment configuration?

Build representative scenarios for due dates, discounts, holds, credits, partial payments, currencies, legal entities, bank changes, and rejection handling, with expected accounting and bank outputs. Include negative tests proving ineligible invoices remain excluded and unauthorized users cannot release payments. Compare file totals and beneficiary data with approved proposals in a safe test environment. A configuration change that fixes one supplier may alter every payment method using the same rule. Require documented approval, controlled deployment, and post-change reconciliation. Do not send live test payments without explicit authority, and distinguish test-file validation from actual end-to-end bank settlement testing.

104. How would you govern straight-through invoice processing?

Define eligibility based on stable supplier data, supported receipt or service evidence, acceptable matching results, reliable coding, and appropriate risk limits. Keep high-risk changes and exceptions in human review, and monitor the entire processed population with detective controls. An invoice can be extracted accurately and still be unauthorized, so model confidence should not replace purchasing authority. Measure false approvals, missed duplicates, overrides, and financial impact alongside automation rate. Use controlled rule changes and representative testing. The goal is safe low-touch processing with traceable decisions, not maximizing a percentage by excluding difficult invoices from the denominator or disabling useful checks.

105. How would you manage AP operations during an ERP outage?

Activate a preapproved continuity process that preserves authorization, supplier verification, unique transaction references, and a durable log for later reconciliation. Restrict emergency payments to justified cases and use bank controls that remain effective without the ERP. Before paying a critical supplier manually, check the last reliable open-item and payment records to reduce duplication risk. After restoration, reconcile every manual action and record the correct accounting exactly once before normal runs resume. Do not maintain an uncontrolled parallel ledger indefinitely. Exercise the procedure beforehand, including access, approvals, evidence storage, and the point at which ordinary processing can safely restart.

106. How would you make AP analytics reliable enough for control decisions?

Establish data lineage, reconciled source populations, explicit definitions, and repeatable transformations before trusting a dashboard. Check canceled invoices, reversals, payment attempts, partial settlements, currency conversions, and entity filters. A table with one row per invoice line can overstate payment counts if joined to header totals without aggregation. Reconcile outputs to known control totals and inspect edge cases manually. Version analytical rules and document exclusions, then monitor data freshness and missing feeds. Treat a fraud score or anomaly flag as an investigative lead, not proof. Control decisions require trustworthy inputs and accountable resolution, not only visually persuasive charts.

107. How would you design AP access reviews and privileged-access controls?

Review effective capabilities across the ERP, supplier portal, integration tools, and bank platform, including inherited roles and service accounts. Focus on incompatible combinations, dormant users, emergency privileges, and the ability to alter logs or payment files. A user may appear read-only in AP while retaining bank-release authority elsewhere. Require business-owner certification supported by role detail and recent changes, then verify that removals actually took effect. Restrict and monitor privileged access with time-bounded approval where possible. Periodic review complements joiner, mover, and leaver controls; it should not be the first opportunity to remove access after someone changes responsibilities.

108. How would you reduce AP processing costs without weakening controls?

Measure cost drivers by process stage and exception type, then remove avoidable rework through better supplier intake, PO quality, receipt timing, master data, and workflow ownership. A high cost per invoice may come from repeated missing receipts rather than slow data entry. Pilot changes with clear control-quality metrics, including duplicate payments, unsupported overrides, and reconciliation differences. Avoid savings claims based only on headcount reduction while work shifts unnoticed to procurement or suppliers. Retain appropriate review for high-risk transactions and improve low-risk automation. The strongest business case links lower effort to fewer defects, faster resolution, and demonstrably preserved authorization.

109. How would you design AP responsibilities in a shared-service center?

Define which activities are centralized and which remain with local entities, including tax decisions, service acceptance, bank authority, and statutory reporting. Establish clear handoffs, service levels, escalation paths, and evidence standards. For example, the center can capture and validate invoices, but a local business owner may still need to confirm that a site-specific service was delivered. Maintain entity and currency segregation even when suppliers are shared. Track end-to-end outcomes rather than allowing each team to report success while invoices stall between them. Local legal requirements should inform the design without becoming an excuse for undocumented exceptions to every standard process.

110. How would you assess a global e-invoicing rollout from an AP perspective?

Start with country-specific legal requirements, affected entities and transaction types, required formats or clearance processes, and the distinction between legal receipt and ERP posting. Map validated invoice identifiers, corrections, cancellations, tax data, and attachments into AP with duplicate protection across old and new channels. Test rejected and delayed documents as well as the happy path. Do not assume a PDF emailed to AP satisfies every jurisdiction’s e-invoicing rules or that government clearance proves commercial approval. Tax and legal teams should verify current local mandates; AP owns accurate intake, exception routing, accounting integration, and payment controls within that framework.

111. How would you investigate a clean AP reconciliation with an unexpectedly large expense increase?

Reconciliation proves recorded balances agree, not that expense classification, cutoff, or transaction validity is correct. Analyze the increase by supplier, account, period, entity, and transaction type, looking for duplicated accruals, reversed prepayments, miscoded assets, or unusual invoices. Compare with purchasing activity and business explanations. For example, an annual software invoice expensed immediately instead of following the approved prepaid schedule can inflate the month while AP still reconciles exactly. Confirm whether the accounting treatment is actually wrong before adjusting it. Link corrections to source transactions and assess related populations rather than making a top-side entry solely to restore the expected trend.

112. How would you diagnose payment complaints when the ERP shows invoices as settled?

Trace the entire chain from invoice allocation through payment creation, bank acknowledgment, settlement, remittance, and supplier application. Check wrong bank destinations, rejected files, partial payments, currency differences, and allocation to a different supplier site. An ERP settlement may clear an invoice against an unapplied credit or a payment journal without proving the supplier received cash. Obtain bank evidence and reconcile the supplier statement before retrying. If the payment went to an unauthorized account, escalate as an incident rather than a routine delay. Report the confirmed state and next action, avoiding a blanket “our system says paid” response.

113. What would you do if management asked you to delay recording valid invoices to improve results?

Explain that payment timing and recognition timing are different decisions, and refuse to omit valid liabilities or expenses merely to achieve a target. Establish the facts and applicable policy, document the request appropriately, and escalate through the controller, compliance, or other designated reporting channels if pressure continues. A company may negotiate later payment, but that does not erase goods or services already received. Consider whether uninvoiced or held items also require recognition. Do not secretly alter records or accuse people without evidence; preserve an accurate audit trail and seek a properly authorized accounting conclusion rather than following an unsupported instruction.

114. How would you handle a request to bypass AP controls for an executive’s urgent payment?

Verify the business need and use the approved emergency process, retaining independent supplier verification, appropriate authorization, and payment evidence. Seniority does not authenticate a request or remove fraud risk. An urgent message from a purported executive demanding secrecy and a new beneficiary is especially important to verify through trusted channels. If required controls cannot be completed, escalate the specific blocker rather than inventing approval or fabricating documents. Record the exception and arrange the required subsequent review. A well-designed emergency path is faster because responsibilities are predefined, not because it abandons the controls protecting company funds.

115. How would you resolve repeated late payments caused by missing receipts?

Measure where and why receipts are delayed, then work with receiving and business owners to fix the upstream process. Compare physical delivery or service completion with receipt-entry dates, interfaces, responsibilities, and approval workload. A recurring failure at one site may need training or an integration repair; a service category may need a better acceptance workflow. Do not have AP create blanket receipts just to release invoices. Track improved receipt timeliness, exception age, and payment performance together, while monitoring false receipts and overrides. Sustainable improvement removes the cause of the hold rather than teaching staff to bypass it.

116. How would you evaluate an AP automation vendor’s business case?

Use your actual invoice mix, exceptions, systems, entities, and control requirements to test the claimed benefit. Ask for a representative pilot covering poor-quality documents, duplicates, partial receipts, credits, taxes, currencies, and bank-change requests, not only clean invoices. Compare total cost, implementation effort, support, security, auditability, integration failure handling, and exit options. Define how accuracy and touchless processing are measured and what human work remains. A high extraction score does not establish payment safety or accounting correctness. Require evidence that the solution improves outcomes without creating opaque decisions or shifting unresolved work into another team’s inbox.

117. What should an AP leader include in a monthly management review?

Present reconciled balances, overdue and held items, payment performance, cash requirements, supplier risks, control exceptions, and progress on root-cause fixes. Separate trends from one-off events and disclose data limitations. For example, a lower backlog accompanied by more manual hold overrides is not an unqualified improvement. Include aged credits and advances, GRNI issues, duplicate incidents, bank-change exceptions, and forecast accuracy where relevant. Assign decisions and owners rather than delivering a dashboard without action. Tailor detail to the audience while keeping traceability to underlying records so material changes can be explained and challenged.

118. How would you prioritize AP improvements during your first 90 days?

First establish whether cash, supplier obligations, access, and reconciliations are under control; then use evidence to prioritize process improvements. Review critical overdue items, unexplained balances, bank-change controls, payment failures, and close readiness before optimizing cosmetic metrics. Map the end-to-end workflow with procurement, receiving, treasury, and tax, and identify a small set of measurable fixes. For example, stabilizing a broken receipt interface may outperform a broad OCR rollout. Agree owners, baseline measures, and success criteria, deliver controlled changes, and reassess residual risk. The plan should reflect the organization’s actual problems, not a generic promise to automate everything immediately.

119. How would you assess an AP candidate using a practical invoice scenario?

Give the candidate a realistic invoice, PO, receipt, supplier record, and short payment history, then ask what they would record, hold, verify, and escalate. Introduce a changed assumption, such as a partial receipt or recently changed bank account, to test reasoning rather than memorized terminology. Look for a clear distinction between recognition, approval, and payment, plus balanced journal entries and documented ownership. A strong candidate should identify missing evidence without inventing facts and explain when tax or technical accounting expertise is needed. Score the decision process consistently, not just whether they recite a preferred ERP navigation path.

120. How would you resolve a combined receipt, credit, bank-change, and cutoff exception?

Separate the issues and preserve one coherent transaction trail. Suppose 100 units at $50 were ordered, 80 were received before month end, and the supplier invoiced $5,000 while offering a $1,000 credit for the undelivered portion and requesting new bank details. Verify receipt and contractual recognition, obtain the valid credit, and ensure the supported net invoice amount is $4,000, subject to tax and existing receipt accruals. Resolve cutoff without duplicating GRNI or expense, and independently verify the bank change before payment. Keep the remaining 20-unit order position accurate. Neither an agreed credit nor an urgent due date eliminates the other controls.

Accounts Payable Documentation and Further Reading

Use these primary references to check the applicable accounting framework, jurisdiction, and installed ERP behavior. Product documentation is not accounting authority, and an accounting framework does not replace local tax rules. The Oracle release labels are intentional; confirm your own version and configuration.

• Microsoft Dynamics 365 Finance: Accounts payable invoice matching overview

• Microsoft Dynamics 365 Finance: Vendor invoices overview

• Microsoft Dynamics 365 Finance: Create vendor payments using a payment proposal

• Oracle Fusion Cloud Financials 26C: Types of holds

• Oracle Fusion Cloud Financials 26A: Payables Trial Balance Report

• IRS: Instructions for the Requester of Form W-9

• IRS: Backup withholding

• California CDTFA: Use tax for businesses and individuals

• HMRC: Reclaim VAT on business expenses

• IFRS Foundation: IAS21 The Effects of Changes in Foreign Exchange Rates

• IFRS Foundation: IFRIC22 Foreign Currency Transactions and Advance Consideration

• FASB: Accounting standards and the Codification

• PCAOB: AS2201, Audit of Internal Control Over Financial Reporting

• FBI: Business Email Compromise

• IFRS Foundation: Supplier-finance transparency and disclosures