Constituencies linked to memberships

Hi Katherine,

If you look at the actual membership record does anything change when you apply a payment? I noticed something similar with upgrades via DD…

Gary

I have come across what seems like a weird anomoly with constituencies created by memberships

We have a membership scheme with the option to pay monthly by direct debit or as a lump sum. When someone opts to pay monthly by direct debit the full amount is entered as a pledge with the payments scheduled across 12 months using the Direct Debits billing method. The basis amount is set as the value of their first payment. All good and working so far...

...the weirdness starts whenever I process a payment. Making a payment on the pledge inactivates the constituency created by the membership even though the basis amount has been met. The issue is not limited to direct debits we tested with a cash payment and got the same result.

Has anyone else experienced this? Is there something very simple that I am missing in the set up that woudl fix this or is this how you would expect the constituency to behave?

Thank you

Katherine

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Hi Katherine,

If you look at the actual membership record does anything change when you apply a payment? I noticed something similar with upgrades via DD…

Gary

I have come across what seems like a weird anomoly with constituencies created by memberships

We have a membership scheme with the option to pay monthly by direct debit or as a lump sum. When someone opts to pay monthly by direct debit the full amount is entered as a pledge with the payments scheduled across 12 months using the Direct Debits billing method. The basis amount is set as the value of their first payment. All good and working so far...

...the weirdness starts whenever I process a payment. Making a payment on the pledge inactivates the constituency created by the membership even though the basis amount has been met. The issue is not limited to direct debits we tested with a cash payment and got the same result.

Has anyone else experienced this? Is there something very simple that I am missing in the set up that woudl fix this or is this how you would expect the constituency to behave?

Thank you

Katherine

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!