01
When does an amount become accounts receivable?
A receivable normally follows an issued customer invoice with payment due later. The invoice identifies the customer, amount, currency, due date and supplied goods or services. Before issue, a draft or quote may represent expected billing but should not be treated as an open customer balance.
The exact accounting entry belongs in the designated accounting system. Operationally, the billing team needs the invoice state, due date, delivery evidence and owner so an open amount is not mistaken for an incomplete draft.
- Draft: not yet an open customer invoice.
- Sent and not due: open, but not overdue.
- Past due: open beyond its due date.
- Paid and matched: closed against payment evidence.
See the operating model in the Accounts Receivable hub.
02
How is receivable different from revenue and cash?
Receivable describes an amount owed by a customer. Cash describes money received. Revenue is an accounting concept whose treatment depends on the applicable policy and facts. The three may occur at different times and should not be used as synonyms.
A billing workflow can show that an invoice was sent and remains open, but the accounting platform remains responsible for ledger treatment. Keeping that boundary avoids turning operational status into an unsupported accounting conclusion.
- Invoice issued on credit: may create an open receivable.
- Payment received: creates payment evidence that still needs matching.
- Revenue treatment: determined under the applicable accounting process.
Clarify the originating document in what is an invoice.
03
What states make receivables actionable?
A useful receivable list goes beyond open or closed. Not due, due soon, overdue, disputed, promised, partially paid and unmatched-payment states imply different next actions. Each item should retain an owner and enough context to act without rediscovering the customer history.
A disputed invoice should not receive the same message as an ordinary late invoice. An unmatched payment should be investigated before another reminder is sent. State quality is therefore more important than a large count of automated messages.
- State
- Owner
- Age or due date
- Dispute or promise context
- Next action and date
Group open balances with an AR aging report.
04
Worked example: one invoice, several possible states
A business issues a $12,000 invoice on 1 August with payment due on 31 August. On 20 August it is an open receivable but not overdue. On 5 September, if no payment or dispute is recorded, it is five days past due and ready for the appropriate follow-up.
If the customer pays $7,000 and that payment is matched, the remaining open amount is $5,000. The record should show both the original invoice total and the matched payment rather than overwriting history with only the current balance.
- Original invoice: $12,000
- Matched payment: $7,000
- Remaining receivable: $5,000
- Next action follows the remaining balance and current state.
Design proportionate follow-up through payment reminders.
05
How should a team manage accounts receivable?
Begin with accurate delivery and due dates, then segment open invoices by state and age. Verify the record before contacting the customer, use reminders proportionately, assign disputes and promises to named owners, and match payments promptly.
Management is a continuous control loop, not a single month-end report. Aging, collections and reconciliation are different views of the same open-record lifecycle and work best when their states remain connected.
- Verify
- Prioritise
- Contact
- Resolve
- Match and close
Close paid records through reconciliation.
Continue in context