Matching Rules - FAQ

1. Why is the Account missing on the Payment Txn?

This may happen for organisations that are using the Nonprofit Success Pack.

For some background: In standard Salesforce, a user would normally create an Account first, then setup the related Contact.

When Payments2Us goes through the matching process to locate contacts and create/update Accounts/Contacts and if it needs to create a new Account/Contact then in a standard Salesforce instance, it creates the Account First, then the Contact.

However, when the Nonprofit Success Pack (NPSP) is being used, Payments2Us does NOT create the Account, it simply creates the Contact and the NPSP automatically creates/manages the Household Account for that contact.  I.e. Payments2Us are not in control of the creation of the Account and do not have access to the details about the account at the time of processing.

Should your desire to have the Account on the Payment Txn, you'll need to add your own Flow to populate this.  Setting up and providing advise on custom Flows is outside the scope of our standard support - If you need assistance, please contact your Salesforce partner or purchase a premium support pack.

2. What date is used on the opportunity close date?

When a opportunity is created, the close date is set to the related Payment Txn - Bank Deposit Date and NOT the transaction date.

The primary reason for this is some organisations will integration Opportunities to their Finance system and this reflects the date the funds were actually received in their bank account.

If you need to amend this, please work with your Salesforce admin, Salesforce consulting company or our Premium support to create a flow to adjust this.  Alternatively, simply add a field on the Opportunity with a type of Date and an API name of Transaction Date.  The like for like copy of fields from the Payment Txn will then populate this field.