Skip to content

figo Filters

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

Info

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

Prior to using the figo service, your organization must conclude a contract with figo.

Reference: figo Data Conversion

figo 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 figo transaction
TransactionNo__c <transaction_id> Internal figo 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 figo account ID
BookingDate__c <booking_date> Booking date
ProviderSpecificData__c complete transaction JSON data The retrieved figo transaction JSON data for this object

The figo Connect Transaction Object JSON data 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 figo 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 figo transaction
TransactionNo__c <transaction_id> Internal figo 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 figo Transaction Filter for each account or figo 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 figo 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 figo Transaction Filter.

You can create a filter for each banking account to be considered. The name of the filter must match the figo 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.

  1. In Setup, open Custom Settings.

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

    In Salesforce Classic, navigate to Develop > Custom Settings.

  2. Click Manage in the row of figo Transaction Filter.

  3. Click New.
  4. Specify the details as necessary.

    Field Description
    Name Unique name for the filter.
    Banking Account ID Must match the internal figo 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.
  5. Click Save.

    This creates the new figo Transaction Filter.

Note

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

Configuring figo Transaction Content Filter

In addition to the figo Transaction Filter setting, which configures the data retrieval from the figo 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 figo transactions to payment entries. Hence, the filter operates on payment entry records, and the table below refers to fields of the Payment Entry object.

  1. In Setup, open Custom Settings.

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

    In Salesforce Classic, navigate to Develop > Custom Settings.

  2. Click Manage in the row of figo Transaction Content Filter.

  3. Click New.
  4. 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.
  5. Click Save.

    This creates the new figo Transaction Content Filter.