We have opportunities where a member commits to a payment amount and agrees to pay with 1, 2, 4 or 10 instalments
Once the opportunity is fully paid, certain automated processing takes place. This means that recurring donations aren't really a feasible option
I've tried using the NPSP donation importer as it is end-users who will be importing the instalments, but second and subsequent payments overwrite the previous payment on the opportunity.
I've tried several of the matching options in the importer, but they either attempt to create a new opportunity or they overwrite the prior payment
Is there any way to force the importer to use the current logic to find a matching opportunity then create a new payment instead of replacing the existing one?
Data loader isn't really an option as end-users would need would need to export the opportunity IDs and then import the payments against these
Creating a Best Answer:
Add the schedule payments actions to the payments related list and generate scheduled payments for any opportunities where the member pays by instalments, then this can be made to work if you match by date and amount and set the date range to around 5 days. This works well for monthly direct debit payments as they typically are from known amounts on dates that don't vary by more than a few days each month. (They can move up to 4 days in many jurisdictions if payments are not made on holidays and weekends). In China where Chinese New Year can go on for as long as 10 days, if no DD's are made during that festival, you might need to manually schedule the payment that happens at that time to occur on the first date following return to banking business.
If you allow part payments but part paid opportunities are not "Won" then you will find that the Customizable Rollup that determines the Membership Renewal Status will show members as in Gravce Period and then Expired once the prior fully paid membership end date has passed as the Membership Renewal Status field on contact is calculated based on the Membership End Date of the latest-dated Won opportunity. If part paid membership opportunities aren't set to a stage that maps to a Closed-Won category, then the members concerned will move into grace period then expired once the grace period set up in the org has passed
To resolve this, edit the Memberships: Won Filter group under Customisable Rollups > Filter Groups
- Delete the default filter criterion Opportunity.Won = True
- I have a before save flow on the Opportunity object which sets
- the Opportunity Stage Name to be Part-Paid if amount outstanding > 0 and amount paid >0
- and sets the stage name to be Fully Paid if Amount Outstanding <= 0 (people are welcome to overpay) and Amount Paid >0
- Add a filter criterion of Opportunity.StageName in List (select all stages that you want to consider qualify the member as being current). In my case this is part-Paid, Fully Paid and Posted
