Asset Management Strategies: A Layered Guide to Capital Allocation
How objectives, allocation, manager choice, costs and review fit together
A practical reference on credit decisions, invoicing, aging, collections and controls
Accounts receivable is the money customers owe for goods and services already delivered. How a business governs that balance decides how quickly it becomes cash. This reference walks through the full cycle, from the credit decision that creates a receivable to the collections, dispute handling and allowance for doubtful accounts that follow. It explains why days sales outstanding and aging distribution matter more than the total balance, why invoice accuracy prevents more disputes than aggressive chasing, and how to scale collection effort to exposure and risk. Worked numbers, a checklist and common mistakes close the book.
Start readingAccounts Receivable Management: Turning Credit Sales Into Cash
A practical reference on credit decisions, invoicing, aging, collections and controls
Accounts receivable is the money a customer owes for goods or services a business has already delivered. It arises at the point of sale when the business agrees to be paid later rather than immediately. On the balance sheet it is a current asset, because the business expects to convert it into cash within its normal operating cycle.
The field sits within broader credit management. Practitioners decide who receives credit, on what terms, how invoices are issued and corrected, how overdue balances are pursued, and how doubtful amounts are provided for. A competent practitioner is expected to review the receivables process, identify bad and doubtful debts, check compliance with agreed terms, plan recovery actions and prepare reports with supporting documentation.
A receivable is created at the moment of sale, so its quality is decided before any invoice is chased.
This reference treats receivables as a cash problem first and an accounting entry second. A sale on credit is only complete when the cash arrives. The rest of the book follows that cycle in order.
| Assess | Invoice | Collect | |
|---|---|---|---|
| Credit | ●●● | ● | ● |
| Billing | ● | ●●● | ● |
| Recovery | ● | ● | ●●● |
Several terms recur throughout the field. Credit limit is the maximum exposure a business accepts to one customer. Payment terms state when an invoice falls due, for example net thirty days. Aging groups open balances by how long they have been outstanding. Days sales outstanding, often shortened to DSO, estimates the average number of days needed to collect after a sale. Allowance for doubtful accounts is a reserve that estimates the part of receivables that may not be collected.
Cash application is the step where incoming payments are matched to the invoices they settle. Unapplied cash and misapplied cash both distort aging and make customers look more overdue than they are. Dispute refers to any claim by the customer that an invoice is wrong in amount, quantity, pricing or delivery.
Clear shared vocabulary between sales, credit and finance prevents many avoidable disputes.
Learning this vocabulary first makes the later sections easier. Most conversations about receivables turn on a few of these words, and using them consistently prevents confusion between sales, credit and finance staff.
Receivables are one of the largest components of working capital for many businesses, alongside inventory and cash itself. Money tied up in receivables cannot pay suppliers, wages or debt. For that reason, the size of the balance matters less than how long each dollar stays outstanding.
A useful way to see the mix is to break total working capital into its main drivers. Receivables usually compete with inventory and payables for management attention. A business can have a healthy sales record and still run short of cash if collections are slow, which is why receivables deserve direct governance rather than being left to the accounting period close.
A large receivables balance is only a problem when it ties up cash for longer than the business can afford.
The share of working capital held in receivables varies by industry and business model. Practitioners should compare their own balances over time and against agreed targets instead of relying on a single benchmark figure.
Receivables work is shared across several functions. Sales proposes customers and commits to terms. Credit assesses risk and sets limits. Billing or invoicing produces accurate documents. Accounts receivable staff apply cash, maintain customer records and monitor aging. Collections pursues overdue amounts. Finance records the allowance and reports results to management.
Clear ownership matters because gaps appear at the handoffs. When sales promises terms that credit has not approved, or billing issues an invoice with the wrong purchase order number, the problem surfaces later as a collections dispute. Written procedures and defined escalation paths reduce these gaps.
Most receivables problems begin at a handoff between functions, not inside a single team.
Practitioners are expected to follow company policies and relevant legislation, and to document recovery actions. Accountability for the process should be clear enough that any balance can be traced to a named owner.
Every receivable starts with a credit decision. Before extending terms, a business should understand the customer's ability and willingness to pay. Practitioners gather information such as trade references, financial statements where available, payment history with the business, and the size of the exposure requested relative to the credit limit.
The decision is best made with a consistent framework rather than personal judgment alone. A common approach ranks customers into risk classes and ties each class to a maximum limit, shorter or longer terms, and required security such as a deposit or guarantee. Higher exposure justifies more scrutiny, and lower exposure can be approved more quickly.
Set the credit limit before the sale, because the limit is the cheapest control a business has.
Credit decisions should be revisited as circumstances change. A customer whose payments slow, whose order size jumps, or whose industry weakens may need a lower limit even though it was once approved comfortably.
Receivables follow a repeating cycle. The business assesses a customer, agrees terms, delivers and invoices, monitors payment, and then reviews what happened. The review feeds back into the next credit decision, so each cycle should leave the process slightly better governed than before.
Thinking in a cycle helps practitioners avoid treating collections as an isolated task. A late payment is information about the customer, the invoice, the terms and the earlier credit decision all at once. Practitioners who review patterns across many cycles can tighten limits, correct recurring invoice faults and adjust terms.
Each collection outcome should feed back into the next credit decision for the same customer.
The cycle has no fixed end date for an individual customer. It runs continuously while the relationship lasts.
An invoice is the document that makes a receivable enforceable in practice. It should state the customer, the goods or services supplied, the quantities, unit prices, taxes, total amount, payment terms and any purchase order or reference the customer requires. Errors in any of these fields give the customer a reason to withhold payment.
Good practice is to check the invoice against the customer's own records before it is sent, where the process allows. Matching the value and the referenced order, and confirming that delivery has been recorded, prevents many disputes that would otherwise surface only at the collection stage.
A correct invoice sent a day late usually collects faster than a fast invoice that must be reissued.
Accuracy therefore comes before speed. Sending a wrong invoice quickly is often more costly than sending a correct one a day later.
Once an invoice is sent, the business waits for payment. The sequence from issue to cash moves through several stages: the customer receives and approves the invoice, the payment is scheduled, the payment is sent, the funds arrive, and the receipt is applied to the invoice. Delays can occur at any stage.
Practitioners should map this flow for their own business so they can see where time is lost. Approval delays on the customer side are often outside the seller's control, but internal delays in matching remittances to invoices are not. Clear remittance details on each invoice help customers pay the right amount to the right reference.
Find out where the delay sits before deciding whether the customer or your own process needs fixing.
Tracking each stage makes it possible to tell a slow customer from a slow internal process, which call for different responses.
An aging report groups open balances into buckets such as current, one to thirty days overdue, thirty-one to sixty, sixty-one to ninety, and over ninety days. The distribution across these buckets matters more than the total. A balance that is mostly current is in a very different position from one with a large share over ninety days, even when the totals match.
The example below is illustrative and shows how a distribution can reveal risk. Practitioners should focus on the share in older buckets, because those balances are most likely to need allowance or escalation. Trends across several periods are more informative than a single snapshot.
Watch the share of balances in the oldest buckets, not just the total receivable figure.
Aging should be reconciled to the general ledger regularly. Unapplied cash and misposted items can inflate older buckets and send collectors after customers who have already paid.
Days sales outstanding estimates how many days, on average, the business takes to collect after a sale. A lower figure generally means cash is returning faster. Practitioners often calculate it from receivables and credit sales over a chosen period, and then compare the result against the stated payment terms.
Tracking DSO over time reveals direction. A rising trend suggests that collections are slipping or that customers are stretching terms. A figure well above the standard terms points to an issue worth investigating, such as weak collections follow-up, customer disputes or a shift toward slower-paying accounts.
Compare DSO against your actual payment terms, because a figure far above them signals stuck cash.
DSO should be read alongside aging, because an average can hide a few very old balances. Use both measures together to see whether the problem is broad or concentrated.
Customers can be sorted into risk classes so that exposure is managed consistently. A simple scheme might distinguish low, medium and high risk based on payment history, financial strength, industry conditions and the size of the requested balance. Each class carries a default limit, a standard set of terms and rules for when extra security is needed.
The matrix below rates three common decision factors against the three areas of exposure. Practitioners can adapt the criteria to their own portfolio. The purpose is to make the reasoning visible and repeatable rather than to produce a precise score.
A consistent risk class gives sales and credit a shared reason for every limit decision.
When a customer moves to a higher risk class, the business should adjust its limit promptly, even if the customer has not yet missed a payment. Waiting for a default is usually too late to limit losses.
| Low | Medium | High | |
|---|---|---|---|
| History | ●●● | ●● | ● |
| Strength | ●●● | ●● | ● |
| Size | ● | ●● | ●●● |
A collection strategy sets out what the business does at each stage of lateness. Early contact is usually a reminder that confirms receipt of the invoice and asks when payment will be made. Later contact escalates to a named contact, a payment plan or a formal demand. The strategy should be written so that every collector follows the same sequence.
Effort should scale with exposure and risk, not with how loudly a customer complains. A large, high-risk balance may justify senior attention, while a small, low-risk balance may need only a polite reminder. Treating every overdue account the same wastes effort and can damage valuable relationships.
Scale collection effort to exposure and risk class, not to the volume of a customer's complaints.
Documentation matters at every stage. Each contact, promise to pay and agreed plan should be recorded with a date so that the next collector understands the history.
When a customer cannot pay in full, a structured payment plan can recover more than an unsupported demand. A plan sets out the amount, the timing and the consequence of missing an instalment. It should be agreed in writing and confirmed by both parties, with the balance still shown on the aging report until it is cleared.
Negotiation works best when the business understands its own position. It should know the minimum it will accept, the point at which legal recovery is considered, and whether a reduced settlement is commercially sensible. Concessions should be tied to firm commitments rather than given freely.
A written payment plan with clear consequences recovers more than a verbal promise to pay.
Plan terms must comply with company policy and applicable law. Practitioners should check requirements before agreeing terms that affect how a debt may be pursued.
A dispute is a customer claim that an invoice is in correct, in complete or not owed. Common causes include wrong quantities, price differences, missing purchase order references, goods not received and services not performed as agreed. The first step is to log the dispute, separate the disputed amount from the undisputed balance, and tell the customer which part is not in question.
Resolution depends on the facts. Practitioners check delivery records, contracts, purchase orders and pricing agreements. Where the business is at fault, it should correct the invoice promptly by issuing a credit note and a replacement invoice. Where the customer is wrong, the response should be clear and well documented.
Separate the undisputed amount from the dispute so that the customer has no excuse to hold back everything.
Disputes should be tracked to their cause. Repeated disputes about the same product, customer or process signal a systemic fault worth fixing at the source.
Not every receivable will be collected. The allowance for doubtful accounts is a reserve that estimates the portion of receivables that may not be paid. Under accepted accounting practice, receivables should be reported at net realizable value, meaning the amount expected to be collected rather than the gross balance.
At each reporting period, the business assesses whether there is objective evidence that a receivable is impaired, such as a customer entering bankruptcy or a sustained default. Where impairment is identified, the expected loss is recognized, usually by increasing the allowance. When an amount is confirmed as uncollectable, it is written off against that allowance.
Report receivables at the amount you expect to collect, not the gross amount on the invoices.
Estimates of the allowance can be based on aging patterns, historical loss experience and specific customer information. Practitioners should document the method used and review it regularly, because an unreasonable allowance can misstate reported results in either direction.
Recovery is itself a cycle. Practitioners assess the account, choose a recovery step, carry it out, and then review the outcome. The review decides whether the next step should be the same, stronger or different. Without the review step, collectors tend to repeat the same reminder long after it has stopped working.
The cycle should use the records kept along the way. Each promise to pay, payment received, dispute logged and plan agreed becomes evidence for the next decision. Reviewing outcomes across many accounts also shows which tactics work for which risk classes.
Review each recovery outcome so the next action is chosen from evidence rather than habit.
Recovery actions that go beyond the normal process, such as formal legal steps, should follow company policy and be approved at the right level. Practitioners should never take an action that is not sanctioned, and should note where the boundary of their authority lies.
Putting the process in place starts with written procedures. These describe how accounts move through stages, what each collector must record, who approves exceptions and how escalation works. A written process lets a new practitioner step in without guesswork and gives managers something to audit.
The process typically moves through a short sequence: confirm the invoice was received, establish the expected payment date, follow up on any agreed date, escalate where promises are broken, and hand over to formal recovery only when the policy allows. Each step has a defined owner and a recorded outcome.
A written step-by-step process lets any trained collector pick up any account without losing ground.
Practitioners should also set rules for communication frequency and tone so that customers are not contacted more often than the relationship supports.
Consider the path a single order takes. A customer asks for goods on credit. Credit checks the account and approves a limit that covers the order. Sales confirms the agreed terms. Billing issues the invoice after delivery. The customer approves it, pays on the due date, and the payment is applied to the invoice.
Each step can introduce a problem. If the order exceeds the limit, the sale should be held or re-approved before delivery. If the invoice quotes a different price from the order, the customer will dispute it. Tracing the path shows exactly where a broken link would have changed the outcome.
Check the credit limit before delivery, because approval after shipment removes your leverage.
This flow is the basis for the controls described later. Every handoff is a point where an error can be caught early.
Performance is easier to manage with a small set of measures. Common ones include DSO, the share of balances in the oldest aging buckets, the amount of bad debt written off, the rate of disputes per thousand invoices, and the proportion of cash received on or before the due date. Each measure answers a different question about the process.
Measures should be reported on a fixed schedule with a stated target. Chart results over time so that changes are visible. Because a single good month can hide a longer problem, practitioners should look for sustained movement rather than one-off results.
Track a small set of receivables measures on a fixed schedule so that trends are visible.
The figures below are illustrative and show how one measure, the share of invoices paid on time, might be presented for comparison across segments. They are not benchmarks for any particular business.
Accounts receivable software can automate reminders, track due dates, match remittances to invoices and produce aging reports. Automation shifts the practitioner's time away from routine tasks and toward exceptions, disputes and risk decisions. It also reduces the chance of for getting a follow-up on a large balance.
Automation is only as good as the data behind it. In accurate customer master records, wrong payment terms or unmatched cash will be processed faithfully and produce wrong reminders. Practitioners should validate setup data before relying on automated outputs, and should review exceptions the system flags.
Automation amplifies good data and bad data alike, so validate the setup before trusting the reminders.
Tools also support controls, such as segregation of duties and approval thresholds for credit notes and write-offs. The choice of tool should be guided by the process it must support, not the other way round.
Choosing a response means weighing the amount at stake against the risk of the customer and the strength of the relationship. The matrix below rates three response types against three situations. A high-value, high-risk balance usually warrants a firm response, while a low-value, low-risk one is better served by a quick reminder.
Avoid the temptation to apply the strongest tool everywhere. Heavy pressure on a valuable, reliable customer over a small late payment can cost more in relationship damage than the money recovered. Conversely, a soft approach to a high-risk, large balance can let exposure grow unchecked.
Match the intensity of your response to the exposure and the risk, not to your frustration.
Practitioners should document the reasoning behind a response so that decisions are consistent and can be reviewed later.
| Reminder | Escalate | Recover | |
|---|---|---|---|
| Small | ●●● | ●● | ● |
| Large | ● | ●● | ●●● |
| High risk | ● | ●● | ●●● |
Several mistakes recur across receivables operations. Approving limits without checking current exposure lets balances grow past what the business can absorb. Sending invoices with errors invites disputes that delay payment for weeks. Chasing the largest complaint instead of the largest exposure wastes effort on the wrong accounts.
Other common faults include leaving unapplied cash unmatched so that customers look overdue, failing to record promises to pay so that the next collector starts from zero, and delaying the allowance until a loss is certain rather than when evidence of impairment exists. Each of these is avoidable with routine checks.
Most receivables losses trace back to a control that was skipped, not to a single unlucky customer.
Practice improves when mistakes are reviewed without blame. A short post-mortem on a bad debt or a recurring dispute often identifies a process fix that prevents many later cases.
Use this checklist to test an operation. Are credit limits set before sales and reviewed when risk changes? Are invoices matched to customer records and delivery before they are sent? Is the aging report reconciled regularly, and is unapplied cash cleared? Are disputes logged, separated from undisputed amounts and tracked to root cause?
Continue with the review questions. Is DSO compared against actual terms and trended? Is the collection strategy written and scaled to exposure and risk? Is the allowance based on a documented method and reviewed each period? Are recovery actions taken within policy and recorded with dates?
A yes to every checklist question means the cycle is governed; any no marks the next improvement.
A process that answers yes to these questions is well governed. Any no points to the next improvement to make.
Accounts receivable management is the discipline of turning credit sales into cash on time and at the right value. It begins with a credit decision, depends on accurate invoices, is monitored through aging and DSO, and is governed through collection strategy, dispute handling and an honest allowance for doubtful accounts.
The key ideas to carry forward are these. The balance matters less than its age. Invoice accuracy beats speed. Collection effort should follow exposure and risk. Every outcome should feed the next credit decision. Measures should be few, consistent and reviewed on schedule.
Govern the whole cycle, from credit decision to cash, and the balance will take care of itself.
Practitioners who apply these ideas consistently will find that cash arrives more predictably, disputes fall, and reported results reflect a fair view of what the business will actually collect.
How objectives, allocation, manager choice, costs and review fit together
How scattered holdings become a governed, measured investment system
Matching, investigating and signing off cash records that agree with the bank
A practical reference for turning strategy into numbers and keeping plans responsive
Payment Successful!
Check your email for the course access link.
For quick, secure checkout on the next step
Non-Refund Policy
All course purchases on vaayaa.com are non-refundable. Since the courses are pure text with no streams, the full digital course content becomes accessible immediately after payment. Therefore, we cannot process refunds once a purchase is completed.
Please ensure you have reviewed the course details before proceeding with your purchase.