> For the complete documentation index, see [llms.txt](https://academy.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pakk.io/school-of-erp/invoicing-and-payments/managing-payments.md).

# Managing Payments

Once the customer receives an invoice, the next step is to track and manage payments. ERP systems provide functionality to log payments, track outstanding amounts, and send payment reminders.

**Key Concepts in Payment Management:**

* **Payment Methods:** ERP systems track different payment methods, such as credit card, bank transfer, or cash.
* **Partial Payments:** If a customer only pays part of an invoice, the system tracks the remaining balance.
* **Overdue Payments:** Automated reminders can be sent to customers when payments become overdue.
* **Reconciliation:** Payments received are matched against the respective invoices, ensuring that financial records are accurate.

<figure><img src="https://2730446929-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcGTthTPJX2LiOOtMQ0VH%2Fuploads%2FbjgySnENHU941KpYmjk8%2FClipboard_10-18-2024_07.jpg?alt=media&amp;token=eaf83992-42b4-4dca-bf0d-ff2f72abced2" alt=""><figcaption><p>Payment tracking: Emailing Payment reminders in Pakk</p></figcaption></figure>


---

# 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://academy.pakk.io/school-of-erp/invoicing-and-payments/managing-payments.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.
