Finance
The finance module handles what profiles owe and pay: payment plans with their fees and instalments, discounts, who pays each fee, online payments through gateways, and the transactions that record every payment. It connects to applications and registrations, which create plans and can require fees to be paid before submission, and to automation, which reacts when plans are published and fees are paid.
Key concepts
| Term | Definition |
|---|---|
| Payment plan template | The reusable definition of a product's fees, due dates, gateway, instalment options and discounts. Plans are created from it. |
| Payment plan | What one profile owes for one class, course or the institution: fees, discounts, payers and transactions. Hidden from the applicant until published. |
| Fee | One amount due on a date, in one currency. A fee is paid when completed transactions and discounts cover it. |
| Set of instalments | A fee divided into several smaller fees with their own due dates, managed together. |
| Fees structure | Fixed: staff define the fees. Flexible: the applicant divides the product price across fees themselves. |
| Discount template | A discount a template offers, applied automatically to new plans or by code. |
| Payer | Who pays a fee: the student themselves, or an external payer such as a parent or sponsor. |
| External payer request | A payment link for one fee, emailed to an external payer and valid for one week. |
| Payment gateway | Stripe, PayPal, Flywire, Adumo or External: how a fee or application fee is paid online. |
| Transaction | One movement of money against a fee: a gateway payment, a manual payment, a refund or a reversal. |
Pages in this section
| Page | Covers |
|---|---|
| Payment plan templates | Template settings, fee types, due dates, instalment options, deleting templates |
| Payment plans | Creating plans, fees, fee and plan status, publishing, the Payment plans list, deleting |
| Instalments | Dividing fees, rounding, applicant-chosen instalments, editing and re-dividing sets |
| Discounts | Discount templates, codes, one-off discounts, how discounts are calculated |
| Payers | Payer templates, external payers, payment requests and their emails |
| Transactions | What counts as paid, transaction states, manual transactions, refunds, reversals |
| Payment gateways | Setting up Stripe, PayPal, Flywire and Adumo, choosing a gateway, how each reports back |
| Applicant payments | The Payments page, paying while applying, the payment plan statement PDF |
| Automation and emails | Triggers, the Create payment plan action, reminders, merge fields, letters |
| Finance across the platform | Applications and registrations, offers, profiles, courses, exports, API |
| Settings and permissions | Where finance is configured, institution features, permission features |
A typical setup
- Set up a payment gateway, if fees are paid online.
- Create payer templates for the kinds of external payers the institution accepts, if any.
- Create a payment plan template for each programme, with its fees, due dates and gateway, and assign it to its classes.
- Add discount templates to it, and its automation rules.
- Switch on payment plans on the application or registration template, or create plans for profiles directly.
- Publish each plan when it is ready for the student to see.