Dues & invoices

GreekManage tracks dues at the chapter level, not per-member. The chapter receives one invoice per billing period (covering all member types and head counts), and chapter officers handle payment through the org's configured processor. As a chapter member, you'll see information about your chapter's invoice but not a personal per-member invoice or self-service payment flow in v0.62.1.

:::info What you see depends on your role

• Chapter members see the Dues Balance card on the dashboard (read-only summary), but the Billing page in the sidebar returns "Access denied" — viewing invoices and paying is officer-and-up only.
• Chapter officers and presidents can open Operations → Billing to view invoices, see line items, and trigger payment.
• National (org) admins configure dues rates, billing periods, and the payment processor. :::

How dues flow through GreekManage

1. Your org admin sets dues rates by member type (Undergrad, Associate, Alumni, etc.) and a billing cadence (monthly, quarterly, semesterly, annually).
2. At the start of each billing period, GreekManage generates one invoice per chapter, computed as head count by member type × rate by member type.
3. The invoice gets a unique ID, an issued date, a due date (commonly net-30 from issuance), a status (Unpaid → Partial → Paid, or Overdue if past due date), and a balance due in cents.
4. Chapter officers open the invoice from Operations → Billing, review line items, and submit payment via the org's configured processor (Stripe, Braintree, Square, or PayPal).
5. After payment, the processor calls a webhook back to GreekManage; the invoice status updates to Paid (or Partial if it was a partial payment), and your chapter dashboard's Dues Balance card reflects the new state within a minute.

The chapter billing page (visible to chapter officers only).

the dues balance card on the chapter dashboard as a regular member sees it

What you see as a regular member

The Dues Balance card on your dashboard

This is the primary member-facing surface for dues. It appears in your chapter dashboard if:

• Your org has the Operations module enabled, and
• At least one chapter invoice exists.

The card shows:

• The current billing period label (e.g. "Spring 2026").
• The balance due in dollars (a chapter total, not your share).
• The due date.
• A status badge:

Status	Color	Meaning
Unpaid	Amber	Invoice generated, no payment yet
Partial	Orange	Some payment received, balance remaining
Paid	Emerald	Fully settled
Overdue	Red	Past the due date with balance remaining

The card auto-refreshes every 60 seconds so when your treasurer pays, the badge flips within a minute.

A View Invoice button on the card links to /chapter/billing/invoices/[id] — but that page is officer-only. Clicking through as a regular member returns a permission-denied error.

Reading dues announcements

Bulletins from your officers (in the Announcements banner on the dashboard) are the most common way you'll hear about dues directly: "Spring dues are $X per active. Payment plan signups due Friday." That communication channel is separate from the invoice system itself — the system tracks the chapter-total invoice, while the bulletins describe per-member expectations from your treasurer.

Ask the chatbot

If your org has the AI Services module enabled, the floating chatbot widget (bottom-right) can answer questions like:

• "When are dues due?"
• "What's the dues balance on my chapter?"
• "Is the spring invoice paid?"

The bot reads the invoice records the same way the dashboard card does, so it'll quote the same period, due date, and status.

What you don't have access to in v0.62.1

• Per-member invoice. There's no individual invoice line for "your share". Your share is collected by your chapter treasurer outside the app (Venmo, Zelle, a check, a payment plan).
• Self-service payment. You can't pay your share through GreekManage. The integrated Pay Now flow is for chapter officers paying the chapter-total invoice on the chapter's behalf.
• Refund flow. Refunds are processed by your chapter officer or org admin through the underlying processor. Talk to your treasurer.
• Payment history visible to members. The list of past invoices and payment receipts is gated behind officer permissions. Ask your treasurer for a summary if you need one.

How chapter officers pay (member context)

You're not the audience for this flow, but knowing how it works helps you understand what you're seeing:

1. Officer opens Operations → Billing.
2. The table shows every invoice for the chapter — period, issued date, due date, total, balance, status, and a View action.
3. Clicking View opens the invoice detail with line items per member type.
4. Officer clicks Pay Now to open the Payment modal, which loads the correct payment form for the org's processor:

Processor	Embedded form
Stripe	Stripe Elements card field with Apple Pay / Google Pay where supported
Braintree	Braintree drop-in UI (card + PayPal + Venmo where enabled)
Square	Square Web Payments SDK
PayPal	PayPal Smart Buttons

5. The modal shows a "Secure payment processing" footer with a shield icon while the form is active.
6. Submitting the payment switches the modal to a processing spinner ("Processing Payment — Please wait while we process your payment…").
7. On success: a green checkmark and "Payment Successful — Your payment has been processed." Closing the modal triggers a refetch and the Dues Balance card updates.
8. On failure: a red alert with the decline message; officer can retry.

The processor selection is made once by your org admin in Org Settings. Each chapter sees the same one — there's no per-chapter override.

Payment processor differences (from a member POV)

You don't choose a processor as a member, but if you're curious why your chapter takes payments a particular way:

• Stripe — most common; supports credit/debit, ACH where enabled, Apple Pay, Google Pay. Fastest setup for the org admin.
• Braintree — owned by PayPal; supports PayPal balance, Venmo (US), and cards under one integration.
• Square — strong fit for chapters that already run Square Point of Sale at events.
• PayPal — PayPal Smart Buttons; familiar UX for members who pay other Greek organizations through PayPal already.

Apple Pay, Google Pay, ACH, and other rails are supported only to the extent the chosen processor offers them — see your processor's documentation.

Receipts

After a successful payment, your treasurer typically receives:

• A receipt email from the processor (Stripe, PayPal, etc.) at the email registered for the processor's account.
• An updated invoice record in GreekManage with the new balance reflected.

GreekManage doesn't email each chapter member a receipt — only the payer (officer) gets the processor's confirmation. If you need a receipt for personal records (your share of the dues), your treasurer can forward it.

For donations to the org's Foundation (separate from chapter dues), donors do get an individual receipt email — but that's the Foundation module, not the dues system. See Donations for the donor-side view.

Refunds

There is no self-service refund flow in v0.62.1. If your chapter overpaid or you need your individual share refunded:

1. Contact your chapter treasurer.
2. The treasurer (or org admin) issues the refund through the underlying processor's dashboard.
3. The refund webhook updates the invoice balance in GreekManage; status may flip from Paid back to Partial.

Mobile differences

• The Dues Balance card on your dashboard renders the same on mobile, stacked into a single column.
• The chapter Billing page that officers use is also mobile-responsive — table rows reflow to stacked cards on phone widths.
• Payment modal embeds (Stripe Elements, etc.) work in the native app via the in-app web view; Apple Pay and Google Pay pop the native sheet for biometric confirmation.

What officers and admins see that you don't

• Chapter officers and presidents see the full Billing table with every invoice, click into detail views, trigger payments, and see payment history.
• National admins see every chapter's invoices in their org, can generate new billing periods, configure dues rates and the payment processor, see export totals, and trigger XLSX exports of invoice data.
• Foundation admins are completely separate — they handle org-level fundraising, not chapter dues.

The sidebar Billing item under Operations is visible to everyone with Operations enabled, but the page itself returns "Access denied" for non-officer members.

Errors and edge cases

Situation	What you see
Org admin hasn't configured a payment processor	Officers see "Payment Unavailable — No payment processor has been configured for your organization. Please contact your national administrator…"
Invoice hasn't been generated yet for the period	No Dues Balance card on the dashboard
Payment is processing	Card shows the old status until the webhook fires; the underlying officer-side modal shows processing
Webhook fails	Status may stay "Unpaid" even after payment cleared the processor — the officer needs to manually reconcile via the processor's dashboard
Invoice was generated with the wrong head count	Officer must contact the org admin; there's no member-driven correction

Troubleshooting

• The dashboard says Unpaid but my treasurer told me they paid. Webhook may not have fired yet. Wait a minute and refresh. If still Unpaid after 30 minutes, the treasurer should check the processor dashboard.
• The Dues Balance card disappeared. Either Operations is now disabled at the org level, or no invoice exists for the current period.
• I want to pay my share via the app. Not supported in v0.62.1. Pay your treasurer directly.
• The View Invoice link gave me an error. That's expected — invoice detail and payment require officer permissions.
• I think the invoice amount is wrong. Contact your treasurer or chapter president. They can escalate to the org admin who configured the rates.

Related

• Dues & billing (org admins) — rate configuration, billing periods, processors
• Donations — Foundation donations (separate from dues)
• Module: Operations

Last verified against v0.62.1 (2026-05-11).