[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# List payment entries

> Payment entries with party, amount, date, reference and state. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/erpnext/list_payment_entries

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Payment entries with party, amount, date, reference and state.

ERPNext MCP tools: https://cotlet.dev/docs/mcp/erpnext.md

MCP tool: `erpnext_read → list_payment_entries`

Access: read.

Lists Payment Entry records, newest posting date first. A customer payment has the payment type Receive. state is draft, submitted or cancelled; only submitted entries have posted to the General Ledger. Each entry lists the invoices it is allocated to. Pages hold up to 100 entries; pass next_cursor back as cursor for the next page.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `party` | string | no | Customer ID from list_customers. |
| `payment_type` | string | no | Receive, Pay or Internal Transfer. |
| `state` | string | no | draft, submitted or cancelled. |
| `from_date` | string | no | Posting date from, YYYY-MM-DD. |
| `to_date` | string | no | Posting date to, YYYY-MM-DD. |
| `limit` | integer | no | Records per page. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "erpnext_read",
    "arguments": {
      "operation": "list_payment_entries",
      "arguments": {}
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "payment_entries": [
      {
        "payment_entry": "ACC-PAY-2026-00018",
        "payment_type": "Receive",
        "party": "Lumen Dental",
        "posting_date": "2026-10-12",
        "paid_amount": 200,
        "mode_of_payment": "Wire Transfer",
        "reference_no": "WIRE-88102",
        "state": "submitted",
        "allocated_to": []
      }
    ],
    "next_cursor": null
  },
  "isError": false
}
```

Previous: [List overdue invoices](https://cotlet.dev/docs/mcp/erpnext/list_overdue_invoices.md)
Next: [Create customer](https://cotlet.dev/docs/mcp/erpnext/create_customer.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.