Release Notes - January '20

We are happy to present you the FinDock January ’20 Release Notes. There are no manual actions required to continue using existing functionality. For new features manual actions are required.

Important Dates:

  • Release to Sandboxes: January 5, 2020
  • Release to Production: January 20, 2020

FinDock support for the Swiss market

Swiss bank statement reconciliation

The ISO 20022 message standard defines the following Cash Management Messages:

  • Bank-to-Customer Statement (camt.053)
  • Bank-to-Customer Debit/Credit Notification (camt.054)

This release introduces support for both message types for the Swiss market. In the Swiss market, it’s possible to receive CAMT files from PostFinance (the financial services unit of Swiss Post) with images of ESR (Einzahlungsschein mit Referenznummer) Payment Slips attached to the bank statement report. The collection of files is delivered as a zip file. In FinDock we now support the upload of this zip file to ProcessingHub. FinDock creates the transaction set and transactions similar to a regular CAMT file upload.

The images are added as attachments to the corresponding transactions. The images are delivered in TIFF format. Salesforce doesn’t support preview of TIFF files. However, on the target level you can change the file format to PNG to preview the file in Salesforce. A very common use case for this is previewing the file during the guided review process to match the transaction to a donation.

How to enable:

To enable this functionality, the Swiss Payments for FinDock package needs to be installed and configured.

Swiss Direct Debit procedure (Swiss DD)

The message standard recommended by Swiss financial institutions is based on the ISO 20022 standard. For collections from PostFinance, the collection type "CH- DD" (based on the PostFinance "CH-DD direct debit (Swiss Direct Debit)" procedure) under the Swiss ISO 20022 payment standard applies. For collections from banks, the collection type "CH-TA" (based on the banks "LSV+/BDD" procedure) under the Swiss ISO 20022 payment standard applies.

Swiss payment standards

PostFinance "CH-DD” direct debit

FinDock supports direct debit payments via PostFinance. It is suitable for companies that regularly collect amounts in francs or euros and want to offer customers a simple and convenient mode of payment. Via FinDock we support both the Customer Direct Debit Initiation (pain.008) and the Customer Payment Status Report (pain.002).

LSV+/BDD "CH-TA” direct debit

FinDock supports direct debit payments via the LSV+. LSV+ is the process offered by Swiss banks for processing direct debits with the right of objection. It is suitable for companies that regularly collect amounts in francs or euros and want to offer customers a simple and convenient mode of payment. Via FinDock we support both the Customer Direct Debit Initiation (pain.008) and the Customer Payment Status Report (pain.002).

How to enable: To enable this functionality, the Swiss Payments for FinDock package needs to be installed and configured.

SIX Saferpay for FinDock

FinDock supports Six Saferpay as a Payment Service Provider. Both single and recurring transactions are supported for credit card payments.

How to enable:

The Saferpay functionality is part of the Six-Saferpay-for-FinDock package.

Swiss ESR code generation

Via the Swiss Payments for FinDock package, the ESR payment method is supported. With this payment method, you can create Installments with a valid ESR code that can be shared with the customer. With the reference generator (beta), you can generate ESR codes on any field on any object in Salesforce. Two subtypes of ESR codes are supported: based on the SFDC record ID or ‘bring your own.’ With the latter type, you can define your own pattern of ESR codes to be able to reconcile easier afterwards.

How to enable: To make use of the payment method ESR, the Swiss Payments for FinDock package needs to be installed and configured.

The reference generator is available as a Salesforce tab in the Lightning Experience App launcher for all customers who installed FinDock. Users need to have create, read and update access to the Reference Generator Run object and its fields. Also the object-tab needs to be visible for their profile and the Lightning component “Reference Generator” is placed on the Reference Generator Detail page.

Other new features

Targets to Salesforce

Currently target information is stored in the ProcessingHub account attached to the FinDock Salesforce environment. After this release, the target information is stored in Salesforce as custom settings. With this change we finished the journey to bring all customer-specific settings to Salesforce and out of ProcessingHub. This will set us up for automatic, smart deployments and already gives you the ability to deploy FinDock from org to org without having to manually enter any information.

To complete this change, a migration script will be run in the background. This process is managed by FinDock and no manual action is needed.

NPSP Field Mapper for Opportunities and Installments

The FinDock-for-NPSP Opportunity Installment Field Mapper allows organizations to customize in more detail how Installment and Opportunity records are synced on field level. This removes the need for custom triggers or process builders to sync fields between Installment and Opportunity.

How to enable:

The new field mapper is auto-enabled for new orgs and cannot be disabled. So this section applies only to existing orgs. After enabling, the toggle will not be shown anymore. In the unlikely case that an organization wants to disable this feature, this can be done by logging a case with FinDock support.

Enabling this feature without adding custom mappings changes the behavior of the system. For the following fields, the synchronization is triggered bidirectionally instead of only on Opportunity changes:

  • AccountId
  • Primary_Contact
  • Amount
  • Payment_Method
  • Payment_Profile
  • Payment_Processor
  • Target
  • Due_Date

This change may impact your customizations, so we do advice to perform regression testing after enabling this feature.

Checkout.com for FinDock

FinDock supports Checkout.com as a Payment Service Provider. Both single and recurring transactions are supported for credit card payments. The Checkout.com for FinDock package also supports single payments via Bancontact or iDEAL.

How to enable: To enable this functionality, you need to install and configure the Checkout.com for FinDock package.

Bug Fixes and Enhancements

Batch manual review - opportunity creation

Issue: Processing transactions via Manual Review Batch Process didn’t create opportunities when using the FinDock for NPSP connector.

Solution: The Manual Review Batch Process is updated so that in the case of NPSP the opportunities are created.

Status on multiple Installment matching

Issue: When matching to first (oldest) non-Collected Installments, we now match to the Installment with status not equal to ‘Collected, even if that’s a closed status, like ‘Reversed.’

Solution: In the previous release we introduced the concept of ‘open’ and ‘closed’ status. Matching on multiple installments should take the oldest OPEN Installment. Not only on non-Collected, but a non-closed status.

‘+’-signs in account holder name

Issue: Account Holder Names containing '+' are causing processing errors when using the classic manual review.

Solution: Plus (+) signs were not escaped in the queries and therefore lead to SOSL exception errors. The values are now correctly escaped.

Null value in bank statement for iDEAL payments via Buckaroo

Issue: When iDEAL payments were conducted via the Buckaroo for FinDock package there was potential room for a null value in the customer’s bank statement description for Ideal payments.

Solution: Across all payment methods, the Buckaroo for FinDock package fills the Buckaroo invoicenumber attribute with the Installment-id. This solves the potential room for null values in the customer’s bank statement description.

How to enable: Contact FinDock support to enable this enhancement.

New method to get updates for transactions via Buckaroo

Issue: The FinDock PSP extensions listen to webhook notifications from their specific payment service provider. On the Buckaroo for FinDock package, we added a second, backup method to handle updates on transactions.

Solution: To the Buckaroo for FinDock extension we’ve added a new batch that can be scheduled, we suggest, on a daily basis. This batch will query all the Buckaroo installments in the Salesforce org with status ‘Pending’ and make a callout to Buckaroo to get the actual status and update the Installments accordingly. The batch is named ‘BuckarooPendingInstallmentsBatch’ and can be scheduled.

How to enable: Contact FinDock support to enable this enhancement.