Demoing the Enhanced Recurring functionality, and understanding how it differentiates from FY Recurring/Legacy Recurring
Check out the demo here:
Key takeaways:
In Legacy recurring, if a donor changes their schedule from weekly to monthly, we actually stop the first version and start a brand new recurring donation in SF. However, in Enhanced Recurring, we keep the same recurring donation object and then SF will create a new schedule. So you’ll see an “Active Schedule” and then you’ll see a “Future Schedule” underneath it that will show the upcoming changes.
GAUs (iDonate Designations) - SF manages the GAUs that we create for recurring donations. So if a recurring donation at iDonate has 3 designations, then SF will actually create 3 designations for the recurring donation object and then SF knows exactly what donations are associated with the upcoming opportunities.
Pledged opportunities - payment has not been made yet for this particular opportunity, but it’s the upcoming installment that is coming next (whether in the next week, month, etc. of the schedule’s run).
- SF creates the first transaction as a pledged opportunity, but then we close the opportunity, which causes SF to create a new pledged opportunity for the next installment of the schedule. If the donor updates their next run date, then the pledged opportunity will automatically update to the next installment to the correct date.
- Legacy recurring will actually generate up to a year’s worth of pledged opportunities, but enhanced recurring only generates the very next one (or no auto generated pledged opportunities if SF admin switches it off)
- A pledge is paid when we update it to “closed won” and the custom field data will be populated AFTER the transaction runs
- Legacy recurring - SF generates a whole year’s worth of opportunities, instead of the closed opportunity(s) and then the ONE pledge that ER does.
- How do we locate the pledged opportunity in salesforce? We find it by the close date.
Legacy:
Enhanced:
