Automate customer onboarding KYC
Unstract reads each applicant's ID, proof of address, bank statement and formation documents, matches them to the application, and passes clean files to sanctions screening and your onboarding or KYC system.
Trusted by lending and onboarding teams around the globe
Applicants send photos and scans, not verified data
An applicant fills in the form in a few minutes. The passport photo, the utility bill and the bank statement then sit in a queue until an analyst opens each one, compares it with the application and keys it in.
An applicant waiting to fund the account while an analyst keys the form
A utility bill scanned crooked at the branch, the stamp over its date
A house number that differs between the application and the bill
Proof of address and a bank statement trailing the application by days
One owner listed twice on an ownership chart, so the shares pass 100%
Each file is read, compared with the application and keyed in by hand before screening starts, and the applicant waits to fund the account.
Unstract reads the ID, the proof of address and the formation documents as they arrive, matches them to the application, and sends clean files to screening. An analyst sees only the files that don't match.
From the application to sanctions screening, without the keying
Five steps, run on their own for every applicant. Parsing by LLMWhisperer, extraction by Document Studio, the whole run by Flow.
Pick up each application wherever it lands
Applications come in through your portal, by email or as a branch upload, with a photo ID, a proof of address and a bank statement. A business adds its articles of incorporation, a certificate of good standing and an ownership chart. Each upload is tied to the applicant it belongs to, one record per applicant.
The run starts when the application is submitted, not when an analyst reaches the queue.
Sort the branch scan into a bill and a statement
A branch often scans everything the applicant handed over into one PDF. The file is split into its documents and each one is classified (passport, driver's license, utility bill, bank statement, articles of incorporation, ownership chart) so the right fields come out of each.
A utility bill is read as proof of address and a statement as a statement, in whatever order the pages went through the scanner.
Read every ID and proof of address, then pull the fields that matter
LLMWhisperer reads each page as text with its layout kept, so a passport photographed on a desk or a bill scanned at an angle comes out cleanly. Document Studio then extracts the fields you defined: name, date of birth, document number and expiry, address, and for a business the entity name, registration number, officers and every owner above 25%.
The same field definitions run on a US passport, a UK driver's license and a Delaware filing alike.
Check every document against the application before screening
The ID is matched to the application on name and date of birth, the address to the proof of address, and a business to its certificate of good standing. Expired IDs, proof of address older than 90 days and owners that don't add up to 100% are flagged. A file that passes keeps moving. One that fails stops for a KYC analyst with the documents side by side.
Only the files with a mismatch or a missing owner wait for an analyst. Every other applicant keeps moving.
Pass the matched file to screening, your CRM and core banking
Matched files go to sanctions screening in LSEG World-Check One or LexisNexis Bridger Insight XG, to your CRM in Salesforce or HubSpot, and to core banking on Fiserv or FIS, with the documents attached. Every decision an analyst made is recorded against the applicant.
Screening starts on checked data, and the audit file for each customer builds itself as the run goes.
See it run on a week of your own applications.
Bring the IDs, utility bills and formation documents from one product line. We run them live and show every field, every match and every held applicant.
Everything an applicant sends for KYC verification
Documents
- Account applications
- Passports
- Driver's licenses and national ID cards
- Utility bills
- Bank statements
- Lease and rental agreements
- Articles of incorporation
- Certificates of good standing
- Ownership charts and beneficial owner forms
- Partnership agreements
- Tax registration documents
- Existing customer records from your CRM
Fields captured
Our agents are extroverts.
Cloud storage like S3, Google Drive, Dropbox and Box. Databases and warehouses like Snowflake, BigQuery, Postgres and SQL Server. Accounting, ERP and CRM systems like QuickBooks, Xero, SAP, NetSuite, Salesforce and HubSpot. Project trackers like Jira, Asana, ClickUp and Linear. And anything with an API.
Live on one product line first
Your team writes no code, and the old process keeps running until the new one has proved itself. Onboarding is built on your own applicant files and tested on one product line before it goes further.
Book a consultation
We go through a week of your onboarding files together: which documents applicants send, through which channels, and what an analyst checks before screening.
Built on your documents
The fields, the matching rules from your KYC policy and the hand-off to screening, CRM and core banking are set up on your own applications, IDs and formation documents.
Pilot on one product line, then roll out
Personal checking or small business accounts run live within days. When the numbers hold, the other products follow and the hold rules carry over.
Built for the teams that open accounts
Branch and online applications matched to their IDs and proof of address before an analyst opens them, and funded accounts sooner.
Know your customer checks that keep pace with app sign-ups, with phone photos of IDs read as cleanly as scans.
Every match, hold and analyst decision recorded against the customer, so an examiner can follow each file from the application to screening.
Account opening paperwork for individuals, trusts and entities read into your onboarding or KYC system, owners and signatories included.
Applicants screened in minutes, mismatches held at intake
Identity documents stay under your controls
An onboarding file holds a passport number, a date of birth, a home address and a bank account: enough to open an account in someone else's name. For a business it adds every owner's identity as well.
- Encrypted in transit and at rest.
- Applicant documents are never used to train models.
- Access by role, product line and document type, with every match, hold and analyst decision logged against the applicant.
- Retention you set, in line with your record-keeping policy for customer identification.
- Self-hosted deployment for banks whose controls keep identity data inside their own environment.
What onboarding and compliance teams ask first
Read each document with its layout kept, extract the same named fields from every version of it, and check those fields before they reach a system. LLMWhisperer reads passports, bills and statements as text, including phone photos and crooked scans. Document Studio turns them into one record per applicant: name, date of birth, ID number and expiry, address, and owners for a business.
They automate the document work that comes before screening. Unstract picks up each application, sorts the uploads, reads the fields, matches them across documents and passes clean files on. Analysts handle only the held files, and every step is logged for KYC compliance review.
Yes. A long file is split into its documents first: articles of incorporation, the certificate of good standing, the ownership chart, officer IDs and bank statements. Each is read for its own fields, and the owners above 25% are listed with their shares, which must add up to 100% before the file moves on.
Before it. Screening tools check a name against sanctions and watch lists, and they need that name, date of birth and address typed in correctly first. Unstract reads them off the documents, matches them to the application and sends the checked record to your screening tool, so it starts from verified data.
Passports, driver's licenses and national ID cards for identity; utility bills, bank statements and lease agreements for address; and for a business, articles of incorporation, certificates of good standing, partnership agreements and ownership charts. You can add other documents your policy accepts.
Yes, the rules come from your policy. A common setup flags proof of address older than 90 days, an expired ID, a name or date of birth that differs from the application, and owners that don't add up to 100%. You change a rule in one place and the next applicant runs on it.
The applicant stops for a KYC analyst on a screen that shows the application, the ID and the proof of address side by side, with the differing field marked. The analyst confirms the right value or asks the applicant for a new document, the decision is logged, and every other applicant keeps moving.
Sanctions screening in LSEG World-Check One or LexisNexis Bridger Insight XG, your CRM in Salesforce or HubSpot, and core banking on Fiserv or FIS. Flow sends the record and the documents as part of the run, so nothing is downloaded and typed again.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Applicant documents are encrypted in transit and at rest, never used to train models, and kept only as long as you choose. Self-hosted deployment keeps identity data inside your own environment; see the Trust Center.
Within days on one product line. In a consultation we set up the fields, your matching rules and the hand-off to your systems on your own applications. Nobody on your side writes code, and other products follow once the numbers hold.
Bring a week of onboarding files to the consultation
The applications, ID photos, utility bills and formation documents from one product line, the crooked branch scans included. You watch each applicant reach screening, and every held file shows why it stopped.