> 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/~/revisions/5mWfap1wj08VLBd4NLdS/charted-faqs.md).

# Charted FAQs

Find answers to common questions about Invoice AI, Payment Automation, and Charted email handling.

### FAQ categories

* [Invoice AI Setup and Configuration](/ap-automation/~/revisions/5mWfap1wj08VLBd4NLdS/charted-faqs/invoice-ai.md) for Invoice AI setup, capture notifications, and due date issues.
* [Payment Automation](/ap-automation/~/revisions/5mWfap1wj08VLBd4NLdS/charted-faqs/payment-automation.md) for ACH, check processing, business entity verification, and international payments.
* [Charted Email Handling](/ap-automation/~/revisions/5mWfap1wj08VLBd4NLdS/charted-faqs/charted-email-handling.md) for email delivery and approval-email behavior.

### Related resources

* [Charted Configuration](/ap-automation/~/revisions/5mWfap1wj08VLBd4NLdS/charted-configuration.md) for full setup and admin guides.
* [Charted Features](/ap-automation/~/revisions/5mWfap1wj08VLBd4NLdS/charted-features.md) for product overviews and workflow summaries.
* [Charted Support](/ap-automation/~/revisions/5mWfap1wj08VLBd4NLdS/charted-support.md) if you need technical or configuration help.
* [Release Notes](/ap-automation/~/revisions/5mWfap1wj08VLBd4NLdS/release-notes.md) for recent changes and fixes.


---

# 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/~/revisions/5mWfap1wj08VLBd4NLdS/charted-faqs.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.