Accounts receivable ageing: a UAE small-business workflow
Build and reconcile a receivables ageing schedule, prioritise overdue invoices, resolve disputes and keep collection forecasts separate from recorded receipts.
An accounts receivable ageing report turns “customers owe us money” into a collection plan. It identifies which invoices are outstanding, how late they are, why payment is delayed and who will resolve the next action. The useful result is not a coloured chart; it is a supported list of balances and commitments that can be checked against the books.
For a UAE small business selling on credit, start with the agreed payment terms and an explicit reporting date. The buckets and escalation steps below are suggested operating choices, not statutory collection deadlines. Apply the customer’s contract and obtain appropriate advice before taking legal action or changing a formal tax position.
Age the unpaid balance from a defined date
Choose the reporting date and use the invoice’s contractual due date to measure days overdue. An invoice not yet due belongs in a current bucket. Using invoice date instead may make a customer with sixty-day terms look late after thirty days, even when the customer is still within the agreed terms.
Build a line-level schedule with customer, invoice reference, invoice date, due date, original amount, credits, receipts applied and balance outstanding. Add currency, dispute status, collection owner and next action. Keep the original due date visible if terms are later changed, with evidence of the approved change.
Before ageing, apply known receipts and credit notes to the appropriate invoices. Unallocated cash can make an already-paid invoice appear overdue. A negative customer balance might be an advance, a credit or a misallocation; investigate it instead of netting it silently against a different customer’s debt.
Worked example: one total, four different actions
Consider an illustrative AED receivables schedule as at 30 September 2026. Ignore foreign-currency translation, VAT adjustments and impairment measurement. The four open invoice balances are:
| Customer reference | Due date | Outstanding AED | Position at 30 September |
|---|---|---|---|
| A | 15 October 2026 | 10,000 | Not yet due |
| B | 20 September 2026 | 15,000 | 10 days overdue |
| C | 15 August 2026 | 20,000 | 46 days overdue |
| D | 30 June 2026 | 12,000 | 92 days overdue |
Total receivables are AED 57,000. Using buckets of current, 1–30, 31–60, 61–90 and over 90 days produces AED 10,000, AED 15,000, AED 20,000, zero and AED 12,000 respectively. The AED 47,000 overdue amount is meaningful, but its components need different decisions.
A may only need confirmation that the invoice reached the correct contact. B may need a reminder and a payment date. C may require resolution of a disputed delivery. D needs a focused assessment of recovery prospects and the next authorised step. Sending the same automated wording to all four would ignore the information the report was created to reveal.
Suppose B’s original invoice was AED 20,000 and an AED 5,000 receipt was already applied. Follow up the remaining AED 15,000, and include a statement showing the receipt. Asking for AED 20,000 would damage the collection conversation and indicate that the report was not reconciled before use.
Reconcile the schedule before contacting customers
Tie the invoice-level total to the receivables control account for the same date. A simple roll-forward can reveal missing records. For illustration, opening receivables of AED 55,000 plus AED 40,000 of invoices, less AED 30,000 receipts and AED 8,000 credit notes, gives the same AED 57,000 closing balance.
Investigate differences between the roll-forward, ledger and ageing total. Possible causes include a receipt posted directly to revenue, a credit note not linked to an invoice, duplicate sales or a customer balance entered through a journal outside the normal schedule. Record the correction and its reference rather than forcing the report total to agree with an unexplained plug.
Use the bank reconciliation guide to support the cash side. A receipt appearing in the bank still needs an explanation of which customer or invoice it settles. When one transfer pays several invoices, retain the remittance breakdown and confirm the allocation with the customer where necessary.
Separate collection problems from disputes
Give each overdue invoice a reason code that leads to a useful action. Examples include invoice not received, missing purchase-order reference, delivery dispute, agreed payment plan, promised payment missed and suspected financial difficulty. A reason such as “customer slow” does not tell the team what to do next.
For a disputed delivery, attach the relevant correspondence and ask the operational owner to identify the specific unresolved item. If the dispute concerns AED 2,000 of a larger invoice, establish whether the remaining balance is accepted and when it can be paid. Do not promise a credit note or waive an amount without the required approval.
Record promised dates as commitments, not receipts. When a customer promises AED 6,000 next week, the receivable remains outstanding until the payment is properly recorded. A separate expected-cash column can support planning without overwriting the actual accounting balance.
Use a collection record that another person can continue
A useful follow-up entry states the date, contact, issue discussed, commitment obtained, owner and next review date. Keep the invoice and supporting documents readily available. This avoids restarting the conversation when a colleague is absent or a customer asks for a copy of evidence already supplied.
Choose an escalation policy suited to the business and apply it consistently. For example, a missed promise might require a call from the account manager before further credit is approved. Treat that as an internal decision, not a universal UAE legal rule. Consider the commercial relationship, contract terms and any regulated activity before changing service or credit arrangements.
Review large or concentrated balances separately. One customer owing half the ledger can matter more than many small invoices reaching the same age bucket. Include both balance size and age when prioritising work.
Keep ageing separate from accounting and tax conclusions
A ninety-day label does not automatically mean an invoice should be written off, that a fixed percentage provision is correct or that VAT can be reduced. Where IFRS 9 applies, the IFRS Foundation’s impairment guidance explains that expected credit losses involve more than historical ageing alone. Have the preparer assess the applicable reporting requirements and supporting facts.
Likewise, any tax treatment requires its own conditions and records. Keep the original invoice, collection history, dispute evidence, approvals and accounting decision. The record-keeping guide helps preserve that trail; the month-end close checklist places the review within the wider reporting process.
The next report should show what changed: receipts obtained, allocations corrected, disputes closed, promises missed and risks escalated. That movement is the measure of a useful ageing process. A ledger can remain the same size while becoming much more understandable and actionable.
Source principles checked on 26 October 2026. Customers, amounts, buckets and collection steps are illustrative.