How to Convert a SABB (Saudi Awwal Bank) Statement to Excel

SABB — now formally Saudi Awwal Bank (SAB) after its merger with Alawwal Bank — sits behind a large share of the Kingdom's business current accounts, so its statement lands on a Saudi bookkeeper's desk with some regularity. And it arrives in the same awkward shape every time: pages laid out to be read by a person, not calculated with. Between that PDF and a sortable, importable Excel sheet sit hours of manual re-entry that nobody needs to do.

This guide walks the whole path: getting the statement out of the bank, dealing with the password, converting it to Excel or CSV, verifying that 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 exactly four banks — Emirates NBD, FAB, ADCB and Dubai Islamic Bank — and SABB is not one of them. Instead the engine uses smart auto-detection: it reads the layout of your PDF, copes with Arabic-Indic numerals (٠١٢٣) and bilingual Arabic/English narration, maps the columns it finds, 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 SABB file a one-minute sample review. If it needs work, email me a sample and I will tune the layout for you.

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 native PDF carries a real text layer, which is what makes clean extraction possible. 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.

Channel	Rough path	Note
SAB Online	Log in → e-statement section → pick the statement by date	The cleanest source for conversion
SAB Mobile app	Account → statements / documents → select period	Convenient, but confirm you are getting a PDF and not an image
Email e-statement	The notification email points you to the statement	Often the encrypted copy — see step 2

Those paths are deliberately loose: banks redesign their apps, and a button label quoted here would be wrong within a year. Look for the statements or e-statement area of whichever channel you use, and pick PDF as the format.

Two habits make everything downstream easier. Choose statement-cycle periods over custom date ranges where you can — a full cycle prints its own opening and closing balances, which is exactly what the reconciliation step checks against. And pull the whole period in one file when you are assembling records for a VAT return or an external auditor: a full quarter in a single PDF means one reconciliation check instead of three.

One SABB-specific wrinkle. Because the rebrand happened in 2023, a client archive spanning several years will hold statements under two different identities — older SABB-branded documents and newer SAB ones — and the layouts are not necessarily identical. Treat the first file of each design as a new format and sample-check it, rather than assuming this year's file behaves like last year's.

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. No converter can read it until it is unlocked.

Gulf banks encrypt emailed statements so a leaked inbox does not hand over an account history, and they derive the password from details the customer already holds. The exact formula is stated in the covering email — take it from there rather than guessing. Common ingredients:

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

Once you can open the file, 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. 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 SAB Online, where the copy is often not encrypted at all.

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, 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 SABB 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, maps the date, description, debit/withdrawal, credit/deposit and balance columns — in Arabic or English — and converts Arabic-Indic numerals into values Excel can actually 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, whichever your accounting software wants.

Nothing is uploaded at any point. The parsing runs as JavaScript inside the browser tab you already have open — which you can prove in about fifteen seconds by turning your Wi-Fi off and converting anyway. For a practice bound by client confidentiality, that is a materially different proposition from a converter that posts the file to a backend and asks you to trust its retention policy.

Because SABB 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.

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 or a VAT return that will not tie out.

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 (SAR)	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
Decimal convention	SAR halalas land as .00, not as thousands	A misread separator can inflate a figure a hundredfold
Dates correct	Day and month not transposed	Wrong dates land transactions in the wrong VAT period

BayanSheet runs this reconciliation automatically after every conversion, checking the running balance row by row as well as the period totals, and marks anything that does not balance — down to a one-riyal difference. Failing rows are flagged rather than quietly exported. That is arithmetic, not a promise. A converter that simply hands you rows and tells you to review them carefully 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 VAT via ZATCA

For a VAT-registered business the bank statement is a core supporting document: it is where declared sales are matched against receipts, and where supplier payments tied to input VAT are traced.

📁 Ground rule: the Excel file is a working copy, not a replacement for the original record. ZATCA's VAT rules generally require records and supporting documents to be retained for at least six years from the end of the relevant tax period, with longer periods for capital assets and real property — and the original bank PDF remains the document of authority in an audit. Keep both: the PDF as the record, the spreadsheet as the tool. Confirm the period that applies to your own records with your tax adviser.

A layout that pays off later:

• Name files consistently: SABB_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 a tax-treatment column (standard-rated, zero-rated, exempt, out of scope) rather than editing the original narration.
• Do not delete non-VAT rows; keep them so the sheet still ties back to the statement.

The wider Saudi picture — which records matter, and how the statement feeds the return — is in bank statements, Excel and ZATCA VAT.

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 commonest CSV rejection), and keep debit and credit separate — if the software wants one signed amount column, derive it with a simple positive/negative formula.

• 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 Zoho reuses it 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 committing a whole year. If the mapping is wrong, you would much rather find out across 40 rows than 500.

Common mistakes

• Converting a mobile screenshot instead of the original PDF.
• Skipping the reconciliation check because the table "looks fine".
• Assuming an older SABB-branded statement and a newer SAB one share the same layout.
• Keeping only the Excel file and deleting the original PDF — a mistake that shows up in an audit.
• Editing original transaction data instead of adding new classification columns.

Conclusion

Converting a SABB 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 required, and credits you buy later never expire. If a SABB file does not come out clean, email a sample to support: I answer those myself and tune layouts by hand. For the wider Kingdom picture start at the Saudi Arabia converter hub, or browse the BayanSheet blog.