Answers.Body: <p>In the screenshot above -&gt; I don't see any double charges. Every Contribution in the screenshot belongs to a different recurring series (the id = numbers are different).</p>
  <p>As far as at the same time on the same day -&gt; if cron has not run for some time on your site -&gt; then this is exactly what you would see. Every recurring series that has a next_scheduled_date in the past would be due as soon as <code>iATS Payments Recurring Contributions (Daily)</code> is triggered by your system cron.</p>
  <p>As far as double charges -&gt; there are safe guards in place for that -&gt; it can really only happen if that cron job is triggered by two crons at the same time and/or if you have a production and a development set up and you have cron running on both.</p>
  <p>PS - Make sure you are on the latest iATS Extension update (1.7.4)</p>
  <p>On timing -&gt; which recurring contribution series should create a new contribution  to be submitted for processing to iATS -&gt; is solely governed by the Next Scheduled Contribution Date in the Recurring Series Record.</p>
  <p>In this report -&gt; /civicrm/report/com.iatspayments.com/recur?reset=1 you can filter Next Scheduled Contribution Date -&gt; next week so see what's going to happen next week. For this client -&gt; they will have two series transact on April 09 and one on April 10.</p>
  <p><a href="https://i.sstatic.net/RBnru.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/RBnru.png" alt="enter image description here" /></a></p>
  <p>It sounds like your recurring series definitions/dates are not in line with your membership dates.</p>
  <p>Also very important - do not switch ON Recurring within your iATSpayments.com account itself as then you have both civicrm and iats trying to control the schedule of your payments.</p>
  <p>So go into one of your recurring series records (for example id = 578 you have in your second screenshot) -&gt; and view all variables re: time -&gt; i.e. next scheduled date + frequency</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-02T20:58:33.653Z
Answers.Text: Yes it is the latest version of iATS.  Maybe double charged is not the right phrase to use.  We have many instances of people being charged when they shouldn't be and it's all happening on the same days.  For instance,Memberships that are not due to be renewed until next year are all renewed on March 30th. Something is very wrong here.
Answers.UserDisplayName: fdarn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-02T21:02:31.117Z
Answers.Text: I have updated the post with more info.
Answers.UserDisplayName: fdarn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-02T21:28:11.377Z
Answers.Text: see above for more details.
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-02T20:32:51.763Z
Answers.LastActivityDate: 2021-04-02T21:40:28.323Z
Answers.LastEditDate: 2021-04-02T21:40:28.323Z
Answers.UserDisplayName: KarinG - Semper IT
Body: <p>CiviCRM 5.35.1
  WordPress 5.7</p>
  <p>We noticed last week that our members who set up recurring payments via Credit Card with the iATS processor are being double charged or even triple charged in some cases. All of sudden 100s of recurring transactions are being triggered at the same time when they should not be triggered.  For instance, someone who should only be recurring once a year, was charged twice We have no idea what is going on. This just recently started happening.  Please see screenshot below for example.  As you can see, all these transactions are happening at the same time on the same day.  This is not normal and people are being double charged.<br />
  <a href="https://i.sstatic.net/rbHeF.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/rbHeF.png" alt="enter image description here" /></a></p>
  <p>This screenshot shows contributions for an ANNUAL membership that is not due to be renewed until January 30th 2022, but it was renewed on March 30th.  This is just one example.  We have hundreds of instances of this happening over the last 5 or 6 days.<br />
  <a href="https://i.sstatic.net/RDQ2y.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/RDQ2y.png" alt="enter image description here" /></a></p>
  
Tags: <civimember><recurring-contributions><iats>
Title: Members are being charged early
ThreadText: # Members are being charged early
  
  (Asked by: username_0 on 2021-04-02)
  
  CiviCRM 5.35.1
  WordPress 5.7
  
  We noticed last week that our members who set up recurring payments via Credit Card with the iATS processor are being double charged or even triple charged in some cases. All of sudden 100s of recurring transactions are being triggered at the same time when they should not be triggered. For instance, someone who should only be recurring once a year, was charged twice We have no idea what is going on. This just recently started happening. Please see screenshot below for example. As you can see, all these transactions are happening at the same time on the same day. This is not normal and people are being double charged.  
  [![enter image description here](https://i.sstatic.net/rbHeF.png)](https://i.sstatic.net/rbHeF.png)
  
  This screenshot shows contributions for an ANNUAL membership that is not due to be renewed until January 30th 2022, but it was renewed on March 30th. This is just one example. We have hundreds of instances of this happening over the last 5 or 6 days.  
  [![enter image description here](https://i.sstatic.net/RDQ2y.png)](https://i.sstatic.net/RDQ2y.png)
  
  **Tags:** civimember, recurring-contributions, iats
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-04-02. Score: 1
  
  In the screenshot above -> I don't see any double charges. Every Contribution in the screenshot belongs to a different recurring series (the id = numbers are different).
  
  As far as at the same time on the same day -> if cron has not run for some time on your site -> then this is exactly what you would see. Every recurring series that has a next\_scheduled\_date in the past would be due as soon as `iATS Payments Recurring Contributions (Daily)` is triggered by your system cron.
  
  As far as double charges -> there are safe guards in place for that -> it can really only happen if that cron job is triggered by two crons at the same time and/or if you have a production and a development set up and you have cron running on both.
  
  PS - Make sure you are on the latest iATS Extension update (1.7.4)
  
  On timing -> which recurring contribution series should create a new contribution to be submitted for processing to iATS -> is solely governed by the Next Scheduled Contribution Date in the Recurring Series Record.
  
  In this report -> /civicrm/report/com.iatspayments.com/recur?reset=1 you can filter Next Scheduled Contribution Date -> next week so see what's going to happen next week. For this client -> they will have two series transact on April 09 and one on April 10.
  
  [![enter image description here](https://i.sstatic.net/RBnru.png)](https://i.sstatic.net/RBnru.png)
  
  It sounds like your recurring series definitions/dates are not in line with your membership dates.
  
  Also very important - do not switch ON Recurring within your iATSpayments.com account itself as then you have both civicrm and iats trying to control the schedule of your payments.
  
  So go into one of your recurring series records (for example id = 578 you have in your second screenshot) -> and view all variables re: time -> i.e. next scheduled date + frequency
  
  > **Comments:**
  > **username_0**: Yes it is the latest version of iATS.  Maybe double charged is not the right phrase to use.  We have many instances of people being charged when they shouldn't be and it's all happening on the same days.  For instance,Memberships that are not due to be renewed until next year are all renewed on March 30th. Something is very wrong here.  
  > **username_0**: I have updated the post with more info.  
  > **username_1**: see above for more details.  
  
  ---
  
  