Subjects, classes, tuition, and payment

Subjects, classes, tuition, and payment

These settings control what the student is enrolled in and what must be paid before the journey can complete.

Subject assignment

Choose one assignment strategy for a matched blueprint:

• Manual — staff select subjects. Safest for a first rollout or irregular curricula.
• Recommendation only — the system suggests curriculum subjects but staff confirm them.
• Automatic curriculum — valid curriculum subjects are assigned automatically.

What this does

Assignment strategies are selected by stable keys and validated settings. They do not allow arbitrary formulas or scripts.

Class assignment

Manual assignment leaves sections to staff. First-available assignment reserves a class only inside a database transaction and locks capacity records, protecting the final seat from concurrent enrollments.

Before enabling automatic class assignment, confirm:

• Class capacities are accurate.
• Schedules are complete.
• Conflict checks are enabled when required.
• Staff know how to retry a failed transition.

Tuition calculation

The core course-rate strategy materializes its behavior into the enrollment snapshot. Its compatibility defaults include NSTP lecture pricing, modular laboratory and per-subject pricing, course miscellaneous fees, additional fees, and lecture-only discounts. Later PHP default changes therefore cannot reinterpret an enrollment already in progress.

An authorized enrollment submission may carry a one-off miscellaneous override and a billing override. The assessment stores both the reusable discount_id and the applied percentage snapshot so later edits to a discount preset do not rewrite historical tuition.

Payment methods

Choose the methods accepted by this policy, such as cash, bank transfer, or supported online channels. A method must also be operational in the school’s finance configuration.

Receipt behavior is also explicit:

• Required — a receipt or invoice identifier must be supplied.
• Optional — a configured transition may accept either form.
• None — permitted only by an authorized no-receipt transition with an audited reason.

Minimum-payment gates

• No minimum — payment does not block the configured completion action.
• Fixed amount — require a specific currency amount.
• Percentage — require a portion of calculated tuition.

Minimum-payment rules are deferred while an applicant starts enrollment. They are enforced inside the terminal transition after configured payment actions run, and policy simulations identify them as completion gates rather than entry blockers.

A no-payment blueprint omits the payment action entirely; it does not synthesize a zero-value transaction.

Billing sections replace atomically

When a scoped blueprint overrides billing, it owns the complete billing strategy and payment-method section. This avoids mixing incompatible pieces from multiple strategies.

Common scenarios

Manual enrollment with payment later

Use manual assignment, course-rate tuition, accepted payment methods, and No minimum. Keep assessment generation in the workflow if students still need an official statement.

Public manual applications do not synthesize curriculum or class selections. Staff can make those selections through the configured assisted workflow; automatic curriculum policies continue to resolve subjects through their pinned assignment strategy.

Reserve a class after cashier verification

Place class assignment on the cashier approval transition or the next authorized step. Keep the capacity action transactional and test a full class and a final-seat contention case.

Scholarship discount

Configure the supported discount in the billing strategy and use an eligibility rule for approved scholarship status. Do not encode an arbitrary formula in a backup file.

Verify with simulation

Test at least:

1. A regular student with full tuition
2. A discounted student
3. A student below the payment gate
4. A student at the unit limit
5. A student competing for the last available class seat