The contract extension uses the ch_defer_payment_start flag to define, whether a follow-up mandate (e.g. after a change of rhythm or IBAN) should start asap (value 0) or the current collection rhythm should be upheld (value 1).
This flag, however, is currently not exposed in the backend UI - but it should be.
The contract extension uses the
ch_defer_payment_startflag to define, whether a follow-up mandate (e.g. after a change of rhythm or IBAN) should start asap (value0) or the current collection rhythm should be upheld (value1).This flag, however, is currently not exposed in the backend UI - but it should be.