Catch paused-student billing leaks before the monthly dues run goes out.
DuesShield gives martial-arts schools, tutoring centers, dance studios, youth academies, and enrichment programs a safe / review / blocked preflight for paused enrollments, skipped periods, partial invoice runs, stale credits, and AR follow-up.
Billing preflight
412 active students reviewed
19
need review
Potential leak
$1,840/mo
Stale pauses
7 families
Next
review before run
Narrow customer
Small academy owners and office managers with recurring dues.
Best fit: 75-600 active students, monthly billing, parent pauses, credits, refunds, and a busy front desk that cannot audit every family by hand.
Paid problem
Paused students and partial billing runs leak real monthly revenue.
The cost is missed dues, disputed charges, bookkeeper cleanup, parent trust damage, and owner uncertainty at month-end.
Validation test
One redacted export in. One exception packet out.
The waitlist tests whether real operators will share redacted billing data for a concierge monthly dues preflight.
Day-in-the-life pain
It is billing week. A parent pause from two months ago is still silently blocking dues.
The office manager remembers that one family paused for travel. Another student skipped a month after an injury. A credit was promised after a duplicate charge. The platform shows balances, a spreadsheet tracks notes, and the owner wants to know whether this month's run is safe. Nobody wants to discover the answer after invoices are sent or cash is missing.
Input
Upload a redacted monthly billing export, paused-family list, invoice-run CSV, or screenshots from your current academy-management system.
Checks
DuesShield flags stale pauses, skipped periods without review dates, partial invoice runs, odd credits, aging balances, and families that need owner attention.
Output
You get a safe / review / blocked billing packet, family follow-up list, owner summary, and audit notes before invoices go out.
Why the workaround breaks
Billing exceptions cross people, dates, credits, and exports. Staff memory is not a control system.
Academy systems can process payments. Spreadsheets can record notes. But the risky work sits between them: deciding which pauses should resume, which invoice run is incomplete, which credit is still open, and which family balance needs follow-up before owner reports are trusted.
Pause and skip-period review
Catch families whose temporary hold or skipped period became a permanent revenue hole before another billing cycle is missed.
Billing-run integrity scan
Find orphan invoice keys, missing line items, suspicious reruns, and export mismatches that should be repaired before statements are trusted.
AR-aging owner view
Show billed amount, collection rate, aging families, and follow-up priorities in the language an academy owner can act on quickly.
Credit and refund trail
Surface promised credits, refunds, and adjustments so parent conversations do not depend on staff memory or one hidden spreadsheet.
Concierge first review
Start with one redacted export. We return the exception packet manually before asking you to change systems or connect payments.
Public evidence
The signal points to billing confidence, not another generic student database.
These are public research signals, not proof of demand. The waitlist tests whether academy operators identify with the exact pause, skip-period, invoice-run, credit, and AR-aging workflow.
GitHub Issues · paused enrollment billing gap
Monthly student dues can exclude paused enrollments or skipped periods indefinitely when there is no enforced resume review, row-level deferral audit, or clear admin visibility.
Open source link →GitHub Issues · partial monthly invoice runs
Invoice keys can be reserved before ledger invoices and lines are fully persisted, leaving partial billing state after crashes, restarts, transient writes, or concurrent reruns.
Open source link →GitHub PR · owner financial dashboard expectations
Academy owners expect billed amount, collection rate, payment visibility, and per-family AR-aging drill-down rather than a vague payment dashboard.
Open source link →GitHub PR · refunds, credits, and audit logs
Standard reporting includes refunds, credits, dated billing audit records, account-credit ledgers, and exports that make money movement explainable.
Open source link →Objections
This only works if it is narrower than a platform migration.
DuesShield is deliberately a validation experiment. We are testing a painful monthly control point: catch billing exceptions before the run, without forcing a small academy to replace its management system.
Why not just use Jackrabbit, iClassPro, or another academy platform?
You may already use one. DuesShield is not a replacement. It is a preflight layer for the exception lane owners still check manually.
Can a spreadsheet handle this?
A spreadsheet can list families. It does not reliably detect stale pauses, partial invoice state, aging risk, credits, refunds, and follow-up context together.
Is this safe with student billing data?
The validation step uses redacted exports first. The goal is to prove the exception packet is useful before any deep integration or sensitive workflow exists.
Is the evidence enough?
Not yet. The page is the test: we only keep pursuing this if real academy operators recognize the pain and volunteer redacted examples.
Early waitlist offer
Send a redacted export. Get a billing-risk packet.
Early users get a concierge review: stale pauses, skipped periods, invoice-run integrity, credits/refunds, and AR follow-up. Demand is validated only if academy operators share real redacted examples and want this monthly.