> For the complete documentation index, see [llms.txt](https://digitals-private-organization.gitbook.io/rizones45678.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitals-private-organization.gitbook.io/rizones45678.org/web-portal-guide/club-dues.md).

# Club Dues

Set up member fees, collect and approve payments, and issue receipts.

The page opens with a collection summary and one row per fee setup.

> **Screenshot slot:** the Club Dues page, showing the collection summary and fee setup rows.

## Create a dues setup

{% stepper %}
{% step %}

### Go to Club Dues

{% endstep %}

{% step %}

### Click + Create Dues Setup

{% endstep %}

{% step %}

### Choose the Fee Type and amount

**Annual**, or **Semi-Annual 1 and 2**.
{% endstep %}

{% step %}

### Allocate the fee to members

It is applied automatically to all non-honorary members.
{% endstep %}
{% endstepper %}

## Record or approve a payment

{% stepper %}
{% step %}

### Open the dues setup row, then Members

{% endstep %}

{% step %}

### Record an offline payment

For cash or cheque, use **Record Offline Payment** with Given To **\***, Payment Date **\***, Transaction ID and Remark.
{% endstep %}

{% step %}

### Approve or reject

Rejecting requires a **Rejection Reason**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Members can also pay online themselves with **Pay Now**. Receipts and reminders are automatic.
{% endhint %}


---

# 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://digitals-private-organization.gitbook.io/rizones45678.org/web-portal-guide/club-dues.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.