Stripe

Overview

Stripe knows what your customers paid. DualEntry needs to know what that means for the books — including the parts that are easy to miss, like processing fees and payout timing.

‍

Once connected, Stripe activity creates and updates DualEntry records automatically. Customers become customers, products become items, one-time invoices become invoices and subscription invoices become contracts. Payments post as customer payments, payouts as bank transfers, and Stripe's processing fees as direct expenses so your net deposit reconciles against gross revenue.

‍

Record sync runs one way: DualEntry never changes the status of a Stripe invoice or subscription. The one deliberate exception is collection — you can initiate a Stripe charge when collecting against an invoice.

Key Features

1. Fees booked, not lost
   Stripe processing fees post as direct expenses, so the gap between gross revenue and your net payout is accounted for rather than absorbed.
   ‍
2. Subscriptions become contracts
   Subscription invoices create contract and contract invoice records, giving recurring revenue the structure it needs downstream.
   ‍
3. Payouts as bank transfers
   Each Stripe payout arrives as a bank transfer to your mapped bank account, so deposits reconcile against the ledger.
   ‍
4. Kept current automatically
   After setup, customers and products stay up to date as they change in Stripe, and invoices and payments sync as they are created and paid.
   ‍
5. Per-product GL mapping
   Map income and deferred revenue accounts per product, alongside your income, expense, deferred revenue and bank account settings.
   ‍
6. Backfill from a date you choose
   Set a sync start date on first run to bring historical Stripe activity into the ledger.