Sales Receipt or Invoice in QuickBooks Online? Build the Right Customer Workflow

October 6, 2026

Bottom line: Use a sales receipt when the customer pays at the time of sale and an invoice when payment is due later. The choice should follow the real order-to-cash event, not whichever form is faster to enter. A controlled workflow connects the customer document, payment evidence, deposit, fees, refunds, and bank match without recording revenue twice.

Decide from payment timing, not industry labels

Two businesses selling the same service may need different forms. A consultant who receives card payment during online booking may use a sales receipt. Another consultant who completes work and gives the customer 15 days to pay may issue an invoice. A retailer can have immediate counter sales and wholesale customers on terms. The transaction facts determine the form.

Create a short decision map for each sales channel. Record when the obligation to the customer is fulfilled, when the customer is charged, which system creates the customer-facing document, where payment is captured, and how money reaches the bank. Note whether the business uses QuickBooks Payments, another processor, an ecommerce marketplace, checks, ACH, or cash.

Intuit’s guide to invoices and sales receipts explains the invoice workflow, while its sales receipt guidance covers paid-at-sale transactions. Confirm the current product behavior in the company’s subscription and settings before documenting exact clicks.

Follow the accounting path of each form

An invoice generally records income and accounts receivable. The later customer payment reduces that receivable and moves the amount to a bank account or undeposited funds, depending on the workflow. The payment is not a second sale. A sales receipt generally records the sale and payment together, so it should not later receive a separate customer payment as though an invoice remained open.

The bank deposit is another distinct event. If three 100 sales receipts are grouped into a 300 deposit, the bank-feed item should match that deposit, not create 300 of new income. If a processor remits 291 after a 9 fee, preserve gross sales of 300 and record the 9 fee through an approved settlement workflow. Categorizing the 291 bank deposit directly to income can understate revenue and lose the fee detail.

Build a transaction matrix with one row per channel. Include source order, QuickBooks form, customer name convention, product or service item, income account, sales-tax handling, payment method, clearing account, deposit grouping, fee treatment, refund path, and reviewer. This prevents staff from improvising when a bank-feed item appears.

Control the handoff from order to QuickBooks

For immediate-payment sales, the source packet should identify the customer or approved generic-customer convention, sale date, items, gross amount, discounts, tax, tips if applicable, payment reference, and processor status. If another platform is the sales subledger, define whether transactions are summarized or entered individually and who approves that method. Never invent a customer name or collapse transactions in a way that defeats required tax or management reporting.

For invoiced sales, capture the approved customer record, billing terms, service or delivery evidence, item, quantity, rate, tax status, class or location, purchase-order reference when used, and recipient. Separate invoice preparation from approval when practical. Keep proof of sending and record disputes or promised credits in an exception queue rather than altering the invoice without authorization.

Use stable external references to prevent duplication. A sales-channel order number, processor transaction ID, or approved batch ID can be recorded in a memo or custom field. Before creating a form, search the reference and compare customer, date, and amount. The control should catch both an exact duplicate and the same sale entered once as an invoice and again as a sales receipt.

Handle mixed and changing payment situations

Deposits and retainers require special care because cash may arrive before the business has earned revenue. Do not choose a sales receipt merely because money arrived. Follow the company’s accountant-approved policy for customer deposits, liabilities, and later application. Link the payment to the eventual invoice or other transaction so the customer balance and deferred amount can be reconciled.

Partial payment also does not convert an invoice into a sales receipt. Keep the invoice, apply the amount actually received, and leave the supported balance open. If the customer pays more than the invoice, record the overpayment under the approved process and route refund or future-application decisions to an authorized reviewer.

If an immediate sale later becomes a refund, preserve the original sales receipt and use the proper refund or credit workflow. Document the reason, authorization, amount, tax effect, processor reference, and cash movement. Deleting the original receipt hides the sequence and may make the settlement impossible to reconcile.

When staff discover that the wrong form was used, stop before deleting anything. Determine whether the customer received the document, whether payment was processed, whether sales tax was reported, whether the transaction is in a closed period, and whether another system references its number. Prepare the proposed correction and obtain approval. The cleanest-looking edit is not always the safest historical treatment.

Reconcile three independent views

At least weekly for active channels, compare the sales source, QuickBooks customer activity, and cash settlement. The source view proves what was ordered and paid. The customer view shows invoices, sales receipts, credits, and open balances. The cash view shows processor batches and bank deposits. Differences should be listed, not netted away.

Useful exception types include order missing in QuickBooks, duplicate form, invoice still open despite payment, sales receipt plus categorized bank income, failed payment, fee posted against revenue, refund without original reference, deposit split across days, and sales-tax difference. Assign an owner and expected evidence to each item.

For example, an online store reports 1,200 gross sales, 80 refunds, 36 fees, and a 1,084 payout. QuickBooks contains 1,200 of sales receipts but the bank-feed payout was also added as income. The reconciliation exposes 1,084 of duplicate income. The correction should remove the duplicate bank-feed coding while preserving the actual sales, refunds, fees, and matched payout under reviewer approval.

Deliver a workflow that survives staff changes

The final procedure should include the channel matrix, examples of each supported path, required source fields, duplicate search, deposit grouping rule, exception codes, review cadence, and escalation boundaries. Add screenshots only where they remain useful; product interfaces change, while the decision logic should stay clear.

Measure quality with operational checks: unmatched bank deposits, overdue invoices with unapplied payments, duplicate external references, sales forms lacking source evidence, and old clearing-account balances. A zero accounts-receivable balance is not enough if paid-at-sale transactions were duplicated in the bank feed.

QBOAssistant can help document the sales channels, enter approved forms, apply payments, prepare deposit matches, and maintain the exception queue. Review accounts payable and receivable VA support or request a consultation to scope the handoff.

Sources

• Intuit: Create invoices in QuickBooks Online
• Intuit: Create and send sales receipts