Solutions
One set of financial accounts, a different risk behind every name
The engine reads your receivables accounts, checks every invoice, then returns a score for each customer with the reason behind every point of it.
Definition
What it is
Receivables are what your customers owe you once you have delivered and issued the invoice. On the balance sheet they are one number. In reality they are dozens of separate relationships: a customer that pays on the date every time, a customer that runs late every time, and a government entity whose payment cycle is long by design. The engine takes that single number apart into names, and scores each name.
A score starts at 60, a neutral point that neither praises nor condemns. Every reason then moves it up or down: payment regularity, the ageing of the debt, how much of your financial accounts hangs on one name, and the soundness of the invoices themselves. The final number is the sum of those movements, so the explanation and the score are the same arithmetic — one of them cannot say something the other contradicts.
Government buyers are read differently, deliberately. An entity paying at 54 days is a payment-timing fact, not a credit event, and the engine keeps it out of the at-risk figure and shows it where it belongs, in the cash-flow reading. A tool that does not draw that line paints sound financial accounts red, and then asks you to explain the colour.
Mechanics
How it works
Who
The company
What
Connects its accounting system or uploads the receivables accounts with its ageing
When
At the start of the subscription, then on every refresh
Who
The engine
What
Matches each invoice against its cryptographic stamp and ZATCA hash chain, and marks what is duplicated or missing
When
Before any score is calculated
Who
The engine
What
Scores each customer from a starting 60 and records every reason that moved it, and by how much
When
In the same run
Who
The company
What
Reads the score and its reasons line by line, alongside concentration across the financial accounts and the at-risk figure
When
At any time, and on every refresh
The engine, step by step
A motion graphic of how the engine reads financial accounts
Six steps: the invoices arrive scattered with the account statement, the engine reads and orders all of them, and out come the ECL reports and the counterparties whose position is financially sound, alongside the regulatory standing and records, ending in analysis that supports your decision.
1/6Scattered invoices
Invoices from different customers arrive apart, with no clear picture of the financial accounts.
Step 1 of 6
An illustration. The counterparty names and figures here are examples we wrote to explain the reading, not the financial accounts of Fkah or of any client.
Who reads this assessment
Two readers, one output: a score explained reason by reason. What differs is the question each of them brought to the financial accounts.
Corporates
Know your risks: you get a risk rating on each of your customers, worked out on your financial accounts and on nothing else. It is a reading of what your own data says, there to support your commercial judgement rather than replace it: not an official rating, not a recognised register, and not a recommendation about what to do.
- A score per customer, with the reasons that built it
- An at-risk figure that deliberately excludes government payment timing
- Concentration in the financial accounts: how much of your revenue hangs on one name
- A history showing when a score moved, and on what reason
Financial institutions
Know your client's risk before financing: a financial institution subscribes to read its own portfolio — the clients on its own financial accounts, their invoices, and how payment behaves inside them. The engine supplies the analysis a credit decision rests on — the score and its reasons, the state of each invoice after checking, payment behaviour, concentration — and the decision stays with your credit committee alone. The engine decides nothing and sets no limit; it shows you what you are deciding on.
- A reading of your portfolio, not of anyone else's financial accounts
- The analysis a decision rests on: score and reasons, invoice state, payment behaviour, concentration
- The decision stays yours; the engine decides nothing and sets no limit
- No third-party data compiled, and no assessments about anyone sold
Fit
Who it suits
- Companies selling on terms and issuing ZATCA-cleared e-invoices
- Companies where a meaningful share of revenue sits with a small number of customers
- Companies supplying government entities that need timing separated from distress
- Financial institutions reading their own receivables accounts before a renewal or an expansion
Cost
What the subscription costs
An annual subscription, set by the size of the financial accounts, the number of users and the depth of the integration. It does not move with the result of a reading.
An annual subscription. What moves it is the size of the financial accounts, the number of people using it, and how deep the integration with your accounting system goes. Fkah's plans and their details are published on the pricing page at launch.
The pricing pageQuestions about this assessment
How is this different from a credit bureau report?
How do I know where a score came from?
My customer is a government entity paying at 54 days. Is that a danger?
What does an e-invoice stamp actually prove?
Next step
Register your interest in this assessment
Registering commits you to nothing and creates no contractual relationship. We reply as soon as subscriptions open.
The other end of the financial accounts