> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-a-r/transactions.md).
# Transactions
Maitre'D transactions report provides you with customer address, account number, credit limit on the account and the date range for which you see the transactions. From the report filter window, you select the date range and customers needed.
**The following is a sample of the transactions report:**
**Date:**
Date the transaction took place
**Completed:**
Completed column displays a check mark if the transaction date is older then the last Finalize Statement operation. So this transaction cannot be printed on the customer statement anymore.
**Printed:**
Printed column display check mark if the transaction has been previously printed on the customer statement.
**Invoice Number:**
Invoice number column displays the reference number of the transaction entry. If this transaction is a invoice transaction from the POS, the check number is used, if this transaction entry is from the Back-Office, the reference field from the Add Transaction option is used.
**Transaction Type:**
Invoice:Indicates it was a check closed at the workstation to the account
Charge:Indicates it was a charge added to the account from the Back-Office
Credit:Indicates it was a credit (payment) applied to the account from the Back-Office
Payment received. Thank You. Indicates a payment against the account was done from the workstation
**Amount:**
$ Amount of the transaction
---
# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-a-r/transactions.md?ask=&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.