More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
docs
betterdocs_faq

Check for lack of installments with financial transactions before saving the selected arrangement plan

Updated on July 7, 2026

3 min to read

Overview

Check for lack of installments with financial transactions before saving the selected arrangement plan/Elegxos_Gia_Elipsi_Minon_Me_Oikonomiki_Kinisi_Kata_Tin_Apothikeusi_Diakanonismou is a setting located under Financial Settings > General Settings > Arrangements Parameters, in the Arrangement Modifications sub-group.

 

What This Setting Does

This setting adds a safety check when editing an existing financial Arrangement. When a user changes the billing plan of an Arrangement, Classter checks whether any installment (month) that already has a payment linked to it would be removed by the new plan. This helps prevent accidentally deleting an installment that has already received a payment.

 

Where It Is Used

This check is implemented as a save-time validation in the backend when an Arrangement’s billing plan is changed. It affects:

  • Main Menu > Financial > Arrangements List – opening a Student’s existing Arrangement and selecting a new billing plan is where this save-time check would trigger.

 

Business Logic / Behavior

  • When enabled, before an edited Arrangement is saved, Classter checks whether the new billing plan removes any installment (month) that already has a financial transaction (payment) associated with it.
  • If such an installment would be removed, Classter blocks or warns against the save to protect the recorded payment from being orphaned or lost.
  • When disabled, users can freely switch billing plans, potentially removing installments that already have payments linked to them.

 

Example(s)

At Alpha Institute, an accountant named Priya is editing the 10-installment Arrangement of a Student named Sam C.. Sam has already paid $300 against the March 2026 installment, bringing its balance from $300 down to $0. Priya then tries to switch Sam’s Arrangement to a new 8-installment billing plan that no longer includes a March installment. With this setting enabled, Classter detects that the March installment already has a $300 payment recorded against it and blocks the save with an error, until Priya either keeps a March installment in the new plan or manually reassigns the $300 payment first.

 

When to Use

Use this setting whenever the institution wants extra protection against losing track of installments that already have payments recorded.

 

When to Enable

Enable this to have Classter actively check and prevent the removal of already-paid installments when a billing plan is changed, reducing the risk of reconciliation issues.

 

When to Disable

Disable this if the finance team needs unrestricted flexibility to change billing plans, including removing installments that already have payments, for example when manually restructuring an Arrangement and handling the payment reassignment separately.

 

Notes

No prerequisites are required for this setting; it operates independently as a validation rule on Arrangement editing.

  • Edit existing arrangement: Check if the new billing plan installment amounts are higher than the already invoiced amounts (Elegxos_Gia_Diafora_Posou_Tomologithisas_Dosis_Kai_Epilegmenou_Planou_APY_Kata_Tin_Apothikeusi_Diakanonismou in Financial Settings > General Settings > Arrangements Parameters > Arrangement Modifications)
  • Delete arrangement when the selected user types terminate/stop a service (Delete_Arrangement_When_User_Stops_Service in Financial Settings > General Settings > Arrangements Parameters > Arrangement Modifications)

 

This setting behaves the same regardless of whether Higher Education Mode (Enable Configuration for Higher Education/Xrisi_parametropoihshs_kolegiou) is enabled or disabled.

 

Was this article helpful?