Referral Partners: How to submit KYC for UK clients
Some UK collection partners require basic identity information about your client's director before they can begin collection work. This guide shows you how to submit that information from the Referral Partner Dashboard (or via the API) so your client's cases are not blocked.
When KYC is required
KYC is required only when a client is routed to a collection partner that has been flagged as requiring it. Today this applies to UK collection partners (currently Oriel Collections). Clients routed to partners outside the UK are not affected.
If KYC is required for a client, case submission through the referral partner flow is blocked until the information is on file. The platform returns a MissingKycVerification error on case creation until you submit the three required fields. This is a hard block - unlike the SDCA and Power of Attorney gates, cases are not created in a pending state while KYC is outstanding.
For background on the other case-creation gates, see Contracts & signatures: SDCA, PoA, and the legal framework (overview).
What you'll need before you start
You need three pieces of information about a senior manager or director of your client's company:
Full name
Home address
Date of birth
Collect these details directly from your client. The data is stored once per client and reused across all their cases - you do not need to submit KYC per case.
Submit KYC from the Clients page
This is the recommended flow for most partners.
Open the Referral Partner Dashboard and go to the Clients page.
Locate the client in the list. For clients routed to a KYC-requiring partner, a KYC Status column is shown.
If the badge reads Pending (amber), click it. A form opens where you enter the director's full name, home address, and date of birth.
Submit the form. The badge updates to Completed (green) once the data is saved.
Clicking a Completed badge opens a read-only view of the previously submitted data. If no badge is shown, the client is not routed to a KYC-requiring partner and no submission is needed.
You can resubmit the form if the information changes. The most recent submission is the one Debitura uses for verification checks.
Submit KYC via the API
If you are integrated with the Referral Partner API, you can submit KYC programmatically instead of using the dashboard.
GET /clientsreturns each client with arequiresKycVerificationflag and akycVerificationobject (ornullif none on file).POST /clients/{externalTenantId}/kyc-verificationsubmits the three KYC fields and returns201 Created.
By default, submitting KYC posts a short system message on all active cases for the client confirming that KYC was submitted. You can disable this by passing ?sendChatNotification=false on the request. Chat posting is best-effort - if it fails, the KYC submission itself is not affected.
You can submit KYC for any client, even if requiresKycVerification is currently false - the API does not reject submissions for clients that do not currently require KYC.
What happens after you submit
Once KYC is on file for a client:
New case submissions for that client proceed without the KYC block.
The submitted director details are visible to the collection partner in their case and client views, so they have what they need for their compliance checks.
If you had blocked cases waiting on KYC, you can resubmit them and they will be accepted.
See Lead & quote status definitions (and expected actions) for how a client moves through the broader lifecycle, and How to support your customers using Debitura for first-line support workflows.
What this flow does not do
The current KYC step is a targeted solution for UK referral flows. A few things are worth being aware of:
Referral partner flow only. KYC is enforced only when cases are submitted through the referral partner flow. Clients submitting cases directly through the Creditor App or their own API key will not be asked for KYC.
No automated verification. Debitura stores the three fields you submit but does not verify them against Companies House, sanctions lists, or PEP databases. The collection partner performs their own compliance checks against the data you provide.
Text fields only. There is no document upload - no ID, no proof of address, no supporting documentation. The data you submit is the data the partner receives.
No ongoing monitoring. KYC is a one-time data collection step. There are no periodic re-checks on the platform today.
If your client's director details change, resubmit the form. The latest submission is the one used for verification checks.