finleap connect Filters

JustOn integrates with finleap connect to retrieve banking transactions, which are to be stored as payment entries.

Info

The finleap connect integration is available as of JustOn 2.55 and requires at least the Salesforce Enterprise Edition.

Reference: finleap connect Data Conversion

finleap connect stores banking transactions in the figo Connect Transaction object. Upon data transfer, JustOn automatically maps the retrieved transaction JSON data to the Payment Entry object.

The following table shows which data is written to the payment entry.

Payment Entry Field	Value	Description
ExternalTransactionId__c	`FIGO` + `<transaction_id>`	External ID that is used to uniquely match a finleap connect transaction
TransactionNo__c	`<transaction_id>`	Internal finleap connect transaction ID
PaymentProvider__c	`figo`	Name of the payment provider
Status__c	`New`	Status for newly created objects
Debit__c	`<amount>` if the value is positive	The debit amount
Credit__c	`<amount>` if the value is negative	The credit amount
Reference__c	`<purpose>`	Purpose text, can be empty if the transaction has no purpose
CustomerName__c	`<name>`	Name of originator or recipient
BankAccountId__c	`<account_id>`	Internal finleap connect account ID
BookingDate__c	`<booking_date>`	Booking date
ProviderSpecificData__c	complete transaction JSON data	The retrieved finleap connect transaction JSON data for this object

The JSON data of the figo Connect Transaction object contains a number of additional fields. JustOn can write additional data values to custom fields of the payment entry. Each JSON value is processed in the following way:

(1) The JSON field name is converted to a Salesforce field name, where

underscores are removed,
if the JSON value belongs to a child object, the field name is prefixed with the field name of the parent object, connected by an underscore,
the string FIGO_ is prepended,
the string __c is appended.

(2) If there is a matching field on the Payment Entry object, the field value is written to this field.

(3) The type of the Payment Entry field must match the type of the JSON field value, like Text (255) for bank_name, Currency for amount or Date for value_date. JustOn automatically converts the JSON value to the type of the Payment Entry field.

Example field conversions

JSON Field	Salesforce Field Name	Type
account_number	FIGO_AccountNumber__c	Text (255)
value_date	FIGO_ValueDate__c	Date
end_to_end_reference	FIGO_EndToEndReference__c	Text (255)
additional_info.gross_amount	FIGO_AdditionalInfo_GrossAmount__c	Currency (13,5)

When retrieving finleap connect transactions from the banking server, the response may contain a list of deleted transactions. For these transactions, JustOn also creates payment entries with the following data:

Payment Entry Field	Value	Description
ExternalTransactionId__c	`FIGO` + `<transaction_id>`	External ID that is used to uniquely match a finleap connect transaction
TransactionNo__c	`<transaction_id>`	Internal finleap connect transaction ID
PaymentProvider__c	`figo`	Name of the Payment Provider
Status__c	`New`	Status for newly created objects
IsDeleted__c	`true`	Indicates that the corresponding transaction is deleted

You can specify a finleap connect Transaction Filter for each account or finleap connect Transaction Content Filters to filter the retrieved transactions by its contents. If available, the filters are applied automatically when retrieving transactions.

Info

As a best practice, JustOn recommends to first retrieve all transactions without filters, and then, based on the produced result, configure the filters according to your requirements. You may have to repeat the filter configuration to yield the intended result.

Configuring finleap connect Transaction Filter

Your business may require to control which types of banking transactions are to be transferred. To this end, JustOn uses the custom setting finleap connect Transaction Filter.

You can create a filter for each banking account to be considered. The name of the filter must match the finleap connect internal banking account ID, which is also stored in the field BankAccountId__c of the Payment Entry object. As soon as there is a filter set up for a specific account, it is used automatically when retrieving transactions.

Click to enter Setup, then open Custom Settings.

In Salesforce Lightning, navigate to Custom Code > Custom Settings.

In Salesforce Classic, navigate to Develop > Custom Settings.
Click Manage in the row of finleap connect Transaction Filter.
Click New.

Specify the details as necessary.

Field	Description
Name	Unique name for the filter.
Banking Account ID	Must match the internal finleap connect ID of the bank account for which the filter is to be applied.
Include Pending	Indicates whether pending transactions are to be included in the response. Pending transactions are always included as a complete set, regardless of the selected time period.
Type	A list of comma separated transactions types by which the transactions are filtered, like `Transfer, Standing order`
Active (checkbox)	Enables/disables the filter. Defaults to `true`.

Click Save.

This creates the new finleap connect Transaction Filter.

Note

Make sure to activate only one filter for a specific account ID. Enabling multiple filters per account produces unpredictable results.

Configuring finleap connect Transaction Content Filter

In addition to the finleap connect Transaction Filter setting, which configures the data retrieval from the finleap connect service, you can filter the retrieved transactions by their content.

Info

This filter is an exclude filter. Retrieved transactions that match the filter conditions are not written to the database. Consequently, you use this filter to determine transactions that you do not want to be retrieved based on the specified content.

Be aware that JustOn converts finleap connect transactions to payment entries. Hence, the filter operates on payment entry records, and the table below refers to fields of the Payment Entry object.

There are two ways to configure finleap connect transaction content filters:

Administrators create, modify or delete content filters using the custom setting finleap connect Transaction Content Filter.
Users can create (not modify nor delete) content filters when deleting retrieved payment entries.

Managing finleap connect Transaction Content Filter Custom Setting

Click to enter Setup, then open Custom Settings.

In Salesforce Lightning, navigate to Custom Code > Custom Settings.

In Salesforce Classic, navigate to Develop > Custom Settings.
Click Manage in the row of finleap connect Transaction Content Filter.
Click New to create a new content filter, or Edit to modify an existing content filter.

Specify the details as necessary.

Field	Required	Description
Name		Unique name for the filter.
Content		Must match with either the Payment Entry field `CustomerName__c` or `Reference__c`.
Negative Amount (checkbox)		If selected, only payment entries with a negative amount are filtered, otherwise payment entries with a positive amount are filtered.
Active (checkbox)		Enables/disables the filter. Defaults to `true`.

Click Save.

This creates the new or modifies an existing finleap connect Transaction Content Filter.

Info

To delete a finleap connect Transaction Content Filter, click Del next to the filter.

Creating finleap connect Transaction Content Filter on Payment Entry Deletion

The Delete Payment Entries page allows users to create finleap connect Transaction Content Filters automatically based on their selection. JustOn displays the options for creating the filters if at least one payment entry that has been created by a finleap connect transaction retrieval is selected for deletion.

To create a content filter on the Delete Payment Entries page:

Select the Create Transaction Content Filter checkbox to enable the filter creation.
Define the filter condition.

Select whether the payment entry field Customer Name or Reference is used for the filter creation.

JustOn creates a filter for each unique value of the selected payment entry field, except there is already a corresponding filter.
Select the Delete all matching Payment Entries checkbox to apply all new and existing active filters to all retrieved finleap connect-based payment entries.

If, for example, you create a filter with the content John Doe, then JustOn will delete all existing payment entries that match the content John Doe, even if you have not selected them for deletion.

Following the options section, the Delete Payment Entries page shows a table that lists the new and existing filters that match the selected payment entries. For new filters, the table allows to edit the filter name (by default, the first 30 characters of the filter content value) as well as to deactivate the filter. Existing filters cannot be modified.

Note

Users are to use this option with care. Once created and activated, the filter will exclude all matching entries in the future. To deactivate or delete the filter, they need administrative access.