QuickBooks Online ↔ Stripe integration

Every Stripe payment lands in QuickBooks Online as a payment against the right invoice, with processing charges and refunds accounted for

Stripe knows who paid and when. QuickBooks Online knows which invoice that money belongs to. Without a link, the bookkeeper spends the start of every month matching Stripe payouts to invoices, splitting out processing charges and hunting for refunds. The QuickBooks Online ↔ Stripe pair does the matching as payments happen: a QuickBooks invoice gets a Stripe payment link, the payment closes the invoice, the processing charge is booked as an expense, and a refund reverses the right amount. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: QuickBooks Online →System page: Stripe →

What moves between the systems

QuickBooks Online → StripeAn invoice issued in QuickBooks Online gets a Stripe payment page with the same amount, currency and reference, and the customer pays by card or a local method.
Stripe → QuickBooks OnlineA successful Stripe payment is recorded in QuickBooks as a payment against that invoice, and the invoice is closed the same minute.
Stripe → QuickBooks OnlineThe Stripe processing charge is booked as a separate expense, so the payment amount in QuickBooks matches the invoice and the bank receives the net amount as expected.
Stripe → QuickBooks OnlineA full or partial refund in Stripe creates the matching refund in QuickBooks against the same customer and invoice.
Stripe → QuickBooks OnlineStripe payouts to the bank are recorded as transfers, so the bank feed in QuickBooks reconciles against them instead of against dozens of individual payments.
QuickBooks Online ↔ StripeCustomers are matched by email: a new Stripe customer is created in QuickBooks once, and an existing one is reused, so the customer list is not doubled.

What we connect

We check which QuickBooks Online region and currency the company file uses and whether Stripe is enabled for the same country and currency.
You connect the QuickBooks company to the integration through Intuit's standard consent screen; we never ask for the QuickBooks login.
In Stripe you create a restricted key for the integration and we register the receiver of payment, refund and payout events with signature checks.
Together with the bookkeeper we choose the QuickBooks accounts: where Stripe processing charges go, which clearing account holds money before payout, and how refunds are booked.
We agree on the matching rules: by invoice number in the payment reference first, by customer and amount second, and what goes to the “needs attention” list.
We run it in Stripe test mode against a QuickBooks test company first, then switch to live with a small batch of real invoices.

Automation scenarios

Month-start reconciliation

Before the bookkeeper exports Stripe payouts, splits each into payments and processing charges, and matches them to QuickBooks invoices by hand for a day or two.

After each payment closes its invoice on the day it happens, processing charges are already booked, and the payout matches the bank feed.

Invoice paid, but still open

Before the customer paid through Stripe a week ago, QuickBooks still shows the invoice overdue, and the customer gets a reminder.

After the invoice closes the minute Stripe confirms the payment, and reminders stop on their own.

Refunds found at year end

Before refunds issued in Stripe are not reflected in QuickBooks, and the revenue figure is overstated until the accountant finds them.

After every Stripe refund creates the matching refund in QuickBooks against the same invoice on the same day.

Subscriptions paid every month

Before Stripe charges subscriptions automatically, and the bookkeeper creates a QuickBooks invoice for each charge by hand.

After each subscription charge becomes a paid invoice in QuickBooks for the right customer without anyone's involvement.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

In QuickBooks an invoice is a sales form where the customer pays for a product or service later — exactly what a CRM deal turns into.
Source: developer.intuit.com ↗ checked 2026-09-27
A payment in QuickBooks can be applied to several invoices of one customer at once, so one incoming payment can close several deals in the CRM.
Source: developer.intuit.com ↗ checked 2026-09-27
QuickBooks notifies a connected application whenever data in the customer's company file changes — this is what keeps the CRM current without constant polling.
Source: static.developer.intuit.com ↗ checked 2026-09-27
Payment Links, Stripe's no-code hosted payment page, support 40+ payment methods, send automatic receipts and allow no-code refunds directly from the dashboard.
Source: docs.stripe.com ↗ checked 2026-09-25
Webhook authenticity is confirmed by checking the Stripe-Signature header against a signing secret issued when the endpoint is set up; the receiving server should respond quickly with a 2xx status instead of running long business logic inside the handler, and Stripe's official libraries allow a default 5-minute tolerance between the signature timestamp and server time.
Source: docs.stripe.com ↗ checked 2026-09-25
When a subscription is created, Stripe automatically generates invoices, attempts to collect payment and manages the subscription's status through its whole lifecycle; with automatic charging, Stripe creates an invoice with an open status and gives the customer 23 hours to pay, during which the subscription stays incomplete.
Source: docs.stripe.com ↗ checked 2026-09-25

Limits

QuickBooks Online is built for the US, Canada, the UK, Australia and a few other markets; Intuit's materials show no Ukrainian version or Ukrainian reporting, so this pair is for companies that already keep their books in QuickBooks. Stripe's own documentation does not publish a single clear statement about Ukraine, so we check availability for your registration country at the start. How processing charges, refunds and payouts are booked is an accounting decision: we set it up the way your bookkeeper says.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

QuickBooks already has its own card payments. Why Stripe?

Because the money already comes through Stripe: the site, the subscriptions or the checkout are built on it. The pair does not replace either system, it stops the bookkeeper from re-entering what Stripe already knows.

What if a payment cannot be matched to an invoice?

It is not guessed. The payment goes to a “needs attention” list in QuickBooks with the customer and amount, and the bookkeeper assigns it in one click. We report how many such cases there were in the first weeks and tighten the rules.

One payment covers several invoices. Does it work?

Yes. QuickBooks allows one payment to close several invoices of the same customer, and the pair uses exactly that: the amount is split across the open invoices in the order agreed with the bookkeeper.

Can we start with test data?

Yes, and we insist on it. Stripe has a test mode and Intuit provides test companies for the regions QuickBooks supports, so the first run touches no real books.