Holds

wires system validations may trigger the following hold types type reason applies to clearing method beneficiary account the beneficiary account number in the payment did not match an account in cos inbound automated, manual beneficiary title the beneficiary name in the payment did not match the beneficiary account title inbound automated, manual catchy scan some of the payment details potentially matched information within our fraud prevention database inbound, outbound automated, manual collected funds the core was unable to successfully collect funds for the payment from the originator’s account outbound automated duplicate suspect some of the payment details matched a payment that has been processed within the same business day inbound, outbound automated, manual inbound international some of the payment details indicate that the payment is an international transaction inbound automated, manual internal review the payment was originated by an internal user via the cos explorer portal outbound manual manual miscellaneous hold placed on a wire inbound, outbound manual ofac scan some of the payment details potentially matched information within the ofac database inbound, outbound automated, manual outbound international some of the payment details indicate that the payment is an international transaction outbound automated authorization the amount of the wire requires one or more approvals one or more partner users must access cos explorer to clear the hold outbound manual phone confirmation the payment was originated by an external user (partner) via the cos portal and must be processed using the bank’s callback verification procedure outbound automated, manual travel rule the payment is missing some information that is required by the fincen travel rule outbound automated wires must achieve a pending status to be eligible for distribution this happens when either the validation process did not trigger any holds, or all triggered holds were manually cleared by a user ach system validations may trigger the following hold types type reason applies to clearing method catchy scan some of the payment details potentially matched information within our fraud prevention database inbound, outbound automated, manual collected funds the core was unable to successfully collect funds for the payment from the originator's account outbound manual contested return the rdfi attempted to return this payment to you but the return was not made properly inbound manual dishonored return dishonored return inbound manual internal review a payment was manually originated by an internal user via the cos explorer portal outbound automated, manual manual miscellaneous hold placed on an ach by an internal user inbound, outbound manual ofac scan some of the payment details potentially matched information within the ofac database inbound iats, outbound iats automated, manual phone confirmation a payment was manually originated by a partner user via the cos partner portal outbound automated, manual po box address the payment has an iat sec code and address indicated in the payment contained a po box outbound manual requested return we have received a request from another financial institution to initiate a return but need to investigate it inbound manual unknown account the receiver account listed in the ach entry details does not match an account within cos inbound manual unmatched noc the ach entry details do not match an ach entry which was previously submitted to the fed inbound manual untimely return the return we received was outside of the window allowed by nacha inbound manual untimely unauthorized return the unauthorized return we received was outside of the window allowed by nacha inbound manual