Set up your Stripe integration

Leapfin’s pre-built integration with Stripe makes it easy for you to import your Stripe billing and payment data into Leapfin. Once imported, Leapfin maps this data as accounting records, which are used to create accounting rules and ultimately generate journal entries.

Following the steps below to set up your Stripe integration with Leapfin:

1. In Leapfin, click your account name in the top right corner of the screen.
2. Click Integrations in the drop-down.

3. Locate Stripe in the list of integrations and click CONNECT.

4. Log in to your Stripe admin account.

Note: Before logging in, ensure your admin account is not connected to any other platforms.

🚧

Email can't be use error message

If you see the following error message after attempting to log in, log into Stripe via single sign-on and retry the connection.

5. Your account will automatically connect after a successful Stipe admin login. When an account is connected, the CONNECT button will be replaced with IMPORT and RECONNECT buttons.

Repeat this process to connect as many Stripe accounts as you need.

Data sources

Once you set up your Stripe integration, Leapfin leverages Stripe’s API to retrieve financial data from the following Stripe objects:

• Invoices
• Charges
• Refunds
• Disputes
• Payouts
• Credit notes
• Balance transactions
• Customer balance transactions

For organizations using Stripe Connect, Leapfin retrieves the following additional Stripe objects to support marketplace transactions:

• Application fees
• Application fee refunds
• Transfers
• Transfer reversals

Depending on the scenario, Leapfin uses one of the following methods to retrieve data from the Stripe objects listed above:

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:

📘

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.

📘

Invoice credit mapping

In regards to credit, there are three scenarios that can occur on an invoice:

• A credit is applied to the invoice
• A line of credit is issued as part of the invoice
• A line of credit is issued and fully/partially applied on the same invoice

As such, there are three credit mappings to account for each scenario.

Invoice mapping

• Creation condition: Leapfin creates an invoice record for each stripe-invoice.
• Target: LeapfinInvoice(schema)
• Source: stripe-invoice (schema)

Line item mapping

• Creation condition: Leapfin creates a line item record for each stripe-invoice.lines.data listed on the invoice with a positive amount.
• Target: LeapfinLineItem (schema)
• Source: stripe-invoice (schema)

Credit mapping (application type)

• Creation condition: stripe-invoice.starting_balance < stripe-invoice.ending_balance and stripe-invoice.status = "paid"
• Target: LeapfinCredit (schema)
• Source: stripe-invoice (schema)

Credit mapping (issuance type)

• Creation condition: Leapfin creates an issuance credit record for each stripe-invoice.lines.data listed on the invoice with a negative amount.
• Target: LeapfinCredit (schema)
• Source: stripe-invoice (schema)

Credit mapping (application type)

• Creation condition: stripe-invoice.starting_balance < stripe-invoice.ending_balance and stripe-invoice.status = "paid"
• Target: LeapfinCredit (schema)
• Source: stripe-invoice (schema)

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)

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) and stripe-balance-transaction (schema)

Fee mapping

• Creation condition: For each stripe-charge record, Leapfin retrieves the associated stripe-balance-transaction record based on stripe-charge.balance_transaction. A fee record is then created for each item within stripe-balance-transaction.fee_details[] that has a stripe_fee type.
• Target: LeapfinFee (schema)
• Source: stripe-charge (schema) and stripe-balance-transaction (schema)

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) and stripe-balance-transaction (schema)

📘

Payment failure refund

For ACH, direct debit, and other asynchronous payment methods, Stripe creates a refund object when 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.

Fee mapping

• Creation condition: For each stripe-refund record, Leapfin retrieves the associated stripe-balance-transaction record based on stripe-refund.balance_transaction. Leapfin then creates a fee record for each item within stripe-balance-transaction.fee_details[] with a stripe_fee type.
• Target: LeapfinFee (schema)
• Source: stripe-refund (schema) and stripe-balance-transaction (schema)

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 Refund record for each stripe-dispute.
• Target: LeapfinDispute (schema)
• Source: stripe-dispute (schema) and stripe-balance-transaction (schema)

Fee mapping

Creation condition: For each stripe-dispute record, Leapfin retrieves all associated stripe-balance-transaction records based on stripe-dispute.balance_transactions[]. Leapfin then creates a fee record for each item within stripe-balance-transaction.fee_details[] with a stripe_fee type.

Target: LeapfinFee (schema)

Source: stripe-dispute (schema) and stripe-balance-transaction (schema)

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 instripe-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) and stripe-balance-transaction (schema)

Fee mapping

• Creation condition: For each stripe-payout record, Leapfin retrieves the associated stripe-balance-transaction records based on stripe-payout.balance_transaction and then creates a fee record for each item within stripe-balance-transaction.fee_details[] with a stripe_feetype.
• Target: LeapfinFee (schema)
• Source: stripe-payout (schema) and stripe-balance-transaction (schema)

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)

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 within stripe-credit-note.lines.data\[].
• Target: LeapfinCredit (schema)
• Source: stripe-credit-note (schema)

Credit mapping (issuance)

• 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 the stripe-customer-balance-transaction record associated with the Stripe credit note and creates a single credit record.
• Target: LeapfinCredit (schema)
• Source: stripe-credit-note (schema) and stripe-customer-balance-transaction (schema)

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 ways to refund 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.applicationFeeAmount on 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), and stripe-application-fee (schema)

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)

Fee mapping

• Creation condition: For each stripe-transfer record, Leapfin retrieves the associated stripe-balance-transaction records based on stripe-transfer.balance_transaction and creates a fee record for each item within stripe-balance-transaction.fee_details[] with a stripe_fee type.
• Target: LeapfinFee (schema)
• Source: stripe-transfer (schema) and stripe-balance-transaction (schema)

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)

Fee mapping

• Creation condition: For each stripe-transfer-reversal record, Leapfin retrieves the associated stripe-balance-transaction records based on stripe-transfer-reversal.balance_transaction and creates a fee record for each item within stripe-balance-transaction.fee_details[] with a stripe_fee type.
• Target: LeapfinFee (schema)
• Source: stripe-transfer-reversal (schema) and stripe-balance-transaction (schema)