qventisqventis

Two release calendars
One certification examiners can read

nCino inherits three Salesforce releases a year on top of its own package releases. Lending teams certify each one in plain English, through to core banking.

  • Salesforce and package releases
  • Through to core banking
  • Evidence examiners can follow
Commercial loan reaches credit approvalnCino, 5 steps
  1. Open the 'Loan' record '{{loan.name}}'

  2. Select 'Credit Approval' from 'Stage'

  3. Click the 'Save' button

  4. Check that 'Approval status' shows 'Pending credit officer'

  5. Check that the 'Covenants' tab lists 'Debt service coverage'

Lending teams own certification

Plain-English steps

Lending operations staff write and read tests in banking language.

Core banking clients too

The desktop engine drives teller and servicing screens other tools can't see.

Evidence for examiners

Steps, results, screenshots and a named sign-off in Quality View.

Certify each nCino release

The nCino release rhythm

Salesforce's calendar you cannot move. nCino's package releases your bank schedules.

ReleaseTimingCan you defer?
Salesforce major releases (inherited)Spring, Summer and Winter, with sandbox previewsNo
Salesforce patches (inherited)WeeklyNo
nCino package releasesScheduled by your bankYou choose when

Typical cadence. Dates vary by instance and region; check your vendor's release calendar.

Compare all vendor calendars

Questions

Do we test for Salesforce or nCino releases?

Both. Run the same suite in the Salesforce preview sandbox and again before each package release.

Is the evidence enough for an exam?

It gives examiners a clear record of steps, results, screenshots and sign-off. Your compliance team decides what an exam needs.

See one loan certified into core banking

Bring one lending process. We run it across nCino and core banking with you.