Onboarding SLA

An onboarding SLA (service-level agreement) is the target time within which a business application must be reviewed and reach a decision, or a defined next step, measured from a stated start point such as submission or receipt of a complete file. It can be an internal target, a commitment in a contract with a partner or vendor, or both.

Why it matters in KYB review

Onboarding speed is a commercial number and a compliance risk at once. Slow reviews cost applicants, and applicants who wait tend to drop out or go to a competitor. Pressure to hit a speed target, without a clear definition of what "done" means, is how files end up with gaps.

Regulation sets what must happen, not how fast. For banks, the customer identification rule in 31 CFR 1020.220 requires identity verification "within a reasonable time after the account is opened," and procedures for when the bank cannot form a reasonable belief that it knows the customer's true identity: when not to open an account, the terms under which a customer may use it while verification is pending, and when to close it. An SLA has to fit inside those procedures, never override them.

How to define one

A usable onboarding SLA names:

• The start event. Application submitted, or complete file received.
• The end event. Approved, declined, or first request for information sent. These give very different numbers.
• The clock. Business hours, business days or calendar hours, and which time zone. Weekend applications behave differently under each.
• Segments. Standard cases and cases needing enhanced due diligence should have different targets.
• Exclusions. Time waiting on the applicant, and escalations to a partner bank.
• The measure. Median, 90th percentile, and share of cases breaching target. An average hides the long tail.

What a reviewer checks against it

• Cases approaching breach, flagged before they breach.
• Whether a quick decision is still a complete one: every required check done and recorded.
• Where time goes: waiting in the queue, active review, waiting on the applicant, or waiting on escalation.

Common pitfalls

• An SLA that counts only business hours, so work submitted on Friday evening sits until Monday while the metric looks healthy.
• Hitting the target by sending a partial request list, then a second and a third. One consolidated request is faster for everyone.
• No link between the SLA and capacity planning, so every volume spike becomes a backlog (see KYB manual review queue).
• Measuring speed without measuring rework or QA findings.

Related terms

KYB manual review queue, request for information (RFI), alert escalation, business onboarding review.

Sweat AI is an AI-native BPO for banks and fintechs, working onboarding and fraud queues 24/7, so the queue is worked when your team logs in. Each case comes back with the evidence and one consolidated list of what is still needed, and your team makes the decision. See 24/7 onboarding review or model your own queue with the onboarding backlog calculator.