The safest way to collect membership dues online is to connect every payment to one member, one membership period and one access state. A payment link alone collects money; a dues register shows who owes what, whether payment cleared and when membership should start or end.
This workflow is for clubs, professional associations, alumni groups and member-led organizations replacing cash, bank-transfer screenshots or an annual spreadsheet chase.
Choose Recurring Collection or an Annual Payment Request
| Model | Best when | Main operational control |
|---|---|---|
| Automatic recurring membership | Membership continues until cancellation | Mandate, renewal date and failed-payment state |
| Annual invoice or payment page | Members actively renew each year | Renewal campaign and paid-through date |
| Manual bank-transfer invoice | A member or employer requires an invoice | Reference matching and overdue follow-up |
Do not describe an annual payment request as an automatically renewing membership. The checkout, reminder and member record should all state the same commitment.
PayRequest documentation distinguishes automatic subscription payments from manual recurring invoices. Automatic collection fits ongoing memberships; invoice-based collection remains useful when a company pays on behalf of a member or a mandate is unavailable.
Build the Member-to-Dues Register
Use one row per membership period, not one permanent “paid” checkbox.
| Field | Example | Why it matters |
|---|---|---|
| Member ID | CLB-0248 | Prevents two people with the same name being merged |
| Plan | Individual annual | Identifies the promise and amount |
| Period | 1 Sep 2026–31 Aug 2027 | Defines what the payment buys |
| Amount and currency | €96 EUR | Makes reconciliation explicit |
| Collection method | Automatic mandate | Explains the next payment action |
| Payment state | Due, pending, paid, failed, refunded | Separates an attempt from settled money |
| Access state | Scheduled, active, grace, ended | Keeps member benefits aligned |
Never overwrite last year's row. A history lets a treasurer answer whether a member renewed late, received a refund or changed plan without reconstructing events from email.
Use a Reconciliation Rule, Not Screenshots
A bank screenshot is evidence that someone initiated something; it is not reliable confirmation that your organization received and matched the money. Use the verified provider event, settled transaction or matched bank entry defined by your process.
Run reconciliation in this order:
- Match the transaction to member ID and period.
- Confirm amount, currency and final payment state.
- Mark that period paid once.
- Activate or extend access once.
- Send a receipt or renewal confirmation.
Keep exceptions visible: underpayment, duplicate payment, employer payment, chargeback and refund each need a recorded resolution.
Create a Three-Message Renewal Sequence
For actively renewed annual dues, use a short sequence rather than repeated generic reminders:
- Opening notice: amount, period, due date, benefits and payment route.
- Due-date reminder: current unpaid state and one direct action.
- Grace/end notice: exact consequence and effective date under the published policy.
Stop the sequence immediately after verified payment. A member who pays should never receive the next overdue reminder because a spreadsheet was updated late.
Configure the PayRequest Flow
Use PayRequest Memberships when access is recurring and should stay connected to an active membership. Members can join through a hosted Page, log in by magic link and open protected posts while active or on trial.
For an organization that intentionally asks members to renew each year, create an annual subscription or a clearly labelled annual payment page based on the real agreement. PayRequest supports flexible subscription cycles and customer records; test the exact provider and mandate flow you select before inviting the full roster.
Run the Five-Member Test
Before launch, create five controlled cases: normal payment, failed payment, employer-paid invoice, duplicate payment and cancellation. Confirm each produces one understandable dues row, the correct access state and no duplicate reminder.
Launch only when a new treasurer can answer three questions from the register: who is paid through which date, which payments need action, and which access changes are due.
Start with one clear membership on PayRequest Memberships, then test the complete join, renewal and cancellation journey before replacing your old dues process.