> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/accounting/bank-reconciliation/bank-statement-centre/bank-statement-centre-fields.md).
# Bank Statement Centre Fields
### Overview
The Bank Statement Centre provides header-level actions, search fields, and grid columns that allow users to manage imported bank statements and bank statement transactions. Depending on the selected **Search By** option (**Bank Statement Header** or **Bank Statement Detail**), the displayed columns change to provide either statement-level or transaction-level information.
### Header Level Search Fields
These fields allow users to filter and locate bank statement records.
| Field | Description |
| --------- | --------------------------------------------------------------------------------------------- |
| Bank Feed | Filters records based on the selected bank account/feed. |
| Search By | Allows users to switch between **Bank Statement Header** and **Bank Statement Detail** views. |
### Header Level Actions
The following actions are available in the Bank Statement Centre.
* **Refresh Transactions:** Retrieves the latest imported bank statement transactions for the selected bank feed.
### Header Level Icons
These features provide quick actions for managing bank statement records.
* **Refresh:** Reloads the latest bank statement records based on the selected filters.
* **Save:** Saves the current grid layout and user preferences.
* **Search:** Searches records using the selected criteria.
* **Columns:** Allows users to customize the columns displayed in the grid.
* **Download:** Export bank statement information in supported formats.
* **Advanced Search:** Enables advanced filtering using specific conditions such as column name, operator, and value.
### Bank Statement Header Columns
The following columns are available when **Search By** is set to **Bank Statement Header**.
| Field | Description |
| -------------- | --------------------------------------------------------------------------------- |
| Import Date | Displays the date on which the bank statement was imported. |
| Start Date | Displays the starting date covered by the bank statement. |
| End Date | Displays the ending date covered by the bank statement. |
| Start Balance | Displays the opening balance of the imported bank statement. |
| End Balance | Displays the closing balance of the imported bank statement. |
| Status | Indicates whether the bank statement has been reconciled or remains unreconciled. |
| Is Reconciled? | Indicates whether the bank statement has been fully reconciled. |
| Type | Displays the imported bank statement file type (for example, CSV). |
### Bank Statement Detail Columns
The following columns are available when **Search By** is set to **Bank Statement Detail**.
| Field | Description |
| ------------------- | ---------------------------------------------------------------- |
| Account Name | Displays the bank account associated with the transaction. |
| Post Date | Displays the transaction posting date. |
| Type (Debit/Credit) | Indicates whether the transaction is a debit or credit entry. |
| Description | Displays the transaction description imported from the bank. |
| Category | Displays the category assigned to the transaction, if available. |
| Amount | Displays the transaction amount. |
| Currency | Displays the transaction currency. |
| Transaction Status | Displays the processing status of the imported transaction. |
| Status | Displays the reconciliation status of the transaction. |
| Reconcile Date | Displays the date and time when the transaction was reconciled. |
| Reconcile Source | Displays the user or source that performed the reconciliation. |
| Type | Displays the imported file type. |
| Is Reconciled? | Indicates whether the transaction has been reconciled. |
### Recover Deleted Statement Lines
In the **Bank Statement Detail** view, users can delete individual bank statement transaction lines using the **Delete** icon available at the end of each transaction record. This is useful for removing incorrectly imported or unwanted statement lines without affecting the remaining transactions in the bank statement.
Deleted bank statement lines are not permanently removed. Instead, the **Delete** icon is replaced with a **Recover** icon, allowing users to restore the deleted transaction whenever required. Clicking the **Recover** icon reinstates the bank statement line and makes it available again for reconciliation.
#### **Workflow:**
**Step 1:** Go to **Menu → Accounting → Bank Statement Centre**.
**Step 2:** Select the required **Bank Feed** and choose **Bank Statement Detail** from the **Search By** dropdown.
**Step 3:** Locate the bank statement transaction line that you want to delete and click the **Delete** icon at the end of the row.
**Step 4:** The selected transaction line is marked as deleted, and the **Delete** icon changes to the **Restore** icon.
**Step 5:** To restore the deleted transaction, click the **Restore** icon.
{% hint style="info" %}
Reconciled bank statement transactions cannot be deleted directly. If the transaction is already reconciled, click the **Reconciled** icon displayed in the **Is Reconciled?** column to open the **Reconciled Transaction Details** window.
Click **Unreconcile** to remove the reconciliation. Once the transaction has been unreconciled, you can delete it using the **Delete** icon.
{% endhint %}
#### FAQs
#### How are imported bank transactions categorized? Does XoroERP assign the categories, and can they be edited?
Imported bank transactions are categorized based on the information provided by your financial institution.
XoroERP uses a third-party banking integration service, such as **Flinks**, to securely import bank transaction data directly from your bank. The transaction details—including the assigned category and other banking information—are retrieved exactly as supplied by the bank through the integration service.
XoroERP does **not** assign or modify these categories. Since the category information originates from the bank and is synchronized through the third-party integration, it is **read-only** within XoroERP and cannot be edited or changed.
**Key Points**
* Transaction categories are provided by your bank.
* XoroERP imports the category information through the third-party banking integration (for example, Flinks).
* XoroERP does not generate or alter the transaction categories.
* Imported categories are read-only and cannot be modified within XoroERP.
#### **Is it better to void or delete a bank deposit amount if a correction is needed?**
\
If you need to correct an amount in a bank deposit, you do not need to void or delete the entry. The **Amount** field in the **Bank Deposit Lines** section is editable. Simply click the field and update the amount as required.
#### If a bank deposit is voided, do the payments appear back in **Undeposited Funds**?
\
Voiding a bank deposit permanently deletes the bank deposit from the system. However, the documentation does not confirm whether the payments automatically reappear in **Undeposited Funds** after the deposit is voided.
If a correction is required, void the bank deposit and then check **Undeposited Payments** to verify whether the original payments are available for redeposit. If needed, recreate the bank deposit.
#### How should I record a bank deposit when the amount deposited into my account is reduced by bank fees or other deductions?
\
You can record the deposit in **Bank Deposit** and account for the fee or deduction within the deposit itself. Add the undeposited payments as usual, enter the amount that actually reached the bank, and use the **Cash Back Account**, **Cash Back Memo**, and **Amount** fields to record the applicable fee or deduction.
If the deposit line amount itself needs correction, the **Amount** field is editable and can be updated directly.
---
# 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.xorosoft.com/xoroerp-1/accounting/bank-reconciliation/bank-statement-centre/bank-statement-centre-fields.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.
