> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/close-management/bulk-reclass.md).
# Bulk Reclass
Bulk Reclass allows you to change the GL account or custom fields, such as Department, Location, or Class, across multiple transactions at once.
### Find and Reclassify Transactions
Follow these steps to find and reclassify transactions in bulk:
1. Go to **Close Management > Transaction Lines**.
2. Use the dropdown to select the transaction criteria, then click **Run Query**.
3. Select all or individual transactions you want to reclassify.
4. Select **Reclassify**.
5. Choose the new accounts and/or field values in the side panel.
6. Click **Reclassify** to confirm.
The selected transactions are updated with the new classification.
### Frequently Asked Questions (FAQ)
What types of transactions can be reclassified?
Manual Journal Entries, Bills, Charges, Reimbursements, and Vendor Credits.
Does selecting all only choose what is on the page, or all results?
Selecting all only selects what is visible on the page, up to 100 lines at a time.
### See Also
To learn more about reclassifying transactions in **Rillet**, review this article:
* [**Reclassify Transactions**](/EjmEP4KZ9BVp9j2ho4Mh/accounts-payable/vendors/reclassify-transactions.md)
---
# 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.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/close-management/bulk-reclass.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.
