Every startup hits the same wall sooner or later. You send an invoice, the cash hasn't arrived yet, and you're staring at your books wondering where to put the number. Accounting for accounts receivable is one of the first real bookkeeping challenges a young company faces, and getting it wrong can distort your financial picture from day one. The concept itself isn't complicated: someone owes you money, and you need to track that promise until it converts to cash. But the details matter. The timing of revenue recognition, the allowance for bad debts, and the classification on your balance sheet all carry weight with investors, lenders, and tax authorities.
If you're a founder running on accrual-basis accounting (which most startups should be), receivables show up the moment you earn revenue, not when the payment lands in your bank account. That gap between earning and collecting is exactly where mistakes hide. This guide walks through the correct treatment, common errors, and what to look for in software that handles the process for you. Whether you're pre-revenue or scaling past your first million in annual recurring revenue, a clean receivables process keeps your financials trustworthy.
Accounts receivable (AR) is the money your customers owe you for goods or services you've already delivered. It's a current asset on your balance sheet. Startups encounter AR the first time they invoice a customer on credit terms, like net-30 or net-60, rather than collecting payment upfront.
Here's the high-level process. First, you record the receivable when you recognize revenue. Second, you estimate any amounts you might not collect and set up an allowance. Third, you record the cash receipt when the customer pays. Fourth, you write off any balance that becomes truly uncollectible. The rest of this guide breaks each step down with journal entries and practical advice so you can get it right from the start.
AR affects two primary accounts: accounts receivable (an asset) and revenue (which flows to equity through retained earnings). Under ASC 606, you recognize revenue when you satisfy a performance obligation, not necessarily when you send the invoice. The receivable is the other half of that entry.
Here's the foundational journal entry when you earn revenue on credit:
This entry tells anyone reading your books: "We performed the work, we're owed payment, and we've recognized the income." No cash has changed hands yet, but accrual accounting demands that you record the economic event when it happens.
When the customer pays, you reverse the receivable:
One more layer matters for startups: the allowance for doubtful accounts. Under ASC 326 (the current expected credit losses model, or CECL), you estimate expected losses over the life of the receivable. For most early-stage companies, a simplified approach works. You estimate a percentage of your outstanding AR that you don't expect to collect, then record it:
The allowance method keeps your balance sheet honest. Investors and auditors expect to see it, even if your startup's AR balance is relatively small.
Recording revenue on cash receipt instead of delivery. Many founders default to cash-basis thinking. If you're on accrual accounting, revenue belongs in the period you earned it, not when the wire hits. Misstating the timing inflates or deflates revenue in the wrong period and can trigger restatements later.
Skipping the allowance for doubtful accounts. It's tempting to assume every customer will pay. But carrying AR at full face value overstates your assets. Even a small estimated reserve (say 2-5% of outstanding invoices) shows financial discipline and keeps your balance sheet realistic for due diligence.
Failing to reconcile AR to the subledger monthly. Your general ledger AR balance should match the sum of individual customer invoices in your subledger. When these drift apart, you lose visibility into who owes what. Reconcile at least monthly, ideally as part of your close process.
The biggest trigger that changes how you record a receivable is when the balance becomes uncollectible. If a customer goes bankrupt or simply stops responding after exhaustive collection efforts, you write off the specific balance against your allowance:
Notice this write-off doesn't hit your income statement again because you already recognized the expense when you set up the allowance. If you later collect on a written-off balance (it happens), you reverse the entry and record the cash.
Another scenario: you offer early-payment discounts (like 2/10, net 30). The discount reduces the amount you collect, and you'll need to record it as a contra-revenue item or a sales discount expense at the time of payment. Your treatment depends on whether you use the gross or net method, so pick one and stay consistent.
Not every tool handles receivables well, especially for startups with unusual billing structures. Here's what to look for:
Automatic revenue recognition tied to invoicing. Good software creates the AR journal entry the moment an invoice is generated and performance obligations are met. You shouldn't need to make a manual entry every time you bill a customer.
Aging reports and allowance tracking. The right platform generates aging schedules (0-30 days, 31-60, 61-90, 90+) automatically. It should also let you set allowance percentages by aging bucket so your bad debt estimate stays current without spreadsheet gymnastics.
Subledger-to-GL reconciliation. Your software should reconcile individual customer balances to the general ledger AR account in real time. If you have to export data to a spreadsheet to check whether your numbers tie, that's a red flag. Clean reconciliation prevents the drift that causes month-end headaches.
Is accounts receivable a debit or credit?
Accounts receivable carries a normal debit balance. It's an asset, and assets increase with debits. When you record a sale on credit, you debit AR and credit revenue. When the customer pays, you credit AR to reduce it and debit cash. If your AR account shows a credit balance, something's wrong: it usually means you recorded a payment without a matching invoice or over-applied a credit memo.
Is accounts receivable an asset or a liability?
AR is a current asset. It represents money owed to your company, not money you owe someone else. On the balance sheet, it sits under current assets because you expect to collect it within one year (or one operating cycle). Investors look at your AR balance relative to revenue to gauge how quickly you're collecting. A growing AR balance without corresponding revenue growth can signal collection problems.
What happens when a receivable becomes uncollectible?
You write it off against the allowance for doubtful accounts you've already established. The journal entry debits the allowance (reducing the contra-asset) and credits accounts receivable (removing the specific customer balance). Your income statement isn't affected at the write-off stage because you already recognized the bad debt expense when you set up the allowance. If you never created an allowance, you'd record the full write-off as bad debt expense in the current period, which creates an earnings hit.
How does AR differ for SaaS startups versus product companies?
SaaS companies often bill monthly or annually in advance, which means deferred revenue (a liability) is more common than AR. You only record a receivable for the portion of the subscription you've already delivered. A product company, by contrast, typically records the full invoice amount as AR upon shipment. The key distinction is timing: SaaS revenue recognition under ASC 606 is spread over the service period, so your AR balance tends to be smaller relative to total contract value.
Should a pre-revenue startup worry about AR?
Not yet, but you should understand the mechanics before your first invoice goes out. Setting up your chart of accounts with proper AR accounts, allowance accounts, and aging categories takes minutes now and saves hours later. The moment you issue your first invoice on credit terms, you'll need these accounts ready. Waiting until you have dozens of outstanding invoices to build the structure is a recipe for messy books.
Puzzle is the AI-native accounting platform built for startups and the firms that serve them. From SAFEs to stock comp, Puzzle categorizes complex transactions correctly the first time, with a clean audit trail your accountant will actually trust. Spend less time second-guessing journal entries and more time on the work that matters.
