Digital onboarding
for financial services

Customer onboarding software for banks and other lenders is the front door of a loan: the tool that takes a borrower from first interest to a submitted, verified application. It runs the calculator, collects the right data for a person or a company, checks identity and bank details, screens against your blacklist, and hands a complete file to origination. The application can start on a self-service portal, in your back office, through an agent, or inside your own checkout by API. HES LoanBox sits in this category, built for banks, credit unions, and alternative lenders that want one intake feeding every channel rather than a separate form for each.

Both create the same application; they differ in who starts it. In the borrower portal, the customer applies on their own, on desktop or mobile, moving through the calculator, data entry, and verification at their own pace. In the back office, one of your operators opens and fills the application with the customer, which suits call centers, branches, and anyone who would rather be walked through it. Because both feed one intake in HES LoanBox, the verification, scoring, and handoff to origination run the same way regardless of where the application began, so your pipeline stays consistent no matter the channel.

Identity and bank checks are a standard part of digital onboarding in banking, and both run inside the application. For identity, HES LoanBox connects to KYC providers such as Jumio or Ondato, which check documents and personal data automatically or with an operator in the loop. For bank details, open banking providers like Flinks, Plaid, or Illion let the applicant connect an account so the system confirms ownership and reads balances, instead of your team chasing statements by email. Alongside these, the contact and identity are screened against your blacklist. The result is that files reach your credit team already verified, which cuts fraud and manual review.

Yes, as finance client onboarding software, the platform collects individual or company applications from one intake. A deployment can be set up for individual borrowers, companies, or both, decided during implementation to match how you lend. Individual applications collect personal details; company applications collect business and director information along with KYB. Because the borrower type is configured to your lending model rather than left as a generic switch, the questions, documents, and checks each applicant sees fit the product they are applying for. This makes the same platform workable for consumer lenders, SME and commercial lenders, or a book that spans both.

Highly, and much of it without code. The fields, steps, and conditional logic of the form are configurable, so you decide what each applicant is asked and in what order. Products are set up in groups, each with its own amounts, terms, rates, and eligibility, and you can run as many as your market needs. The workflow behind the form, the stages an application passes through and how it routes, is drawn in a BPMN builder rather than hard-coded. For anything genuinely unique to your business, custom development is available, but a great deal is handled through configuration in HES LoanBox.

By removing the friction that makes people quit partway. An applicant can pause on one device and resume on another without losing what they entered, so a break does not mean starting over. Configurable SMS, email, and in-app reminders bring them back to finish a form or supply a missing document. Duplicate and stale starts are cleared automatically, keeping one active application per borrower and a clean queue for your team. After submitting, applicants follow progress in a read-only tracking view, which also cuts status calls. Together these keep more of the people who begin an application from abandoning it.

The services an intake depends on: KYC providers, open banking feeds, address lookup, credit bureaus, e-signature, and your core banking system. HES LoanBox ships with a set of prebuilt integrations and an open API, so where a provider is not already connected, your team can wire it in. That matters because onboarding is only as fast as the checks behind it; when identity, bank, and bureau data flow in automatically, applications reach a decision without manual lookups. The same open API lets an application start inside your own checkout or a partner app and still land in the platform for the same verification.