Stripe and Your Billing Platform in QuickBooks

A customer pays a $4,200 annual subscription. Chargebee raised the invoice, Stripe took the card payment, and both of them have a QuickBooks connection turned on. By the end of the day QuickBooks holds a $4,200 invoice with a payment against it, and a separate $4,200 sales receipt for the same money. Revenue for the month is $4,200 too high, and nothing in either app is broken. Both did exactly what they were configured to do.

This is the most common way a well-run Stripe and QuickBooks setup goes wrong, and it has nothing to do with sync reliability. It is an ownership question that nobody answered: when two systems can both write the same sale into one company file, which one is allowed to?

Running Stripe next to a billing platform? Acodei posts Stripe charges, fees, refunds, and payouts into QuickBooks Online against the accounts you choose, so the money side of the file stays consistent no matter who raises the invoice. Start a free trial.

Two systems, and neither one knows everything

The reason this setup is tempting is that each side genuinely holds something the other does not.

Your billing platform owns the commercial document. It knows the subscription terms, the proration math, the dunning state, and the invoice number your customer will quote back to you. Chargebee, Recurly, Maxio and the rest exist because that logic is hard, and none of it is visible from a Stripe charge.

Stripe owns the money. It knows the processing fee on each charge, which charges were grouped into which payout, when that payout left, and what the balance is right now. None of that is visible from an invoice.

A QuickBooks file needs both. The mistake is assuming that because each system knows half, you should let each system write its half. The halves overlap, and the overlap is the sale itself.

Chargebee's own documentation is unusually clear about how much it writes. Its QuickBooks integration syncs invoices, credit notes, payments, refunds, customers and products, and the integration guide states plainly that "This is a one-way sync; all invoices and related information from Chargebee will be updated to QuickBooks." On the money side it says "Payment & refund transactions will be synced to Bank/Clearing Account in QuickBooks", and that you may choose "a Bank account/Clearing account/Undeposited funds account for the sync."

Read that last sentence with your Stripe setup in mind. Your billing platform is being pointed at the same class of account your Stripe sync deposits into, and quite possibly at the same account.

Duplicate protection will not catch this

This is the part worth being precise about, because people assume the opposite and find out at quarter end.

Acodei has duplicate protection, and it works by writing its own transaction id into the QuickBooks document number field on the record it creates. When the same Stripe webhook arrives twice, the second write collides with the first and QuickBooks refuses it, so you get one record rather than two. That is the whole mechanism, and it is a good one.

What it is not is a check against records Acodei did not create. It has no view of an invoice that Chargebee wrote, or of a sales receipt a bookkeeper hand-keyed last Tuesday. It compares against the document numbers of its own output. The full explanation of what duplicate protection checks is worth reading if you have been treating it as a general safety net, because a second writing app is exactly the case it cannot see.

So the safety has to come from configuration, not from detection.

The decision is one sentence: who owns the invoice?

Everything else follows from that. There are two configurations that work and one that looks like it works.

Configuration one: the billing platform owns accounts receivable

Your billing platform writes the invoice and the credit note into QuickBooks. It is the system of record for what customers owe. The Stripe side then has one job: represent the money.

Acodei's routing between record types is decided by account settings rather than by the individual charge. On a connection configured for it, a successful Stripe charge becomes a standalone QuickBooks Payment against the customer rather than a sales receipt, and that Payment is not linked to an invoice. It is deposited into the holding account you nominated, the same as every other record Acodei writes.

An unlinked payment is not a finished job. In QuickBooks it sits against the customer waiting to be settled against something. Whether QuickBooks does that by itself depends on your own settings, and Intuit's description of automatic application is worth quoting because of what it does not promise: QuickBooks "applies the credit to the oldest unpaid invoice and if the credit matches or exceeds the remaining balance, closes the invoice", and "Any additional credit is applied to the next oldest unpaid invoice until all unpaid invoices are paid." Intuit's guide to credit memos and delayed credits also notes that "If there are no unpaid invoices, the credit memo's status is Unapplied, and your customer's balance is negative."

Oldest, not correct. For a customer with one open invoice that is the same thing. For a customer with four open invoices and two payments in flight it is not, and the aging report will look plausible while pointing at the wrong invoices. If you run this configuration, checking the application is part of the close, not an optional tidy-up.

Configuration two: Stripe owns the invoice

If your invoices originate in Stripe, Acodei's Invoice Sync mirrors them: when a Stripe invoice is finalized, a QuickBooks invoice is created reproducing the line items and tax lines your mapping allows, and when it is paid, a payment receipt or credit memo is created and applied to that invoice.

The documented use case for it is specific. It is for businesses that generate all customer-facing invoices in Stripe but manage accounts receivable and reporting in QuickBooks. If your invoices are generated in Chargebee, that sentence is not describing you, and turning on Invoice Sync alongside a billing platform that is also writing invoices produces two accounts receivable ledgers for one set of customers.

In this configuration the billing platform's QuickBooks connection goes off. That feels like losing something until you notice that the invoice arriving in QuickBooks is a copy of the one your customer received either way.

The configuration that looks like it works

The tempting middle path is to let the billing platform write invoices and let the Stripe sync keep writing sales receipts, on the theory that you will spot and delete the duplicates.

You will spot the obvious ones. The ones you will not spot are partial payments, invoices paid across two charges, refunds issued against one system's record but not the other's, and any month where volume was high enough that nobody read every line. The structural problem is that a sales receipt is a complete sale, revenue and cash together. An invoice plus a payment is also a complete sale. Neither is a fragment you can safely keep alongside the other.

Splitting by record type is defensible only when the two systems never touch the same money. Subscription invoices through the billing platform and a separate Stripe Checkout line for one-off merchandise can coexist, because no single charge appears in both. Split by customer or by "we will clean it up later" and you are in the previous paragraph.

Invoice numbers collide before the accounting does

The first symptom is usually not doubled revenue. It is a sync failure, because QuickBooks objects to a duplicate document number long before anyone reads a profit and loss.

Acodei has a setting for precisely this collision: an invoice number suffix that appends -AC1, -AC2 and so on, which exists because users sometimes enter invoices directly into QuickBooks under the same numbers. Invoice Sync also compares invoice numbers before writing in order to prevent duplicates. Those defenses were built for the hand-entry case, and a billing platform writing its own invoice numbers is the same collision arriving at machine speed.

Chargebee's documentation flags a related asymmetry that matters when you unwind a mistake: "Invoices cannot be voided in QuickBooks via API. Voided invoices will be created as credit notes in QuickBooks." A void in one system is a credit memo in the other, which is why a cleanup that looks symmetrical in the billing platform does not look symmetrical in QuickBooks. More on how QuickBooks treats Stripe invoice numbers and suffixes.

Your clearing account only works if it stands for one balance

The holding account is the QuickBooks account that stands in for your Stripe balance. Every synced sale is deposited into it, and every payout moves money out of it into the real bank account. Under Undeposited Funds, a payout becomes an itemized deposit that sweeps the individual payments. Under a regular asset clearing account, a payout becomes a single transfer for the net amount.

The value of that account is that its balance is checkable against exactly one external number. Acodei builds on that directly: on clearing-account connections a daily tracker fetches the Stripe balance and the QuickBooks holding balance and records whether they match. Under Undeposited Funds that comparison is not available, and the supported reconciliation is narrower: match each payout deposit against the bank feed and reconcile the bank account. The Undeposited Funds balance itself is not something Acodei supports reconciling, because items arrive at deposit time and the balance legitimately diverges in between.

Now point your billing platform's payment sync at that same account. The balance becomes the Stripe balance plus whatever the billing platform has recorded, and no screen anywhere produces that number for comparison. You have not created an error. You have removed the check that would have found one. This is the same failure as pooling two payment processors into one clearing account, arriving from a different direction.

If both systems must write cash entries, they need separate accounts, and only the Stripe one should be called the Stripe clearing account. The setup walkthrough for that account covers the account type and the direction of each entry, and the holding account definition covers the role it plays.

One more constraint worth knowing before you choose: under Undeposited Funds a payout deposit can only be built once every underlying transaction already exists in QuickBooks, and it fails with a mismatch if they do not. In a file where another system is also writing, that sequencing is one more thing that can hold up a deposit, which is part of why a clearing account is the recommendation for complicated accounts.

Fees and payouts have exactly one possible source

Whatever you decide about invoices, two things can only come from Stripe.

The processing fee is one. Acodei records it either as a negative line on the sales record, netting it to what actually entered your Stripe balance, or as a separate expense with the sales record left gross, depending on your fee configuration. Fees are never added to a synced invoice, because that would make the invoice total disagree with the Stripe invoice your customer received. Your billing platform's invoice has the same property for the same reason: the customer was billed $4,200, not $4,200 minus processing.

The payout is the other. A billing platform knows a payment succeeded. It does not know that this payment, two others, a refund and a week of fees left Stripe as one deposit on Thursday. That reconciliation is only reconstructible from Stripe's own balance transaction data, which is what the fee and payout reconciliation guide walks through in full.

So even in configuration one, where the billing platform owns the entire accounts receivable ledger, the Stripe sync is not decorative. It is the only thing that can tell your books what the deposit consisted of.

If your file already double-counted

Two things are true and both matter.

Settings are not retroactive. Changing a mapping, a fee method, or which system writes invoices affects what happens next, not what already happened. Correcting history is a separate action.

The correction is a resync from the Data Feed rather than hand-editing QuickBooks. A resync deletes the QuickBooks side and rebuilds it under current settings. Editing the QuickBooks record by hand breaks the linkage Acodei uses for reconciliation and reversal, which turns one wrong record into a record that can no longer be repaired automatically. The mechanics of what a resync rebuilds are worth understanding before you run one on a month you have already closed.

For the duplicates themselves, work from the clearing account rather than from the profit and loss. Duplicated revenue is hard to eyeball; a clearing account holding twice as much as Stripe says is not. The general cleanup sequence for duplicated Stripe entries applies here without modification, since a duplicate from a second app behaves like any other duplicate once it is in the file.

The configuration, written down

Decide these four things, in this order, and write the answers somewhere your future bookkeeper will find them.

1. Which system writes the invoice. One of them. Turn the other's invoice sync off rather than leaving it on and filtering.
2. Which account each system deposits into. Never the same account. The Stripe clearing account represents the Stripe balance and nothing else.
3. Where the processing fee lands. One expense account, fed from Stripe, whichever invoice path you chose.
4. How you will check it. Compare the Stripe clearing balance to the Stripe balance on a fixed day. That single comparison catches almost everything the two-writer setup can do to you.

Frequently asked questions

Can I run my billing platform's QuickBooks sync and a Stripe sync at the same time?

Yes, but only with the invoice job assigned to exactly one of them. Two systems writing invoices for the same customers produces two accounts receivable ledgers. The workable split is one system writing invoices and the other writing the money side, or the two systems handling completely separate revenue that never shares a charge.

Will duplicate protection stop the double entry?

No. Acodei's duplicate protection writes its own transaction id into the QuickBooks document number so a repeated webhook collides with the record it already made. It compares against Acodei's own output, not against records another application or a person created. A second writing app is outside what it can see.

Should both systems deposit into the same clearing account?

No. A clearing account is only useful because its balance can be compared against one external balance. Pool two sources into it and there is no report anywhere that produces the combined figure for comparison, so the account stops being checkable at exactly the moment it becomes more important.

My billing platform records the payment. Do I still need Stripe fees in QuickBooks?

Yes. Check what your billing platform's integration actually lists: Chargebee's covers invoices, credit notes, payments, refunds, customers and products, and the Stripe processing fee is not among them. A record that $4,200 was paid is not a record that $4,078 arrived. Without the fee, revenue is right, cash is wrong, and the gap grows at roughly your effective processing rate.

Why did QuickBooks apply the Stripe payment to the wrong invoice?

Most likely because automatic application chose by age. Intuit describes the behaviour as applying a credit to the oldest unpaid invoice and then to the next oldest. When a customer carries several open invoices, oldest and correct are different invoices, and nothing in the payment itself tells QuickBooks which invoice the Stripe charge was actually for.

I have three months of doubled revenue. What is the fastest way back?

Fix the configuration first, so the problem stops growing, then correct history. Use the clearing account to size the damage, resync from the Data Feed rather than editing QuickBooks records by hand, and be deliberate about periods you have already closed and reconciled. Doing it in the other order means correcting the same months twice.

The point

Two systems with a QuickBooks connection is not a redundancy. It is an unassigned ownership question, and QuickBooks will answer it with whichever record arrives first.

Assign it explicitly. One system writes the invoice, the other writes the money, each deposits somewhere it does not share, and one daily balance comparison tells you the arrangement is still holding. That takes an afternoon to decide and removes an entire category of quarter-end surprise.

Let the Stripe half take care of itself. Acodei syncs Stripe charges, refunds, fees, and payouts into QuickBooks Online, deposits them into the holding account you choose, and, on a clearing account, tracks whether your Stripe balance and your QuickBooks balance still agree. Start a free trial.