When a client has already uploaded a document to their file, asking for it again creates unnecessary friction and slows the process down. With requirement auto-completion, Complif checks the client's file at the moment the requirement is created: if it finds a valid document of the same type, it completes the requirement on its own and leaves it ready for your review.
This article explains how to enable it, how it behaves, and what the client sees in the User Portal.
How does it work?
Auto-completion is configured in the requirement automations of your onboarding and case templates. Once enabled, every time the automation creates that requirement, Complif runs the following steps:
It searches the client's file for a valid document of the type configured in the requirement.
If it finds one, it automatically creates a submission linking that existing document, without asking for it again.
The requirement moves to Under review, which the client sees as Completed in the User Portal.
The analyst reviews that submission and approves or rejects it like any other.
If there is no valid document of that type in the client's file, nothing changes: the requirement is created as pending and is requested from the client as usual.
Auto-completion does not approve the requirement: it leaves it under review. The final decision still belongs to the analyst.
Which requirements can be auto-completed?
The option is available only for requirements that meet both of these conditions:
They are file upload requirements (the client has to attach a document).
They have a document type defined in the template. That type is what Complif uses to look for matches in the client's file.
If the requirement does not meet both conditions, the option does not appear in the configuration.
How to enable it
Go to Settings and open the onboarding or case template where the requirement is requested.
Find the requirement within the template's automations and open its configuration.
Check the Auto-complete with existing document option.
Save the template.
The setting applies from that moment onward, to the requirements the automation creates from then on. Requirements that already exist are not changed retroactively.
Auto-completion is enabled per requirement and per template. You can have it on in the onboarding template for legal entities and off in the one for individuals, or on for only some documents within the same template.
How it looks in the admin panel
Auto-completed requirements are handled just like any other, with one visible difference: when you open the requirement, the automatically generated submission shows an info banner flagging it as auto-completed.
That banner lets you tell at a glance the difference between:
A document the client uploaded specifically for that requirement.
A document that was already in the client's file and that Complif reused.
The distinction matters at review time: on an auto-completed submission it is worth checking that the reused document is still appropriate for this particular request (validity, scope, period covered).
What the client sees in the User Portal
The client does not receive a request that is already resolved. Instead:
The requirement appears as completed, with no pending action on their side.
When they open it, they see the message: "We found a document of this type in your file. You don't need to do anything", instead of the generic review message.
On grouped requirement screens, an info banner tells them upfront that part of what was requested has already been resolved automatically.
The message is available in Spanish, English and Portuguese, and is shown in the language configured for the client.
Approval and rejection
Reviewing an auto-completed submission works exactly like reviewing any other:
If you approve it, the requirement is completed and the process continues as usual.
If you reject it, the requirement goes back to pending and is requested from the client like any other document request.
In other words, auto-completion never leaves the client unable to respond: if the reused document is not good enough, the request is reactivated.
Document linking
The reused document is linked to the requirement and to the related entities (people, accounts and account openings), exactly as if the client had uploaded it at that moment. It is the same document that was already in the client's file, not a new copy.
Recommendations
Turn it on first for stable documents whose content does not change over time (for example, bylaws or a valid ID document), before extending it to documents that are renewed often.
Check that the template's document type is the right one: the search is done on exactly that type.
If your compliance policy requires a document issued within a given period, keep in mind that the analyst is still the one who validates that condition when reviewing the submission.
Frequently asked questions
Does the client have to do anything?
No. The requirement is not left pending any action from the client: if they log into the portal, they will see it as completed, with the corresponding message.
Does it work on manually sent requirements?
No. Auto-completion applies to requirements created by the automations in onboarding and case templates.
What if there is more than one document of the same type in the client's file?
Complif links a valid document of that type to the requirement. When reviewing the submission you can check which document was reused and, if it is not the right one, reject it so it is requested from the client.
Can I turn it off?
Yes. Uncheck the option in the requirement's configuration within the template. From then on, new requirements are created as pending and requested from the client.
If you need help setting it up, reach out to Support.