Sync pending ACH donations and update the record once it’s cleared | Voters

I think the close date is the donation date but it doesn't seem to sync to Salesforce until it is actually closed in Give Lively. For example, ACH donations that are pending, don't sync over until they are actually closed. This actually causes a problem for some of our Salesforce automations because they rely on this close date. I think one idea is what John suggested, sync the donation over with the donation date and then add the close date later once it is actually closed (for the dontations that do take a few days to clear). Another option I think would be to sync the donation over regardless of the status and use the 'Stage' field to track where it is at. If it is pending, then use the Pledged status. Once it is actually closed, then used Closed Won or Posted, whatever the account default is currently. Just some food for thought.

Rose Sherman

It seems like this would be very important for ACH donations made in the last few days of December for donor tax reporting purposes, or during other fundraising campaigns that end on a specific date.

Jonathan Lin

Michael Sulja: Good context. Salesforce requires a value in Close Date to save the record, so we do have to populate it to even sync over a donation, whether pending or succeeded. We have a separate Canny request tracking the request to sync pending ACH donations, viewable here: https://givelively.canny.io/salesforce/p/sync-pending-ach-donations-and-update-the-record-once-its-cleared

Our approach is expected to track quite closely to what you've described. I am curious to hear everyone's feedback regarding how the relevant dates will be stored. Since Close Date is required at the beginning, it may make the most since to track that as the donation date, and then use Payment: Payment Date to track the date the charge actually succeeds. Thoughts?

Michael Sulja

Jonathan Lin: So after talking to the accountant, I realize that because we have the accounting subledger installed in our SF instance, we can look at the transaction date on the ledger to find the date Give Lively syncs over the donation (it's not easy to find but it is possible). However, I'm not sure that other organizations use the accounting subledger module in SF so I understand the need to do this change. If you update the Give Lively sync to now update the payment date once the ACH is cleared/charge succeeds, we are OK with that. The accountant will just add the close date to their QuickBooks report that is setup in SF so that when they export from SF and import to QB, they have it use the 'close date' and not the 'payment date'. I hope that makes sense, if you need clarification, feel free to email me direct.

Jonathan Lin

Michael Sulja: Thanks for your response! Our plan will have Opportunity: Close Date reflect the date the donation was initiated, and Payment: Payment Date reflect the date when the payment was received. The hope is that this will offer the important data for the vast majority of our member organizations without necessitating a new custom field.

John Bono

Jonathan Lin: Could you clarify in Stripe terminology, what "...Payment: Payment Date reflect the date when the payment was received" reflects? Is it the payout date (https://dashboard.stripe.com/payouts/)?

Jonathan Lin

John Bono: Sorry to keep you waiting. Your question kicked off a longer internal discussion. To summarize briefly, the date we'd be using for payment received doesn't directly correlate to payouts. Rather, it's a type of event that we can track via the Stripe API: https://stripe.com/docs/api/events, and then (likely) record as a date on our side, which would then allow us to use it when syncing to a nonprofit's Salesforce org.

Nicole Alter

marked this post as

under review

Jonathan Lin

This would be nice. The current behavior causes some confusion among staff.