Vehicle leasing and fleet customers

The problem

Lease applications mix individual and company customers, each with their own documents, and the questions are re-sent by email for every application.

What can happen

• Company applications stall while the right person is found to supply documents.
• Individual and company files are inconsistent.
• Documents are scattered across inboxes.

A better process

Build two workflows, one for individual customers and one for company customers, and save each as a Workspace template. Each application then starts from the right one.

How UMNIII Verify helps

UMNIII Verify lets the leasing team write its own questions once, attach them to two saved workflows, and add identity or company verification only for the customers who need it.

Which Verify features help?

Custom information forms

Your own questions: customer details, the vehicle and term, and the affordability or business-purpose questions your company sets.
Establishes: A structured record of what the recipient told you, filed against the request.
Does not establish: An answer is not independently verified because it was collected through Verify. It is what the recipient said.

Document requests and uploads

Supporting documents for individuals, and company documents for company customers.
Establishes: That the recipient uploaded these files against this request, and when.
Does not establish: An upload does not establish that a document is genuine, valid, current or the recipient’s own.

Identity verification

Optional: verifies an individual customer, or the authorised contact of a company.
Establishes: That a government-issued photo ID was checked for authenticity and matched to a live selfie of the person presenting it.
Does not establish: It does not establish an address, a right to work or rent, creditworthiness, a driving entitlement, or anything about a company.

Business verification (KYB)

Optional: verifies a company customer and its associated people.
Establishes: A company check: a registry lookup where records are available, company documents, and checks on the company’s associated people, its officers and beneficial owners.
Does not establish: It is not a credit check, and it does not decide whether to do business with the company.

Standard AML screening

Optional: where your policy screens customers.
Establishes: Whether the person appears on sanctions lists or politically exposed person (PEP) databases at the time of screening.
Does not establish: It does not include adverse media, and a result is information for your own decision rather than a decision.

Optional, added separately

• Identity verification: For an individual customer, or a company’s authorised contact.
• Business verification (KYB): For a company customer that must be verified.
• Standard AML screening: Where your policy requires sanctions and PEP screening.

Information that may be collected

• Individual or company customer details
• The authorised contact, for a company
• The vehicle or vehicles and the lease term
• Your own affordability or business-purpose questions

Documents that may be requested

• Supporting documents for an individual, as you request
• Company documents, for a company customer

What Verify does not do here

• Verify does not assess affordability or credit, and does not decide whether to lease to a customer. Answers are what the customer stated.

How to create or adapt the workflow

1. Create your individual and company forms under Custom Forms in UMNIII Verify.
2. In UMNIII Verify, open the Dashboard. The request composer is headed “Send verification invite”. Leave “Start from a template” on “Compose from scratch”.
3. Tick “Collect information (forms)” and choose the forms to send: the forms UMNIII provides, or your own under “Your forms”.
4. Tick “Request documents”, choose each document, write its instructions, and mark it optional where the recipient may not have it.
5. Add any optional check only where it genuinely fits your process. None is added by default.
6. Save each composition as its own template, then send from the one that fits the customer.

Create a reusable information form

• Owners, admins and members create forms under Custom Forms in UMNIII Verify: a name, then each question with its type, whether an answer is required, and any help text.
• Preview the form as the recipient will see it, save it, and it is offered under “Your forms” whenever a request is composed.
• One form can be attached to any number of requests and templates. Editing it changes future requests only; a request already sent keeps the questions it was sent with.

Read the full guide to creating a reusable form

Save and reuse it as a template

• Once the composition is right, an owner, admin or member of the Workspace presses “Save as template”, gives it a name and, optionally, a description.
• From then on it appears in “Start from a template” beside the UMNIII templates. Choosing it fills in the request, every part stays editable for that one request, and choosing a template sends nothing on its own.
• To adapt a UMNIII template, choose it and press “Copy to this Workspace”. The copy is yours to change; the original is unchanged.
• A saved template is not edited in place. To change one, apply it, adjust the composition and save it again under a new name.
• Your Workspace’s own and copied templates are listed under Other / General in the credit calculator inside UMNIII Verify.

Templates, forms and guides

UMNIII system template

A ready-made workflow that UMNIII provides. It is labelled UMNIII in the product, and your Workspace cannot change it.

Workspace template

A workflow someone in your Workspace has saved for reuse. It belongs to your Workspace.

Copied template

A UMNIII template copied into your Workspace so it can be adapted. The copy is yours and the original is unchanged.

Reusable information form

A set of questions your Workspace writes once and attaches to any request or template.

Workflow guide

An explanation like these pages. A guide is not a template: unless it says a UMNIII template is available, it describes a setup you build yourself.

Next step

Build this setup in UMNIII Verify and save it as your own template. Current prices are shown in the product before you send anything.

Related guides

• Vehicle sales and reservations

  Collect a buyer’s details, the vehicle and reservation, and the documents your dealership asks for, without a check unless you add one.

• Create a reusable information form

  Write your questions once in Custom Forms, then attach the form to any request or template.

• Build and save a reusable verification workflow

  Design a process once, with forms, documents and checks, save it as a Workspace template, and send it the same way every time.