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
Could this be an issue with the script update? I suppose there is a chance that the script update is only recognizing the amount paid on the installment, and not the pledge, which might explain why the constituency is inactivated. Best of luck with this. Kindly, Mark