Dissociate or associate a price plan with an account

Mode of request to create dis/association

Id of the price plan if association request

Date of effectiveness of the association. The date is expected in YYYY-MM-DD format

• Editing of a BILLING plan with deferredRevenue can be achieved with effectiveFrom as start date of current cycle or using retainStartOffset option.

Date until which the association must be effective. The date is expected in YYYY-MM-DD format

If this flag is true, current pricing cycle of the account on the date of association will continue rather than the configurations of the newly associated price plan. Pricing cycle overrides specified using pricePlanDetailsOverride will take precedence over the pricing cycle configurations of the new price plan that the account needs to migrate to. PricingCycleInterval of the existing plan and the new plan must be same for this to work. We'll return a 400 BadRequest otherwise. Examples:

• Ongoing plan (1st Oct to 30th Oct) - {dayOffset: 1, monthOffset: NIL} New association (15th Oct to 15th Nov) of different price plan with retainStartOffsets option true will use the same pricing cycle configuration {dayOffset: 1, monthOffset: NIL} rather than using the pricing cycle configuration of the new price plan that the account needs to migrate to.
• Ongoing plan (1st Oct to 30th Oct) - {dayOffset: 1, monthOffset: NIL} New association (1st Nov to 30th Nov) of different price plan with retainStartOffsets option true will throw a 400 BadRequest as no existing price plan configuration found on date of association

Identifier of the account

Name of the Account