I am trying to deduct a payment to a corporate constituency pledge that was entered several months ago. The pledge shows up on the individual record, but doesn't appear as an option in the "existing contributions" window within the contribution batch. I've seen several people post similar issues on this forum, but haven't seen a clear solution that applies to my problem. Any ideas?
If it helps, when the original pledge was entered, it was backdated. The campaign and appeal are "rolling", though, and still open.
This is a shot in the dark, but is the source code inactive? Are you entering the individual constituent's ID during gift entry, since that's where the gift lives?
The constituent ID I'm entering in the contribution batch is the same one that the pledge was entered under. The source code is still active, and its under a rolling campaign that's expiration date is set out in the future for about another five years. I'm running out of ideas!
Did you find a fix for this? First time I'm running into this issue, but I'm thinking it's similar. Thanks!
Hi Courtney,
There are two ways I know of that this happens. Our most common is soft crediting. If a Patron pledges $5,000 and says they will pay through their family foundation, the pledge is put on the family foundation and soft credit goes on the Patron's record. (It should show up in green, you may have to click onto another contribution for it to change color.) When it comes in you have to go to the family foundation record to pay it. If you open the Patron's record, despite 'seeing' it in that record, it is not payable from there.
For business units, we have our Society (annual) and Foundation (endowment). They have separate batch types and if I open a Society batch I can't pay down a Foundation pledge (and vice versa).
Hope that helps.
Ann
Hi - sorry for the slow response,
We did solve the issue, eventually. It turns out with us there was a problem with the Business Unit associated to the contribution/pledge. We couldn't ever really figure out how the issue originated (my organization is a part of a larger consortium, and in house, I NEVER deal with Business Units - I didn't even heard of them until I had this issue) and our system administrator who operates out of the building actually found out that there wasn't a Business Unit used for the pledge when it was created, but one was added to the batch type after the fact. So, when I tried to apply a payment to that pledge, it wasn't showing up because it wasn't associated with a BU. My administrator just updated the contribution record to give it a BU, then I could work with it as normal.
I hope that makes sense. I'd be happy to e-mail you the e-mail chain that ended up solving my problem, if that's helpful.
Thanks for the information! I'll look into the BU issue. I was able to work around the issue by skipping the payment when it popped up initially while entering my batch, then entering the source code and the associated pledge popped up. I added the payment information once I was already in the pledge and it seemed to work. Kind of odd but a good work around until I can figure out what's going on. Thanks again!