> 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/recording-payments/how-to-manually-add-a-payment.md).

# Record a Manual Payment

How to record manual payments like cash, check, or electronic transfers on invoices

Record cash, check, or electronic transfer payments directly on an invoice.

1\. Select **+Add/Request Payment** on the invoice and choose **Record Payment.**

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2FGfsiB3OfSD32dUSDig6m%2FScreenshot%202026-08-07%20at%2011.53.50%E2%80%AFAM.png?alt=media&amp;token=b677866e-1604-4247-98f2-1e9ac468a145" alt="Screenshot showing the Add/Request Payment pop-up with the Record Payment option"><figcaption></figcaption></figure>

2\. Enter the **payment method**, **amount paid**, and **payment date**. You can also add a customer note, such as a check number, and mark the payment as a deposit if needed.

3\. When you are done, save the payment.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2FLpvnYrWzjQ7DidV4b3o2%2FScreenshot%202026-08-07%20at%2011.55.06%E2%80%AFAM.png?alt=media&amp;token=2bee538b-436c-4c71-9bb8-f7de72f96c11" alt="Screenshot showing the Record Payment form with fields for payment method, amount, date, and notes"><figcaption></figcaption></figure>

4. The payment appears in the Payments Table with a **Successful** status

* Manual payments do not move into **Processing** or **Failed**.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2FZ4EhYsty9maDYHxEtKwM%2FScreenshot%202026-08-07%20at%2011.56.20%E2%80%AFAM.png?alt=media&amp;token=d1add203-68de-4303-8a34-6f97a66ad9f6" alt="Screenshot showing the recorded payment in the Payments Table with a Paid status"><figcaption></figcaption></figure>

{% hint style="info" %}
You can add your list of payment methods in settings. [Learn more](/support/customization/templates-and-presets/adding-payment-methods.md).
{% endhint %}

&#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>Resolving Payment Requests</strong></td><td>Process online payment requests automatically, or record payments taken manually.</td><td><a href="/support/invoicing-and-payments/payment-requests/how-to-mark-a-payment-request-as-paid.md">Resolving Payment Requests</a></td></tr><tr><td><strong>Customer Payment Experience</strong></td><td>See what customers experience after receiving a payment request.</td><td><a href="/support/invoicing-and-payments/payment-requests/how-customers-make-a-payment.md">Customer Payment Experience</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/recording-payments/how-to-manually-add-a-payment.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.
