Skip to main content
Aria Knowledge Central

update_payment_plan_m Guide

The update_payment_plan_m API updates an existing payment plan schedule on a specified account. It allows you to:

  • update a payment plan aligned with a master plan instance;
  • update the payment method associated with a payment plan;
  • update a payment plan schedule. You can initiate two types of modifications: 
    • modify specific payment plan sequences (dates, due amounts, or both); or
    • modify remaining payment plan sequences.
  • initiate a lump sum collection.

Fields that are not updated will retain their original definition, unless they are specified.

API Specification:

update_payment_plan_m

Required Fields:

  • <client_no>
  • <auth_key>
  • <acct_no> or <client_acct_id>
  • <payment_plan_no> or <client_payment_plan_id>

Additional Guidance

  • When modifying specific sequences (dates, due amounts, or both), note:
    • When you change a specified sequence due amount, Aria will recalculate and distribute the remaining amount evenly to other sequences not specified.
    • This modification does not change the number of sequences in the payment plan schedule.
    • You can update dates only without changing the due amount (independent only).
    • You can update the due amount only without changing the dates.
    • You cannot modify the last sequence due amount.
  • When modifying remaining sequences, note:
    • When you alter the due amount, the number of sequences could change (e.g. from 3 sequences to 5 sequences).  
    • When you specify one sequence, Aria replicates the change to the remaining sequences.
    • In this type of change, Aria uses the original payment plan interval and type to calculate the schedule changes.
    • When you alter a due amount, it impacts the length of the payment plan: it becomes longer if the new due amount is lower; or shorter if new due amount is higher.
  • You can only modify unnotified sequences that are neither partially nor fully paid.
  • You cannot modify notify dates nor due dates for aligned payment plans.
  • The amount you enter per sequence is tax inclusive.
  • When an account misses a sequence due date and Aria puts a subscription into dunning: if you modify that specific sequence due date to a future date, Aria removes the subscription from dunning the next day.

Input Fields

Field Name Notes
<update_scope>

Specifies how the system should apply those changes.

Allowable Values
Values Description
0 Apply changes to specified sequences only (default)
1 Apply changes to the remaining sequences, start with specified sequence
2 Create a New Schedule for the remaining unpaid balance including those dues have been notified.
<do_write>

Boolean indicator that specifies whether to perform the requested operation or not.

Allowable Values
Values Description
true Performs the requested operation (default)
false Returns potential effects without performing the operation

<new_payment_plan_type>

Defines the type of payment plan for the remaining unpaid balance.

Allowable Values

Values Description
0 Independent (own schedule and due dates)
1 Aligned (with an existing master plan instance anniversary statement)
If null, defaults to 0 – Independent.

<new_payment_plan_period_type>

Specifies the payment plan period type. This field is mandatory when <new_payment_plan_type> = 0.

Allowable Values

Values Description
M Months
W Weeks
D Days

Error Codes

Error Code/Description Associated Inputs

1001: unexpected error

 

1009: account does not exist, Account not found: AriaNo (acct_no), Account not found: Userid (userid), or Account not found: ClientId (client_acct_id)

<acct_no>, <client_acct_id>

1016: invalid input

Additional Comments:  This error can be caused by the wrong type of input; for example, text in a numbers-only field, or specifying a value other than one of the documented allowable values.

<payment_plan_no>, <client_payment_plan_id>, <primary_payment_method_no>, <client_primary_payment_method_id>, <backup_payment_method_no>, <update_scope>, <seq_no>, <notify_date>, <due_date>, <due_amount>, <update_specific_sequence_list>, <new_independent_payment_plan_date>

1024: invalid date format

Additional Comments: All date inputs must be in yyyy-mm-dd format.

<notify_date>, <due_date>, <new_independent_payment_plan_date>

14046: If you passed in an invalid plan_instance_no, this message will appear: "Invalid Plan instance number". If you passed in an invalid master_plan_instance_id, this message will appear: "Invalid master_plan_instance_id".

Additional Comments: The plan_instance_no or master_plan_instance_id must belong to the account, or it is invalid. The percent_eval_plan_instance_no must belong to the account and also to the MPI given in input.

<aligned_payment_plan_master_plan_instance_no>

14047: If you passed in an invalid client_plan_instance_id, this message will appear: "Invalid client Plan instance identifier". If you passed in an invalid client_master_plan_instance_id , this message will appear: "Invalid client_master_plan_instance_id".

<aligned_payment_plan_client_master_plan_instance_id>

26003: The API execution is not supported because your client parameter Account_EOM_Enabled is set to False. Please contact Aria customer support with questions about the Account_EOM_Enabled client parameter.

<client_no>
TOP
  • Was this article helpful?