A custom build on the platform
When the borrower is a company, almost every screen changes.
A personal loan file is one person with one identity document. An SME file is an entity with directors, shareholders, a business registration, accounts, and guarantees from people who are themselves borrowers somewhere else.
CD Business Lending is built on the Covenant Desk platform for entity borrowers: a company as the subject of the record, directors and guarantors attached to it, and exposure measured across both. This is built on the Covenant Desk platform rather than switched on. It needs engineering that an unsecured personal-loan data model does not contain, so it is scoped, quoted and agreed before any work starts.
The page opens on the company, not a person: registration details, structure, the directors and guarantors attached to it, the facilities outstanding, and the exposure those people carry with you personally.
Each stage below runs on the Covenant Desk platform. The result and the evidence behind it stay attached to the borrower and the loan.
Business registration number, company number, incorporation details and structure sit at the centre of the file, with the people attached to it rather than the other way round.
Each carries their own identity evidence, their own screening result and their own consent, because each of them is a natural person with rights under the PDPO regardless of whose loan it is.
Sanctions and PEP screening covers the company and the people behind it. Potential matches queue for a named staff member to clear or escalate, exactly as they do on a personal file.
Turnover, accounts, sector, tenor, security — the rules and scorecards are yours to write. The platform assembles the context and routes exceptions to the authority you set.
A director who guarantees a company facility and holds a personal loan with you is one exposure, not two unrelated files. Cross-company visibility is permission-scoped and audit-logged.
AI Copilot answers plain-language questions about your own portfolio with links back to the underlying records. AI Credit Analyst summarises a file and cites where each figure came from. Document processing reads what the borrower sent into fields your staff confirm, and email and WhatsApp intake turn enquiries into structured leads.
None of it approves anything. Every output is decision support attributed to the staff member who accepted it, and no loan is approved without a named person signing off. That boundary is the same on this product as on every other.
These are the platform plans this product line runs on. The build itself is scoped and quoted separately before any work starts, so there is no checkout button on this page — book a scoping call and we will price it against your book.
入門版
成長版
集團版
Bring your own book to the demo and we will work through it against these questions rather than a slide.
預約示範Built for you. An entity borrower is not a configuration of a personal-loan record — it changes the subject of the file and therefore most screens that assume an HKID. Covenant Desk builds custom financial operations systems, and this is one of them, scoped and priced before any work starts.
No. The Registrar's guidelines state that Licensing Condition 15 applies to the granting of unsecured personal loans only. Conditions 1 to 5 and 13 still apply to any agreement for loan, so third-party disclosure, the fee prohibition, the explanation of terms and referee consent all follow you into corporate lending.
That is the usual shape. The same workspace, the same permissions model and the same audit trail, with company records and personal records as different subjects. A person who appears in both is one identity for exposure purposes.
