> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/feature-references-lac-es/referencias-de-funciones-y-productos/estacion-de-trabajo-del-administrador/estacion-de-trabajo-de-informes-del-gerente/imprimir-detalles-de-variacion.md).

# Imprimir detalles de variación

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/cwayZR0SY2uDYPZSRQT0/Unknown%20image)

**Detalles del reporte**

* *Número de tienda: Número de tienda.*
* *Período: Período para el cual se generó el informe.*
* *Apertura: Fecha y hora de apertura del período.*
* Cierre: *Fecha y hora de cierre del período.*
* N.º de secuencia: Número de secuencia.
* *Nombre de ID: Nombre del cajero que realizó la transacción, número de caja y número de secuencia.*
* *MOP: Método de pago utilizado para la transacción.*
* Total ECR: Total de la caja registradora electrónica.
* Real: El monto ingresado por el cajero que cierra después de contar el MOP en el cajón.
* Corrección del gerente: El monto que corrigió el gerente.
* Variación: Monto real - Corrección del gerente.


---

# 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.verifone.com/feature-references/feature-references-lac-es/referencias-de-funciones-y-productos/estacion-de-trabajo-del-administrador/estacion-de-trabajo-de-informes-del-gerente/imprimir-detalles-de-variacion.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.
