How to Convert a QNB Statement to Excel (Qatar Guide)

QNB is the largest bank in the Middle East and Africa by assets, which means its statement PDF lands on more Qatari bookkeepers' desks than any other single document. And every month the same thing happens to it: the transactions are all there — dated, described, debited and credited, with a running balance down the side — but locked inside a file built to be read, not calculated with. So they get retyped, by hand, one row at a time.

This guide walks the whole path: getting the statement out of QNB, dealing with the password, converting it to Excel or CSV, verifying the numbers survived the trip, and importing the result into Xero, Zoho Books or QuickBooks.

⚠️ One honest note up front. BayanSheet ships hand-tuned templates for four banks — Emirates NBD, FAB, ADCB and Dubai Islamic Bank — and QNB is not one of them. For QNB the engine uses smart auto-detection: it reads the layout of your PDF, handles Arabic and English narration and Arabic-Indic numerals (٠١٢٣), and still runs the full reconciliation check on the result. That works well, and it is not the same claim as a tuned template — so give your first QNB file a one-minute sample review. If the layout gives the auto-detection trouble, email a sample through support and it will get tuned; the founder answers those personally.

Step 1 — Download the statement as a PDF

You want the bank's own PDF, not a mobile screenshot and not a printed-then-scanned page. A natively generated PDF carries a real text layer, which is what makes clean extraction possible at all. Screenshots and scans are images with no text layer at all — BayanSheet detects that and refuses the file rather than guessing at it, because there is no OCR step anywhere in this product. Not sure which you have? Open the PDF and try to select a transaction line with your mouse: if the text highlights it will convert, and if nothing selects it is an image, so download the statement again from online banking or ask the bank for a digital copy.

Menu labels change over time and business banking differs from retail, so treat the paths below as approximate — the destination is the same in every channel.

Channel	Rough path	Note
QNB Internet Banking	Accounts → select the account → Statements / Account Statement → choose the period	The cleanest source for conversion
QNB Mobile	Accounts → the account → Statements / e-Statement	Convenient, though export options are narrower than on desktop
QNB e-statement by email	Arrives automatically once you register for the service	Usually the encrypted copy — see step 2
Branch or relationship manager	Requested statement, often stamped	Use when a certified copy is needed for a third party

Choose full statement-cycle periods over custom date ranges where you can: a full cycle prints its own opening and closing balances, which is exactly what step 4 needs. And if you are assembling files for the annual close or an external auditor, pull the whole period in one file — one file means one reconciliation check instead of twelve.

Step 2 — Handle the password-protected PDF

If the PDF asks for a password when you open it, that is the bank's encryption, not a corrupted download. No converter can read the transaction table until the file is unlocked.

The password is derived from details you already hold, and the covering email states the exact formula. Across Gulf banks the ingredients are usually some combination of:

Ingredient	Typical form
Date of birth	DDMMYYYY or DDMM
Customer / QID number	Full or last digits
Account number	Last 4–6 digits
Name	First few letters, often uppercase
Mobile number	Last digits

Always take the formula from the email that delivered the statement rather than guessing — repeated wrong attempts waste time, and the wording is right there in the message.

Once you can open it, there are two routes:

• Convert it as-is. BayanSheet accepts encrypted PDFs and asks for the password locally in your browser. Neither the file nor the password is transmitted anywhere.
• Save an unlocked copy. Open the PDF, enter the password, then use Print → Save as PDF to write a decrypted version. Be aware this route can rasterise some documents, turning selectable text into an image — and an image-only PDF is refused rather than guessed at — so prefer converting the original, or fall back to a fresh download from internet banking.

There is a fuller treatment in our guide to converting password-protected bank statements.

🔒 Never email the password in the same thread as the statement. It defeats the entire point of the encryption. If you must send both to a colleague or a client, use two separate channels.

Step 3 — Convert the statement to Excel or CSV

With the PDF in hand:

1. Open BayanSheet in your browser.
2. Drag the QNB PDF onto the page — or use the file picker.
3. If the file is encrypted, enter the password when prompted. It stays on your machine.
4. Smart auto-detection reads the transaction table and maps the date, description, debit/withdrawal, credit/deposit and balance columns — in Arabic or English — extracting every row and converting Arabic-Indic numerals to values Excel can sum.
5. The reconciliation check runs automatically and flags any row that does not add up.
6. Download the result as Excel (.xlsx) or CSV, depending on what your accounting software wants.

Nothing is uploaded at any point. The parsing runs as JavaScript inside the browser tab you already have open.

Two things worth a glance on a Qatari statement specifically. Amounts are in Qatari riyals to two decimal places, and the currency may be written QAR or QR in the header rather than beside each figure — confirm the amount column arrived as numbers, not text, before you build formulas on it. And corporate statements in the Gulf frequently carry two date columns, a posting date and a value date. If yours does, decide which one your ledger uses and stay consistent across the year; mixing the two produces a period-end difference that is genuinely painful to trace.

Because QNB is auto-detected rather than tuned, take one minute on the first file of a given format: open the converted sheet next to the PDF and spot-check a sample of rows plus the totals. Once the mapping is confirmed, later statements in the same format behave the same way. The general mechanics are in how to convert a bank statement to Excel, and there is a regional overview in the Qatar, Kuwait, Oman and Bahrain converter guide.

Step 4 — Verify the output before it touches your ledger

The costly extraction error is rarely the loud one — it is the silent one: a single dropped row, a decimal read wrong, or a withdrawal that landed in the deposit column. The table looks perfect, and the problem surfaces three weeks later as a reconciliation that will not close.

The governing equation:

Opening balance + total credits − total debits = closing balance

Run these checks on the converted file:

Check	What to look for	Why it matters
Balances reconcile	Opening + credits − debits = closing (QAR)	Catches dropped rows and misread decimals
Row completeness	Row count matches the PDF	Missing or duplicated transactions
Debit / credit split	Two distinct columns, correct signs	A merged amount column inverts your net movement
Descriptions intact	A wrapped narration stays on one row	Split descriptions create phantom transactions
Arabic-Indic numerals	Amount columns read as numbers, not text	Text amounts will not sum in Excel
Dates correct	Day and month not transposed	Wrong dates land transactions in the wrong period

BayanSheet runs this reconciliation automatically after every conversion — the opening-to-closing equation plus a per-row running-balance check — and marks the rows that do not balance, down to a one-riyal difference. A failing row is flagged in the preview rather than quietly exported. That is arithmetic, not a promise. Where a converter simply hands you rows and tells you to review them carefully, it is transferring the checking work back to you. Our five-test method for evaluating any converter, including this one, is in how to verify a bank statement converter.

Step 5 — Qatari record-keeping, and why this still matters without VAT

Let us be precise about the tax position, because plenty of Gulf content is not: Qatar has not implemented a VAT regime as at the time of writing. There are no input and output VAT columns to code, and no quarterly return to tie your statement back to.

What Qatar does have is corporate income tax, administered by the General Tax Authority through the Dhareeba portal, and a record-retention rule with real teeth: taxpayers carrying on business activity in Qatar must keep accounting books, records and supporting documentation for ten years following the year they cover, extended for as long as any dispute over them remains unresolved. Ten years is long enough that how you file today is a decision about a colleague you have not met yet.

📁 Ground rule: the Excel file is a working copy, not a replacement for the original record. The QNB PDF is the document the bank issued and it remains the record of authority; the spreadsheet is where the work happens. Keep both.

A layout that pays off later:

• Name files consistently: QNB_account-no_2026-Q1.pdf with a matching .xlsx.
• Keep the balance column in the spreadsheet even after classifying — it is the fastest way to trace any discrepancy.
• Add your own classification columns rather than editing the original narration.
• Do not delete rows you consider irrelevant; keep them so the sheet still ties back to the statement.

Step 6 — Import into Xero, Zoho Books or QuickBooks

Each package wants a slightly different shape, but two habits prevent most failures: standardise the date format across the whole column before exporting (DD/MM/YYYY is the usual Gulf convention, and a mismatch here is the most common CSV rejection), and keep debit and credit separate — if the software wants one signed amount column, derive it with a positive/negative formula rather than merging by hand.

• Xero — Accounting → Bank accounts → the account → Import a Statement, then map date, description and the amount columns.
• Zoho Books — Banking → the account → Import Statement, map the columns, and save the mapping so it is reused next month.
• QuickBooks Online — Transactions → Bank transactions → Upload from file; confirm dates parsed as dates, not text, before accepting the import.

Import one month first and reconcile it before batching a whole year — if the mapping is wrong you would much rather find out across 40 rows than 500. The mapping step is covered in importing bank statements into accounting software, with a Tally-specific walkthrough in importing bank statements into Tally.

Common mistakes

• Converting a mobile screenshot instead of the original PDF.
• Skipping the reconciliation check because the table "looks fine".
• Mixing posting date and value date within the same ledger period.
• Keeping only the Excel file and deleting the original PDF — a mistake that shows up years later, in a country with a ten-year retention rule.
• Skipping the first-file review on an auto-detected bank. QNB is not tuned, so that one minute is the difference between confidence and a surprise at close.

Conclusion

Converting a QNB statement to Excel saves hours of manual entry, but the real value is in step four: verifying that the balances reconcile before the numbers reach your ledger. Download the original PDF, unlock it if needed, convert, verify, then import — and always keep the PDF as the record of authority.

Try it on a single statement at the converter and compare the output against the PDF in front of you — the first 10 pages are free, no card is required, and purchased credits never expire. For more accounting guides, browse the BayanSheet blog.