KYC and AML customer portal
Give every customer a clear path through the information and evidence that applies.
Swootle connects a white-labelled customer journey to the same configurable onboarding, KYC/KYB, evidence, exception and review workflow used by internal teams. Customers can see what is required and operations can see what remains outstanding.
Implementation boundary: Portal branding and advanced configuration depend on the selected plan and implementation. External providers perform their respective identity, KYC/KYB and screening checks; the portal collects configured customer inputs and does not make the firm’s risk or approval decision. Confirm accessibility, language, provider, integration and data requirements before deployment.
How the workflow fits together
Start with the relationship
Invite the customer into the path that applies to their case
Begin with the configured product, service, relationship and jurisdiction context so the portal presents the relevant journey. Avoid sending every individual, company or trust the same generic document request.
- Branded customer invitation and guided entry point
- Product, service and jurisdiction context
- A clear view of required and outstanding work
Adapt the questions
Collect individuals, entities, trusts and connected parties without one fixed form
Use configured branches to request identity, entity, ownership, control, representative and service information for the customer structure in front of the firm. Keep each connected person or entity within the same operational case context.
- Individual and entity-specific question paths
- Trust, beneficial-owner and controller relationships
- Connected parties and authorised representatives
Request the evidence
Explain what is needed and collect it against the relevant requirement
Ask for documents, declarations and supporting information alongside the customer or entity detail they evidence. Configure source-of-funds, source-of-wealth or enhanced-review requests only where the firm’s case path requires them.
- Documents and declarations linked to the case path
- Requirement-specific instructions and completion state
- Risk-sensitive evidence requests rather than a universal list
Follow up clearly
Turn missing or unsuitable evidence into a precise customer request
Route incomplete or inconsistent submissions to the internal team, then return the configured request for the specific update required. Email and SMS notifications can bring the customer back to the same guided journey instead of starting another disconnected thread.
- Structured request-more-information loops
- Clear outstanding item and next action
- Configured email and SMS notifications
Protect the review boundary
Keep internal risk context and approval work with the responsible team
The customer sees the questions, evidence requirements and follow-up intended for them. Provider-returned checks, internal notes, configured risk treatment, reviewer tasks and approval decisions remain in the operational workspace and review path.
- Customer and internal-team responsibilities separated
- External checks routed into the internal workflow
- Human judgement and approval kept out of the customer view
Continue the lifecycle
Carry the completed journey into approval, remediation and later refresh
Keep the customer submission connected to the reviewer action and retained outcome, then use that record as context when the firm initiates a remediation case, periodic KYC review or event-led update.
- Operational hand-off with submission context
- Retained evidence, actions and decision history
- A starting point for the next configured review
Evaluate the operating model
Map a customer evidence journey · Explore regulated onboarding