Who paid, who owes, who is waived — summed to the cent, per organization and season.

How a dues roster reconciles

The dues roster projects forward from opaque obligations to a sums-only treasurer aggregate. Every step is exact integer cents, and the hardship reason never leaves the treasurer’s audit.

1. A member is assessed for an organization and a season. An obligation is created for one member, one organization, one season: the assessed amount in exact whole-cent integers. The member, organization, and season are opaque references — never a student identifier, a name, or a grade — so the obligation row carries no student column at all.
2. A hardship waiver is assessed, fail-closed. If a waiver request is both eligible and approved, it zeroes the assessment and records the closed hardship reason for the treasurer’s audit. Eligible-only or approved-only does not zero the assessment — both are required. A waived member owes nothing; a waiver recorded against a nonzero assessment is flagged as inconsistent rather than silently accepted.
3. Payments are collected against the obligation. As dues come in, the collected cents rise. The balance is the assessed amount minus the collected amount, in exact integer cents. A member who pays exactly is paid in full; short is balance-due with the amount surfaced; over is overpaid with the surplus surfaced and the balance due held at zero — never a negative.
4. The obligation lands in exactly one status. Waived, paid-in-full, balance-due, overpayment, or flagged — most-protective first. A bad cent value or an inconsistent waiver is flagged and excluded from the sums rather than corrupting them. The status is a pure function of the obligation, so the same row always resolves the same way.
5. The treasurer aggregate rolls up, sums only. Obligations group by organization and season into counts and cent sums — and no per-member row. Every sum is guarded against integer overflow; an overflow is flagged, not wrapped. This is the only member-derived shape a treasurer sees, and it honors the student-data PII wall because it never carries a member identity.
6. The reconcile identity is asserted. For each organization and season, the assessed total minus the paid total equals the outstanding total minus the overpayment total. The software checks this on every roll-up. No cent is lost or created between the roster and its aggregate.
7. Export or hold a charge — honest-off. The aggregate CSV is always safe to hand a treasurer; the per-member detail CSV shows opaque references unless an authorization and consent gate both pass, and never the hardship reason. A held-charge intent proves the exact balance a real rail would collect — it moves no money and posts no charge. A human gate and the payments rail collect the real dues.

Money honest-off: the charge is a held intent

Dues Software reconciles who owes what. It does not, today, move the money. The held-charge intent is explicit about this: it returns the exact balance a real payment rail would collect, and it moves no money and posts no charge. A human gate and the payments rail collect the real dues. Every amount the software reports as owed or collected is a reconciliation fact, not a fabricated payment.

This is deliberate honesty, not a limitation to hide. The math is real and exact — assessed, collected, outstanding, overpaid, all in integer cents that reconcile — and the collection is a separate, human-gated step. When a treasurer reads a member as paid in full, that reflects collected cents recorded against the obligation, not a charge the software silently ran.

There are no take-percentages here. Dues Software is the roster and the reconciliation, not a slice of the dues. A member owes what the organization assessed; the organization keeps what it collects. The software’s job is to make the roster honest and the totals reconcile — who paid, who owes, who is waived — not to skim the middle.