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. 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:

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: 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 — Zoho Books, Xero, QuickBooks, Odoo — 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.

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. The FTA 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.
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.

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.
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.

The other direction — reconciling supplier statements

The same document arrives inbound, and most UAE SMEs waste it. 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.

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:

Underneath sits the ageing strip — in this example: current AED 8,400, 1–30 days AED 11,025, nothing older — and the payment block. 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

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.

Common template mistakes we clean up

• 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. 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. Request a quote through the contact page and we will respond within one UAE business day.