The institution's method, inside the product.
The institution's Playbook within RSEEN governs source hierarchy, formulas, evidence requirements, exceptions and authority. It is not a separate software product.
RSEEN Core · the standalone entry product
The evidence and analysis product that starts beside your existing systems.
RSEEN Core is a complete client-facing product with its own interface. Credit teams use it to manage documents, evidence, spreading, conflicts, sufficiency and human review while the institution retains its system of record and credit decision.
Inside the RSEEN Core interface.
RSEEN Core interface · synthetic case
A complete working journey inside RSEEN Core
- 01Open the case
Create the case and organise eligible Arabic and English documents.
- 02Build the evidence
Link material facts to the document, page and excerpt that support them.
- 03Compute the analysis
Spread financials and calculate ratios using defined formulas.
- 04Keep conflict visible
Preserve competing values and sources until an authorised reviewer resolves them.
- 05Apply sufficiency
Withhold the grade when the institution's evidence condition is not met.
- 06Review and output
Record the authorised action and produce review-ready analysis.
The paid first scope produces a working baseline.
The Credit Control Blueprint produces a client-kept Playbook Specification and a real, versioned Initial RSEEN Core Configuration Baseline with validation results and known gaps. If a separate pilot proceeds, that baseline becomes its starting point after revalidation and agreed changes.
RSEEN OCT follows when broader workflow control is justified.
The same platform expands into queues, routing, committee workflow, conditions and handoff when the wider operating case is proven.
How it works, up close.
Three focused views of RSEEN Core behavior: the number with its evidence, the ratio with its formula, the analysis with its parts.
Illustrative · synthetic case
Every number opens to its source.
A material fact carries its reference — document, page, excerpt. The reviewer moves from the number to its page in one step.
Total revenue — FY2024 SR 98.4M
Source-linked Audited statements · p. 14 · "Revenue for the year totalled SR 98,412 thousand"
The ratio is computed — and the grade is shown.
The formula is named, every input is source-linked, and the result recomputes to the same value. The composite grade renders from the scorecard pillars.
DSCR = operating cash flow ÷ debt service
Operating cash flowSR 41.2M
Debt serviceSR 29.0M
1.42× Computed · formula v3
B+ Composite grade · 6 pillars
Analysis beyond the tables.
The analysis page assembles sector credit intelligence, SWOT, and the open diligence items — one file, committee-ready.
Sector intelligence
Building materials — stable demand, freight margin pressure
- SLong-term government contracts
- WCustomer concentration 41%
- OEastern Province expansion
- TInput-price volatility
Open diligence items
- Bank clearance confirmation letter
- Updated warehouse lease agreement
- Related-party disclosure
Where to start
Best first fit: document-heavy corporate credit.
RSEEN earns its place where teams collect, reconcile, spread and review Arabic and English evidence by hand—and the decision must stay attributable to authorised people.Best fit now
Corporate lending at Saudi finance companies, with multi-source files and repeatable credit review
Credit, risk and operations teams that need source references, controlled formulas and visible conflicts
Workflows that can start beside the existing system while authorised people remain in control
Engagement mechanics
- Credit Control Blueprint
- A paid, fixed-scope engagement — typically 4–8 weeks — that produces the client-kept Playbook Specification, a working, versioned Initial RSEEN Core Configuration Baseline, a Scope Gap Register and the next-scope decision.
- Separately scoped pilot
- Runs the agreed case set against clear measures and stop conditions.
- Activation and licence
- Activates RSEEN Core after the separate decision and approvals, then adds RSEEN OCT when the wider workflow case is proven.