# Resolving Not Ready for Release Issues
### Abstract
Payments may appear in the *Not Ready for Release* queue when they fail to meet specific requirements, such as missing a funding source or currency not supported. This queue provides administrators with visibility into problems that must be resolved before payments can be released. For example, if a vendor has not selected a preferred payment method, that issue will appear here for correction.
This article explains how to locate and resolve issues that cause payments to enter the *Not Ready for Release* queue.
### Accessing the Not Ready for Release Queue
Before resolving any issues, administrators need to locate the **Not Ready for Release** section within the payment release screen. This view surfaces all payee payments that failed automatic qualification due to a missing or incorrect configuration.
1. To access the **Not Ready for Release** queue, hover over **Charted**, then **AP Automation**, and click the **Home** tab:\
2. Next, click the **Release Payments** tab from the left sidebar menu, which will take you to the **Release Payee Payments** page:\
3. Once you’re on the **Release Payee Payments** screen, locate the **Not Ready for Release** queue:\
\
4. Review all payments that aren't ready for release by referring to the **Reason** column. Here are some of the most common reasons and resolutions:
| Reason | Resolution |
| --------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The vendor hasn't been onboarded into Charted Payments as a valid payee | Transactions will only flow to Charted for vendors that have been onboarded as a Payee. Follow the [import payee process](/ap-automation/charted-configuration/payment-automation/importing-and-managing-payees-vendors.md) to invite your payee and add and approve a payment method. |
| The GL account on the bill payment is not linked to a funding source within Charted | To resolve this, please follow the steps [here ](/ap-automation/charted-configuration/payment-automation/linking-bank-accounts-to-your-netsuite-gl-accounts.md)to link bank accounts. Then, void and re-create your bill payment. |
| The payee has not completed the invite to provide payment information or you have not approved the supplied payment method. | Review the Payee and re-send the invite to remind the Payee to complete their information or approve the payment method provided |
| The payment is over the maximum allowed amount. | Currently payments are limited to $500,000. If you need to pay a payee more than the maximum allowed amount, you can split into separate bill payments. |
| The payment is not in a supported currency | Payments Automation only supports US Dollar transactions. |
| ACH Payments not allowed | ACH Payments needs to be enabled on the business entity |
| No Preferred Payment Method | Set [preferred payment](/ap-automation/charted-features/payment-automation/managing-preferred-payment-methods.md) method for the vendor |
\
This concludes the process of resolving **Not Ready for Release** issues.
---
# Agent Instructions: 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:
```
GET https://docs.charted.com/ap-automation/charted-features/payment-automation/resolving-not-ready-for-release-issues.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.