About
A Saudi technology company that builds a risk engine, and leaves the decision to you
Fkah builds the credit risk data engine: software a company connects to its own receivables and payables accounts to read the risk in its own financial accounts. Registered in Riyadh, and small.
The problem
A company sells on credit, and from that moment its money exists in someone else's hands. Whether it arrives, and when, is the question a finance team asks every month and answers mostly from memory.
The evidence is already in the financial accounts: who pays, how late, how concentrated the exposure is, what has been drifting. It is rarely read as evidence, because reading it by hand is slow and a credit bureau report answers a different question.
The same is true on the other side of the financial accounts. The payables accounts say as much about supplier dependence as the receivables accounts say about customer risk.
The thesis
Read the financial accounts the way an analyst would, every day, and show the working. A score without its reasons is an opinion; a score whose reasons add up to the number is evidence.
Keep each company's data to that company. The moment financial accounts are pooled, one company's customer list becomes someone else's product, and the trust that made the financial accounts available is gone.
Support the decision and never take it. The engine gives a finance team or a credit committee something to decide on. It does not set a limit, and it does not say yes or no.
What we are building
Receivables risk
Your customers, read from your own financial accounts: payment behaviour, concentration, verified invoice status, and what changed.
Payables risk
Your suppliers, read the same way: dependence, terms, and where a single failure would hurt.
Scores that show their working
Every score opens at 60, which is neutral, and each reason moves it. The final number is the sum. The explanation and the score cannot disagree.
Invoice verification
Reading a cleared e-invoice and checking its stamp and hash chain, which proves the document is authentic and the sequence intact, and nothing more than that.
Where we stand today
The engine is subscription software: it reads your own financial accounts, verifies your invoices, and gives every counterparty a score explained reason by reason.
Its boundaries are part of its design: it sets no limit, issues no decision, sells no assessment about any third party, and no money moves through it.
The company's register record is published further down this page, including the unified national number any counterparty can verify.
How we judge ourselves
Arabic first
Everything we publish is written in Arabic first and then translated, not the other way round.
No figure without a source
We publish no statistic, customer name, testimonial or certification before it exists and we may publish it.
Gaps are stated
What is not built yet appears on our pages in its true tense: planned, not live. Where data is held today is stated as it is, not as it is meant to be.
The decision stays yours
Nothing the engine produces is a verdict, a limit or a recommendation about a counterparty. That line is a product constraint, and it holds in every feature.
Company details
From the commercial register, as issued. Any counterparty can verify the unified national number independently.
- Registered legal name
- شركة فكة حلول (Sharikat Fkah Hulul)
- Trading name
- Fkah (فكّة)
- Legal form
- Company — limited liability company (LLC) — Single-person LLC
- Register type
- Main register
- Unified national number
- 7055054576
- Registered on
- August 23, 2026 (1448-03-10 AH)
- Registered address
- حي النفل الحسناء, Riyadh, Saudi Arabia
- Register status
- active
- Contact
- info@fkahtech.com
The register carries no English name. The Latin-script form shown beside the Arabic is a transliteration to help reading, not a registered name.
Team
We publish names with the written consent of the people concerned, and with no claim about performance or results. No names are published yet.
See it on sample data first
Request a demo and we walk through the engine on sample data. Running it on an extract of your own financial accounts is the second step, agreed in writing.