> For the complete documentation index, see [llms.txt](https://docs.charted.com/ap-automation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charted.com/ap-automation/charted-features/payment-automation/navigating-the-ready-for-release-queue.md).
# Navigating the Ready for Release Queue
After a bill payment is created in *NetSuite*, the final step before disbursement is managing payments through the *Ready for Release* queue. This queue only displays payments that meet key requirements, such as vendor onboarding, funding source linkage, and checklist completion. It also includes tools for filtering, selecting, and exporting payment data to support efficient payment processing.
This article provides a step-by-step guide to accessing and navigating the *Ready for Release* queue in **Charted**. It outlines how payments flow into the queue, how to manage and organize them, and how to use available features to streamline release operations.
### Access and Use the Ready for Release Queue
The **Ready for Release** queue collects payments that meet all required criteria and are ready to be released.
These steps explain how to navigate and manage payments within this view.
1. Once a bill payment is created in *NetSuite*, it may take up to 15 minutes to appear in the Ready for Release queue. \
2. To access the **Ready for Release** queue, hover over **Charted**, then **AP Automation**, and click the **Home** tab:\
3. Next, click the **Release Payments** tab from the left sidebar menu:\
4. You can control the number of rows displayed on this page by choosing from the **Items per page** dropdown. \
\
\
5. At the top of the page, you’ll see three tabs: **Ready for Release**, **Not Ready for Release**, and **Release in Process**:
The **Ready for Release** tab includes bill payments that have passed all requirements, such as a linked funding source, onboarded payee, and a completed checklist.\
\
The **Not** **Ready for Release** tab include payments related to payees who haven't responded to an invite, a payment method still pending approval, or an unlinked funding source.\
\
The **Release in Process** tab includes all payments that have been released in the last 60 seconds. After 60 seconds these payments will be released and removed from the queue.
6. Payments are grouped by **BUSINESS ENTITY**, and this view is collapsible. Click the arrow icon to expand or collapse each group and view all related payments:
7. You can select all payments under a business entity by clicking the header row radio button, or choose individual payments as needed:
8. If you prefer to have transactions grouped by business entity turned off, you can view the transactions as a flat file by pressing the 'Grouped' button in the top right.\
9. The total aggregated amount and number of payments selected is displayed at both the business entity level and at the bottom of the page. \
10. To filter the list, click on the field form you'd like to filter on, and select the filter applied using the dropdown:\
\
\
\
Only payments that match the active filter will be shown and available for release. Payments outside the active filter can't be released. This is to ensure that hidden payments are not accidently released.
11. To clear all active filters, press the 'Clear' button
12. You can also export the data by clicking **Export to CSV**. This downloads the table with active filters applied, for use in Excel or downstream business intelligence systems.
This concludes the overview of navigating the **Ready for Release** queue.
---
# 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.charted.com/ap-automation/charted-features/payment-automation/navigating-the-ready-for-release-queue.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.