Enrollment by program
Compare accepted applications and active enrollments by campus and academic period.
Implementation and migration
Start with an academic period the registrar and bursar can reconcile together.
Implementation phases
- Agree the operating boundaryTeam and ERP.ai
- Map the source dataTeam and ERP.ai
- Configure a bounded pilotTeam and ERP.ai
- Rehearse the exceptionsFaculty
- Reconcile and releaseTeam and ERP.ai
Phase 1 · Team and ERP.ai
Agree the operating boundary
The scope is administrative education ERP. Learning content, accredited assessment engines, statutory reporting portals and payment acquiring remain connected systems with their own requirements. The institution decides admission, concessions and academic policy; Proto prepares information and configuration for review.
Phase 2 · Team and ERP.ai
Map the source data
Keep student identity separate from application and enrollment. Link fees to the enrollment and attendance to the scheduled session. Retain the payment-provider reference when importing receipts, and do not allocate more than the confirmed receipt or open charge.
Phase 3 · Team and ERP.ai
Configure a bounded pilot
Pilot one campus, one academic period, an approved fee schedule and a representative teaching week. Reconcile accepted students, charges and confirmed receipts before expanding.
Phase 4 · Faculty
Rehearse the exceptions
A duplicate payment event must not settle the same charge twice. A student transfer must preserve prior enrollment and fee history. A faculty or room overlap must block timetable publication until resolved. A faculty account must not access another teaching group’s restricted student notes.
Phase 5 · Team and ERP.ai
Reconcile and release
Compare record counts, financial balances and open commitments with the source. Obtain domain-owner acceptance, keep an export of the source, and agree the rollback window before a controlled cutover.
Submitted
| Number | Organization | Source Type | Source Number | Period |
|---|---|---|---|---|
| JE-26031 | ORG-6303 | ST-714 | JE-97031 | PRD-963 |
| JE-62706 | ORG-9697 | ST-610 | JE-42043 | PRD-824 |
| JE-30305 | ORG-2932 | ST-489 | JE-85477 | PRD-717 |
| JE-22174 | ORG-4355 | ST-846 | JE-62834 | PRD-483 |
| JE-30113 | ORG-6364 | ST-777 | JE-40402 | PRD-555 |
| JE-68876 | ORG-1870 | ST-703 | JE-81755 | PRD-434 |
- Program and campus structure, academic calendar and room capacities.
- Student identifiers, enrollment history and opening fee balances.
- Admission, concession, refund and attendance-correction policies.
- Faculty assignments and the current timetable with known exceptions.
Use Proto to prepare changes on a branch. Review the changed fields, affected permissions, import mappings and reports with their owners. Replay the pilot’s exception cases before release. Historical decisions keep their original policy context.
Prepare your first configuration.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.