Rejected ACH marked as Completed

[twomice]

Actual behavior:

• An ACH contribution submitted on Jan. 9 was marked as Completed in CiviCRM.
• On Jan. 16, iATS sent notification by email that the transaction was rejected as "62: CANNOT_TRACE"
• The transaction remains Completed in CiviCRM.

Expected behavior:

• The contribution should never have been marked Completed; at least it should have been left at Pending from the time it was submitted until a response from iATS was available (which can take a day or two, I believe), and later marked as Failed when it was rejected by iATS.

Supporting documents:

• Screenshot of contribution record (another contributions similarly affected is not shown):
• Message received as text file from iATS (note that it references both the above-shown contribution and one more similarly affected):

  
  Hello,

The following returns were received today and are included in your IATS reports.

RETURN DATE: 2018/01/16 AGENCY CODE: 3KOO

REF_ID NAME BANK_ACCOUNT AMOUNT REJ_CODE REJECT_REASON

---

AA73387D [REDACTED] [REDACTED] 54.00 62 CANNOT_TRACE
AA7338D0 [REDACTED] [REDACTED] 54.00 62 CANNOT_TRACE

---

TOTAL 2 108.00

Should you have any questions regarding these items, please do not hesitate to contact IATS Customer Service at 1-888-955-5455 or iatscs@iatspayments.com

NACHA operation rules are in effect to assess fines for reprocessing ACH rejects to the same invalid bank account. The client may not resubmit transactions on any accounts that receive ACH returns for reason codes of 60, 62, 63, 65, 72, 77. NACHA may impose fines (up to $500,000 a month until remedied and ultimately suspension from ACH origination if violations continue) for reinitiating ACH transactions to a merchant's account when an ACH return has occurred for the reason codes noted above. 60 NO AGREEMENT EXISTED 62 CANNOT TRACE 65 ACCOUNT CLOSED 75 AGREEMENT REVOKED 63 PAYMENT STOPPED/RECALLED 72 INVALID ACCOUNT # / BANK# NOT FOUND 77 RECEIVED DFI NOT QUALIFIED

[KarinG]

Contributions that are Returned are actually Completed by the ACHEFT banking system (log into iATSPayments.com - find the ACHEFT batch on January 10 and notice it's marked completed); and then later on they are Returned - it's an additional entry (If I'm not mistaken this could be up to 90 days) -> in your case 6 it was days later;

I've tried explaining this in the README file why we don't process these automatically -> let me know if you've got Edits/Suggestions to my wording:

Please note that ACH Returns require manually processing. iATS Payments will notify an organization by Email in case such ACH Returns occur - the reason (e.g. NSF) is included. It is up to CiviCRM administrators to handle this in CiviCRM according to your organization's procedures (e.g. if these were monies re: Event registration -> should that registration be canceled as well or will you ask participant to bring cash; if NSF fees should be charged to the participant etc).

[twomice]

I think I understand, @KarinG. Thanks for the quick response.