Skip to main content
Orgo Membership Fees is the dues collection and billing module that charges, tracks and reconciles member payments. Built for membership organisations collecting dues from a distributed member base: professional associations, alumni networks, youth organisations, faith communities and federated nonprofits. Replaces the spreadsheet that tracks who has paid. It is not accounting software; payment data feeds into that.

How the pieces fit

A membership fee is a product of type Membership Fee with one price per membership level. Each member is assigned one of those prices. A successful payment stamps a billing period on the member, and the end of that period becomes their valid fee date, which reminders, mandatory-fee gating and chapter statistics all read.

Setting up

Payments and Fees module settings with Membership Fees, All Members Fee Eligible and Event Ticket Sales toggles All three steps require ADMIN_TENANT.
1

Connect Stripe

Settings → Payments & Fees → Payment Gateway. Without it you can still record payments by hand, but members cannot pay online. See Stripe Integration.
2

Create the fee product and its prices

Finance → Products → Create Product → Membership Fee. Set Period and Cycle beginning, then add one price per membership level. See Products.
3

Point the organisation at it

Settings → Payments & Fees → Membership fees → Enable Membership Fees, then pick the Membership Fee Product and its Default Price. Nothing charges until it is selected here.

Membership fee settings

Membership fees settings showing Enable Membership Fees, the Membership Fee Product and Default Price selectors, and the Payment Options and Local Center Configuration sections A Checkout donation section adds an optional gift to the membership checkout, with an optional custom amount and prompt.

What a payment buys

Fixed Starting Date for Fees decides the period:
  • Off (anniversary): the period runs from the payment date for the product’s number of months, ending the day before the anniversary. An annual fee paid on 1 September covers to 31 August.
  • On (fixed cycle): the period is anchored to the product’s Cycle beginning month, so a September-anchored annual fee always runs 1 September to 31 August and a January payment buys only the remainder.
Proration decides the price, not the end date. With Enable pro-ratio for shorter first cycle off, a mid-cycle payer still ends on the cycle boundary and pays in full; with it on the amount is reduced for the remaining months, unless Number of months after cycle begining to start pro-rate vetoes it for members who join in the opening months of the cycle.

Worked example: joining mid-cycle

An example, not a default. An annual membership priced at 120, Period 12 months, Cycle beginning September, with Fixed Starting Date for Fees and Enable pro-ratio for shorter first cycle both on. Every partial period still ends on the cycle boundary, so everyone renews together on 1 September. Now set Number of months after cycle begining to start pro-rate to 3. Anyone joining in the first three months of the cycle (September, October, November) is charged the full 120 instead, and proration only starts with a December join. The setting exists so that a member joining a few weeks late does not get a discount for it. Proration is measured from the member’s join date, not from the day they pay: a member who joined in January but only settles in June still buys the January to August period at 80.

Which price a member pays

Each member carries an assigned membership price, per level, plus an optional local one. For a given date Orgo resolves the amount in this order:
  1. The effective-dated assignment covering that date.
  2. The member’s current assigned price.
  3. The version of that price that was valid on the date.
  4. The organisation Default Price (age-appropriate, when age restrictions are on).
Raising a price therefore never reprices history: a 2024 payment still resolves against the 2024 version. On Finance → Local members fees the fee column is a per-member dropdown, and the change is recorded against the fee year on screen, so a member can sit on one level this year and another next. The first future-dated change pins the member’s current level to the current cycle, so promoting the new level later cannot reprice earlier periods. The change is refused with a conflict once a successful payment covers the target cycle or any later one; the lock icon marks the rows the server would refuse. Example. With Cycle beginning September, the fee year labelled 2026 means 1 September 2026 to 31 August 2027, and in July 2026 the current fee year is still 2025. So in July 2026 you can move a member from Student to Standard for 2026 even though they have paid 2025 in full: the earliest period the change touches is 1 September 2026, and no payment reaches it yet. Once that member pays 2026, the 2026 dropdown locks and only 2027 onwards remains editable.

The valid fee date

Fee validity is not hand-set. It is the furthest period end among the member’s successful, unrefunded payments for the fee product, recomputed whenever a payment is recorded, approved or refunded. Recording an older period never pulls the date backwards. Local fees keep a separate date. Two prices bypass payment: a lifetime price with no amount sets validity 100 years out, and a price marked Is only assignable by admins (hidden for members) with no amount sets validity to today plus the product period each time it is applied. That covers honorary and free memberships. The admin-only price does not add to whatever the member already had, so re-applying it to a member with longer remaining validity shortens it. Exemption comes from the user type, not the individual: a user type with Not eligible for fee on, the organisation’s designated non-eligible user type, or an active user-type role carrying that flag. Exempt members are never assigned a fee and see “You are not eligible for paying fees” on their profile.

Collecting payments

On the Local members fees table an admin may only record a payment for a member they manage: chapter and organisation finance admins for their whole scope, unit admins only for members in their own units. Mark as paid is a finance-admin action and is not offered to unit admins at all.

Worked example: recording a part-paid year

An example, not a default. A member on a 120 level with a September cycle already paid 30 by card for 1 June to 31 August 2026. An administrator now ticks the whole 1 September 2025 to 31 August 2026 cycle under Mark as paid. Orgo works out what the cycle costs (120), subtracts the overlapping part of what is already paid (the 30), and records a single 90 row. The member’s periods do not double up and the totals still add up to what was actually collected. If the selection turns out to be fully covered, nothing is recorded for that member at all and they simply do not appear in the batch. An early renewal is stacked the same way. When a member pays while their membership is still valid, the new period starts at their current validity date rather than at the payment date, so paying two weeks early costs them nothing in days.

Approving recorded payments

Finance → Fee payments (route /fee/payments) is the queue of recorded fee batches. It requires FINANCIAL_LOCAL; unit fee admins also reach it, scoped to their own chapter. Fee payments queue with Organisation and Local toggles, a chapter filter, status filters and columns for ID, date, value, payer, chapter, method and status Filter by Organisation or Local, by chapter, and by All Statuses, Pending or Approved. Each row shows the batch total, payer, chapter, method (card, check or IBAN) and status. What arrives approved is decided by how the batch was written, not by how the member paid. A card batch arrives approved, and only Stripe fulfilment ever writes one. A Mark as paid batch, method check, arrives approved too. What arrives pending is the batch written by Pay on Finance → Local members fees, stamped as a bank transfer (iban), for organisation and chapter fees alike. Approving marks every payment in the batch successful and recalculates each affected member’s valid fee date, the chapter date for a chapter fee product and the organisation date otherwise. Until then the periods show as paid-but-pending on the fee tables and no validity date moves. Approve is shown only to ADMIN_TENANT. A chapter administrator with ADMIN_LOCAL sees Cancel instead, which deletes the batch and every payment row in it.

Watching collection

Finance → Local members fees shows one row per member and one column per fee period: which periods each member has settled, a switch between the organisation and local fee, filters for year, member status and unit, and recording payment for the selection. Requires FINANCIAL_LOCAL and the Local Center Members Table setting. Finance → Stats shows fees by chapter for a chosen period: chapter, status, active member count and fees paid, with a total. Requires FINANCIAL_TENANT; for ADMIN_TENANT it also highlights chapters below Minimum Members per Local Center or Minimum Active Members Percentage. Local groups fees table listing chapters with status, active member count and paid fee count, with under-target rows highlighted Per-member history lives on Members → open a member → Fee. A summary card at the top shows the status (active or Unpaid), the amount, the Plan with a Change plan link where the member can pick another level, and the Pay or Automatic Renewal buttons when they apply. Below it, the History lists every period with its amount and a tag (Paid, Partially paid, Pending, Unpaid, Refunded or Exempt), newest first; older periods sit behind a +N older link. When the member also has a local fee, the Organisation fee and Local fee cards appear side by side and the summary shows each amount plus the combined total. Fee periods are separate from the member’s other purchases: the profile’s Payments tab lists every payment and can be narrowed with the Payment type filter (see Recording a payment). Fee tab on a member profile with the status and total fee summary above the organisation fee and local fee cards, each showing its plan and its paid periods The payment screens have no built-in CSV export. To pull payment data out, build a payments report (Reports in the sidebar, ADMIN_TENANT only): Payments is one of the report builder’s starting points, with columns from the product, the price, the payer, the company, the invoice and five other related records, and the download holds every matching row rather than one page. See Reports. For a one-off question rather than a repeatable file, the Ask Orgo assistant (Ask Orgo in the sidebar, ADMIN_TENANT only) also exports query results as CSV.

Reminders and renewal

Renewal reminders run automatically once a day; there is no “send reminder” button on a member list. Company-covered members are excluded from the personal ladder. See Renewals.

When fees are mandatory

With Fee Payment Mandatory on, a member whose valid fee date has passed is redirected to the payment page and cannot use the rest of the platform until they pay. Organisation HR and finance administrators are never gated, and neither are fee-exempt user types. With Company Fee Payment Mandatory on, a member who belongs to a company is gated on the company’s fee instead of their own.
Making fees mandatory degrades the experience for every unpaid member. Pair it with Days Until Deactivation rather than Auto-deactivate on Fee Expiry alone, so members get a grace window before their account is deactivated.

Refunds

Open the payment on Finance → Payments and choose Refund. Orgo refunds exactly that payment row through Stripe, so refunding a membership charge does not claw back the registration fee booked alongside it. The member’s valid fee date is then recalculated from what remains, and any event attendance paid by that charge is cancelled. Refunds are always the full row amount; there is no partial-amount field.

Troubleshooting

Validity is the end of the paid period, not the payment date, so a payment recorded against last year’s period will not clear this year. Also check the batch was approved on Finance → Fee payments; pending batches do not count.
Payment opens when the fee expires or the advance-payment window opens, one month before expiry for multi-month fees and seven days for monthly ones unless you changed it under Eligibility Rules.
The level locks once a successful payment covers that cycle or a later one. Change it for a later year instead.
Both are opt-in: Enable VAT on Fees and Enable One-time Registration Fee under Pricing Options. While either is off it is never charged, whatever the price row stores. See VAT.
Do not delete their price. Mark their user type Not eligible for fee, or assign an admin-only price with no amount to keep an active membership without paying.
Turn on Local Center Fees Enabled and configure each chapter’s fee product. Members then hold two independent validity dates. See Local Center Fees.
Working as designed: the online payment buttons only ever appear to the member looking at their own fee tab. An administrator settles someone else’s fee with Mark as paid, or sends them the payment link to pay themselves. Before digging further, confirm whether it is you or the member who cannot see the button, because the two have completely different causes.
Three conditions close the member’s own payment route regardless of dates. An active, uncancelled subscription on the fee product, because they are already being charged automatically. A bank transfer already in progress, because Orgo is waiting for that money to land. And, with Require Contract for Membership on, an unsigned or lapsed membership contract, which also fails on the server with “Please sign the mandatory membership contract before any payments”. The last two block Mark as paid as well, so an administrator cannot work around them; an active subscription does not, which is how you settle a period for a subscriber whose charge went astray.
Two arrears settings do this. Minimum Cycles to Pay produces “You must select at least N cycles to pay”, and only bites when the member actually has that many unpaid periods. Continuity Mandatory produces “Your account has unpaid balances from previous fee periods”: the selection has to start at the oldest unpaid period and run without gaps, so a member cannot pay this year while last year is open. One checkout also covers at most 12 periods; a member further behind than that pays in two goes.
Approve is shown only to ADMIN_TENANT, and only while the batch is still pending. A chapter administrator with ADMIN_LOCAL sees Cancel instead, which deletes the batch rather than approving it. A finance-only administrator, FINANCIAL_LOCAL or FINANCIAL_TENANT without an admin permission, sees the queue and the batch details but neither button, so the batch stays pending and the members it covers stay unpaid.
On Finance → Payments, or a member’s Payments tab, open the Payment type pill and choose Fee. The type comes from the product that was paid: membership fee products are Fee, donations Donation, event tickets Event ticket, shop items and digital downloads Shop, and everything else, including payments from invoices, Admin. See Recording a payment.
The one-time registration fee is due only to a member who has never had a membership validity date. Any date at all in their history exempts them, including one that came from a lapsed membership, a level switch, or a free or lifetime price an administrator assigned. There is no way to charge it a second time.