ADCB Bank Statement Converter

TL;DR

ADCB statements pack a separate value-date column, multi-line descriptions, and bilingual Arabic / English narration into a tight PDF layout that breaks generic converters. ClearlyLedger ships a dedicated ADCB profile that stitches the multi-line descriptions back together, keeps the value date as a distinct field, and exports balance-verified Excel or Tally / Zoho / QuickBooks-ready CSV — FTA VAT compliant.

Why ADCB Statements Are Tricky

Abu Dhabi Commercial Bank is the second-largest UAE bank and a default for federal-government salary accounts, free-zone corporate accounts and retail customers across Abu Dhabi. Its statement PDFs are dense: the transaction description spans up to four physical lines, the value date sits in its own column, and incoming SWIFT remittances drop an IBAN reference on a separate row from the amount.

Generic table-extractors treat each physical line as a separate row, producing dozens of orphan entries with no debit / credit and an unreconciled closing balance. That output is useless for a VAT return.

Step 1: Download Your ADCB PDF

1. Log in to ADCB Personal Internet Banking or the ADCB mobile app.
2. Go to Accounts → e-Statements, select the account and period.
3. Download the PDF. ADCB email statements are password-protected — the default password is your account number or date of birth depending on enrolment date; the ADCB email body specifies.

Step 2: Upload & Unlock

Drag the PDF onto ClearlyLedger and enter whichever password ADCB assigned you — account number or date of birth — when prompted. That password has exactly one job: opening this specific PDF for this specific conversion. It is not written to a log, not attached to your account, and not carried over to your next upload; once the statement is parsed, both the password and the unlocked file are gone.

Step 3: What the ADCB Profile Does

• Stitches multi-line descriptions back into a single Payee field, capped at 30 characters for QuickBooks compatibility, with the remainder preserved in the Reference column.
• Keeps the transaction date and the value date as separate columns — important for accountants doing month-end accruals and settlement reconciliation.
• Preserves IBAN, SWIFT BIC and Direct Remit codes in the Reference column rather than dumping them into Description.
• Splits AED amounts with sign awareness — debit / credit columns populated correctly regardless of how ADCB has formatted the row.
• Bilingual narration: the Arabic column is preserved as a secondary reference so RTL auditors lose nothing.
• Runs balance reconciliation (opening + credits − debits = closing) before allowing export.

ADCB Business & ProCash Statements

This is where ADCB diverges most from a retail statement, and it's the part generic converters get wrong most often. ADCB Business and ProCash (corporate cash management) statements interleave individual transaction rows with batch-payment summary rows — a single line that rolls up dozens of underlying WPS salary payments or supplier disbursements into one settlement figure. Feed that into a generic table-extractor and it treats the summary row as just another transaction, so the batch total gets added on top of the individual payments it already represents and the closing balance comes out inflated by the exact size of the batch.

The ADCB Business profile recognizes the batch-summary row pattern specifically, pulls those rows out of the transaction ledger entirely, and keeps their totals in a separate metadata block instead — so the reconciliation math only ever counts each dirham once. For a company running weekly WPS batches, that's the difference between a statement that balances and one that's off by tens of thousands of AED for no visible reason.

Step 4: Export

Excel (.xlsx) and Standard CSV are on every plan including Free. Starter and above add direct-import CSV formats for Xero, QuickBooks, and Tally Prime. Dates default to DD/MM/YYYY for UAE locale, with clean AED amounts that need no reshaping.

FTA VAT & Corporate Tax

The export schema (Date, Description, Reference, Debit, Credit, Balance) preserves the transaction detail these records depend on. The two retention periods are not the same, which is the part people get wrong: VAT records must be kept for at least 5 years, while the Federal Tax Authority requires Corporate Tax records to be retained for at least 7 years after the end of the Tax Period they relate to — for Exempt Persons as well as Taxable Persons (FTA, 28 August 2025). Corporate Tax has applied at 9% on taxable income above AED 375,000 since 1 June 2023. Mainland LLCs registered with DED, free-zone companies in DMCC / JAFZA / ADGM, and federal-government salary account holders all use the same export.

Common Issues & Fixes

• Multi-line description split across rows. Generic tools do this; the ADCB profile prevents it. If you see it, you have not selected the ADCB profile — it should auto-detect; re-upload if not.
• Value date confused with transaction date. ClearlyLedger keeps both. Pick the one your accountant prefers in the preview before exporting.
• Closing balance off by a fil. Usually a separator misread on a single high-value row. The repair UI highlights the suspect row.

Key Takeaways

• Multi-line descriptions stitched into a single clean Payee field.
• Value date preserved as a separate column.
• ProCash batch-summary rows are pulled out of the ledger so WPS and supplier batches don't get double-counted.
• AED balance reconciliation before every export.
• Password unlock is conversion-scoped: not logged, not stored, not reused on your next upload.
• CSV imports directly into Tally Prime, Zoho Books and QuickBooks Online.

Ready? Convert your ADCB statement free, or browse the full UAE bank statement converter hub.

Written by John Snow, Financial Data Specialist.