Glossary

QuickBooks Invoice

A QuickBooks invoice is a sales form recording goods or services a customer has agreed to pay for later, which books the income now and leaves the amount owed sitting in Accounts Receivable until a separate payment record settles it.

Also called: invoice, QBO invoice, open invoice, accounts receivable invoice

Start a free trial View Pricing

Definition

Intuit puts the purpose in one sentence: "An invoice informs your customers of what they owe you for work items, goods, or services." The operative words are "what they owe". An invoice is a claim, not a receipt.

That is the whole distinction from its nearest neighbour. Intuit describes the other form this way: "A sales receipt records goods or services paid for immediately at the time of purchase (sometimes referred to as a ‘point of sale’ purchase)." One documents money you are still waiting for. The other documents money you already have.

Choosing between them is the single most consequential structural decision in a Stripe-to-QuickBooks setup, and it is usually made by accident. Both forms book revenue. Only the invoice creates a receivable, which means only the invoice makes your Accounts Receivable balance mean anything, and only the invoice needs a second record later to close it out.

This entry covers the QuickBooks record. The Stripe invoice is a different object with its own lifecycle, and the two are related but not interchangeable.

Key points

+An invoice records a sale the customer has agreed to pay for later. Intuit: "An invoice is used when your customer agrees to pay you later."
+The unpaid amount sits in Accounts Receivable until a payment is applied against it.
+A sales receipt is the alternative, for sales "paid for immediately at the time of purchase".
+A payment is a separate record applied to the invoice, never an edit to the invoice itself.
+Intuit on overdue status: "If they don’t pay within the specified time limit, their invoice is overdue."
+Voiding keeps the record and zeroes the amount. Deleting removes it. Intuit recommends voiding.
+Acodei creates a QuickBooks invoice when a Stripe invoice is finalized, and applies a payment record to it when that Stripe invoice is paid.

Invoice or sales receipt: the choice that decides what your books mean

Intuit draws the line by timing of payment. On invoices: "An invoice is used when your customer agrees to pay you later. You can set up terms to indicate how long the customer has to pay." On the alternative: "A sales receipt is used when your customer pays you on the spot for goods or services."

For a business selling through Stripe, "on the spot" describes most of what happens. A card charge succeeds and the money is yours, subject to settlement. That is a sales receipt shape, and it is why most Stripe-to-QuickBooks setups sensibly record sales receipts rather than invoices.

The invoice shape is right when there is a genuine gap between agreeing the sale and collecting it. Stripe Billing produces exactly that gap: an invoice is finalized, sent, and sits open until a payment method is charged or the customer pays it. If you bill that way and record only sales receipts, you lose the period where the money was owed but not received, and Accounts Receivable never reflects reality.

The cost of picking wrong is not cosmetic. Use sales receipts for genuinely credit-based sales and revenue lands early with no receivable to age. Use invoices for immediate card sales and you create a receivable that closes moments later, cluttering A/R with entries that were never really outstanding. Both files reconcile against the bank. Only one of them answers "how much do customers owe me right now?" correctly.

A third form is worth naming so it is not confused with either: a statement. Intuit describes it as showing "what a customer still owes you at a certain time", including "a summary of all sales, credits, and payments in each line item". A statement summarises invoices. It does not replace them, and it books nothing.

A payment is a separate record, not an edit to the invoice

This is the mechanic people most often get wrong, and it explains why "just mark it paid" is the wrong instinct.

When money arrives against an open invoice, QuickBooks does not modify the invoice. It writes a second transaction, the payment, and links it to the invoice. Intuit describes the effect: "Once you save the transaction, the invoice status updates, and the customer’s outstanding balance decreases accordingly." The invoice keeps its original amount and date. The payment carries its own.

That two-record structure is what makes partial payments and aging work at all. An invoice can carry several payments over time, each with its own date, and the receivable drops with each one. If the payment were an edit to the invoice, none of that history would survive.

The payment also has to land somewhere. Intuit’s instruction is to "Select the destination account from the Deposit To ▼ dropdown", and it notes the option of using the Undeposited Funds account when recording several payments together. That destination choice is the difference between a payment that hits your checking account directly and one that waits to be grouped into a deposit matching the lump sum your bank actually shows. For Stripe, where a payout batches many charges into one bank line, that grouping question is unavoidable rather than optional.

The payment record has its own entry in this glossary, and the account it lands in has its own entry too.

Open, overdue, and why voiding is not deleting

An invoice with a balance remaining is open. Intuit’s payment instructions assume exactly that starting point, describing the prerequisite as "An open invoice with an outstanding balance". Once terms lapse without payment, the same invoice is overdue: "If they don’t pay within the specified time limit, their invoice is overdue." Overdue is not a separate document. It is the same record past its date.

When an invoice should not have existed, or will never be collected, the temptation is to delete it. Intuit is direct that this is usually the wrong move: "For recordkeeping, voiding is better than deleting. It keeps a record of the transaction in your books without changing your totals."

The two operations differ in what survives. Voiding: "Any transaction you void has its amount changed to zero, and is marked VOID in your records." Deleting: "Deleted transactions are removed everywhere other than your audit log, but the transaction numbers don’t change." And the warning that matters most when someone is tidying up a synced file at speed: "After you delete a transaction, you can’t get it back."

For an invoice that came from a sync rather than from a person, this distinction carries extra weight. A voided invoice still exists to be matched, resynced, or explained six months later. A deleted one leaves the upstream system pointing at nothing.

Worth separating from both: writing off a genuinely uncollectible invoice is an accounting decision with its own treatment, not the same as voiding a mistake.

What Acodei writes to a QuickBooks invoice

Acodei only creates QuickBooks invoices when Invoice Sync is enabled. It is a premium feature available on paid plans, toggled per company under Account Mapping, and it changes the shape of the sync: instead of every charge becoming a sales receipt, Stripe invoices become QuickBooks invoices and the charges that pay them become payments applied against those invoices.

When a Stripe invoice is finalized, Acodei creates a QuickBooks invoice that reproduces every line item, and tax lines, as allowed by your mapping settings. When that Stripe invoice is paid, whether by a successful charge, a manual payment according to your settings, or a credit balance offset, Acodei creates a payment receipt or a credit memo and automatically applies it to the invoice it already created. That auto-application depends on QuickBooks Automatic Application being on, which is why Acodei documents leaving it on as a best practice.

The same routing shows up from the charge side. When a charge belongs to a Stripe invoice Acodei has already synced, it books a payment receipt against that QuickBooks invoice rather than a sales receipt, and the Stripe fee posts as a separate expense. More generally, Stripe fees are never added to invoices, because that would make the invoice total disagree with Stripe. Fees are handled on sales receipts, deposits, or as expenses instead.

Duplicate invoice numbers are a real hazard when a business also hand-enters invoices in QuickBooks, so Acodei appends a suffix (-AC1, -AC2, and so on) to the invoices it creates. That is on by default. It does not protect against someone manually renaming an invoice in QuickBooks afterwards.

Later lifecycle events are mirrored rather than ignored. A voided Stripe invoice results in the QuickBooks invoice being voided or a credit memo being created, and any attached credit notes are deleted first. An invoice marked uncollectible is treated the same way, and if it is later paid, Acodei reopens it and processes the payment.

Two validation and scope details are worth knowing before you reconcile. Acodei compares the invoice it generated in QuickBooks against the Stripe invoice amount to confirm they match exactly, and that particular check applies only when tax is enabled. Separately, zero-decimal currencies are not yet supported, so a business billing in a currency like JPY is outside what Invoice Sync covers today.

Want to see this on your own Stripe data?

Start a free trial

Frequently asked questions

What is an invoice in QuickBooks?

A sales form recording goods or services a customer has agreed to pay for later. Intuit describes it as informing "your customers of what they owe you for work items, goods, or services". It books the revenue and leaves the amount owed in Accounts Receivable until a payment is applied against it.

What is the difference between an invoice and a sales receipt in QuickBooks?

Timing of payment. Intuit: "An invoice is used when your customer agrees to pay you later", while "A sales receipt is used when your customer pays you on the spot for goods or services." The invoice creates a receivable that waits for a separate payment record. The sales receipt does not, because the money is already in hand.

Does recording a payment change the invoice?

No. The payment is its own transaction, linked to the invoice. Intuit describes the result: "Once you save the transaction, the invoice status updates, and the customer’s outstanding balance decreases accordingly." The invoice keeps its original amount and date, which is what makes partial payments and aging reports work.

Should I void or delete a QuickBooks invoice?

Intuit recommends voiding: "For recordkeeping, voiding is better than deleting. It keeps a record of the transaction in your books without changing your totals." A voided transaction "has its amount changed to zero, and is marked VOID in your records", while a deleted one is removed everywhere except the audit log, and "After you delete a transaction, you can’t get it back."

When does Acodei create a QuickBooks invoice instead of a sales receipt?

When Invoice Sync is enabled, which is a premium feature toggled per company. With it on, a finalized Stripe invoice becomes a QuickBooks invoice reproducing its line items and tax lines per your mapping settings, and the charge that pays it becomes a payment receipt applied to that invoice rather than a standalone sales receipt.

Why do my Acodei-created invoices have a suffix on the number?

To avoid duplicate invoice number errors in QuickBooks when you also create invoices by hand. Acodei appends -AC1, -AC2 and so on to the invoices it creates, and the setting is on by default. It cannot protect against an invoice being manually renamed in QuickBooks after the fact.

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