SME lending operations

Control the exception journey without replacing the LOS.

Clarivy coordinates application signals, KYB documents, credit-policy exceptions, requests for information and accountable human review. The institution’s loan origination system remains the authority for credit approval and the loan lifecycle.

Recommended system boundary

Use Clarivy as the governed decision-operations layer around the LOS. Clarivy prepares and explains a review; the LOS continues to own credit decisions, offers, contracts, disbursement, servicing, accounting and collections.

Non-STP exception review

  1. 1

    Application event received

    Lending Middleware opens a case with a stable application reference, stage, product, Nucleus policy result and idempotency key.

    Output: Authorized case

  2. 2

    Customer and KYB context linked

    Clarivy links approved merchant, beneficial-owner, screening, consent and document references without becoming the merchant master.

    Output: Case context

  3. 3

    Exception classified

    Deterministic controls classify knockout failures, STP disqualifiers, missing documents, inconsistencies and items requiring manual review.

    Output: Review plan

  4. 4

    Controlled agents assist

    Specialist agents extract cited fields, compare records, identify contradictions, explain the policy gap and draft the request for information.

    Output: Source-backed proposals

  5. 5

    Missing information requested

    An approved template sends a precise RFI through a secure upload link with bounded reminders and clear stop conditions.

    Output: Tracked RFI cycle

  6. 6

    Maker-checker review completed

    Named reviewers resolve alerts and exceptions, record a reason and approve the structured disposition returned to the lending platform.

    Output: Human-owned disposition

  7. 7

    Decision record preserved

    Clarivy preserves the application snapshot, policy version, inputs, model runs, document reviews, exceptions, actors and callbacks.

    Output: Reconstructable case packet

Sales-assisted application journey

  1. 1

    Referral captured

    Sales records the merchant, requested product or facility, expected amount, source channel and named owner.

    Output: Owned opportunity

  2. 2

    Qualification completed

    The team confirms product fit and the minimum information required to open the authorized lending application.

    Output: Qualified application

  3. 3

    Application readiness tracked

    Clarivy coordinates KYB documents, missing information, merchant requests and reminders against the same application reference.

    Output: Complete intake

  4. 4

    Operations handoff prepared

    Lending Operations validates completeness and submission readiness before the bounded payload is sent to Lending Middleware.

    Output: Submission-ready case

  5. 5

    Exceptions reviewed

    Non-STP risk or compliance exceptions go to named reviewers with the policy version, reason code and relevant documents.

    Output: Controlled disposition

  6. 6

    Safe status returned to Sales

    Sales sees readiness, next action, owner and the approved disposition without receiving protected screening details or risk rationale.

    Output: Role-safe follow-up

Role-safe workspace views

WorkspacePrimary userVisible purpose
Sales pipelineRelationship manager or sales operationsReferrals, product requests, ownership and next action.
Application readinessSales and lending operationsMinimum data, KYB documents and merchant follow-up.
Operations queueLending operationsCompleteness, data quality and Lending Middleware submission readiness.
Risk reviewRisk analystNon-STP risk exceptions, reason codes and reviewer disposition.
Compliance reviewCompliance analyst or MLRO delegateKYB, sanctions, PEP and AML/CFT issues within authorized scope.
Decision handoffAuthorized users and source systemsReviewed outcome and the allowed next step.

Responsibility by system

CapabilityClarivyLoan origination system
Application and stageReceives a bounded snapshot from Lending Middleware and keeps operational review state.Owns the authoritative application and lending stage.
Credit policy and scorePreserves the evaluated policy, reason codes and exceptions for review.Owns approved credit rules, scorecards and final credit authority.
KYB and screeningLinks provider results, resolves gaps and records analyst disposition.Consumes the approved outcome according to institutional policy.
Document requestsCreates targeted RFIs, secure upload routes, reminders and review tasks.Receives the resulting completion or exception status.
Human reviewProvides the queue, maker-checker controls, rationale and audit lineage.Advances or declines the application through an authorized action.
Offer and servicingNo authority.Owns offer generation, contracts, disbursement, repayment and servicing.

Common exception types

ExceptionClarivy actionRequired human control
Knockout or policy rule failedShow the exact rule result, input facts, policy version and required follow-up.Reviewer determines whether the case may proceed, needs an exception or must return to the LOS.
STP disqualifier presentRoute the application to the correct queue with the triggering reason and relevant documents.Analyst resolves the disqualifier; the authorized approver owns the outcome.
KYB document missing, stale or unreadableRequest only the unresolved document and continue the same application.Reviewer verifies authenticity, relevance and expiry.
AECB consent or result unavailableHold the affected control and preserve consent/result status without inferring creditworthiness.Authorized lending staff decide the next permitted action.
Bank-statement analysis requires reviewLink the provider output, extracted features and source statements; keep conflicts visible.Credit or risk reviewer accepts, challenges or rejects the analysis.
Application and merchant record conflictCompare the named fields and route a targeted correction or document request.Reviewer determines the authoritative value and records the reason.

Governed AI and ML controls

ControlRequired behaviour
Bounded contextAgents can access only the authorized tenant, case, policy version and attached source references.
Source citationsEvery material model statement identifies the document or provider result that supports it.
Model inventoryRecord model, deployment, purpose, risk tier, owner, prompt version and approved use.
ValidationEvaluate extraction, contradiction, classification and summary tasks on approved test sets before release.
Human oversightNo agent approves credit, rejects an applicant, overrides policy or files an STR/SAR.
MonitoringTrack acceptance, rejection, unsupported-claim, drift, latency and exception rates by model version.

Pilot success measures

Measure review preparation time, analyst handling time, RFI cycles, applications returned for missing documents, exception ageing, policy overrides and the time required to reconstruct a completed review. Do not treat the number of AI outputs as a success metric.

Continue reading

Connect the lending ecosystem

Configure the LOS, KYB, screening, risk, document and communication integration boundaries.