> 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/tarjetas-de-flota-compatibilidad-con-mudflap/reportes-de-la-compatibilidad-con-mudflap.md).

# Reportes de la compatibilidad con Mudflap

Mudflap usa el mismo conjunto estándar de reportes de flota del lado de la terminal que los demás proveedores comerciales de flota:

* **Resumen diario de terminal** -- totales a nivel de día para la actividad de Mudflap (pensados principalmente para uso de back office).
* **Detalle** -- detalle a nivel de transacción (pensado principalmente para uso de back office).
* **Detalles de excepciones del día** -- transacciones que no pudieron finalizarse con Mudflap, con el resultado del fallo, el monto, el número de rastreo (STAN) y el número de cuenta, además de los totales de excepciones. Este es el reporte que debe consultarse cuando una finalización no pudo llegar a Mudflap.

Para imprimir el reporte de excepciones en el punto de venta:

{% stepper %}
{% step %}

## Abra el menú de red

Desde las funciones de CSR, abra el menú de red.
{% endstep %}

{% step %}

## Seleccione EPS Secure Report

Seleccione EPS Secure Report.
{% endstep %}

{% step %}

## Abra el reporte de excepciones

Seleccione MudFlap Report y luego Exception Report.
{% endstep %}
{% endstepper %}

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/ytd5rFOM6DzLfQetPV3Q/images/image2.png)

*Reporte de excepciones de Mudflap de muestra.*


---

# 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/tarjetas-de-flota-compatibilidad-con-mudflap/reportes-de-la-compatibilidad-con-mudflap.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.
