9 answers
@Seban Babu Based on what SF stated, I don't believe it would be automatic. you'd have to set something up to trigger it to change to completed or manually update.
#Recurring0 discussing
- Recent Activity
- Created Date
- Recommended
- All Questions
- Questions with an Accepted Answer
- Unanswered Questions
- Questions with No Accepted Answer
Hi,
I would like to know if it's possible to disable or modify the default mapping of the amount field between Recurring Donation and Opportunity?
The reason behind this is because we want the first Opportunity amount to be bigger then the following Opportunities amount. Because of the default mapping NPSP always modifies the amount on the opportunity to the amount of the Recurring Donation and this is what we don't want.
Is there somebody who already came across this issue before and has a bypass for it? Or knows how to disable the mapping?
Link to the documentation: https://help.salesforce.com/s/articleView?id=sfdo.NPSP_Map_Recurring_Donation_Fields_to_Opp_Fields.htm&type=5
Thanks
2 answers
Hmmmm you're on enhanced recurring donations, yes? I did something similar where I wanted whatever the LATEST donation was to be a different amount. In my use case the amount changed installment by installment. After messing about with it for a while, I found the only way to change that installment amount on an open installment was to change the PARENT RECURRING DONATION AMOUNT, and I set it up/automated it that way. I wonder if that might be possible with the first donation -- you would need some sort of automation that set the RC amount to X and then at a later point reset it to Y so subsequent installments were made with Y. This is technically very doable, but the question is -- does it work with your use case? How many installments do you need extant at any given time?
Batch Number is not being populated for entries that are updating existing opportunities when the batch is processed, e.g. when we are marking Pledged #Recurring Donations​ as received (opportunity stage Closed Won equivalent). It is populated fine when new opportunities are created.
I've created a workflow to copy from our former custom field for Gift Batch Number for now as our team manually enters this number when matching an opportunity (because batch defaults are overwritten by opportunity fields when selecting one to match).
Hopefully I've explained that correctly @James Browne​ ​
8 comments
The trouble with a flexible system and people using it lots of different ways - functionality can't always suit everyone's way of working :)
We went live yesterday with new Gift Entry, and despite testing in sandbox, have some issues, mainly regarding the matched opportunities.
We have thousands of recurring donations and hundreds of online purchases to match up in gift entry.
When finding an opportunity to match up and processing batch, they do not appear to be using the Close Date and Stage in the default values of the batch header. I haven't tested amount yet.
Is there any detailed documentation on how this is expected to behave? When the defaults are or aren't used? If it is possible to define which ones should use the defaults regardless of the opportunity details?
I'm waiting for the partial sandbox to spin up before I can test more thoroughly - the old one was broken by the recent NPSP update pushed to sandboxes presumably regarding the new npsp data import fields for recurring donations (most of which I'd already manually created).
14 answers
Hi @James Browne​, Yes Richa was on the case so we found the missing permission that was needed - the Elevate status field on Payment object (for anyone with the same issue let me know if you can't see the case with the details).
Just working with Finance on the most efficient way to deal with the defaults not being used for matched items business - probably mass update from a list view as we'll make sure our custom batch number field is populated..
thanks for all your help.
Hello!
Is it possible to process recurring donations in Gift Entry? I created a mapping the Recurring Donation object but when I try to process the batch I receive the following error: "Recurring Gift Import Status: You must select an Account or Contact." I have the Contact 1 and Account 1 fields in the batch and it seems to just create a opportunity record and not the recurring donation. Does another mapping need to be created for the recurring contact or account?
Thank you!
We have Donors that want to donate twice in a month, but not on the 1st and 15th (they are choosing their dates). Would we ever be able to configure that in the ERD? Otherwise we have to create two sets, and I don't believe that was the goal for ERD's. Also, having more than one is messing with some customizations we have (which is another thing I need to figure out).
@RecurringDonations
Thanks,
Mia
3 answers
Hi @James Browne​ , I added Daily to the list, so i see now what you are referring to. However, you lost me on the rest. The Donor asked for the 11th and the 17th. How would you set it up?
When one of our recurring donors would like to change their recurring giving amount (typically a monthly gift), we cancel their plan (open-ended status = closed) and create a new one for the amount they'd like to give so the calculations of what they've committed to versus have remaining are correct. We do this because the majority of our donors are fixed/non-open-ended donors who have agreed to give for a set number of months, typically 12, and if we just changed the amount of their giving the calculation of their total expected and total remaining would be off.
Curious...do you have fixed recurring donors in your org and, if so, how does your org update giving amounts and calculate amount committed vs. outstanding and does this work well for you?
Thanks!
3 answers
@Morgyn-Britney Abbey​ I know what you've described is pretty common in general, but I'll leave specific advice for the Community (cc'ing the @Fundraising​ and #Recurring Donations​ folks). You'll be happy to know that the new #Enhanced Recurring Donations​ product allows you to modify the dollar amount (and other fields) of a Recurring Donation and set a specific "Effective Date" so the change can be applied in the future automatically. Meaning, if you get a donor calling in to increase the amount they are giving but ask for it to start in two months, you can set that up on the existing RD, and forget it. On the effective date, the change is applied. Also, only 1 future Opty is created and the totals are a bit different, so you shouldn't have any options with Fixed Length.
Check out the upgrade guide to see if updating is right for your org 🙂
Seeking help on an error that occurred during attempt to Validate Data in advance of upgrading to #Enhancedrecurringdonations​ :
"There were one more errors updating or inserting the following records: * 0011I00000DRtcjQAD: UNABLE_TO_LOCK_ROW- unable to obtain exclusive access to this record or 32 records: 0011I00000DRtcjQAD,0011I00000DRtcmQAD,0011I00000DRtczQAD,0011I00000DRtd0QAD,0011I00000DRtdNQAT,0011I00000DRtdeQAD,0011I00000DRtdjQAD,0011I00000DRtdlQAD,0011I00000DRtdmQAD,0011I00000DRtdpQAD, ... (22 more) *"
Can anyone help me identify how to fix this error/what the issue is?
Thanks!
Claire
@Nonprofit Success Pack​ @Fundraising​ #Recurring Donations​ #Errors​
Hi,
After some advice/opinions on how non profits are dealing with Failed, recalled or refunded Direct Debit payments.
We use the Recurring Donation functionality within NPSP to handle our Direct Debits (both BACS in UK and SEPA in europe).
Each month, we run a claim and change all "Pledged" opportunties to "Posted". If any fail, or are recalled (which seems to be quite common in europe for SEPA dds), we mark the opportunity as Failed, amount set to 0.
Whilst this works ok from a supporter record perspective, our finance team dont like it. They want to see the +ve entry for the claim, then a corresponding -ve one for the failure/recall - so SF matches exactly what happens in our bank account.
So they want to see 2 opportunties like this:
05/04/2020: €10 Posted.
12/04/2020: -€10 Refunded/Failed
Before thinking about the technicalities of how this might work, is this even possible under a recurring donation? can we just insert opportunities like this and link them to the RD record? will that work and not affect roll ups, or the way it creates future opps?
And in general, how do people deal with refunds on single donations? Do you create -ve opportunities for this?
I know each Opp has a payment object that could possibly help with this, but it wont work for us. We have a separate "Transaction Allocation" object underneath opportunity, which codes the donation against the correct GL code for finance. (So 1 £10 donation can be split £5 against GL Code A and the other £5 against GL Code B). its this level we report on income - so having an +ve and -ve payment wouldnt work for us.
Interested to know how other people handle this, so i can come up with a feasible solution for our Finance Director.
Thanks in advance for any help.
James
2 answers
Adding in @Fundraising​ and #Recurring Donations​ for greater reach on your question.
I'll defer to others, however it's not common from my experience to create two Opportunities in the manner you've described when using Recurring Donations. Also, it's not common to mark the stage as Closed/Lost and then change the Amount to 0. I can see why your finance team isn't pleased :). More often, the Payment object is used for this purpose. You can mark the Opty as Closed/Lost, and then mark the related Payment record as "Written Off" rather than paid which will accomplish half of what your team is looking for. You may consider looking into using the @Accounting Subledger​ product.
Also, just note that we've released an update to Recurring Donations (called Enhanced Recurring Donations) which does't create extra Opty's or negative Payments, but does have some other really great functionality. Take a look and consider upgrading.
6 answers
We use additional ​picklist values - sustaining and new sustaining. This allows us to customize our thank you letters/emails.