Processing of Auto/Manual Returns

During ACH Credit Receipts processing, the transaction can be moved to any of the exception queues due to validation failure. This can be a result of system validations done or Generic validations maintained.

Auto Returns

Auto-return can be configured for certain Error codes by linking the same to a Return Code in ACH Return Code maintenance PMDRTNCD. If the Return Code linkage is not available, the transaction moved to the related exception queue so that a return can be initiated manually.

It is possible to configure auto-return based on error codes linked to Generic validations or error codes received from ECA system.

Whenever Generic validation error is encountered except for validation types 'Replace' / 'Report' , system checks whether the error code is linked to a return code in PMDRTNCD. If yes, auto return is processed. If the auto return processing could not be initiated, the transaction moves to the related exception queue for the user to take manual action.

If any of the 'Cancel' validation / 'Repair' validation could not be auto processed, the transaction moved to Repair Queue. Failure of 'Exception' validation moves the transaction to Process Exception queue and the 'Override' validation moves the transaction to Business Override Queue.

For the error codes received from External Account validation by DDA system, it is assumed that single error code is received in the error code field of EAC response. System try to match the string value received in the error code field of the EAC response with the linkage available in the ACH Return Code Maintenance PMDRTNCD. If the error code linkage is available, then auto return is processed. Else, the transaction moved to EAC queue. User can manually return the transaction from the EAC queue using queue action 'Cancel'.

Note:

In case there are multiple return codes are received from ECA system, say "AC-TXN-001; ACTXN-002" ,a corresponding maintenance is required in PMDRTNCD, linking the Error Code "AC-TXN-001;AC-TXN-002" to a Return Code. Else, the auto return processing fails.

For ACH Receipts, even if the EAC status is maintained for 'Auto Cancel' in ECA system maintenance PMDECAMT, auto return is processed only if error code received in EAC response is linked to Return code in PMDRTNCD.

Initiating Manual Returns

If the Originated transaction status is Exception, user has to invoke 'Cancel' action from the Exception Queue screen and provide the Reject Code manually to initiate return processing. This is an existing Exception Queue Functionality for inbound ACH transactions.

If the original transaction is of Transaction type 'CT Receipts - Payment', user can select the Return Codes maintained in ACH Return Code maintenance PMDRTNCD for the Network.

When Return is initiated from any of the Exception Queue screens, the system performs the Return days validation based on the Return days maintained for R-transactions in ACH Credit Receipts Preferences Function ID: PYDINPRF.

Note:

If Return Days are not maintained, this validation will be skipped.

Return is allowed for ACH Receipt Value Date+ Return days. If Return is processed beyond this period, an override message is displayed to the user.

Return days are over for the transaction. Do you want to continue with return processing?"

Note:

Return days are counted as Network working days. If the last allowed date is a branch holiday then it will be moved backward to nearest branch working day.

User can Accept/ Reject the override. User can accept the override and
proceed with the Return processing even though return days are over.

Note:

Return of liquidated ACH Receipts are not consider for 14.3.1 scope