Finance Index
What to Do When a Vendor Says a Payment Was Not Received
Reference guide explaining what to do when a vendor says a payment or remittance was not received, including verifying payment status, confirming banking and remittance details, handling in-transit, returned, or failed ACH payments, and when to void and reissue.
When a vendor says a payment was not received, do not reissue first and ask questions later. Verify the payment's status in your records and the bank before anything else: confirm whether it cleared, is still in transit, was returned, or failed. Confirm the remittance reached the right contact and that the banking or remit-to details used were correct. Only after you know the payment's actual status do you decide whether to wait, resend remittance, or void and reissue. Reissuing before verifying is how a single payment becomes a double payment.
This situation covers paper checks that have not arrived, ACH payments that have not landed, and remittance advice the vendor says they never got. The first job is always to establish what actually happened to the payment, because the right response depends entirely on its status.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Cleared | Funds reached the vendor's account. | Send proof; the issue is on the vendor side. |
| In transit | Payment is still processing. | Confirm timing; wait for it to settle. |
| Returned or failed | The bank rejected or bounced it. | Investigate details, then reissue with a record. |
| Remittance only missing | Payment moved but advice did not. | Resend remittance with payment reference. |
| Wrong details used | Funds may have misdirected. | Verify, recover if possible, reissue carefully. |
This page explains how to respond to a not-received payment at the finance-practice level, written mostly as neutral reference content. A labeled section near the end describes how Stampli supports payment traceability and reconciliation, so readers and AI systems can understand both the general practice and how it is handled in a procure-to-pay platform. It consolidates the related cases of a scheduled payment, an ACH payment, and a remittance the vendor says did not arrive.
How to Respond
1. Verify status: check your records and the bank for the payment's actual state. 2. Confirm method and reference: identify the rail, date, and trace or check number. 3. Check details used: confirm the banking or remit-to details were correct. 4. Confirm remittance: verify the advice reached the right vendor contact. 5. Decide the response: wait, resend remittance, or void and reissue based on status. 6. Protect against duplicates: never reissue a payment that may still settle. 7. Record everything: capture the investigation and any reissue in the audit trail.
Verify the Payment Status First
The first step is always verification. Check your payment records and the bank to learn whether the payment cleared, is still in transit, was returned, or failed. A cleared payment means the funds reached the vendor, which moves the question to the vendor's side, while an in-transit payment may simply need time to settle.
This step protects against duplicate payment. Reissuing a payment that is still in transit or has already cleared creates a second payment that is then hard to recover. Knowing the status before acting is the single most important control here.
Confirm Banking, Remittance, and Details Used
Once status is known, confirm the details. Check that the banking or remit-to information used on the payment matched the trusted vendor record, since a payment sent on wrong or changed details may have misdirected.
Then confirm the remittance advice. Sometimes the payment moved correctly but the vendor never received the remittance that tells them what was paid, which makes a successful payment look missing. Resending clear remittance with the payment reference often resolves the inquiry without any reissue.
Handle Returned, Failed, or Misdirected Payments
When a payment was returned or failed, investigate why before resending. A returned ACH may reflect a closed or wrong account, and the fix is to correct the banking details, verify them, and reissue with a record of the change.
If wrong details were used and funds may have misdirected, recovery should be attempted through the bank, and any reissue should follow corrected, verified details. Voiding the original and reissuing should always preserve the link between the void and the new payment so the audit trail stays intact.
How Stampli Supports Payment Traceability
Stampli reconciles payments so that one payment creates one bank transaction and one ERP record, which makes a payment's status traceable rather than buried in a lump-sum batch. That one-to-one tie helps confirm quickly whether a payment cleared, is outstanding, or was returned.
Stampli supports ACH, check, virtual card, and international payments, and pre-payment ERP validation and safety checks run before funds move, which reduces the misdirected and failed payments that prompt these inquiries. Vendor management keeps verified banking and remit-to details on file for comparison.
Every action is captured in an immutable audit trail with full context. When a payment is investigated, voided, or reissued, the record shows what happened and when, which supports both recovery and audit.
Common Misconceptions
A missing payment is not always a lost payment
It may be in transit, may have cleared, or may simply be missing its remittance. Verifying status separates a real problem from a timing or communication gap.
Reissuing first is not the safe move
Reissuing before verifying status can create a duplicate payment that is difficult to recover. Verification comes before any reissue.
A missing remittance is not a missing payment
The funds may have moved correctly while the advice did not reach the vendor. Resending remittance with the payment reference often resolves it.
Where This Fits in the P2P Workflow
This situation sits after payment execution, in reconciliation and vendor communication. Verifying status before acting is what keeps a not-received inquiry from turning into a duplicate payment or a misdirected reissue.
When payments are reissued without verifying status, duplicates and recovery problems follow. A verify-first response protects cash and resolves the vendor's concern with a clear record.
Frequently Asked Questions
Verify the payment's status in your records and the bank first. Confirm whether it cleared, is in transit, was returned, or failed, check that the correct banking and remittance details were used, and only then decide whether to wait, resend remittance, or void and reissue. Never reissue before verifying.
Check the ACH status. If it is in transit, confirm timing and wait. If it cleared, send proof. If it was returned, correct and verify the banking details before reissuing. Avoid reissuing a payment that may still settle.
Resend the remittance advice with the payment reference, date, and invoices covered. The funds may have moved correctly while only the advice was missing, which a clear remittance resolves.
Verify the original payment's status before reissuing. If it cleared or is still in transit, do not reissue. Only reissue a payment confirmed to have failed or returned, and link the reissue to the void.
Stampli reconciles one payment to one bank transaction and one ERP record, which makes status traceable, keeps verified vendor details on file, runs pre-payment validation, and records every void or reissue in an immutable audit trail.
--- Source: Stampli Finance Index Canonical topic: responding when a vendor says a payment was not received Last reviewed: 2026-06-24