- Market
- Saudi Arabia
- Written for
- CTO, COO
- Decision
- Integrate billing systems with the SADAD payment system
- Languages
- EN · AR
The whole surface
The systems a SADAD bill touches between issue and settled cash
A bill is not one message; it is a lifecycle that crosses your billing system, the payment rail, your bank and your ledger. The integration earns its keep at the boundary in the middle, where everything is matched.
A surface diagram: billing and ERP, customer payment channels and the biller’s bank feed into a single reconciliation boundary that matches notifications and settlement lines to bills and bank credits, producing reconciled receivables, a worked exception queue and finance reporting that closes.
Billing and ERP
Invoices and receivables originate here, and every presentable bill must trace back to exactly one of them.
Customer payment channels
Customers pay through their own banks’ channels; your systems learn of it through notifications, not through the customer.
Your bank
Settlement and the files that describe it arrive on the bank’s cadence and formats, agreed as part of biller onboarding.
What we do
The reconciliation boundary
One place where presentment is kept in step with billing, payment notifications post exactly once, settlement lines are matched to bills and bank credits, and anything that does not match becomes a case rather than a discrepancy.
Reconciled receivables
A ledger where paid means matched — to a bill, a notification and a bank credit.
A worked exception queue
Partials, duplicates and late arrivals each reach an owner with the context to resolve them.
Finance reporting that closes
A month-end that does not begin with an unexplained difference between collections and the ledger.
The rail moves the money; the boundary is what makes the money explainable.
The build, in order
How we take a biller from a first SADAD bill to a ledger that closes
The order matters: the lifecycle before the notifications, the notifications before the files, and the exceptions designed alongside all three rather than after them.
Model the bill lifecycle
Issue, amend, expire, pay — every state a bill can be in on the rail is mapped to a state your billing system owns, so the two can never quietly disagree about what a customer owes. One version of the truth about every bill.
Build the notification path
Payment notifications are applied to receivables promptly and idempotently — a repeat can never post twice, an out-of-order arrival cannot corrupt a balance, and a gap is detected rather than discovered. Receivables that update once, correctly, per payment.
Ingest and match the settlement files
Files arrive in the formats specified by the operator and your bank; every line is matched to a bill and to a bank credit, and the day does not end with lines nobody can place. Settlement explained line by line.
Give exceptions and refunds a home
Partial payments, duplicates, late notifications and refund cases each land in a queue with an owner and an audit trail, following the correction paths agreed with your bank — never a silent write-off. Exceptions that close with reasons, not with time.
The cost of carelessness
The unmatched payment is the real price of a careless SADAD build
A billing integration that only handles the happy path works impressively in the demo and degrades invisibly in production. The duplicate notification that posted twice, the settlement line nobody could place, the partial payment written off because investigating it was manual — each is small, and together they compound into a reconciliation debt: a standing unexplained difference between what the rail says was collected and what the ledger says is owed. By the time finance escalates it, the cheap moment to fix the design is months behind you.
The discipline that prevents it is unglamorous and precise: idempotency on every notification, a match key for every settlement line, and the rule that nothing unexplained is ever absorbed — it becomes a case with an owner or it blocks the close. That rule feels strict until the first audit, when the ability to explain every riyal that moved becomes the entire point of having built the integration properly.
Our role
What we engineer for SADAD billing and what your bank arranges
- 01
The integration, end to end
Presentment, notifications, settlement ingestion and reconciliation are built as one system with your billing and ledger, to the specifications the operator and your bank provide.
- 02
The matching, made total
Every payment and every settlement line either matches or becomes a case; the design leaves no third state where a difference can quietly live.
- 03
The operation, handed to your team
The exception queue, the monitoring and the runbooks are built for your finance and operations people to run without us, because a reconciliation only a vendor understands is a new dependency, not a solution.
Biller enrolment, credentials and commercial terms run between the operator, your bank and your organisation; we build to their specifications and prepare the technical side of that onboarding, so the integration is ready when the approvals are.
Common questions
What buyers ask
How do we become a SADAD biller — is that something you arrange?+
Enrolment is not ours to arrange, and it is worth being precise about why. Becoming a biller runs through your bank and the platform operator: the agreements, the credentials and the approval are granted to your organisation, not to a software supplier. Our part is the engineering on your side of that line — building the presentment, notification and reconciliation flows to the specifications you receive, preparing the technical material the onboarding asks for, and having the integration tested and ready so the commercial process, not the code, is the thing you are waiting on.
What does reconciling SADAD payments actually involve day to day?+
Three matches, run continuously. Payment notifications are matched to bills as they arrive, so receivables update the day the customer pays. Settlement files from your bank are matched line by line to those notifications and to the credits on your bank statement, so the money that arrived is tied to the bills it paid. And whatever fails any match — a partial amount, a duplicate, a line with no counterpart — lands in an exception queue where a person resolves it with an audit trail. Done well, the daily experience is a short queue and a close that balances; done poorly, it is a spreadsheet named “differences” that only grows.
Can refunds be automated in a SADAD integration?+
The workflow can be automated; the rules it follows are set by the arrangements between your organisation, your bank and the operator, and the honest design starts by confirming those rather than assuming them. What we build is the machinery around whatever path applies to you: the refund case opens against a specific matched payment, carries its approval chain, executes through the agreed channel, and closes only when the reversal is visible in reconciliation. What we do not do is promise a refund mechanism the rail’s arrangements for your case may not offer — that is exactly the kind of detail an integration must take from the operator’s specifications, not from a vendor’s optimism.
In this cluster
Next step
Map your billing flows
A mapping session that traces one bill from issue to settled cash across your systems and names where matching, exceptions and refunds will live.

