Configuring products, roles and entity scope is quick. Migrating an existing portfolio is the part that depends on your records: a single entity with clean loan numbers moves faster than four entities whose borrower identities were never reconciled. The demo scopes the plan for your bank, and phased migration keeps your current system running throughout.
Implementation
Start with one workflow, then scale the platform.
Covenant Desk is built to your bank's operation and integrated with your systems. It begins with one workflow and expands into the lending core, repayment, borrower app, intake channels, the AI banking agent and group operations in phases.
What it involves
Implementation is mostly a records question, not a software one.
Installing the software is the short part. What actually determines how long a rollout runs is the state of the records you already hold: how many lending companies they sit under, how consistently borrowers are identified across them, whether loan numbers follow one format, and how much of the history lives in a spreadsheet somebody maintains by hand.
So the work is sequenced to answer that first. Discovery establishes what exists and who may see it. Data setup maps your source fields to the borrower record. A pilot runs one workflow end to end with real records and real staff, because that is the only honest test of whether the mapping was right. Only then does scope widen. Nothing has to cut over in a single step: phased migration lets your existing system and Covenant Desk run side by side while you move across at your own pace.
Tailored deployment
A deployment for one institution, not a tenant on a shared screen.
The engine stays the same; what surrounds it is yours. We configure the platform to your credit policy, documents, systems and regulator before your team sees it.
Credit policy and scorecard
Your thresholds, weights, hard stops and grade bands in a policy table with effective dates and an approval trail, changed by Credit Risk without a software release.
Authority and committee
Your delegated authority matrix by amount, risk grade and product, with credit committee routing and recorded votes.
Memo and letter templates
The credit memo in your format and the facility letter, guarantee and security documents from your legal wording, in English and Traditional Chinese.
Connected systems
Core banking (for example Finacle, Temenos or FLEXCUBE) through APIs or file exchange, credit bureau and commercial credit reference, HKMA CDI, iAM Smart, CorpID, single sign-on and your screening provider.
Hosting and data residency
A dedicated instance in the cloud region your regulator expects, or in your own data centre. Database, documents and backups stay in that region.
AI model of your choice
Use a model you already approve, one hosted in your region, or a private model on your own hardware through our partner Minima AI. The AI provider is chosen by your bank.
How an engagement runs
- 1Working session
Two hours on one of your files and your credit policy.
- 2Demo on your case
A fictional case shaped like your book, run through your stages.
- 3Pilot
Your policy loaded and your systems connected; an acceptance test by your credit team on fictional and anonymised cases.
- 4Production
Integrations, an independent penetration test before live data, then go-live.
Rollout path
From demo discovery to connected operation.
- 01
Discovery
Map lender entities, staff roles, source systems, borrower touchpoints, repayment workflows, approval handoffs, and reporting needs.
- 02
Data setup
Configure company units, user scope, source mapping, import files, FPS receiving IDs, activation flow, and demo-safe validation data.
- 03
Pilot
Enable the first workflow, validate dashboard, search, profile and notice behaviour, train staff, and confirm audit and permission rules.
- 04
Scale
Add entities, borrower self-service, the AI banking agent, WhatsApp and email channels, management exports, and advanced controls.
Before the demo
Prepare the operating facts that determine scope.
- 01
Companies
List each lending company, branch or unit structure, brand display needs, and which staff should see each company.
- 02
Source data
Identify source systems, Excel files, notice feeds, customer identifiers, loan number formats, and fields that must be trusted.
- 03
Workflows
Choose the first workflow: SME lending, Customer 360, repayment operations, borrower app, the AI banking agent, intake or management reporting.
- 04
Controls
Confirm user roles, approval authority, borrower consent points, phone and HKID visibility, audit expectations, and export needs.
Before you commit
What banks ask about rollout.
If yours is not here, ask it on the demo, and we will scope it with you.
One person who knows how the book is actually run, and one who can authorise decisions about roles and permissions. They are often the same person. Beyond that we need the operating facts listed above: your company structure, your source systems, the first workflow you want live, and who is allowed to see what.
It is normal, and it is best handled during mapping, before go-live. Duplicate borrower identities, inconsistent loan number formats and fields that were never trusted all surface during discovery, and the mapping records which fields are authoritative. You decide what is correct, because you are the one who stands behind it, and we build the cleaning rules to your decisions.
Yes, and most banks do at first. Records import into the Covenant Desk database and scheduled sync keeps them current, so both can operate during rollout. Cut-over happens on your schedule, in phases. Covenant Desk can run as your lending core or beside your existing core banking system through APIs or file exchange.
The pilot is the training. One workflow goes live with the people who will actually run it, using real records, and the questions that come out of that week are the ones worth answering. Staff who already work a loan book tend to need orientation on where things live rather than instruction on what the work is.
The one that currently costs the most staff time. For most banks that is SME lending (application, document collection, spreading and credit memo) or the repayment follow-up queue, because both replace work that is being done by hand today. The AI banking agent works across all of them.
Scope your rollout on a working session.
Bring one of your files and your credit policy. We map what goes first, what needs configuring and how long your records will take.
Book a personalised demo