Accounts Receivable Collections: A Beginner’s Guide

Late payment can reflect a lost invoice, missing approval, billing error, dispute, customer cash pressure, or refusal. A controlled follow-up process identifies the cause early and routes it to the person who can resolve it.

Prevention beats collection

• Invoice the day work completes. Every day of delay is added to the front of your cycle
• Confirm before starting who approves payment and where the invoice should go
• State terms on the invoice and reference them in the contract
• Make paying easy: multiple methods, no login required, correct reference
• Take deposits or milestone payments on larger work

These controls can reduce preventable collection work and make overdue items easier to diagnose.

Make the call

When email does not identify the cause, contact the person who approves payment or owns the commercial relationship. A short conversation may surface a missing invoice, purchase-order problem, dispute, or payment queue. Record the result and next commitment.

When to escalate

Eventually, the options may include an approved payment plan, pausing service where the contract permits, a collections agency, or legal action. Each option has cost, legal, and relationship consequences that should be evaluated before use.

The practical test is whether the amount justifies the cost and whether you want the customer again. Note that the ability to charge late payment interest or fees depends on your contract terms and applicable law, so confirm what applies rather than assuming.

Know when to stop

Continuing to work for a customer who is significantly overdue increases your exposure rather than improving your chances of payment. Deciding a stop-work threshold in advance, and applying it consistently, is easier than deciding under pressure.

Watch concentration

If one customer represents a large share of receivables, their payment behaviour is a structural risk rather than an inconvenience. That is worth monitoring in the aging report as a number, not a feeling.

Start with a collectible ledger

Before contacting a customer, prove the invoice exists once, was issued to the correct legal customer, reached the required approver, reflects the contract or purchase order, and remains open after receipts and credits. Reconcile the aging to the accounts receivable control account and record unapplied cash separately.

Collection activity built on a damaged aging wastes time and can harm trust. Give each invoice a unique ID, due date, original amount, open amount, dispute status, last contact, promised date, next action, and owner.

Segment by cause and risk

Separate administrative delay, billing error, commercial dispute, promised payment, customer cash pressure, and refusal. These are different problems. A missing purchase order needs correction, a dispute needs an operational owner, and a broken promise needs escalation.

Prioritize using amount, age, concentration, dispute status, payment history, strategic importance, and the effect on the cash forecast. Do not let small easy calls crowd out one material exposure, and do not let a large customer remain untouched because the relationship feels sensitive.

Use a status-based sequence

Send a pre-due confirmation when the invoice or approval path warrants it. On the due date, confirm payment status and any missing requirement. At the first overdue review, attach the invoice and ask for a specific cause and payment date. If unresolved, contact the approver or commercial owner and document the next commitment.

Escalate when a promised date is missed, a dispute has no owner, exposure is increasing, or the customer stops responding. The cadence should reflect the contract, customer process, amount, relationship, and legal context rather than a universal number of days.

Manage disputes outside the reminder queue

Record the disputed item, customer position, internal owner, evidence needed, decision authority, and target resolution date. Pause repetitive reminders while the dispute is actively owned, but keep the invoice visible in the aging and forecast.

When resolved, issue an approved credit or correction promptly, or restate the amount due with supporting evidence. A dispute is not closed because a customer stopped replying, and it should not disappear through an unexplained write-off.

Control promises to pay

Record the person, amount, date, payment method, and conditions of every promise. Follow up when the date passes and distinguish a bank timing issue from a missed commitment. Repeated broken promises are evidence that the account’s risk and future terms may need review.

Payment plans should be written, approved, reconciled to the ledger, and monitored. Confirm how interest, fees, releases, security, or other terms are treated under the agreement and applicable law before offering them.

Coordinate commercial escalation

Define who can place an account on hold, change credit terms, approve a plan, issue a credit, refer the matter externally, or authorize legal action. Sales and operations should see material overdue exposure before accepting new work that increases it.

Preserve the contract, purchase order, delivery or acceptance evidence, invoice, statements, correspondence, credits, and payment history. External recovery options depend on facts, jurisdiction, contract, limitation periods, and cost, so qualified advice may be required.

Measure process quality

Track the aged balance, customer concentration, disputed amount, unapplied cash, kept and missed promises, invoice delivery failures, and time spent waiting for internal resolution. Use trends to change billing and service workflows, not merely to score the collector.

Compare expected receipts with actual collections in the cash forecast. Classify variance as timing, dispute, omission, amount, or customer risk. This creates evidence for future collection assumptions.

Illustrative collection review

As an illustrative example, suppose one customer has a current invoice awaiting its normal payment run, a second has an overdue invoice missing a purchase order, and a third missed a written payment promise. The first needs confirmation, the second needs billing correction, and the third needs escalation. One generic reminder would treat three different causes as one problem.

Weekly control checklist

• Aging agrees with the ledger and report date
• Unapplied receipts and credits are visible
• Every material overdue invoice has an owner
• Disputes have evidence and resolution dates
• Promises to pay are recorded and followed
• Commercial teams can see increasing exposure
• Escalation authority is defined
• Expected receipts feed the cash forecast

Feed collection evidence into credit policy

Use payment history, disputes, concentration, and broken commitments when approving new limits, deposits, milestones, or terms. Credit decisions should consider expected margin and exposure together. A large sale can strain cash if the business must fund delivery before the customer pays.

Review policy exceptions separately. Record who approved the exception, amount exposed, reason, expiration, and monitoring plan. Do not allow a one-time commercial decision to become an undocumented permanent term.

Close the loop with billing

Summarize recurring collection causes by source: missing purchase orders, incorrect customer data, late acceptance, wrong rates, duplicate invoices, unclear tax, or disputed delivery. Assign the process owner and verify that the fix reduces future exceptions.

Collection work should become easier when the source process improves. If the same cause repeats, adding more reminders treats the symptom while preserving the failure.

Retain a month-end aging snapshot and the associated status log. Comparing successive snapshots shows whether balances were collected, credited, disputed, promised, written off, or simply rolled forward without a decision.