# Reports and Transaction Backups

| Revision Version | Revision Date | Author    | Description            |
| ---------------- | ------------- | --------- | ---------------------- |
| 1.0              | 12/10/2018    | Emily\_R1 | Original documentation |
| 1.1              | 02/22/2019    | CrystalP2 | Minor update           |
| 1.2              | 12/13/2019    | CrystalP2 | Update support info    |

**Date of Last Review/Revision: DECEMBER 13, 2019**

***

### REPORTS & TRANSACTION BACKUPS

The purpose of this document is to provide details on backing up or saving reports and transaction logs to your computer. Reports and Transactions are stored on the Commander series of site controllers for a minimum of 30 days. If you wish to keep transactions or reports for longer periods, please review the following information.

***

### Reports

Anytime a report is opened or viewed through the Report Navigator program, it is automatically cached to the computer it’s viewed on.

**Note:** Reports that are not viewed or opened on the computer are NOT saved. Only the reports that are opened/processed in the program are stored on the local computer.

The report cache is stored in:

C:\Users(YourUserName)\Documents\VeriFone\SRNTemp

The user’s name that is logged in will be utilized for **(YourUserName).**

These files can be backed up and stored to an external drive or another location. If you’ve had previous versions of the Site Management Suite (SMS) installed on your computer, then these files may also be found in other locations.

To view these reports within the Report Navigator program, simply log in with your credentials, go to **Tools > Report Cache** and open them in any available web browser that is installed on your computer.

***

### Transactions

Transactions (T-Logs) are stored on the site controller and viewed through the **Transaction Manager** program.

There is an **Archive** feature in Transaction Manager’s Tools menu. Use the archive options to save transaction logs to the computer the program is opened on.

{% stepper %}
{% step %}

### Archive New Transactions

* Backs up transactions that have been stored on the site controller **since the last archive**.
* If there was no previous archive, this option archives all transactions.
  {% endstep %}

{% step %}

### Archive All Transactions

* Backs up **all** transactions from the site controller to the configured location.
  {% endstep %}
  {% endstepper %}

**Tip:** The archive destination can be modified under **Tools > Options** in Transaction Manager. The directory can point to any drive visible to the computer (internal or external).

{% hint style="warning" %}
Technicians must not store site Archives on their installing laptop.

Also: Technicians must not enable **Archive New Transactions at Log On** on an installing laptop — enabling this will archive site transactions to that laptop when Transaction Manager is used on-site.
{% endhint %}

There is an optional setting in Transaction Manager: **Archive New Transactions at Log On** will automatically archive to the configured location when a user logs into Transaction Manager. There is **no** automatic timed archive function available.

To view archived transaction logs: in Transaction Viewer or Transaction Manager select **File > Open Local TLog** — this opens a file dialog so you can locate the archived transactions.

***

### Notes & Important Items

* Reports that are only present on the site controller and never opened in Report Navigator will **not** be stored on the local computer — only reports that are opened are cached locally.
* If you need transactions/reports retained longer than the controller’s 30 days, archive them to your backup location.
* The archive directory is configurable in Transaction Manager: **Tools > Options**.

***

***

Document images in this page are embedded as base64; per import rules they were preserved unchanged.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-and-integrated-pos/manuals/reports-and-transaction-backups.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.