Skip to main content

How do others deal with actual payments that do not align with Opportunity Payment records?

 

When donors submit payments for different amounts or for different dates than what is recorded in Salesforce, can you use NPSP Data Import to update existing Opportunity Payments without creating new Opportunities.  I created a custom "Opportunity Number" field to match on, but that seems to only work with Opps with a single Payment record.  If I am importing a payment for a second Payment record, I can't get a match, or NPSP updates my Opportunity Amount to the value of the payment. 

 

Here's a common scenario.  Donor pledges $500 so an Opp is created with a single $500 Payment.  But when the check comes, it's only for $300.  NPSP can update the Payment record to indicate that $300 has been paid.  Later, when the second installment of $200 comes in,  I can't get the data import to create a $200 Payment under the original Opportunity.  

 

Any suggestions on what to do when donors don't cooperate with my existing payment schedules will be greatly appreciated. @Nonprofit Success Pack

8 respostas
  1. 1 de jan. de 2023, 18:15

    Specifies how to match Contacts in NPSP Data Import records against existing Contacts. The rules specify which set of Contact fields to use to find matches. For example: First Name, Last Name, and Email or First Name, Last Name, and Phone. Some specific things to keep in mind:

    • The matching rules attempt to match on any NPSP phone or email field.
    • Name matching uses exact string matching, but is case insensitive. For example, "Tom Smith" would not match to "Thomas Smith", but "thomas smith" would match.
    • Phone number matching uses exact match only. For example, if the phone number's format is 123-345-4567, then you must use that format, not 123.345.4567 or 1233454567. get moreinfo with calculador de paypal mexico 2023
0/9000