Preparation
Before enabling recurring support for Salesforce, you'll need to reach out to your Salesforce customer support representative for specific details to configure your account correctly.
Enabling recurring support in Qgiv without the proper configuration on the Salesforce side will result in export errors until the account is properly configured.
You have two options on the Salesforce side:
- The Legacy setting will create all pledged installments of a recurring donation at the point when the first gift that’s part of a recurring donation is exported from Qgiv to Salesforce.
- The Enhanced setting creates only one pledge installment at a time. Another important thing to note about the Enhanced setting is that when you export multiple recurring gifts at once the date of the opportunity will be updated to the export date. Turning off the option to create next installment within Salesforce prevents this.
Setup
The Create Single Opportunity Per Transaction toggle is the new default for new integrations. Rather than creating an opportunity per line item of the transaction, an opportunity is created for the entire transaction with this setting. If you’d like an opportunity per line item instead, simply toggle this option off. To enable this feature in a pre-existing integration, manually toggle this setting on in your integration settings.
To get started, toggle on the Enable Recurring Support? option.
Three drop-down menus will appear that are specific to recurring support.
- Salesforce Recurring Version automatically indicates which version of Salesforce (Enhanced or Legacy) recurring support is enabled for. If you upgrade your Salesforce version at a later date, you can select a new choice here and save your settings.
- Recurring Status Reason due to Changes contains statuses you created in Salesforce related to changes to the recurring donation. The status you select in this drop-down menu is applied to recurring donations that are changed significantly in Qgiv after they’ve already been exported to Salesforce. When a recurring donation that has been updated on the Qgiv side is exported, the status reason will be applied, the donation will be cancelled in Salesforce, and a new recurring donation that retains the unchanged details of the previous donation will be created in its place.
- Recurring Status Reason due to Cancellations houses statuses created within Salesforce when your organization configured your Salesforce account for recurring support. This status is applied to recurring donations that are cancelled. For example, if a donor wants to change a recurring donation to one-time, the recurring donation can be cancelled in Qgiv. When exported, the recurring donation will be cancelled in Salesforce and the status reason will be applied.
Once your statuses have been set, configure your other integration settings and set up your mappings. Your recurring donation information will now be exported to Salesforce whenever a transaction with recurring information is exported into a Salesforce Opportunity.
What if I Want to Upgrade from Salesforce Legacy to Enhanced Configuration?
If you decide to upgrade, you’ll want to take a few actions to avoid export errors.
Set your export frequency to manual in Qgiv BEFORE upgrading to Enhanced in Salesforce. An optional step that goes along with this is verifying that the Daily recurring frequency exists in Salesforce if needed.
Once you’ve upgraded, change your Recurring Version from Legacy to Enhanced in Qgiv, and update your export frequency back to automatic if desired.
It’s important to note that when you switch to Enhanced, the way Installment Period is displayed changes in Salesforce.
|
Legacy |
Enhanced |
|
Daily Installment Period: Daily
|
Daily Installment Period and Frequency Installment Period: Days Frequency: 1
|
|
Weekly Installment Period: Weekly
|
Biweekly Installment Period and Frequency Installment Period: Weeks Frequency: 2
|
|
Monthly Installment Period: Monthly
|
Monthly Installment Period and Frequency Installment Period: Months Frequency: 1
|
|
Quarterly Installment Period: Quarterly
|
Quarterly Installment Period and Frequency Installment Period: Months Installment Frequency: 3
|
|
In the Legacy configuration, the Installment Period uses only one word to describe the recurring installment period.
|
The installment period and frequency together define when the next installment will be billed. For example, with a quarterly donation this means a new installment is created once per quarter three months after the last installment was received.
|
Speaking of Salesforce installment periods, if you use a frequency in Qgiv that isn’t present in either the Legacy or Enhanced configuration of Salesforce, you’ll need to create that custom installment period in Salesforce. Instructions for adding custom installment periods for both Legacy and Enhanced configurations are shown below.
1. If you plan on using a Daily, Bi-Weekly, or Semi-Annually recurring frequency, you'll need to add a custom installment period in Salesforce
a. Legacy https://powerofus.force.com/s/article/NPSP-Installmt-Periods-Recur-Dons
i. Daily
1. NPS Settings
a. Name: Daily
b. Time Period Frequency: 1
c. Time Period Type: Days
2. Object Manager
a. Object: Recurring Donation (npe03__Recurring_Donation__c)
b. Field: Installment Period (npe03__Installment_Period__c)
c. Value: Daily
ii. Bi-Weekly
1. NPSP Settings
a. Name: Bi-Weekly
b. Time Period Frequency: 2
c. Time Period Type: Weeks
2. Object Manager
a. Object: Recurring Donation (npe03__Recurring_Donation__c)
b. Field: Installment Period (npe03__Installment_Period__c)
c. Value: Bi-Weekly
iii. Semi-Annually
1. NPSP Settings
a. Name: Semi-Annually
b. Time Period Frequency: 6
c. Time Period Type: Months
2. Object Manager
a. Object: Recurring Donation (npe03__Recurring_Donation__c)
b. Field: Installment Period (npe03__Installment_Period__c)
c. Value: Semi-Annually
b. Enhanced
i. Object Manager
1. Object: Recurring Donation (npe03__Recurring_Donation__c)
2. Field: Installment Period (npe03__Installment_Period__c)
3. Value: Daily
2. Add a custom Recurring Donation "Status Reason" to the Recurring Donation record
What if a recurring donation is paused, a payment is missed, or the gift is cancelled in Qgiv?
If a recurring donation is paused in Qgiv, nothing will happen on the Salesforce side.
However, a missed payment in Qgiv will show as an unfulfilled pledge using the Legacy configuration because this configuration creates all pledges up front. Because only one pledge is made at a time with the Enhanced view a missed payment will not trigger an unfulfilled pledge.
If the recurring gift is cancelled within Qgiv, it will be closed in Salesforce on the next export.