Skip to main content
Aria Knowledge Central

assign acct plan m Error Messages

Error Codes

Error Code/Description Associated Inputs

1001: unexpected error


1004: authentication error

Associated Inputs: auth_key, client_id, client_no

<auth_key>, <client_no>

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

Associated Inputs: acct_no, account_no, client_acct_id, user_id, userid, parent_acct_no

<acct_no>, <client_acct_id>

1010: missing required parameters, Missing input: (object-name) is required with assignment_directive ($AriaNo)

Associated Inputs: all required inputs, typically one of the following: custom_rate_per_unit, custom_rate_seq_no, status_cd, dunning_state, userid, acct_no, client_acct_id, assignment_directive, billing_group_no, client_billing_group_id, threshold_billing_rule_no, client_threshold_billing_rule_id

Alternate Message Output

1010: username is required
1010: first name is required
1010: last name is required
1010: email is required
1010: roles are required

Associated APIs: create_user_m, get_user_details_m, delete_user_m, update_user_m

Associated Inputs: username, first_name, last_name, email, role_no

<custom_rate_per_unit>, <custom_rate_seq_no>, <acct_no>, <client_acct_id>, <assignment_directive>

1012: invalid input format

Associated Inputs: client_receipt_id

Additional Comments: This value must be unique for a client and must be alphanumeric. A previously used client_receipt_id can be reused if all those previous calls have failed (with an error_code other than 0/OK), if the client parameter NEVER_ALLOW_USED_RECEIPT_ID = FALSE.

Alternate Message Output

1012: email is invalid
1012: include_archived_user is invalid
1012: status is invalid

Associated APIs: create_user_m, get_users_m, update_user_m

Associated Inputs: email, include_archived_user, status


1016: invalid input, acct_no: (acct_no) is not a valid long, assignment_directive: (assignment_directive) is not a valid long, “billing_group_no: (billing_group_no) is not a valid long, threshold_billing_rule_no: (threshold_billing_rule_no) is not a valid long

Associated Inputs: alt_service_no_to_apply, assignment_directive, auto_skip_to_next_bill_date, client_billing_group_id, custom_rate_service_no/custom_rate_client_service_id, plan_instance_no, plan_instance_service_no, client_plan_instance_id, client_plan_instance_service_id, plan_instance_no, plan_instance_service_no, client_plan_instance_id, client_plan_instance_service_id, plan_instance_service_no, eligible_plan_no, eligible_service_no, email, force_master_bill_date_reset, fulfillment_only, include_master_plans, include_supp_plans, include_billing_groups, include_payment_methods, include_master_plans, include_supp_plans, include_billing_groups, include_payment_methods, invoice_no, length_months, end_date, limit, limit_records, modify_directive, contract_plan_instances_update, modify_directive, contract_plan_instances_update, offset, percent_amount, percent_eval_plan_instance_no, client_percent_eval_plan_instance_id, percent_eval_service_no, client_percent_eval_service_id, phone_ext, work_phone_ext, plan_unit_inst_status_cd, plan_units, reason_code, start_date, end_date, start_date, end_date, status_cd, acct_no, assignment_directive, billing_group_no, threshold_billing_rule_no

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

  • For the get_order_m API, this is the error code returned when the user passes an invalid order value for the <status_filter_cd> input which is other than the allowed values (0/null, 1, 2, 3, 4 and 5).
  • For the bulk_cancel_order_m API, invalid input can occur with the <order_status_directive> argument. Allowed values are 0, 1, 2, 3, 4/null, 5 and 6.
  • For the get_acct_coupon_details_m API, invalid input can occur with the <include_all_active> input parameter (values are 0, 1 or NULL).

Alternate Message Output

1016: username cannot be longer than 30 characters
1016: first_name cannot be longer than 30 characters
1016: last_name cannot be longer than 30 characters

Associated APIs: create_user_m, update_user_m

Associated Inputs: username, first_name, last_name

<assignment_directive>, <client_def_billing_group_id>, custom_rate_service_no/custom_rate_client_service_id>, <client_plan_instance_id>, <force_master_bill_date_reset>, <offset_months>, <plan_units>, <acct_no>

1024: invalid date format

Associated Inputs: bill_birthdate, birthdate, degrade_date, initial_credit_date, invoice_line_reversing_date, service_fulfillment_date, queue_date, start_bill_date, end_bill_date, start_date, end_date, stmt_birthdate, bill_birthdate

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

<bill_birthdate>, <alt_start_date>, <stmt_birthdate>

1031: can not pass in an alternate starting date AND alternate billing day

Associated Inputs: alt_bill_day, alt_start_date

<alt_bill_day>, <alt_start_date>

1033:  a parameter that represents a true or false value contains invalid input

Associated Inputs: alt_collect_on_approve, alt_send_statement_on_approve, cancel_orders_on_discard, cascade_action, do_auto_discard, do_collect, change_status_after_coll, reset_dates_after_status, disable_existing_on_update, do_write, exclude_terminated_plan_inst, include_all_rate_schedules, include_plan_hierarchy, retrieve_bundled_nso, retrieve_included_nso, include_translations, include_inactive_items, include_invoice_activity_eligibility, include_rs_summary, include_translations, include_service_supp_fields/include_product_fields/, include_plan_instance_fields/include_plan_services/, include_surcharges, include_void_transactions, include_voided, invoice_unbilled_usage, is_unlinked_refund, record_cc_on_auth_failure, retrieve_excluded_usage, send_email, usage_pooling, do_write

<do_write>, <usage_pooling>

1035: invalid assignment directive, Invalid Assignment Directive: (assignment_directive)

Associated Inputs: master_plan_assign_directive, assignment_directive


1049: Billing or Plan changes not allowed due to the account status, Cannot add assignment for account with status code -99, Cannot add assignment for account with status code 0

Associated Inputs: N/A

Additional Comments: This message indicates a processing problem.


1053: invalid notification template group id

Associated Inputs:billing_group.notify_template_group


1069: Long cycle (Combine invoice) is not available, since Plan instance has Plan rollover or contract rollover or future Plan changes in the middle of the cycle or while generating a pending invoice.


1500: Unsupported bank/country code for this payment method.

Associated Inputs: proc_status_code, proc_status_code, bank_country_cd

Additional Comments: Added in support of ACH payments via Direct Debit (country code must be US).


3017: pro-ration period cannot be greater than Plan billing interval


3018: invalid automatic offset months option


4006: invalid pay method or alternate pay method

Associated Inputs: alt_pay_method, pay_method_type, pay_method_type


4008: invalid expiration date

Associated Inputs: alt_pay_method, cc_expire_mm, cc_expire_yyyy, credit_expiry_date, pay_method_type

Additional Comments: Dates must be in yyyy-mm-dd format.

<cc_expire_mm>, <cc_expire_yyyy>

4009: invalid cc number

Associated Inputs: cc_number, alt_pay_method, cc_num, pay_method_type


4010: invalid bank draft info

Associated Inputs: bank_acct_no, bank_routing_no, alt_pay_method

Additional Comments:

  1. The client parameter BANK_DRAFT_INDICATOR must be enabled.
  2. Bank_acct_no and bank_routing_no are required.
  3. Valid bank_routing_no from Aria's ABA lookup in case of US address.
  4. Bank_routing_no must be numeric.
  5. For US, bank_routing_no should be 9 digits in length (left padded with zeros).
  6. Bank_routing_no must pass checksum validation.
<bank_acct_no>, <bank_routing_no>

4017: duplicate payment method client defined id.

Associated Inputs: client_payment_method_id, new_client_payment_method_id

Additional Comments: This value must be unique at the client level.


4019: Invalid Bank Account Type.

Associated Inputs: alt_pay_method, bank_acct_type


4032: cc_id is required.

Associated Inputs: cc_id, pay_method_type

Additional Comments: cc_id is required for this payment processor.


4044: Missing a required value. Please check that either bank_account_no, bank_routing_number or agreement_id is present.


5003: invalid notify method

Associated Inputs: notify_method_no


5004: invalid responsibility level cd

Associated Inputs: resp_level_cd

Additional Comments: Resp_level_cd=4 is not supported in Aria Billing Cloud.


5020: alternate billing day must be between 1 and 31

Associated Inputs: alt_bill_day


5041: Invalid invoicing option provided

Associated Inputs: invoicing_option


5052: Product field is not mapped to the Plan you have specified. Alt: Invalid product field

Associated Inputs: plan_instance_fields_info.field_name, field_name

Additional Comments: The field is not mapped to the Plan.


5053: Missing values for required Plan instance field

Associated Inputs:   plan_instance_field_value

Additional Comments: This field is required, but did not have a value.


5059: Invalid Product Field Value.

Associated Inputs: field_value

Additional Comments: The value must be from the configured allowed values.


5061: Number of Product Field value exceeds maximum number of allowed values.

Associated Inputs: field_value

Additional Comments: The value must meet the configured maximum values.


5062: Number of Product Field values does not meet required minimum number of values.

Associated Inputs: field_value

Additional Comments: The value must meet the configured minimum values.


5019: error recording balance forward

Associated Inputs: balance_forward

Additional Comments: This indicates an error in the balance forward transaction creation.


6021: Invalid state_prov entered

Associated Inputs: bill_state_prov, state_prov, stmt_state_prov, bill_state_prov

<bill_state_prov>, <stmt_state_prov>

6027: IBAN is alphanumeric and is 15 to 34 characters in length

Associated Inputs:  iban, alt_pay_method_iban


6029: Bank swift code is alphanumeric and is 8 or 11 characters in length

Associated Inputs: bank_swift_cd, alt_pay_method


6031: BBAN is numeric and up to 16 digits

Associated Inputs: alt_payment_method, bank_acct_no


6032: Bank ID code is numeric and up to 10 digits


6033: Bank branch code is numeric and up to 10 digits

Associated Inputs: bank_branch_cd


6034: Basic bank account number or IBAN is required for Direct Debit

Associated Inputs: iban, bank_acct_no

<iban>, <bank_acct_no>

6045: Account can have only one active NETS payment method.

Associated Inputs: payment_method_type


6053:Either IBAN or Agreement ID is required for this payment method. 

Associated Inputs: iban, bill_agreement_id, pay_method_type, alt_pay_method

<iban>, <bill_agreement_id>, <primary_pay_method_type>

7028: duplicate billing group client defined id.

Associated Inputs: client_billing_group_id, new_client_billing_group_id

Additional Comments: This value must be unique at the client level.


7029: The new_client_dunning_group_id field contains the ID of an existing dunning group.

Associated Inputs: client_dunning_group_id

Additional Comments: This value must be unique at the client level.


7031: Invalid dunning_process_no

Associated Inputs: dunning_process_no


7033: Invalid client defined dunning process id

Associated Inputs: client_dunning_group_id


7035: The Plan selected for update is a Master Plan. The force_master_bill_date_reset input can only be used in conjunction with Supplemental Plans. Please clear the value of force_master_bill_date_reset or input a Supplemental Plan.

Associated Inputs: force_master_bill_date_reset


12010: Client account group does not exist

Associated Inputs: collections_acct_group_no, client_acct_group_id, alt_client_acct_group_id


12012: Collection group does not exist


12013: Collection group identifier does not exist


12016: Billing group belongs to collections based group using same payment method


14004: Invalid_plan_no

Associated Inputs: new_plan_no, rollover_plan_no


14006: invalid rate schedule no

Associated Inputs: acct_rate_schedule_no, mpi_rate_schedule_no, master_plans_detail, alt_rate_schedule_no, supp_plan.alt_rate_schedule_no

<mpi_rate_schedule_no>, <alt_rate_schedule_no>

14012: Alternate rate schedule's currency does not match the account's currency.

Associated Inputs: alt_rate_schedule_no, client_alt_rate_schedule_id

Additional Comments: The alt_rate_schedule currency does not match the  account currency.

<alt_rate_schedule_no>, <client_alt_rate_schedule_id>

14016: The Plan is already assigned to the account

Associated Inputs: new_plan_no


14017: invalid alternate proration start date Alt: Date must be in YYYY-MM-DD format

Associated Inputs: alt_proration_start_date

Additional Comments: The alt_proration_start_date must be within the last billed period.


14019: usage_accumulation_reset_months must be from 0 to 99  Alt: invalid usage accumulation reset months value

Associated Inputs: usage_accumulation_reset_months

Additional Comments: The accumulation months is not between 0 and 99.


14022: Supplemental Plan violates Plan exclusion group

Associated Inputs: plan_no

Additional Comments: The Supplemental Plan is not matched with the Master Plan exclusion group.


14023: Offset Interval must be greater than zero

Associated Inputs: offset_interval


14024: Invalid Offset Interval and Assignment Directive combination.

Associated Inputs: offset_interval, assignment_directive

Additional Comments: Offset_interval only applies to the anniverary date.

<offset_interval>, <assignment_directive>

14025: Invalid do_write and assignment directive combination for queuing Plan.

Associated Inputs: assignment_directive, do_write

Additional Comments: Preview cannot be done for queued anniversary date cases.

<assignment_directive>, <do_write>

14026: The Effective Date must be in the future, "YYYY-MM-DD" format, and a valid date.

Associated Inputs: effective_date


14033: Invalid Promo Code

Associated Inputs: promo_cd


14035: Invalid client Plan id

Associated Inputs: client_plan_id, custom_rate_client_plan_instance_id


14036: Invalid client service id

Associated Inputs: client_service_id, client_plan_instance_service_id, client_percent_eval_service_id, custom_rate_client_service_id

<client_service_id>, <custom_rate_client_service_id>

14039: Invalid client rate schedule id

Associated Inputs: client_alt_rate_schedule_id, rollover_client_rate_sched_id


14042: Promo Code Expired

Associated Inputs: promo-cd


14045: Promo code's start date is in the future

Associated Inputs: promo_cd


14049: Invalid parent Plan instance no

Associated Inputs: parent_plan_instance_no


14050: Parent Plan instance is required

Associated Inputs: parent_plan_instance_no or client_parent_plan_instance_id

Additional Comments: A Supplemental Plan was entered without a parent Plan.

<parent_plan_instance_no> or<client_parent_plan_instance_id>

14051: Invalid Plan status for the new Plan

Associated Inputs: plan_instance_status, status_cd


14063: duplicate Plan instance client defined id.

Associated Inputs:client_plan_instance_id, new_client_plan_inst_id

<client_plan_instance_id>, <new_client_plan_id>

14065:Promo code not allowed for Supplemental Plan

Associated Inputs: promo_cd


14066: Assignment directive cannot be anniversary for Master Plan

Associated Inputs: assignment_directive


14072: Offset interval not allowed for Master Plan assignment.

Associated Inputs: offset_months


14075: Supplemental Plan not eligible under this Plan instance.

Associated Inputs: new_plan_no


14077: Account status not support Plan provisioning.

Associated Inputs: status_cd

Additional Comment: The current status of the account does not allow provisioning.


14078: Master Plan Instance status not support Plan provisioning.

Associated Inputs: status_cd

Additional Comments: The current status of the Master Plan does not allow provisioning.


14079: Supplemental Plan instance status not support Plan provisioning.

Associated Inputs: supp_plan.status_cd


14084: Invalid rate schedule. Please verify start date and end date of provided rate schedule.

Associated Inputs: alt_rate_schedule_no, alt_rate_schedule_id

<alt_rate_schedule_no>, <client_alt_rate_schedule_id>

14086: Plan Units cannot be below the minimum required units for this child Plan.

Associated Inputs: plan_units


14087: The maximum number of allowable units has been exceeded.


14098: Invalid proration invoice timing

Associated Inputs: mp_proration_invoice_timing, proration_invoice_timing


14102: Invalid parent Plan instance id

Associated Inputs: parent_client_plan_instance_id

<resp_client_master_plan_instance_id>, <client_plan_instance_id>, <client_parent_plan_instance_id>

14108 Plan cannot be queued because parent Plan instance's status is non-provisioned

Associated Input: assignment_directive


14109 Plan cannot be queued because Master Plan Instance is in dunning or has completed dunning(i.e., dunning state is 'In Progress' or 'Completed')

Associated Input: assignment_directive


14110 The effective date of a queued child Plan assignment must be on or after the effective date of the queued parent Plan assignment

Associated Inputs: effective_date


14111 Plan cannot be queued because parent Plan instance is not in scheduled queue ie. Effective date is not given


14112 Cannot update/replace/cancel any queued Plan instance which is in queued assignment

Associated Inputs: plan_instance_no, client_plan_instance_id


14113 The Plan provided is not a valid child of the Plan that will be associated with the parent Plan instance on the effective date provided

Associated Inputs: new_plan_no


14123: Cannot assign child Plan with assignment scope as immediate/anniversary when the parent Plan is in queue


14124 The effective date of a queued parent Plan assignment must be on or before the effective date of the queued child Plan assignment


14132: Custom rates cannot be assigned for this non-provisioned status.


14135: The Responsible Master Plan Instance provided is queued for assignment and not allowed to be used for payment responsibility.


14136: Offset months must be greater than or equal to 0.


14137: To permit usage pooling on plans the invoice settings parameter 'Allow MPI Level Usage Pooling' needs enabling.


14310: Enter a Bill Lag days between +/- Plan's Billing Interval.

Additional Comments: Invalid input: For bill lag days, Enter a number between +billing interval and - billing interval days.


14311: Enter a Bill Lag days less than/equal to Plan's Billing Interval.

Additional Comments: Invalid input: For bill lag days, Enter a number less than/equal to billing interval days.


14402: Usage Pooling is not allowed when the Rating Model rates usage on a ‘per record’ basis.


15001: invalid coupon code

Associated Inputs: coupon_codes


15002: coupon expired

Associated Inputs: coupon_codes, coupon_cd


15006: Duplicate surcharge number in input

Associated Inputs: acct_surcharges, mpi_surcharges, mp_surcharge_no

<mpi_surcharges>, <mpi_surcharge_no>

15008: Invalid surcharge rate schedule no

Associated Inputs: rate_schedule_no, mp_rate_schedule_no


15009: Invalid surcharge number

Associated Inputs: surcharge_no, mp_surcharge_no

<mpi_surcharges>, <mpi_surcharge_no>

15010: Coupon code not allowed for Supplemental Plan

Associated Inputs: coupon_cd


15011: The coupon code provided for this account or Master Plan does not match its specified Coupon Applicability Scope, which determines whether the coupon is available at the account level, the Master Plan Instance level, or both.

Associated Inputs: coupon_cd


15012: Coupon code has already been applied and cannot be used again.

Associated Inputs: coupon_codes


15013: The surcharge provided for this Account or Master Plan does not match its specified Surcharge Applicability Scope, which determines whether the surcharge is available at the account level, Master Plan Instance level or both.

Associated Inputs: mpi_surcharges, mp_surcharge_no

<mpi_surcharges>, <mpi_surcharge_no>

15014: Duplicate Surcharges found.

Associated Input: mp_surcharge_no


15015: Surcharge can't be assigned because its application scope is payment method

Associated Inputs: mpi_surcharges, mp_surcharge_no

<mpi_surcharges>, <mpi_surcharge_no>

18005: Invalid Template number

Associated Inputs: alt_msg_template_no, cn_alt_msg_template_no, alt_inv_template_no, alt_stmt_template_no

<credit_memo_template>, <rebill_template>, <client_notification_template_group_id>

18010: Invalid Credit Memo Template number

Associated Inputs: credit_memo_template

Additional Comments: The credit memo template must be mapped to the "CM" template class.


18011: Invalid Rebill Template number

Associated Inputs: rebill_template

Additional Comments: The rebill template must be mapped to "RB" template class.


20026: agreement id OR credit card info is required

Associated Inputs: pay_method_type, bill_agreement_id, cc_num

Additional Comments: The pay_method_type is "13", the bill_agreement_id is null and cc_num is null.

<primary_pay_method_type>, <bill_agreement_id>, <cc_number>

20031: agreement id is mandatory for this payment method

Associated Inputs: pay_method_type, bill_agreement_id

Additional Comments: The pay_method_type is "29" and the bill_agreement_id is null.

<primary_pay_method_type>, <bill_agreement_id>

23013: Invalid usage threshold applicability

Associated Inputs: usage_threshold_applicability

Additional Comments: The usage_threshold_applicability is not in, "ut" or "up".


25001: failed to calculate taxes


25020: Illegal characters entered

Associated Inputs: All character field inputs like firstname lastname, dunning_group_name, comments, etc.


25032: The override_bill_thru_date must be in the future, must be after the alt_start_date, retroactive_start_date, or effective_date (if provided), and cannot exceed one recurring billing interval in the future.

Associated Inputs: override_bill_thru_date, alt_start_date, retroactive_start_date, effective_date

Additional Comments: Override_bill_thru_date is before alt_start_date, retroactive_start_date, or effective_date.

<override_bill_thru_date>, <alt_start_date>, <retroactive_start_date>, <effective_date>

25034: When override_bill_thru_date, override_dates_mp_instance_no, or override_dates_client_mp_instance_id is specified, alt_bill_day cannot be used.


25035: When override_bill_thru_date, override_dates_mp_instance_no, or override_dates_client_mp_instance_id is specified, status_until_alt_start cannot be used (defaults to Inactive).


25036: When override_bill_thru_date, override_dates_mp_instance_no, or override_dates_client_mp_instance_id is specified, invoicing_option must be configured to be Perform Prorated Invoicing.


25037: invalid override dates mp instance no or override dates client mp instance id.

Associated Inputs: override_dates_mp_instance_no/override_dates_client_mp_instance_id

<override_dates_mp_instance_no>, <override_dates_client_mp_instance_id>

25039: To align the billing dates of the new Master Plan being assigned with the existing Master Plan Instance on the account, the bill_thru_date of the existing Master Plan Instance must be in the future.


25040: Effective date is required when an assignment directive is in the future and override bill thru date is used.


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.


26007: Provided client defined pay method ID does not exist for this account.

Associated Inputs: client_payment_method_id, client_primary_payment_method_id, client_backup_payment_method_id

<existing_client_primary_payment_method_id>, <existing_client_backup_payment_method_id>

26008: Provided payment_method_id does not exist for this account.

Associated Inputs: payment_method_no, payment_method_no, client_payment_method_id, primary_payment_method_no, backup_payment_method_no

<existing_client_primary_payment_method_id>, <existing_client_backup_payment_method_id>

26010: Invalid billing group number

Associated Inputs: billing_group_no


26012: Invalid client-defined billing group ID.

Associated Inputs: client_billing_group_id


26013: Invalid dunning group number

Associated Inputs: dunning_group_no


26014: Invalid client-defined dunning group ID.

Associated Inputs: client_dunning_group_id


26019: Provided primary payment method idx or primary payment method client defined id is invalid

Associated Inputs: primary_payment_method_idx, primary_client_payment_method_id


26020: Provided secondary payment method idx or secondary payment method client defined id is invalid

Associated Inputs: backup_client_payment_method_id, backup_payment_method_idx


29005: The contact number provided is invalid for the specified account.

Associated Inputs: acct_contact_no, bill_contact_no, stmt_contact_no

<item_dest_contact_no>, <bill_contact_no>, <stmt_contact_no>, <dest_contact_no>


  • Was this article helpful?