Answers.Body: <p>It’s 100% the same transaction. iATS reported they had an issue with Transaction ID numbering sequence for a portion of Nov. I’ll copy paste the Email thst went out to Partners:</p>
  
  <p>Dear Valued Partner,
  Please be advised that if your environment takes postbacks and/or runs morning download journals from the iATS system, your clients may have recently been impacted by duplicate transaction records caused by a logic error in creating and assigning iATS transaction ID's.
  When did the issue occur? From November 18th to December 2nd .
  Has the issue been resolved?
  Yes. Our development team has identified the root cause and made the necessary coding changes to correct any duplicate iATS transactions importing into your environment. We can confirm that this was due to our logic in creating/assigning iATS transaction ID’s and did not impact the number of transactions charged to account holders. This has been corrected and should not occur again, but as always, please keep us informed if you see any instances of this occurring.
  What should you do?
  There is no update needed on your part to correct the coding in order prevent this in the future. Clients are free to delete the duplicate iATS transaction from the environments without worry of impact. Note, clients should check the iATS portal to confirm which iATS transaction was processed and which one was the duplicate needing to be deleted.
  If you have any additional questions, or should you need assistance in identifying these duplicate transactions, we are happy to assist you, or our mutual clients directly. They can reach out to our iATS Customer Care team for assistance with this process at iatscs@iatspayments.com or via phone at 1-888-955-5455 Option 1. 
  Sincerely, </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-11T17:19:12.303Z
Answers.Text: That email copy/paste needs some formatting.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-11T19:35:00.347Z
Answers.Text: Thanks Karin! That helps
Answers.UserDisplayName: Zachary
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-11T01:54:02.730Z
Answers.LastActivityDate: 2019-12-11T01:54:02.730Z
Answers.UserDisplayName: KarinG - Semper IT
Body: <p>Love iATS and Civi!</p>
  
  <p>That aside, we're experiencing an issue where some transactions have a mismatch as stated in title.</p>
  
  <p>In the SQL Database I'll browse the 'civicrm_iats_journal' table and find the transaction record and I'll see something like 'AC13AA7R' </p>
  
  <p>Then, on the civi contribution record, I'll see this in the transaction ID field: 'A1FA1CC2:1574381880' i.e. a different ID altogether.</p>
  
  <p>Curiously, the invoice ID matches in the contribution 'Invoice Reference' field, in the iATS online journal, and Civi's '<code>civicrm_iats_journal</code>' table. So I'm 99.9% sure it's the same transaction.</p>
  
Tags: <iats>
Title: mismatch between journal and contribution transaction ID
ThreadText: # mismatch between journal and contribution transaction ID
  
  (Asked by: username_0 on 2019-12-10)
  
  Love iATS and Civi!
  
  That aside, we're experiencing an issue where some transactions have a mismatch as stated in title.
  
  In the SQL Database I'll browse the 'civicrm\_iats\_journal' table and find the transaction record and I'll see something like 'AC13AA7R'
  
  Then, on the civi contribution record, I'll see this in the transaction ID field: 'A1FA1CC2:1574381880' i.e. a different ID altogether.
  
  Curiously, the invoice ID matches in the contribution 'Invoice Reference' field, in the iATS online journal, and Civi's '`civicrm_iats_journal`' table. So I'm 99.9% sure it's the same transaction.
  
  **Tags:** iats
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-12-11. Score: 2
  
  It’s 100% the same transaction. iATS reported they had an issue with Transaction ID numbering sequence for a portion of Nov. I’ll copy paste the Email thst went out to Partners:
  
  Dear Valued Partner,
  Please be advised that if your environment takes postbacks and/or runs morning download journals from the iATS system, your clients may have recently been impacted by duplicate transaction records caused by a logic error in creating and assigning iATS transaction ID's.
  When did the issue occur? From November 18th to December 2nd .
  Has the issue been resolved?
  Yes. Our development team has identified the root cause and made the necessary coding changes to correct any duplicate iATS transactions importing into your environment. We can confirm that this was due to our logic in creating/assigning iATS transaction ID’s and did not impact the number of transactions charged to account holders. This has been corrected and should not occur again, but as always, please keep us informed if you see any instances of this occurring.
  What should you do?
  There is no update needed on your part to correct the coding in order prevent this in the future. Clients are free to delete the duplicate iATS transaction from the environments without worry of impact. Note, clients should check the iATS portal to confirm which iATS transaction was processed and which one was the duplicate needing to be deleted.
  If you have any additional questions, or should you need assistance in identifying these duplicate transactions, we are happy to assist you, or our mutual clients directly. They can reach out to our iATS Customer Care team for assistance with this process at iatscs@iatspayments.com or via phone at 1-888-955-5455 Option 1.
  Sincerely,
  
  > **Comments:**
  > **username_2**: That email copy/paste needs some formatting.  
  > **username_0**: Thanks Karin! That helps  
  
  ---
  
  