We are happy to present the FinDock June '20 Release.
- Release to Sandboxes: May 24, 2020
- Release to Production: June 07, 2020
In this release, we have three new features, as well as important enhancements and bug fixes.
- New features:
- FinDock multi-currency support
- New Guided Matching rule type: Keyword Search
- Payment Profile upgrade
- Enhancements and bug fixes:
- Bacs sort code handling
- CAMT.053 US dollar amount stored as Euros
- CODA statement handling corrections
- 'Is Test' in the Six Saferpay could not be disabled
- API call with many custom fields breaks on deduplication
- Gift Aid installments with negative open amount
- Payment Request Generator generates incorrect Acceptgiro
- Open amounts on recurring donations
- Text handling in Pain.008 payment message files
- WorldPay recurring donation handling
- Diner Club card support for SIX Saferpay
- Guided Matching NPSP payable Installments
- Improved SIX Saferpay and PayPal setup
When the multiple currencies feature is enabled in your org, the CurrencyISOCode field is added to all objects. FinDock checks your org for this setting and handles multiple currency support accordingly under the hood. There is nothing you need to do in your FinDock configuration when you enable multiple currencies. For further information, see Multiple currency support in FinDock.
If you do not have multi-currency enabled in your org, the changes associated with FinDock multi-currency support do not affect your Salesforce implementation.
The new Keyword Search rule type allows you to search for multiple keywords on transaction records. You can use this rule type, for example, to match transactions to campaigns by searching for keywords in the payment reference from the donor that relate to the campaign name.
We are upgrading the Payment Profile object with new identifier fields that enable indexing and enforce uniqueness. These upgrades improve overall data quality and allow automated processes like Guided Matching to query Payment Profile data in a way that supports larger data volumes. With these upgrades, we changed Guided Matching Create Payment Profile rule from insert to upsert (on unique identifier). This improves processing of CAMT files where the same customer or donor has multiple transactions in the same CAMT file. Enforcing Payment Profile uniqueness is a new FinDock general setting option. The setting is NOT enabled by default and can be enabled in both existing and new orgs. Enabling this setting does not affect existing records. Uniqueness will only be enforced on newly created Payment Profile records. For Payment Profile records, we have added the following fields. You can add these, for example, to the Details layout if you want to view them.
- Enforce uniqueness: enforce uniqueness of active Payment Profiles checking the unique identifier of the record.
- Unique Identifier: generated identifier composed of several data elements from the payment profile, such as contact ID, record type name, bank account, etc.
- Primary Identifier: indexed field that can be queried by Guided Matching and other Salesforce processes. Identifier value can be a bank account number, last 4 digits of a credit card number, etc.
Issue: If a Payment Profile was changed, the Bacs sort code was not updated correctly.
Solution: If a Payment Profile is updated and there is a new Bacs sort code available, all related mandates that had the old sort code are updated with the new sort code.
Issue: If the amount in a CAMT.053 was available in multiple currencies, FinDock incorrectly stored the US dollar amount in Salesforce as a Euro amount when EUR was the target currency. This resulted in wrong amounts on the Installment.
Solution: FinDock now stores the Euro amount from CAMT.053 in Salesforce when the target current is EUR.
Issue: Extraction of Coded Statement of Account (CODA) files could result in empty reason fields and failed duplicate protection.
Solution: The error codes in CODA statements are now always mapped to the corresponding SEPA Direct Debit (SDD) reason code, so there is always a value in the reason field of the transaction record. The duplication protection issue was caused by a bug in our code which we founded and fixed.
Issue: In some scenarios the ‘Is Test’ option in the Six Saferpay configuration could not be disabled, but was always switched back ‘on’ on the save of the configuration.
Solution: The ‘Is Test’ option is again working as expected.
Issue: When a lot of custom fields were included in the Contact object in an API call, the call would fail when trying to run the deduplication rules. This was caused by field length limitations.
Solution: FinDock can now handle more custom fields on Contact when running deduplication rules.
Issue: Gift aid Installments were sometimes left at a negative ‘Open Amount’ after reconciliation with HMRC.
Solution FinDock now rounds the values as HMRC does, so no negative amount will remain in the ‘Open Amount’ field.
Issue: The Payment Request Generator generates incorrect Acceptgiro (Dutch payment slips) references with 17 characters.
Solution: The Payment Request Generator generates correct references for Acceptgiro with 16 characters.
Issue: Updating the amount on a recurring donation changed the amounts on all related installments. However, only the first installment in the list was correctly updated with the new open amount.
Solution: We fixed the update trigger behavior so that all related installment open amounts are correctly updated when the amount on the recurring donation is changed.
Issue: Unsupported characters in Pain.008 payment messages, such as those with diacritics like “ü” or “ñ” and exclamation marks, were replaced by a question mark when FinDock parsed the Pain.008 payment.
Solution: We changed character handling to transform unsupported characters in Pain.008 files with more meaningful replacements. For example:
Issue: If WorldPay sent a new recurring donation for an existing contact with an active mandate (same credit card), FinDock created a second mandate and payment profile for the contact.
Solution: When a new recurring donation is submitted in this scenario, FinDock matches the mandate and payment profile to the existing contact and attaches this information to the new recurring donation.
We’ve added support for Diner Club credit cards to the SIX Saferpay for FinDock payment extension.
Issue: When Guided Matching created an Installment with recordtype ‘Payable,' no Opportunity was created if the source is NPSP.
Solution: If a ‘Payable’ Installment is created through Guide Matching, FinDock automatically creates a corresponding Opportunity in NPSP.
We’ve improved the SIX Saferpay for FinDock and PayPal for FinDock setup with more detailed help info on each setting and revamped instructions in our Knowledge Base. For further information, see SIX Saferpay for FinDocK and PayPal for FinDock.