UAE Receivables: Built for Cheques, Paid Instantly

The Two Days Nobody Budgets For

In most UAE finance teams there is a person whose first two days of every month disappear into the same task: working out which invoices the month’s receipts actually paid.

The bank statement shows a transfer. The reference field says the customer’s name, or a number that matches nothing, or nothing at all. The amount does not match any single invoice because the customer paid four of them together and deducted a credit note. So somebody emails the customer’s accounts department and waits.

Meanwhile the ageing report is wrong, because unapplied cash is sitting against the customer rather than the invoices. The credit controller chases invoices that were paid three weeks ago. A customer who genuinely has not paid looks identical to one who has.

This is not a small-business problem or a careless-team problem. It is what happens when a receivables process designed around cheques and manual bank transfers meets a volume of transactions it was never built for.

What makes it worth revisiting now is that both ends of the cycle are changing. The UAE’s payment infrastructure has moved substantially, and e-invoicing is about to make your outbound invoices structured data. This article is about the half in the middle — getting paid, and knowing what you were paid for.

What Has Changed on the Rails

Worth being specific, because the scale of the change is easy to miss from inside a finance department.

Aani, the UAE’s national instant payments platform, is operated by Al Etihad Payments, a subsidiary of the Central Bank of the UAE. As reported by Al Etihad Payments in April 2026:

• More than 12.5 million registered users
• 74 licensed financial institutions connected, with integration at 85% of banks
• Account-to-account transactions completing in no more than three seconds on average
• Transfers up sixfold year on year, with around 25,000 daily transfers made using a mobile number alone
• Approximately 774,000 merchants using Aani as a primary payment solution

Current capabilities include QR code payments, Request to Pay, transfers by mobile number or Emirates ID, and managing accounts across multiple banks in one application.

That is a genuine transformation of how money moves in the UAE — and it has happened largely around consumer and merchant payments.

What Has Not Changed in B2B

Here is the part most commentary skips.

Al Etihad Payments lists electronic direct debit, e-cheques and business-to-business payments among features expected to launch later. They are on the roadmap, not in production.

So the UAE B2B settlement picture today is still largely what it was: bank transfers initiated manually by the customer’s finance team, cheques including post-dated ones, and remittance advice that arrives by email when somebody remembers to send it.

Two things follow, and both are actionable now.

First, the bottleneck is not payment speed — it is payment information. Even when a customer pays instantly, if the reference does not identify the invoices, your team still does the matching by hand. Faster money with the same missing data produces the same two days of work. The fix is not waiting for better rails; it is capturing better references on the rails you have.

Second, when B2B capabilities do arrive, the businesses that benefit will be the ones whose receivables data is already clean. Electronic direct debit is only useful if you have accurate customer banking records, agreed terms and reliable invoice data. Request to Pay is only useful if your invoices are correct and your customer records are right. The preparation work is the same work that fixes the problem you have today, which makes it unusually easy to justify.

The Three Places Cash Goes Missing

1. Unidentifiable payments. A receipt arrives with no usable reference. Until somebody identifies it, it sits as unapplied cash — in your bank, not against the invoice. Your ageing is wrong and your collections team is working from fiction.
2. Part payments and deductions. The customer pays most of an invoice and withholds a disputed amount, or nets off a credit note, or pays four invoices in one transfer. Each requires a judgement, and judgements do not scale. This is where the hours go in a business with volume.
3. Disputes that were never recorded. A customer is not paying because of a delivery issue raised with the sales team two months ago. Nobody wrote it down in a place finance can see. The credit controller chases, the customer is annoyed, and the invoice ages for reasons that have nothing to do with their ability to pay.

The pattern. None of these is a payments problem. All three are information problems — missing references, unrecorded decisions, invisible disputes. That is why faster rails alone will not fix them, and why the fix sits in your accounting system rather than your bank.

The Post-Dated Cheque Question

Any honest article about UAE receivables has to deal with this, because post-dated cheques remain a normal part of B2B trade here in a way they are not in most markets.

The operational reality. A PDC is a commitment to pay on a future date, which you hold physically, must deposit on or near that date, and which may or may not clear. Between receipt and clearance it is neither a receivable you can treat as settled nor one you should chase in the normal way. Most UAE businesses track them in a spreadsheet maintained by one person — with the familiar consequences when that person is on leave.

The honest software position. Zoho Books does not provide a dedicated post-dated cheque module. PDC handling is a long-standing request in Zoho’s own community and feature-request forums, and businesses that need it today use workarounds — a combination of custom fields, scheduled records and disciplined process — or a separate register. If PDCs are material to your business, treat this as a requirement to design for, not a feature to switch on, and confirm the current product position before you plan around it.

What a workable approach looks like. The cheque is recorded against the invoice with its due date, so the invoice is visibly committed rather than simply overdue. The deposit date is a scheduled action with an owner. A bounced cheque has a defined process that returns the invoice to active collections immediately rather than quietly. And the PDC position is visible in your cash forecast, because a drawer full of cheques is forecastable cash that most forecasts ignore.

Where volume justifies it, a purpose-built register in Zoho Creator alongside Zoho Books is a reasonable answer. For most businesses, disciplined use of custom fields is enough.

What Zoho Books Can Actually Do

The problem: payments arrive without usable information and matching is manual. The capability: Zoho Books as the receivables system of record. The outcome: most receipts match themselves, and your team works the exceptions.

Make it easy to pay you, with the reference attached. Zoho Books supports multiple online payment options and the sending of online payment links. A customer paying through a link pays a specific invoice, which means the payment arrives already identified. This single change removes more matching work than anything else on this list, and it costs nothing to try on your highest-volume customers.

Automate the chasing. Zoho Books can automate invoices and reminders, and its automation can trigger emails and notifications on defined conditions. A reminder sequence that runs reliably before and after the due date recovers invoices that were simply forgotten — which, in most UAE businesses, is a meaningful share of overdue balances. The discipline matters more than the wording.

Match in the banking module. Zoho Books presents bank transactions for matching and categorisation, with reconciliation built on that. The quality of automatic matching depends entirely on the quality of the data arriving, which is the subject of the next section.

Give customers a portal. Zoho Books provides customer portals for communication, which gives customers a place to see their outstanding position rather than emailing to ask for a statement. Confirm the current payment capability within the portal for your plan and region before relying on it.

Report ageing properly, per entity. A group running several licences needs ageing by entity, not blended, because collections decisions are made per legal entity.

A note on scope. This is a configuration and process engagement, not a product purchase. The capability is largely there; what is usually missing is the design, the data and the discipline.

The Data That Makes Matching Work

Automatic matching is not magic. It depends on four things, and most businesses are missing at least two.

• A payment reference convention your customers actually use. Decide the format, print it prominently on the invoice, and tell your customers’ accounts departments — not just your buyer contact. This is a relationship task as much as a system one, and it works: finance teams generally want to pay correctly.
• Customer records that match the bank. The paying entity’s name as it appears on a transfer frequently differs from the name in your ledger. Recording the paying entity name against the customer lets matching succeed on receipts that would otherwise fail.
• Clean, current invoice data. Correct amounts, correct terms, correct entity. An invoice the customer disputes on a detail is an invoice that ages for a reason your system cannot see.
• Disputes recorded where finance can see them. If sales agrees a credit, it has to reach the ledger. A dispute held in an inbox is an unexplained ageing balance.

The exercise worth doing this week. Take last month’s receipts and sort them: matched automatically, matched manually in under a minute, required an email to the customer. The third category, multiplied by twelve, is your annual cost — and it is usually the number that gets the project approved.

Measuring It Properly

Four measures, and most UAE finance teams track at most one.

• DSO, calculated consistently and reported monthly. The level matters less than the trend and the definition staying fixed.
• Unapplied cash — the total sitting against customers rather than invoices, and how long it has been there. This is the purest measure of the matching problem and almost nobody reports it.
• Auto-match rate — the share of receipts applied without human intervention. This is the number your project should move.
• Overdue by reason, separating cannot-pay from will-not-pay from disputed from never-chased. Each needs a different response, and a single ageing report hides all four.

Zoho Analytics can carry these as a standing collections view alongside the management pack. The point is that collections performance becomes visible rather than anecdotal.

Dubai and UAE Considerations

Multi-entity groups. Many Dubai businesses invoice from several licences, sometimes across mainland and free zone. Ageing, credit limits and collections ownership belong at entity level. A blended group ageing report is not something a credit controller can act on.

Cheques are not disappearing this year. Design for a mixed reality — instant transfers, conventional transfers and cheques including PDCs — rather than for the process you would prefer.

Payment terms in practice. UAE B2B terms are frequently longer in practice than on the invoice, particularly with large buyers. Your system should reflect agreed terms accurately so that genuine overdue balances stand out from normal behaviour.

E-invoicing changes the invoice, not the collection. Under the UAE mandate your outbound invoices become structured and validated. That improves invoice accuracy, which helps — but it does not make the customer’s payment carry a reference. Treat receivables as a separate project running alongside e-invoicing readiness, using the same customer master data work.

Arabic. Where your customers’ finance teams work in Arabic, reminder and statement templates should be too. Zoho’s applications support Arabic; confirm template handling for your configuration.

What This Will Not Fix

• It will not make customers pay faster if they have decided not to. Automation removes the invoices that were forgotten and the disputes that were invisible. A customer with a cash problem is a commercial conversation, and no configuration substitutes for it.
• There is no PDC module. Post-dated cheque handling in Zoho Books is a design exercise using custom fields, process and possibly a separate register — not a feature. Be clear-eyed about that if PDCs are material to you.
• Automatic matching has a ceiling. Part payments, deductions and consolidated payments across many invoices will always need judgement. A realistic target is to remove the routine and leave your team the exceptions, not to reach zero manual work.
• Aani’s B2B capabilities are not available yet. Electronic direct debit, e-cheques and B2B payments are listed as forthcoming by Al Etihad Payments. Plan for the rails you have, and prepare the data so you benefit when the rest arrives.
• Clean data is a prerequisite, not an outcome. If customer records are inaccurate, matching will not improve. That remediation is the project’s first phase, not a by-product.

A Realistic Implementation Sequence

1. Measure the baseline — one month of receipts sorted by how they were matched, plus current unapplied cash. This is your business case.
2. Agree the payment reference convention, and how you will communicate it to customers’ accounts departments.
3. Remediate customer records, including paying-entity names where they differ from the ledger name.
4. Turn on online payment options and payment links for your highest-volume customers first.
5. Design the reminder sequence — timing, tone, escalation and who owns each step.
6. Configure bank matching and work the exceptions deliberately for a month to find the patterns.
7. Design the PDC approach if cheques are material, and give it an owner.
8. Record disputes where finance can see them, with a route from sales into the ledger.
9. Build the collections view — DSO, unapplied cash, auto-match rate, overdue by reason.
10. Review after one quarter against the baseline you measured in step one.

Best Practices

1. Measure before you configure. The baseline is what justifies the work and proves it afterwards.
2. Make paying you easy. Payment links attach the reference automatically.
3. Tell your customers’ accounts teams the reference convention, not just your buyer.
4. Record the paying entity name where it differs from the customer name.
5. Automate reminders before the due date, not only after.
6. Report unapplied cash. It is the clearest signal of a matching problem.
7. Track auto-match rate as the project’s headline metric.
8. Separate overdue by reason. One ageing report hides four different problems.
9. Age by entity, not across the group.
10. Give PDCs an owner and a forecast line.
11. Create a route for disputes to reach the ledger.

Common Mistakes

• Treating slow collections as a sales problem. Usually it is an information problem.
• Configuring reminders on dirty customer data. You will chase the wrong people politely and at scale.
• Not measuring the baseline. You cannot prove the improvement, so the project is judged on feeling.
• Leaving unapplied cash unreported. It is where the hours hide.
• One blended ageing report across several entities.
• Expecting automation to fix disputes. It surfaces them; people resolve them.
• PDCs in one person’s spreadsheet.
• Assuming instant rails solve matching. Faster money with no reference is the same work.
• Chasing every overdue invoice identically, regardless of reason or customer value.
• Stopping after go-live. The exception patterns in month one are the instructions for month two.

An Illustrative Scenario: A Dubai Trading Business

A composite illustration built from patterns common in the UAE market. It is not an account of a specific named client.

Consider a Dubai trading business running Zoho Books across two mainland entities, invoicing several hundred B2B customers monthly, with a finance team of five.

Before

Receipts arrived as bank transfers with inconsistent references and a steady flow of cheques, some post-dated. One accountant spent the first two working days of each month applying cash. Post-dated cheques lived in a shared workbook. The ageing report was produced monthly and treated internally as approximately true — the credit controller checked with the accountant before chasing anything significant, because the report was known to include invoices already paid.

What the Baseline Showed

Before changing anything, the team sorted one month of receipts. Roughly half matched without intervention. A further group matched manually within a minute. The remainder — concentrated among the largest customers, who paid multiple invoices together with deductions — required an email and a wait. Unapplied cash at month end was the number that surprised the finance director, because nobody had ever reported it.

What Was Done

The payment reference convention was agreed and, importantly, sent to customers’ accounts departments rather than only to buyers. Customer records were remediated with paying-entity names where they differed. Online payment links were enabled, starting with the highest-volume customers. The reminder sequence was redesigned to start before the due date. PDCs moved out of the workbook into a register with a named owner and a deposit schedule, and into the cash forecast.

After Two Quarters

The auto-match rate improved materially, concentrated in mid-sized customers who had simply never been told what reference to use. The two days at month end became roughly half a day, with the remaining time spent on the large consolidated payments that genuinely need judgement — which the finance director accepted as the right place for a person.

The more valuable outcome was that the ageing report became trusted. The credit controller stopped verifying it before acting, which changed how quickly collections conversations happened. And separating overdue by reason revealed that a meaningful portion of the oldest balances were disputes nobody in finance had known about.

Industry Considerations

• Trading and distribution. High invoice volume, a long tail of customers, consolidated payments and deductions — the largest matching burden of any sector, and where this work pays back fastest. See trading and distribution solutions.
• Logistics and freight. Many small invoices per customer per month, frequently settled together, with disputes over accessorial charges. Dispute visibility matters more here than almost anywhere. See logistics solutions.
• Manufacturing. Fewer, larger customers with longer terms and higher PDC usage. Forecasting the cheque position is the priority. See manufacturing solutions.
• Healthcare. Mixed payer arrangements including insurers produce part payments and deductions as the norm rather than the exception. See healthcare solutions.
• E-commerce and retail with wholesale arms. Consumer payments are already clean; the B2B wholesale side carries the problem. See e-commerce solutions.

Collection Methods Compared

The useful read: the column that matters is the first one. Payment speed is largely solved in the UAE. Matching effort is not, and it is the one you control.

Gateways, Currencies and Hosting in Zoho Books

Card and link payments

Telr and PayTabs are among the payment gateways listed for Zoho Books in the UAE, so customers can pay an invoice through a link. Telr also publishes apps for Zoho Books, Zoho Inventory, Zoho Billing, Zoho Checkout, Zoho Invoice and Zoho Commerce, but not for Zoho CRM, so CRM-led payment flows need to pass through one of those apps.

Foreign currency receivables

Zoho Books invoices in the customer’s currency, reports in AED and posts exchange differences on payment. The Kuwaiti and Bahraini dinars use three decimal places, so test rounding on those invoices before you automate matching.

Where receivables data sits

Zoho’s UAE region has run since January 2026, with the primary data centre in Dubai and the secondary in Abu Dhabi. Zoho places each account by the country chosen at sign-up, so accounts created earlier, or under another country, may still be hosted outside the UAE. See our guide to Zoho UAE data centres.