Document expiry is a deposit problem wearing a compliance badge
Onboarding attrition is optimised because it is visible in a funnel. Mid-life document expiry is neither measured nor owned, and it freezes funded accounts that were already trading.
Document chasing is treated as a compliance cost. It is a deposit problem. A client blocked by an expired proof of address is a funded account that cannot trade, and the interval before someone notices is measured in weeks at most brokers.
Where the money actually goes
Onboarding attrition is well studied and heavily optimised, because it is visible in the funnel. Mid-life document expiry is neither. A client who cleared KYC eighteen months ago and whose identity document lapsed last Tuesday does not appear in any funnel, and their deposit sits in a wallet nobody is watching.
An expired document on an existing client is not a compliance exception. It is a deposit that has stopped and a churn event that has not happened yet.
The three costs, only one of which is measured
| Cost | Who carries it | Measured? |
|---|---|---|
| Staff time chasing | Operations headcount | Usually |
| Blocked deposit, not traded | Revenue | Rarely |
| Client leaves rather than resubmit | Retention | Almost never |
The resubmission cliff
Asking an existing client to resubmit a document is a materially different request from asking a new one. The new client is in an onboarding mindset and expects friction. The existing client has been trading for a year and experiences it as an accusation. Completion rates reflect that, and they fall further with each reminder that uses the same wording.
E[chase] = P(complete) × blocked_balance × P(trades | unblocked) − staff_costTiming dominates everything else
The single largest lever is not the message. It is contacting the client before the document expires rather than after. Pre-expiry, the request is administrative and completion is high. Post-expiry, the account is frozen, the client discovers this by failing to trade, and the conversation starts from frustration.
- 01Expiry minus 30 daysAdministrative request, highest completion
- 02Expiry minus 7 daysStill pre-emptive, still high
- 03ExpiryAccount restricted
- 04Client attempts to trade and failsDiscovery by friction
- 05Support ticket raisedNow it costs you twice
| Chased after expiry | Chased 30 days before | |
|---|---|---|
| Accounts | 400 | 400 |
| Completion rate | 34% | 71% |
| Average days blocked | 19 | 0 |
| Support tickets generated | 186 | 12 |
| Accounts lost entirely | 41 | 9 |
Illustrative figures, chosen to show the mechanism. Your own numbers will differ.
What makes this hard in practice
- Expiry dates live in the KYC provider, balances live in the platform, and language lives in the CRM.
- Nothing watches for the intersection of “document expiring” and “account funded”.
- Reminder sequences are usually built once and never varied by cohort, channel or language.
- The team doing the chasing is measured on documents collected, not on deposits unblocked.
That last point is the one that keeps the problem alive. Measured on documents, the rational strategy is to chase the easiest ones. Measured on unblocked balance, it inverts immediately, and the funded accounts with real money in them get contacted first.