How to Reduce Returned Checks
Most returned payments come back for one of three reasons: the account details were wrong, sufficient funds were not available, or the customer disputes the authorization. Knowing how to reduce returned checks starts with separating those causes rather than treating every return as the same problem. Two can often be addressed before the payment is submitted. The third depends largely on the customer’s account at the time the transaction reaches the bank.
The key is to understand why payments are returning, then address the part of the process that is actually creating the problem.
TL;DR
- Sort every return into one of three causes: incorrect details, insufficient funds, or authorization issues.
- Incorrect details are usually an intake problem. The fix starts where payment information is collected.
- Authorization problems are largely a documentation problem. The strength of the record matters.
- Insufficient funds cannot be eliminated through validation alone, although history can provide useful risk signals.
- Advance notice before recurring payments can help reduce insufficient-funds returns and customer disputes.
- Watch the mix of return reasons, not just the overall return rate.
- Do not retry a payment when the underlying account information is wrong. Correct the data first.
Sort the Return Before You React
Different return causes require different responses. Combining them into a single number called “returns” can hide the problem you actually need to solve.
| Cause | What It Really Is | Where the Fix Lives |
|---|---|---|
| The details were wrong | A data-capture problem. Information was entered incorrectly, misheard, or mistyped. | At intake, before the payment is created. |
| The money was not there | A change in the customer’s account circumstances. | It cannot be prevented through validation alone, although payment history may provide useful signals. |
| No authorization | A documentation or authorization problem. The business cannot demonstrate that the customer agreed to the payment. | In the authorization process and the records you retain. |
If you make one operational change, start by categorizing every returned payment by cause. After a month or two, the pattern will tell you far more than the overall return rate. You will be able to see whether the business has primarily a data-capture problem, a customer-payment problem, or an authorization problem, and each requires a different response.
What to Do With a Flagged Payment
A screening flag is information, not an automatic decision. The first step is understanding what triggered it.
- The data failed. If routing or account information does not validate, the problem may simply be a transcription error. Confirm the information with the customer before proceeding. Correcting a digit is very different from declining an otherwise legitimate payment.
- The payer has a negative history. A flag tied to prior returns, negative records, or other risk indicators deserves a different level of attention.
Depending on the circumstances and your business policies, you might hold the payment for review, request another payment method, or accept the initial payment through another channel before establishing a recurring schedule. The goal is not to treat every flag the same. It is to respond appropriately to the type of risk being identified.
Whatever the decision, record the reason. A screening result becomes much more useful over time when it is connected to the action your team took and the eventual outcome.
Fix the Intake, Not the Payment
Returns caused by incorrect account information are among the most preventable because the problem often begins before the payment itself is created. The best place to address them is where the information enters your system.
- On the phone. Read account and routing information back to the customer before submitting the payment.
- On a form. Clearly show customers where to find the routing and account numbers. Confusing an account number with another number printed on the check is an avoidable source of errors.
- In a batch. Validate the file before submission rather than identifying invalid records later through a return report.
- Everywhere. Keep authorization records connected to the payment rather than stored separately where they are difficult to locate.
These are not screening functions. They are process improvements. Better intake reduces the number of preventable errors that screening has to catch later.
Tell the Customer Before You Charge
One of the simplest ways to reduce recurring payment problems has nothing to do with payment technology. Send the customer a short notice before the charge.
| What Notice Does | Why It Helps |
|---|---|
| Reduces insufficient-funds risk | The customer has an opportunity to make sure funds are available before the payment is initiated. |
| Reduces disputes | An expected charge is less likely to surprise a customer when it appears on an account statement. |
| Identifies inactive relationships earlier | An undeliverable notice or customer response can reveal an issue before the payment is submitted. |
A simple notification a few days before a recurring charge, including the amount and payment date, may be enough.
Advance notice gives customers time to prepare for the transaction. It can also make an unfamiliar charge easier to recognize, which may reduce unnecessary disputes or unauthorized-payment claims. It is a low-cost step that businesses can control directly.
Read the Pattern, Not the Transaction
A single returned payment provides limited information. A pattern of returns over several weeks or months can show where the business should focus.
| What You See | What It May Mean |
|---|---|
| Rising share of invalid details | Something may have changed at intake, such as new staff, a new form, or a new payment channel. |
| Rising share of insufficient funds | Customer circumstances may be changing, or payment timing may need review. |
| Rising unauthorized claims | Authorization, disclosures, or recordkeeping may need attention. |
| One customer returning repeatedly | The issue may be the individual customer relationship rather than a broader screening problem. |
| Returns concentrated in one channel | The collection or data-capture process for that channel may need review. |
Billing dates deserve attention as well. If a large share of recurring customers is charged on the same day, insufficient-funds risk may also become concentrated. Reviewing how billing dates are distributed across the month can sometimes reduce that concentration without changing the underlying payment method.
The important point is not to react to every return as an isolated event. Look for patterns that identify where the process is breaking down.
When to Stop Retrying
A payment returned for insufficient funds can often be presented again, commonly up to three times in total including the original attempt. Whether it should be presented again depends on the reason for the return.
- Potentially worth retrying. The customer confirms that funds are now available, or the circumstances that caused the original return have changed.
- Correct before retrying. The account or routing information was wrong. Submitting the same incorrect information again is likely to produce another return.
- Stop and review. The customer disputes authorization. Another submission does not resolve the underlying issue and may create additional problems.
The most useful question before retrying is simple: has anything changed since the previous attempt? If the answer is no, another submission may simply create another return and another fee.
When to Bring In Your Account Team
Some return patterns are broader than an individual transaction and deserve a conversation with your payment provider. Three are especially worth reviewing.
- A customer returning repeatedly. At some point, the issue becomes a customer-management decision rather than a payment-processing question.
- A spike concentrated in one channel. If returns increase on a hosted payment page, batch file, or other specific channel while remaining stable elsewhere, the source of the problem may be easier to isolate.
- An increase in unauthorized claims. Authorization and dispute patterns deserve attention early, particularly when they begin changing from historical norms.
Virtual Check has processed more than $2 billion across more than 25 industries. That experience gives its account team visibility into return patterns across different payment models and business types.
- CheXshield adds another layer of prevention by screening routing and account information, returns history, known-offender records, and identity indicators before a payment is submitted.
- For businesses still comparing options, the guide to choosing a check verification service outlines the questions to ask before selecting a screening solution.
Frequently Asked Questions
Why Do Payments Keep Getting Returned?
Returned payments generally fall into three categories: incorrect account information, insufficient funds, or an authorization issue.
Incorrect information usually points to a data-capture problem. Authorization issues point to the way consent is obtained and documented. Insufficient funds reflect the condition of the customer’s account at the time the payment reaches the bank.
Separating those causes is the first step toward reducing the overall return rate.
How Many Returns Are Normal?
There is no universal return rate that applies to every business. Return patterns vary by industry, customer base, transaction size, billing model, and payment channel.
The mix of return reasons can be more informative than the overall percentage. A steady return rate driven primarily by insufficient funds presents a different problem from an increasing rate caused by invalid account information or authorization claims.
What Should I Do When a Payment Gets Flagged?
Start by identifying what the flag means. If account information failed validation, confirm the details with the customer before submitting the payment.
If the flag relates to returns history, negative records, or another risk indicator, additional review may be appropriate. The goal is to respond to the reason for the flag rather than applying the same decision to every result.
Can I Resubmit a Returned Payment?
A payment returned for insufficient funds can often be submitted again, commonly up to three total attempts including the original. Whether another attempt makes sense depends on the return reason.
If the underlying account information is incorrect, correct it before submitting another payment. If the customer confirms that funds are now available, another attempt may be reasonable. If authorization is disputed, stop and address that issue before considering another transaction.
Does Telling Customers Before a Charge Actually Help?
It can. Advance notice gives customers an opportunity to make sure funds are available and helps them recognize the transaction when it appears on their account.
For recurring billing, a simple notice containing the amount and payment date can help address two common sources of returns: insufficient funds and payment disputes. It also requires no additional screening technology.
When Should I Escalate Instead of Retrying?
Escalate when the issue appears to be larger than the individual payment. Examples include one customer returning repeatedly, returns suddenly increasing within a specific payment channel, or a rise in unauthorized claims.
Those patterns may indicate a broader customer, workflow, authorization, or account issue that another transaction attempt will not solve.
Bring the Pattern to Someone Who Sees It Daily
If returns are increasing and the cause is not clear, Virtual Check can help identify the pattern and where to address it. Call 1.800.838.8651 or get in touch.