NSPS Payment object and recurring gift opportunities

[BeverlyMIS]

Several of my clients have Salesforce NPSP set up to create a payment record when an opportunity is created. That is working fine on nearly all of the opportunities, including the opportunities that are created for recurring gifts. When I spot checked them, it appears that this is working fine on the first recurring payment is done at the same time the recurring gift is set up, however when it is entered with a first payment date that is later than the date it is entered, the zero opportunity is created for the preauthorization, but on that opportunity and on subsequent opportunities with an amount is created, no accompanying payment record is created.

Since we are using the payment records for a number of reports, this is causing a problem. Can you tell me if this is a known issue, or something new and whether it can be corrected?

I'm seeing this pattern on a couple different clients, but the one that is easiest to see it on is WERU (Salt Pond Broadcasting). SF # 0Do0000000e6Y2 and you do have login access.

You can see a number of these on the report linked here

There are a bunch of them here because Click and Pledge did a data upload from a previous card processor starting 4/6/16 and these are all the ones that are not creating payments.

[BeverlyMIS]

Hi All - can you let me know whether you have come up with any thoughts on this or if you need more information. I really need to get back to the client, and if it's a known issue, I also will want to modify the way we're running some reports. Please let me know the status.

[CnP.Support]

Good day @BeverlyMIS,

Sorry for the late reply -this was missed.

Currently the $0 pre-authorization creates an opportunity by design. It posts to Salesforce and Opportunity is being created with the total of $0.

This feature has already been requested by others and in release 10.x we are adding an option for not creating opportunity for $0 donations. This also extends to free items, etc.

Sorry that at this time there is not a work around.

[BeverlyMIS]

OK - I get that, but it actually isn't the gist of my question. The issue is not the zero opportunity, it's that the subsequent opportunities that are not zero opportunities are not creating the associated payment object record, but recurring gifts that don't start out with a zero opportunity record do create the associated payment object record. I'm asking about why there is a difference there because we are using the payment record to track information in reports that are used for accounting purposes. Basically, we're using the information in the payment object to create deposit reports that match what is going into the bank regardless of where it is coming from. So, when some of the recurring gifts are creating payment records, but others are not, it is causing a problem.

So, what I'm asking is what is causing the difference in the way this record creation is being handled and is there any way around it?

[CnP.Support]

Good day!

NPSP does not create any payment records for $0 opportunities. We have discussed this in the past with NPSP and they are aware of this and may add the feature in a future release.

Is this what you are asking about?

[CnP.Support]

Good day!

I would like to add one point here for clarification.

When a future date transaction occurs we perform the following steps:

1. Initial create a $0 pre-authorization opportunity
2. When the payment processes we UPDATE the previous opportunity with the correct amount, stage, and the order number.

Unfortunately NPSP does not create a PAYMENT record for $0 amount and as such the payment record is not created when the pre-authorization occurs. When we update the opportunity with the right amount, NPSP completely ignores it.

We understand the situation and have resolved it in the next update where we do not UPDATE the previous opportunity and create a new one. We are also adding an option for not creating opportunity when the amount is $0.

The present behavior is by design since our clients did not want 2 opportunities for a single future date transaction. Regardless of what we do, clients using NPSP and those not using NPSP wish for different behavior. With the update due out by the end of the month you will have the option to address this.

Hope this further clarifies the scenario you are experiencing.

[BeverlyMIS]

Thank you so much, that explains it. I'll pass this on.