Skip to content

pollockk

My feedback

2 results found

  1. 52 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    28 comments  ·  Wishlist » Members  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We have started analysis for this issue, and it seems that key problem is how Wild Apricot handles level changes close to renewal date. The system is currently designed to collect the full new level amount and set renewal date according to new level renewal policy. All prepaid amounts for old levels are disposed. Moreover, since no prorating occurs, the new level might be effective only for a few days.

    As a first step, we suggest to redesign how level change is working and add prorating there:

    - Level would be changed immediately, as now

    - Remaining portion of old membership level payment will be applied to new level

    - For new levels with specific renewal date (e.g. annual levels with renewals Jan 1st) apply the pro-rating settings for new applications:
    - Allow member to pay only a pro-rated amount of the new level fee (e.g. six months before renewal…

    pollockk supported this idea  · 
    An error occurred while saving the comment
    pollockk commented  · 

    Thank you Mr. Chief for the quick response.

    I am pleased that you have this issue in your sights. please let me know if you need any help with testing or logic on this problem.

    We all have the same goal - make WA do everything for everyone!

    Kim P.

    An error occurred while saving the comment
    pollockk commented  · 

    Our 2000 + organization offers 1 year, 2 year and 3 year memberships. Our renewal date for everyone is Jan 1. We send out dues notices starting 60 days before dues are due.

    The issue we are having is that the system does not calculate renewal dates correctly for our members who move from one level to another.

    If an annual member has a renewal date of 2012 and we send out the dues notice in Nov of 2011, the member has the option of changing to a 2 year or 3 year membership. If they do so, the new renewal dates are calculated from the date of the change and NOT from the date of renewal.

    The following table explains my frustration - All changes were made in 2011 at dues renewal time...

    Renewal Current New Level WA Calculation Should Be
    Date Level

    2012 Annual No Change 2013 2013

    2012 Annual 2 Year 2013 2014

    2012 Annual 3 Year 2014 2015

    This causes our administrator to be constantly changing dates for people exercising level changes. Why would the software make the change to renewal dates based on the date of the change and NOT by adding the new level to the existing renewal date?

    Is this a problem for anyone else?

  2. 139 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    73 comments  ·  Wishlist » Members  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We have started analysis for this issue, and it seems that key problem is how Wild Apricot handles level changes close to renewal date. The system is currently designed to collect the full new level amount and set renewal date according to new level renewal policy. All prepaid amounts for old levels are disposed. Moreover, since no prorating occurs, the new level might be effective only for a few days.

    As a first step, we suggest to redesign how level change is working and add prorating there:

    - Level would be changed immediately, as now - Remaining portion of old membership level payment will be applied to new level - For new levels with specific renewal date (e.g. annual levels with renewals Jan 1st) apply the pro-rating settings for new applications: - Allow member to pay only a pro-rated amount of the new level fee (e.g. six months before renewal…
    pollockk supported this idea  · 
    An error occurred while saving the comment
    pollockk commented  · 

    We also have this problem with the WA software logic. When it is time for our members to renew, they are given the chance to renew for 1, 2 or 3 years. The current logic of treating level changes differently than renewals means that any level change requires administrator manual intervention every time.

    We strongly endorse changing that logic to insure that level changes are treated with the same logic as renewals .

    Kim P.

Feedback and Knowledge Base