A backdated plan change is rejected
Backdating only reaches the 1st of the current month, and only while no invoice exists for that month.
What you see
You want to backdate a member's plan to the 1st of this month, and the app does not accept it.
Why
A plan change generally takes effect on the 1st of the following month, no matter which day you enter it. As an operator you may override that rule in one respect and backdate to the 1st of the current month. It does not reach further back.
The change is rejected when an invoice already exists for a month in the affected window. An issued invoice cannot be recalculated afterwards, and a change that re-values the period would demand exactly that.
What you can do
- Check the invoice archive for which invoice covers the month. It can be up to three documents. See Three documents per month.
- Schedule the change for the 1st of the following month. That is the normal case and needs no exception.
- If the existing invoice really is wrong, you correct it with a credit note in your accounting system. selfdesk cannot withdraw an issued invoice. See Issued invoices are frozen.
- If the change goes through, desk usage in the window that has not been billed yet is re-priced. Prices of rooms already booked stay as they were. The member gets an email, and the action lands in the audit log.
If all you want is for one member to pay less, an individual price on the member is the quieter route than a backdated change. See Individual price for a member.
If that is not enough
If the app does something wrong: report a problem.