AR
Credit risk assessment for receivables
Where is your future money concentrated, and what is the risk in it? Who pays on time, whose lateness keeps growing, and how much of your ledger hangs on one name.
Decide on evidence, not instinct
The credit risk data engine
Financial data, properly read — so a default never arrives unannounced
Your invoices pile up, your customers multiply, and the picture stays unclear — you cannot tell where the exposure is building. The engine reads them invoice by invoice, gives every customer a risk score, and shows the factors behind it. Then the picture is whole, and your decision stands on solid ground.
What you see inside the platform
Your whole book, every side in its place
Five screens that do the reading for you: what you are owed, what you owe, a file on every customer and supplier, and ready reports in Arabic or English.
Illustrative figures on a sample company
What customers owe you, and where it is late
Your receivables aged from not yet due to over 420 days, and one look at how much of your money sits with your largest customers.
- Aging across nine buckets
- Each customer's share of your book
- A flag when lateness grows
Receivables aging
Share of book- Not due38%
- 1–3022%
- 31–6013%
- 61–909%
- 91–1206%
- 121–1805%
- 181–3603%
- 361–4202%
- Over 4202%
Largest customers
- Customer A18%
- Customer B11%
- Customer C7%
- Customer D5%
- Others59%
What you owe, to whom, and when
Your upcoming dues in order, the suppliers you lean on most, and how many of their invoices you paid on time.
- A clear schedule of dues
- Supplier concentration
- Your own payment discipline
One customer, the whole story
A score from 0 to 100 with a plain word, the reasons that pushed it up or down, and how their payments are trending.
- A 0–100 score with a word
- Each reason and what it did
- Payment trend over time
A supplier you rely on: where do things stand?
How much of your purchasing depends on them, what you owe them and how old it is, and what the engine found in their invoices.
- Their share of your purchasing
- Aging of what you owe them
- Findings from the invoice checks
Reports ready to share, in Arabic or English
Export the customer, supplier, sector or full book report as PDF or Excel, in the language your team needs.
- Four ready reports
- PDF or Excel
- Arabic or English
The engine at a glance
The buckets are labelled; no counts are shown
Scattered invoices
Invoices from different customers arrive apart, and give no clear picture.
Mudarhim gathers them
Mudarhim is the engine: it reads the invoices and the statement, matches the stamp, knows the one recorded twice, and works out how long each has run.
The buckets
The invoices settle into labelled buckets: the financially sound, the ones that need a look, and the ones documented and matched.
A clear view
Out comes a read for each customer: their invoices and how long they have run, the reasons behind the read, and what changed. The analysis supports the decision, and the decision stays with the reader.
An illustration. The customer names here are ours, written to show how the reading works — not Fkah's accounts, and not any customer's.
The method
How the engine reads your books, in four steps
From the moment you connect your accounts to the moment you see what changed — same order every time, across receivables and payables.
Connect your books
Connect your accounting system, or upload an Excel or CSV file. The engine reads every invoice — what customers owe you and what you owe suppliers. Not a sample, and not just your ten biggest.
Every invoice is checked
It checks the ZATCA stamp and the invoice sequence, and flags any invoice that looks like a duplicate inside your own books.
Each counterparty gets a score from 0 to 100
Every customer and supplier gets a score, a word that sums it up — like Sound or Needs attention — and the reasons behind it: how regularly they pay, how long you have dealt, and their share of your book.
You see what changed; your team decides
With every refresh you see who improved, who slipped and why, and every number traces back to its reasons.
The analysis is yours. The decision is your team's.
The score
A score you can read reason by reason
Every customer and supplier gets a score from 0 to 100, with one word that sums it up: Strong, Sound, Moderate, Weak or Needs attention. Under the score sit the reasons that pushed it up or down, so you know where it came from.
An illustration, not a real customer. A reason is read the same way wherever it appears, so two customers with the same finding get the same reading. The score is analysis that supports your decision — not a credit limit, and not a decision.
Score64/ 100Moderate
- Every invoice carries a valid ZATCA stampRaises it
- More than three years of dealing with youRaises it
- Late payments growing quarter on quarterLowers it
The file holds more reasons — this list is the short version.
The distinction
A government buyer is read differently
A government customer can settle well past the agreed terms. The question here is not whether the money arrives, but when.
Not every delay is high risk
Payment can run late without collection being at risk. A tool that cannot tell the two apart turns its own data from a decision aid into a reading that can walk you into the wrong call.
How the engine reads it
Government payment tracks the approval cycle, not ability to pay. The engine reads it through that reason and reports the government share of your ledger separately, so the timing shows up where it belongs — in the collection timeline, not in the collection odds.
The solutions
Two directions, one reading
The same reasons, the same score — once for what is owed to you, once for what you owe.
AP
Credit risk assessment for payables
The risk sits with your suppliers: who you depend on, how much you owe them, and what changes in your operation if one of them fails.
Who it is for
Two audiences, the same reading
One engine, two questions. A company that wants to know its own risks, and a financial institution that wants to know its client's risk before it decides.
For companies
Know your risk: a score for every counterparty in your ledger, with the reasons behind it, plus analysis that supports your decision and what follows from it — so you see where exposure concentrates by design, not by accident.
For financial institutions
Know your client's risk before you finance them: the engine reads your own portfolio and hands you the analysis and evidence a credit decision rests on — a verified document, readable payment behaviour, an explained score. The decision is yours.
What next
Want to know more?
Three pages cover the rest: what you subscribe to, how it connects to your systems, and who we work with.
- 01Packages
A package that fits
Four packages, by what you want read: receivables, payables, both, or both plus external assessments. - 02Integrations
Connects to your systems
Accounting systems like Dynamics 365, Odoo and Zoho Books, commercial registration data from the Ministry of Commerce through Wathq, or a simple file upload. - 03Coming soon
Partners
A programme we are setting up with licensed financial institutions. You choose whether to be introduced, and nothing of your data moves without your written consent.
Next step
Tell us about your financial accounts
Leave your details and we reply within two working days. No commitment, and you can stop the messages whenever you like.
Your data
- We work to SDAIA rules, and the trust page says exactly where the data sits today
- A published privacy notice covering what we collect and where it is held today
- Your ledger is analysed for you alone. We never pool client ledgers into one dataset, and we never build one company's score from another company's data.
Questions
Frequently asked questions
What is the credit risk data engine?
An engine that reads your receivables and payables accounts: it verifies every invoice, scores each counterparty, and shows where the score came from. The engine is software bought by subscription: it supports your decision and never takes it.
What is the difference between the receivables reading and the payables reading?
Receivables reads whoever owes you: your customers and how they pay. Payables reads whoever you owe: your suppliers and what you have committed to with them. Both directions use the same reasons and the same score.
How is this different from a credit bureau report?
The engine reads your own financial accounts: your invoices, your counterparties, and payment behaviour whose evidence you can see for yourself, line by line. A credit bureau report is a different thing, drawn from records that financial institutions share between them. The two answer different questions.