Financial Planning
Accounts Receivable: Organize Invoices and Follow Up Clearly
Understand accounts receivable, build an invoice-aging register, and follow up on customer balances without confusing invoices with cash.

What you will learn
- Explain receivables versus revenue and cash.
- Age outstanding invoices consistently at a stated date.
- Reconcile balances and assign a clear next action.
Accounts receivable is money customers owe for credit sales. A useful receivables process tells you which invoices remain open, which payments or credits have arrived and who owns the next conversation. Start with a reconciled balance, then use invoice aging and dispute notes to make follow-up specific. An invoice total is not collected cash.
What does it mean to do accounts receivable?
OpenStax’s receivables discussion separates the credit sale from later collection. The operational job connects the customer, source invoice, due date, receipts, credits and unresolved differences. Recording a collection against an existing receivable does not create revenue again.
Keep your accounting system as the balance source. A customer-conversation tool can hold context and follow-up, but it should not become a competing ledger. If the customer disputes the invoice, preserve the dispute and assign someone to resolve it rather than overwriting the amount to make the list look clean.
Build an aging register that people can use
Fictional professional-services example as of November 15, 2026. Age by days past the contractual due date, not by invoice age. The amounts below are already net of confirmed receipts and approved credits. Future-due invoices are not overdue.
Original invoice-aging and action register
| Invoice | Due date | Remaining | Days past due | Next action |
|---|---|---|---|---|
| A104 | November 20, 2026 | $4,000 | Not yet due | Confirm customer has the invoice |
| A105 | November 10, 2026 | $3,000 | 5 | Ask the agreed contact to confirm payment status |
| A106 | October 20, 2026 | $5,000 | 26 | Resolve a documented scope dispute with the service owner |
| A107 | September 30, 2026 | $2,000 | 46 | Escalate internally for an evidence-based review |
| Total open balance | As of November 15 | $14,000 |
Aging buckets such as current, 1–30, 31–60 and 61+ days are organizational choices, not universal collection instructions. State the boundaries so a due-today invoice does not move between categories depending on who prepared the report.
Reconcile the total before drafting follow-up
Suppose opening receivables were $18,000. New invoices add $12,000, confirmed receipts subtract $15,000, and approved credits subtract $1,000. Closing receivables are $18,000 + $12,000 - $15,000 - $1,000 = $14,000, matching the register.
Investigate an unmatched payment before sending a reminder. A receipt may be posted to the wrong customer or an approved credit may not yet be reflected. Do not assume every aging exception means the customer has failed to pay.
Make the next message specific and respectful
A useful reminder identifies the invoice, remaining balance, due date, relevant record and a clear request. For example: “Could you confirm the payment status of invoice A105, with $3,000 outstanding and a November 10 due date? If a purchase-order reference or supporting record is missing, please let us know.” This fictional draft is not a demand letter or legal collection advice.
The IRS recordkeeping overview explains the role of supporting transaction documents. For this task, preserve invoice versions, payment confirmations and approved adjustments. Do not place sensitive payment details in an AI prompt or act on an unverified bank-account change.
What is accounts receivable vs payable?
Receivables are amounts customers owe the business; payables are amounts the business owes suppliers. The same commercial relationship can have separate balances, so identify the legal counterparty and source record. Do not net unrelated obligations merely because names look similar.
Use the commercial-events lesson to distinguish a contract, invoice and receipt. The cash-cycle lesson aggregates collection timing, while this register owns the invoice-level action.
Close the loop on the relationship
For each exception, record a factual status, accountable owner, last communication and next agreed step. Keep disputed, promised, scheduled and confirmed-paid states distinct. A promised payment is not evidence that the funds arrived.
Keep the customer conversation connected to the payment question. Use Finta CRM for relationship history and follow-up context, and ask Aurora to draft a respectful reminder from the invoice facts you provide. Review the message before sending and update the receivable balance through your accounting process, not a separate CRM ledger.
Copyable AI prompt
Try this with Aurora AI in Finta, Codex, or Claude. Share only information you are allowed to use, and check the answer before acting.
Using [authorized invoice-aging extract] and [approved customer notes], draft an exception register with invoice, remaining amount, due date, aging basis, dispute, evidence, owner and next action. Reconcile the stated balance movements. Draft respectful status requests only from supplied facts. Flag unmatched payments and unknowns. Do not send messages, alter balances, expose bank details or provide legal collection advice. Human review required.Finta Field Guide. By Finta Editorial Team. Sources checked November 15, 2026. Examples and worksheets are original fictional teaching exercises, not customer results or benchmarks. General education, not individualized accounting, financial, investment, legal or tax advice.