> 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/features-and-products-references/full-service-attendant/reporting-full-service-attendant/eps-network-reports.md).

# EPS Network Reports

## FSA Totals by Card Type Report

The FSA Totals by Card Type Report contains a list of all cards used in that terminal batch, count and total sales for each card.\
Electronic Payment System (EPS) based reports are available in the EPS Network Report menu.

**POS EPS Network Reports Procedure**

{% stepper %}
{% step %}
From Sales > go to: CSR Func > Network Menu.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2F6LYgQ97Utdww9vZEOKvn%2Fimage.png?alt=media&amp;token=757f62f2-4573-48bd-bc52-95c3d20fa037" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select \[EPS Network Reports].

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FcgQ7IIOvMaT1VZkiU2Oh%2Fimage.png?alt=media&amp;token=7196da34-635c-423d-b55c-a13ed179a284" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select \[FSA Totals by Card Type Report].

The EPS Network Report prints.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FDiMvyp41HHRvhKEoJ8Cx%2Fimage.png?alt=media&amp;token=b6a048cb-055e-400c-b99e-8e259c756633" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

***Report Details:***

* TITLE: FSA Totals by Card Type Report
* PRINTED:
  * MM/DD/YY: Date in month, date year format.
  * HH:MM:SS: Time in hour, minutes, and seconds.
* WORKSTATION ID: Identifies the POS where the report was generated.
* TERMINAL BATCH ID: Identifies the terminal batch number.
* TERMNAL BATCH OPEN: Identifies when the batch was opened.
  * MM/DD/YY: Date in month, date year format.
  * HH:MM:SS: Time in hour, minutes, and seconds.
* TERMINAL BATCH CLSE: Identifies when the batch was closed.
  * MM/DD/YY: Date in month, date year format.
  * HH:MM:SS: Time in hour, minutes, and seconds.
* CARDTYPE: Identifies the card type used in this terminal batch.
* COUNT: An FSA transaction updates the transaction count for that card type.
* SALES: A FSA transaction updates the amount a for that card type.
* TOTAL: Total includes the summary count of transactions and sales amount for all FSA transactions approved by this host for this terminal batch.


---

# 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/features-and-products-references/full-service-attendant/reporting-full-service-attendant/eps-network-reports.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.
