Multiple Stripe Subscriptions per Customer and QuickBooks
Several Stripe subscriptions on one customer mean separate invoices, charges and failures. What reaches QuickBooks, and how to read A/R by subscription.
Northwind Labs subscribes to your $49 monthly analytics plan on March 3. Two weeks later, on March 19, they add your $15 monthly storage add-on, and your app creates it as a second subscription. Nothing about that is unusual. Stripe lets one customer hold as many subscriptions as you like.
From that point on, Northwind gets two invoices a month, on two different dates, paid by two separate charges. If the card fails on the 19th, the storage subscription goes past due while the analytics subscription carries on as if nothing happened. And in QuickBooks, both streams of invoices land on the same customer, where Accounts Receivable shows one balance and no hint of which subscription it came from.
Every subscription invoice, on the right customer. With Acodei's Invoice Sync, a paid-plan feature, a QuickBooks invoice is created when a Stripe invoice is finalized, and the payment is applied to it when the invoice is paid. Start a free trial.
This post covers what Stripe does when one customer has several subscriptions, a worked month with real numbers, the things the subscriptions share and the things they don't, what reaches QuickBooks, how to read Accounts Receivable by subscription, and when it is better to put everything on one subscription instead.
What Stripe does with several subscriptions on one customer
Stripe's subscription quantities guide has a section on exactly this setup. It says: "You can simultaneously create multiple subscriptions for a single customer." It is just as clear about the consequence: "Each subscription has its own separate billing period, invoice, and charge, even if the underlying prices have the same billing period."
The independence goes all the way down. In Stripe's words, "Each subscription has a unique ID and its state is handled independently from the customer's other subscriptions. Each subscription also has its own independent billing period, based on the billing cycle anchor of the subscription."
So two subscriptions on one customer behave like two customers who happen to share a name, an email address and a card. Each one:
- Renews on its own date, set by its own billing cycle anchor.
- Produces its own invoice every period.
- Attempts its own payment for that invoice.
- Has its own status, so one can be
past_dueor canceled while the other isactive.
Stripe even warns about the case where this is not what you meant: "If you create multiple subscriptions with the same price, each subscription is independent, including payments and billing periods. If that's not what you want, create a single subscription using multiple quantities instead."
When you need to find every subscription a customer holds, the same guide points to the Customer object: "When a customer has multiple subscriptions, the Customer object's subscriptions property provides a list of every subscription."
A worked month: two subscriptions, two invoices, two charges
Take Northwind Labs from the opening. Both prices are monthly, so the billing periods have the same length, but the anchors differ because the subscriptions started on different days.
| Date | Subscription | Invoice | Amount | Payment |
|---|---|---|---|---|
| April 3 | Analytics, $49/month | Invoice 1 | $49.00 | Charged, succeeded |
| April 19 | Storage add-on, $15/month | Invoice 2 | $15.00 | Charged, declined |
| May 3 | Analytics, $49/month | Invoice 3 | $49.00 | Charged, succeeded |
Three things follow from this table that a single subscription would not produce.
Two charges instead of one. Northwind is billed $64 a month, but in two pieces. On card pricing with a fixed per-transaction component, that fixed part is paid twice, and your bank deposit for the month is built from two charges per customer instead of one.
Payment failures are partial. On April 19 the storage invoice fails while the analytics subscription is untouched. The customer is now past_due on one subscription and fully current on the other. Retries, reminder emails and any eventual cancellation all apply to the storage subscription alone.
Accounts Receivable fragments by date. On April 20, Northwind owes you $15 from Invoice 2 and nothing else. On May 3, Invoice 3 is paid on the day it is issued. If the storage invoice stays unpaid, an aging report shows a single $15 item that keeps getting older while every other invoice for the same customer is current.
What the subscriptions share, and what they don't
The subscriptions are independent, but they hang off one Customer object, and a few things on that object reach across all of them.
The payment method, unless a subscription has its own. The subscription object reference describes default_payment_method as the "ID of the default payment method for the subscription," and adds: "If neither are set, invoices will use the customer's invoice_settings.default_payment_method." When the customer updates the card on the Customer, every subscription without its own payment method picks up the change. A subscription that has its own default_payment_method keeps using it, which is a common reason one subscription keeps failing after the customer says they updated their card.
The credit balance. This is the one that surprises bookkeepers. Stripe's customer credit balance guide states that "The credit balance automatically applies to the next finalized invoice to a customer." It says the next invoice to the customer, not the next invoice for the subscription that created the credit. If Northwind downgrades the analytics plan and the proration leaves a credit on the customer balance, that credit can be consumed by the storage add-on's next invoice if that is the one that finalizes first.
The customer record itself. Name, email, address and tax details live on the Customer, so every subscription's invoices carry the same customer details.
What the subscriptions do not share is everything tied to the billing cycle: the renewal date, the invoice, the payment attempt, the subscription status and the collection settings.
The credit balance behavior has a reporting consequence. The credit is created on one subscription's invoice and used on another's, so neither invoice tells the whole story on its own. Stripe's prorations guide and the customer balance post cover where those credits come from.
What QuickBooks receives
How the two subscriptions show up depends on how your Acodei account is set up.
With Invoice Sync on. When a Stripe invoice is finalized, Acodei creates a QuickBooks invoice that reproduces its line items and tax lines, as your mapping settings allow. When that Stripe invoice is paid, Acodei creates a payment and applies it to the QuickBooks invoice created for it. So the worked month above becomes three QuickBooks invoices, two with payments applied and one open. The automatic application needs QuickBooks' Automatic Application setting turned on, and Acodei's documentation recommends keeping it on. Invoice Sync is available on paid plans and is turned on per company under Account Mapping, Premium Features.
With Invoice Sync off. On real-time accounts, each successful Stripe charge becomes a QuickBooks sales receipt by default, so each of Northwind's successful charges produces its own sales receipt, on its own date. Accounts on the daily balance summary get one aggregated receipt per day instead of a record per charge.
The customer. Acodei resolves the QuickBooks customer from the Stripe customer's name. It first checks the names it has already synced, then looks for a QuickBooks customer whose display name matches exactly (the match ignores case but must otherwise be identical), and creates a new customer if neither matches. Every subscription belongs to the same Stripe customer, so its invoices resolve the same way, and they all land on one QuickBooks customer.
That has a corollary worth knowing before you plan a structure around it. Acodei's customer sync is flat: QuickBooks sub-customers are not handled. A setup with one parent customer and a child record per subscription is not something the sync creates or posts into.
A credit used across subscriptions. When Stripe applies a customer balance to an invoice, Acodei by default includes that applied balance as a line on the QuickBooks invoice, so the invoice matches what Stripe charged. An admin setting can skip that line and create the invoice at its full gross amount instead. Either way, the line or the reduced total sits on whichever invoice Stripe applied the credit to, which may belong to the other subscription. One case to check by hand: if a credit covers an invoice in full, that invoice has nothing due, and Acodei's handling of zero-due invoices depends on an admin setting, so confirm what reached QuickBooks for it.
Reading Accounts Receivable by subscription
Once both subscriptions post to one QuickBooks customer, the customer's balance is a blend. The A/R Aging reports, the Open Invoices report and the customer's transaction list all show Northwind's invoices together. That is correct, because Northwind owes the money regardless of which plan generated it. It is less useful when someone asks "which subscription is behind?"
There are three practical ways to separate them.
1. Separate the products. Each subscription bills a different Stripe Product and Price, and that is the most reliable thing to split on. In Acodei's Multiple Product Mapping, Stripe Product mapping sends a Stripe product to the QuickBooks product you choose. Without the pricing tier, every price on that Stripe product routes to the same QuickBooks product. With the pricing tier, Acodei stores both the Product ID and the Price ID, so a monthly and an annual price can go to different QuickBooks products. Each invoice line then carries a product that names the subscription, and the Sales by Product/Service reports split revenue by subscription. If a line matches no rule, it goes to the default product or raises a sync error, depending on your settings.
2. Use subscription metadata where products overlap. If two subscriptions bill the same product (for example, two seats of the same plan bought separately), products cannot tell them apart. Acodei's metadata mapping reads metadata from the charge, the PaymentIntent, the invoice and the subscription, in that order, so a key set on each subscription can route its revenue to a QuickBooks product. Because the subscription comes last in that order, the same key on the charge, PaymentIntent or invoice is read first.
3. Read the invoice, not the balance. When the question is "what is open?", go to the open invoices rather than the customer balance. Each QuickBooks invoice corresponds to one Stripe invoice, and each Stripe invoice comes from one subscription. On the Stripe side, the invoice's parent field records "The parent that generated this invoice," per the invoice object reference, which is how you trace an open QuickBooks invoice back to its subscription.
One QuickBooks behavior to plan for: a customer statement lists everything open for the customer, so Northwind's statement will show the analytics and storage invoices together. Stripe's own emails and hosted invoice pages stay per invoice. If customers ask why the statement from your bookkeeper shows a different set of items than the Stripe emails, this is usually why.
When one subscription is the better answer
Several subscriptions per customer is the right model when the subscriptions are genuinely independent: different start dates that should stay different, the ability to cancel one without touching the other, or separate payment methods. If those aren't requirements, a single subscription is easier on the books.
Multiple products on one subscription. The same Stripe guide describes subscriptions with several items, where Stripe "generates a single invoice." One invoice and one charge per period means one QuickBooks invoice, one payment and one fixed fee, with each product on its own line.
Different intervals on one subscription. If one plan is annual and the other monthly, you no longer need two subscriptions. Stripe's mixed interval guide says "Mixed interval subscriptions must use flexible billing mode." The mixed-interval post covers the invoice period trap that comes with it.
Keeping separate subscriptions but aligning dates. If you need the independence but want one billing day, Stripe's billing cycle guide shows how to match a new subscription to an existing one: if an existing monthly subscription's anchor is the 15th at 12:30:00, "you can align a new monthly subscription with it" by setting day_of_month, hour, minute, and second in billing_cycle_anchor_config to the same values. The invoices are still separate, but they arrive on the same day, which makes the customer's A/R line up by month. The billing cycle anchor post covers the stub invoice an anchor change creates.
One-off extras. Adding a one-off charge for a customer with two subscriptions needs care. As the pending invoice items post explains, an invoice item without its subscription field set goes to the next scheduled invoice, which may belong to the wrong subscription.
A checklist for customers with several subscriptions
- Decide whether you need independence. If the subscriptions never need separate dates, payment methods or cancellations, use one subscription with several items.
- Map each subscription's product. Use Product ID mapping so each subscription's revenue lands on its own QuickBooks product, and check where unmatched lines go.
- Set metadata when products overlap. If two subscriptions bill the same product, a subscription metadata key is the way to tell them apart.
- Check the payment method on each subscription. A subscription-level
default_payment_methodwill not follow a card update on the Customer. - Watch credits that move between subscriptions. A credit from one subscription applies to the next finalized invoice for the customer, whichever subscription it belongs to.
- Keep QuickBooks' Automatic Application on, so each synced payment settles the invoice it belongs to.
- Read open invoices, not the customer balance, when you chase a past-due subscription.
- Align anchors if you want one billing day, using
billing_cycle_anchor_configon the new subscription.
Frequently asked questions
Can one Stripe customer have more than one subscription?
Yes. Stripe lets you create multiple subscriptions for a single customer. Each subscription has its own unique ID, billing period, invoice and charge, and its state is handled independently from the customer's other subscriptions, even when the prices have the same billing interval.
Does Stripe combine several subscriptions into one invoice?
No. Separate subscriptions always produce separate invoices and separate charges. To bill several products on one invoice, put them on one subscription as separate items. Since Stripe introduced mixed interval subscriptions, that also works for a monthly and an annual price, as long as the subscription uses flexible billing mode.
If one subscription's payment fails, what happens to the others?
Nothing. Each subscription has its own invoice and payment attempt, so a declined charge makes only that subscription past due. The customer's other subscriptions keep renewing and charging as normal, and their invoices stay paid.
Do several Stripe subscriptions create several customers in QuickBooks?
Not with Acodei. Acodei resolves the QuickBooks customer from the Stripe customer's name, and every subscription belongs to the same Stripe customer, so all of its invoices post to one QuickBooks customer. Acodei does not post into QuickBooks sub-customers, so there is no per-subscription child record.
How can I see which subscription an open QuickBooks balance belongs to?
Look at the open invoices instead of the customer balance, because each QuickBooks invoice corresponds to one Stripe invoice from one subscription. For reporting, map each subscription's Stripe product to its own QuickBooks product, so the product on each invoice line identifies the subscription.
The point
Several subscriptions on one Stripe customer are several independent billing streams: separate dates, separate invoices, separate charges and separate failures. In QuickBooks they meet on one customer, where the balance blends them together. Give each subscription its own product mapping so the lines tell them apart, watch credits that move from one subscription's invoice to another's, and if the subscriptions don't need to be independent, put them on one subscription.
Several subscriptions, one clean customer. Acodei syncs finalized Stripe invoices into QuickBooks Online and applies each payment to the invoice it paid, with every subscription's invoices on the same customer and each line on the product you mapped. 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.