How long does AML screening take to clear a new customer?

AML screening has no universal clearance time: a completed database search is not the same as approval of a new customer. A possible match, missing identity details, or additional due diligence keeps the decision open until the relevant questions are resolved. For 2026 onboarding, separate the screening result from the approval decision before promising a completion time.

Why this matters

A customer waiting to open an account and a guest waiting for arrival instructions both need a clear next step. Neither benefits from a message that says screening is complete when someone still needs to review the result.

Measure time to a usable decision, not just time to a search result. That distinction keeps your customer messages accurate and prevents your team from treating an unresolved alert as an approval.

Start with how sanctions screening works if you need to understand why a name match requires interpretation. A screening system identifies potential matches. Your approval process determines what those matches mean for the customer.

How long does AML screening take to clear a new customer?

AML screening takes as long as the required checks and review take to reach a defensible decision. There is no single completion time that applies across providers, customer types, jurisdictions, and review requirements.

For your 2026 workflow, track these stages separately. Each ends at a different point, and only the final stage answers whether the customer can proceed.

A quick search is useful because it gives the reviewer information promptly. Its limitation is that speed says nothing about whether an alert is resolved or whether other required checks are complete.

A review process adds the context needed for a decision. Its trade-off is an additional dependency on information, reviewer availability, and the organization's requirements.

Do not describe a customer as cleared while a required review remains open. Use a status that reflects the actual stage instead.

No unresolved match: check the rest of onboarding

When screening returns no unresolved match, the search itself is no longer the blocking task. The next question is whether the customer has satisfied the rest of your onboarding requirements.

Identity verification, customer information collection, and approval are related tasks, but they are not interchangeable. A result from one task does not establish that every other task is complete.

Use a simple completion check before approving the customer:

• Confirm the required searches have finished.
• Check that the identity details belong to the customer being reviewed.
• Confirm there are no outstanding requests for information.
• Apply the relevant approval requirements.
• Record the decision and its basis.

This route is best for customers whose information is complete and whose results do not require further investigation. Its advantage is a clear path to decision. Its limitation is that a clean search result covers only the sources and checks included in that search.

For 2026 reporting, keep a completed search and an approved customer as distinct statuses. Otherwise, the apparent screening speed hides unfinished onboarding work.

Possible match: resolve identity before deciding

A possible match means a customer resembles a record closely enough to need review. It is not, by itself, proof that the customer is the person in that record.

Names alone do not always distinguish people. A reviewer uses available identifying details, such as date of birth and nationality, to assess whether the result concerns the same person.

Treat an alert as a question to resolve, not a verdict to repeat to the customer. Ask for the specific information needed to answer that question rather than requesting unrelated documents.

A practical review sequence is:

1. Identify the record that triggered the alert.
2. Compare the customer details with the record's identifying details.
3. Identify what remains uncertain.
4. Request relevant information if needed.
5. Record the match assessment and route the decision appropriately.

This route is best for cases where the search produces a plausible identity overlap. Its advantage is that it prevents a name resemblance from becoming an unsupported decision. Its limitation is that incomplete source records or missing customer details leave the reviewer with less information.

Keep the customer message neutral. Explain what you need and what happens next without presenting an unresolved screening alert as a confirmed finding.

Additional due diligence: screening is only part of the work

Some customer reviews require information beyond the initial search. Depending on the applicable requirements and the case, this includes understanding ownership, the purpose of the relationship, or the source of funds.

That work has a different endpoint from database screening. A search finishes when results return. Due diligence finishes when the required information has been assessed and the appropriate decision has been made.

Politically exposed person status also requires context. It is not equivalent to a sanctions designation, and it does not automatically establish wrongdoing.

This route is best for relationships that require a deeper assessment under the organization's applicable obligations. Its advantage is a decision based on the relationship, not just a name search. Its limitation is that approval depends on information and review beyond the initial result.

Avoid quoting the search turnaround as the full clearance time. The customer is still waiting on the broader assessment, even if the screening result arrived earlier.

Why AML screening time varies

The factors that change clearance time are the work required to reach the decision, not simply the speed of the search. Identify the active dependency before trying to shorten the process.

• Completeness of customer information. Missing identifying details create another request and another response cycle.
• Ambiguity of a potential match. Similar names require context to establish whether the record concerns the customer.
• Scope of the checks. Sanctions screening, politically exposed person screening, and other checks answer different questions.
• Need for additional due diligence. Ownership or relationship information adds work beyond the initial screening search.
• Review ownership and availability. An alert remains unresolved if nobody is responsible for assessing it.
• Customer response. A reviewer cannot assess information the customer has not yet supplied.

For your 2026 process, attach each pending case to a reason and a next action. A generic pending label tells you little. Waiting for a date of birth, waiting for customer documents, and waiting for a reviewer describe different problems.

Fix the dependency you can actually identify. Sending the same search again does not supply a missing document or assign an unowned review.

How do you measure the real clearance time?

Measure clearance from the point your defined onboarding process starts to the point the customer receives an actionable decision. Also measure the search and review stages separately so you can see where the elapsed time accumulates.

Choose the start point deliberately. An application created, a verification link sent, and complete customer information received are different events. Mixing them produces timing figures that cannot be compared fairly.

Record these events consistently:

• Customer information requested.
• Required information received.
• Screening result returned.
• Additional information requested, if applicable.
• Review completed.
• Customer decision communicated.

Keep customer waiting time visible rather than silently removing it. It affects the onboarding experience even when your team is not responsible for the delay.

For a 2026 service promise, use measured results from your own defined process. State which customers and checks the promise covers, and distinguish straightforward cases from cases requiring further review.

A provider's search-speed claim is not a substitute for this measurement. Your customer experiences the full journey, including information requests, review queues, and the final message.

How can you reduce delays without skipping checks?

Reduce avoidable back-and-forth by collecting clear information, explaining the next step, and assigning responsibility for review. Faster decisions come from removing unnecessary waiting, not calling unfinished work complete.

Collect usable information

Ask for the details your process actually requires. Make instructions specific enough that the customer understands what to submit and why.

Review incomplete submissions before they become an unexplained hold. A focused request is easier to act on than a broad instruction to provide more information.

Give every review an owner

Assign someone to assess unresolved results and define how that person escalates a case. Ownership turns a pending status into an active task.

Keep the decision trail understandable. Another reviewer should be able to see what was checked, what remained uncertain, and why the outcome was chosen.

Explain the next action

Tell customers whether they need to do something or whether your team is reviewing the information already supplied. Do not ask them to repeat a completed step without a reason.

For a hospitality workflow, keep booking communications separate from unresolved verification decisions. A professional guest experience needs clear instructions, not technical terminology or unsupported timing promises.

Where shared-link guest verification fits

Checktiv is best for independent short-term rental hosts who want zero-code guest verification through shared links. It gives hosts a straightforward way to request verification and review it without building a technical workflow.

The Checktiv guest verification journey is presented as 3 steps in 5 minutes: sign up, get a link, and review the verification. That is a setup-and-use journey, not a guaranteed AML clearance time for every customer or every result.

1. Sign up. Establish your account before introducing the verification step to guests.
2. Get a link. Use the shared-link approach to request guest verification.
3. Review the verification. Assess the result before making your hosting decision.

*Reviewing the verification is a separate step from sending the link.*

The benefit is a zero-code process suited to a host managing guest communications and arrivals. The boundary is equally important: a convenient verification link does not establish the full scope of a regulated business's AML obligations.

Use Checktiv when the operational need is professional guest verification. If your business needs a regulated customer approval process, define the required screening, review, and decision responsibilities separately.

Can you approve a customer as soon as screening finishes?

Approve a customer after screening finishes only when the required review and other onboarding conditions are also complete. A returned result is an input to the decision, not a universal authorization to proceed.

If an alert remains unresolved, keep the status accurate. The next action is to resolve or escalate the alert under your process, not to label the customer cleared because the search ran successfully.

Does a possible match mean the customer failed?

A possible match does not mean the customer failed screening. It means the result needs assessment to determine whether it concerns the customer and what action follows.

Use identifying details and relevant context to resolve the alert. Do not equate a similar name, politically exposed person status, and a confirmed sanctions match.

Does initial clearance cover future activity?

Initial clearance does not establish that future information or activity will remain unchanged. Ongoing screening and monitoring serve a different purpose from the initial onboarding decision.

For 2026 operations, define when reassessment is required under your applicable obligations and business process. Keep that policy separate from the time promise you give a new customer.

One last thing

A faster search does not shorten a queue nobody owns. Before changing your screening provider, inspect an unresolved case and identify the person, information, or decision it is waiting for.

For your next 2026 workflow review, replace a single pending status with a specific reason and next action. That small operational change makes the customer message clearer and the team's work easier to assign.

Related guides

• How long does an ID verification check take?
• How often should sanctions screening be run?
• Identity verification for short-term rental hosts