What Is Accounts Receivable Management? A Complete Guide for Finance Teams
Invoicing a customer is not the same as being paid by one. This guide covers what accounts receivable management actually involves — the full cycle, the ownership problem, the metrics worth reporting, and the mistakes that quietly add weeks to your DSO.
On this page
Key takeaways
- Accounts receivable management is everything that happens between issuing an invoice and banking the cash — it is not invoicing, and it is not accounting.
- In the UAE, around half of B2B sales are made on credit at an average of 47 days, and 58% of those credit sales are paid late. Late payment is the norm, not the exception.
- The single biggest structural failure is ownership: when receivables belong to "finance" in general, no individual account has a named person chasing it on a named date.
- Four numbers tell you almost everything: DSO, Best Possible DSO, Collection Effectiveness Index, and promise-kept rate. Most teams track only the first.
- Cutting DSO by 23 days on AED 12m of annual credit sales releases roughly AED 756,000 of cash permanently — that is the size of the prize.
Every finance team has had the same conversation. Sales hit target, revenue looks healthy, the P&L is fine — and yet the first week of the month is spent working out which supplier can wait. The invoices went out. The money did not come in.
That gap is where accounts receivable management lives. It is one of the few areas of finance where a moderately better process produces cash directly, without a single extra sale, and it is also one of the most consistently under-managed — usually because it looks like admin and gets staffed like admin.
This guide covers what AR management actually involves, who should own each part of it, the numbers worth putting in front of a CFO, and the failure patterns that show up again and again in receivables ledgers. It is written for finance managers, credit controllers and business owners who already know what an invoice is, and want to know why theirs are not being paid on time.
What accounts receivable management actually is
Accounts receivable management is the process of converting credit sales into cash, on time, without damaging the customer relationship. It starts before the first invoice is raised — with the decision to extend credit at all — and it ends when the payment is received, applied to the correct invoice, and reconciled.
It is worth being precise about this, because AR management is routinely confused with three adjacent things that it is not.
| Function | What it does | How it differs from AR management |
|---|---|---|
| Invoicing / billing | Produces and delivers the invoice document | Ends the moment the invoice is sent. AR management begins there. |
| Accounting / bookkeeping | Records the receivable and the payment in the ledger | Records what happened. AR management is about changing what happens. |
| Debt collection agency | Recovers debts that have already failed, usually on commission | A last resort for a small fraction of the book. AR management is about the other 95%. |
| ERP / accounting system | Holds invoices, payments and balances as the book of record | Stores the data. It rarely holds the chase history, the promises, or who is responsible. |
The distinction matters commercially: teams that already have an ERP often assume they already have AR management. They have the ledger, not the process.
Why receivables are a working-capital problem, not an admin problem
The reason AR management gets under-resourced is that its cost is invisible. Nobody sends you an invoice for slow collections. But the money is real, and it is straightforward to size.
Days Sales Outstanding (DSO) measures the average number of days between making a credit sale and collecting the cash:
For context on what "normal" looks like regionally: Atradius' 2025 Payment Practices Barometer found that around half of UAE B2B sales are transacted on credit, at average payment terms of 47 days, and that 58% of credit-based sales are paid late — most often, the survey reports, because of administrative bottlenecks inside the customer's own payables process rather than an inability to pay. Bad debts averaged around 8% of overdue invoices.
Read that carefully, because it reframes the job. If the dominant cause of late payment is administrative friction rather than distress, then most of your overdue balance is not a collections problem at all. It is a documentation and follow-up problem — and those are fixable by process, not by pressure.
The seven stages of the accounts receivable cycle
A complete AR process has seven stages. Most teams run four of them well and treat the other three as somebody else's job — which is exactly where the leakage happens.
| Stage | What happens | Typical failure mode |
|---|---|---|
| 1. Credit assessment | Decide whether to sell on credit, and how much | Credit granted by sales on relationship, with no documented limit |
| 2. Terms and documentation | Agree payment terms; capture LPO, contract and delivery evidence | Missing purchase order reference — the invoice is unpayable and nobody knows |
| 3. Invoicing | Raise and deliver an accurate invoice promptly | Invoice raised days late, or sent to a person rather than the payables inbox |
| 4. Aging and monitoring | Bucket open invoices by age; identify what needs action | Aging report rebuilt monthly in Excel, out of date within 48 hours |
| 5. Follow-up and collection | Contact the customer, resolve blockers, secure a commitment | Contact happens; the commitment is never recorded or followed up |
| 6. Payment application and reconciliation | Match receipts to invoices; agree the statement of account | Payments applied on account, so the aging report ages the wrong invoices |
| 7. Escalation, dispute and write-off | Escalate, hold supply, negotiate, or provide for the debt | No trigger for escalation, so accounts drift into 90+ by default |
Stages 5 and 6 are where the largest recoverable gains sit, and they are the two most often left to individual habit. If you only change one thing after reading this, make it stage 5: record every commitment a customer makes, with a date and an amount, and check it on that date.
Who owns receivables — and why "finance" is the wrong answer
Ask most companies who owns overdue receivables and the answer is "finance". That answer is the problem. Ownership has to be at the level of the individual account, held by a named person, with an explicit next action and date. Anything vaguer and the account is nobody's until it is a crisis.
| Role | Owns | Accountable for |
|---|---|---|
| Credit controller | The credit decision and the limit | New accounts assessed before supply; limits reviewed on schedule |
| Collection officer | A defined book of accounts | Contact cadence met; every promise logged and chased on its date |
| Finance manager | The aging report and the process | Aged debtors accurate; escalation triggers actually fire |
| Sales / account manager | The commercial relationship | Resolving disputes they created; supporting escalation, not blocking it |
| CFO | The working-capital target | DSO and bad-debt provision against plan |
The four metrics that tell you whether it is working
Most receivables reporting stops at DSO, which is a problem, because DSO moves for reasons that have nothing to do with collections performance — a strong sales month mechanically inflates it. These four together are much harder to misread.
| Metric | Formula | What good looks like |
|---|---|---|
| DSO | (AR ÷ Credit sales) × Days in period | Within ~15 days of your average payment terms |
| Best Possible DSO | (Current AR ÷ Credit sales) × Days in period | The floor your terms allow — the gap to actual DSO is the opportunity |
| Average Days Delinquent | DSO − Best Possible DSO | The days you are losing to lateness alone. Trend it monthly. |
| Collection Effectiveness Index | (Opening AR + Credit sales − Closing AR) ÷ (Opening AR + Credit sales − Closing current AR) × 100 | Above 85% is healthy; best-in-class runs 90–98%; below 70% signals a process fault |
CEI is the one to argue for if you can only add a single metric. It isolates collections effectiveness from sales volume, which DSO cannot do.
There is a fifth metric that almost nobody reports and that I would put ahead of three of the above for diagnostic value: promise-kept rate. Of the payment commitments customers made this month, what percentage were honoured in full, on or before the promised date?
Reading an aging report properly: a worked example
The aged debtors report is the core artefact of AR management, and it is routinely read wrong — as a list sorted by size, worked from the top. Here is an illustrative AED book of 1.68 million, and what it actually says.
| Customer | Current | 1–30 | 31–60 | 61–90 | 90+ | Total |
|---|---|---|---|---|---|---|
| Gulf Metal Trading | 180,000 | 96,000 | — | — | — | 276,000 |
| Al Noor Contracting | 240,000 | 118,000 | 92,000 | 64,000 | 210,000 | 724,000 |
| Emirates Facilities | 62,000 | — | — | — | — | 62,000 |
| Skyline Interiors | — | — | — | 41,000 | — | 41,000 |
| Marina Retail Group | 310,000 | 145,000 | 38,000 | — | — | 493,000 |
| Desert Rose Foodstuff | — | — | — | — | 87,000 | 87,000 |
| Total | 792,000 | 359,000 | 130,000 | 105,000 | 297,000 | 1,683,000 |
Illustrative figures, constructed to show four distinct account patterns. Buckets are calendar days past due date.
Worked top-down by balance, you would start with Al Noor and Marina Retail. That would be a mistake on both counts. Read by pattern instead:
- Marina Retail Group (AED 493,000, nothing past 60 days) — the second-largest balance on the book and the healthiest account on it. It is large because they buy a lot, not because they pay slowly. No action beyond the normal cadence. Working it first would consume your best hours for no cash.
- Al Noor Contracting (AED 724,000, with 210,000 at 90+ and 240,000 still current) — this is the real finding, and it is not a collections failure. Someone is still supplying an account with AED 210,000 sitting past 90 days. The correct escalation is a credit hold and a conversation about the total exposure, not another follow-up call on the oldest invoice.
- Desert Rose Foodstuff (AED 87,000, entirely 90+, nothing current) — the account has stopped buying. That pattern is either an unresolved dispute or genuine distress, and it is the highest bad-debt risk on the page despite being the second-smallest balance. Treat it as an exception case, not a chase.
- Skyline Interiors (AED 41,000, a single invoice at 61–90) — one stranded invoice against an otherwise clean account is almost never unwillingness to pay. In my experience it is a missing LPO reference, a delivery note that was never signed, or an invoice that went to a person who has left. Ten minutes of reconciliation usually clears it, and it is the fastest cash on the page.
The 90+ column holds AED 297,000 — 17.6% of the entire book — concentrated in two customers with completely different causes and completely different remedies. That analysis is what an aging report is for. Sorting by balance hides all of it.
Common mistakes in accounts receivable management
These are the patterns that recur most often, roughly in order of how much cash they cost.
- Chasing invoices instead of customers. Three calls to one customer about three invoices is not three times the pressure — it is a customer who now believes your records are disorganised. Chase the account, with a reconciled statement, once.
- Treating the aging report as the output. Producing the report is not the work; it is the trigger list for the work. If the report is produced monthly and no action list comes out of it, the report is a cost.
- Not recording what was promised. The most expensive habit in collections. A promise that only exists in a call log or someone's memory cannot be checked on its date, cannot be escalated when broken, and cannot be counted.
- Escalating on age alone. A 95-day invoice from a customer who is buying and paying is a lower priority than a 40-day invoice from a customer who has gone quiet. Age is one input to risk, not the definition of it.
- Credit limits that exist on paper only. A limit that does not stop an order when it is breached is documentation, not a control. The check has to be at the point of order, not at the point of month-end review.
- Reconciling the statement of account only when the customer asks. In the UAE and wider GCC a monthly SOA is standard practice; when reconciliation is reactive, disputes surface at 90 days instead of at 15, and by then the disputed item is buried in a much larger balance.
- Measuring collectors on amount collected. Amount collected is mostly a function of which accounts they were given. Measure the things they control: contact cadence met, promises logged, promises chased on date, disputes escalated within SLA.
- Letting the invoice go out with a documentation gap. A missing purchase-order number or an unsigned delivery note does not cause a payment delay — it causes a payment stop, silently, and you usually find out at day 45 when you finally call.
Best practices that actually move the number
Ranked by impact per hour of effort to implement, based on what tends to change the number fastest:
Accounts receivable management checklist
- Assign every customer account to a named collector, and make the assignment visible to the customer-facing team.
- Log every payment commitment as a structured record — customer, invoice, amount, promised date — not as a note.
- Diarise the promised date and make the follow-up automatic. A promise not checked on its date teaches the customer that promises are optional.
- Set an escalation trigger by days past due and value, so escalation happens by rule rather than by someone remembering.
- Send a reconciled statement of account monthly, before the customer's payment run, not after it.
- Confirm the customer's payment cycle and cut-off date, and submit invoices to land before it. Missing a weekly cheque run by one day costs a full week.
- Capture the LPO / purchase-order reference at order stage and validate it before the invoice is issued.
- Check credit limits at the point of order entry, with a hard block, not at month-end review.
- Contact new customers before the first due date. The first invoice sets the tone for the whole relationship.
- Review the aging report by pattern — concentration, stalled accounts, single stranded invoices — not by balance.
- Report DSO alongside Best Possible DSO and CEI, so a strong sales month cannot be mistaken for a collections problem.
- Reconcile receipts to specific invoices on the day they land. Payments sitting on account corrupt the aging report.
What accounts receivable management looks like in the UAE
The fundamentals are universal; the friction is local. If you are running receivables in the UAE or the wider GCC, five things shape the process in ways that generic AR advice does not cover.
1. The payment run, not the due date, determines when you are paid
Many established UAE buyers pay on a fixed cycle — a weekly or fortnightly cheque and transfer run, with a submission cut-off several days before. An invoice that arrives one day after the cut-off does not become late by one day; it waits for the next cycle. Knowing each major customer's run date and cut-off is worth more than an extra reminder email, and it is a five-minute question that almost nobody asks.
2. LPO and SOA discipline is not optional
A local purchase order reference on the invoice, and a monthly statement of account that the customer's payables team has actually agreed, are the two documents that determine whether an invoice enters a payment run at all. Where an invoice is stuck with no dispute and no explanation, the cause is a documentation mismatch far more often than an unwillingness to pay.
3. Post-dated cheques changed meaning, but not usefulness
Since the Commercial Transactions Law reforms that took effect in January 2022, most bounced cheques are handled as civil rather than criminal matters. The reforms did not weaken the cheque as a collections instrument, though — a dishonoured cheque is now treated as an enforceable instrument, which lets the holder go to execution directly rather than starting a fresh claim. The practical shift is in how you use it: a PDC is now best understood as an enforcement shortcut, not as leverage.
4. VAT bad debt relief has conditions worth knowing before you need them
Under Article 64 of the UAE VAT legislation, a supplier can recover the VAT already accounted for on a bad debt — but only where the output tax was paid, the consideration has been written off in the supplier's accounts, more than six months have passed since the date of supply, and the customer has been notified of the written-off amount. That last condition catches people out: relief depends on evidence you took reasonable steps to notify, which means the notification has to be part of the write-off process, not an afterthought.
5. E-invoicing is about to remove one of the oldest excuses
The UAE's Peppol-based e-invoicing regime moves into its pilot and voluntary phase from July 2026, with the first mandatory wave — businesses with annual revenue of AED 50 million or more — required to appoint an accredited service provider by 30 October 2026 and to be live from 1 January 2027. For collections teams the significant consequence is that "we never received the invoice" stops being an available answer, and delivery timestamps become evidence. Teams that already track follow-ups against a documented delivery date will get more out of this than teams that do not.
When a spreadsheet stops being enough
Spreadsheets are a perfectly reasonable place to start, and plenty of businesses run receivables well from one. The point at which they stop working is fairly predictable — it is not a revenue threshold, it is a set of structural signals:
- More than one person needs to update the same view of the ledger on the same day.
- You cannot answer "what did this customer last commit to?" without opening an inbox.
- The aging report is rebuilt manually, and is therefore always describing the past.
- Nobody can produce collector-level or branch-level performance without an evening of work.
- A disputed balance cannot be evidenced with a timestamped history of what was said and when.
Each of those is a symptom of the same underlying thing: the process has outgrown a document and needs a system of record for the activity, separate from the accounting system's record of the transaction. That is the category collections management software occupies — it does not replace your ERP, it manages what happens between the invoice and the payment. If you are evaluating that shift, the accounts receivable software overview covers what the software layer is responsible for, and invoice aging software covers the aged debtors reporting specifically.
Bringing it together
Accounts receivable management is not a reporting exercise and it is not debt collection. It is the operational discipline of making sure every open invoice has a named owner, a recorded history, a known next action, and a date — and that the credit decision behind it was made deliberately in the first place.
The teams that do this well are rarely the ones chasing hardest. They are the ones where nothing falls through: promises get checked on their date, disputes surface at day 15 instead of day 90, credit limits actually stop orders, and the aging report is read for pattern rather than sorted by size. The cash improvement follows from the process, not from pressure.
If you take one action from this guide, make it the smallest one: start recording every payment commitment your customers make, with an amount and a date, and check each one on that date. It is a week of habit change, it costs nothing, and it will tell you within a month whether your problem is collections effectiveness or something further upstream.