Credit card statements turn into expense-coded books through five steps: assign every card a fixed code set, map the statement lines to those codes, split personal from business spend, attach the supporting invoice, and reconcile the card balance at month-end. The statement is evidence of payment — it is not the accounting. Here is the 2026 workflow that turns it into books the FTA and your auditor will accept.
TL;DR
- A card statement proves payment, not VAT — the tax invoice is the claimable document.
- Code to the merchant's business, not the category the card app suggests.
- Split personal spend out at the card level, every month, with a paper trail.
- Attach the invoice to each coded line before the month closes.
- Finanshels runs card-statement coding as part of its bookkeeping service.
Why this matters
Card spend is where UAE books quietly rot. The statement arrives with clean merchant names, a card app suggests categories, and six months later the P&L carries "Software" lines that are actually office supplies, VAT recoveries that were never claimed, and a director's personal purchase sitting inside marketing costs. Every one of those misstates the accounts — and the last one is a tax problem, not a tidy-up.
The FTA's view is blunt: input VAT recovery under Article 59 of Federal Decree-Law No. 8 of 2017 requires a valid tax invoice, and a card statement is not one. The statement proves the payment; the invoice proves the VAT. Coding statements directly from the card app loses both. (Federal Decree-Law 8/2017, uaelegislation.gov.ae)
Step 1: fix the code set before the first statement arrives
Decide the expense codes once, for the business, and stop revising them mid-year:
- Marketing and advertising
- Software and subscriptions
- Office and premises costs
- Travel and accommodation
- Government fees and licensing
- Repairs and maintenance
The set is small on purpose. A twenty-code chart of accounts on a single card is how spend gets coded to the wrong bucket forever.
Step 2: map the statement lines to the codes
Work the statement top to bottom, one month at a time:
- Assign each line the code matching the merchant's actual business, not the app's suggested category.
- Confirm the amount and currency against the merchant's invoice or receipt.
- Flag recurring lines — subscriptions, insurance, retainer fees — so future months code themselves.
The recurring-line list is the single biggest time saver in this workflow: most card spend repeats, and a coded month should take minutes, not an evening.
Step 3: split personal from business spend — every month
Any personal transaction on a business card gets coded to the owner's current account, not to an expense. The entry reads "director current account" and carries the supporting note. Two reasons this is non-negotiable:
- The accounts stay true — expenses represent business activity only.
- The tax position stays defensible — personal spend inside business costs is an FTA finding waiting to happen.
Step 4: attach the invoice behind every coded line
The statement line gets its supporting document at the moment of coding: the supplier's tax invoice with the TRN, or a receipt for the small purchases that do not carry one. This is what makes the coded books audit-ready — every figure can walk from the ledger to a document in one step.
Step 5: reconcile the card balance at month-end
At close, tie the card's statement balance to the ledger's credit-card control account. The statement balance, payments made and outstanding balance should agree to the fils. A mismatch means a line was coded twice, a refund was missed, or a payment was recorded against the wrong month. Fix it in the month it appears — carry-forwards compound.
What the coding looks like across statement volumes
| Lines per month | Manual coding | Systematic / outsourced coding |
|---|---|---|
| Under 30 | 30–45 minutes, manageable | Auto-coded with monthly review |
| 30–100 | Half a day, error-prone | Recurring rules clear most lines |
| 100+ | Not sustainable by hand | Statement import with rule engine and exception review |
At 100+ lines a month the manual path stops being bookkeeping and becomes a reconstruction exercise at year-end — the exact point Finanshels takes over card-statement coding inside its accounting and bookkeeping service.
FAQ
Can I code expenses straight off a credit card statement in the UAE?
You can record the payment, but the expense and its VAT need the supplier's tax invoice. A card statement proves what was paid; it does not carry the TRN, VAT amount or invoice elements the FTA requires for input tax recovery.
How do I handle personal spending on a business card?
Code it to the owner's current account, not to an expense, every month. Personal spend inside business expenses misstates the accounts and creates a tax exposure if it reaches a return.
What is the fastest way to code recurring card charges?
Build a recurring-line map: every subscription, retainer and fixed monthly charge gets a standing code. After the first month, most statements code themselves and the review is exceptions-only.
Do I need an invoice for every small card purchase?
For input VAT recovery, yes — Article 59 of Federal Decree-Law 8/2017 conditions the claim on a valid tax invoice. Small purchases from unregistered vendors may have nothing to recover, but they still need coding and a receipt for the accounting records.
How often should the card balance be reconciled?
At every month-end. The statement balance, payments and outstanding balance should tie to the ledger's card control account to the fils, in the month the difference appears.
One last thing
The card control account is the canary for the whole ledger. When it reconciles every month, coding discipline holds everywhere else; when it drifts, the drift is usually in every other account too.
