Plain-English steps
Lending operations staff write and read tests in banking language.
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.
Open the 'Loan' record '{{loan.name}}'
Select 'Credit Approval' from 'Stage'
Click the 'Save' button
Check that 'Approval status' shows 'Pending credit officer'
Check that the 'Covenants' tab lists 'Debt service coverage'
Lending operations staff write and read tests in banking language.
The desktop engine drives teller and servicing screens other tools can't see.
Steps, results, screenshots and a named sign-off in Quality View.
Salesforce's calendar you cannot move. nCino's package releases your bank schedules.
| Release | Timing | Can you defer? |
|---|---|---|
| Salesforce major releases (inherited) | Spring, Summer and Winter, with sandbox previews | No |
| Salesforce patches (inherited) | Weekly | No |
| nCino package releases | Scheduled by your bank | You choose when |
Typical cadence. Dates vary by instance and region; check your vendor's release calendar.
Compare all vendor calendarsPlatform and package change together, even when only one moved.
Certify the processes your examiners and customers care about.
Credit policy changes do not wait for a release. When the approval matrix changes, prove the right officer still gets the loan.
The loan is approved in nCino. The customer feels it in core banking and servicing.
The loan is approved and closed in nCino.
Core banking books it with the approved terms.
Servicing produces the first statement with the right payment.
Both. Run the same suite in the Salesforce preview sandbox and again before each package release.
It gives examiners a clear record of steps, results, screenshots and sign-off. Your compliance team decides what an exam needs.
Bring one lending process. We run it across nCino and core banking with you.