It would be quite helpful to be able to apply a soft credit as a pledge payment.
We have people make pledges or businesses make pledges but when their checks come in (pledge payments) they come from a donor advised fund or an individual will send in a check to apply to their business pledge or a business check comes through for an individual's payment. In turn the soft credit goes into the account of the one that made the pledge and does not get deducted from their pledge payment schedule. When running reports on the status of pledges or campaigns it is very difficult to keep this all straight. It would be helpful if we could apply soft credits to their pledge payments.
Can we resurrect this idea? Our company receives at least 10 Third Party Pledge Payments every campaign and our consultants BEST advice was to soft credit the original donor on the account the payment was made, add in the pledge payment on the original account, and then add a disbursement on the same account so that the actual received amount isn't double-counted.
The issue with this (beyond that it's tedious) is that disbursements are not accounted for in the eTap standard fund reports or campaign activity so we have to keep an external record of what our actual received amount is when we're running a campaign or setup a regular report of disbursed funds (neither of which should be necessary, IMHO). Either fix how the disbursed funds are actually accounted for in your standard reports or allow pledges to be fulfilled by other accounts.
I've run into this problem as well. Donors often will have a third party/donor advised fund send a check and it, at least partially, should be used as a pledge payment. Sometimes it is part of a split transaction too. Can't there be some way to assign the soft credit and then click off a pledge if that donor has one?
Please make it so we can apply soft credits as payments towards active pledges.
Another term would be "Third Party Pledge Payments", which is what this is most used for. At this time, I am not planning on implementing this level of functionality in eTapestry.
This, please!