Stripe commerce integration
Transform configured Stripe charge, invoice, payout and refund events into supported accounting records without confusing payment activity with bank-feed connectivity.
Distinguish the sale from the settlement
A charge, invoice and payout can describe different parts of the same commercial activity. Configure which source events should create the supported accounting target so the sale is not recorded again merely because funds are later paid out. Customer identity, currency, fees and document references need a clear rule before automation.
Make refund and fee policy part of the mapping
Refunds and fees should be represented according to the agreed accounting policy and available source detail. Review the confirmed target record against the original event when the amounts differ. This FOR:OMNI connector concerns Stripe commerce events; the bank-account connection and imported bank movement workflow belongs to FOR:EXCHANGE.
What to know before you start
Do not enable overlapping event rules without reviewing duplication risk. The connector is not a promise of automatic support for every Stripe product or settlement configuration.
Practical questions
Is a payout always new revenue?
No. It may settle activity already represented by sales and payments. Define the accounting treatment explicitly.
Is this the bank-connection feature?
No. This page covers commerce-event transformation. Use FOR:EXCHANGE for the bank-account workflow.
Continue the workflow
Commerce and payment integrations
Transform supported commerce, payment and file events into the intended accounting records using configured customer, product, tax and document rules.
Bank connections
Connect eligible US and European bank accounts, read imported movements and choose how each account participates in the accounting workflow with FOR:EXCHANGE.
Credit notes and sales corrections
Record sales corrections with the appropriate credit document and original-invoice context, rather than disguising a reduction as a negative new invoice.