> 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/canada-doc-center/applications/secure-payment/payment-standalone-mode/transactions/process-a-settlement.md).

# Process a Settlement

### Process a Settlement

When you process transactions, they are saved on the terminal and on the authorization server. Funds collected are only transferred to your merchant bank account after you perform a reconciliation between the terminal and server; this reconciliation process is the settlement.

By default, the terminal automatically closes the batch of transactions and processes the settlement at the end of the business day. You can configure the automatic settlement through the [*Automatic Report Printing*](/payfacto-knowledge/canada-doc-center/applications/secure-payment/payment-standalone-mode/terminal-configuration/automatic-report-printing.md#automatic-report-printing) procedures.

You can choose to process a settlement before the end of the business day. When you process a settlement, the system validates that the transactions processed on the terminal match those on the authorization server before  beginning the process of transferring the funds to your merchant bank account.

As you process transactions, the terminal and authorization server track the transaction history (operations) in the open batch. When you process a settlement, you close the open batch and clear the transaction history on the terminal and authorization server.

{% hint style="info" %}
NOTE: When you process a settlement, the terminal is unable to perform any other transaction at that time.
{% endhint %}

#### **To print a summary list of transactions for the current batch:**

1. From the main screen, touch **Settings**.<br>

<figure><img src="https://3906380439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6flXtoPk5hDLO7lHpA2z%2Fuploads%2FdhLEU2RKoXZNc6VLIw2n%2FMainSaleScreen_SettingsButton.png?alt=media&amp;token=a6116f3b-758e-4deb-9e60-b1f28a80a44a" alt=""><figcaption></figcaption></figure>

2. Enter the merchant password and touch **Confirm**.
3. In the **Transaction management** section, touch **Settlement**.<br>

<figure><img src="https://3906380439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6flXtoPk5hDLO7lHpA2z%2Fuploads%2FMMcOhqHPnDHhxtKRY9qD%2FSettingsMenu_Settlement.png?alt=media&amp;token=9938b3c5-8605-4179-9bab-5bee704bdfec" alt=""><figcaption></figcaption></figure>

4. Touch the **Confirm** button to proceed with the settlement. The terminal prints the *Settlement Report*.


---

# 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/canada-doc-center/applications/secure-payment/payment-standalone-mode/transactions/process-a-settlement.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.