> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/invoicing-and-payments/invoices/payments-table-overview.md).

# Payments Table Overview

Find the right workflow to request, record, take, refund, and review invoice payments.

The Payments Table helps you request, record, refund, and review payments on an invoice.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-abe6b1870e32e9130383105c779a9753a0820915%2FScreenshot%202026-07-07%20at%209.07.36%E2%80%AFAM.png?alt=media" alt="Screenshot showing the Payments Table located between the Invoice and Options sections on an invoice"><figcaption></figcaption></figure>

***

## Choose a payment task

Use the Payments Table to track every payment activity on an invoice.

* [Record a Manual Payment](/support/invoicing-and-payments/recording-payments/how-to-manually-add-a-payment.md) — Record cash, check, or electronic transfer payments.
* [Create a Payment Request](/support/invoicing-and-payments/payment-requests/how-to-create-a-payment-request.md) — Request a deposit, progress payment, or balance from your customer.
* [Take a Credit Card Payment](/support/invoicing-and-payments/payments/manual-credit-card-payments.md) — Take a card payment directly on the invoice.
* [Take an ACH/EFT Payment](/support/invoicing-and-payments/payments/take-an-ach-eft-payment.md) — Take a bank payment directly on the invoice.
* [Resolving Payment Requests](/support/invoicing-and-payments/payment-requests/how-to-mark-a-payment-request-as-paid.md) — Review online payments or record an offline payment against a request.
* [Refund a Payment](/support/invoicing-and-payments/refund-a-payment.md) — Process full or partial refunds, or cancel a processing ACH/EFT payment.
* [Payment Receipts](/support/invoicing-and-payments/payment-receipts.md) — Download an invoice payment receipt.

***

## Payment statuses

**Requested** — A payment request was sent and is waiting on payment.

**Successful** — The payment was received and settled.

**Processing** — The processor is still confirming the payment. ACH or EFT payments can take up to 5 business days.

**Failed** — The processor declined the payment, or a processing ACH/EFT payment was cancelled. Manual payments do not fail.

**Refunded** — A paid payment was refunded.

&#x20;&#x20;

## Related articles

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Create and Send an Invoice</strong></td><td>Create invoices from estimates manually or automatically, then send them to customers for payment.</td><td><a href="/support/invoicing-and-payments/invoices/creating-invoices.md">Create and Send an Invoice</a></td></tr><tr><td><strong>Record a Manual Payment</strong></td><td>How to record manual payments like cash, check, or electronic transfers on invoices</td><td><a href="/support/invoicing-and-payments/recording-payments/how-to-manually-add-a-payment.md">Record a Manual Payment</a></td></tr></tbody></table>


---

# 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://help.paintscout.com/support/invoicing-and-payments/invoices/payments-table-overview.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.