Statement of Account Template UAE — the Format That Actually Gets Invoices Paid

Every UAE business sends invoices; the ones that get paid on time also send statements. In a market where a Dubai buyer and an Abu Dhabi supplier may be reconciling across two accounting systems, two currencies and two AP calendars, the statement is the only document that makes both ledgers say the same thing. A statement of account — the periodic summary of a customer’s ledger showing every invoice, credit note and payment with a running balance — is the document that turns “we’ll check and revert” into a settled balance, and its absence is why so many receivable disputes in Dubai start eleven months after the invoice nobody flagged.

This guide, updated July 2026, gives you the working statement of account template: the exact fields, the two layout choices, the UAE-specific VAT and TRN points, the sending cadence that collects, and the reconciliation routine on the payable side. If you first want the concept itself unpacked — what an SOA is and is not — start with our companion piece, what is a statement of account, then come back for the format.

The template — ten fields, none optional

A statement of account format that does its job carries all of the following, in roughly this order:

#	Field	What belongs there
1	Issuer block	Your legal name, UAE address, TRN, contact — matching your tax invoices
2	Customer block	Customer legal name, account/reference code, contact person
3	Statement date	The date the statement was generated
4	Period covered	e.g. 1–30 June 2026 — never leave the window implicit
5	Opening balance	Closing balance of the prior statement
6	Transaction lines	One dated line per invoice, credit note, adjustment — document number, description, debit/credit, running balance
7	Payments received	Date, reference and the invoices each payment was applied against
8	Closing balance	The number you expect the customer to agree
9	Ageing strip	Current / 1–30 / 31–60 / 61–90 / 90+ days
10	Payment + dispute block	UAE bank details and IBAN, payment terms, a named contact and a stated dispute window (7 days is common practice)

No UAE authority prescribes that layout — there is no statutory statement format the way there is a statutory tax invoice format — but every field above earns its place in a reconciliation, and a statement missing two or three of them generates the queries it was supposed to prevent.

Two details separate professional statements from exports nobody reads. First, payment application: showing which invoices each receipt was applied to kills the single most common reconciliation argument — “we paid that one”. Second, the ageing strip: a customer who sees their own 90+ column knows the next email is a formal one, and behaves accordingly. Benchmarks for what those buckets should look like sit in our AR ageing and DSO guide.

Open-item vs balance-forward — pick deliberately

Open-item statements list only unpaid and partially paid documents, each aged individually. This is the correct default for UAE B2B trading, where a single customer may hold six open invoices across two purchase orders: your customer’s AP team can tick off exactly which invoices to schedule, and nothing old hides inside a brought-forward number.

Balance-forward statements open with the prior balance and show only new activity. They suit high-volume, small-ticket accounts — think trade counters and recurring subscriptions — where per-document detail would run to pages. Their weakness is collections: a disputed invoice from March disappears into April’s opening balance, and by year-end nobody can say what the balance is made of.

Most accounting platforms generate both from the customer ledger, which is the real point: the statement should be a report from the books, never a hand-built Excel. A hand-typed SOA that disagrees with the ledger is worse than no statement, because you have now published the error.

Which layout suits which UAE account is usually obvious once the question is asked properly.

Account type	Layout	Why
B2B trade customer on 30–60 day terms	Open-item	The AP team needs invoice-level instructions to schedule payment
Government or large-corporate customer	Open-item	Payment runs match specific invoice and PO numbers
Contracting customer with retentions	Open-item, retentions shown separately	Retention balances age differently from trade debt
High-volume, small-ticket account	Balance-forward	Per-document detail would run to pages
Recurring subscription or service retainer	Balance-forward	Predictable, low-dispute activity
Any account in dispute or heading to collection	Open-item, always	Old items must stay visible, not vanish into an opening figure

The retention row is the one specific to UAE construction and fit-out work, where a retained percentage sits unpaid for months after practical completion. Folding it into the ordinary ageing makes the whole strip misleading; showing it as its own line keeps both numbers honest.

The UAE specifics — VAT, TRN and what an SOA is not

Three points that matter under the UAE’s tax framework:

1. An SOA is not a tax invoice. Article 59 of the UAE VAT Executive Regulation (Cabinet Decision No. 52 of 2017, as amended) prescribes the contents of a tax invoice — and input VAT is claimed against tax invoices, never statements. The statement shows the gross (VAT-inclusive) value of each underlying document; it charges nothing itself. Issue every invoice through a compliant format first — the UAE tax invoice generator covers the required fields — and let the statement summarise them.
2. Show your TRN in the header for identification, and your customer’s reference. As e-invoicing arrives in the UAE, statements become the human-readable reconciliation layer on top of structured invoices, not a substitute for them. A TRN in a statement header also lets the recipient verify you on the FTA’s free channels before paying, which is a courtesy that shortens onboarding with cautious UAE buyers.
3. Credit notes belong on the statement with their own document numbers, dated when issued. Netting them silently into invoice lines is how balances become unexplainable — the issuance rules are covered in our credit note guides.

7 days

Common dispute window stated on UAE B2B statements — after which the balance is treated as accepted

The cadence that collects

The template earns nothing until it ships on a rhythm. The routine we run for clients:

1. Close the month — all invoices raised, receipts applied, credits posted. An SOA from an unclosed ledger is a rumour.
2. Generate statements in the first week of the new month for every account with a balance — not just the late ones. Statements to current accounts prevent lateness; statements to late accounts cure it. Most UAE AP departments run payment approvals in the first half of the month, so a statement that lands in week one is read inside that cycle rather than after it.
3. State the dispute window (“please raise discrepancies within 7 days”) so silence starts to mean acceptance.
4. Escalate on the ageing — 30 days late gets a reminder referencing the statement; 60 gets a call; 90 gets a formal demand attaching the statement history. Three statements showing the same unpaid invoice are quietly powerful in front of a judge or arbitrator.
5. Year-end confirmations — auditors will circularise balances anyway; accounts that received monthly statements confirm in days, not weeks.

“

Customers do not pay invoices. They pay suppliers whose ledgers are visibly in order — and the monthly statement is how a ledger becomes visible.

Reading the ageing strip — what each bucket is telling you

The ageing strip at the foot of a UAE statement is the part customers read and suppliers underuse. Each bucket carries a different meaning and a different action, and treating them all as “overdue” wastes the information.

Bucket	What it usually means	The right action
Current	Invoiced, not yet due	Nothing — but confirm the invoice was received and matched to a PO
1–30 days	Slipped past terms	A statement and a short reminder naming the invoice numbers
31–60 days	A process problem at the customer, or a query nobody raised	A call to the named AP contact; ask what is blocking the specific line
61–90 days	Either a dispute or a cash problem	Written escalation; get the undisputed portion released
90+ days	Recovery, not collections	Formal demand attaching the statement history; consider a notarised notice

Two habits change the numbers. The first is sending statements to current accounts, not only late ones — a customer who reconciles every month is a customer who queries in week two rather than month eleven. The second is naming a person, not a department: an AP clerk who knows who to email answers, and one who has to guess does not.

For a UAE business, the ageing strip also feeds a real accounting judgement. Balances sitting in the 90+ column are the population an expected credit loss assessment starts from, and a provision that is never revisited is either overstating profit or understating it. The benchmarks worth measuring against sit in the AR ageing and DSO guide.

VAT, credit notes and what the statement must never do

Three tax points sit underneath every UAE statement of account, and getting them wrong turns a collections document into a tax problem.

Point	The rule	What it means for the SOA
Input VAT recovery	Claimed against a compliant tax invoice	A statement can never support a claim; it is not a tax invoice
Tax invoice contents	Article 59, VAT Executive Regulation, Cabinet Decision No. 52 of 2017 as amended	Your TRN appears on the invoice; showing it on the statement is identification, not compliance
VAT on the statement	The statement reports documents that already exist	Show gross, VAT-inclusive amounts; charge no VAT of its own
Credit notes	Issued as their own documents	List each with its number and date, pointing at the invoice it corrects
Rounding and currency	Statement currency must match the ledger	Mixed-currency accounts need one statement per currency, never a blended total

The credit note row causes the most reconciliation pain in UAE B2B ledgers. Netting a credit silently into an invoice line makes the two ledgers permanently irreconcilable: your customer’s AP shows an invoice of AED 12,600 and a credit of AED 1,575, while your statement shows a single line of AED 11,025 that matches nothing on their side. Show both documents, always, and point the credit at the invoice it corrects.

The mixed-currency row matters for any Dubai trading business invoicing in dollars and dirhams. A statement that adds AED and USD lines into one running balance is not a statement, it is an error with a total — and it is the fastest way to lose a customer’s confidence in every other number you send them.

The other direction — reconciling supplier statements

The same document arrives inbound, and it is routinely wasted. Every supplier statement of account should be matched line-by-line against your AP ledger monthly: it catches invoices that never reached you (and whose input VAT you therefore never claimed), duplicate postings, payments the supplier has not applied, and credits you were owed but never recorded. Ten minutes per major supplier per month, and year-end AP surprises stop existing. This reconciliation habit is half of what a structured payables function does — the other half, payment scheduling and approval controls, is territory covered by our receivables and payables management service.

Here is what that reconciliation looks like when it is written down rather than done in someone’s head. A Dubai supplier’s statement for June 2026 shows AED 86,400; the AP ledger shows AED 70,300.

Reconciling item	AED
Balance per supplier statement, 30-06-2026	86,400
Less: payment TT-20614 sent 30-06-2026, not yet applied by the supplier	(6,300)
Less: agreed rebate, debit note DN-07 raised by us and accepted, not yet credited	(2,100)
Adjusted supplier balance	78,000
Balance per our AP ledger, 30-06-2026	70,300
Add: tax invoice SUP-4412 dated 28-06-2026, never received by us	9,450
Less: tax invoice SUP-4370 posted twice in error	(1,750)
Adjusted AP ledger balance	78,000
Difference	0

Four reconciling items, four different actions. The payment in transit and the agreed rebate are timing — they clear themselves next month, and the only job is to confirm they do. The missing invoice and the duplicate posting are errors, and both cost real money.

The missing invoice is the expensive one. AED 9,450 gross at the 5% UAE VAT rate carries AED 450 of input tax that was never claimed because the tax invoice never arrived — and input VAT is recovered against the tax invoice, so no amount of statement evidence substitutes for chasing the document itself. The duplicate posting works the other way: AED 1,750 of cost and creditor recorded twice, overstating both the expense and the payable until someone catches it.

Run this on your ten largest suppliers each month and the pattern that emerges is usually consistent — one supplier with a persistent invoice-delivery problem, one with an application problem, and eight that reconcile cleanly. Fix the first two at the source and the exercise shrinks. The method itself is set out step by step in the supplier reconciliation process guide.

A worked example — what the lines actually look like

Abstract field lists are easy to nod at and hard to copy, so here is the transaction body of an open-item statement of account template filled with plausible numbers. Assume a statement dated 5 July 2026 covering June, for a customer on 30-day terms:

Date	Document	Reference	Debit (AED)	Credit (AED)	Balance (AED)
01-06-2026	Opening balance	—	—	—	18,900.00
04-06-2026	Tax invoice	INV-2041 / PO-7712	12,600.00	—	31,500.00
11-06-2026	Credit note	CN-0188 (against INV-2032)	—	1,575.00	29,925.00
18-06-2026	Payment received	TT ref 99823 → INV-2029, INV-2032	—	18,900.00	11,025.00
25-06-2026	Tax invoice	INV-2055 / PO-7738	8,400.00	—	19,425.00
30-06-2026	Closing balance	—	—	—	19,425.00

Underneath sits the ageing strip — in this example: current AED 8,400, 1–30 days AED 11,025, nothing older — and the payment block with the UAE bank details, the IBAN and a named contact for queries. Three things to imitate from the example: every debit is a numbered tax document, the payment line names the invoices it settled, and the credit note points at the invoice it corrects. A customer’s AP clerk can process this statement without a single clarifying email, which is the entire test of the format.

The statement as evidence — and when it escalates

The escalation ladder, and where the statement sits on each rung:

Rung	Document sent	What the statement contributes
1. Routine	Monthly statement of account	Establishes the balance as a shared fact
2. Reminder	Statement plus a written reminder naming the aged invoices	Shows the same balance unchanged
3. Call	Statement re-sent to a named contact	Forces a specific answer on a specific line
4. Balance confirmation	Statement returned signed or stamped by the customer	Converts a supplier record into a joint admission
5. Formal demand	Statement history plus the underlying UAE tax invoices	Demonstrates the debt was asserted consistently
6. Legal notice	Notarised notice, statements annexed	The evidence pack a UAE court or arbitrator reads

Because the SOA is a routine business record rather than a demand, it accumulates quiet evidential weight: a customer who received twelve consecutive statements showing the same balance and never disputed it has a hard story to tell later. UAE collection practice builds on exactly that — the escalation ladder runs statement → reminder referencing the aged lines → call → signed balance confirmation → formal demand, which for serious balances typically means a notarised legal notice served through the channels our notary public in Dubai guide explains, before any case is filed. A statement history plus a signed confirmation shortens that road considerably; a first-ever statement produced mid-dispute barely helps at all.

The inbound mirror has its own method note: reconciling a supplier’s statement against your purchase ledger has a defined sequence — capture, match, investigate, confirm — which we walk through line by line in the supplier reconciliation process guide. Run it monthly for your top vendors and the year-end accrual scramble disappears.

Year-end: from statement to balance confirmation

The statement earns its last piece of value at year end, when an auditor circularises balances. A UAE company that has been sending monthly statements gets confirmations back in days; one that has not spends the audit chasing customers who have never seen a summary of their own account.

Year-end step	What the statement does	What is still needed
Balance confirmation request	Supplies the balance and the supporting lines	An independent confirmation direct to the auditor
Unreconciled differences	Identifies timing versus error before fieldwork	Adjusting entries posted in the correct period
Expected credit loss review	Provides the ageing population	A documented provision judgement
Cut-off testing	Shows the last invoice and receipt of the period	Delivery evidence supporting the cut-off
Related-party balances	Isolates intercompany accounts	Agreement to the counterparty’s ledger

Two of those rows carry a UAE tax consequence as well as an audit one. Cut-off decides which period a supply falls in for VAT, and a receivable written off has its own conditions before any output tax adjustment can be made. Both are far easier to evidence from a ledger that has produced a statement every month than from one reconstructed in January.

The related-party row is worth its own note for group structures. Intercompany balances that never agree between two UAE entities in the same ownership are a recurring audit finding, and the fix is the same discipline applied internally: each entity issues the other a monthly statement, and someone reconciles them. Groups that skip this because “it is all our money” end up explaining a difference to an auditor and, if the entities sit in different tax positions, to the FTA as well.

What to do when the ledger has never been reconciled

Where the receivables position has drifted for a year or more, sending a statement is the wrong first move — an inaccurate statement published to a customer is worse than no statement, because you have now put your own error on the record.

The sequence that works is bounded and finite. Agree a cut-off date and freeze it. Rebuild the customer ledger from tax invoices, credit notes and bank receipts rather than from the previous summary. Apply every receipt to the specific invoices it settled, using the remittance advice where one exists and the customer’s own reference where it does not. Write off what is genuinely uncollectable with a documented decision rather than leaving it aging forever. Only then issue the first statement — and issue it to every account with a balance, current ones included, so the new cadence starts clean.

Expect the rebuild to surface three categories: receipts that were never applied, credit notes issued but never posted, and invoices raised twice. All three inflate or deflate a UAE company’s reported receivables, and therefore its reported profit — which is why the exercise is an accounting correction rather than a collections chore. Where the books behind it have also fallen behind, the wider clean-up is covered in our guide to catch-up bookkeeping.

Common template mistakes

• Statements built in Excel, separately from the ledger — the moment they diverge, every future statement is suspect.
• No payment application detail — receipts shown as lump sums, so old invoices look unpaid and arguments start.
• Missing credit notes — the customer’s copy shows a credit yours does not, and the balances never agree.
• No ageing strip — the statement informs but applies no pressure.
• Sporadic sending — a statement that only appears when you are angry reads as a threat, not a routine.
• No dispute window or contact — queries route to whoever answers the phone, and nothing gets resolved on the record.

Where Velmont Crest fits in

Statements are a by-product of clean books — which is exactly why ours ship on time, whether the customer ledger sits in Dubai, Sharjah or Abu Dhabi. Under our accounts receivable and payable management service, the monthly close produces customer statements automatically, the ageing drives a written escalation routine, and supplier statements get reconciled against the purchase ledger before payments run. Clients see their receivables position in a monthly pack instead of discovering it at year-end.

If your balances are already tangled — customers disputing numbers, supplier accounts that have never been reconciled — the cleanup is a defined project with a defined end, and it usually pays for itself in unclaimed input VAT and receipts nobody had applied. UAE receivables rarely go bad quietly; they go bad while the paperwork says everything is fine. Request a quote through the contact page and we will respond within one UAE business day.