Five steps from your financial accounts to a score you can read

Illustrative figures, written to show how the reading works. Not Fkah's portfolio and not any client's.

1. 1

   Step 1

   Connect the financial accounts, or upload them

   You start from the receivables or payables accounts as they sit in your accounting system: a direct connection, or the ageing report uploaded as a file. The engine needs nothing beyond the fields every set of financial accounts already has: the counterparty and its commercial registration, the invoice number and amount, the issue and due dates, and the status. Your data is read for your account alone and never enters a shared dataset.

   Source of the financial accounts

   • Accounting system connection

     The engine reads the financial accounts from your system on a refresh schedule

   • File upload

     The ageing report as your system exports it, as a table

   Fields the engine reads

   • Counterparty and its commercial registration
   • Invoice number
   • Amount
   • Issue date
   • Due date
   • Status

   Invoices

   39

   Counterparties

   9

   Read in the illustrative financial accounts

2. 2

   Step 2

   Verify every invoice

   Before any score, every invoice passes a document check: does it carry a valid ZATCA stamp, is the hash chain intact, and does it match another invoice in the same financial accounts on amount, date and counterparty? An invoice that fails is not deleted; it is flagged, and the flag shows up in the counterparty's score.

   Invoice inv-bh-03

   Passed the check

   Bahr Al Khaleej Foodstuff

   Amount

   SAR 1,100,000

   Due

   September 18, 2026

   • ZATCA stampvalid
   • Hash chainintact
   • Duplicate in the financial accountsno match

   Invoice inv-ws-01

   Flagged

   Wasl Al Sarie Freight

   Amount

   SAR 600,000

   Due

   July 20, 2026

   • ZATCA stampmissing
   • Hash chainnot checked without a stamp
   • Duplicate in the financial accountsmatches another invoice

   What the stamp proves: the document is authentic and the seller's sequence intact. What it does not: that the invoice has not been presented elsewhere.

3. 3

   Step 3

   A score for each counterparty

   The engine reads each counterparty on its own: payment regularity, the ageing of the debt, its share of your financial accounts, the soundness of its invoices, its commercial registration. Then it gives it a score out of 100, with a band and a trend. The score is a reading of your data, not an official rating, and not an opinion on what you should do.

   Tamween Al Wusta Distribution

   Wholesale

   Score

   71out of 100

   Band

   Low risk

   Trend

   Stable

   Share of the financial accounts

   27%

   Reasons

   • More than three years of continuous dealing
   • Volume steady across four quarters
   • Every invoice carries a valid ZATCA stamp
   • The single largest share of the financial accounts

4. 4

   Step 4

   The explanation is the arithmetic

   A score opens at 60, a neutral point that neither praises nor condemns. Each reason then moves it up or down by a fixed weight, and the final number is the sum of those movements. So the explanation cannot say something the score contradicts: add the reasons and you get the number. On the same screen you see what pulled it up and what pulled it down.

   Rukn Al Bina Contracting

   High risk

   Opening reading60

   Each with its weight and sign

   • Days beyond terms widening quarter on quarter−22
   • Repeated part payments against single invoices−10
   • The contracting sector is under liquidity pressure−6
   • More than three years of continuous dealing+7
   • Commercial registration current, details match+6

   Sum35

   The weights above, added to the opening reading. The same number, from the same function.

5. 5

   Step 5

   Watch what changes

   The financial accounts move every day and the score moves with them. On every refresh the engine reads again and records what changed and why: days beyond terms widening, concentration growing on one name, an invoice with no stamp, a dispute left open. Alerts reach you ordered by weight, and the decision stays yours.

   Alerts, heaviest first

   1. HighRaised September 18, 2026

      Rukn Al Bina: settlement is widening quarter on quarter

      The last invoice it settled closed at 45 days past due. Every open invoice now sits further out than that, alongside repeated part payments against single invoices.

      Rukn Al Bina Contracting

   2. HighRaised September 16, 2026

      Wasl Al Sarie: invoices with no valid stamp

      The document itself is unconfirmed, so the reading on this counterparty is less certain than its number suggests.

      Wasl Al Sarie Freight

   3. MediumRaised September 15, 2026

      Tamween Al Wusta: the single largest share of the financial accounts

      The counterparty reads perfectly well on its own. What is worth looking at is the size of the share: one delay here moves the whole of the financial accounts.

      Tamween Al Wusta Distribution

• A late government payer is not a distressed one

  Government payment follows the budget cycle, not capacity. So the engine reads a government delay as a timing fact, keeps it out of the at-risk figure, and shows it where it belongs: in the cash-flow reading.

• The stamp proves the document, not its history

  The stamp and the hash chain prove the document is authentic and the seller's sequence intact. They do not prove the invoice has not been presented elsewhere, and we say so.

• No decision, no limit

  The engine gives you the score and its reasons, the state of each invoice, the concentration and what changed. It suggests no percentage, sets no credit limit, and neither approves nor declines. The decision is yours, on your own authority.

• Not a credit bureau

  The engine reads your financial accounts and nothing else. It compiles no payment behaviour on third parties, sells no assessments about anyone, and is not a source of records financial institutions share across the market. A credit information report answers a different question, and the comparison page sets out the difference.

• A reading, not a prophecy

  The engine reads, measures and warns. It cannot stop anyone paying late, and it does not know in advance who will default. What it does is show you what is in your financial accounts before it reaches you as a late payment.