xavier_8_29_98
My feedback
2 results found
-
143 votes
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…xavier_8_29_98
supported this idea
·
An error occurred while saving the comment -
5 votes
An error occurred while saving the comment xavier_8_29_98
commented
Ditto! I'd be interested in reviewing this feature. Our site's been live 3 days and folks are asking about a sitemap, FAQ, and org chart or someway to identify the officers of the organization
Hi...any update on this post from the WA Team?
We've been using WA for 2 years now and having to manually handle member level changes vs renewal is becoming more and more of an issue for our admin team. It's confusing for our membership to see two buttons on their profiles: one for Change Level and another for Renew.
Most click the Change Level button thinking that they'll be paying for next year at the new level, only to discover that they've just paid for THIS year twice. Either our admin team has be on the look out for these random events, our members have to know to check the "Renewal due on" date that they rarely ever notice, or when it's time to tally our member counts for voting rights, our admin team discovers the mistake. As you can imagine, the member records are not clean and that is highly problematic for a Sorority.
Has a solution been implemented or is there a way for us to manage this using some custom scripting?