Bookkeeping UAE: Your Bank Statement Isn't Bookkeeping

A founder in Al Quoz showed us his bookkeeping last month. He opened his laptop, pulled up the business banking app, scrolled through the month's transactions, and leaned back with the calm of a man who has everything under control. "There it is," he said. "Every dirham in, every dirham out. That's my bookkeeping." We asked him one question: who approved the AED 14,200 payment to the supplier on the 12th? He scrolled up. Looked at the line. "The bank doesn't say that." Then we asked him what tax treatment he'd applied to the AED 38,000 consultancy invoice from the UK firm. He scrolled again. The bank doesn't say that either. By the third question he had stopped scrolling. The bank statement tells you money moved. Bookkeeping in the UAE — at least the kind the Federal Tax Authority now expects — is everything the statement leaves out.

This is the conversation that has been doing the rounds in bookkeeping circles lately, usually dressed as an "unpopular opinion": your bank feed is not your bookkeeping. It is doing the rounds again on LinkedIn, and this time October gave it regulatory teeth. Two FTA decisions now define, in writing, what sits between a bank transaction and a defensible record — and a statement full of money movement clears neither of them. This is not a philosophical debate anymore. It is an enforcement standard.

What the FTA actually said — Decision No. 4 of 2026

On 2 June 2026, the FTA issued Decision No. 4 of 2026, setting out the rules and requirements for maintaining the information contained in accounting records and commercial books. It took effect on 30 July 2026. That means it has been binding for nearly three months while most of the market carried on exactly as before — and that is the first uncomfortable fact of this piece.

The Decision does not ask whether you keep records. It asks whether the information inside those records can actually be produced when the FTA asks for it. Practitioner analysis of the Decision describes three baseline tests: the retained information must be complete and identical to the originals, clear and easily legible, and accessible to the FTA on request — without delay or obstruction. (Farahat & Co, FTA Decision No. 4 of 2026 analysis)

Then it gets specific — and this is where the bank-feed habit collapses. The practical reading of the Decision, as translated by practitioners, is that every transaction needs to be reconstructable on its own:

• A unique reference, the date, and the counterparty — so any single entry can be located and matched independently.
• Amounts and the tax treatment — net value, VAT applied, the rate used, the ledger accounts hit.
• Links to the supporting documents — the invoice, contract, delivery note, bank entry or receipt that evidences the transaction.
• Classification data — cost centre, project, jurisdiction, whatever coding corporate tax and VAT reporting need.
• An authorisation trail — who recorded the entry, who approved it, who posted it.

Electronic records add their own discipline: stable formats, protection against undetected alteration, reliable time-stamps, audit trails, access controls, and searchable indexing — with the records retrievable within the timeframe the FTA specifies. Inability to produce a required record can itself constitute a breach. And partial scanning is expressly rejected: a scan must reproduce the whole document, every page, in order. Capturing only the signed page will not do. (Global Law Experts, Decision No. 4 practical guide, updated Oct 2026)

One more myth to clear while we are here: this is not a big-company rule. The framework's scope is driven by tax status and transaction activity, not company size — small enterprises are not automatically exempt from the substantive requirements. If you are a taxable person keeping commercial books, this is your standard.

Four questions your bank feed can't answer

Hold a bank statement next to that benchmark and the gap is visible in seconds. A feed gives you dates, amounts, and counterparty names. It never answers the four questions an auditor — or the FTA — actually asks:

1. Who chose this supplier, and why? The feed shows you paid someone. It doesn't show the commercial purpose, the quotes you compared, or the meeting where you decided. Under the decision on supplier verification (Decision No. 13 of 2026, in force since 1 October), documented judgement per supply is the standard — and judgement doesn't live in a transaction feed.
2. Who approved it? Decision 4's authorisation trail asks who recorded, who approved, who posted. The feed records none of the three. In founder-led SMEs, one person is often all three — which is exactly the control weakness the standard is designed to surface, as we saw when regulators penalised an auditor for dismissing the management-override risk.
3. What was the tax treatment — and who decided it? Was that imported consultancy invoice reverse-charge? Was the payment above the VAT registration threshold counted correctly? The feed knows an amount left the account. It has no opinion on your tax position, and the FTA will not accept "the bank shows it" as evidence of one.
4. Where is the document? The invoice, the contract, the delivery note — linked, indexed, retrievable. A feed row has no attachment. A business whose invoices live in disconnected folders, in inboxes only one employee can search, or in chat threads, fails the retrievability test while believing it is "fully documented."

None of this is theoretical. The FTA carried out over 103,000 field inspection visits in the first half of 2026 alone — up more than 20% on last year. The returns are in; now they are checking what sits behind them. And the check starts with the records.

Decision 13 joins the argument — judgement doesn't live in a feed

If Decision 4 defines what the record must contain, Decision No. 13 of 2026 defines the thinking the record must evidence. In force since 1 October 2026, it requires verification of suppliers before input VAT is claimed — and the standard is judgement-based: the FTA can disallow a claim where the business "knew or should have been aware" of an evasion link. We wrote about this when the rules took effect — a bookkeeping app can record a supplier payment, but it cannot perform the verification. The same logic now hits the bank feed even harder: a payment line is not evidence of diligence. It is evidence of payment.

Picture the FTA reviewing a sample transaction under both decisions at once. Decision 4 asks: show me the complete, linked, authorised record of this purchase. Decision 13 asks: show me the documented judgement behind this supplier. The business whose answer to both is "here's the bank statement" has answered neither. This is the October reality: the record standard and the judgement standard landed within three months of each other, and together they close the gap the bank-feed habit has been hiding in.

The seven-year shoebox

The retention maths sharpens the point. UAE tax law requires records to be kept for defined minimum periods — seven years for corporate tax records. Seven years of bank statements is not seven years of books; it is seven years of money movement with no memory attached. When an auditor samples a transaction from 2024 in 2029, the question will not be "did the money move?" The question will be "who, why, under what tax treatment, authorised by whom — prove it from the record."

Practitioners advising on the Decision put it bluntly: maintain your records as though the person retrieving them will not be you. Because it won't be you. It will be an auditor, a tax agent, or an FTA officer, working to a published benchmark, sampling transactions and following the links. Files that only one staffer understands, ledgers disconnected from their invoices, scanned PDFs with no audit trail — these are not records under Decision 4. They are the shoebox the Decision was written to retire.

The five-minute audit-readiness test

Here is a test you can run this week. Pick any five purchase transactions from last month — not the biggest, not the most complicated, any five — and try to produce, for each one, the full chain the Decision implies:

1. The ledger entry with a unique reference, date, and counterparty.
2. The supporting document — invoice, contract, delivery note — linked to that entry by the same reference.
3. The tax treatment recorded at the time: VAT rate applied, and why.
4. The authorisation — who approved the spend and posted the entry.
5. The whole chain retrievable in minutes, not days — by someone who wasn't involved.

If you clear five out of five, your records are doing what Decision 4 asks. If you found yourself opening three apps and messaging a colleague for two of them, you are running on the bank-feed habit — and you now know the standard it fails. Most businesses we test land at two or three. The gap is rarely malice; it is a system designed for money tracking being asked to do evidence work.

What to fix this month — before the FTA asks

The good news: this is a systems problem, not a history problem. The businesses closing the gap fastest are doing four things:

1. Join the ledger to the document at entry. Every invoice gets a unique reference that appears in the ledger posting and on the stored document. This is the single change that kills the shoebox — no more ledgers floating free of their evidence.
2. Capture authorisation as a data field, not a memory. Who approved the payment, who posted it. In a founder-led business this can be a simple approval step in the workflow — what matters is that it exists in the record, not in the founder's head.
3. Index everything for someone who isn't you. One searchable place, consistent naming, no folders that only one employee understands. Retrieval speed is now a compliance metric — build for the stranger.
4. Attach judgement to the payment, not just the amount. Supplier choice rationale, commercial purpose, tax treatment — recorded when the decision is made, not reconstructed at audit. Decision 13 makes contemporaneous evidence the currency; Decision 4 makes the record its vault.

Note what none of this requires: a new ERP, a bigger team, or a six-month project. It requires discipline at entry — the month-end close captures what the transaction day recorded. The expensive version is reconstruction: paying professionals to rebuild, from memory and fragments, a chain the standard expects you to have kept all along. We have seen that bill. It is larger than the discipline costs, every time.

The debate: "my bank shows everything"

It doesn't. Your bank shows money. The FTA's standard shows what the money meant — who chose it, who approved it, what tax position it took, and where the document is. A bank feed is a cash-flow tool, and a fine one; it belongs in the treasury conversation, alongside the cash-flow planning it serves. But as a record of the business's tax reality, it is one line of evidence where the Decision demands a chain. "My bank shows everything" is the 2026 version of "my PDFs are my records" — and the FTA answered that one in June.

The uncomfortable question for the comments: pick any payment from last month — could you produce its full chain by Friday? The unique reference, the document, the tax treatment, the authorisation, retrievable by a stranger. If the answer is a scroll through a banking app, October's two Decisions just told you what that scroll is worth at audit. And with deadlines stacking across the compliance calendar, the businesses that fix their records now are buying something no deadline gives you: the ability to answer the FTA with a link instead of a story.

Not sure your books would pass the five-minute test? Talk to Escrow Consulting Group. We run free accounting system health checks for UAE businesses — a review of how your records, documents, and approvals actually hold up against the FTA's published standard, plus monthly and catch-up bookkeeping that captures the chain at entry instead of reconstructing it at audit. Visit escrowconsultinggroup.com for a free consultation.