> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/es/store-manager/configure-pos-and-store-manager/store-financials/setting-up-tender-rules.md).

# Reglas de cobro

Este tema describe cómo configurar reglas con respecto al tipo de cobro predeterminado que se usará al dar cambio a los clientes o al período de tiempo durante el cual los vales emitidos por la tienda siguen siendo válidos.

{% hint style="info" %}
Debe configurar los tipos de pago de su tienda antes de poder configurar las reglas de pago. Las reglas de pago son globales y se aplican a todos los equipos.
{% endhint %}

1. Haga clic en **Archivo** | **Configuración**.
2. Haga clic en la pestaña **Pago** .
3. En el campo **Cambio de pago predeterminado** , seleccione el tipo de pago predeterminado para proporcionar cambio a los clientes. Por ejemplo, si acepta tarjetas de débito y permite devolución de efectivo con las compras, seleccione Efectivo.
4. En el campo **Vencimiento del vale** campo, ingrese el número de días que tienen los clientes para usar un vale (por ejemplo, una tarjeta de regalo o un certificado de regalo) antes de que el vale deje de ser válido.

{% hint style="success" %}
Ingrese cero (0) en el campo Vencimiento del vale si no desea que el vale caduque.
{% endhint %}

5. Haga clic en **Guardar y cerrar**.


---

# 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.rmhpos.com/es/store-manager/configure-pos-and-store-manager/store-financials/setting-up-tender-rules.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.