> 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-faqs/payment-automation/what-happens-to-payments-when-i-deactivate-a-payee.md).

# What happens to payments when I deactivate a payee?

Unreleased payments to the payee are held until you reactivate the payee or cancel the payments. Where they are held depends on **Exclude Unavailable Payees from Charted** in General settings: when it is off, they move to Not Ready for Release with the reason Payee Deactivated; when it is on, they do not flow into Payment Automation.

* You can still create new bill payments for the payee, but they cannot be released until you reactivate.
* Payments already released continue and complete normally.
* When you reactivate, held payments return to Ready for Release automatically. Cancel any you do not want released before you reactivate.

Deactivation keeps the payee's onboarding status and bank details, so reactivating does not mean onboarding again. Invitations are unaffected: you can still send them and the payee can still accept them. Deactivation does not change approval status, and it is separate from NetSuite's own inactive status on the vendor. Deactivated payees are hidden from the Payees list until you filter for Inactive. You can deactivate or reactivate at any time.

{% hint style="info" %}
See [Onboarding payees](https://docs.charted.com/ap-automation/charted-features/payment-automation/onboarding-payees.md).
{% endhint %}


---

# 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.charted.com/ap-automation/charted-faqs/payment-automation/what-happens-to-payments-when-i-deactivate-a-payee.md?ask=<question>&goal=<user_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.
