Skip to content

Finance, insurance, professional services · Solution

Onboarding stalls for days chasing one missing document.

Soluvide builds onboarding and KYC document collection for UAE finance, insurance and professional-services firms. It asks each new customer for exactly the documents their profile needs, over WhatsApp or a secure link, reads the Emirates ID, passport and trade licence, checks they are complete and in date, chases what is missing, and hands your compliance officer a prepared file. The officer makes the decision; the data stays in your systems.

Message us on WhatsApp
  • Documents collected over WhatsApp or a secure link
  • Completeness and expiry checked before review
  • Your compliance officer makes every decision
  • Data stays in your own systems

The problem

The customer said yes. The file is still open.

What the day actually looks like — described as an operator would, not as a brochure.

A new client has agreed to go ahead. Now someone in your team sends a list of required documents by email, and the client replies over WhatsApp with a photo of the front of their Emirates ID, a passport scan from three renewals ago, and a promise to send the trade licence later. Nobody is quite sure which of those is current.

What follows is days of back and forth. The back of the ID is missing. The licence has expired and the renewed one is with the PRO. The MOA is a long scanned PDF and nobody knows which page shows the shareholders. Each chase is a separate message, from whoever remembers, in whichever channel the client last replied on.

Meanwhile the documents end up scattered across a relationship manager's phone, a shared inbox and a desktop folder — which is exactly where you don't want copies of identity documents sitting. When the compliance officer finally reviews the file, they find a gap and the cycle starts again.

The commercial cost is a client who agreed to buy and is now waiting to be allowed to. The compliance cost is a process nobody can reconstruct afterwards: what was asked for, when it arrived, who checked it, and where the copies went.

Why the obvious fixes fail

You've probably already tried these.

None of them are stupid. They fail because the work itself stays manual — they just move who does it.

An email checklist

Sending a PDF list of requirements puts the burden on the customer to work out which items apply to them, then to send them in one go. They rarely do. Your team is left checking each reply by eye and writing a fresh chase for every gap.

A generic e-form

Upload forms make the customer do the work but check nothing. They accept a blurred photo, an expired licence or the wrong page of a passport just as happily as the right one — so the problems surface later, at review, when the customer has stopped paying attention.

An off-the-shelf KYC platform

Full KYC suites are built for banks with dedicated compliance operations. For a brokerage, insurer or advisory firm they are often heavier and costlier than the problem, store your customers' data on someone else's platform, and still don't chase the customer on the channel they actually reply on.

What we build

Collect it, check it, chase it, and let your officer decide.

The honey step is where a person stays in control. Everything else is the typing and checking the system does for you.

  1. Checklist
  2. Collect
  3. Read + check
  4. Chase gaps
  5. Officer review
  6. File + reminders

Engineering decision. Automate the collecting and checking, never the decision. Reading an ID and noticing it has expired is mechanical; deciding whether a customer can be onboarded is a regulated judgement that belongs to your compliance officer. The system prepares the file, and screening stays with the tools and people already accountable for it.

  1. 1

    The right checklist

    When a customer is ready to onboard, the system works out which documents apply — an individual, a mainland company, a free-zone company, a particular product — and asks only for those, in Arabic or English, with a short note on what a good photo or scan looks like.

  2. 2

    Collection

    Customers send documents in the WhatsApp conversation they're already in, or through a secure upload link if your policy prefers it. Everything arrives in one place, tied to one customer record, instead of across phones, inboxes and desktop folders.

  3. 3

    Reading and checking

    Each document is read: name, ID number, nationality, dates of issue and expiry, licence number and activity, shareholders where the MOA shows them. The system checks the set is complete, legible, in date and consistent — the name on the passport matches the ID, the licence covers the company that is signing.

  4. 4

    Chasing what's missing

    Gaps get a specific, polite request: the back of the Emirates ID, the renewed licence, a clearer passport page. Reminders follow at intervals you set, on the same channel. If the customer asks something outside the checklist, the conversation goes to a person on your team.

  5. 5

    Compliance review

    Your compliance officer receives a prepared file: the documents, the extracted details, what was checked, and anything flagged for attention. Where you use a screening tool with an API, its result can be attached. The officer reviews and decides — approve, request more, or decline.

  6. 6

    Filing and expiry reminders

    The approved file is written to your CRM or document store with a record of what was requested, when it arrived and who reviewed it. When a stored Emirates ID or trade licence approaches expiry, the system asks the customer for the renewed copy before it becomes a problem.

Named systems, not “connects to anything.”

We confirm exactly which of your systems connect during scoping. The system commonly touches:

  • WhatsApp Cloud API
  • Secure upload portal
  • OCR
  • Arabic document parsing
  • Your CRM
  • SharePoint / Google Drive
  • Your screening tool's API

Engineering decisions

Clear lines, agreed up front.

What the fixed price covers, and the things we will not build. Both are written into the scope before we start.

In scope

  • A document checklist per customer type, in Arabic and English
  • Collecting documents over WhatsApp or a secure upload link
  • Reading Emirates ID, passport, visa and trade licence details
  • Checking completeness, legibility and expiry dates
  • Polite, specific chasing for what is missing
  • A prepared file for your compliance officer to review
  • Expiry reminders when a stored document is about to lapse

Not in scope

  • Approving or rejecting a customer — your officer decides
  • AML, sanctions or PEP screening — that stays with your tools
  • Verifying a document's authenticity with the issuing authority
  • Storing customer data on our servers

What you get

Live in weeks, quoted before we start.

Most onboarding systems go live in about three to five weeks. What moves it inside that range is how many customer types and checklists you run, which system the prepared file lands in, and how much review your compliance team wants before launch. No hourly billing, no surprises.

  1. 1Week 1

    We map the work, then quote it

    A short call, then we document how new customers get onboarded today, from the first document request to the compliance sign-off — including the exceptions and the workarounds people built around it. You get a written scope, acceptance criteria and a fixed price before any build begins.

    You get: Scope + fixed quote

  2. 2Weeks 2–5

    We build on the tools you already run

    WhatsApp Cloud API, Secure upload portal, OCR and the rest of your stack — no rip-and-replace. Outputs are structured and checked against your own data, not trusted blindly.

    You get: Working system on your stack

  3. 3Go-live

    Your team approves, then it runs

    The human step is tested with the people who will own it before anything goes out. Logging and alerts so problems surface early, documentation your team can read, and you own the code and the accounts.

    You get: Approval gate, monitoring, full ownership

Stop chasing documents one message at a time.

Tell us which customer types you onboard and what your compliance team needs to see. We reply within one business day, and the price is fixed after a free scoping conversation.

Questions compliance teams ask

Straight answers.

If yours isn't here, send it on WhatsApp and you will get a straight reply.

Prefer a form? Contact page

No. It collects the documents, reads them, checks they are complete, legible and in date, and prepares the file. Your compliance officer reviews that file and makes the onboarding decision. The system makes the officer's job faster; it never makes the decision for them.

WhatsApp us