Stripe data mapping
- Ian Fondrk (Unlicensed)
- Jeff Huang
Table of contents
- 1 Overview
- 2 Data sources
- 3 Data mapping
- 3.1 Invoices
- 3.2 Charges
- 3.3 Refunds
- 3.4 Disputes
- 3.5 Payouts
- 3.6 Fees
- 3.7 Credit note
- 3.8 Application fee refund
- 3.9 Transfers
- 3.10 Transfer reversals
- 4 Mapping logic change management
Overview
Once you set up your Stripe integration, Leapfin will retrieve and process raw billing and payment data from Stripe and map that data as accounting records. These accounting records are used to create accounting rules to codify your accounting policy and ultimately create journal entries based on your specific requirements.
Data sources
Leapfin leverages Stripe’s API to retrieve financial data from the following Stripe objects:
For organizations using Stripe Connect, Leapfin retrieves the following additional Stripe objects to support marketplace transactions:
Depending on the scenario, Leapfin uses one of the following methods to retrieve data from the Stripe objects listed above:
Scenario | Data retrieval method |
|---|---|
Backfilling historical data | Leapfin calls object-specific API endpoints to pull each Stripe object in bulk. For example, Leapfin uses the List all invoices endpoint to pull all historical Stripe invoices. |
Processing daily incremental data | Leapfin calls Stripe's Events endpoints to pull newly created or updated Stripe objects. |
Data mapping
Once Leapfin retrieves your financial data from the applicable Stripe objects, it maps this data as Leapfin accounting records. Data mapping is a crucial step in your accounting process, as it converts raw data into a standard, usable format for your general ledger.
The Stripe data mapping flow is as follows:
Stripe object | Imported into Leapfin as (source) | Leapfin accounting records created (target) |
|---|---|---|
Note: Line items, issuance credits, and one type of application credit are mapped from the | ||
| Note: Leapfin creates charges using both | |
| Note: Leapfin creates refunds using both | |
| Note: Leapfin creates disputes using both | |
| Note: Leapfin creates payouts using both | |
|
Note: Leapfin creates credit notes using both | |
| Leapfin uses | |
| Leapfin uses | |
| Leapfin uses | |
|
| |
| ||
|
Currency and date-time format conversion:
Leapfin applies data format conversions on all currency amounts and date-time values from Stripe.
Currency amounts from Stripe are integers in the smallest currency unit. For example, USD 1.03 is stored as 103. JPY 710 is stored as 710.
Date-time values from Stripe are in Unix epoch formation. For example, epoch value 1665441318 is 2022-10-10 03:35:18PM PST.
Exchange rates for zero-decimal currencies:
The exchange rate value on Stripe's balance transaction object can be confusing in the case of zero-decimal currencies. For example, assume a charge of JPY 100 is settled as USD 1.00. The exchange rate should be 1/100 (JPY to USD). However, the actual exchange_rate value stored in Stripe's balance transaction is 1. This is because Stripe stores all currency amounts as integers in the smallest currency unit, so both JPY 100 and USD 1.00 are stored as 100.
When mapping exchange rates, Leapfin adjusts the exchange rate values based on zero-decimal currencies.
Invoices
Leapfin imports each Stripe invoice object as a stripe-invoice record, which contains many pieces of data such as line items, credit application, credit issuance, and tax. When mapping, Leapfin creates separate financial records for each piece of data contained on the invoice.
It is important to note that although the invoice object is the primary source, Leapfin uses the lines.data array of the invoice object to map line items, issuance credits, and one type of application credit. This is an important distinction, as the Stripe ID for these objects will be in the format of ii_xxxx:
As opposed to objects mapped directly from the invoice object, which are in the format of in_xxxx:
Invoice mapping
Creation condition: Leapfin creates an invoice record for each
stripe-invoice.Target:
LeapfinInvoice(schema)Source:
stripe-invoice(schema)
Target | Source |
|---|---|
objectType | "invoice" |
id |
|
total |
|
subtotal |
|
currencyCode |
|
status |
|
date |
|
issueDate |
|
uncollectibleDate |
|
paidDate |
|
dueDate |
|
exchangeRates | None |
customFields | Leapfin adds the stripeMetaData = |
links | None |
Line item mapping
Creation condition: Leapfin creates a line item record for each
stripe-invoice.lines.datalisted on the invoice with a positiveamount.Target:
LeapfinLineItem(schema)Source:
stripe-invoice(schema)Line items are mapped from the
stripe-invoice.lines.dataarray of the invoice object.
Target | Source |
|---|---|
objectType | "line-item" |
id |
|
amount |
|
currencyCode |
|
date |
|
quantity |
Null value is converted to 1. |
discountAmount | The sum of all Null value is converted to 0. |
description |
|
startDate |
|
endDate |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the invoice record with:
|
Credit mapping (issuance)
Creation condition: Leapfin creates an issuance credit record for each
stripe-invoice.lines.datalisted on the invoice with a negativeamount.Target:
LeapfinCredit(schema)Source: Primary source:
stripe-invoice(schema)Issuance credits are mapped from the
stripe-invoice.lines.dataarray of the invoice object.
Target | Source |
|---|---|
objectType | "credit" |
id |
|
amount | Negative |
currencyCode |
|
date |
|
type | "issuance" |
description |
|
startDate |
|
endDate |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links |
|
Credit mapping (application)
Creation condition: Leapfin creates an application credit record for each
stripe-invoice.lines.datalisted on the invoice if theamountis negative andproration=true.Target:
LeapfinCredit(schema)Source:
stripe-invoice(schema)This type of application credit is mapped from the
stripe-invoice.lines.dataarray of the invoice object.
Target | Source |
|---|---|
objectType | "credit" |
id |
|
amount | absolute( If the sum of this calculation is negative, then |
currencyCode |
|
date |
|
type | "application" |
description |
|
startDate | None |
endDate | None |
exchangeRates | None |
customFields | None |
links | Leapfin adds a link to the invoice record with:
|
Credit mapping (application)
Creation condition:
stripe-invoice.starting_balance<stripe-invoice.ending_balanceandstripe-invoice.status= "paid"Target:
LeapfinCredit(schema)Source:
stripe-invoice(schema)
Target | Source |
|---|---|
objectType | "credit" |
id |
|
amount |
|
currencyCode |
|
date |
|
type | "application" |
description | "" |
startDate | None |
endDate | None |
exchangeRates | None |
customFields | None |
links | Leapfin adds a link to the invoice record with:
|
Tax mapping
Creation condition: Leapfin creates a single tax record if
stripe-invoice.tax> 0 on the invoice.Target:
LeapfinTax(schema)Source:
stripe-invoice(schema)
Target | Source |
|---|---|
objectType | "tax" |
id | Leapfin uses |
amount |
|
currencyCode |
|
date |
|
description | "" |
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the invoice record with:
|
Charges
Leapfin imports each Stripe charge object as a stripe-charge record and then maps it as a LeapfinPayment record. Leapfin also creates separate fee records for Stripe fees associated with the stripe-charge. Stripe fees are contained in the stripe-balance-transaction record associated with the stripe-charge record.
Application fee mapping:
An application fee is always collected as part of a charge on Stripe. Although a separate application fee object is created, the same information is also included in the balance transaction object of the Stripe charge. Leapfin stores the application fee as customField.applicationFeeAmount on the payment record.
Payment mapping
Creation condition: Leapfin creates a payment record for each
stripe-charge.Target:
LeapfinPayment(schema)Source:
stripe-charge(schema) andstripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "payment" |
id |
|
amount |
|
currencyCode |
|
date |
|
status |
|
succeededDate | When pulling incremental data from Stripe Event API, Leapfin maps the event object as succeededDate if |
description |
|
exchangeRates | Leapfin maps
|
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated invoice record with:
|
Fee mapping
Creation condition: For each
stripe-chargerecord, Leapfin retrieves the associatedstripe-balance-transactionrecord based onstripe-charge.balance_transaction. Leapfin then creates a fee record for eachstripe-balance-transactionrecord wheretypeis notpayment_failure_refundandfeeis not zero.Target:
LeapfinFee(schema)Source:
stripe-charge(schema) andstripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "fee" |
id |
|
amount |
|
currencyCode |
|
date |
|
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated payment record with:
|
Refunds
Leapfin imports each Stripe refund object as a stripe-refund record and then maps it as a LeapfinRefundrecord. Leapfin also creates separate fee records for Stripe fees associated with the stripe-refund. Stripe fees are contained in the stripe-balance-transaction record associated with the stripe-refund record.
Refund mapping
Creation condition: Leapfin creates a Refund record for each
stripe-refund.Target:
LeapfinRefund(schema)Source:
stripe-refund(schema) andstripe-balance-transaction(schema)
Payment failure refund
For ACH, direct debit, and other asynchronous payment methods, Stripe creates a refund object if the payment fails. A balance transaction object with a payment_failure_refund type is also created with the Stripe refund object.
By default, Leapfin creates a refund record for each Stripe refund object. Alternatively, Leapfin can ignore Stripe refund objects, if desired.
Target | Source |
|---|---|
objectType | "refund" |
id |
|
amount |
|
currencyCode |
The corresponding settlement currency is in |
date |
|
status | If Else if Otherwise, the status is set as the same value as the |
exchangeRates | Leapfin maps the exchange rate from the associated
|
customFields | Leapfin adds the following fields from the source record:
If
|
links | Leapfin adds a link to the associated payment record with:
Leapfin also adds a link to each associated line Item record by looking up the
|
Fee mapping
Creation condition: For each
stripe-refundrecord, Leapfin retrieves the associatedstripe-balance-transactionrecord based onstripe-refund.balance_transaction. Leapfin then creates a fee record for eachstripe-balance-transactionrecord wheretypeis notpayment_failure_refundandfeeis not zero.Target:
LeapfinFee(schema)Source:
stripe-refund(schema) andstripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "fee" |
id |
|
amount |
|
currencyCode |
|
date |
|
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated refund record with:
|
Disputes
Leapfin imports each Stripe dispute object as a stripe-dispute record and then maps it as a LeapfinDispute record. Leapfin also creates separate fee records for Stripe fees associated with the stripe-dispute. Stripe dispute objects are associated with one or more stripe balance transaction objects, which contain fees charged by Stripe.
Dispute mapping
Creation condition: Leapfin creates a Dispute record for each
stripe-dispute.Target:
LeapfinDispute(schema)Source:
stripe-dispute(schema) andstripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "dispute" |
id |
|
amount |
|
currencyCode |
The Corresponding settlement currency is in |
date |
|
status | If |
description |
|
initiatedDate | When pulling incremental data from Stripe Event API, Leapfin maps
|
resolvedDate | Leapfin maps the resolvedDate from the When backfilling historical data, or if no such balance transaction exists, the resolvedDate is left as null. |
exchangeRates | Leapfin maps exchangeRates from each associated
|
customFields | Leapfin adds the following fields from the source record: stripeMetaData = For each associated
For each associated
|
links | Leapfin adds a link to the associated payment record with:
Leapfin also adds a link to each associated line item record by looking up the
|
Fee mapping
Creation condition: For each
stripe-disputerecord, Leapfin retrieves all associatedstripe-balance-transactionrecords based onstripe-dispute.balance_transactions[]. Leapfin then creates a fee record for eachstripe-balance-transactionrecord wheretypeis notpayment_failure_refundandfeeis not zero.Target:
LeapfinFee(schema)Source:
stripe-dispute(schema) andstripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "fee" |
id |
|
amount |
|
currencyCode |
|
date |
|
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated dispute record with:
|
Payouts
Leapfin imports each Stripe payout object as a stripe-payout record and then maps it as a LeapfinSettlementrecord. Leapfin also creates separate fee records for Stripe fees associated with the stripe-payout. Stripe fees are contained in stripe-balance-transaction record associated with the stripe-payout record.
Payout mapping
Creation condition: Leapfin creates a Payout record for each
stripe-payout.Target:
LeapfinSettlement(schema)Source:
stripe-payout(schema) andstripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "payout" |
id |
|
amount |
|
currencyCode |
|
date |
|
status | If |
description | If |
exchangeRates | Leapfin maps exchange rate from each associated
|
customFields | Leapfin adds the stripeMetaData = |
links | No links are created as part of standard payout mapping. However, Leapfin can establish custom links to payments, refunds, or dispute records upon request. Note: Adding custom links may result in extended data processing time. |
Fee mapping
Creation condition: For each
stripe-payoutrecord, Leapfin retrieves the associatedstripe-balance-transactionrecords based onstripe-payout.balance_transactionand then creates a fee record for eachstripe-balance-transactionrecord wheretypeis notpayment_failure_refundandfeeis not zero.Target:
LeapfinFee(schema)Source:
stripe-payout(schema) andstripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "fee" |
id |
|
amount |
|
currencyCode |
|
date |
|
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated payout record with:
|
Fees
Stripe does not have an outright fee raw data structure, like it does for other transaction types like stripe-invoice, stripe-charge, etc. Instead, payment processor fee data is captured in stripe-balance-transaction data. Fees from stripe-balance-transaction data are inclusive of individual transaction fees for payments, refunds, disputes, settlements as well as batch level fees such as network costs and adjustment fees.
Note that not all stripe-balance-transaction are fee-related, as the type of balance transaction can vary. Learn more here for details about Stripe balance transactions.
Refer to the above sections for transactional fee mapping for charges, refunds, disputes and settlements.
Network fees mapping
Creation condition: Leapfin creates a Fee record for each
stripe-balance-transactionrecord wheretypeisstripe_feeornetwork_cost.Target:
LeapfinFee(schema)Source:
stripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "fee" |
id | Leapfin uses |
amount |
|
currencyCode |
|
date |
|
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | None |
Adjustment fees mapping
Creation condition: Leapfin creates a Fee record for each
stripe-balance-transactionrecord wheretypeisadjustmentandreporting_categoryisfee.Target:
LeapfinFee(schema)Source:
stripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "fee" |
id | Leapfin uses |
amount |
|
currencyCode |
|
date |
|
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | None |
Credit note
Leapfin imports each Stripe credit note object as a stripe-credit-note record, which contains a breakdown of all credit note items. When mapping data, Leapfin creates a credit note record to represent the total adjustments to the invoice and a credit record to represent the actual credit being issued (if any). Refer to Leapfin’s Credit note documentation for an explanation of the difference between credit note and credit.
Credit note mapping
Creation condition: Leapfin creates a credit note record for each
stripe-credit-note.Target:
LeapfinCreditNote(schema)Source:
stripe-credit-note(schema)
Target | Source |
|---|---|
objectType | "credit-note" |
id |
|
totalAmount |
|
subTotalAmount |
|
currencyCode |
|
date |
|
status |
|
issueDate |
|
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated invoice record with:
A link is then added to the credit note record on the retrieved refund record. |
Credit mapping (adjustment)
Creation condition: Leapfin creates adjustment credit records if the Stripe credit note is issued prior to payment, specifically
stripe-credit-note.type= "pre_payment". In this scenario, Leapfin creates a credit record for each item withinstripe-credit-note.lines.data[].Target:
LeapfinCredit(schema)Source:
stripe-credit-note(schema)
Target | Source |
|---|---|
objectType | "credit" |
id |
|
amount |
|
currencyCode |
|
date |
|
type | "adjustment" |
description |
|
startDate | None |
endDate | None |
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated credit note record with:
If a
|
Credit mapping (issuance type)
Creation condition: Leapfin creates an issuance credit record if the Stripe credit note is issued after the payment, specifically
stripe-credit-note.type= "post_payment". In this scenario, Leapfin retrieves thestripe-customer-balance-transactionrecord associated with the Stripe credit note and creates a single credit record.Target:
LeapfinCredit(schema)Source:
stripe-credit-note(schema) andstripe-customer-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "credit" |
id |
|
amount | negative |
currencyCode |
|
date |
|
type | "issuance" |
description |
|
startDate | None |
endDate | None |
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated credit note record with:
|
Application fee refund
Leapfin imports each Stripe application fee refund object as a stripe-fee-refund record and maps it as a LeapfinRefund record.
Issuing an application fee refund
Stripe allows two methods for refunding application fees:
Method 1 (most common): Refund the application fee together with the charge (the most common method)
When using this method, the application fee refund is included as part of the balance transaction object associated with the Stripe refund object. Leapfin maps the application fee refund as
customFields.applicationFeeAmounton the Leapfin refund record. (see Refund mapping logic).
Method 2: Issue an application fee refund separately
When issued separately, the application fee refund object is not associated with any Stripe refund objects. In this scenario, Leapfin maps the refund as a separate refund record.
Refund mapping
Creation condition: Leapfin creates a refund record for each
stripe-fee-refund.Target:
LeapfinRefund(schema)Source:
stripe-fee-refund(schema),stripe-balance-transaction(schema), andstripe-application-fee(schema)
Target | Source |
|---|---|
objectType | "refund" |
id |
|
amount |
|
currencyCode |
|
date |
|
status | "succeeded" |
exchangeRates | Leapfin maps exchange rates from the associated
|
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to each associated payment record by looking up the
|
Transfers
Leapfin imports each Stripe transfer object as a stripe-transfer record and maps it as a LeapfinSettlement record. Leapfin also creates separate fee records for Stripe fees associated with the stripe-transfer. Stripe fees are contained in the stripe-balance-transaction record associated with the stripe-transfer record.
Payout mapping
Creation condition: Leapfin creates a payout record for each
stripe-transfer.Target:
LeapfinSettlement(schema)Source:
stripe-transfer(schema)
Target | Source |
|---|---|
objectType | "payout" |
id |
|
amount |
|
currencyCode |
|
date |
|
status | "paid" |
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated payment record, if applicable:
|
Fee mapping
Creation condition: For each
stripe-transferrecord, Leapfin retrieves the associatedstripe-balance-transactionrecords based onstripe-transfer.balance_transactionand creates a fee record for each item withinstripe-balance-transaction.fee_details[]with astripe_feetype.Target:
LeapfinFee(schema)Source:
stripe-transfer(schema) andstripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "fee" |
id | Leapfin uses |
amount |
|
currencyCode |
|
date |
|
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated payout record with:
|
Transfer reversals
Leapfin imports each Stripe transfer reversal object as a stripe-transfer-reversal record and maps it as a payout record. Leapfin also creates separate fee records for Stripe fees associated with the stripe-transfer-reversal. Stripe fees are contained in the stripe-balance-transaction record associated with the stripe-transfer record.
Payout mapping
Creation condition: Leapfin creates a payout record for each
stripe-transfer-reversal.Target:
LeapfinSettlement(schema)Source:
stripe-transfer-reversal(schema)
Target | Source |
|---|---|
objectType | "payout" |
id |
|
amount |
|
currencyCode |
|
date |
|
status | "paid" |
description | "" |
exchangeRates | None |
customFields | Leapfin adds the following field from the source record: stripeMetaData = |
links | Leapfin adds a link to the associated payment record, if applicable:
|
Fee mapping
Creation condition: For each
stripe-transfer-reversalrecord, Leapfin retrieves the associatedstripe-balance-transactionrecords based onstripe-transfer-reversal.balance_transactionand creates a fee record for each item withinstripe-balance-transaction.fee_details[]with astripe_feetype.Target:
LeapfinFee(schema)Source:
stripe-transfer-reversal(schema) andstripe-balance-transaction(schema)
Target | Source |
|---|---|
objectType | "fee" |
id | Leapfin uses |
amount |
|
currencyCode |
|
date |
|
description |
|
exchangeRates | None |
customFields | Leapfin adds the following fields from the source record:
|
links | Leapfin adds a link to the associated payout record with:
|
Mapping logic change management
Leapfin periodically updates its standard mapping logic based on Stripe raw data to stay current with best accounting practices. To ensure standard mapping changes do not adversely impact existing mapped data or accounting policies, Leapfin tracks these updates through version flags.
The following tables list all existing version flags for each source report. Each flag is assigned a default value, which reflects the flag value of the standard mapping configuration detailed above.
Differences from default values
If your mapping configuration differs from the default values indicated below, it is likely due to one of the following reasons:
Legacy or custom mapping logic was applied
Recent updates in standard mapping logic that were not available at the time of implementation
Custom business requirements that deviated from standard mapping logic
Stripe invoice flags
Flag | Object | Default Value | Versioning Update | Customer Specific | Details |
|---|---|---|---|---|---|
Map Objects | Invoice | MAP_NOTHING | X |
| Supports Stripe Connected Accounts. If specified, listed Leapfin objects will be mapped from Stripe connected. |
Map Tax Object | Invoice | false |
| X |
|
Map Paid Out Of Band Reason | Invoice | false |
| X |
|
Map Merchant Tax Id | Invoice | false |
| X |
|
Map Invoice Local Currency Total | Invoice | false |
| X |
|
Map Trip Uuid Connector | Invoice | false |
| X |
|
Map Service Area Name | Invoice | false |
| X |
|
Map External Id As Invoice Number | Invoice | false |
| X |
|
Stripe line item flags
Flag | Object | Default Value | Versioning Update | Customer Specific | Details |
|---|---|---|---|---|---|
Map Objects | LineItem | MAP_NOTHING | X |
| Supports Stripe Connected Accounts. If specified, listed Leapfin objects will be mapped from Stripe Connected. |
Map Customer Id | LineItem | false | X |
| If marked true, Leapfin maps in |
Map Trip Uuid Connector | LineItem | false |
| X |
|
Map Service Area Name | LineItem | false |
| X |
|
Map Unique Id Connector | LineItem | false |
| X |
|
Map Billing Period Dates | LineItem | false |
| X |
|
Map Invoice Total | LineItem | false |
| X |
|
Map Prorated Info | LineItem | false |
| X |
|
Stripe Cash Object Flags
Flag | Object | Default Value | Versioning Update | Customer Specific | Details |
|---|---|---|---|---|---|
Map Payment Failure Refunds | Refund | true | X |
| Maps in a refund record, regardless of its |
Enable Recurly Connector | Payment | false | X |
| Offers the ability to link a Recurly invoice to a Stripe Charge in Recurly-Stripe cross-integration setups. |
Map Refund Local Currency Amount | Payment | false | X |
| Maps in |
Additional Custom Fields | Payment | Map.empty |
| X |
|
Enable Rate Card Connector | Payment | false |
| X |
|
Map Fee | Payment | false | X |
| If marked true, Leapfin maps in customFields.fee = |
Enable Payout To Balance Transaction Edge | Payment | true | X |
| Supports intermediate data processing by linking the payout to all associated |
Map Payment Local Currency Amount | Payment | false | X |
| If marked true, Leapfin maps in |
Map Service Area Name | Payment | false | X |
| If marked true, Leapfin maps in |
Map Balance Transaction Details | Settlement | true | X |
| Marked true by default, this maps in the |
Map Postal Code | Payment | false | X |
| If marked true, Leapfin maps in |
Specify Suffix for Network Fees | Fee | false | X |
| If marked true, Leapfin maps in |
Map Adjustment Fees From Balance Transaction | Payment | false | X |
| If marked true, and if |
Stripe credit note flags
Flag | Object | Default Value | Versioning Update | Customer Specific | Details |
|---|---|---|---|---|---|
Map Objects | Credit Note | MAP_NOTHING | X |
| This Supports Stripe Connected Accounts. If specified, listed Leapfin records will be mapped from Stripe Connected. |
Map Refund | Credit Note | false | X |
| If marked true, Leapfin maps in |
.Map Customer Balance Transaction | Credit Note | false | X |
| If marked true, Leapfin maps in |
Map Credit Note In Credit | Credit | false | X |
| If marked true, Leapfin maps in |
Map Total Excluding Tax | Credit Note | false | X |
| If marked true, Leapfin maps in |
Map Tax To Credits | Credit Note | false | X |
| If marked true, Leapfin creates a link between the credit note and its corresponding target tax record. |
Map Credit Note To Line Item Link | Credit Note | false | X |
| If marked true, Leapfin creates a link between the credit note and its corresponding target invoice line item records. |