> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/interfaces/backoffice/transactions/batch-close.md).
# Batch Close
Under Batch Close, you can view present and past booking periods, export said periods, among other things.
### What is a Batch Close?
The Batch Close, or daily closing, is executed once each day on every terminal that is connected to your Saferpay account. By default, this happens automatically at 10 pm CET/CEST. During this process, all transactions that have passed through the capture or booking are filed with the payment method processor in order to initiate the cash flow.
## Overview
The overview shows a list of all your booking periods, their opening and closing dates, the number of transactions filed, as well as the respective Saferpay terminal.
## The Search
By clicking on the **Advanced Search icon** in the top right of the overview, you can filter this view by a date, the state of the period, or a terminal, or you can also search for a specific booking period by entering its ID.
## Export
By clicking on **Export** for a given booking period, you can download an Excel .xlsx file. Similar to the Backoffice Export, it contains a list of transactions. However, in this case only the transactions that are filed under this specific booking period.
#### Example
{% file src="/files/-McIp\_KCjz4uD3Q99K84" %}
Batch Close Export example
{% endfile %}
## Details
When you click on **Details**, you'll get an overview of the given booking period. That includes the opening date, the date of closing, the terminal the booking period is attached to, the number of instructions, and then a listing of the amount made per currency and payment method.
### Details
If you want, you can get a listing of all transactions included in a given booking period if you click on **Show transactions** in the Detail view. This will lead you to the [Transaction Journal](/home/interfaces/backoffice/transactions.md#journal), displaying the connected transactions.
## Triggering the Batch
### Via API
If desired, the Batch Close can also be triggered via the Saferpay API. The request necessary for this is called [Batch Close](http://saferpay.github.io/jsonapi/index.html#ChapterBatch).
{% hint style="warning" %}
Before you can use the API, you need to disable the daily closing in the Saferpay Backoffice via [Settings => Terminals](/home/interfaces/backoffice/settings.md#payment-means-terminals) for the respective terminal. Closing should be carried out only once a day.
{% endhint %}
### Via the Backoffice
You can also trigger the batch by clicking on the **Batch Close** button on the Booking period details page.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.saferpay.com/home/interfaces/backoffice/transactions/batch-close.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.