Skip to main content
Aria Knowledge Central

update acct complete m Error Messages

Error Code/Description Associated Inputs

1001: unexpected error

 

1004: authentication error

<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)

<acct_no>, <client_acct_id>

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

<client_no>, <auth_key>, <acct_no> or <client_acct_id>

1012: invalid input format

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.

<client_receipt_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.

<client_no>, <acct_no>, <acct_contact_idx>, <acct_contact_no>, <status_cd>, <notify_method>, <senior_acct_no>, <test_acct_ind>, <alt_msg_template_no>, <cn_alt_msg_template_no>, <seq_func_group_no>, <tax_exemption_level>, <invoicing_option>, <alt_bill_day>, <functional_acct_group_no>, <collection_acct_group_no>, <collection_acct_grp_directive acct_supp_field_directive surcharge_no>, <surcharge_directive>, <rate_schedule_no master_plan_instance_no>, <master_plan_no>, <dunning_group_no>, <mp_billing_group_no>, <master_plan_instance_status>, <master_plan_units>, <resp_level_cd>, <alt_rate_schedule_no>, <master_plan_assign_directive>, <offset_months>, <offset_interval>, <usage_accumulation_reset_months>, <plan_instance_field_directive>, <mp_surcharge_no>, <mp_surcharge_directive>, <mp_rate_schedule_no custom_rate_service_no>, <custom_rate_seq_no>, <custom_rate_from_unit>, <custom_rate_to_unit>, <custom_rate_per_unit>, <billing_group_no>, <bg_notify_method>, <notify_template_group>, <statement_template>, <credit_note_template>, <primary_payment_method_no>, <backup_payment_method_no>, <stmt_contact_idx>, <stmt_contact_no>, <bg_list_start_master_file>, <payment_terms_no>, <credit_memo_template>, <rebill_template>, <collections_group_bg_no>, <collections_grp_directive payment_method_no>, <bill_contact_idx>, <bill_contact_no>, <pay_method_type>, <cc_expire_mm>, <cc_expire_yyyy>, <bank_check_digit>, <cc_id>, <revrec_profile_no>, <mp_proration_invoice_timing>, <list_start_master_file>, <locale_no>, <addr_contact_idx>, <legal_entity_no>, <plan_instance_supp_field_update_only>, <fraud_filter>, <recurring_processing_model_ind>, <usage_accumulation_reset_months_renewal_option>, <bill_lag_days>, <resp_master_plan_instance_no>, <auto_offset_months_option>

1017: invalid password

Additional Comments: The password does not meet the parameters set by the client.

<password>

1023: userid is missing or invalid

Additional Comments: You must enter a user_id if the client is not enabled to automatically generate them.

<userid>

1024: invalid date format

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

<birthdate>, <acct_start_date>, <alt_start_date>, <retroactive_start_date>, <stmt_birthdate>, <bill_birthdate>, <addr_birthdate>

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

<reset_dates_after_status>, <invoice_unbilled_usage>, <invoice_approval_required>, <usage_pooling>, <do_collect>, <remove_pi_custom_rates>, <force_currency_change>, <include_plan_instance_queue>

1034: there is no data to be modified

 

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

<master_plan_assign_directive>

1037: invalid account group directive

<functional_acct_grp_directive>, <collection_acct_grp_directive>

1046: invalid tax exemption level code

Additional Comments: Note that tax_exemption_level is only used with Aria's internal tax engine.

<tax_exemption_level>

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

Additional Comments: This message indicates a processing problem.

 

1064: Invalid surcharge directive

<surcharge_directive>

1066: Locale name does not exist in the system.

<locale_name>

1067: Locale no does not exist in the system.

<locale_no>

1101: Credit-only proration is not valid in this case because there is a mandatory child Supplemental Plan that will be assigned and result in charges on the account.

<master_plan_assign_directive>

1108: Invalid billing group, collection group directive.

 

3003: could not create invoice

Additional Comments: Could not create a preview invoice due to account status, plan status, or other processing error. Please contact Aria Customer Support.

 

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

 

3018: invalid automatic offset months option

 

3098: Negative Charge Line Items are not allowed.

 

4006: invalid pay method or alternate pay method

<primary_payment_method_no>, <backup_payment_method_no>, <payment_method_no>, <pay_method_type>

4008: invalid expiration date

Additional Comments: Dates must be in yyyy-mm-dd format. For update_payment_method_token_m, the date must be a future date.

<cc_expire_mm>, <cc_expire_yyyy>

4009: invalid cc number

<cc_num>

4010: invalid bank draft info

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_num>, <bank_routing_num>

4011: cc authorization failed

Additional Comments: $1 authorization has failed.

<cc_num>, <cc_expire_mm>, <cc_expire_yyyy>

4017: duplicate payment method client defined id.

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

<client_primary_payment_method_id>, <client_backup_payment_method_id>, <client_pay_method_id>

4019: Invalid Bank Account Type.

<bank_acct_type>

4022: invalid cc id

<cc_id>

4027: Changes for this Plan were not saved because the collection attempt associated with this change was unsuccessful.

<do_collect>

4032: cc_id is required.

Additional Comments: cc_id is required for this payment processor.

<cc_id>

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

 

5002: invalid account status code

<status_cd>

5003: invalid notify method

<notify_method>

5004: invalid responsibility level cd

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

<resp_level_cd>

5005: invalid parent account no

<senior_acct_no>

5008: invalid userid length

Additional Comments: This error is based on the client parameters MIN_USERID_LENGTH and MAX_USERID_LENGTH.

 

5009: userid contains illegal characters

Additional Comments: Only alphanumeric characters are allowed.

<userid>

5010: userid is reserved

Additional Comments: You must select another user ID.

<userid>

5011: userid is taken

Additional Comments: You must select another user ID.

<userid>

5012: password is too short

Additional Comments: This error is based on the client parameter MIN_PASSWD_LENGTH.

<password>

5013: password is too long

Additional Comments: This error is based on the client parameter MAX_PASSWD_LENGTH.

<password>

5014: password contains invalid characters

<password>

5016: password not strong

Additional Comments: The password  must be at least eight characters in length and must contain at least one alphabetic and one numeric char.

<password>

5017: invalid iso country code

<country_cd>, <stmt_country>, <bill_country>, <bank_country_cd>, <addr_country>

5018: account in uneditable status

Additional Comments: If the account is in an archived state, edit is not allowed.

 

5021: invalid test acct indicator

<test_acct_ind>

5024: number of supp field values exceeds maximum number of allowed values

Additional Comments: The number of values given for a given field must meet the maximum values criteria set at configuration.

<acct_supp_field_value>

5026: supp field value already exists

Additional Comments: The same name was provided more than once with the same value.

<acct_supp_field_name>

5030: Child account's Currency is not matching with Parent account's Currency

 

5031: Child account of this account cannot be set as its parent.

Additional  Comments: The given senior_acct_no must not be a child account.

<senior_acct_no>

5033: Invalid parent account user id.

<senior_acct_userid>

5034: Invalid parent client account id.

<senior_client_acct_id>

5036: Client Account ID is already assigned to other account

Additional Comments: This validation occurs only when the client parameter CHECK_CLIENT_ACCT_ID_ALREADY_TAKEN is enabled for the client.

 

5038: Client Account ID has exceeded maximum size

Additional Comments: Maximum allowable length is 50 characters.

<client_acct_id>

5039: Invalid RevRec profile ID.

<revrec_profile_no>

5040: Invalid RevRec client-defined ID.

<client_revrec_id>

5041: Invalid invoicing option provided

<invoicing_option>

5048: Responsible account number/identifier is mandatory when master_plan_instance's resp_level_cd is not self pay (does not equal 1). Alt: Missing senior account number/identifier. 

Additional Comments: Senior account number is mandatory when master_plan_instance.resp_level_cd is not equal to 1.

<senior_acct_no>, <resp_level_cd>

5051: The responsible Master Plan Instance number/identifier must be from an ancestor account. Alt: the responsible Master Plan Instance number/identifier is not associated with the senior account number; The responsible Master Plan Instance number/identifier must be from an ancestor account.

Additional Comments: The responsible mpi_no must be from the senior/parent account.

<resp_master_plan_instance_no>, <resp_client_master_plan_instance_id>

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

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

<plan_instance_field_name>

5053: Missing values for required Plan instance field

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

<plan_instance_field_value>

5055: The first name, middle initial and last name of account contact, billing contact and statement contact must be the same when consumer_acct_ind = 1. Alt: Updating multiple contacts with different names on a consumer account is not allowed.

Additional Comments: The first name, middle initial and last name of account contact, billing contact and statement contact must be same when consumer_acct_ind = 1.

 

5059: Invalid Product Field Value.

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

<plan_instance_field_value>

5060: Invalid Product Field Directive.

<plan_instance_field_directive>

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

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

<plan_instance_field_value>

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

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

<plan_instance_field_value>

5063: Field cannot be added because it is not a Plan instance field.

<plan_instance_field_name>

5070: Invalid Legal Entity no

<legal_entity_no>

5071: Invalid Client Legal Entity ID

<client_legal_entity_id>

5073: Once an account is set with a Legal Entity, it cannot be changed or removed.

<legal_entity_no>, <client_legal_entity_id>

5075: Only self-pay Master Plan Instances can be assigned to a Billing Group.

 

5077: This child account currently cannot be unassigned. One or more Master Plan Instances of this child account or its descendant accounts (child, grandchild, etc.) are using the Master Plan Instance from one of its ancestor accounts for payment responsibility.

 

6003: could not validate billing information

Additional Comments: There was an error during the $1 authorization attempt.

 

6004: validation not supported for this payment method

Additional Comments: Only payment methods 1 and 13 are supported.

<primary_payment_method_no>, <backup_payment_method_no>

6005: invalid supplemental field

Additional Comments: Unknown field name.

<acct_supp_field_name>

6007: CVV Declined

Additional Comments: $1 authorization has failed due to CVV.

 

6008: Address verification declined

Additional Comments: $1 authorization failed due to billing address.

 

6009: CVV timeout - retry

Additional Comments: $1 authorization failed due to CVV check timeout.

 

6010: Address verification timeout - retry

Additional Comments: $1 authorization failed due to billing address check timeout.

 

6021: Invalid state_prov entered

<state_prov>, <stmt_state_prov>, <bill_state_prov>, <addr_state_prov>

6022: invalid supp field value

Additional Comments: Value is empty or not from the configured allowed values.

<acct_supp_field_value>

6023: billing information does not exist

Additional Comments: Taxable address does not contain country or state info. The tax credit calculation during proration does this validation.

 

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

<iban>

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

<bank_swift_cd>

6031: BBAN is numeric and up to 16 digits

<bank_acct_num>

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

 

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

<bank_swift_cd>, <bank_acct_num>

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

<pay_method_type>

7028: duplicate billing group client defined id.

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

<client_mp_billing_group_id>

12001: Account group does not exist

Additional Comments: An invalid seq_function group_id was entered.

<seq_func_group_no>, <client_seq_func_group_id>

12002: Account group is collections based

 

12003: Account group is not collections based

<collection_acct_group_no>, <client_collection_acct_group_id>

12004: Account already assigned to this group

<collection_acct_group_no>, <client_collection_acct_group_id>

12010: Client account group does not exist

<collection_acct_group_no>, <client_collection_acct_group_id>

12011: A collection account group must be provided in order to add or remove it from this account

<collection_acct_grp_directive>

12012: Collection group does not exist

 

12013: Collection group identifier does not exist

 

12018: Billing group already assigned to this group

 

14001: invalid Master Plan no

<master_plan_no>

14005: invalid Plan service combination

Additional Comments: The given Plan number and service number combination for master and Supplemental Plans is not valid.

<custom_rate_service_no>, <custom_rate_client_service_id>

14006: invalid rate schedule no

<rate_schedule_no>, <alt_rate_schedule_no>, <mp_rate_schedule_no>

14008: account has Supplemental Plans that are not eligible under this Master Plan

Additional Comments: The Supplemental Plan is not linked to the Master Plan.

 

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

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

<alt_rate_schedule_no>, <client_alt_rate_schedule_id>

14013: New Plan does not have a rate schedule with a currency matching the account's currency.

Additional Comments: The given rate schedule currency does not match the account's currency.

<alt_rate_schedule_no>

14014: When entering custom rates, the end sequence number of one tier must immediately precede the start sequence number of the next tier. Alt: invalid rate tier structure

Additional Comments:

When entering custom rates, the tiers must be continuous, that is, the end sequence number of one tier must immediately precede the start sequence number of the next tier. In addition, the rate schedule must have the same number of units in each tier, and the same number of tiers, as the schedule on which it is based. From_units must be greater than - and less than to_units.

<custom_rate_seq_no>, <custom_rate_to_unit>

14015: The custom rates for services other than usage and recurring types can have only one tier with rate_seq_no set to 1, the from_unit set to 1 and to_unit left empty. Alt: custom from and to units not supported for given service_no

Additional Comments: For the custom rate sequence, the "from" unit in one tier is not immediately after the end unit in the previous tier. Tiers are not allowed for other than recurring and usage services.

<custom_rate_from_unit>, <custom_rate_to_unit>

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

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

<usage_accumulation_reset_months>

14023: Offset Interval must be greater than zero

<offset_interval>

14024: Invalid Offset Interval and Assignment Directive combination.

Additional Comments: Offset_interval only applies to the anniverary date.

<offset_interval>, <master_plan_assign_directive>

14027: The end units of final rate tier is not infinity

Additional Comments: The custom rates final unit must be infinity.

<custom_rate_to_unit>

14033: Invalid Promo Code

<promo_cd>

14035: Invalid client Plan id

<client_master_plan_instance_id>, <client_master_plan_id>, <resp_client_master_plan_instance_id>

14036: Invalid client service id

<custom_rate_client_service_id>

14039: Invalid client rate schedule id

<client_alt_rate_schedule_id>, <custom_rate_client_service_id>

14042: Promo Code Expired

<promo_cd>

14043: Invalid Plan instance rate_seq combination

Additional Comments: If the from/to units are not specified, the given rate_seq_no must be a valid rate_seq_no.

<custom_rate_from_unit>, <custom_rate_to_unit>

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

<promo_cd>

14053: Invalid Master Plan Instance number

<master_plan_instance_no>

14054: Invalid client Master Plan Instance identifier

<client_master_plan_instance_id>

14055: Missing senior Master Plan Instance number/identifier

Additional Comments: If resp_level_cd is not 1 and no responsible Plan instance number or ID was entered.

<resp_master_plan_instance_no>, <resp_client_master_plan_instance_id>

14059: The senior Master Plan Instance cannot be responsible for another Plan instance because it is set to Parent Pay

Additional Comments: The responsible Plan instance is a child pay,

<resp_master_plan_instance_no>, <resp_client_master_plan_instance_id>

14060: Plan cannot be replaced because the Plan stauts of the existing lan does not allow the Plan to be replaced

Additional Comments: The current status of the MPI does not allow its Plan to be replaced

 

14063: duplicate Plan instance client defined id.

<client_master_plan_instance_id>, <new_client_master_plan_instance_id>

14077: Account status not support Plan provisioning.

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

<status_cd>

14078: Master Plan Instance status not support Plan provisioning.

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

<status_cd>

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

<alt_rate_schedule_no>, <client_alt_rate_schedule_id>

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

<master_plan_units>

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

 

14098: Invalid proration invoice timing

<mp_proration_invoice_timing>

14133: Self-pay MPI cannot be converted to parent-pay as it is currently in dunning or completed dunning without exiting.

Additional Comments: MPIs that are in dunning or have completed dunning without exiting successfully are not displayed, because they cannot be converted from self-pay to parent-pay while in this state. The MPIs that are in dunning are NNNNN, NNNNN, NNNNN, etc.

 

14134: Please apply outstanding manually applicable payments before modifying payment responsibility..

 

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.

 

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

<force_currency_change>

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

<force_currency_change>

15001: invalid coupon code

<acct_coupon_cd>

15002: coupon expired

<acct_coupon_cd>

15006: Duplicate surcharge number in input

<surcharge_no>, <mp_surcharge_no>

15008: Invalid surcharge rate schedule no

<rate_schedule_no>

15009: Invalid surcharge number

<surcharge_no>, <mp_surcharge_no>

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.

<acct_coupon_cd>

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

<acct_coupon_cd>

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.

<mp_surcharge_no>

16021: The currency for the contract completion rollover target rate schedule must match the currency on the account.

 

18005: Invalid Template number

<alt_msg_template_no>, <cn_alt_msg_template_no>, <statement_template>, <credit_note_template>, <credit_memo_template>, <rebill_template>

18010: Invalid Credit Memo Template number

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

<credit_memo_template>

18011: Invalid Rebill Template number

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

<rebill_template>

20026: agreement id OR credit card info is required

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

<pay_method_type>, <bill_agreement_id>, <cc_num>

20031: agreement id is mandatory for this payment method

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

<pay_method_type>, <bill_agreement_id>

20287: The email address is not valid.

<email>, <stmt_email>, <bill_email>, <addr_email>, <stmt_email_list_cc>, <stmt_email_list_bcc>

23013: Invalid usage threshold applicability

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

<usage_threshold_applicability>

25020: Illegal characters entered

<client_receipt_id>, <auth_key>, <client_acct_id>, <userid>, <password>, <secret_question>, <secret_question_answer>, <pin>, <first_name>, <mi>, <last_name>, <company_name>, <address1>, <address2>, <address3>, <city>, <locality>, <state_prov>, <country_cd>, <postal_cd>, <phone>, <phone_ext>, <cell_phone>, <work_phone>, <work_phone_ext>, <fax>, <email>, <birthdate>, <senior_acct_userid>, <senior_client_acct_id>, <taxpayer_id>, <alt_client_acct_group_id>, <acct_coupon_cd acct_start_date>, <client_seq_func_group_id>, <client_alt_msg_template_id>, <client_cn_alt_msg_template_id>, <reset_dates_after_status>, <new_client_acct_id>, <alt_start_date>, <retroactive_start_date>, <client_functional_acct_group_id>, <client_collection_acct_group_id>, <acct_supp_field_name>, <acct_supp_field_value>, <client_master_plan_instance_id>, <new_client_master_plan_instance_id>, <client_master_plan_id>, <master_plan_instance_desc>, <client_dunning_group_id>, <client_mp_billing_group_id>, <client_alt_rate_schedule_id>, <promo_cd>, <mp_coupon_cd invoice_unbilled_usage>, <invoice_approval_required>, <usage_pooling>, <usage_threshold_applicability>, <plan_instance_field_name>, <plan_instance_field_value>, <custom_rate_client_service_id billing_group_name>, <billing_group_description>, <client_billing_group_id>, <client_primary_payment_method_id>, <client_backup_payment_method_id>, <stmt_first_name>, <stmt_mi>, <stmt_last_name>, <stmt_company_name>, <stmt_address1>, <stmt_address2>, <stmt_address3>, <stmt_city>, <stmt_locality>, <stmt_state_prov>, <stmt_country>, <stmt_postal_cd>, <stmt_phone>, <stmt_phone_ext>, <stmt_cell_phone>, <stmt_work_phone>, <stmt_work_phone_ext>, <stmt_fax>, <stmt_email>, <stmt_birthdate>, <payment_terms_name>, <client_payment_term_id>, <ean_gln_num>, <ean_gln_requisition_num>, <client_collections_group_bg_id>, <client_notification_template_group_id>, <bill_first_name>, <bill_middle_initial>, <bill_last_name>, <bill_company_name>, <bill_address1>, <bill_address2>, <bill_address3>, <bill_city>, <bill_locality>, <bill_state_prov>, <bill_country>, <bill_postal_cd>, <bill_phone>, <bill_phone_ext>, <bill_cell_phone>, <bill_work_phone>, <bill_work_phone_ext>, <bill_fax>, <bill_email>, <bill_birthdate>, <pay_method_name>, <client_pay_method_id>, <pay_method_description>, <cc_num>, <bank_acct_num>, <bank_routing_num>, <cvv>, <track_data1>, <track_data2>, <bill_agreement_id>, <iban>, <bank_swift_cd>, <bank_country_cd>, <mandate_id>, <bank_id_cd>, <bank_branch_cd>, <do_collect>, <change_status_after_coll>, <bank_name>, <bank_city>, <bank_acct_type>, <bank_acct_holder_type client_revrec_id>, <po_num>, <mp_po_num>, <locale_name>, <addr_first_name>, <addr_middle_initial>, <addr_last_name>, <addr_company_name>, <addr_address1>, <addr_address2>, <addr_address3>, <addr_city>, <addr_locality>, <addr_state_prov>, <addr_country>, <addr_postal_cd>, <addr_phone>, <addr_phone_ext>, <addr_cell_phone>, <addr_work_phone>, <addr_work_phone_ext>, <addr_fax>, <addr_email>, <addr_birthdate client_legal_entity_id>, <fraud_control_field_name>, <fraud_control_field_value stmt_email_list_cc>, <stmt_email_list_bcc>, <force_currency_change>, <include_plan_instance_queue>, <proc_field_name>, <proc_field_value remove_pi_custom_rates>, <resp_client_master_plan_instance_id>, <alt_proration_end_date>, <application_id>, <application_date>, <alt_caller_id>, <attach_qualifier_option>, <qualifier_name>, <qualifier_value>

25022: Unsupported backup pay method provided

<backup_payment_method_no>, <client_backup_payment_method_id>

25023: Primary payment method is required.

Additional Comments: There must be a primary pay method before setting up a secondary pay method. When the primary pay method is removed, then the secondary becomes primary.

<primary_payment_method_no>

25025: Backup pay method cannot be different than primary pay method

<backup_payment_method_no>

25026: Primary pay method cannot be different than backup pay method

<primary_payment_method_no>, <backup_payment_method_no>

25027: Provided payment method is not a credit card

Additional Comments: expiry date can be modified only for credit card.

<cc_expire_mm>, <cc_expire_yyyy>, <pay_method_type>

25042: The expiration date for tokenized credit cards cannot be edited as that information is provided by the payment processor.

<cc_expire_mm>, <cc_expire_yyyy>

25043: Primary payment method does not support secondary pay method.

Additional Comments: The primary_client_payment_method_id is not 1, 2, or 13) and the backup_client_payment_method_id is not null.

<primary_payment_method_no>, <backup_payment_method_no>

25044: Secondary payment method type must match the primary.

Additional Comments: The backup_client_payment_method_id is not 1, 2, or 13.

<backup_payment_method_no>, <client_backup_payment_method_id>, <client_primary_payment_method_id>, <primary_payment_method_no>

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.

<client_backup_payment_method_id>, <client_primary_payment_method_id>

26008: Provided payment_method_id does not exist for this account.

 

26010: Invalid billing group number

<mp_billing_group_no>, <billing_group_no>

26012: Invalid client-defined billing group ID.

<client_mp_billing_group_id>, <client_billing_group_id>

26013: Invalid dunning group number

<dunning_group_no>

26014: Invalid client-defined dunning group ID.

<client_dunning_group_id>

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

<client_primary_payment_method_id>

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

<client_backup_payment_method_id>

26024: The account status provided is not supported when your client parameter Account_EOM_Enabled is set to True.

<status_cd>

26031: Client payment terms id not found.

<client_payment_term_id>

26032: Payment terms is not available for the account.

Additional Comments: The payment_terms_no must be mapped to the acct_group_no.

<payment_terms_no>, <payment_terms_name>, <client_payment_term_id>

26034: Payment terms not found.

<payment_terms_no>, <payment_terms_name>, <client_payment_term_id>

26037: EAN GLN number and EAN GLN requisition numbers are required for EAN GLN Payment Terms.

Additional Comments: The payment_terms_no is valid and requires that ean_gln_num and ean_gln_requisition_num values are entered, but these values were not entered.

<ean_gln_num>, <ean_gln_requisition_num>

26048: The Responsible Master Plan Instance cannot be changed for this Parent-pay Master Plan Instance since it is in dunning or has completed dunning without exiting successfully as a result of an unpaid balance transfer.

 

29004: Provided contact idx is invalid.

Additional Comments: When there is no matching map index available for acct_contact_idx, contact_idx, bill_contact_idx, stmt_contact_idx, dest_contact_idx, item_dest_contact_id, this error occurs.

<acct_contact_idx>, <stmt_contact_idx>, <bill_contact_idx>, <addr_contact_idx>

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

<acct_contact_no>, <stmt_contact_no>, <bill_contact_no>
  • Was this article helpful?