Member portal
Every relationship gets its own portal.
One record
Two views. The same numbers.
- Obligation
- $240 annual dues
- Received
- $240 · mobile money
- Allocated
- Annual dues 2026
- Standing
- Good standing
This is the part that matters and the part that is easy to miss. A portal built on an exported copy of the data is a second set of books, and a second set of books is what produces “your records say one thing and mine say another” — the argument the whole product exists to end.
What they see
Enough to answer their own question.
What I owe
Every obligation, current and upcoming, with what it is for and when it is due — not a single blended balance.
What I have paid
Every payment, on whichever rail it arrived, with the date it landed and the receipt.
What it settled
Which obligations each payment discharged, including one payment split across several.
My statement
The account over a period rather than a balance today, which is what somebody actually needs at year end.
Where I stand
Good standing, inside a grace period, in an arrangement, overdue — stated, rather than inferred from a number.
What that grants
Voting rights, access, member pricing, a service tier. The consequences of standing, made visible to the person they apply to.
The loop
Every message has somewhere to lead.
Reminder sent · account opened · obligation understood · payment made · payment reconciled · standing updated · entitlement restored. Each step writes to the record the next one reads, which is why none of it requires anybody to tell anybody else that something happened.
Sending notifications is commodity functionality. Giving them somewhere to lead is not.
Good standingGOOD_STANDING
Nothing due, or everything due is paid.
DueDUE
An obligation has come due and is not yet settled.
GraceGRACE
Past the date, inside the window the policy allows.
OverdueOVERDUE
Past grace. Enters the collections worklist.
RestrictedRESTRICTED
Some entitlements withdrawn; the account still works.
SuspendedSUSPENDED
Access withdrawn until the balance or an arrangement lands.
And the states that stop the escalation
ArrangementARRANGEMENT
An approved installment plan. Owes money, escalation stops while it is kept.
DisputedDISPUTED
The obligation itself is contested. Chasing it is the wrong action.
WaivedWAIVED
Written off or forgiven by someone with the authority to do it, on the record.
One financial relationship. One shared record. Two experiences.
It is worth being precise about why this is unusual. Billing platforms, accounting systems and payment providers are back-office software: they serve the organization and stop at its edge. Membership platforms run the member experience but carry one balance per person underneath it. Holding both sides on one financial model is what makes the relationship — rather than the invoice or the transaction — the thing the system is actually built around.
Questions
About the portal
What can someone see in the portal?
What they owe and why, what they have paid and when, what each payment settled, their current standing, and what that standing entitles them to. It is the same record the organization works from rather than a summary generated for them — which is the point, because a portal built on a separate copy of the data reintroduces exactly the disagreement it was meant to end.
Do they need an account before they can pay?
No. Payment does not depend on the portal, and money that arrives outside it — a bank transfer, a wallet payment, cash at the office — reconciles the same way and appears in their view once it is allocated. The portal is where somebody goes to understand a balance, not a toll gate in front of paying one.
What happens to portal access when someone falls behind?
It stays on, unless you deliberately configure otherwise. Withdrawing the route back is a common and self-defeating policy — the portal is where an overdue member would go to pay, and locking them out of it removes the cheapest path to recovering the money. Other entitlements can be suspended independently.
Can we brand it as ours?
The people you serve should experience it as your organization's, not as a third party's. What each thing is called follows the vocabulary you configure — dues, fees, contributions, levies, rent — for the same reason every other surface in Zetu does.
Is it a separate product?
No, and it is not priced separately. It reads the same obligations, settlements and standing the rest of the platform writes, which is why it cannot drift out of date — there is nothing to synchronise.
Bring us one messy month.
Bring one month of obligations and one month of payments. We will show you what reconciles, what does not, and what that is costing you.