Applying Stripe Credit to an Open Invoice and QuickBooks

You can now aim Stripe credit at a specific open invoice through a preview API. The request, the rules, the limits, and the QuickBooks check.

Acodei Content Team · 11/21/2026 · 16 min read

A customer is billed $1,200 a month on net 15 terms. Their October invoice is finalized, emailed and still open. On November 3 you give them a $300 goodwill credit after an outage, and they reply asking you to take it off the October invoice so they can pay $900 and be done with it.

Until this month, Stripe's answer was no. A customer credit balance waits for the next invoice Stripe finalizes, which here is the December invoice, so October stays open at $1,200 and the customer pays it in full while the credit sits unused for another month. The workarounds were a credit note against the October invoice instead of a balance credit, or voiding October and reissuing it.

On November 18, 2026, Stripe documented a public preview that does exactly what the customer asked: apply existing credit to a specific open invoice. This guide covers how it works, the conditions it enforces, the errors and retry rules, what it can't do, and what to check on the QuickBooks side, where the invoice may already have been created at the full amount.

Keep your QuickBooks invoices tied to Stripe. Acodei's Invoice Sync creates a QuickBooks invoice when a Stripe invoice is finalized and applies the payment when it's paid, including payment by a credit balance offset. Start a free trial.

The default rule, and when it picks the wrong invoice

Every Stripe customer has a credit balance, which Stripe also calls the customer invoice balance. It's a ledger of credit and debit adjustments, and our Stripe customer credit balance entry explains the sign rules and transaction types in full.

How the balance gets used is the part this guide is about. Stripe's customer invoice balance guide states the defaults plainly:

  • "The invoice balance automatically applies to the next invoice finalized for the customer."
  • "A credit invoice balance is applied up to the invoice total amount."
  • "A debit invoice balance applies the full balance to the invoice."

The key word is next. The balance is consumed at finalization, so it only ever lands on an invoice that is being finalized after the credit exists. An invoice that is already open is invisible to it.

For subscriptions that is usually fine. A downgrade proration or a credit note credit shows up on next month's bill, and nobody minds. It goes wrong in three common situations:

  1. The customer is behind. They have an older open invoice and want credit used to clear it, not to discount a bill that hasn't arrived yet.
  2. The credit relates to a specific invoice. You granted it because of a problem with October's service, and October is still open.
  3. There is no next invoice. The customer has cancelled, and their final invoice is open. Under the default rule the credit would wait for an invoice that is never coming.

In all three, the default leaves you with an open invoice for the full amount and an unused credit on the same customer, and your receivables are overstated until someone fixes it by hand.

What the preview adds

Stripe's guide describes the new capability in one sentence: "You can manually apply a customer's existing invoice credit balance to a specific open invoice instead of waiting for Stripe to apply it automatically to a new invoice."

A few facts about the preview before the mechanics:

  • It is an API feature on a preview version. It needs API version 2026-11-18.preview. Stripe says "You don't need to enroll your account," and also that access "doesn't change the restrictions that apply to generally available API versions or the Dashboard." So there's nothing to click in the Dashboard; someone has to make the API call.
  • SDKs need the preview channel. Stripe says to install the released public preview SDK that supports this, and warns that generally available SDKs and older preview SDKs "might not include the required parameters and properties."
  • It spends existing credit. It moves credit that is already on the customer's balance onto an invoice. It doesn't create credit.

The request

You create a customer balance transaction, but with a new type. Stripe's instruction: create it "with type=applied_to_invoice, applied_to_invoice[invoice], amount, and currency." Applying $300 to the October invoice from the example looks like this:

curl https://api.stripe.com/v1/customers/cus_123/balance_transactions \
  -u "sk_live_...:" \
  -H "Stripe-Version: 2026-11-18.preview" \
  -H "Idempotency-Key: 6f1c2b0e-credit-application-1" \
  -d type=applied_to_invoice \
  -d "applied_to_invoice[invoice]=in_october" \
  -d amount=30000 \
  -d currency=usd

Two details are easy to get backwards. First, the amount is positive. Stripe says "A positive transaction amount consumes existing credit. It doesn't grant new credit." That's the opposite of an ordinary adjustment, where a negative amount is a credit. Second, the type parameter is what makes it an application: "Omitting type continues to create an ordinary adjustment instead." Leave it out and the same positive amount becomes a $300 debit on the customer, which is the reverse of what you meant.

Stripe also asks you to save the returned balance transaction id "to reconcile the application with the invoice and the customer's transaction history." Do it. It's the only record linking this credit to this invoice.

The conditions Stripe enforces

Stripe lists what has to be true before the call will work:

  • Use the right balance. It must be the customer's invoice credit balance, not their cash balance, and "The customer must have enough available credit to cover the amount you want to apply."
  • The invoice must be open and belong to the customer, in the same account and mode. It must have "no pending payment," and the request currency must match the invoice currency.
  • The amount must be a positive integer in the currency's minor unit and can't exceed the invoice's remaining unpaid amount.
  • On Connect, use an account-scoped request for a connected account.

The pending-payment rule matters for bank debits. A customer whose ACH debit on the October invoice is still processing can't have credit applied to that invoice until the payment resolves, one way or the other.

Reading the invoice afterward

Retrieve the invoice on the same preview version and look at a new property, customer_balance. Stripe breaks the credit into three parts:

  • automatically_applied_balance: "Credit applied when Stripe finalized the invoice."
  • manually_applied_balance: "Credit applied after finalization."
  • applied_balance: "The total automatically and manually applied credit."

All three are negative, because credit reduces what's owed, even though you sent a positive amount in the request.

Stripe's own worked example: a 50 USD invoice with 10 USD applied automatically at finalization starts with 40 USD due. Apply another 30 USD manually and the invoice shows status open, amount_due 1000, automatically_applied_balance -1000, manually_applied_balance -3000 and applied_balance -4000, in cents.

For the October invoice in our example, no credit was applied at finalization, so after the $300 application you'd expect amount_due of 90000, automatically_applied_balance of 0 and manually_applied_balance of -30000, with the invoice still open.

Partial or full. Stripe says "A partial application normally leaves the invoice open. Applying the full remaining unpaid amount transitions it to paid." There's one edge: if what remains is below the minimum chargeable amount, "Stripe might also settle it." So applying $1,199.70 of credit to a $1,200 invoice may leave you with a paid invoice rather than one open for 30 cents.

A field worth watching. Invoices have long carried starting_balance and ending_balance, the customer balance before and after finalization. Stripe's preview guide reports manual applications in the new customer_balance property and says nothing about starting_balance changing. If anything in your stack (a report, a script, a sync) reads starting_balance to work out how much credit an invoice used, it will see the finalization amount. Check it against applied_balance on the first invoice you try this on.

Errors, retries and idempotency

Stripe documents four reasons a request returns HTTP 400:

CauseWhat to do
The invoice isn't the customer's, isn't open, or has a pending paymentCheck both IDs; wait for any pending payment to resolve
Request currency doesn't match the invoice currencyUse the invoice's currency
Not enough available credit, or the amount exceeds the remaining unpaid amountReduce the amount or add credit first
Amount is zero, negative, or not an integer in minor unitsSend a positive integer

If the API rejects the preview parameters outright, or the invoice comes back without customer_balance, the usual cause is the version: Stripe says to verify that both requests use 2026-11-18.preview and that your SDK supports the feature.

The idempotency guidance is unusually specific, and it's worth following exactly:

  • Use a unique idempotency key "for each intended application, even if you apply the same amount to the same invoice again."
  • Don't derive the key from the invoice ID and amount. If you did, a legitimate second $100 application to the same invoice would be treated as a duplicate of the first and silently skipped.
  • On a timeout, "retry that same request with the same key." A new key on a retry risks applying the credit twice.
  • After an error, re-fetch the customer's credit balance and the invoice before you build a changed request.

What it can't do

Stripe's "Behavior and limitations" list is short, and every item has a bookkeeping consequence.

There's no undo. "There's no standalone API to unapply credit from an invoice. Creating an opposite adjustment doesn't undo an invoice application." If you apply $300 to the wrong invoice and then post a new $300 credit to put the balance back, the wrong invoice keeps its $300 reduction too. The customer has now received the same credit twice.

Voiding is the escape hatch. "Voiding an eligible open invoice restores its applied credit to the customer's balance." So the fix for a wrong application on an open invoice is to void it and issue a correct one. Once an invoice is paid it can't be voided, so a credit used on a paid invoice stays used.

Tax doesn't change. "Applying credit doesn't change the invoice's tax calculations." That matches the default rule, which Stripe describes as applying "after taxes and billing credits." The credit reduces the amount due, not the taxable amount. Tax on the October invoice stays what it was on $1,200.

No new webhook events. Stripe says "This integration doesn't introduce new webhook event types. Existing invoice and balance events still fire as applicable." It doesn't list which ones fire for a partial application. If your integrations listen for events to keep other systems current, test what a partial application actually sends before you rely on it.

Sigma can't see it. "Stripe Sigma queries and exports don't include the automatically applied, manually applied, or total credit amounts. Retrieve these values with the Invoice API." If your month-end credit review runs off a Sigma query or an export, it won't show these applications. Pull them from the invoices directly.

Revenue Recognition is covered. Stripe says its Revenue Recognition product supports manually applying credit to open invoices.

Testing tip. In a sandbox, Stripe says to finalize the invoice before you create the credit adjustment you want to apply, because "If you create the adjustment first, Stripe might apply the credit automatically when you finalize the invoice." That's the default rule doing its job, and it will spoil the test.

When to use it, and when something else fits better

The preview is one of several ways to reduce what a customer owes, and Stripe's own comparison table is clear that they aren't interchangeable.

SituationBetter tool
Customer already has credit and wants it on an older open invoiceThe preview: apply credit to the open invoice
The open invoice itself was wrong (wrong quantity, wrong price)A credit note, which Stripe says "Reduces an open invoice's amount owed"
You're granting credit because of one specific open invoiceA credit note on that invoice, which ties the reduction to it from the start
The invoice needs a new due date or a full reworkVoid and reissue; voiding also restores any applied credit
The customer sent money by bank transfer that hasn't been matchedThe cash balance, not the credit balance
Credit is prepaid or promotional usage creditBilling credits, which apply before tax

The rule of thumb: if the credit already exists on the customer's balance, the preview is the cleanest way to aim it. If you're about to create a credit to fix a particular invoice, a credit note on that invoice is usually cleaner, because the correction and the invoice stay linked in both Stripe and your books. Our Stripe credit notes and QuickBooks guide covers that route.

What QuickBooks sees

QuickBooks has nothing like Stripe's credit balance ledger. A customer credit in QuickBooks Online is a transaction: usually a credit memo, or a payment left unapplied. It reduces an invoice only once it's applied to that invoice.

QuickBooks also has its own version of the "which invoice" question. Intuit's help article on creating and applying credit memos describes a setting under Settings, then Account and settings, then the Advanced tab, in the Automation section. With it on, "QuickBooks applies the credit to the oldest unpaid invoice." With it off you "Choose when to apply credits and to which invoices," using Receive payment. If a credit is never applied, Intuit notes that "the Customer Balance Detail report shows that both the invoice and the credit memo have open balances."

So the two systems use opposite defaults. Stripe aims credit forward at the next invoice, and QuickBooks aims it backward at the oldest one. When credit moves between them, the same customer can end up with the credit on different invoices in each system.

With Acodei's Invoice Sync

Here's what Acodei's documentation covers, and where it stops.

At finalization. When a Stripe invoice is finalized, Acodei's Invoice Sync creates a QuickBooks invoice that reproduces its line items and tax lines, as your mapping settings allow. If Stripe applied a customer balance at that point, Acodei by default includes the applied balance (Stripe's starting_balance) as a line item on the QuickBooks invoice, so it reflects the exact amount Stripe charged. An admin setting, Skip Applied Balance as line item on Invoice, instead creates the invoice at the full gross amount, subtotal plus tax.

At payment. When a Stripe invoice is paid, whether by a successful charge, a manual payment (per your settings) or a credit balance offset, Acodei creates a QuickBooks payment receipt or credit memo and applies it to the invoice it created. That application needs QuickBooks Automatic Application turned on.

Where the documentation stops. A manual application happens after finalization, so by the time you make it, the QuickBooks invoice already exists at the amount it had when Stripe finalized it. Acodei's documentation predates this preview. It doesn't describe credit applied to an invoice after finalization, partial or full, and it doesn't say whether a full manual application that moves the invoice to paid is handled as the credit balance offset described above. It also lists two-way credit balance sync as something Acodei isn't pursuing, so the credit balance ledger itself stays in Stripe.

That means the honest advice is to test before you rely on it:

  1. Make your first manual application on a small invoice.
  2. Retrieve the Stripe invoice and note amount_due and customer_balance.applied_balance.
  3. Open the matching QuickBooks invoice and compare its open balance with Stripe's amount_due.
  4. If they differ, don't edit the synced invoice by hand. Acodei's documentation recommends resyncing from the Data Feed instead of altering synced transactions in QuickBooks. If a resync doesn't bring them into line, contact Acodei support with the invoice and balance transaction IDs.

We've asked for Acodei's documentation to cover this case, and we'll update this guide when it does.

A checklist for your first manual application

Before:

  • Confirm the invoice is open, has no pending payment, and is in the same currency as the credit.
  • Check the customer's credit balance covers the amount.
  • Decide whether this is really a credit-balance job or a credit-note job (see the table above).
  • Generate a fresh idempotency key for this one application.

After:

  • Save the balance transaction id with the invoice ID.
  • Retrieve the invoice on the preview version and check amount_due, status and the three customer_balance fields.
  • Compare the QuickBooks invoice's open balance with Stripe's amount_due.
  • Note the application somewhere your month-end review will see it, because Sigma won't.

At month end: reconcile the customer's Stripe credit balance against what QuickBooks shows for that customer. QuickBooks has no credit balance to compare directly, so list unapplied credit memos and payments in QuickBooks alongside each customer's Stripe balance. Our Stripe customer balance and QuickBooks guide covers that reconciliation in more depth.

Frequently asked questions

Can I apply a Stripe credit balance to a specific invoice?

Yes, through a public preview API. With API version 2026-11-18.preview you create a customer balance transaction with type applied_to_invoice, the invoice ID, a positive amount and the currency. Without the preview, Stripe applies the credit balance to the next invoice it finalizes for the customer.

Can I apply customer credit to an open invoice in the Stripe Dashboard?

Not through this preview. It's an API feature, and Stripe says access to it doesn't change the restrictions on generally available API versions or the Dashboard. Someone has to make the API call with the preview version set.

How do I undo credit applied to a Stripe invoice?

There's no standalone API to unapply it, and an opposite adjustment doesn't remove it from the invoice. Voiding an eligible open invoice restores its applied credit to the customer's balance. A paid invoice can't be voided, so credit used on a paid invoice stays used.

Does applying credit to a Stripe invoice reduce the sales tax?

No. Stripe says applying credit doesn't change the invoice's tax calculations. The credit reduces the amount due after tax, the same way the default credit balance works.

Why doesn't my Stripe Sigma report show credit applied to invoices?

Stripe says Sigma queries and exports don't include the automatically applied, manually applied or total credit amounts. Retrieve them from each invoice's customer_balance property with the Invoice API instead.

Will QuickBooks show the credit I applied to a Stripe invoice?

Acodei's documentation covers credit applied when Stripe finalizes an invoice, which appears as an applied balance line by default, and invoices paid by a credit balance offset. It doesn't yet cover credit applied after finalization, so compare the QuickBooks invoice with Stripe's amount_due after your first manual application.

The short version

Stripe's credit balance still applies itself to the next finalized invoice by default. The new preview lets you aim existing credit at a specific open invoice through the API, with a positive amount, the applied_to_invoice type, and a fresh idempotency key for each application. It can't be undone except by voiding, it doesn't change tax, it adds no new events, and Sigma can't see it. On the QuickBooks side, the invoice was created before you applied the credit, so check that its open balance matches Stripe's amount_due the first time you use it.

Let Stripe invoices and their payments flow into QuickBooks. Acodei's Invoice Sync creates the QuickBooks invoice when Stripe finalizes it and applies the payment when Stripe marks it paid, so your receivables come from Stripe instead of from manual entry. Start a free trial.

Share

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

Get more operational finance guides like this one

We will only send high-value product and finance content.