Custom Field Assignment
Many organizations have their organization-specific use cases with their financial data on Leapfin for Journal Entry creation or reporting.
One common use case is:
- Adding a product tag based on id, name, description. Usually these are used for rule configurations based on these parameters, or to generate a search results based on these parameters
Custom field assignments typically are configured by Solution Architects to handle customer-specific requirements using fields from data sources.
|User must specify a single Leapfin data type on which the custom fields is used|
|a list of new data fields to be added to the selected record|
|The namespace path to the field configured by the user (e.g. "customField.productName")|
|The intended value of the new field. It can be either a text, numeric, or date value|
|a string to filter on |
Currently, Netflix has two types of subscriptions, Monthly and Annual. Netflix uses Stripe to process payments. On the stripe-payment object, there's a
description field that has "monthly subscription plan" or "annual subscription plan".
Using the Custom Field Assignment feature, the user can create a custom field called
customField.subscription that shows up on the desired Leapfin records as either
"monthly" and create or update journal entries.
- leapfinDataType = "leapfinLineItem"
- and leapfinLineItem.description contains "monthly subscription plan"
Arbitrary use case
Currently, Netflix uses Stripe use to process payments. Stripe charges $1.45 to process Netflix's $30 monthly plan. Netflix's FP&A team wants to identify all stripe fees incurred from Stripe that are above $1.45 and label them as "Stripe Fee" and declare them as "Large" fees.
- leapfinDataType = "leapfinFee"
- and leapfinFee.amount > 1.45
- field 1:
newField.name= "description" (update existing field)
newField.value= "Stripe Fee"
- field 2:
newField.name= "customFields.feeSize" (create new field)
- field 1:
Updated 4 months ago