Parties
Identify the student by full legal name and the educational provider by legal entity name, including contact information and billing address for notices.
The Student Customer Agreement clarifies financial obligations, service scope, refund windows, and data-use terms. Clear agreements reduce disputes, speed billing and collections, and provide transparent consumer disclosures required for certain student-facing financial or healthcare interactions.
Typical signers include enrolled students, parent or guardian cosigners, billing administrators, and institutional officers responsible for enrollment or student services.
Institutions and students should confirm authority to sign, required supporting documents, and any third-party payer or guarantor obligations before execution.
Identify the student by full legal name and the educational provider by legal entity name, including contact information and billing address for notices.
Describe courses, materials, software access, or services provided, including duration, delivery method, and any performance or attendance expectations.
State tuition, fees, payment schedule, late fees, and accepted payment methods; note consequences of nonpayment and any collection costs.
Define refund windows, pro rata calculations, deadlines for withdrawal, and any administrative or processing fees charged on refunds.
Specify how student data will be used, disclosed, and retained; address FERPA or HIPAA applicability and any required consent language.
Provide signature blocks for all required parties, include printed names, titles (if institutional), and an effective date for the agreement.
| Field | Configuration |
|---|---|
| Signer Authentication | Email link by default; add SMS or KBA for higher assurance. |
| Signature Fields | Require signature and date fields; enforce mandatory inputs. |
| Conditional Fields | Show terms only when specific options are selected. |
| Notifications | Send reminders after X days; notify countersigners on completion. |
Ensure the eSignature platform supports required integrations, file formats, and authentication methods for institutional workflows.
Confirm the chosen platform provides a tamper-evident audit trail, exportable records, and retention controls to meet institutional policy and regulatory needs.
Date the agreement takes effect, typically the signature date
Institutional policy defines refund eligibility and deadline
Specified payment due date to avoid late fees
Tuition statements typically issued to students by Jan 31
Time allowed for contesting charges per policy