What Is a Statement of Account? SOA Meaning for UAE SMEs

A statement of account is one of the most-used and least-understood documents in day-to-day UAE business. Every SME sends them, receives them, and files them — yet ask five finance teams to explain exactly how a statement of account differs from an invoice and you will get five slightly different answers. The confusion matters, because the SOA is the document that decides whether your receivables get collected cleanly, whether your supplier payments are correct, and whether your month-end close reconciles without a scramble.

This guide sets out what a statement of account actually is, what it contains, the types and formats you will meet, how it differs from an invoice and a tax invoice, and how SMEs use it for reconciliation and collections. If you need a ready structure to work from, our statement of account template for UAE businesses sets out the layout and fields to include — useful whether you are building a statement of account template in Excel or checking that the SOA form your accounting software already produces carries everything it should.

What a statement of account actually is

A statement of account is a periodic summary document that one party sends another to show all the transactions between them over a defined period. A seller sends it to a customer to confirm what that customer owes. A supplier sends it to you to confirm what your business owes them. Either way, the SOA answers a single question: as of this date, what is the balance between us, and how did we get to it?

It does that by listing, in date order, everything that moved the balance during the period. It opens with the balance carried over from the previous period, then works through each invoice raised, each credit note issued, and each payment received, and lands on the closing balance still outstanding. Nothing on a statement is new information — every line already exists as an invoice, a credit note or a receipt somewhere in the ledger. The statement’s job is to gather those scattered documents into one running view so both sides can look at the same number and agree on it.

That agreement is the whole point. A statement of account turns a vague sense of “I think they owe us something” into a precise, dated, line-by-line record that either reconciles cleanly or surfaces exactly where two ledgers disagree.

You will see it abbreviated to SOA almost everywhere in UAE finance teams. The SOA full form is nothing more exotic than “statement of account” — the three letters carry no hidden extra meaning, which is worth saying plainly, because the shorthand gets thrown around so freely that newcomers assume it must stand for something more technical. Whether a colleague says SOA in accounting or SOA in finance, they are pointing at this same document. The SOA meaning in accounting does not shift between the receivables desk and the payables desk either; only the direction of the money changes.

Opening + activity − payments = closing

The universal logic of every statement of account: prior balance, plus invoices and less credit notes and payments received during the period, equals the closing balance outstanding

What a statement of account contains

A well-built statement of account carries a predictable set of elements, whichever accounting system generates it.

Element	What it shows
Header details	Your business name, the counterparty name, the statement date and the period covered
Account reference	The customer or supplier account code, so it maps to the right ledger
Opening balance	The balance brought forward from the end of the previous period
Invoices issued	Each invoice raised in the period, with its number, date and amount
Credit notes	Any credits applied against the account, reducing the balance
Payments received	Each receipt or payment allocated in the period, with date and amount
Closing balance	The net amount still outstanding at the statement date
Aging summary	Often a breakdown of the closing balance by how overdue it is — current, 30, 60, 90+ days

The opening balance, the movements in the middle, and the closing balance always tie together arithmetically: opening balance, plus new invoices, less credit notes and payments received, equals the closing balance. If those numbers do not add up on a statement, the statement itself is wrong before anyone even starts reconciling it against the other side’s ledger.

The aging summary at the foot is where a statement stops being a record and starts being a collections tool. A closing balance of AED 84,000 tells you the total; an aging line that shows AED 60,000 of it is more than 90 days overdue tells you where to spend your Tuesday morning.

Statement of account vs invoice

This is the distinction that trips people up most, so it is worth being precise.

An invoice is a demand for payment tied to a single transaction. It says: you bought this specific thing, on this specific date, for this specific amount, and payment is due by this date. Each sale generates its own invoice, and each invoice stands alone as a request for money.

A statement of account summarises many transactions and shows the running balance. It does not demand payment for any one sale; it gathers all the sales, credits and receipts across a period and nets them into a single outstanding figure. You raise an invoice every time you sell something. You send a statement periodically — usually monthly — to summarise the whole account.

The practical consequence: a customer pays against invoices, not against the statement. The statement is the map that shows which invoices are still open; the invoices are the individual debts that get settled. A customer who “pays the statement” is really paying the specific unpaid invoices the statement lists. This is why an open-item statement, which shows each unpaid invoice as its own line, is so much easier to collect against than a single lumped balance.

The two directions: customer statements and supplier statements

Every statement of account points in one of two directions, and knowing which one you are looking at tells you what to do with it.

A customer statement, or accounts receivable (AR) statement, is money owed to you. You generate it and send it to your customer. Its closing balance is a receivable — an asset — and it feeds your collections process. When you send a customer statement, you are confirming the debt, prompting payment, and giving the customer a clean list of open invoices to settle.

A supplier statement, or accounts payable (AP) statement, is money you owe. Your supplier generates it and sends it to you. Its closing balance is a payable — a liability — and it feeds your reconciliation and payment process. When you receive a supplier statement, your job is to check it against your own AP ledger before you pay anything: does their list of open invoices match yours, have they recorded the payments you have already made, and is there anything on their statement you cannot find in your books?

The same document logic runs in both directions, but the discipline differs. On the AR side you are chasing; on the AP side you are checking. Both matter, and both are core to the accounts receivable and payable management function inside any well-run SME finance team.

Open-item vs balance-forward formats

Beyond direction, statements come in two layout formats, and the choice affects how easy the statement is to reconcile.

An open-item statement lists every individual unpaid invoice and credit note still outstanding on the account. Each open document appears as its own traceable line, so the reader can see exactly which invoices make up the closing balance. This is the format that reconciliation and dispute resolution depend on — when a customer queries a balance, you can point at the specific invoice in dispute rather than defending a lump sum. For B2B accounts with regular transactions, open-item is almost always the right choice.

A balance-forward statement carries a single prior-period total forward, then adds the current period’s new invoices and payments on top, without re-listing older open items individually. It is simpler to produce and read, and it suits consumer-style or low-transaction accounts. Its weakness is traceability: when the carried-forward balance is wrong, unpicking which old invoice caused the discrepancy is much harder because the detail has been rolled up.

For most UAE SMEs chasing B2B receivables, the open-item format is worth insisting on. It makes every line defensible, every dispute specific, and every reconciliation faster.

How SMEs actually use the statement of account

The SOA earns its keep across four everyday finance jobs.

1. Reconciliation. This is the SOA’s home turf. Reconciliation means matching your ledger to the counterparty’s — laying your record of the account next to theirs and resolving every difference. On the payables side, you take the supplier’s statement and tick it against your AP ledger: their open invoices against yours, their recorded receipts against your payments. Anything that does not match is a finding — a missed invoice, a duplicated entry, an unapplied credit, a payment posted to the wrong account. Reconciling supplier statements before payment is one of the cheapest controls an SME can run, and it routinely catches money that would otherwise be paid twice.

2. Collections. A customer statement is the backbone of a collections cadence. Sent monthly, with an aging summary, it prompts payment, confirms the debt, and gives the customer no excuse of “we didn’t know what was outstanding.” A structured collections process leans on the statement as its primary communication — statement first, then a reminder against the overdue lines, then escalation.

3. Month-end close. At close, the closing balance on your customer and supplier statements should reconcile to the receivables and payables control accounts in the general ledger. When they agree, the AR and AP sub-ledgers are clean and the close is defensible. When they do not, the statement is where the investigation starts.

4. Dispute resolution. When a customer or supplier disagrees about what is owed, the statement — especially in open-item format — is the neutral document both sides work from. It reframes an argument about a total into a specific conversation about which invoices are and are not settled.

“

A statement of account only protects you if it is reconciled, not just sent. An unreconciled supplier statement paid in full is how SMEs settle duplicated invoices; an uncollected customer statement filed and forgotten is how receivables quietly age past ninety days. The document is only as good as the discipline behind it.

The UAE and VAT context

Two points matter specifically for businesses operating under UAE VAT.

First, and most importantly: a statement of account is not a tax invoice. VAT is claimed on the tax invoice, not on the statement. The FTA sets out what a valid tax invoice must contain, and a summary of balances does not meet those conditions. If you are recovering input VAT, the evidence is the underlying tax invoice from your supplier — the statement is a reconciliation aid sitting alongside it, never a substitute for it. Filing statements as if they were VAT evidence is a common and avoidable error.

Second, the amounts on a statement are typically shown as the gross balances outstanding — the invoiced totals including VAT that the customer actually has to pay. That is correct for a collections and reconciliation document, because it reflects the real cash position. But it reinforces the first point: the statement shows the money owed, while the tax invoices behind each line carry the VAT breakdown the FTA cares about. Keep both, and keep them clearly distinct.

For SMEs, the clean rule is simple: use the statement to manage the relationship and the cash, and use the tax invoices to manage the VAT.

What a UAE tax invoice must carry that a statement does not

The reason the two documents cannot substitute for each other is written out in Article 59 of the UAE VAT Executive Regulation, Cabinet Decision No. 52 of 2017. A full tax invoice has to carry twelve particulars, and a statement of account carries almost none of them.

Art. 59(1) requires on a tax invoice	Does a typical statement of account show it?
The words “Tax Invoice” clearly displayed	No
Name, address and TRN of the supplier	Name and address usually; the TRN often
Name, address and TRN of the recipient, where registered	Name and address usually; the TRN rarely
A sequential or unique invoice number	No — the statement has its own reference
The date of issuing the tax invoice	It shows the statement date instead
The date of supply where different	No
A description of the goods or services	Usually only an invoice reference
Unit price, quantity, tax rate and amount payable in AED, per line	No
The amount of any discount offered	Sometimes, at balance level
The gross amount payable in AED	Yes — this is what a statement is for
The tax amount in AED, with the exchange rate where converted	No
A reverse-charge statement and the relevant provision, where applicable	No

Only the AED gross balance row is genuinely satisfied by a statement, and it is the one particular a collections document exists to show. Every other row — the tax amount in AED, the per-line rate, the sequential number, the words “Tax Invoice” — lives on the invoice and nowhere else. That is why an FTA reviewer will not accept a statement in place of the invoice. Only the last row of the “yes” column is genuinely satisfied, and it is the one particular a collections document exists to show.

Two related provisions are worth knowing, because they are where statements and invoices genuinely touch. Article 59(6) prohibits a registrant from issuing separate tax invoices for supplies that are already included on a summary tax invoice issued and delivered to the recipient. A summary tax invoice is a real instrument in UAE VAT and it looks superficially like a statement — but it must still carry the Article 59(1) particulars, and issuing it closes off separate invoices for the same supplies.

If your month-end document is genuinely intended to serve as the tax invoice for a month of UAE supplies, it has to be built to Article 59(1), not to statement conventions. Plenty of Dubai and Sharjah businesses run both: a summary tax invoice that meets Article 59(1) for the VAT, and a separate statement of account for the collections conversation.

Article 59(5) allows a simplified tax invoice, carrying the shorter list in Article 59(2), in two cases only: where the recipient is not registered, or where the recipient is registered and the consideration does not exceed AED 10,000. It is not available where the reverse charge under Article 48 of the Decree-Law applies. That AED 10,000 line is the one most UAE SMEs should have written into their invoicing template rules, because it decides which of two templates a given sale uses — and the FTA tests the invoice, not the intention behind it.

Timing matters too. Article 67(1) of Federal Decree-Law No. 8 of 2017 requires a registrant to issue a tax invoice within 14 days from the date of supply. A monthly statement sent on the 5th does nothing to satisfy that deadline for a UAE supply made on the 2nd of the previous month. The statement is a reconciliation document; the fourteen-day clock runs on the invoice, and Article 67(2) leaves the Executive Regulation to set the cases that run to a different period or require immediate issue.

How long a UAE business must keep its statements of account

Statements sit inside the same record-keeping obligation as the rest of the ledger. Cabinet Decision No. 74 of 2023, the Executive Regulation of the Tax Procedures Law, sets the periods in Article 3.

Situation	Retention period	Source
Accounting records, commercial books and information of a taxable person	5 years following the tax period they relate to	CD 74/2023, Art. 3(1)(a)
Persons other than taxable persons	5 years from the end of the calendar year the document was created	CD 74/2023, Art. 3(1)(b)
Real estate records	7 years from the end of the calendar year the document was created	CD 74/2023, Art. 3(1)(c)
Dispute with the FTA, ongoing tax audit, or notice of intended audit	Additional 4 years — in a dispute, until finally settled, whichever is later	CD 74/2023, Art. 3(2)(a)–(c)
Voluntary Disclosure submitted in the fifth year	Additional 1 year from the date of submission	CD 74/2023, Art. 3(2)(d)
Refund application on which the FTA has not decided	Additional 2 years	CD 74/2023, Art. 3(2)(e)
Records relating to real estate, for VAT	15 years after the end of the tax period they relate to	VAT ER, Art. 71(2)
Records supporting a Corporate Tax return	7 years following the end of the tax period	FDL 47/2022, Art. 56(1)

Last verified: 5 August 2026 against the texts published by the UAE Ministry of Finance and the Federal Tax Authority.

Two of those rows deserve a second look. The fifteen-year rule in Article 71(2) of the VAT Executive Regulation applies to records relating to real estate and is a VAT rule in its own right — it is not seven years, and it does not come from an amending decision. And Article 56(1) of the Corporate Tax Law imposes its own seven-year period on the records that support a return, running notwithstanding the Tax Procedures Law. A UAE business therefore has more than one clock running over the same AR and AP file, and the longest one governs. In practice that means a Dubai SME archiving its statements to the five-year rule alone can still be short of what the FTA is entitled to ask for.

The one place a UAE statement of account carries legal weight

Everything above says what a statement is not. There is one UAE VAT provision where it becomes the natural vehicle for something the law actually requires, and most SMEs never connect the two.

Article 64(1) of Federal Decree-Law No. 8 of 2017 lets a registrant supplier reduce output tax to recover the VAT on a bad debt, on four cumulative conditions: the goods or services were supplied and the tax charged and paid; the consideration has been written off in full or part as a bad debt in the supplier’s accounts; more than six months has passed from the date of supply; and the supplier has notified the recipient of the amount of consideration written off. That fourth condition is a positive obligation to tell the customer, in writing, what you have written off — and the customer statement, which already lists the invoices and the balance, is the document built for it.

The obligation runs both ways, which is the part payables teams miss. Article 64(2) requires a registrant recipient to reduce its own recoverable input tax where the supplier has reduced output tax and notified them, the recipient received the goods or services and deducted the input tax, and the consideration has gone unpaid for over six months. Article 64(3) sizes both adjustments at the tax related to the written-off consideration. So a supplier statement arriving with a write-off notice attached is not a courtesy — it is the trigger for an entry in your own UAE VAT return.

Position	What the six-month rule does	Source
Supplier, debt written off and notice sent	May reduce output tax	FDL 8/2017, Art. 64(1)
Supplier, notice never sent	Condition (d) unmet — no relief	FDL 8/2017, Art. 64(1)(d)
Customer, notified and unpaid over 6 months	Must reduce recoverable input tax	FDL 8/2017, Art. 64(2)
Either side	Adjustment equals the tax on the written-off amount	FDL 8/2017, Art. 64(3)

There is a Corporate Tax dimension on the same file. Article 28(1) of Federal Decree-Law No. 47 of 2022 allows expenditure incurred wholly and exclusively for the business, and Article 28(2)(c) denies a deduction for losses not connected with or arising out of the business. A written-off receivable is a deduction that has to be evidenced as a trading loss, and the aged statement — with the dates, the balances and the chase history behind it — is the evidence. Article 56(1) then keeps that file open to the FTA for seven years.

The practical instruction for a Dubai or Abu Dhabi finance team is short. Where a UAE receivable is heading for write-off, send the customer a statement that states the AED amount being written off, keep the delivery record, and diarise the six-month date from the supply rather than from the invoice. On the payables side, read every supplier statement for a write-off notice before you file it, because the AED adjustment it triggers is yours to make in your own UAE VAT return, not the supplier’s.

The scale is easy to underestimate. On a single AED 500,000 standard-rated invoice written off in full, the tax at stake is AED 25,000 — recoverable by the supplier under Article 64(3) if the notice went out, and lost entirely if it did not. Across a UAE trading business with a handful of failed customers a year, the statement that nobody bothered to send is the most expensive piece of unsent paperwork in the finance function.

Best practice for running statements well

Getting value from statements of account is less about the document and more about the routine around it.

Send customer statements on a fixed monthly cadence, shortly after month-end once the period’s invoices and receipts are posted. A predictable rhythm matters more than the exact date — customers build it into their own payables routine, and your collections process gains a natural cycle. Include an aging summary so every statement doubles as a prompt to act on what is overdue.

On the payables side, reconcile every supplier statement against your AP ledger before you release payment. This is the single most valuable habit, because it stops duplicated invoices, already-settled invoices and phantom charges before the money leaves. Treat any line on a supplier statement you cannot trace in your own books as a query to resolve, not a figure to trust.

Tie the whole thing to your close. At each month-end, the closing balances on your statements should reconcile to the AR and AP control accounts. When they agree, your accounting and bookkeeping records are clean and audit-ready; when they do not, you have found something worth finding early.

Where this leaves your finance function

The statement of account is a simple document that carries a lot of weight. Get it right — reconciled monthly, sent on a fixed cadence, tied back to the control accounts — and it becomes the quiet engine behind clean receivables, correct supplier payments and a close that ties out without drama. Get it wrong — generated ad hoc, never reconciled, treated as a tax document it is not — and it becomes the place where old errors hide until an audit surfaces them at the worst possible time.

The distinction to hold onto is the one most teams blur: an invoice demands payment for one transaction, a statement summarises many and shows the running balance, and a tax invoice — separate again — is the VAT evidence the FTA relies on. Keep those three clear and the rest follows.

For the deeper mechanics of checking a supplier statement line by line against your ledger, read our supplier reconciliation process guide. To see how statements fit into the wider receivables and payables cycle, explore our accounts receivable and payable management service.

Velmont Crest is a DED-licensed UAE accounting firm providing advisory, preparation and processing support across the full AR/AP cycle — customer and supplier statements, reconciliations, collections support and month-end close — for mainland and free zone SMEs. Read more on our insights hub or get in touch via our contact page.

---

Disclaimer: Velmont Crest is a DED-licensed accounting firm providing advisory, preparation and compliance support services. We are not a licensed tax agent or FTA representative. UAE VAT and tax invoice requirements change — verify current tax invoice conditions and input VAT recovery rules with the Federal Tax Authority framework and consult a licensed professional for advice specific to your circumstances.

References

• UAE Federal Tax Authority (FTA) — VAT and tax invoice requirements
• UAE Ministry of Finance — Taxation in the UAE
• UAE official portal — Value Added Tax (VAT)