SHŌKEN FOR ORIGINATORS
For CFOs, funding and operations teams at mid-market originators. Organise the book, explain balance changes and prepare the evidence behind your next facility review.
Chapter 01 / Organise
Bring contract identifiers, balances, dates and servicing records into a consistent book. Scope a review by currency, status and facility while keeping the source reference close.
Source references within the review scope
A defined population is the starting point for the review.
See it in the productChapter 02 / Explain
The history retains payment observations, corrections and their reversals. Follow each change to its source record. A separate reconciliation preview illustrates comparison with customer-provided bank data.
Observations, corrections and reversals
A balance observation is not a confirmed bank reconciliation.
See it in the productChapter 03 / Evaluate
Apply the approved rule version to the facility population. Review each criterion’s result and reason. Missing source evidence and failed eligibility conditions remain different review questions.
Result tied to approved rules
An eligibility result tied to a population, date and rule version.
See it in the productChapter 04 / Prepare
Review the eligible base, terms and limits behind the capacity calculation. Check snapshot validity and keep funding evidence separate. The reporting preview brings together the cut-off date and open questions.
Calculation separate from completed funding
Capacity is a calculation to review, not completed funding.
See it in the productSimulated interfaces based on operator workflows. Reconciliation and reporting are conceptual previews. The model illustrates records and calculations, not bank transfers.
Simulated demonstration
Choose Atlas in the selector. Only contracts belonging to this facility will remain in the table.
Loan book scoped to Atlas
Select CT-0042 to inspect its type, dates, jurisdiction and servicing references.
CT-0042 record opened
The History tab connects related observations. Later events do not erase earlier ones.
Contract history visible
Open OBS-017. The servicer recorded a payment observation with a date and a source file.
Servicing observation expanded
OBS-018 corrects the reference on OBS-017. Their relationship preserves the explanation of the change.
Correction linked to the observation
OBS-019 reverses the correction, retaining its reason and its link to OBS-018. The full history remains available.
Reversal and reason identified
Inspect SRC-021 to connect the history with the supplied file. Servicing evidence does not confirm a bank payment.
Source record inspected
Simulated demonstration
The History tab connects related observations. Later events do not erase earlier ones.
Contract history visible
Open OBS-017. The servicer recorded a payment observation with a date and a source file.
Servicing observation expanded
OBS-018 corrects the reference on OBS-017. Their relationship preserves the explanation of the change.
Correction linked to the observation
OBS-019 reverses the correction, retaining its reason and its link to OBS-018. The full history remains available.
Reversal and reason identified
Inspect SRC-021 to connect the history with the supplied file. Servicing evidence does not confirm a bank payment.
Source record inspected
Simulated demonstration
Choose v3. The assessment retains this version of the rules, effective from 01 Sep 2026.
Version v3 selected
JUR-01 requires the contract country to be Spain. Inspect the condition before interpreting its result.
Contractual condition visible
Open country_code to see how the contract field relates to the criterion. A missing field requires review.
Field and source values visible
Each contract retains a result and its reason: eligible, excluded or awaiting data.
EVAL-009 matrix opened
Choose Excluded. The matrix narrows to the contract that does not meet the jurisdiction criterion.
Excluded result located
Open CT-0037. Its country is Portugal; the approved criterion requires Spain. The exclusion has an identifiable cause.
JUR-01 reason explained
Follow SRC-037 to the source field. The evidence for the data stays separate from the eligibility decision.
Source linked to the result
Simulated demonstration
Inspect EVAL-009. Capacity starts with a defined population assessed against rules v3.
Assessment population visible
Select Included in the base. CT-0042 is included; excluded CT-0037 and incomplete CT-0019 remain outside.
Borrowing-base scope identified
Open TERM-003. The eligible base is interpreted through the facility’s terms and restrictions.
Applicable terms opened
Review how the commitment, eligible base and restrictions relate. This view explains dependencies without monetary values.
Limits and dependencies expanded
Compare CAP-011 and CAP-012: cut-off date, rule version and input references. Validity depends on these inputs.
Snapshot references compared
Open the execution file. A capacity calculation does not establish a drawdown; supporting evidence remains outstanding here.
Execution evidence still pending
SHŌKEN / Explore the workflow
Organise contracts, explain changes and review rules, capacity and reconciliation. Follow the evidence through to preparing the facility report.
Simulated demonstration
Follow a contract from the loan book to its source record.
Preparing the interactive demonstration…
Simulated demonstration. No changes are sent to the platform.
Simulated demonstration
Choose Atlas in the selector. Only contracts belonging to this facility will remain in the table.
Loan book scoped to Atlas
Select CT-0042 to inspect its type, dates, jurisdiction and servicing references.
CT-0042 record opened
The History tab connects related observations. Later events do not erase earlier ones.
Contract history visible
Open OBS-017. The servicer recorded a payment observation with a date and a source file.
Servicing observation expanded
OBS-018 corrects the reference on OBS-017. Their relationship preserves the explanation of the change.
Correction linked to the observation
OBS-019 reverses the correction, retaining its reason and its link to OBS-018. The full history remains available.
Reversal and reason identified
Inspect SRC-021 to connect the history with the supplied file. Servicing evidence does not confirm a bank payment.
Source record inspected
Simulated demonstration
Choose v3. The assessment retains this version of the rules, effective from 01 Sep 2026.
Version v3 selected
JUR-01 requires the contract country to be Spain. Inspect the condition before interpreting its result.
Contractual condition visible
Open country_code to see how the contract field relates to the criterion. A missing field requires review.
Field and source values visible
Each contract retains a result and its reason: eligible, excluded or awaiting data.
EVAL-009 matrix opened
Choose Excluded. The matrix narrows to the contract that does not meet the jurisdiction criterion.
Excluded result located
Open CT-0037. Its country is Portugal; the approved criterion requires Spain. The exclusion has an identifiable cause.
JUR-01 reason explained
Follow SRC-037 to the source field. The evidence for the data stays separate from the eligibility decision.
Source linked to the result
Simulated demonstration
Inspect EVAL-009. Capacity starts with a defined population assessed against rules v3.
Assessment population visible
Select Included in the base. CT-0042 is included; excluded CT-0037 and incomplete CT-0019 remain outside.
Borrowing-base scope identified
Open TERM-003. The eligible base is interpreted through the facility’s terms and restrictions.
Applicable terms opened
Review how the commitment, eligible base and restrictions relate. This view explains dependencies without monetary values.
Limits and dependencies expanded
Compare CAP-011 and CAP-012: cut-off date, rule version and input references. Validity depends on these inputs.
Snapshot references compared
Open the execution file. A capacity calculation does not establish a drawdown; supporting evidence remains outstanding here.
Execution evidence still pending
Simulated demonstration
Conceptual view
Select Unmatched to find records that need an explanation. This reconciliation workflow is conceptual.
Inbox filtered by match status
Conceptual view
REC-014 connects contract CT-0042 with a servicing record and customer-provided bank data.
Exception opened for review
Conceptual view
Open SRV-032. It retains the contract reference, observation date and origin in the servicing file.
Servicing record visible
Conceptual view
Add BNK-018 to the comparison. Records align field by field; this demo has no bank connection or account access.
Sources aligned for comparison
Conceptual view
Inspect Reference: CT-0042 versus ATLAS-042. The date difference also needs context before the records can be linked.
Reference and date differences highlighted
Conceptual view
DOC-032 should explain how the references match. Without it, the review cannot be treated as resolved.
Supporting-document request identified
Conceptual view
You can edit the draft. Save adds the note to this demo’s history without sending information or closing the exception.
Simulated note added to history
Simulated demonstration
Conceptual view
Select September 2026. The cut-off date defines which sources enter this conceptual report preparation.
Review period selected
Conceptual view
Inspect the loan-book, rules and capacity references. Open exceptions stay within the review.
Scope and sources identified
Conceptual view
The draft brings Atlas context, references and open questions together. It does not represent an issued certificate.
Review document opened
Open the allocation annex. The screen changes to the calculation’s priority structure.
Waterfall structure visible
Expand the order: expenses, interest and principal. Precedence explains allocation review; it does not establish transfers.
Priority order expanded
Review each priority’s obligation and proposed allocation. Payment confirmation remains in a separate column.
Obligations and allocations distinguished
A source changed after the calculation. Validation requires recalculation with current evidence before proceeding.
Changed-source block explained
Review outstanding updated inputs and external payment support. This simulation executes no payments and issues no report.
Pending evidence identified
THE DETAILS
Checks against the source evidence available for a facility. It is distinct from eligibility under financing rules, does not guarantee legal title and is not an external audit. Source-verification workflows are presented as a preview.
Start with a representative loan tape, servicing records and supporting evidence. The documented import scope includes CSV, structured JSON and controlled single-sheet XLSX. Source mapping, availability and data quality determine the setup; specific integrations are agreed during scoping.
Shōken does not require bank account access for the workflows shown here. The reconciliation preview uses bank data supplied by the customer. Shōken is non-custodial: it does not hold funds or execute payments. Banking and payment arrangements remain with your existing providers.
The focus is mid-market asset-backed facilities involving loan books, receivables and asset finance. Suitability depends on the available records, contractual rules and operating model. Asset-class coverage is confirmed during scoping, without a minimum portfolio threshold.
Information and actions depend on role, tenant and facility permissions. The demonstrations use simulated interfaces based on operator workflows. They do not imply that every lender has a portfolio dashboard or access to every workflow.
Approved conditions and rule versions accompany the calculation they support. Review the effective version, inputs and date when assessing a result. A waterfall calculates allocations by priority; it does not execute a bank transfer or confirm payment.
Start with the relevant record, calculation date and supporting evidence. The reconciliation preview shows how an unmatched item can be investigated with its source context and a review responsibility. Missing evidence remains unresolved until it is explained; the illustration is not a completed customer reconciliation.
Access depends on the configured role, organisation and facility permissions. Read-only review packs and broader third-party reporting are presented as previews. Availability and the permitted information are agreed during scoping, rather than assumed for every participant.
A DEMONSTRATION WITH YOUR CONTEXT
Bring a representative loan tape and facility terms. We will follow your data from the contract record to eligibility, capacity and reporting preparation.
Online scheduling is not yet available. You can explore the guided demonstrations on this page.
Platform sign in