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

Edit existing arrangement: Check if the new billing plan installment amounts are higher than the already invoiced amounts.

Updated on July 7, 2026

3 min to read

Overview

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 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 someone edits an existing financial Arrangement for a Student. Before Classter allows the changes to be saved, it compares the new billing plan against the amounts that have already been invoiced. If the new plan would set any installment amount lower than what has already been invoiced for that installment, Classter blocks the save so the user cannot accidentally undercharge an already-billed installment.

 

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 changing its billing plan is where this save-time check would trigger.

 

Business Logic / Behavior

  • When enabled, Classter compares each installment in the newly selected billing plan against the amount already invoiced for the corresponding installment.
  • If any installment amount in the new plan is smaller than the amount already invoiced, Classter prevents the Arrangement from being saved.
  • This is a preventive/validation check only – it does not automatically correct the plan; it simply blocks the save until the user selects a compatible billing plan or amount.
  • When disabled, users can freely change the billing plan on an Arrangement regardless of previously invoiced amounts, which could result in installments with an invoiced amount higher than the newly configured installment amount.

 

Example(s)

At Alpha Institute, a finance officer named Alex is updating the Arrangement for a Student named Jordan M.. Two installments have already been invoiced at 200 each. Alex tries to switch Jordan’s Arrangement to a new billing plan where those same two installments are only 150 each. With this setting enabled, Classter blocks the save and alerts Alex that the new plan would reduce an installment below what has already been invoiced, prompting Alex to pick a plan with compatible amounts.

 

When to Use

Use this setting whenever the institution wants to protect the integrity of billing plans against being retroactively reduced below what has already been billed to a Student.

 

When to Enable

Enable this when the finance team wants Classter to actively prevent staff from saving a modified Arrangement that would lower an installment amount below its already-invoiced value, reducing billing errors and disputes.

 

When to Disable

Disable this if the institution needs full flexibility to adjust billing plans at any time, including lowering installment amounts below previously invoiced values, for example when manually correcting billing mistakes or issuing retroactive reductions.

 

Notes

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

  • 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 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?