The invoice says paid. The warehouse shipped the order. A few days later, the bank returns the payment.
Now the company has two problems. It doesn’t have the money, and the customer already has the merchandise.
I’d pull the payment records first. I want to know when the payment was submitted, when the order shipped, and what the bank actually confirmed before the merchandise left.
There’s a good chance someone saw “Paid” in the accounting software and assumed the money was safe.
That’s an expensive assumption.
A September 1 article from PYMNTS caught my attention because it suggests a surprising number of businesses are making it.
Researchers surveyed 60 heads of payments at companies with annual revenues between $100 million and $1 billion. Of those surveyed, 57% said their companies usually discovered payment fraud or nonclearance after settlement. Only 30% said they generally caught problems before payment initiation or during authorization.
The study was conducted with Plaid, a bank-verification technology company. It’s a small sample of larger businesses, so I wouldn’t apply those percentages to every company.
But I would take a hard look at the timing.
Why are so many businesses finding out there’s a payment problem after the transaction has supposedly been completed?
I’d Like to See the Original Payment
Consider a $30,000 equipment order paid by ACH.
The customer submits payment Monday. The invoice is marked paid. Tuesday, the warehouse ships the equipment.
Thursday, the bank returns the ACH because the account was closed.
That’s not an actual case from the study, but it’s a useful example of what I’d be looking for.
I’d pull the processor’s records and compare the timestamps.
Did the processor confirm that the payment request had been accepted, or that the funds had actually settled?
Those aren’t the same thing.
And even a settled ACH payment may be subject to a later return under applicable banking rules.
I’d also want the original order. Customer name, bank account information, billing address, shipping address, and any correspondence requesting expedited delivery.
Then I’d check the company’s procedures.
Were employees supposed to verify payment before shipping?
If so, who verified this one?
If not, why not?
The answer matters because the customer may have made an innocent mistake. An old bank account number could explain the return.
But it wouldn’t explain why the business released $30,000 worth of equipment without adequate payment verification.
A Closed Account Is One Thing. A Pattern of Closed Accounts Is Another.
The PYMNTS study found that 88% of respondents had experienced at least one accounts-receivable payment integrity issue during the previous year.
Seven in ten reported ACH returns involving invalid or closed accounts or customer entry errors. Sixty-three percent had experienced reversals or disputes after delivery, and 47% reported account identity or legitimacy problems.
I’d be careful about calling all of that fraud.
Customers make mistakes. Businesses change banks. Legitimate disputes happen.
The return reason is important.
But I’d be suspicious if I kept seeing large orders paid from accounts that didn’t belong to the customer, particularly when the merchandise was shipped somewhere other than the customer’s business address.
I’d check whether the same delivery address appeared on orders from different customers.
I’d look for repeat phone numbers, email addresses, and bank accounts.
I’d also compare the customer’s ordering history.
A first-time customer placing a $40,000 rush order deserves more scrutiny than an established customer ordering the same supplies they’ve purchased every month for five years.
I wouldn’t automatically reject the order. I’d want to verify who I was dealing with before shipping.
Who Overrode the Payment Hold?
Here’s a report I’d want to examine: every order released despite a failed or incomplete payment verification.
I’d start with the largest amounts.
Who requested the exception? Who approved it? Was there an explanation in the customer’s file?
Suppose a salesperson approved several shipments before payment verification was completed.
I’d compare those orders with the employee’s overall sales. Maybe they handle most of the company’s large accounts. Maybe they’re following a procedure nobody ever questioned.
Or maybe they’re making exceptions because they don’t want to lose a sale.
I’d ask.
I’d also look at whether employees receive commissions when an order ships or only after the customer pays.
If shipping the order triggers a commission, the company has given the salesperson a financial reason to get merchandise out the door quickly.
That doesn’t mean the employee is dishonest. But I’d want someone else approving exceptions to payment requirements.
And I’d want those approvals documented.
A company shouldn’t have to interview five employees two weeks later to figure out who authorized a shipment.
The Verification Records Tell Another Story
The study found that companies detecting problems earlier were more likely to use bank-account verification tools.
Among companies that usually identified problems before settlement, 81% used instant account verification. Among those usually discovering problems afterward, 47% did.
For bank-account ownership checks, the figures were 76% and 35%.
That doesn’t prove the software prevented fraud. But I’d want to know whether the business was using the verification tools available to it.
And more importantly, what happened when verification failed.
Did somebody investigate the mismatch?
Did the order get placed on hold?
Or did an employee dismiss the warning because the customer was in a hurry?
I’d review a sample of failed verifications and follow those transactions through to completion.
If the company routinely releases orders after failed checks, buying better verification software isn’t going to solve the underlying problem.
What Happened Before the Payment Failed?
When a bank returns a payment, most people start with the return.
I’d start earlier.
What changed before the order was placed?
Was this a new customer? Did an existing customer suddenly request a different payment arrangement? Did the delivery address change at the last minute?
I’d compare the order against the customer’s previous transactions.
If a longtime customer suddenly provides different banking information, I’d want someone to confirm the change using a phone number already on file.
Not the number in the email requesting the change.
And if the customer is pushing for immediate shipment while the payment details are still being verified, I’d want to know why.
Maybe there’s a perfectly good reason.
But I’m not releasing expensive merchandise based on a story I haven’t checked.
Pull the Last Twelve Months
One bad payment doesn’t tell me whether a business has a bigger problem.
I’d pull every ACH return, payment reversal, and dispute from the previous year.
I’d want the original amount, customer, payment date, return date, reason code, and fulfillment date.
Then I’d sort by customer, transaction size, payment method, and employee who approved the order.
I’m looking for repetition.
Do the same customers keep having payments returned?
Are most of the problems coming from first-time buyers?
Are orders being shipped before payments are verified?
Is one employee approving an unusually high number of exceptions?
I’d also want to know how much money the business eventually recovered.
A $20,000 returned payment that’s corrected the next day is different from a $20,000 returned payment on merchandise that can’t be recovered.
Both belong in the report. But they don’t represent the same loss.
Once I understood the reasons behind the returns, I’d know which procedures needed attention.
An Accurate Reconciliation Won’t Get the Equipment Back
The bookkeeper can record the original payment, reverse it when the bank returns it, and reconcile the account perfectly.
The books can be 100% accurate.
The business can still be out $30,000.
I think this distinction gets missed when owners assume their accounting department will catch payment problems.
Accounting can identify a returned payment and make sure the receivable is still recorded.
It can’t always prevent the warehouse from releasing an order.
That’s a decision made earlier, usually by sales, operations, or management.
So I’d want to know exactly what those employees see before an order ships.
Does the system distinguish between a payment being submitted and a payment actually settling?
Does someone review unverified bank accounts?
What happens when a customer insists they need the merchandise immediately?
And who has the authority to approve an exception?
I’d rather see a short, enforceable approval procedure than a twenty-page policy that employees ignore.
The Question I’d Ask After Reviewing the File
Go back to that $30,000 equipment order.
The customer paid by ACH on Monday. The equipment shipped Tuesday. The bank returned the payment Thursday.
I’d put the payment confirmation beside the shipping authorization.
Somewhere between those two records, someone decided the transaction was safe enough to proceed.
That’s the decision I’d examine.
What did that person know? What could they have verified? And did they follow the company’s procedures?
The answer might lead to a better payment process, additional verification, or a change in who can release expensive orders.
But I’d want the answer before another shipment went out.
The PYMNTS study found that 57% of respondents usually discovered payment problems after settlement. It doesn’t tell us how many losses could have been prevented.
I’d be more interested in finding that out for my own business.
Because the worst time to discover a customer can’t pay is after you’ve handed over the merchandise.
And the most important evidence may be the payment warning somebody saw before they shipped it.
Sources: PYMNTS, September 1, 2026; PYMNTS Intelligence/Plaid study and methodology.