Introduction

The Assignor registration is essential to start the operation of any fund that purchases credit rights. In this section we explain the entire flow, from submitting the first pieces of information through to opening the Assignment Pipeline for asset submission.

To gain access to the services covered in the next sections, contact the team at integracao.dtvm@qitech.com.br so that the proper clearances are granted, both in the Sandbox and in the Production environment.

It is worth noting that, for an Assignor to be effectively released, two different systems must be used:

1. The Assignor's registration in our base, performed only once;

2. Formalization of an Assignment Contract between the Assignor and the Fund;

For both systems, either the manager or the consultant can act as the agent, proposing registrations and contracts between assignors and funds as the operation develops.

Assignor Registration

At this stage, you must submit all the information about the Assignor as well as about its representatives and ultimate beneficial owners. Once submitted, the Assignor starts as Pending Registry, a first analysis is generated and the required documentation must be sent to validate the registration. Finally, after attaching all the required documents, you must trigger the Analysis — that is, submit the Analysis for validation, which goes through an anti-fraud and AML process.

Some documents are required for the analysis. For a legal entity: the articles of association, with the latest available update, a simplified certificate from the Board of Trade, and the minutes electing the current board of directors. In addition, the documents of the company's ultimate beneficial owners must be submitted, for the purposes of combating money laundering, corruption and terrorism financing. For natural person assignors, the identification document alone is sufficient for the analysis.

In both cases, a statement of responsibility from the registration agent is required, attesting that they carried out the full document collection — revenue statements, compliance records, among others — as required by the CVM and ANBIMA rules.

As soon as this first Analysis is approved, the registration goes through an internal validation stage, in which a team validates the information received and moves it forward, after the signers are validated. Once effective, the assignor becomes available for the next operations. At this point, if configured, we send a Webhook notifying that the Analysis was approved; you can also track the registered assignors through the manager's portal.

Analyses idle for 1 month are canceled automatically

An Analysis that goes 1 month without activity is canceled automatically, moving to the canceled status. In practice, the most common case is an analysis that remains in pending_documents — those where the documentation was never attached, or where the Analysis Trigger was never commanded.

The cancellation is terminal: a canceled analysis cannot be reverted and accepts neither new documents nor triggering. To resume the registration, generate a new analysis through the Registration Update.

The change fires the assignor_registry.analysis_status_change webhook with analysis_status: canceled — see Analysis Webhooks.

Assignor Update

If a registration update is needed, all the Assignor's information must be submitted again with the desired changes. After submission, a new Analysis is generated, to which the necessary documentation must be attached so that we can ensure the update is valid. Finally, after attaching all the required documents, you must trigger the Analysis — that is, submit the new Analysis for validation.

Note that the documents to be submitted are only those of the entities that changed, whether it is the addition of a new representative or a change to some of the company's registration data.

As soon as this new Analysis is approved, the Assignor's new registration data is effectively changed. At this point, if configured, we send a Webhook notifying that the Analysis was approved. Note that an Assignor's registration update does not prevent new operations from being carried out with them.

Assignment Contract Formalization

To formalize the relationship between the Assignor and the Fund, an Assignment Contract governing this sale of assets must be signed. We provide an API that enables this process automatically.

The process involves the formalization request, based on a template, which internally triggers the contract creation and its submission for signature. The contract's products (for example, the assignment of a given asset type, or repurchase) are defined by the template. Once the contract is signed, each product is activated automatically — there is no activation call. At the end, we send the assignment_contract.product_status_change webhook with the key of the generated Assignment Configuration (assignment_configuration_key), the identifier that will be used later in the asset purchase and sale process. See Contract Webhooks.