1: We choose from different expiration dates based on whether the person is renewing a membership prior to lapsing vs renewing a lapsed membership or joining for the first time. We also extend all to the end of the month of the gift, so a gift made on May 5, 2011 would likely have an expiration date of May 21, 2012 (unless it’s a member renewing early). Our files don’t have expiration dates on them.
2: Yes, that would be great. Our dues amounts do not overlap.
3: This would also be great!
Hope this is helpful.
-Wendy
Jeffrey Montgomery
1) Expiration Dates: Do you typically have the expiration date value to import? If not, is there any special processing around calculating the expiration date of a membership. For instance, do you add a year and two weeks to the transaction date to account for time "lost" processing the membership? If a renewal, does the renewal always expire one year after the previous term expired, or if it's been more than x months, does the expiration date get reset?
2) Category and Program: Would you like an option that could automatically pick program based on matching the transaction amount to the price range of any given program defined for that category. This will work fine if your programs do not have overlapping dues amounts (ie, they should be like "10-19.99" and "20-39.99", not overlapping like "10-25" and "20-40").
3) Upgrades and Downgrades: Would you the option for IOM to automatically classify a renewal as a upgrade if the transaction amount puts it in a program that has a higher price range than the previous program? For instance, they singed up for "adopt a llama" last year at $45. This year the amount is $65 which falls in the "adopt an elephant" program, whos range is higher than the "adopt a llama" program? Again, this would depend on your programs not having overlapping dues amounts.
Thanks!
Jeff