Invoice settings that affect other aspects of membership
Along with the plethora of suggestions I have for this database, one that I haven't seen mentioned is adding an "after payment is completed" functionality to certain invoices. Example, after invoice is settled and payment is received, set the renewal date to 00/00/00, or after payment is received their level becomes XYZ. This would help with manual invoices that need to be created for yearly renewal, as Wild Apricot doesn't recognize them as renewal invoices. Also, it would create a workaround for those that need to have graduating levels. Ex: Our database has dues based on how many years you've been a member, but also what stage of your profession you are currently in. So it is not cut and dry, but if we could bunch people into groups and mass produce their invoices with a certain type of settings and then onto the next group with a separate type of settings, that would be phenomenal.
I honestly know that I am shouting into the wind at this point and will most likely be met with "This would involve major restructuring of our system" or "This is not a priority this year" or "Here is this loophole". Maybe it's time to restructure and give your users the functionality they NEED. Whenever I run into a problem this is the first place I look, not for an answer, but for a request that has either been unanswered or unattempted for years.
Ava Whisman
shared this idea
Ava, we won't make any automations after invoice is marked paid. 3 main reasons:
- For membership renewals there are ways to setup dues for really complex setups using extra charge fields. Not all of scenarios would work for self-service, but everything is possible manually. This case you would have up-to-date member database and all automations in place.
- Even if we would go with some post-invoice actions - it would be also shouting in the wind. Very few accounts will need it, and to make it usable - we would need to think of huge amount possible scenarios
- If you want to still use some automations, I would advise going on with Make/Zapier. These are perfect for such tailored scenarios and we have all integrations in place for Finances and Members functionality.
