User Support Forum

In Canada, we are required to segregate givings to "Local" based on who receipts it, and whether it is the result of donation of securities. Our members pledge to one fund - Local (let's say fund 3). Most donations are deposited to this fund (3). if they give to local by way of security donation, it is entered into fund 100 (for example), and if the donation to Local is through a third party that issues the receipt (say the United Way), then it goes into fund 101. All three funds are to benefit "Local" expenses and it is to that fund that our members pledge. Is there a way currently (PC 11.5) to recognize donations to any of these 3 funds as count towards the "Local" pledge". There is a "Contribution Fund Type" specification already - could that be used somehow to aggregate the appropriate funds towards a pledge?

pwlong wrote:In Canada, we are required to segregate givings to "Local" based on who receipts it, and whether it is the result of donation of securities. Our members pledge to one fund - Local (let's say fund 3). Most donations are deposited to this fund (3). if they give to local by way of security donation, it is entered into fund 100 (for example), and if the donation to Local is through a third party that issues the receipt (say the United Way), then it goes into fund 101. All three funds are to benefit "Local" expenses and it is to that fund that our members pledge. Is there a way currently (PC 11.5) to recognize donations to any of these 3 funds as count towards the "Local" pledge". There is a "Contribution Fund Type" specification already - could that be used somehow to aggregate the appropriate funds towards a pledge?

In a word, no.

The Pledges function expects a pledge goes toward a single fund. You can have multiple pledges, each going to a separate Contribution Fund, but they can't be aggregated.

However, nothing says you can't ask to have this functionality added to the 'wishlist'. My advice is put together an explanation of what you'd like to see, how you would expect it to work, how this will save your time and effort, and then send that to 'wishlist@powerchurch.com'.

When the developers/designers look at what they will add to the program, they look at ideas that will give the most 'bank for the buck' to the most users. If something will provide a feature that has been asked for by many users, its usually the one that gets the development time. So when you write it up, give good examples of how this will aid other users in their process.

I would be interested in this option as well. Curious if anyone has developed a work around or learned how to effectively manage this issue without PowerChurch supporting this need. Thank you.

Thanks for the suggestion. I will follow up on the wish list approach. Thanks again