> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/pt-br/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/bulk-add-payout-groups-to-a-template-term.md).

# Adicionar em massa grupos de pagamento a um termo de modelo

Se você já sabe quais grupos de pagamento deseja criar, pode carregá-los em lote no termo modelo.

1. Na barra de navegação à esquerda, selecione ![](https://526234278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → Contratos → Termos modelo**.
2. Selecione **Criar termo modelo**.
3. No menu *Tipo de evento* ![](https://526234278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-c2cb550b55c51ea1eeff0acbd6f437a03b621a2c%2F60d033ae8a04c14498d5229c3c0160ac05feea7f605dbd770741793c900469f0.svg?alt=media) **\[Menu suspenso]**, selecione o **Tipo de evento** para o qual este termo modelo será usado.
4. Para adicionar em lote *grupos de pagamento*, selecione ![](https://526234278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[Ativar]** **Configurar grupos de pagamento personalizados** → **Importar**.

   * Carregue um arquivo .XLS, .XLSX ou .CSV.

     <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Observação:</strong> O número máximo de grupos de pagamento que você pode carregar de uma só vez é 4.000. Se o arquivo exceder esse limite, será necessário dividi-lo em vários carregamentos.</p></div>
   * Consulte [Formato de arquivo dos grupos de pagamento](https://docs.google.com/spreadsheets/d/1EMKTJr24qSHVtFzPkBpWg_wFF7IK94VGCkdyi3vyHCU/edit?usp=sharing) para ver os valores aceitos e um exemplo de arquivo na planilha 2.
   * Se você tiver várias regras de pagamento, poderá arrastá-las para alterar a ordem depois de carregá-las.
   * Para definir várias regras em uma mesma ordem, coloque cada regra entre colchetes ( `[]` ) e conecte-as com `AND`, como mostrado abaixo:

     <div data-with-frame="true"><figure><img src="https://526234278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-a46fcfadd0dab407fb1fa3f6095c675ad07a157c%2Fc5d0c6448193f39807f73288d3f14ae0dbe50e102adaf48079553462170f0849.png?alt=media" alt=""><figcaption></figcaption></figure></div>

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Importante:</strong> O formato do arquivo enviado deve incluir os cabeçalhos de coluna <em>Tipo de pagamento</em>, <em>Valor do pagamento</em>, <em>Regras</em>, e <em>Bônus</em>. Se um ou mais desses cabeçalhos não corresponderem exatamente, o envio resultará em um erro.</p></div>
5. Continue criando seu termo modelo.


---

# 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://help.impact.com/brand/pt-br/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/bulk-add-payout-groups-to-a-template-term.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.
