Import a bank statement into your UAE books: a review checklist
Check a PDF or CSV bank-statement import for dates, amounts, duplicates and completeness before using the transactions in your UAE bookkeeping or tax review.
A statement import moves transactions into your books, but the first useful question is whether those records faithfully represent the bank statement. An upload can finish successfully while an ambiguous date, an unreadable PDF row or an overlapping export leaves the dataset incomplete. Categorisation and tax estimates then inherit that problem.
Use the process below to review a statement from the original file through to a reconciled transaction set. It includes a numerical control example and specific checks for dates, amounts and duplicates. The TaxAI import support guide explains the product steps; this article explains how to decide whether the result is ready for bookkeeping review.
Prepare the correct original and a review record
Before uploading, confirm the legal entity, bank account, currency and statement period. Download the original from the bank and keep an unchanged copy. Record the opening balance, closing balance and the bank’s debit and credit totals when available. Note the transaction count if the export provides one; do not count page headers or balance-forward lines as transactions.
Choose the intended company in TaxAI before opening Books and selecting Upload statement. A technically correct import into the wrong company’s workspace creates an accounting problem. If the account or period is unfamiliar, resolve that uncertainty first rather than uploading a file and hoping the description will identify it later.
TaxAI’s upload accepts CSV and PDF files. CSV is a useful fallback when PDF extraction is unavailable or a document cannot be read reliably. For a scanned PDF, check that the amounts and dates are legible and that all pages are included. A recognisable bank logo does not establish that every transaction row can be extracted accurately.
Inspect dates and debit or credit direction
Open a CSV in a viewer that preserves the underlying values. Check its column names, date convention, amount format and currency. A date written as 03/04/2026 could mean 3 April or 4 March. Establish the bank’s convention from an unambiguous date and compare the imported result, especially when an export was generated with different regional settings.
Check a known incoming receipt and a known outgoing payment. Some statements use a signed amount column; others separate debits and credits. A supplier payment should not become income because a minus sign was lost or the wrong column was interpreted. For values such as 1,250.00, confirm whether commas are thousands separators and periods are decimal separators in that particular export.
If a date or sign is wrong, stop the review and identify the underlying format issue. Repeatedly editing unrelated cells until a file imports can hide the cause. Retain the original, document a necessary conversion and compare the transformed data with the bank’s values before relying on it.
Test completeness with more than a closing balance
Consider an illustrative AED account with an opening balance of AED 20,000, receipts of AED 12,000 and payments of AED 7,500. The expected closing balance is 20,000 + 12,000 − 7,500 = AED 24,500. Confirm that this agrees with the bank’s closing balance and with the transactions used in your reconciliation.
Then compare receipts and payments separately. Suppose an AED 200 customer receipt and an unrelated AED 200 supplier payment were both omitted. The net movement would remain the same, so the closing balance could still appear correct. However, receipts would be understated by AED 200, payments would be understated by AED 200 and two business records would be missing.
For that reason, use several controls together: the bank’s debit total, credit total, transaction count and opening-to-closing movement. If the workspace does not display a particular control, compare its transaction list with a separate review sheet. Avoid assuming that a total labelled income represents every bank credit; owner funding or a transfer may belong to a different accounting category.
Inspect the first and last transactions and several from the middle of the file. For PDFs, include rows around page breaks, repeated headers and multi-line descriptions. Compare a large transaction, a refund and a bank fee. These checks target extraction problems that a quick glance at the newest transactions can miss.
Interpret imported and skipped counts carefully
TaxAI reports the number of transactions imported and duplicates skipped. Those figures are useful review evidence, but they do not independently certify that every row in the original statement was read correctly.
In an illustrative export containing 120 genuine transactions, a result of 115 imported and five duplicates skipped might be correct if those five entries already exist from an earlier overlapping statement. Check the existing five against the bank references. Do not conclude that the import is complete solely because 115 + 5 = 120: first establish that 120 is the correct transaction count and that the skipped entries are genuinely represented in the books.
Two legitimate payments can share a date and amount. One payment can also appear with different descriptions in separate exports. Use the bank reference, direction, counterparty and source document to resolve the distinction. Before correcting a suspected duplicate, establish which record is extra and what evidence supports the correction.
Resolve cash movements before assigning tax treatment
Review transfers between your own accounts, owner contributions, loan receipts and repayments, customer refunds, supplier refunds and bank fees. A cash movement is not automatically a sale or an operating expense. For a transfer, find the matching movement in the other account; for a loan repayment, obtain the information needed to distinguish principal from interest or charges.
Use transaction review and categorisation after checking the imported data. Review the suggestions produced by Auto-categorize and any tax classifications against the invoice or other supporting evidence. A bank description such as “online payment” does not explain the business purpose or establish VAT recovery.
Complete a bank reconciliation after those checks. Keep any unresolved differences in an exception log with the reference, amount, owner and action needed. The goal is to know what remains uncertain before a report or estimate is used.
Handle a failed upload without multiplying the problem
Read and retain the error message before retrying. Confirm the file type, selected company and permission to change its books. If a PDF cannot be processed, obtain a CSV export from the bank where available and perform the same completeness checks; do not assume that changing formats removes the need for review.
After an uncertain result, inspect the transaction list and the import confirmation before submitting the file again. If some records were added, a blind retry can make an existing overlap harder to understand. Seek support with the file type, action attempted and error message. Avoid attaching a private bank statement to the initial message; share only what is needed through an appropriate support process.
Save the original, any documented transformation, import result, review controls and outstanding questions. Follow the corporate-tax record-keeping guidance so the figures can be traced back to their evidence when a later tax or accounting question arises.
Product workflow checked against current support documentation and source on 26 October 2026. Numerical examples are illustrative.