#Recurring Donations0 discussing

In early 2022, the org I'm consulting for loaded all of their recurring donations into Salesforce, but since then the Last Donation Date (npe03__Last_Payment_Date__c) field has not updated. Both Next Donation Date and Effective Date are working.

#Enhanced Recurring Donations #Recurring Donations #npsp

I am trying to set up an extended mail merge and the file has fields from both the Opportunity and Recurring Donation Objects. I can get the Opportunity fields to show up, but can not see fields from Recurring Donation on the file when I execute the Mail Merge. Is there a way to get Recurring Donation fields into a mail merge?

As I understand it, when we create a recurring donation for a Household account, we have to set a contact.  If we try and save a recurring donation without a contact, we get the error message 

• You must select a Contact associated with this Household Account.

We have households with recurring donations that (for tax reasons) should not have a contact.

Is there any way to disable this check and create a recurring donation linked to a household without setting the contact?

Thanks

Anyone else getting errors since the upgrade with the recurring donation overnight job?

I'm seeing about ten a night of these and wondering if it is my automation for recurring donations and opportunities causing the error, or if it is a new release thing @Nonprofit Release Readiness:

"Today's scheduled npsp.CRLP_RD_BATCH batch job was skipped because a previous npsp.CRLP_RD_BATCH job was still running. The next batch job will run as scheduled. No action is required; this error is for information purposes only." 

Thanks.

for monthly donors....

Anyway to make the receipting for monthly donors automatic?

Mr. John Doe hasn't been issued one for last year. Because he is a monthly donor.   

We have donors that pledge a multi year donations. For example, a $50k donation that will be paid in $10k increments once per year. Would LOVE to receive feedback from anyone on the following.

- Do you recognize revenue for these future 'Pledged' donations when that pledge is made or only as the cash is received each year?

- If you recognize the revenue, does it all get recognized in the current period or do you defer/amortize any of it?

- Do you enter this in as a Recurring Donation or a single Opportunity with a Payment schedule?

- For the purposes of the Contact/Account rollups, do you consider this a single $50k donation or five $10k donations? If using Recurring Donations and considering it as a single $50k, how are you working that into your rollups on the Contact without double counting?

TIA for any feedback. Looking to see how everyone is doing this so we can align on best practices! :)

is exploring new ways to support entering Recurring Donations in Gift Entry. Do you use recurring donations? Do you have preferred workflows for processing recurring donations? And many more questions!

If you're interested in sharing your thoughts and feedback (especially if gift entry is part of your day to day job) let us know! Message me or email me at

.

Thank you and hope your November has been off to a great start.

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​ ​ 

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).