Setting up Payments Plus

Note: On first install, before setting up Payments Plus ensure that all necessary accounts are allocated a payment method.

Use the Feature Console to guide you through this process. For more details, see Feature Console in the Foundations Help.

Warning: If you were using the pilot version of Payments Plus you still need to perform the following steps. If you do not, you will not have access to new functionality, such as the ability to make electronic payments.

Note:

Some of these steps are not automated. You will need to do these manually. See the Salesforce Help for more information such as creating and assigning permissions sets, button overrides, and adding new values to existing picklists.

The steps you must perform are:

1. This is a manual step. Replace the override of the view action on Payments with paymentview.
   
   Classic mode
   1. Select Setup | Create | Objects.
   2. In the list click the Payment link.
   3. Scroll down to the section Buttons, Links, and Actions. Next to the View link, click Edit.
   4. In the Salesforce Classic Override section, select the radio button for Visualforce page, and in the drop-down list, select paymentview.
   5. Click Save.

   Click Mark as Done when complete.

   
   Lightning mode

   1. Click and select Setup.
   2. Select the Object Manager tab and use the Quick Find box to search for Payment.
   3. Click Payment.
   4. Click Buttons, Links, and Actions. On the View row, click the drop-down arrow and then click Edit.
   5. In the Salesforce Classic Override section, select the radio button for Visualforce page, and in the drop-down list, select paymentview.
   6. Click Save.

   Click Mark as Done when complete.

2. This step is automated. Click Perform to start the automated script. This adds the following new values to the Payment Status picklist on the Payment custom object:

   • Account Removal Error
   • Media Prepared
   • New
   • Preparing Media Error
   • Proposed
   • Ready to Post

3. This step is automated. Click Perform to start the automated script. This adds Electronic as a new value in the Payment Method picklist on the Payment Template custom object.
4. When you have completed all steps, click the Status slider in the Feature section to enable Payments Plus.

Payments Plus Enhancements

Payments Plus has been enhanced so that you can create check payments at invoice level instead of account level, if required. You must enable this enhancement using the Payments Plus Enhancements Feature Console feature.

Work through the steps in the order shown.

• For each automatic step, click Perform. When the step has completed, the Status changes from "Not Done" to "Done".
• For each manual step, follow the instructions on screen then click Mark As Done when the step is complete. More information about performing the manual steps is provided below.

When you have completed all the steps, use the Status slider in the Feature section to enable the feature.

When you have enabled the feature it is recommended that you update the following:

• Payment Details Template. If you use templates, you can create a new template specifically for accounts that you want to create invoice level payments for.
• Accounts. Include the Check Per PIN value to the payment method picklist values on the Account object. You can then change the payment method to Check Per PIN for accounts that you want to create invoice level payments for. You can use this payment value to filter accounts when creating payment proposals.
  

For more information, see "Updating Picklist Values" in the Salesforce Help.

Adding a Blank or Empty Payment Details Template

If you do not want to use the default template, or if you want to begin a payment with all the fields clear, you can add a blank or empty template:

1. Click the Payment Details Templates tab.
2. Click New.
3. In the Payment Details Template Name field, type No Template.
4. Click Save.

At the Payment stage, the template is now available to select in the Payment Details Template picklist.

Custom Settings

Some aspects of Payments Plus are controlled by custom settings. For more information, see Payments Plus Options.

Also, ensure that your GLA Filtering in Payment Selection custom setting is configured correctly.

Check and Remittance Printing History

Prerequisites

You must have installed and configured the FinancialForce Conga Integration for Accounting as explained in the FinancialForce Conga Integration guide available from Community.

Setup

The administrator can enable history tracking on the Checks Printed and Checks Print Date fields. Any user with the necessary permissions to view those fields can then track the check printing history by writing a report.

To do this follow these steps:

1. Select Setup | Create | Objects. Using Lightning ExperienceClick and select Setup.
2. In the Label column click Payment. Using Lightning ExperienceSelect the Object Manager tab and use the Quick Find box to search for Payment. Click Payment.
3. Scroll down to the section Custom Fields & Relationships. Click Set History Tracking. Using Lightning ExperienceClick Fields & Relationships. Click Set History Tracking.
4. In the Track Old and New Values section, for checks select Checks Print Date and Checks Printed. For electronic select Remittances Print Date and Remittances Printed.
5. Click Save.

A history of your check and remittance printing will now be saved. In the payment detail see the section titled Activity History.

Chart of Accounts Structure

Corporate GLAs or local GLAs are used depending on the company's settings and the individual user's settings for the alternate account (Corporate GLA or Local GLA). For more information, see What is a Chart of Accounts Structure?.

Send Notifications from a Custom Email Address

By default, Payments Plus sends notifications from a randomly generated email address. To send notifications from a specific email address, you must:

1. Configure a custom email address as an Org-Wide Email Address.
2. Create a custom email address field in the FDN Background Processing Settings.
3. Specify the org-wide email address in the newly created custom field

You can receive notifications for the following Payments Plus processes:

• Post & Match Payment
• Create Payment Media
• Void Payment
• Discard Payment
• Remove Payment Plus Account

Configure an Org-Wide Email Address

To ensure that Payments Plus sends notifications from your custom email address, you must set this address as an org-wide email address. Then you can create a custom email address field and enter your org-wide email address.

Note:
Org-wide email addresses are a standard feature of Salesforce and are linked to user profiles. The user running the notification process must have access to the correct profile in order to send notifications from an org-wide email address. Before you can use an org-wide email address for the notification process, Salesforce must verify it. For more information, see "org-wide email addresses" in the Salesforce Help.

Create a Custom Email Address Field

Create a new custom field in the FDN Background Processing Settings so that you can specify your org-wide email address for Payments Plus notifications.

To do this, perform the following steps:

1. From Setup, click Custom Code | Custom Settings.
2. In the Custom Settings list, click FDN Background Processing Settings.
3. Click New.
4. Select Text, and then click Next.
5. Enter a field label. We recommend using a label that refers to the org-wide email address, for example: FinancialForceOrgWideEmailAddress.
6. Enter FinancialForceOrgWideEmailAddress in the Name field.
7. Enter 255 as the maximum length for the text field.
8. Click Next.
9. Click Save.

Add a Custom Email Address

To receive Payments Plus notifications from a custom email address, you must specify it in FDN Background Processing Settings.

Note: Before you can specify your email address, make sure that a custom email address field exists in the FDN Background Processing Settings. For more information, see Create a Custom Email Address Field.

To do this, perform the following steps:

1. From Setup, click Custom Code | Custom Settings.
2. In the Custom Settings list, click Manage next to the FDN Background Processing Settings label.
3. Click Edit.
4. Enter the email address you want in the custom email address field. You must enter the same email address that is currently set as the org-wide email address.
5. Click Save.

Enabling the Asperato Service for Outbound Payments for Vendors

This feature enables you to pay vendors using the Asperato service. When making an outbound payment using Asperato, Payments Plus can automatically create, post, and match the related cash entries. Only authorized vendors can receive outbound payments via Asperato so you can use this payment method for specific vendors and currencies.

To start using the Asperato payment method for vendor payments in Payments Plus:

1. Ensure you have installed FinancialForce AccountingSpring 2022 (Package Version Number: 2022.202). For more information, see Upgrading to Accounting Spring 2022.
2. Ensure you have multi-currency enabled in your org. The Asperato service for outbound payments for vendors feature is only available in multi-currency orgs.
3. Enable the following features in the Feature Console:
   • FFA Payments Plus
   • [Optional] FFA Payments Plus - Enhancement
   For more information, see Enabling and Disabling Features in the Foundations Help.
4. Ensure you have installed the latest version of the FinancialForce Asperato Integration package (Asperato Integration Spring 2022 - FF Asperato ONE Integ. Version 2022.207 or later). For more information, see Installing the FinancialForce Asperato Integration in the Integrations Help.
5. Ensure you have installed the latest version of the Asperato ONE package (V2.20 or later). For more information, contact Asperato Support.
6. Contact Asperato Support to enable outbound payments. If applicable, this may also include steps to migrate your org's multiple Asperato customer IDs to Merchant Groups if this has not already been done previously.
   Notes:
   

   If you have an existing bank account linked to an Asperato Customer ID, you may need to update it with a new Customer ID provided by Asperato, or link it to the applicable Merchant Group.

   For more information on configuring bank accounts for Asperato, see Configuring Bank Accounts with Asperato Merchant Groups or Asperato Customer IDs in the Integrations Help.

7. Set up Asperato ONE. For more information, see the Asperato ONE documentation.
   Notes:

   For outbound payments, Asperato uses Airwallex as the Payment Service Provider (PSP). You must configure at least one Airwallex account in Asperato ONE. To facilitate bank reconciliation in FinancialForce Accounting, we recommend creating a separate Airwallex account for each Accounting company that wants to use Asperato for vendor payments from Payments Plus.

   Create a separate bank account in FinancialForce Accounting for each currency that you need to make payments for from your Airwallex (account) wallet, using Payments Plus. For example, you must set up two bank accounts in FinancialForce Accounting to correspond to each currency in your Airwallex (account) wallet if you have:

   • An Airwallex account for an Accounting company:
   • With an Airwallex wallet balance for EUR
   • With an Airwallex wallet balance for GBP

   Transfer funds into the “Airwallex” FinancialForce Accounting bank accounts (via a cash entry or journal) before starting to use the Asperato Outbound Payments service.

   The names of the Merchant Groups created for the Airwallex Payment Service Provider (PSP) must match your Accounting company names.

8. Add the following fields to the Authorisation Outbound Layout page layout of the Authorisations object in Asperato ONE (asp04__Authorisation__c):
   • Account (ffasp__Account__c)
   • Currency (CurrencyIsoCode)
   For more information, see Configuring the Asperato Integration in the Integrations Help.
9. Add the Authorisations related list to the page layouts for the Account object. For more information, see Configuring the Asperato Integration in the Integrations Help.
10. Customize the Payment Method picklist on the payment proposal page. To do this, add Asperato as a custom value to the Payment Method field of the Payment object (​​c2g__codaPayment__c).
    Note:

    You can also add the Asperato payment method to the payment details templates in Payments Plus. To do this, add Asperato as a custom value to the Payment Method field on the ​​Payment Details Template object (c2g__PaymentDetailsTemplate__c).

11. Add the following fields to the layout of the Payment object (c2g__codaPayment__c):
    • Local Clearing System
    • Payment Destination
    • Payment Media
12. Customize the transaction retrieval criteria. To do this, add the following custom values to the Payment Method field on the Account object (c2g__CODAPaymentMethod__c):
    • Asperato - Domestic
    • Asperato - Domestic - ACH
    • Asperato - Domestic - Bank transfer
    • Asperato - Domestic - BANK_TRANSFER
    • Asperato - Domestic - BPAY
    • Asperato - Domestic - FAST
    • Asperato - Domestic - FASTER_PAYMENTS
    • Asperato - Domestic - Fedwire
    • Asperato - Domestic - FPS
    • Asperato - Domestic - GIRO
    • Asperato - Domestic - RTGS
    • Asperato - Domestic - SEPA
    • Asperato - International
13. To use the Asperato service for outbound payments for vendors in Payments Plus, internal users must have the following Asperato ONE and FinancialForce permissions assigned:
    • Accounting - Payments Plus
    • Accounting and Billing - Select Company
    • Asperato Outbound Payment Creation
    • Asperato Outbound Authorisation Creation
    • Asperato Outbound Full Admin (for users who need all the permissions for the outbound payments functionality in Asperato ONE)
    • Asperato Standard User
For more information, see Permissions in the Integrations Help.
14. Complete the standard tasks related to setting up the Asperato Integration. For more information, see Administrator Guide in the Integrations Help.

For more information about the Asperato service, see Introduction in the Integrations Help.