Use caseBusiness banking
Novalis Logistics wants three accounts and twelve cards. Of its eight documents, two disagree. Finding which two used to take a week.
The documents are checked against each other on arrivalBoth gaps go to the customer in one messageThe compliance officer decides, with the file in front of her
Name, capital and registered office match across the documents. But the holding's articles name a shareholder the declaration leaves out: Julie Hartley.
source · 8 documents on the case fileTwo points need the customer · the AI names both, with their pages
Julie Hartley owns 30 percent of Novalis Logistics through a holding, and the declaration on file never mentions her. The board resolution carries one signature where article 17 asks for two. Today an analyst finds both in week two, laying papers side by side, and the CFO gets a second request for something the bank could have asked on day one. The gaps sat in the file from the start. Only the comparison came late.
This time the comparison happens at the door. The AI reads every document as it lands, runs your KYB rules across all eight, and names the two points that disagree, with their pages. Emma confirms the gaps, the CFO fixes both at once, and compliance decides on a complete file.
None of these screens would surprise a KYC team. The timing would: the documents are read against each other the day they arrive, both gaps go out in one message, and compliance sees only what needs a judgment. The nine steps below follow Novalis from the portal upload on November 3 to the accounts set up on November 9.
The company sends its papers, and the AI has read them before the analyst opens the case.
Marcus Reed, the relationship manager, has agreed with Novalis Logistics Inc., a Columbus, Ohio, freight company, to open a checking account, a savings account and twelve corporate cards. He opens a business onboarding case. Its attachments are a list of named slots, one per document your KYB policy asks for.
Tom Becker, the CFO, uploads his files from the business portal the same afternoon. The portal calls the repository API, and each file lands in the case.
The capture chain classifies each file and extracts the values your team defined for it: company name, registration number, capital, registered office, directors, shareholders, the date of the document.
Before Emma Collins, the KYC analyst, opens the case, an AI agent runs it against the rules your compliance team wrote in plain language.
The result is written onto the case in two fields: a status and the reasoning. The status is Attention required, with two points, each naming the two documents that disagree.
Both warnings are about ownership and authority. Emma works them with the documents open beside her.
Emma opens the holding's articles in the viewer, at the page the warning cites. Hartley Holdings holds 60 percent of Novalis, and its shares are split evenly between Marc Hartley and his sister Julie. The declaration names Marc and leaves Julie out.
Emma works out the indirect stake herself: half of 60 percent is 30 percent, above the 25 percent beneficial ownership threshold in your CDD policy. She drops a note on the page so the next reader sees her reasoning.
The second warning is about authority. Emma asks the assistant who must sign a decision to open bank accounts. The answer points to article 17 and to the resolution, which carries one signature.
Emma asks the assistant for a request to Tom Becker. The draft covers both points, with the reason for each and the company name already in it. She adds a line on timing and sends it. The case moves to Waiting for customer, with an SLA timer visible on the step.
The file is complete now, and the last word goes to Keisha Brooks.
Two days later the updated declaration, Julie Hartley's ID and the countersigned resolution come in through the portal. They are filed in their slots, the analysis runs again, and the status moves to Complete.
The workflow routes the case to Keisha Brooks, the compliance officer, because the company has a holding layer. She asks for a summary, opens the two cleared points, and sets the risk rating herself.
Approval opens a task for the back office to set up the accounts, the mandates and the cards. The case closes, and the next review date your policy sets for a Medium rating sits on the customer file as a field.
Novalis landed in the middle box. Every company file lands in one of three, set by the KYB rules your compliance team wrote, and each box sends the case down its own path.
Documents current, owners declared, signatures as the articles require. The analysis lists each rule it ran and the page it read.
Next: the analyst checks, compliance rates and approves.An owner missing, a signature short. The analysis names each point and the pages that disagree.
Next: one request to the customer; the check runs again when the documents arrive.An activity or a legal form your policy does not accept. The AI lists what passes, then names the rule.
Next: the compliance officer reviews and decides, with the reason on the case.It approves nobody. It refuses nobody. It sets no risk rating and opens no account. Across the nine steps on this page, the binding decisions are taken by the analyst and the compliance officer, with their own rights and their own trace.
The AI reads, compares, drafts and summarizes. The control is in the rules your compliance team wrote, and in the workflow that routes each file to the right person.
Three counts from the Novalis file, November 3 to 9. A company with no holding layer would show fewer gaps, one with three layers would show more.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
An analyst, a compliance officer and an architect each get a vote on whether this goes live. Each has a different reason to cast it.
The week goes into comparing papers, and the customer hears from you twice.
You sign files you have no time to open page by page.
Onboarding already crosses a portal, a document store and three back offices.
Pick the comparison your analysts repeat on every company file, such as declared owners against the share registers, and move it to the door. One rule on one queue gives your team real files to judge it by.
Your business portal, your case files and your documents stay where they are. The checks run on top of them.
Let's talk
Bring a few anonymized business files, one with a holding in its ownership, and your KYB checklist. We will walk them through these nine steps with you.