> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-api/connect/available-resources/joint-resolution-6/changelog/2025/2025-02-11-adjust-fields-requirement.md).

# 2025-02-11 - Adjust RS6 Fields Requirement

Changes in data dictionary fields requirement, given understanding of RS6 Interoperability Committee.

The alteration of these fields **impact existing** fraud records and is **retroactive**.

| **Field**                                                                                | **Type of Change** | **Description**                                                                                                                                           |
| ---------------------------------------------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><code>informacoes\_bancarias\_destino</code><br><code>.agencia</code></p>             | Alteration         | <p>Change the field requirement rule.<br><strong>Previous</strong>: Required field;<br><strong>Current:</strong> Optional field.</p>                      |
| <p><code>informacoes\_bancarias\_destino</code><br><code>.codigo\_instituicao</code></p> | Alteration         | <p>Change the field requirement rule.<br><strong>Previous</strong>: Conditional field<strong>¹</strong>;<br><strong>Current:</strong> Required field.</p> |
| <p><code>informacoes\_bancarias\_destino</code><br><code>.conta</code></p>               | Alteration         | <p>Change the field requirement rule.<br><strong>Previous</strong>: Optional field;<br><strong>Current:</strong> Conditional field<strong>¹</strong>.</p> |
| <p><code>informacoes\_bancarias\_destino</code><br><code>.conta.tipo</code></p>          | Alteration         | <p>Change the field requirement rule.<br><strong>Previous</strong>: Conditional field<strong>¹</strong>;<br><strong>Current:</strong> Required field.</p> |
| <p><code>informacoes\_bancarias\_destino</code><br><code>.conta.numero</code></p>        | Alteration         | <p>Change the field requirement rule.<br><strong>Previous</strong>: Optional field;<br><strong>Current:</strong> Required field.</p>                      |

Are changed in the `SuspectedFraudOccurence` schema, used in the [Suspected fraud creation](https://docs.caf.io/caf-api/connect/available-resources/joint-resolution-6/suspected-fraud-creation.md) and in the [Suspected fraud query](https://docs.caf.io/caf-api/connect/available-resources/joint-resolution-6/suspected-fraud-query.md).

> **¹**: This field is **required** when `registro.atividade_relacionada` is equal to: 4, 5, 6, 7 or 8.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.caf.io/caf-api/connect/available-resources/joint-resolution-6/changelog/2025/2025-02-11-adjust-fields-requirement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
