TrueChecks will give you a color coded recommended action with every search. There are five recommended actions and four color codes that you should be familiar with:
The Deny recommended action is used for the following:
| Closed Account | Item Cannot be Re-presented | Lost/Stolen |
| Stop Payments | Duplicate Detection | Retired / Ineligible Routing Number |
| Stale Dated | Post Dated | Item Exceeds Stated Max Value |
| Duplicate Presentment |
The Extended Hold recommended action is used for the following:
| RCC Warranty Breach | Forged and Counterfeit Warranty Breach | Divested Account |
| Unable to Locate | Frozen Blocked Account | NSF |
| Kiting |
The Hold recommended action is used for the following:
| Endorsement Irregular | Signature Irregular | Refer to Maker |
| Refer to Image | Forgery | Counterfeit/Alteration |
| Lottery Winner | Secret Shopper | Overpayment |
| Work From Home | Uncollected Funds | Non-negotiable |
| Not Authorized |
The Insufficient Data recommended action is used for the following:
| Suspect Bad Data |
Important Notice: This response does not constitute a guarantee of payment or check validity. It is provided when no negative information is currently available to report. TrueChecks is a supplemental tool and must be used with—never in place of—your organization’s internal check-cashing and deposit policies. Always adhere to your organization’s procedures.
Insufficient Data
Insufficient Data is a response in TrueChecks when we suspect that bad data was either scanned (through the API) or searched manually through the Frontline. Insufficient Data may populate when the routing and account number match, when the routing/account number and check number match, when the account number is 2 digits or less, etc.
In these situations, we are simply asking that you look at the data you are sending over to make sure that the check data matches the MICR data. If it does, you can simply ignore the Insufficient Data/Suspect Bad Data alert.
Multiple Recommended Actions
It's normal for widely used scam checks to have multiple TrueChecks alerts. Each TrueChecks alert has it's own recommended action, and when multiple alerts are returned, TrueChecks will show the most severe recommended action at the top of the result screen.
For example, a heavily counterfeited item might return 10 separate TrueChecks alerts. Let's say that our 10 TrueChecks alerts consist of 8 counterfeit alerts and 2 closed account alerts. After reviewing the chart above, we know that counterfeit alerts return a recommended action of Hold, while closed account alerts return a recommended action of Deny.
In this example, TrueChecks is going to return a recommended action of Deny at the top of the screen. While we have 8 counterfeit (Hold) alerts, and only 2 closed account (Deny) alerts, the Deny recommended action outweighs the Hold recommended action, and TrueChecks will return the Deny recommended action because it is more severe than the Hold recommended action.
As a best practice, we recommend taking the recommended action, the total quantity of alerts, and your organization's internal policy into consideration when making a decision at the teller line.
Comments
0 comments
Article is closed for comments.