Glossary

Stripe Balance Adjustment

A Stripe balance adjustment is an addition to or deduction from your Stripe balance made outside the normal charge and refund flow, most often because a charge was disputed, a dispute was won, or a refund failed to reach the customer.

Also called: adjustment, balance adjustment, Stripe adjustment transaction

Start a free trial View Pricing

Definition

Almost everything in a Stripe balance report has an obvious cause. A charge came in, a fee came out, a refund went back, a payout left. An adjustment is the type Stripe uses when money moved for a reason that does not fit any of those shapes.

Stripe defines adjustments as "additions or deductions from your Stripe balance that are made outside of the normal charge/refund flow," and names three common causes. A refund failure, where the customer’s bank or card issuer could not process a refund and Stripe returned the funds to your balance. A dispute, where Stripe deducts the disputed amount. And a dispute reversal, where you win and the disputed amount comes back.

That list is worth reading closely, because it tells you something useful: an adjustment is almost never new information. It is a correction to something that already happened. The sale, the refund, or the dispute is the real event. The adjustment is Stripe moving the money to match it.

Which is exactly why an adjustment usually has no matching line in your accounting system, and why looking for one is the wrong instinct.

Key points

+A credit or debit to your Stripe balance outside the normal charge and refund flow.
+The three documented causes are refund failures, disputes, and dispute reversals.
+On a dispute or a dispute reversal the source object is the dispute itself. On a refund failure the description points at the refund.
+It corrects an earlier event rather than recording a new one.
+In QuickBooks it does not appear as its own transaction, because the original record is what gets changed.
+Stripe suggests classifying balance transactions by reporting_category rather than by type for accounting purposes.

The three things that create one

A **refund failure** is the least known of the three and the most confusing to see. You refunded a customer, the money left your balance, and then it came back, because the customer’s bank or card issuer could not process the refund. Stripe documents the cause as something like a closed bank account or a problem with the card. The returned funds appear as an adjustment whose description points at the refund object it relates to. Your books now say you refunded someone you did not actually manage to pay.

A **dispute** is the deduction everyone recognises. When a customer disputes a charge, Stripe removes the disputed amount from your balance, and that deduction is an adjustment whose source object is the dispute. Note that this is separate from the dispute fee, which is its own charge.

A **dispute reversal** is the same mechanism running backwards. Win the dispute and the amount returns to your balance as another adjustment, again with the dispute as the source object.

Stripe also maintains a distinct `refund_failure` type, created when a card refund fails and the funds return. If you are reconciling programmatically, do not assume every returned refund arrives under a single label. And for accounting classification generally, Stripe’s own guidance is to use the `reporting_category` field rather than `type`.

Why there is no adjustment entry in your books

The instinct when you see an unexplained balance movement is to look for the matching journal entry. For adjustments there usually is not one, and that is deliberate rather than a gap.

Think about what a dispute actually means for your accounting. A sale you recorded turned out not to be a sale. The correct treatment is not to record a new expense sitting next to the original revenue. It is to undo the original revenue. Booking a separate "dispute expense" line leaves the sale on your books alongside a loss, which overstates both revenue and expenses and leaves your customer records claiming someone paid you when they did not.

The same logic covers refund failures in reverse. If a refund never reached the customer, the refund did not really happen, so the entry that should change is the refund itself.

So the useful question is never "where is my adjustment entry?" It is "which original record moved?"

Reading adjustments in a balance report

Every balance transaction carries an `amount`, a `fee`, and a `net`, and Stripe’s definitions are precise about direction. Amount is the gross amount, where "a positive value represents funds charged to another party, and a negative value represents funds sent to another party." Net is "net impact to a Stripe balance," positive incrementing it and negative decrementing it, calculated as `amount` minus `fee`.

For adjustments, sign is the first thing to read. A dispute deduction is negative. A dispute reversal and a returned failed refund are positive. Two adjustments of the same size in opposite directions, weeks apart, are very often the same dispute opening and closing.

The second thing to read is what the adjustment points at. Stripe populates `source` with the related object, and disputes put the dispute there. The `description` field, which Stripe describes as "an arbitrary string attached to the object," is what identifies the related refund on a refund failure. Between the two, most mystery adjustments resolve in about a minute.

One counting note that trips people up: the number of "payments" in Stripe is not the number of balance transactions. Fees, adjustments, and payouts are separate balance events, so any accurate reconciliation will show more balance transactions than sales.

How Acodei handles adjustments in QuickBooks

Acodei imports adjustments, but it does not create a standalone QuickBooks transaction for them. Instead it adjusts the original associated entry, so the correction lands on the record that was actually wrong.

Where a dispute or a failed payment is the cause, Acodei reverses or removes the original QuickBooks record rather than posting a new one. For a disputed invoice payment, the linked payment in QuickBooks is deleted, which causes the invoice to reopen as unpaid. The revenue and the fee from that charge are negated rather than double counted. An open invoice after a chargeback is the expected outcome, not a sync error.

Winning the dispute is the case worth planning for, because it is the one that needs you. Acodei does not automatically re-post a won dispute as a new payment. When Stripe returns the funds as a positive adjustment, you record the money coming back yourself, either by re-collecting the payment or by marking the invoice paid.

For a failed refund, Acodei will already have posted the original refund, for example as a Refund Receipt. The documented fix is to resync the affected refund or payout, at which point Acodei should detect the failed refund adjustment and void the previously posted refund entry, restoring the income.

The sync mode changes only the shape, not the principle. In daily summary mode adjustments are folded into that day’s deposit summary, so a negative adjustment reduces that day’s net Deposit and a positive one increases it. In real time mode there is no separate adjustment transaction at all, and the logic voids or corrects the original sales receipt or payment.

Adjustments are counted in Acodei’s transaction totals and included in balance reconciliation, which is why comparing Stripe’s payments count against Acodei’s transaction count will never match exactly. Acodei counts fees, adjustments, and payouts as separate events, because QuickBooks needs to reflect every balance change rather than only customer charges.

Want to see this on your own Stripe data?

Start a free trial

Frequently asked questions

What is a Stripe balance adjustment?

It is an addition to or deduction from your Stripe balance made outside the normal charge and refund flow. Stripe names three common causes: a refund that failed and returned the funds to you, a disputed charge, and a dispute you won where the amount came back.

Why is there no adjustment transaction in my QuickBooks?

Because Acodei corrects the original record instead of posting a new one. A dispute means a sale you recorded was not a sale, so the right fix is to undo that sale rather than to book a separate loss beside it. Look for the changed original transaction, not for a new adjustment entry.

Are Stripe disputes recorded as journal entries or expense lines?

No. Acodei does not create a per dispute journal entry or an itemized dispute expense line. For a disputed invoice payment it deletes the linked payment in QuickBooks so the invoice reopens as unpaid, which negates the original revenue and fee.

My invoice reopened as unpaid after a chargeback. Is that a bug?

No, that is the expected result. The payment was removed because the money was taken back, so the invoice correctly shows as outstanding again. If you later win the dispute, record the returned funds as a new payment against it.

What happens in QuickBooks when I win a dispute?

Stripe returns the money as a positive adjustment, but Acodei does not automatically re-post it as a new payment. You record it, either by re-collecting the payment or by marking the invoice paid, so the returned funds land where you want them.

What do I do about a refund that failed?

Resync the affected refund or payout. Acodei will detect the failed refund adjustment and void the refund entry it previously posted, which restores the income that the failed refund had removed.

Why does my Stripe payments count not match my Acodei transaction count?

Because they are counting different things. Acodei counts fees, adjustments, and payouts as separate events so that QuickBooks reflects every change to your Stripe balance, not only customer charges. A higher count is expected.

What customers say about running Stripe through Acodei

★★★★★

“If you're testing out all the different Stripe/QuickBooks integration apps right now, let me save you some time. This one is the best one by far.”

RyanOwner at Indie Music Academy