Introduction
This section brings together the registrations made by a manager (manager-api) or consultant (consultant-api) on behalf of their quotaholders, covering the three investor types this integration can register:
| Type | person_type / investor_sub_type | What it is |
|---|---|---|
| Natural Person (PF) | natural_person | Natural person investor |
| Legal Entity (PJ) | legal_person + investor_sub_type: default | Investing company — includes financial_institution |
| Investment Fund | legal_person + investor_sub_type: fund_class | Fund class with its own CNPJ (FIMs, FIAs, FIDCs and others), which invests funds on behalf of its quotaholders |
The registration covers sending registration data, address, net worth, bank accounts, suitability, signer groups, documents, related parties and, when applicable, investor owner, up to the triggering of the registration analysis by QI Tech. The required steps vary by type — each following page indicates what applies to PF, PJ and fund.
It is important to note that, for PF and PJ, the signature is always performed exclusively by the investor or legal representative identified during the analysis.
What each profile performs
The manager (manager-api) and the consultant (consultant-api) do not expose the same routes. Before planning the integration, check what your profile performs:
| Step | Manager | Consultant |
|---|---|---|
| 1. Create Investor | ✅ | ✅ |
| 2. Send Registration Data | ✅ | ✅ |
| 3. Send Address | ✅ | ✅ |
| 4. Send Net Worth | ✅ | ✅ |
| 5. Send Bank Accounts (and set main, change status) | — | ✅ |
| 6. Send Suitability | ✅ | ✅ |
| 7. Send Signer Groups (and set default, change status) | — | ✅ |
| 8. Send Investor Documents | ✅ | ✅ |
| 9. Create Related Parties (and change status) | ✅ | ✅ |
| 10. Send Related Party Documents | ✅ | ✅ |
| 11. Send for Analysis | ✅ | ✅ |
| List investors | ✅ | ✅ |
| Query investor, registration analysis, analysis in progress and document batches | — | ✅ |
| List feedbacks | — | ✅ |
- Own fund classes only. Through the manager, the data entry steps (registration data, address, net worth, suitability, documents, related parties) and sending for analysis are only accepted for fund classes of which it is the manager linked to the registration. For other investors, the call is rejected with
QIT000011. - No bank accounts or signer groups.
manager-apihas no working route for these steps. Since sending for analysis requires at least one active bank account (IVR000178), the manager cannot complete the first registration of a fund class on its own: talk to the integration team before you start. When updating a fund class that is already registered, the bank accounts from the previous analysis are reused.
If your flow as a manager depends on something outside this, talk to the integration team at integracao.dtvm@qitech.com.br before planning the registration.
Through the manager (manager-api), the creation of a fund class is only accepted if the manager's CNPJ appears at the CVM as manager or administrator of the class; otherwise, the call is rejected with IVR000260.
In addition, the administrator and the manager of the class (according to the CVM) must be registered as investors at QI Tech; without that, the fund class registration does not move forward. If this is your case, talk to integracao.dtvm@qitech.com.br.
Only classes in operation (operational) at CVM can be registered. Classes in the pre-operational phase, closed, canceled, merged or in any way non-operational are rejected in the analysis.
The classification is read from the CVM public database based on the CNPJ provided when the investor is created. If the CNPJ is not in the CVM database, the field remains undefined and the submit is rejected with IVR000068 — in sandbox, use the CNPJ of a class actually registered and in operation.
Registration Flow
Which steps apply to each type
| Step | PF | PJ | Fund class |
|---|---|---|---|
| 1. Create Investor | ✅ | ✅ | ✅ |
| 2. Send Registration Data | ✅ | ✅ | ✅ (corporate name, incorporation date and net worth come from CVM) |
| 3. Send Address | ✅ | ✅ | ⏭️ skipped |
| 4. Send Net Worth | ✅ | ✅ | ⏭️ skipped |
| 5. Send Bank Accounts | ✅ | ✅ | ✅ |
| 6. Send Suitability | ✅ | ✅ (required for retail) | ⏭️ skipped |
| 7. Send Signer Groups | ✅ | ✅ | ⏭️ skipped |
| 8. Send Investor Documents | ✅ | ✅ | ⏭️ skipped |
| 9. Create Related Parties | optional | ✅ required | ⚠️ only if exclusive |
| 10. Related Party Documents | optional | ✅ required | ⚠️ only if exclusive |
| 11. Send for Analysis | ✅ | ✅ | ✅ |
| 12. Document Signature | ✅ | ✅ | ✅ |
Address, net worth, suitability, signer groups and investor documents are not part of a fund class registration — none of them is required at submit, and the corresponding steps can be skipped entirely.
The data supporting the analysis comes from another source: corporate name, incorporation date, net worth and the links with the administrator and the manager are filled in automatically from the CVM public database when the registration is sent for analysis. The fund is represented by these investor owners, not by legal representatives.
Related parties and their documents are required when, and only when, the class is exclusive at CVM. In that case at least one related party of type exclusive_investor is required, and the summed equity interest must total exactly 100%.
For a non-exclusive class, skip steps 9 and 10 — no related party is needed. The exclusive character (exclusive_fund_class) is automatically derived from the CVM class when the investor is created; see Create Related Party — Requirements by investor type for the full matrix.
In the following subsections we will go through each of the steps required to complete these registrations, with the differences between PF, PJ and fund class indicated on each page.