From confidence-based operations with recurring monthly shortfalls to a chained control structure — multi-center academic management with banking-grade security
An educational foundation with a national network chained collections, attendance and instructor pay by rules — and the monthly shortfalls nobody could explain stopped happening.
CEO or COO of an educational foundation, academy network, technical school with a national network of instructors, or training institution with daily in-person collections and performance-based instructor pay. If your operation runs on trust, you have recurring cash shortfalls nobody can explain, and instructor payroll is calculated by hand from attendance — this case describes your situation.
The client
- Industry
- Education / professional training with a national network of centers and instructors
- Client
- Educational foundation with a national network
- Model
- Logically multi-tenant platform, segmented by training center
- Scale
- 700+ instructor appointments · thousands of students
Operations ran on trust, and every month cash shortfalls appeared that nobody could explain.
- Operations sustained on trust across 700+ instructor appointments and a national network of centers, with recurring monthly cash shortfalls nobody could explain
- Cash collection scattered across spreadsheets with counting errors at end of day
- Teacher honoraria calculated by hand from attendance, with disputes every payroll cycle
- Cancellations and refunds without traceability or formal authorization
- Administrative procedures (filings) without clear status or document validity tracking
- Same login for internal staff and external partners — no segregation
- Single-credential access exposing the institution to credential-stuffing risk
A platform built on 5 functional domains sharing a common security, permissions and audit layer: Administration (centers, branches, areas, catalogs, user↔center assignments), Academy (students, instructors, workshops, groups, attendance, evaluations, document records), Processes (filings with auto-generated folio numbers, controlled statuses and validity periods), Cashier (supervised opening/closing, multi-method payments, 5 cash-closing views) and Payments (instructor pay derived from confirmed attendance, vendors with supervised cancellation).
Collections ↔ attendance ↔ instructor pay, chained by rules
Student pays → attendance moves from “Awaiting payment” to “Attended” → confirmed attendance automatically feeds the instructor's pay calculation. This closes the loop that lives in disconnected modules in any generic ERP or SaaS. It was never a dishonest-staff problem — it was an architecture problem.
Mandatory 2FA with three methods
Microsoft Authenticator (standard TOTP), WhatsApp and email, at the user's choice — mandatory, not optional.
Endpoint-level granular permissions
550+ individually permissioned routes, editable from the interface without development.
Two-key cashier controls
Multi-method payments under a single folio, cancellations requiring requester + approver, and cash shortfalls that require a mandatory justification: a difference is never silently discarded.
Institutional folio numbers
Auto-generated, immutable and gap-free.
Stack & architecture
Results
Individually permissioned routes editable without development, plus 200+ typed actions in the audit log, reportable by date range, user and type.
Banking-grade and mandatory: most users chose Authenticator (TOTP) over WhatsApp.
“We used to log every transaction of the day in Excel, and at month-end the shortfalls had no explanation. Now the system closes the day for me: every peso has an authorization, a justification and someone accountable, and that changed the way we work across all our centers.”
Lessons learned
- Recurring shortfalls at an educational foundation aren't a dishonest-staff problem — they're an architecture problem. When collections, attendance and instructor pay live in separate systems, discrepancies are inevitable and nobody has an incentive to investigate them. Chaining them by rules solved the root cause, not the symptom.
- We expected WhatsApp to be the dominant 2FA method in Latin America given its cultural adoption. Surprise: most users chose Microsoft Authenticator (standard TOTP). Don't assume the lowest-friction method — let users choose and measure real adoption.
- The common internal blocker was operations staff who preferred opacity around cancellations and cash handling. A supervised authorization flow with a mandatory reason dissolved that pattern without confronting anyone. Structure creates discipline.
