Payment Runs Interview Questions & Answers

Q: How are supplier credits and deductions applied within a payment run?

Open credit notes and agreed deductions for the vendor are netted against that vendor's due invoices so only the net is paid. The remittance shows the credits applied. If credits exceed invoices due, the balance carries forward until enough invoices exist or a refund is requested from the supplier.

Q: What is the journal entry when invoices are paid in a payment run?

Paying invoices debits accounts payable (reducing the liability) and credits cash/bank. If an early-payment discount is taken, the discount is credited to a purchase discount or expense-reduction account so only the net cash leaves. This clears the specific invoices selected in the run.

Q: How do you reconcile a payment run to the bank and the ledger?

After a run, agree the total of the bank payment file to the AP clearing postings and to the cash leaving the bank account. Investigate rejected/returned payments (e.g., closed accounts), re-issue as needed, and ensure each cleared item matches an open payable now cleared. This ties the sub-ledger, GL, and bank together.

Q: What is the difference between ACH, wire, and check payments in terms of risk and cost?

ACH/BACS batch transfers are low-cost and reversible within limits, suited to routine bulk payments. Wires are fast, final (hard to recall), and higher-cost—used for urgent or high-value/cross-border payments, but attractive to fraudsters because they're irreversible. Checks are cheap to issue but slow and the most exposed to alteration and theft.

Q: How does AP interact with treasury and cash forecasting around payment runs?

AP feeds treasury the pipeline of approved and upcoming payables (amounts, due dates, currencies) so treasury can forecast outflows, ensure funding and FX cover, and decide timing/discount strategy. Treasury may set run caps or timing to match liquidity. This coordination avoids overdrafts, missed discounts, and unnecessary borrowing.

Q: What is the difference between a manual payment and a scheduled payment run?

A scheduled payment run pays many approved invoices in a controlled batch on a set cadence. A manual (ad-hoc) payment is a one-off outside the run for urgent or exceptional items. Manual payments carry higher risk (less batch control) so they need extra authorization and must still be recorded and reconciled.

Q: How does a purchasing card (P-card) program change AP payment processing?

P-cards let employees buy low-value items directly, replacing many small invoices and payments with a consolidated card statement AP reconciles and pays once. It slashes transaction volume and cost per transaction and can earn rebates, but needs spend limits, merchant controls, receipt capture, and review to prevent misuse.

Q: What is a virtual card and why do companies use it for payments?

A virtual card is a single-use or vendor-specific card number generated for a payment, combining card-payment rebates with tight control (fixed amount, one vendor). It reduces fraud exposure versus a physical card, provides rich remittance data, and can extend float, while suppliers must accept card payments (and their fees).

Q: How do you prevent and detect duplicate payments across payment runs?

Prevent with unique supplier+invoice-number validation, three-way matching, and blocking held items; detect with pre-run duplicate reports, periodic audits comparing amount/date/vendor, and recovery-audit services. When found, seek supplier refund or offset against future invoices, and fix the root cause (e.g., re-keyed invoices).

Q: What is a payment file and how is it sent to the bank securely?

A payment file (e.g., NACHA, ISO 20022 pain.001, BACS) contains the batch of payment instructions. It's transmitted to the bank through secure channels—host-to-host, SFTP, or an online banking portal—often with encryption and dual authorization. Secure handling prevents tampering that could redirect funds.

How are supplier credits and deductions applied within a payment run?

Intermediate

Open credit notes and agreed deductions for the vendor are netted against that vendor's due invoices so only the net is paid. The remittance shows the credits applied. If credits exceed invoices due, the balance carries forward until enough invoices exist or a refund is requested from the supplier.

Vendor due: invoices 5,000; open credit 1,200.
  Net payment = 3,800; remittance lists both.

Real-world example A vendor's $1,200 return credit is applied in the run, so the payment is $3,800 instead of $5,000.

Common follow-ups: What if credits exceed invoices due? | How are credits shown on remittance?

Invoice Processing Cash Application Payment Runs

What is the journal entry when invoices are paid in a payment run?

Beginner

Paying invoices debits accounts payable (reducing the liability) and credits cash/bank. If an early-payment discount is taken, the discount is credited to a purchase discount or expense-reduction account so only the net cash leaves. This clears the specific invoices selected in the run.

Pay $10,000 invoice with 2% discount taken:
  Dr Accounts Payable  10,000
      Cr Bank                  9,800
      Cr Purchase Discounts      200

Real-world example The payment run posts AP clearing for each paid invoice and books the discounts captured that week.

Common follow-ups: Where does the discount get posted? | How is the payment matched to invoices?

Invoice Processing Reconciliations Payment Runs

How do you reconcile a payment run to the bank and the ledger?

Advanced

After a run, agree the total of the bank payment file to the AP clearing postings and to the cash leaving the bank account. Investigate rejected/returned payments (e.g., closed accounts), re-issue as needed, and ensure each cleared item matches an open payable now cleared. This ties the sub-ledger, GL, and bank together.

Real-world example Two ACH payments bounce due to closed accounts; AP re-opens the payables, corrects bank details, and re-pays in the next run.

Common follow-ups: What causes returned payments? | How are rejects re-processed?

Reconciliations Cash Application Payment Runs

What is the difference between ACH, wire, and check payments in terms of risk and cost?

Intermediate

ACH/BACS batch transfers are low-cost and reversible within limits, suited to routine bulk payments. Wires are fast, final (hard to recall), and higher-cost—used for urgent or high-value/cross-border payments, but attractive to fraudsters because they're irreversible. Checks are cheap to issue but slow and the most exposed to alteration and theft.

Real-world example A fraudulent invoice pushed for urgent wire payment is scrutinized precisely because wires can't be clawed back.

Common follow-ups: Why are wires a fraud target? | When is ACH preferred over wire?

Payment Runs Vendor Management Reconciliations

How does AP interact with treasury and cash forecasting around payment runs?

Advanced

AP feeds treasury the pipeline of approved and upcoming payables (amounts, due dates, currencies) so treasury can forecast outflows, ensure funding and FX cover, and decide timing/discount strategy. Treasury may set run caps or timing to match liquidity. This coordination avoids overdrafts, missed discounts, and unnecessary borrowing.

Real-world example AP's due-date pipeline lets treasury pre-fund a large FX payment and avoid a costly same-day funding scramble.

Common follow-ups: What data does treasury need from AP? | How do run caps work?

Aging Analysis Credit Control Payment Runs

What is the difference between a manual payment and a scheduled payment run?

Beginner

A scheduled payment run pays many approved invoices in a controlled batch on a set cadence. A manual (ad-hoc) payment is a one-off outside the run for urgent or exceptional items. Manual payments carry higher risk (less batch control) so they need extra authorization and must still be recorded and reconciled.

Real-world example An urgent supplier is paid by a controlled manual wire between weekly runs, with dual approval and immediate posting.

Common follow-ups: Why do manual payments carry more risk? | When is an ad-hoc payment justified?

Invoice Processing Reconciliations Payment Runs

How does a purchasing card (P-card) program change AP payment processing?

Intermediate

P-cards let employees buy low-value items directly, replacing many small invoices and payments with a consolidated card statement AP reconciles and pays once. It slashes transaction volume and cost per transaction and can earn rebates, but needs spend limits, merchant controls, receipt capture, and review to prevent misuse.

Real-world example Moving thousands of small purchases onto P-cards cuts invoice volume sharply and earns a year-end rebate.

Common follow-ups: What controls do P-cards require? | How do P-cards reduce cost per transaction?

Vendor Management Reconciliations Payment Runs

What is a virtual card and why do companies use it for payments?

Intermediate

A virtual card is a single-use or vendor-specific card number generated for a payment, combining card-payment rebates with tight control (fixed amount, one vendor). It reduces fraud exposure versus a physical card, provides rich remittance data, and can extend float, while suppliers must accept card payments (and their fees).

Real-world example AP pays approved invoices with virtual cards to earn rebates and limit each number to the exact invoice amount.

Common follow-ups: How do virtual cards limit fraud? | What's the supplier-side cost?

Vendor Management Payment Runs Credit Control

How do you prevent and detect duplicate payments across payment runs?

Advanced

Prevent with unique supplier+invoice-number validation, three-way matching, and blocking held items; detect with pre-run duplicate reports, periodic audits comparing amount/date/vendor, and recovery-audit services. When found, seek supplier refund or offset against future invoices, and fix the root cause (e.g., re-keyed invoices).

Real-world example A pre-run duplicate report catches an invoice already paid last cycle, avoiding a second $12,000 payment.

Common follow-ups: What detects near-duplicates? | How are duplicate payments recovered?

Invoice Processing Reconciliations Payment Runs

What is a payment file and how is it sent to the bank securely?

Beginner

A payment file (e.g., NACHA, ISO 20022 pain.001, BACS) contains the batch of payment instructions. It's transmitted to the bank through secure channels—host-to-host, SFTP, or an online banking portal—often with encryption and dual authorization. Secure handling prevents tampering that could redirect funds.

Real-world example The approved run generates an ISO 20022 file uploaded via the bank portal and released by a second authorizer.

Common follow-ups: What is ISO 20022? | Why is dual authorization on the file important?

Reconciliations Payment Runs Invoice Processing