Answers.Body: <p>Ah ha - I solved my own issue ....</p>
  
  <p>It was related to some code I put together myself and forgot, that checks to see if a grace member has had a contribution and re-instates membership.</p>
  
  <p>This was related to some other code that I found a couple of years ago that handled the 'joining' of memberships when contributions have been bulk loaded ( which doesn't auto link ) from this post  <a href="https://forum.civicrm.org/index.php?topic=19322.0" rel="nofollow noreferrer">https://forum.civicrm.org/index.php?topic=19322.0</a>  - but the code had started failing due to deprecated mysql code ...  fixed now</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-16T08:06:14.023Z
Answers.Text: Ah we have all had the same thing.... ;-)
Answers.UserDisplayName: Jaap Jansma - CiviCooP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-16T07:49:00.407Z
Answers.LastActivityDate: 2018-05-16T07:49:00.407Z
Answers.UserDisplayName: Alan Fuller
Answers.Body: <p>It all depends on how your organisation works and how strict the rules are. One could argue that all memberships are renewed at the end of the year and payments are created but with status pending. A member could still benefit altough they did not pay. This means that the membership status should stay active,</p>
  
  <p>One could also argue that as long as someone did not paid the member has no benefit in that case you want an inactive status come into play.</p>
  
  <p>What is really cool about CiviCRM is that it is possible to define those membership status rules yourself. You can do that under Administer --> CiviMember --> Membership status rules.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-14T15:04:06.910Z
Answers.LastActivityDate: 2018-05-14T15:04:06.910Z
Answers.UserDisplayName: Jaap Jansma - CiviCooP
Body: <p>we might have got our sequence / settings wrong, I'm not certain.</p>
  
  <p>Currently  ( and likely in teh future ) we collect membership subs manually, with an annual membership.</p>
  
  <p>We set it up such that memberships expire ( 1 Jan ) and when they expire they go into grace instantly for 2 years.</p>
  
  <p>Then we manually collect sub in the spring and then batch load these based.</p>
  
  <p>The membership contributions get recorded, but the status remains 'grace'.</p>
  
  <p>Have we got this wrong? Should the membership be let expire not go to grace? Logically I guess the sequence should be member - end of year it becomes pending payment and only if payment not received it goes to grace?</p>
  
  <p>Alan </p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-14T21:22:42.863Z
Comments.Text: I think you need to provide more detail on how you are 'recording' the contributions
Comments.UserDisplayName: petednz - fuzion
Tags: <civimember>
Title: Renewal Status & Process
ThreadText: # Renewal Status & Process
  
  (Asked by: username_0 on 2018-05-14)
  
  we might have got our sequence / settings wrong, I'm not certain.
  
  Currently ( and likely in teh future ) we collect membership subs manually, with an annual membership.
  
  We set it up such that memberships expire ( 1 Jan ) and when they expire they go into grace instantly for 2 years.
  
  Then we manually collect sub in the spring and then batch load these based.
  
  The membership contributions get recorded, but the status remains 'grace'.
  
  Have we got this wrong? Should the membership be let expire not go to grace? Logically I guess the sequence should be member - end of year it becomes pending payment and only if payment not received it goes to grace?
  
  username_0
  
  **Tags:** civimember
  
  > **Comments:**
  > **username_1**: I think you need to provide more detail on how you are 'recording' the contributions  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2018-05-16. Score: 1
  
  Ah ha - I solved my own issue ....
  
  It was related to some code I put together myself and forgot, that checks to see if a grace member has had a contribution and re-instates membership.
  
  This was related to some other code that I found a couple of years ago that handled the 'joining' of memberships when contributions have been bulk loaded ( which doesn't auto link ) from this post <https://forum.civicrm.org/index.php?topic=19322.0> - but the code had started failing due to deprecated mysql code ... fixed now
  
  > **Comments:**
  > **username_2**: Ah we have all had the same thing.... ;-)  
  
  ---
  
  ### Answer by username_2 on 2018-05-14. Score: 1
  
  It all depends on how your organisation works and how strict the rules are. One could argue that all memberships are renewed at the end of the year and payments are created but with status pending. A member could still benefit altough they did not pay. This means that the membership status should stay active,
  
  One could also argue that as long as someone did not paid the member has no benefit in that case you want an inactive status come into play.
  
  What is really cool about CiviCRM is that it is possible to define those membership status rules yourself. You can do that under Administer --> CiviMember --> Membership status rules.
  
  
  ---
  
  