SADAD
SADAD is how a great many bills get paid in the Kingdom. The questions it generates are about one thing: has the payment landed, and why has it not been reflected yet.
SADAD is how a great many bills get paid in the Kingdom. The questions it generates are about one thing: has the payment landed, and why has it not been reflected yet.
What SADAD payment data is, and where Elbi reads it
SADAD is the national payment system used for bill payment and government charges. For any organisation billing through it, the resulting contact is dominated by payment confirmation — customers who have paid and whose account does not yet show it.
That gap between payment and reflection is where most of the frustration sits, and it is entirely answerable if the payment record can be checked.
The assistant does not query SADAD itself. As a biller, you send bill information to SADAD under your biller number and receive a notification for each payment made against it; your billing system then posts that payment to the customer's account. Those records — bills issued, payments notified, payments posted — are what this connection reads.
- Payment status — whether a payment against a bill has been received.
- Bill references — the identifiers linking a payment to an account.
- Timing — when a payment was made and when it settles.
- Amounts — what was paid against what was due.
- History — previous payments against an account.
SADAD questions Elbi can answer for billers
Have you received my payment?
The single most common question, answered from the payment record.
Why is my account not updated?
Timing between payment and reflection, explained honestly.
What is my bill reference?
The identifier needed to pay, which is a frequent blocker.
How much is outstanding?
Balance against what has been paid.
When will it clear?
Settlement timing, which sets expectations rather than inviting a chase.
Did my payment go to the right account?
Reference matching, which resolves misapplied payments.
How a SADAD payment check works
- The payer is identifiedThrough your own sign-in or the verification you already use on the phone. Until then, the assistant can explain how SADAD payment works, but it does not read an account.
- The right bill is foundThe customer's account or subscription number leads to the bills issued against it, each with its SADAD bill number, amount and due date, exactly as your billing system holds them.
- Notified and posted are kept apartIf your system records SADAD's payment notification separately from posting it to the account, the assistant can tell the two apart: "we have received your payment; it will show on your account once it is posted". That sentence is the answer most anxious payers need.
- Mismatches are recognisedA payment that arrived against a different account number, or for a different amount than the bill, is identified from the records and passed to staff to correct, instead of leaving the customer to argue that they paid.
- How to pay, not payingWhen a bill is still open, the assistant gives the customer your biller number and their bill number and explains that payment is made through their own bank's app, online banking or ATM. It never takes a payment itself.
- Disputes go to your teamCharges the customer disagrees with, penalties and payment arrangements are decisions for staff, and are handed over with the bill and payment references already gathered.
Scope and control for SADAD billing data
| Source of the data | Your own billing or receivables system, where SADAD bills and payment notifications are recorded. The assistant has no access to SADAD or to a customer's bank. |
|---|---|
| Direction of access | Read-only: bills, amounts due, due dates, payment notifications and postings. It does not issue bills, change amounts or post payments. |
| Who can see what | A verified customer sees their own bills and payments. Staff using the assistant internally see what their role allows. A bill number on its own unlocks nothing. |
| Credentials | Read-only credentials to your billing system, or to a reporting view built for the purpose, issued by you and revocable by you without our involvement. |
| Retention | Account details read during a conversation are not kept: message content is destroyed within 24 hours, usually when the conversation ends, and no external AI service sees it. |
| Audit | Lookups can be logged by account, time and conversation, which is useful when a payment dispute is reviewed later. |
| If billing is unavailable | The assistant says it cannot confirm the payment right now and offers a person. It never confirms receipt it has not read. |
What this replaces
Payment confirmation is a category of contact that is almost entirely avoidable and almost never avoided. A customer pays, the account does not reflect it immediately, and they contact you — often repeatedly, and often while annoyed.
An assistant that can confirm receipt and explain settlement timing removes that contact almost entirely, and removes it at the moment of anxiety rather than the next working day.
The second effect is on misapplied payments. A meaningful share of payment queries are references entered incorrectly, and identifying that quickly turns a dispute into a correction.
Billers that field SADAD questions
Utilities
Payment confirmation at very high volume.
Telecom
Bill payment and reflection timing.
Government charges
Fee payment against applications.
Education
Fee payment confirmation during enrolment periods.
Getting value from SADAD payment records
Payment confirmation comes first, and its timing is predictable: questions cluster after bills are issued and again around due dates. A connection that can answer "have you received my payment?" at those peaks is doing its most useful work, and its effect is easy to see.
The bill-reference question is second. A customer who wants to pay but has lost the bill needs your biller number and their bill number, and at present has to call to get them. Once they are identified, that is a one-line answer.
Outstanding balance and payment history complete the set: what is due, by when, and what has been paid against it. These are the questions that decide whether a customer pays on time, and they are answered from the same records.
What connecting SADAD billing involves
- Locate the SADAD recordsFind where payment notifications land and where they are posted — billing platform, ERP or receivables system — and whether the two steps are recorded separately.
- Settle identificationDecide how a customer proves the account is theirs before anything is read: sign-in, a verification you already use, or both.
- Issue read-only accessYour team creates credentials, or a reporting view, limited to bills and payments for the accounts in scope. You hold them and can revoke them.
- Write the timing wordingAgree how the assistant explains the gap between a payment at the bank and the posting on your side, in your own published terms rather than an estimate.
- Test the awkward paymentsPaid to the wrong account, paid twice, paid in part where your bills allow it, paid after the due date. Each is checked against real records before launch.
- Launch before a billing cycleGo live shortly before bills are issued so the first peak is handled by the assistant, with staff watching the answers.
Governing billing data under PDPL
A bill and its payment history say a good deal about a person: what services they use, what they owe, whether they pay late. Under the Saudi Personal Data Protection Law that is personal data, and for government charges it can be sensitive in its own right. The assistant reads one customer's bills in answer to that customer's question, and nothing broader.
The trap specific to SADAD is treating the bill number as proof of identity. It is printed on paper bills, shared within households and passed to whoever pays on someone's behalf. It is fine for finding a bill once the person is identified; it is not a reason to disclose amounts or history to whoever quotes it.
How billers answer SADAD questions today
Most billers rely on a call centre or branch staff who search the billing system by account number, often supported by an automated phone line for balances. Many also send an SMS once a payment is posted, which prevents a share of calls on its own. The customer's bank app, meanwhile, keeps its own record of the SADAD payment, which customers can use as proof while posting catches up.
Each of those helps, and none answers the question that actually arrives: I paid, your system does not show it, what is happening? That needs the biller's own record, read at the moment of the question.
Where connected assistants go wrong here is overconfidence. Confirming a payment the records do not yet show, or promising a posting time the billing process does not keep, turns a routine question into a complaint.
What billers see with SADAD records connected
Common questions
Where the payment record is connected and the customer is identified.
No. It explains how to pay and confirms receipt. Taking payment is a separate process with its own controls.
It can identify a reference mismatch, which converts a dispute into a correction.
No. It reads your own billing records, where SADAD bills and payment notifications are stored, using credentials you issue and can revoke at any time.
Yes, once they are identified, together with your biller number, so they can pay through their bank. Before identification it explains where the number appears on a bill.
The pattern is the same wherever the entity's own records show the SADAD payment. Which fees are in scope, and what may be disclosed about them, is decided by the entity.
Connect your SADAD billing to Elbi
Payment confirmation, bill references and balances from your own billing records, in Arabic and English.