Why reboarding has become the biggest challenge in compliance
On this page
Every new business customer creates years of future compliance work for financial institutions. As the customer base grows, reboarding can account for up to 90% of compliance volume (Duna 2026).
Think about a fintech company with thousands of customers. Each policy update, regulatory change, or periodic review creates new compliance work across existing customers. Before long, compliance teams spend more time maintaining existing customers than onboarding new ones.
The more customers a financial institution onboards, the greater its reboarding volume, and the operational cost of managing it.
What is reboarding, and what triggers it?
Reboarding, or re-KYC (know-your-customer), is the process of keeping business information current and complete over the course of the customer lifecycle. Different events trigger reboarding, and every review builds on customer information you’ve already collected.
Here are the most common reasons financial institutions reboard existing customers:
Time-based review / periodic reboarding: A customer’s data is only accurate at the point in time it was collected, so today’s data could be stale tomorrow. A time-based review can be triggered when an ultimate beneficial owner (UBO) gets married and changes their last name, gets citizenship in another country, or changes their address or residence.
Regulators require firms to periodically ask customers whether anything has changed, or if their information is still current. The time cycle depends on risk: annually for high-risk customers, and three to five years for low-risk ones.
Event-driven reboarding: Every customer has an expected profile that shows who they are and how they behave. When a customer’s activity or public signals don’t match what’s expected, an event-driven reboard is triggered.
Imagine one of your customers runs a bakery, and suddenly you see they’re earning €1 million in monthly revenue. This change would trigger a review, as would a shift in media presence, or a website that doesn’t reconcile.
A policy or regulatory change: New rules could require you to collect different information or re-check existing customers. For example, you might have to gather health information, financial statements, or a tax ID you didn’t ask for the first time around.
Auditors might also decide that your business processes need to be revised and that you should collect new information, even if you don't have the legal requirement to do so.
Product upgrade/downgrade: When a customer adds a new product, it could change their risk exposure. For instance, a customer who currently has a bank account adds a mortgage, or they’re now using a trading account and investing in stocks. These change how funds flow through the system and would trigger a remediation.
Why reboarding is a defensive function
Financial institutions have very little to win in reboarding. In the best scenario, nothing has changed with customers, and all compliance boxes have been checked. The company is protected from regulatory, financial, and commercial downside.
Worst case, 10-15% of customers haven’t responded to requests for information, or the data is inconsistent.
This leaves companies with a difficult choice: end the customer relationship, or keep the customer and take the risk that everything will work out. Either way, there’s nothing to gain, which makes reboarding such a fundamental challenge for companies in the financial sector.
What breaks when KYB is designed only for onboarding
Workflow-based KYB (know-your-business) systems were designed to onboard new business customers. Reboarding requires teams to continuously reconcile and monitor existing customer information with new information as businesses, regulations, and policies change.
When those systems are used for reboarding, they break in a few predictable ways:
Historical context is lost: KYB platforms built for onboarding store customer information inside a sequence of questions and decisions. When the workflow changes, such as reordering questions or adding dependencies, the historical information becomes hard to reuse because it no longer maps cleanly to the new process.
Changes are harder to explain: Instead of maintaining a single record that shows how each fact changed, information is spread across questionnaires, cases, and reviews. This makes it difficult to understand how the business has evolved.
Customers are asked for the same information again: Reboarding feels like starting over, with customers filling out a new questionnaire even though much of the evidence was already submitted.
Old and new data must be reconciled manually: Different versions of the same fact create data matching problems. Instead of reviewing genuine risk, analysts spend their time comparing old and new values, sending follow-up emails, and trying to understand why two versions of the same information don't match.
A policy-driven approach to reboarding
Reboarding works best when every review builds on what you already know about a customer. As new evidence is added, the system makes it clear what has changed since the last review and why.
Instead of sending every customer through the same workflow, a policy-driven approach starts by defining what “good” looks like. Compliance teams specify the evidence a customer should have on file and the conditions they must meet. The policy engine continuously evaluates the evidence already on file, requests missing evidence, and routes exceptions to analysts for review.
One large European marketplace uses this approach to manage more than 50,000 customers. The company reboarded 97% of its customers, while partners spent an average of just 11.1 minutes completing each request. Customers who no longer actively traded on the platform were offboarded.
“With Duna’s platform, we confidently onboard and manage business customers from first interaction through the full customer lifecycle.”
Bas van Beusekom
CCO, Brand New Day Bank
Keeping business identity current across the customer lifecycle
Staying on top of evolving businesses and policies gets harder with every new customer. When changes are automatically evaluated against policy, regulatory updates become routine instead of disruptive. Compliance teams can then focus on investigating complex cases instead of working through checkbox exercises.
Learn how Duna helps financial institutions manage compliance throughout the customer lifecycle.
Every new business customer creates years of future compliance work for financial institutions. As the customer base grows, reboarding can account for up to 90% of compliance volume (Duna 2026).
Think about a fintech company with thousands of customers. Each policy update, regulatory change, or periodic review creates new compliance work across existing customers. Before long, compliance teams spend more time maintaining existing customers than onboarding new ones.
The more customers a financial institution onboards, the greater its reboarding volume, and the operational cost of managing it.
What is reboarding, and what triggers it?
Reboarding, or re-KYC (know-your-customer), is the process of keeping business information current and complete over the course of the customer lifecycle. Different events trigger reboarding, and every review builds on customer information you’ve already collected.
Here are the most common reasons financial institutions reboard existing customers:
Time-based review / periodic reboarding: A customer’s data is only accurate at the point in time it was collected, so today’s data could be stale tomorrow. A time-based review can be triggered when an ultimate beneficial owner (UBO) gets married and changes their last name, gets citizenship in another country, or changes their address or residence.
Regulators require firms to periodically ask customers whether anything has changed, or if their information is still current. The time cycle depends on risk: annually for high-risk customers, and three to five years for low-risk ones.
Event-driven reboarding: Every customer has an expected profile that shows who they are and how they behave. When a customer’s activity or public signals don’t match what’s expected, an event-driven reboard is triggered.
Imagine one of your customers runs a bakery, and suddenly you see they’re earning €1 million in monthly revenue. This change would trigger a review, as would a shift in media presence, or a website that doesn’t reconcile.
A policy or regulatory change: New rules could require you to collect different information or re-check existing customers. For example, you might have to gather health information, financial statements, or a tax ID you didn’t ask for the first time around.
Auditors might also decide that your business processes need to be revised and that you should collect new information, even if you don't have the legal requirement to do so.
Product upgrade/downgrade: When a customer adds a new product, it could change their risk exposure. For instance, a customer who currently has a bank account adds a mortgage, or they’re now using a trading account and investing in stocks. These change how funds flow through the system and would trigger a remediation.
Why reboarding is a defensive function
Financial institutions have very little to win in reboarding. In the best scenario, nothing has changed with customers, and all compliance boxes have been checked. The company is protected from regulatory, financial, and commercial downside.
Worst case, 10-15% of customers haven’t responded to requests for information, or the data is inconsistent.
This leaves companies with a difficult choice: end the customer relationship, or keep the customer and take the risk that everything will work out. Either way, there’s nothing to gain, which makes reboarding such a fundamental challenge for companies in the financial sector.
What breaks when KYB is designed only for onboarding
Workflow-based KYB (know-your-business) systems were designed to onboard new business customers. Reboarding requires teams to continuously reconcile and monitor existing customer information with new information as businesses, regulations, and policies change.
When those systems are used for reboarding, they break in a few predictable ways:
Historical context is lost: KYB platforms built for onboarding store customer information inside a sequence of questions and decisions. When the workflow changes, such as reordering questions or adding dependencies, the historical information becomes hard to reuse because it no longer maps cleanly to the new process.
Changes are harder to explain: Instead of maintaining a single record that shows how each fact changed, information is spread across questionnaires, cases, and reviews. This makes it difficult to understand how the business has evolved.
Customers are asked for the same information again: Reboarding feels like starting over, with customers filling out a new questionnaire even though much of the evidence was already submitted.
Old and new data must be reconciled manually: Different versions of the same fact create data matching problems. Instead of reviewing genuine risk, analysts spend their time comparing old and new values, sending follow-up emails, and trying to understand why two versions of the same information don't match.
A policy-driven approach to reboarding
Reboarding works best when every review builds on what you already know about a customer. As new evidence is added, the system makes it clear what has changed since the last review and why.
Instead of sending every customer through the same workflow, a policy-driven approach starts by defining what “good” looks like. Compliance teams specify the evidence a customer should have on file and the conditions they must meet. The policy engine continuously evaluates the evidence already on file, requests missing evidence, and routes exceptions to analysts for review.
One large European marketplace uses this approach to manage more than 50,000 customers. The company reboarded 97% of its customers, while partners spent an average of just 11.1 minutes completing each request. Customers who no longer actively traded on the platform were offboarded.
“With Duna’s platform, we confidently onboard and manage business customers from first interaction through the full customer lifecycle.”
Bas van Beusekom
CCO, Brand New Day Bank
Keeping business identity current across the customer lifecycle
Staying on top of evolving businesses and policies gets harder with every new customer. When changes are automatically evaluated against policy, regulatory updates become routine instead of disruptive. Compliance teams can then focus on investigating complex cases instead of working through checkbox exercises.
Learn how Duna helps financial institutions manage compliance throughout the customer lifecycle.
Continue reading
Industries
Customers
Company
Resources
Industries
Customers
Company
Resources
Industries
Customers
Company
Resources