Bank Statement Converter for Qatar, Kuwait, Oman and Bahrain

There is a lot of guidance online about converting UAE and Saudi bank statements, and almost none about the rest of the Gulf. If you keep books for a business in Doha, Kuwait City, Muscat or Manama, you have probably noticed that most converter tools do not mention your bank at all.

That is a gap in the marketing, not a gap in the technology. A Qatar National Bank statement is a table in a PDF, exactly like every other statement — the layout differs, but the problem does not. This guide covers the banks people in these four markets actually deal with, what each country's tax position means for your records, and the workflow that gets a statement into Excel without it passing through anyone's server.

The banks, country by country

Statement layouts vary more between these four markets than people expect. Column order, whether debit and credit are separate columns or a single signed amount, where the running balance sits, and how bilingual narration is laid out all differ.

Qatar

Bank	Notes on the statement format
Qatar National Bank (QNB)	Wide corporate layout; value date and posting date often separate
Commercial Bank (CBQ)	Descriptions frequently wrap to a second line
Doha Bank	Retail and corporate exports differ noticeably
Qatar Islamic Bank (QIB)	Islamic-finance terminology in the narration field

Kuwait

Bank	Notes on the statement format
National Bank of Kuwait (NBK)	Dense layout; long reference strings can wrap
Kuwait Finance House (KFH)	Bilingual headers with Islamic-product descriptions
Gulf Bank	Running-balance column placement varies by account type
Burgan Bank	Compact spacing between transaction rows

Oman

Bank	Notes on the statement format
Bank Muscat	Multiple export formats depending on channel used
Bank Dhofar	Bilingual narration in a single field
Sohar International	Corporate statements carry extra reference columns

Bahrain

Bank	Notes on the statement format
National Bank of Bahrain (NBB)	Standard tabular layout, generally clean text layer
BBK	Descriptions may include merchant strings that wrap
Ahli United Bank	Layout differs between retail and business accounts

What is tuned and what is not — stated plainly. BayanSheet ships hand-tuned templates for four UAE banks only: Emirates NBD, FAB, ADCB and Dubai Islamic Bank.

Every bank listed above is handled by auto-detection. The engine reads the table structure out of the PDF itself rather than applying a pre-written template — and the balance check runs regardless, so you always know whether the extraction reconciles.

We would rather tell you that than publish a list of two hundred "supported" banks that all get the same generic treatment.

The balance check is the point

Any tool can produce rows. The question is whether those rows are the rows that were in the document.

BayanSheet takes the opening balance, adds every credit, subtracts every debit, and confirms the result matches the closing balance printed on the statement. Where it does not match, the offending rows are flagged so you can look at them directly.

The failure mode that costs you time is the silent one. A dropped row, a misread decimal, or a debit posted as a credit will not look wrong on screen. It shows up weeks later as a reconciliation that will not close, and by then you have no idea which file introduced it.

Checking the arithmetic at the point of extraction is the difference between "this looks right" and "this adds up." It is also the only claim a converter can make that you can independently verify in ten seconds against the PDF.

VAT status by country — and why records still matter

The four markets sit in different places on indirect tax, which changes what you do with the converted data but not whether you need it.

Country	VAT position	What it means for your workflow
Qatar	No VAT regime implemented at time of writing	Statements are used for reconciliation, audit support and reporting rather than VAT coding
Kuwait	No VAT regime implemented at time of writing	Same — clean transaction records still underpin the close
Oman	VAT in force, administered by the Oman Tax Authority	Statement lines are matched to invoices and coded for input/output tax
Bahrain	VAT in force, administered by the National Bureau for Revenue	Same — returns rest on transaction data that must tie back to the bank

In every one of these markets the original PDF stays the record. It is the tamper-evident document your bank issued, and it is what you retain.

The Excel file is the working copy. It is what you sort, filter, categorise, reconcile and import. Converting does not replace the statement; it saves you from retyping it.

That framing answers the question we hear most often — if the PDF is the legal record, why convert it? Because a PDF is a record, not a workspace. It cannot be filtered, formula'd or imported. The conversion creates the layer where the actual accounting work happens.

The workflow

1. Download the PDF from the bank's own portal or app. Not a scan, not a photo, not a screenshot. A directly downloaded statement carries a text layer, and that single choice does more for extraction quality than any tool setting. Scanned statements are images and results depend entirely on scan quality.

2. Drop it into the converter. Everything happens in your browser — the file is not transmitted. If the statement is password-protected, as bank-emailed statements often are, you will need that password; the password-protected statement guide covers the common cases.

3. Read the balance-check result first. Before you export anything, check whether it reconciled. If rows are flagged, open the PDF at those rows — usually it is a wrapped description or an unusual fee line, and it resolves in seconds once you know where to look.

4. Export and import. Excel or CSV, then into your accounting system. The mapping step is covered in importing bank statements into accounting software, and there is a Tally-specific walkthrough in importing bank statements into Tally.

The sixty-second output check

Whatever converter you use, spend a minute on the output before you build anything on it. These are the five things that go wrong most often with Gulf statements, and all of them are visible at a glance.

What to check	How to check it	What good looks like
Debit and credit columns	Scan the two amount columns	Separate and correct, not merged into one field
Multi-line descriptions	Find a long narration in the PDF	One transaction stayed on one row
Dates	Click a date cell	Parsed as a date, not a left-aligned text string
Amounts	Look at alignment in Excel	Right-aligned numbers you can sum
Row count	Compare against the PDF	Same number of transactions in and out

Arabic-Indic numerals (٠١٢٣٤٥٦٧٨٩) appear in some statements from bilingual banks across these markets, particularly in Islamic-banking exports. BayanSheet maps those characters to their numeric values during parsing, so the amounts arrive as real numbers rather than text. The alignment test above catches this instantly: numbers right-align by default in Excel, text does not.

Test the privacy claim yourself

Do not take this on trust, from us or anyone else.

The offline test: disconnect your internet, then convert a statement.

A browser-based tool keeps working, because nothing needs to be sent anywhere. A tool that uploads to a server fails or hangs. The result cannot be faked, and it takes fifteen seconds.

When the file in front of you is a client's full transaction history, that is worth knowing before you click convert. The complete evaluation checklist is in how to verify a bank statement converter.

Try it on a real statement

Ten pages are free and no card is required. Use an actual QNB, NBK, Bank Muscat or NBB statement rather than a sample — the balance check will tell you within seconds whether the extraction held up on your bank's specific layout.

Convert a statement now, or see the Gulf converter comparison for how to weigh the options.