Stripe Invoice Payment Plans and QuickBooks
One Stripe invoice, paid in scheduled installments. Why installment status isn't invoice status, and why QuickBooks aging can't see what's overdue.
A $12,000 invoice, paid in four parts over four months, is still one invoice. Stripe's invoice payment plans keep it that way. The schedule of deposits and installments sits on top of a single invoice with a single total, and every payment the customer makes reduces that one invoice's balance.
That is tidy in Stripe. It gets interesting in QuickBooks, because a QuickBooks invoice has one due date and no idea that $3,000 of it was due last month and $3,000 is due next month. Your A/R aging report will either call the whole balance current or call the whole balance late, depending on a date you chose when you created the invoice. Neither is what the customer actually owes today.
Installments in Stripe, receivables in QuickBooks. Acodei's Invoice Sync records each finalized Stripe invoice in QuickBooks and applies its payments to it. Start a free trial.
This guide covers how Stripe payment plans work (the schedule, the installments and their statuses), what happens when you change a plan after the customer has started paying, how bank transfers get matched to installments, and what your QuickBooks file shows at each step. It ends with a worked example and a month-end check.
What a Stripe invoice payment plan is
Stripe's documentation describes payment plans simply: they "let you split an invoice total into separate payments with different due dates." The two patterns Stripe calls out are a deposit followed by the remaining balance, and dividing the amount due into smaller installments over time.
A few things define the feature, and they matter for the books:
- It's one invoice. The plan doesn't create child invoices. The invoice has one total, one number and one PDF, and the installment labels (Stripe's example is "Deposit") appear on that PDF and on the payment page.
- It's send-invoice only. Payment plans "don't auto-charge customers with saved payment details. Customers must return to the payment page to make subsequent payments. You can't use them with
charge_automaticallyinvoices." - It's not for subscriptions. Stripe says plainly: "You can't apply payment plans to subscription invoices."
- It's gated. Stripe has to enable payment plans on your account. If you don't see Request in multiple payments under Payment collection in the invoice editor, you have to request access from Stripe Support.
- It isn't credit. Stripe's disclaimer says the feature "isn't a buy now, pay later service," and that Stripe isn't responsible if your customer fails to pay. The collection risk stays with you, exactly as it would on any invoice with long terms.
In the Dashboard, the default plan splits the amount due evenly into two payments due over two months. You can change the frequency (weekly through every six months, or custom), add up to 50 installments, and set each one as a fixed amount or a percentage. Stripe won't let you save a plan whose installments don't add up to the invoice amount, and it won't let you finalize an invoice whose installments no longer match its total.
Through the API, the plan is a separate PaymentPlan object attached to the invoice. Its schedule holds your intended structure, as either all fixed amounts or all percentages (Stripe doesn't allow mixing them in one schedule). Its installments array holds the result: concrete amounts, resolved due dates, stable installment IDs and each installment's payment state.
Installment status is not invoice status
This is the single most important thing to understand before you try to reconcile a payment-plan invoice.
Each installment has its own due_date, amount_due, amount_paid, amount_forgiven and status. An installment with an unpaid balance becomes past_due once its due date passes.
The invoice doesn't follow along. Stripe is explicit: "The invoice's status describes the invoice lifecycle, not installment delinquency. An invoice can remain open even when every installment is past_due." Stripe also warns against using the invoice's top-level due_date as the installment schedule, and says to use the resolved due dates in installments for payment tracking and collection.
Meanwhile the invoice itself behaves like any partly paid invoice. Stripe's partial payments guide says that when a payment succeeds, "Stripe updates the invoice's amount_paid and amount_remaining," and that "When the invoice is fully paid, Stripe updates the status to paid." Each payment is recorded as an InvoicePayment in the invoice's payments list.
So a payment-plan invoice carries two layers of truth:
| Question | Where Stripe answers it |
|---|---|
| How much has the customer paid in total? | Invoice amount_paid |
| How much is left on the invoice? | Invoice amount_remaining |
| Is the invoice settled? | Invoice status (paid only when fully paid) |
| How much is overdue right now? | Sum of unpaid amounts on installments with status past_due |
| When is the next payment due? | The earliest unpaid installment's due_date |
QuickBooks has a place for the first three. It has nowhere for the last two.
The invoice due date is a choice, and it decides what QuickBooks calls late
When you create a payment-plan invoice through the API, Stripe still requires an invoice due date: the invoice must be send_invoice with either due_date or days_until_due. Stripe notes that installment due dates are separate. They can align with the invoice due date or differ, and Stripe's own examples set days_until_due: 120 to match the final installment.
That invoice due date is the only date QuickBooks will see as "due." QuickBooks Online invoices carry one due date, and receivables reporting such as A/R aging sorts open balances by it. That leaves you two ways to set it, and both distort the picture:
- Invoice due date = final installment. This is what Stripe's examples do. The invoice looks current in QuickBooks right up to the last installment date, even if the customer skipped two installments in the middle. Aging understates delinquency.
- Invoice due date = first installment. The whole remaining balance looks overdue from the first day, including installments the customer isn't supposed to pay for months. Aging overstates delinquency, and a customer statement can read like a dunning letter.
Neither is wrong. They're two different compromises, and the right one depends on who reads your aging report and what your contract treats as the due date. Whichever you pick, pick it once and use it on every payment-plan invoice, so the aging report is at least consistently wrong in a known direction.
What you shouldn't do is rely on QuickBooks aging to tell you who has missed an installment. That information lives in Stripe's installments array and nowhere else.
Changing a plan after the customer starts paying
You can update a payment plan while the invoice is open, without voiding it. Stripe says schedule updates "can change amounts and due dates for installments that are already paid, not only unpaid installments."
How Stripe handles the money already paid is worth reading twice: "The schedule describes how to allocate the invoice balance, not an immutable record of individual payments. When installment amounts change, Stripe reapplies existing payments using first-in, first-out allocation." Earlier payments fill earlier installments first. Updating the schedule "doesn't collect another payment or refund an existing payment."
Two consequences follow:
- A paid installment can become unpaid. Stripe's example: a customer has paid a 1,000 USD deposit, you raise the deposit to 1,500 USD, and that installment now has 500 USD left to collect. Its status becomes
openorpast_duedepending on its due date. You then reduce later installments by 500 USD so the plan still matches the invoice total. - Reducing an installment can move money forward. Shrink an installment that was fully paid and some of its payment flows into the next one.
For the books, the important part is what doesn't change. A schedule edit moves no money and doesn't change the invoice total, because the invoice's amounts can't change after finalization. Stripe says that after finalization "you can't add or remove invoice items or change the invoice's amounts or dates." The invoice, its total and its payments in QuickBooks are unaffected by a schedule change. Only the Stripe-side picture of what's overdue moves.
If a schedule change leaves an installment with nothing left to collect and no money moves, Stripe sends payment_plan.updated and doesn't send payment_plan.installment_paid. If you track installments from webhooks, handle both events.
Bank transfers and the cash balance
Payment plans are common on large B2B invoices, and large B2B invoices are often paid by bank transfer. Stripe's automatic reconciliation can apply transfer funds to a payment plan using the invoice number in the transfer reference, or by matching the amount against the customer's available cash balance.
For amount matching, Stripe considers three totals: the invoice's full remaining balance, the total of all past-due installments, or all past-due installments plus the next unpaid one. Funds are applied to installments in due-date order. Stripe's worked example uses an invoice with a 400 USD installment due now and 600 USD due later. Without automatic partial reconciliation:
- 250 USD doesn't fund the invoice.
- 400 USD pays the first installment.
- 500 USD pays the first installment, and the remaining 100 USD goes to the customer's cash balance.
With automatic partial reconciliation turned on, and the invoice number in the transfer memo, Stripe can apply amounts that don't match one of those totals: 250 USD partially funds the first installment, and 500 USD pays the first installment and puts 100 USD toward the second.
The accounting point is the leftover. Money in the customer's cash balance has arrived at Stripe but hasn't paid any invoice. Until Stripe applies it, it's a customer prepayment, not revenue and not a reduction of receivables. If your month-end comparison of Stripe and QuickBooks is off by exactly the unapplied part of a transfer, this is usually why.
One more rule from Stripe: your underpayment threshold "only applies when the available funds can settle the invoice's full remaining balance. It doesn't reduce the amount required for an individual installment."
What QuickBooks needs to show
Strip away the schedule and a payment-plan invoice is, in QuickBooks terms, an invoice that collects several payments. QuickBooks handles that natively. Intuit's instructions for recording invoice payments are to open Receive payment, choose the customer, "Select the checkbox for each invoice you are recording a payment for," and "Adjust the amounts in the PAYMENT column if they exceed your Amount received." After saving, Intuit says, "the customer's outstanding balance decreases accordingly." Record a second payment the same way and the balance drops again.
The correct end state for a payment-plan invoice in QuickBooks is:
- One invoice for the full total, matching the Stripe invoice line for line.
- One payment per Stripe payment applied to it, so the invoice's open balance equals Stripe's
amount_remaining. - No floating payments. A payment that was recorded but not applied leaves the invoice showing its full balance on the Open Invoices report while the cash sits on the customer's account.
What not to do is split the payment plan into separate QuickBooks invoices, one per installment, by hand. Intuit's tool for staged billing is progress invoicing, which, in Intuit's words, "lets you split an estimate into as many invoices as you need," but that's a different model from Stripe's. If Stripe has one invoice and QuickBooks has four, every payment has to be matched to the right fragment, the invoice numbers no longer correspond, and a schedule change in Stripe makes the QuickBooks invoices wrong without anyone touching them.
The installment schedule itself is something QuickBooks has no field for. Keep it in Stripe, where the statuses are maintained for you, and use QuickBooks for what it's good at: the total owed, the payments received, and the balance between them.
What Acodei documents, and where the documentation stops
Acodei's Invoice Sync is a one-way integration that mirrors Stripe invoices and the payments made on them into QuickBooks Online. It's available on paid plans and turned on per company.
The documented behaviour covers the shape of a payment-plan invoice:
- The invoice. When a Stripe invoice is finalized, Acodei creates a QuickBooks invoice that reproduces every line item, and tax lines, as your mapping settings allow.
- The payments. The documented triggers for a payment are the
invoice.paidandcharge.succeededevents. Acodei creates the QuickBooks payment and applies it to the invoice it already created. That automatic application requires QuickBooks Automatic Application to be on, and Acodei's best-practice guidance is to leave it on. - The checks. When Acodei records an invoice payment, its validation rules check that the correct payment amount is applied to the QuickBooks invoice and that the payment is linked to the correct invoice. Those are the two failure modes that matter most when one invoice collects several payments.
- Pending bank debits. For an ACH payment that starts out pending, Acodei creates the payment against the invoice as if it succeeded. If it later fails, Acodei deletes that payment and records the failed payment's entry into and exit from the Stripe balance on the daily balance summary for the day of failure.
- Manual payments. A payment marked as paid outside Stripe produces a QuickBooks payment only if that setting is turned on, and it's off by default. Acodei's guidance is to avoid marking invoices paid outside Stripe unless you have to.
Now the limit. Acodei's documentation doesn't mention Stripe payment plans or installment schedules. It describes invoices and payments, not the schedule that sits between them, so nothing in it says the installment labels or due dates are carried to QuickBooks. It also doesn't spell out, as a scenario of its own, an invoice settled by several charges over several months. charge.succeeded is a documented trigger and each installment payment is a successful charge, but the multi-payment sequence isn't written down. Our partial payments guide goes into that gap in more detail. The practical advice is the same: the first time you run a payment plan, open the QuickBooks invoice after the second installment and confirm the payments and balance match Stripe before you rely on it.
If something does go wrong, Acodei's guidance is to resync the transaction from its Data Feed rather than editing the synced records by hand in QuickBooks.
A worked example
Northwind Studio quotes a $12,000 website project. The client agrees to a 25% deposit and three equal monthly installments. Northwind creates a send-invoice in Stripe on March 1 with a payment plan:
| Installment | Amount | Due |
|---|---|---|
| Deposit | $3,000 | March 1 |
| Payment 1 | $3,000 | April 1 |
| Payment 2 | $3,000 | May 1 |
| Payment 3 | $3,000 | June 1 |
Following Stripe's examples, Northwind sets the invoice due date to June 1, the final installment.
March 1. The invoice is finalized. QuickBooks gets one invoice for $12,000 due June 1. The client pays the deposit by card the same day. Stripe: amount_paid $3,000, amount_remaining $9,000, invoice open. QuickBooks: invoice open with a $9,000 balance.
April 10. The client pays Payment 1 nine days late. Between April 2 and April 10, Stripe showed Payment 1 as past_due. QuickBooks showed nothing unusual, because the invoice wasn't due until June. After the payment: Stripe amount_paid $6,000, amount_remaining $6,000. QuickBooks: $6,000 balance.
May 15. Payment 2 hasn't arrived. Here's the gap:
| Stripe | QuickBooks | |
|---|---|---|
| Invoice balance | $6,000 | $6,000 |
| Invoice status | open | Open, due June 1 |
| Overdue | $3,000 (Payment 2, past_due) | $0 (aging shows current) |
The balances match. The receivables are right. But anyone reading the QuickBooks aging report on May 15 sees a healthy customer, and the $3,000 overdue installment is visible only in Stripe.
May 20. Northwind agrees to let the client roll Payment 2 into the final payment. It updates the plan: Payment 2 drops to $0 and is removed, Payment 3 rises to $6,000. Nothing moves in QuickBooks, because no money moved and the invoice total didn't change. Stripe sends payment_plan.updated.
June 3. The client sends a $6,000 bank transfer with the invoice number in the reference. Stripe applies it to Payment 3, the invoice's amount_remaining reaches zero and its status becomes paid. QuickBooks: three payments applied ($3,000, $3,000, $6,000), balance $0.
Had Northwind set the invoice due date to March 1 instead, QuickBooks would have shown $9,000 overdue on March 2, the morning after the deposit cleared, and the client's statement would have said so.
A month-end check for payment-plan invoices
Run this for every open Stripe invoice with a payment plan:
- Balance. Stripe
amount_remainingequals the QuickBooks invoice's open balance. If not, look for a payment that wasn't applied, or one that's still pending. - Payment count. The QuickBooks invoice shows one applied payment per succeeded payment in the Stripe invoice's
paymentslist. - Cash balance. Any part of a bank transfer that went to the customer's cash balance instead of an installment is a prepayment. It shouldn't reduce the invoice in QuickBooks until Stripe applies it.
- Overdue. Sum the unpaid amounts of
past_dueinstallments in Stripe. That's your real overdue figure for these customers. Don't take it from QuickBooks aging. - Total. The QuickBooks invoice total still equals the Stripe invoice total. A plan edit never changes it, so a difference here means something else changed.
If you report receivables to a lender or a board, note that payment-plan invoices are aged by a single due date in QuickBooks, and say which convention you used.
Frequently asked questions
Does a Stripe payment plan create multiple invoices?
No. A payment plan splits one invoice's total into installments with their own due dates and amounts. The invoice keeps one number and one total, and each payment reduces its amount_remaining. The invoice becomes paid only when it's fully paid.
Can I use Stripe payment plans with subscriptions?
No. Stripe says you can't apply payment plans to subscription invoices, and they can't be used with charge_automatically invoices. Customers return to the payment page for each installment.
How do I know which installments are overdue?
Read the payment plan's installments array. An installment with an unpaid balance becomes past_due after its due date. The invoice's status stays open even if every installment is past due, so it can't tell you.
What happens to payments if I change a Stripe payment plan?
Stripe reapplies the payments already made, first in, first out, across the new schedule. Nothing is charged or refunded. A previously paid installment can become open or past_due if you increase its amount.
How should a payment-plan invoice look in QuickBooks?
One invoice for the full amount, with each Stripe payment recorded as a payment applied to it, so the open balance matches Stripe's amount_remaining. QuickBooks has no field for the installment schedule, and it ages the invoice by its single due date.
The short version
A Stripe payment plan is one invoice with a schedule on top. Installments have their own due dates and statuses, and an installment can be past_due while the invoice is still open. The invoice's own due date is the only date QuickBooks sees, so QuickBooks aging will understate or overstate what's overdue depending on which date you chose. Schedule changes reallocate payments first in, first out without moving money or changing the invoice total. Bank transfers are matched to installments in due-date order, with leftovers going to the customer's cash balance. In QuickBooks, aim for one invoice with each payment applied to it, keep the schedule in Stripe, and take your overdue figure from Stripe's installments, not from QuickBooks aging.
Keep one invoice, one balance. Acodei's Invoice Sync records each finalized Stripe invoice in QuickBooks and applies its payments, checking the amount and the link to the right invoice. Start a free trial.
Automate your Stripe to QuickBooks sync
Save hours every month. Acodei automatically syncs your Stripe transactions, invoices, and payouts to QuickBooks Online.
14-day free trial · card required · cancel anytime
How Acodei handles this in your stack
Stripe QuickBooks Integration
See how Acodei syncs Stripe payments, fees, refunds, invoices, and payouts into QuickBooks Online automatically.
Or go straight to a capability
Advanced Product Mapping
Map Stripe products to QuickBooks with rule-based logic on product ID, price ID, metadata, and account. Set rule priority and extend mapping to refunds and fees.
Automated Invoice Sync
Bring Stripe invoices into QuickBooks and auto-apply payments and credit memos, with invoice numbering suffixes and quantity tracking to cut double-entry.
Multi-Currency Mastery
Sync Stripe transactions across currencies with automatic exchange rate handling and currency-specific customer records. Our team enables multicurrency on request, and zero-decimal currencies such as JPY are not supported.
Class Mapping
Map Stripe products to QuickBooks classes for scalable categorization and multi-entity reporting. Class tracking requires QuickBooks Online Plus or Advanced.
Historical Data Import
Backfill historical Stripe data into QuickBooks by month range. Preview volume and cost before syncing so reporting starts from a complete baseline.
How to Connect Stripe to QuickBooks Online
Connect Stripe to QuickBooks Online in minutes. Acodei links both accounts with secure OAuth and syncs payments, fees, refunds, and payouts automatically.
Reconcile Stripe Payments in QuickBooks
Reconcile Stripe in QuickBooks Online automatically. Acodei splits out fees, matches payouts to deposits, and keeps every charge audit-ready.
Get more operational finance guides like this one
We will only send high-value product and finance content.