> 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/approving-payment-methods.md).
# Approving Payment Methods
#### Abstract
This article covers the essential steps to review and approve newly added payment methods after a payee has completed the onboarding invitation. Approving payment methods ensures vendor or customer details are accurate and properly validated before any payments are processed. For example, when a supplier updates their address or contact information, approvers must confirm these changes to avoid payment errors and maintain accurate records.
In this guide, you will learn how to locate payment methods awaiting approval, verify the vendor or payee information, approve or reject the proposed details, and confirm the successful creation of an approved payment method.
#### Locating Payment Methods Pending Approval
Before approving a payment method, you need to know where to find any payee submissions waiting for your review. This ensures you can quickly access pending items and decide whether to proceed with approval or rejection.
Follow these steps to finalize the approval process for **Payment Methods**:
1. Begin by hovering over the **Charted** menu, then **AP Automation**, and clicking the **Home** tab.
2. Next, click **Payment Methods** option on the left navigation menu to open the list of all payment methods pending approval:
3. Click on the payment method pending approval in the approval queue to begin the review process. All payment method information will be found in the 'Requested Payment Method' section.
* Type can be ACH, International, or Check.
* Source can be either Manual if the payment method was manually added by your team, or invite if the information came directly from the vendor.
* For ACH payment methods, you can press the eye icon to display the full routing and account numbers.
* By default the **Make this the payee's preferred payment upon approval** checkbox is checked. It's generally recommended to make newly approved payment methods as a preferred payment method.
* Unselect this checkbox if you don't want to change the preferred payment method (for example, for a backup check payment method where ACH is the primary). \
3. The **Payee Information** section will have information like Payee Name, Vendor type, Contact Email, Contact Name, and Phone Number. For fields that are changing, you can reject the field if you prefer to keep the current field value (for example, if there's a typo). Uncheck the **Accept Requested** checkbox to preserve the current value
4. Click **Approve** or **Reject** to complete the payment method review process. Approved payment methods will be ready for payment and show up as **Approved** in a payee's payment method page, and rejected payments will show up as **Rejected**.
1. Preferred payment methods will be clearly marked with the **Preferred** tag.
5. You can always click into the payment method row in a payee's payment method page to view details about that payment, or review the pending payment method. This is another way to access the payment method review 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.charted.com/ap-automation/charted-features/payment-automation/approving-payment-methods.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.