Skip to content

Client Implementation — Saint Edwards

Client Profile

Field Value
Client Name Saint Edwards
Type School
Location Australia
Number of Students ~920
Number of Campuses 1
Current Systems SIS (direct integration)
Contract Start
Go-Live Target
Project Manager
Solution Architect

Solutions in Scope

Solution In Scope Notes
ERP ❌
ARM ✅ Yearly billing cycle, automated configurator
EPM ❌

Implementation Notes

Saint Edwards is the cleanest ARM implementation — the automated billing configurator is operational and used for each billing cycle. Billing is yearly (one cycle per year) with flexible parent-chosen payment dates (weekly, fortnightly, or monthly). The school follows and references the Step 1-2-3-4 process in their support communications.

Configurator Usage

Saint Edwards uses a minimal subset of the configurator suitelet. Their actual workflow:

  1. Navigate to the Families tab → verify debtor count matches expectations
  2. Check the student count — must match expected enrollment (e.g., ~920 students)
  3. Optionally modify the billing period number (e.g., 22 instead of 24)
  4. Hit Submit → billing instructions are generated

They do not interact with the items-to-year mapping, exceptions, mid-year, or maintenance tabs. No inputs are changed on most screens — the configurator essentially validates data and generates billing instructions in one pass.

Saint Edwards also has the oldest version of the configurator codebase. It was the first school to use it, and the code has diverged from other client implementations.

See Configurator Discussion Meeting Extraction for detailed walkthrough with screenshots.

Project Timeline

Phase Start End Status
Discovery & Requirements
Solution Design
Configuration & Customization
Data Migration
Testing (SIT)
User Acceptance Testing (UAT)
Training
Go-Live Completed
Hypercare / Post Go-Live Completed

Detailed Documentation