B2B注文のためのQuickBooksでの顧客預金会計

Customer deposits accounting in QuickBooks comes down to one account and one rule: money you haven't earned yet is money you owe.

---

The wire hit on a Monday: $4,000, reference "PO-2211 deposit." A twelve-location boutique chain had ordered 500 units with custom labeling — $10,000 total, 40% up front to start production, balance on net-30 after delivery. You won't ship for five weeks.

So what is that $4,000, exactly? It's in your bank account, but you haven't shipped anything, so it isn't a sale. Most sellers resolve the ambiguity the fast way: book it as income, or leave it uncategorized in the bank feed, and move on. Then five weeks later the invoice goes out for $10,000, the buyer pays $6,000, and QuickBooks holds some combination of double-counted revenue, a mystery deposit, and an invoice claiming the customer owes money they already sent.

If you've read our guide to net terms and wholesale AR in QuickBooks, you know the wholesale layer's first rule: invoices, not sales receipts, so the gap between earning and collecting stays visible. Deposits are the same discipline pointed the other direction — money that arrives before the earning. This post covers customer deposits accounting in QuickBooks end to end: the liability structure, the setup, a worked example from deposit to final payment, partial payments and aging, progress billing, and refundable versus non-refundable deposits.

The Lie: "Money In Is Money Earned"

The assumption underneath the fast way: "the customer paid me, so it's revenue." For retail, that's true — payment and fulfillment are the same moment. For a B2B deposit, it's false, and booking it as income breaks three things at once.

It puts revenue in the wrong month. The $4,000 lands in March's P&L; the order ships in April. Neither month's margin means anything — March carries 40% of the revenue with none of the cost of goods against it.

It sets up a double-count. When you invoice the full $10,000 at shipment — which you should, because that's when the sale happens — QuickBooks now shows $14,000 of revenue on a $10,000 order. The usual "fix" is invoicing only the $6,000 balance, which understates the sale, breaks your sales tax base, and makes the order's history unreadable.

It hides an obligation. Until you deliver, you owe that buyer 500 custom-labeled units or their money back. Booked as income, that obligation appears nowhere — take deposits on four production orders at once and your books show a healthy cash position with no hint that most of it is spoken for.

The lie is understandable — the bank balance genuinely went up. But money collected and not yet earned has a specific accounting identity, and it isn't revenue.

A Deposit Is a Liability — the Same Logic as Deferred Revenue

Money collected before fulfillment is unearned revenue, and unearned revenue is a liability. It sits on your balance sheet with your loans and unpaid bills because it behaves like them: it's something you owe — in goods rather than dollars.

If you sell subscriptions, you've met this structure before — an annual prepay is twelve months of deposits under one charge, and the deferred revenue guide walks through how that liability unwinds month by month. A B2B deposit is the same mechanism, except the whole liability converts at once, on the day you fulfill the order.

That gives the deposit a clean two-step lifecycle:

1. At receipt: cash up, liability up. No revenue, no P&L movement.
2. At fulfillment: invoice the full order (revenue recognized, correctly, once), then apply the deposit against the invoice — liability down, invoice balance down. What remains open is exactly what the buyer still owes.

Everything else in this post is mechanics for making QuickBooks do those two steps.

Customer Deposits Accounting in QuickBooks: The Setup

You need two objects in QuickBooks Online, both one-time setup:

1. A liability account. Chart of accounts → new account → Other Current Liability, named "Customer Deposits." This is where unearned money lives between receipt and fulfillment.
2. A deposit item. A service item called "Customer Deposit," with its income account pointed at that liability account — not at revenue. This item moves money in and out of the liability from inside ordinary sales forms.

The workflow, with those in place:

• When a deposit arrives, record a sales receipt for the deposit amount using the Customer Deposit item. Cash goes up; the liability goes up; revenue is untouched. Mark the item non-taxable — sales tax gets charged on the full order at invoicing, not on the prepayment. (Deposit tax timing has state-level wrinkles; confirm yours with your CPA.)
• When you fulfill the order, invoice the full order amount — every unit, full price, tax on the whole thing — then add the Customer Deposit item as a negative line for the deposit amount. The invoice total drops to the true remaining balance, the liability drains by the same amount, and one document shows the whole story: full sale, deposit applied, balance due.

You'll also see a shortcut recommended: skip the liability account and record the deposit as an unapplied credit on the customer's record (Receive Payment with no invoice). It works mechanically, but your balance sheet never shows the deposit as what it is — the obligation hides inside AR as a negative — and cash-basis reports surface it as "unapplied cash payment income," which generates exactly the confused CPA email you were trying to avoid. The liability account costs five minutes of setup and keeps the books honest. Use it.

The Worked Example: 40% Down on a $10,000 Order

Numbers fictional and deliberately round. The boutique-chain order from the opening, start to finish:

February 24 — PO accepted. 500 units, custom labeling, $10,000; 40% deposit to start production, balance net-30 from delivery. Nothing is recorded in QuickBooks yet — a purchase order is a promise, not a transaction.

March 3 — the $4,000 deposit arrives. Sales receipt with the Customer Deposit item:

勘定科目	借方	貸方
Cash	$4,000
Customer Deposits (liability)		$4,000

March's P&L doesn't move. The balance sheet shows $4,000 more cash and $4,000 more liability — richer in cash, deeper in obligation, which is the truth.

April 10 — order ships. Invoice the full sale, terms Net 30, with the deposit applied as a negative line:

Invoice line	金額
500 units custom-labeled product	$10,000
Customer Deposit applied	−$4,000
Balance due (Net 30 → May 10)	$6,000

Behind that document: Accounts Receivable up $6,000, revenue up $10,000 — recorded once, in April, the month you earned it — and the Customer Deposits liability back to zero for this order.

May 6 — the buyer pays $3,500. Not the full balance — their AP ran it as a partial. Receive Payment, applied to the invoice: cash up $3,500, AR down $3,500, invoice open at $2,500.

May 28 — the final $2,500 arrives. Same motion. The invoice closes, and every month along the way told the truth: March was a cash event, April was the sale, May was collections.

Partial Payments and What They Do to Aging

That $3,500 payment deserves its own section, because partial payments are where wholesale AR gets quietly misread.

The mechanics are easy: record a partial payment against the invoice (Receive Payment → apply → deposit), never as a standalone bank deposit. QuickBooks handles the arithmetic and the invoice's open balance shrinks to what's actually owed.

The reading is the part to get right. On your A/R aging report, the remaining $2,500 ages from the invoice's original due date — a partial payment does not reset the clock. That matters because "partial-pay and stall" is a classic B2B collections pattern: a buyer sends 60% on time and the remainder drifts for months while looking, at a glance, like an account in good standing. The aging report isn't fooled. A $2,500 balance in the 31–60 column is a collections item, however promptly the first chunk arrived.

Two habits keep partials from becoming leakage. When a payment doesn't match the invoice, find out why — an unexplained short-pay is sometimes AP timing, sometimes an undeclared dispute you'd rather hear about now. And fold partial balances into the weekly aging review from the net-terms guide; a half-paid invoice needs the same nudge a fully unpaid one does.

Progress Billing for the Genuinely Large Orders

Somewhere above the size of the boutique-chain order, a single deposit-plus-final-invoice stops fitting. A $40,000 private-label run delivered in three stages over four months shouldn't be one April invoice — because the earning itself happens in stages.

QuickBooks Online's tool for this is progress invoicing: build an estimate for the full order, then issue partial invoices against it at each milestone — say 40% at production start, 40% at first delivery, 20% at final. Each invoice recognizes its slice of revenue and creates its own receivable with its own terms, and the estimate tracks how much of the total has been billed.

The line to hold: progress invoicing recognizes revenue at each invoice, so it's only honest when each milestone represents value actually delivered. An invoice for "40% at production start" on an order where the buyer receives nothing until final delivery isn't earned revenue — it's a deposit wearing an invoice costume, and it belongs in the liability account like any other prepayment. Rough rule: money for delivered stages → progress invoice; money ahead of any delivery → customer deposit. Large custom orders often use both, and the revenue-timing calls are exactly what a CPA who knows e-commerce earns their fee on — an hour of their time beats guessing.

Refundable vs. Non-Refundable Deposits

Both kinds start life identically — cash up, liability up — because at receipt you owe the buyer something either way. The difference is what can happen next.

A refundable deposit has two exits: applied to the invoice at fulfillment, or the order dies and it goes back. The refund entry is the liability unwinding — Customer Deposits down, cash down. Revenue is never touched in either direction, which is the quiet payoff of the liability structure: a cancelled order leaves no scar on your P&L, because you never claimed the income.

A non-refundable deposit is not income at receipt, a point worth stating twice because the word "non-refundable" tempts people to book it as earned. While the order is alive, you still owe the goods — it's a liability like any other deposit. "Non-refundable" only changes the cancellation path: if the buyer walks and the contract lets you keep the money, the deposit converts to income at forfeiture — Customer Deposits down, forfeited-deposit income up (most sellers use an Other Income account), dated the day the order actually died. Tax timing on forfeited deposits varies with your accounting method and contract terms — a confirm-with-your-CPA item, not a guess-and-hope item.

Either way, put refundability in writing on the PO or terms sheet before money moves. The books can record whatever happens; they can't settle an argument about what was agreed.

Keeping the Order Layer Clean Underneath

Everything above lives at the invoice-and-liability layer, and most of it is judgment work — deciding what's earned, when, and by how much. No sync tool should do that for you, and you should be suspicious of one that claims to.

What a sync tool should do is keep the layer underneath trustworthy: wholesale orders posting as real QuickBooks invoices, payments applied to the invoices they belong to, retail orders staying out of the way. That's the routing problem covered in the net-terms guide — LedgerPort (our product, so judge accordingly) handles it with invoice-based and tag-based order sync methods, so a wholesale-tagged order becomes an open invoice while retail flows on as receipts. The deposit receipt, the negative-line application, the forfeiture entry — those stay yours, or better, your accountant's: one-per-order events, not volume work, and precisely where a professional pays for themselves. If a CPA or firm runs your books, hand them this workflow — and if they support e-commerce clients generally, our page for accounting professionals covers how firms run the sync layer across a client list.

---

Go back to that Monday wire. The $4,000 was never ambiguous — it was a debt, payable in 500 custom-labeled units, and the only real question was whether your books would say so. One liability account and one deposit item make the answer yes, and no month lies about what it was.

If wholesale deposits are becoming a regular part of your order flow, the wider foundation — chart of accounts, fee handling, the accrual mechanics this all sits on — is in the e-commerce accounting guide. Set up the Customer Deposits account before the next PO lands; it's five minutes now or an untangling later.