How to Convert an SNB (Saudi National Bank) Statement to Excel

SNB — Saudi National Bank — is the largest bank in the Kingdom, formed from the 2021 merger of the National Commercial Bank (NCB, "AlAhli") and Samba Financial Group. That scale means its statements land on more Saudi bookkeepers' desks than any other bank's, and every one of them arrives in the same awkward shape: a PDF designed to be read, not calculated with. Retyping those rows by hand is where the month-end evening disappears — and it is at its most painful when the deadline is a ZATCA VAT return.

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

⚠️ One honest note up front. BayanSheet ships hand-tuned templates for a handful of Gulf banks. SNB is not one of them yet. For SNB statements the engine uses smart auto-detection — it reads the layout of your PDF, copes with Arabic and English statements and Arabic-Indic numerals, maps the columns it finds, and still runs the full reconciliation check. That works well, and it is not the same claim as a hand-tuned template — so give your first SNB file a one-minute column-level review.

Step 1 — Download the statement as a PDF

You want the bank's own PDF, not a screenshot and not a printed-then-scanned page. A native PDF carries a real text layer, which is what makes clean extraction possible.

From SNB / AlAhli online banking (desktop)

1. Sign in to SNB online banking in your browser.
2. Open the account you need from the accounts summary.
3. Look for Statements (sometimes shown as Account Statement or e-Statement).
4. Choose the period. Statement-cycle periods are usually cleaner than custom date ranges, because the opening and closing balances are printed on the document.
5. Download in PDF format. If the portal offers an Arabic or English version, either works — the converter reads both.

From the AlAhli mobile app

1. Open the AlAhli app and authenticate.
2. Tap the account, then the statements or transaction-history section.
3. Select the month or date range you need.
4. Download or share the PDF — mailing it to yourself or saving it to files both work.

💡 Prefer the download over the emailed copy. Statements you pull while logged in are frequently unencrypted, whereas emailed statements almost always carry a password. Downloading directly saves you the unlock step entirely.

If you only have a CSV or XLS export

Some accounts offer a direct CSV or Excel export of transactions. If you can get it, take it — but check it carefully. Bank-generated spreadsheets often omit the opening and closing balance lines, which means you lose the ability to reconcile the file against the statement it came from. A PDF plus a converter that checks the arithmetic is frequently the safer artefact.

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 file.

SNB, like most Saudi banks, derives the password from details you already hold, and the covering email states the exact formula. Common patterns across Gulf banks include some combination of:

Ingredient	Typical form
Date of birth	DDMMYYYY or DDMM
National ID / Iqama number	Full or last digits
Customer / CIF number	Full or last digits
Card or account number	Last 4–6 digits
Mobile number	Last digits

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

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.
• Save an unlocked copy. Open the PDF, enter the password, then use Print → Save as PDF to write out a decrypted version. Note that this route can rasterise some documents, turning selectable text into an image, which forces OCR and reduces accuracy. Prefer converting the original.

🔒 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, use 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 SNB 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 — in Arabic or English — and maps the date, description, debit, credit and balance columns. Where the statement uses Arabic-Indic numerals (٠١٢٣٤٥٦٧٨٩), those are normalised to standard digits so the amounts calculate in Excel.
5. The reconciliation check runs automatically: opening balance + credits − debits, compared against the closing balance printed on the statement, in SAR. Any row that does not add up is flagged.
6. Download the result as Excel (.xlsx) or CSV, depending on what your accounting software wants.

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

Because SNB is auto-detected rather than tuned, spend the one minute it takes to eyeball the first converted file — dates, the debit/credit split, and any Arabic descriptions. Once you have confirmed that format, subsequent statements in the same layout behave the same way. The general mechanics are covered in how to convert a bank statement to Excel, and the full library of guides lives on the blog.

Step 4 — Verify the output before it touches your ledger

This is the step most people skip and later regret. A conversion error is rarely loud; it is a single dropped row that surfaces three weeks later as a reconciliation that will not close — or worse, as a VAT figure that does not tie out.

Run these four checks on the converted file:

Check	What to look for	Why it matters
Balances reconcile	The tool confirms opening + credits − debits = closing (SAR)	Catches dropped rows and misread decimals
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
Numerals & dates	Arabic-Indic digits converted; day/month not transposed	Wrong figures or dates land transactions in the wrong VAT period

The reconciliation result does most of the heavy lifting. If opening balance plus credits minus debits equals the closing balance on the PDF, no row was lost and no amount was misread badly enough to matter — that is arithmetic, not a promise. Where a converter simply hands you rows and tells you to review them carefully before making financial decisions, 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 — Saudi record-keeping and ZATCA VAT

In Saudi Arabia, VAT-registered businesses file returns through ZATCA (the Zakat, Tax and Customs Authority), and the bank statement is one of the primary documents that ties your reported figures to money that actually moved. ZATCA requires records to be kept for at least six years, so the statement is not a throwaway — it is a document you may have to produce years later.

Two practical points follow from that:

• Keep the original PDF as the legal record. The Excel or CSV is your working copy for bookkeeping and for reconciling against your VAT return; the signed PDF from SNB remains the artefact ZATCA recognises. Do not delete it after converting.
• Get the dates right, because VAT periods are unforgiving. A transaction pushed into the wrong month by a transposed date lands in the wrong return. This is exactly why the date check in Step 4 matters, and why converting straight from the native PDF beats retyping.

A clean, reconciled sheet in SAR is the fastest way to prepare the output-tax and input-tax figures that feed the return — and to answer confidently if ZATCA ever asks how a number was derived.

Step 6 — Import into Xero, Zoho Books or QuickBooks

Each package wants a slightly different shape.

Xero

Go to Accounting → Bank accounts → the relevant account → Manage account → Import a statement, upload the CSV, then map the columns Xero asks for: date, amount (or separate spent/received), payee and reference. Set the date format to match your file exactly — mismatching it is the single most common import failure.

Zoho Books

Go to Banking → the relevant account → Import Statement, upload the CSV, then map date, description, debit (withdrawal), credit (deposit) and optionally reference. DD/MM/YYYY is the usual Gulf convention; set it explicitly. Save the mapping and Zoho will reuse it next month.

QuickBooks Online

Use Transactions → Bank transactions → Upload from file. QuickBooks accepts CSV with either a single signed amount column or separate debit and credit columns; pick whichever matches your export and map accordingly. Confirm the dates parsed as dates rather than text before you accept the batch.

✅ Import tip: 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.

Common mistakes to avoid

• Trusting a scanned or photographed statement. No text layer means OCR, and OCR on Arabic-Indic numerals is where silent errors creep in. Always start from the native PDF.
• Ignoring the reconciliation flag. If the tool says the totals do not tie out, do not export and move on — find the row it is pointing at.
• Deleting the PDF after conversion. ZATCA expects the original; the spreadsheet is not a substitute.
• Skipping the first-file review on an auto-detected bank. SNB is not tuned, so the one-minute check on a new statement format is the difference between confidence and a surprise at close.
• Emailing the statement and its password together. Separate channels, always.

Why in-browser processing matters for client statements

A bank statement is not an ordinary file. One month of a trading company's SNB account exposes its suppliers, its customers, its payroll, its margins and its cash position — everything a competitor or a fraudster would want.

When a converter uploads that PDF, the client's financial history is copied onto infrastructure you do not control. You inherit that vendor's storage practices, retention window, staff access and breach exposure, usually under terms nobody in the practice has read.

BayanSheet converts entirely inside your browser. There is no upload, so there is no stored copy to leak, subpoena or breach.

⚡ Prove it in fifteen seconds. Disconnect your Wi-Fi and convert a statement anyway. A browser-based tool keeps working because nothing needs to be sent. A tool that uploads will hang. No marketing page can fake that result.

Quick reference

Question	Answer
Where do I get the PDF?	SNB / AlAhli online banking or the AlAhli mobile app, statements section
Password?	Formula is in the covering email; downloads from inside banking are often unencrypted
Tuned template?	No — smart auto-detection (Arabic + English, Arabic-Indic numerals), with full reconciliation still applied
Is the file uploaded?	No — parsing runs in your browser
Output formats	Excel (.xlsx) and CSV
Keep the PDF?	Yes — it stays the official ZATCA record; the sheet is the working copy

Ready to try it on a real file? Start at the converter — the first 10 pages are free and no card is required.