The questions a CFO asks first

Software your company subscribes to. You connect or upload your own receivables and payables accounts, and the engine returns risk analysis about your own financial accounts and your own counterparties: a score with its reasons, verified invoice status, payment behaviour, concentration, and what changed since last time. It supports a decision. It does not make one.

Two kinds of company. A corporate that sells or buys on credit and wants to read the risk in its own receivables and payables. And a financial institution that wants to read its own portfolio with the same discipline. Both get the same engine, each pointed at its own data.

A bureau report tells you what other financial institutions have reported about a company. The engine tells you what your own financial accounts say about how that company behaves with you: how it pays, how late, how concentrated your exposure is, and which way that is moving. Two different questions, two different answers. This is not a credit information company and not an official record of anyone's credit, and it does not try to be.

It sets no limit, takes no decision on your behalf, sells no assessment about any third party, and no money moves through it. It reads your own financial accounts and gives you the analysis with its reasons. The decision stays yours.

No, and by design. It never produces a credit limit, an approve-or-decline verdict, or a decision on your behalf. It gives you the score, the reasons, and the evidence behind them. Your credit committee, or you, decide on your own authority. For a financial institution that is not a disclaimer; it is the reason the engine can sit inside your process without taking its place.

Line by line. Every score opens at 60, which is neutral. Each reason on the list moves it up or down by a stated amount, and the final number is the sum of those moves. The explanation and the score are the same arithmetic, so they cannot disagree, and anyone on your team can check the sum by hand.

Differently, and on purpose. A government entity that pays late is a payment-timing fact, not a credit problem: the money arrives, on a cycle of its own. The engine reads that pattern as timing, and does not mark a government buyer down as if it were a private company at risk of not paying.

Your receivables and payables accounts: invoices, credit notes, payments and their dates, with the counterparty on each. Cleared ZATCA e-invoices add a verified status. That is the whole list. The engine needs no bank credentials, no access to your accounts, and no data about companies outside your own dealings.

Your data is held in databases inside Saudi Arabia. The engine holds no customer ledger today, and the first one has not been loaded. What this site itself stores — form submissions, accounts, and conversations with the site assistant — is all inside the Kingdom. The trust page says so plainly.

You, and the small number of people at Fkah who operate the service. Nobody else. Your financial accounts are analysed for you alone: they are not pooled with other customers' data, no score about another company is built from them, and nothing derived from them is sold or shown to anyone else.

Your customer list is the most sensitive thing in the financial accounts, and the rule is simple: it is yours and stays yours. It is never sold, never shared, never used to build a score for anyone but you, and never used to approach your customers. That is a constraint in how the engine is built, not a marketing line, and it is what makes handing over the financial accounts possible at all.

Expect it to be. Duplicate counterparties, inconsistent names, payments that match no invoice, dates in two calendars. The engine does not hide it: what it could not read shows as unknown rather than filled in with a guess, and the first thing you get back on a new set of financial accounts is a picture of how much of them the engine could read. Cleaning then becomes a conversation, not a prerequisite.

Where an invoice is a cleared ZATCA e-invoice, the engine checks the stamp and the hash chain. That proves two things: the document is authentic, and the seller's sequence is intact. It does not prove the invoice has not been presented elsewhere; nothing in the stamp carries that information, and we do not claim it does.

Yes. Your financial accounts are yours, an export is yours on request, and deletion at the end of the agreement is a term we put in writing before you sign. The retention periods for what the website itself collects are in the privacy notice.

A subscription, quoted in writing for your company before anything is signed. We publish no price list yet, because any figure here today would be invented.

It depends on the shape of your financial accounts, and the honest answer is that we have not measured it on enough real financial accounts to publish a number. An export file is the quick route; a live connection to an accounting or ERP system is scoped with you first.

Ask for a demo. The first session runs on sample data, so you see how a score reads before any of yours is involved. Running the engine on an extract of your own financial accounts is the second step, agreed in writing, under the same data boundary as a subscription.

A file is enough to start: an export from your accounting system in a spreadsheet format. A live connection is for when you want the analysis to refresh without anyone exporting anything. Neither route gives the engine access to your bank.

A Saudi limited liability company registered in Riyadh. Its commercial-register record, including the unified national number any counterparty can verify, is on the about page.

Through the complaints page. You get a reference number the moment you send it, an acknowledgement within two working days, and a stated deadline for an answer. The channel is open now, before the engine has customers, for anything about this site, your data, or a message you received from us.