create_acct_complete_m Error Messages

1001: unexpected error

1004: authentication error

Associated Inputs: auth_key, client_id, client_no

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

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

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.

1017: invalid password

Associated Inputs: password

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

1023: userid is missing or invalid

Associated Inputs: user_id

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

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.

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

Associated Inputs: 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

1046: invalid tax exemption level code

Associated Inputs: tax_exemption_level

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

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

1057: The create_acct_complete_m API is not supported because your client parameter Account_EOM_Enabled is set to False.

1058: Too many accounts. Please reduce the number of accounts to be under <limit>.

Associated Inputs: N/A

1065: account cannot be created because inputs related to account or Plan structure were not specified.

Associated Inputs: acct_no

Additional Comments: The API input is missing acct rows.

1066: Locale name does not exist in the system.

Associated Inputs: locale_name

1067: Locale no does not exist in the system.

Associated Inputs: locale_no, master_plan_instance_no

1068: Combine invoices must be either 1-Long Cycle or 2-Short Cycle or 3-Consider Client Param.

Associated Inputs: combine_invoices

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

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.

3008: pending invoice was created, but auto accept failed

3010: skus must have have units greater than zero

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

3098: Negative Charge Line Items are not allowed.

3100: Future invoice cannot be created as there is an existing contract changes or Plan unit instance fulfillment going to happen in the period.

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. For update_payment_method_token_m, the date must be a future date.

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.

4011: cc authorization failed

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

Additional Comments: $1 authorization has failed.

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

4022: invalid cc id

Associated Inputs: pay_method_type, cc_id

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.

5001: duplicate entry

Associated Inputs: acct_no, userid, reference_code

Additional Comments: The acct_no or userid of the new account is already in use or the reference_code of a payment matches an existing value.

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.

5005: invalid parent account no

Associated Inputs: senior_acct_no

5007: invalid currency cd

Associated Inputs: currency_cd, Currency code of Threshold Billing Rule does not match Account. Rule: AriaNo ($AriaNo)

5008: invalid userid length

Associated Inputs: user_id

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

5009: userid contains illegal characters

Associated Inputs: user_id

Additional Comments: Only alphanumeric characters are allowed.

5010: userid is reserved

Associated Inputs: user_id

Additional Comments: You must select another user ID.

5011: userid is taken

Associated Inputs: user_id

Additional Comments: You must select another user ID.

5012: password is too short

Associated Inputs: password

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

5013: password is too long

Associated Inputs: password

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

5014: password contains invalid characters

Associated Inputs: password

5016: password not strong

Associated Inputs: password

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

5017: invalid iso country code

Associated Inputs country, bank_country_cd, bill_country

5019: error recording balance forward

Associated Inputs: balance_forward

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

5020: alternate billing day must be between 1 and 31

Associated Inputs: alt_bill_day

5021: invalid test acct indicator

Associated Inputs: test_acct_ind

5023: number of supp field values does not meet required minimum number of values

Associated Inputs: supp_field_value

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

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

Associated Inputs: supp_field_value

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

5026: supp field value already exists

Associated Inputs: supp_field_name

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

5029: invalid item or sku

Associated Inputs: filter_item_no, filter_client_item_id, client_sku

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

Associated Inputs: currency_cd

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

Associated Inputs: senior_acct_no

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

5033: Invalid parent account user id.

Associated Inputs: senior_acct_user_id

5034: Invalid parent client account id.

Associated Inputs: senior_client_acct_id

5036: Client Account ID is already assigned to other account

Associated Inputs: client_acct_id

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

5039: Invalid RevRec profile ID.

Associated Inputs: revrec_profile_id

5040: Invalid RevRec client-defined ID.

Associated Inputs: revrec_client_defined_id

5041: Invalid invoicing option provided

Associated Inputs: 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. 

Associated Inputs: senior_acct_no, resp_level_cd

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

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.

Associated Inputs: resp_master_plan_inst_no, parent_acct_master_plan_inst_id

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

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.

5054: The Account Contact name, Billing Contact name, and Statement Contact name must be the same for consumer accounts.

Additional Comments: 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.

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.

5070: Invalid Legal Entity no

Associated Inputs: legal_entity_no

5071: Invalid Client Legal Entity ID

Associated Inputs: client_legal_entity_id

5072: Either legal_entity_no or client_legal_entity_id is required

Associated Inputs: legal_entity_no, client_legal_entity_id

Additional Comments: When the LEGAL_ENTITY_MASTER client parameter is enabled and the client has a legal entity defined, then this is mandatory.

6003: could not validate billing information

Associated Inputs: pay_method_type, cc_auth_amount

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

6004: validation not supported for this payment method

Associated Inputs: alt_pay_method, seq_no

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

6005: invalid supplemental field

Associated Inputs: supp_field_name

Additional Comments: Unknown field name.

6007: CVV Declined

Associated Inputs: backend, related to payment_method.*

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

6008: Address verification declined

Associated Inputs: backend, related to payment_method.*

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

6009: CVV timeout - retry

Associated Inputs: backend, related to payment_method.*

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

6010: Address verification timeout - retry

Associated Inputs: backend, related to payment_method.*

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

6021: Invalid state_prov entered

Associated Inputs: bill_state_prov, state_prov, stmt_state_prov, bill_state_prov

6022: invalid supp field value

Associated Inputs: supp_field_value

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

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

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

Associated Inputs: payment_method_type

7027: Master Plan Instance cannot be created without billing group

Associated Inputs: billing_group_idx/cdid

Additional Comments: Billing_group is mandatory when master_plan_instance.resp_level_cd = 1.

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.

7030: The new Master Plan Instance must be associated with a dunning group. You must enter a dunning group when associating a Master Plan Instance.

Associated Inputs: dunning_group_idx/cdid

Additional Comments: Dunning_group is mandatory when master_plan_instance.resp_level_cd = 1.

7031: Invalid dunning_process_no

Associated Inputs: dunning_process_no

7032: Single order billing not allowed because Plan instance status prevents it

Associated Inputs: plan_instance_status

Additional Comments: This error occurs in the following situations:

1. The Plan instance status code allows billability and the invoice option is "NONE".
2. If the Plan instance status does not allow billability.

7033: Invalid client defined dunning process id

Associated Inputs: client_dunning_group_id

12001: Account group does not exist

Associated Inputs: group_no, acct_group_id

Additional Comments: An invalid seq_function group_id was entered.

12005: Account belongs to collections based group using same payment method

Associated Inputs: collections_acct_group_no

Additional Comments: Two collection groups that have different processors share a payment method.

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

14001: invalid Master Plan no

Associated Inputs: plan_no

14002: invalid Supplemental Plan no

Associated Inputs: plan_no

14005: invalid Plan service combination

Associated Inputs: custom_rate_service_no, custom_rate_service_id

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

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

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.

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

Associated Inputs: alt_rate_schedule_no, acct_currency

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

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

Associate Inputs: custom_rate_to_unit, custom_rate_seq_no

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.

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

Associated Inputs: custom_rate_from_unit, custom_rate_to_unit

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.

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.

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

Associated Inputs: custom_rate_to_unit

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

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

14038: Invalid client Master Plan id

Associated Inputs: client_resp_master_plan_inst_id

14039: Invalid client rate schedule id

Associated Inputs: client_alt_rate_schedule_id, rollover_client_rate_sched_id

14040: No Universal Place Holder rate schedule for this currency

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

14043: Invalid Plan instance rate_seq combination

Associated Inputs: custom_rate_from_unit, custom_rate_to_unit

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

14051: Invalid Plan status for the new Plan

Associated Inputs: plan_instance_status, status_cd

14055: Missing senior Master Plan Instance number/identifier

Associated Inputs: resp_master_plan_inst_no and client_resp_master_plan_inst_id, resp_lvl_cd, parent_acct_master_plan_inst_id

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

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

Associated Inputs: resp_master_plan_inst_no and client_resp_master_plan_inst_id, parent_acct_master_plan_instance_no

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

14063: duplicate Plan instance client defined id.

Associated Inputs:client_plan_instance_id, new_client_plan_inst_id

14071: Master Plan Instance information is missing

Associated Inputs: plan_instance_no, client_plan_instance_id, master_plan_instance_no, client_master_plan_instance_id

Additional Comments: Both plan_no and plan_id must be entered. Master Plan Instance is required if the invoice_no is not provided.

14073: Invalid responsibility Master Plan Instance index

Associated Inputs: resp_master_plan_inst_idx

Additional Comments: The idx must be present in the master_plans array input.

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

14085: Mandatory child Plans are not included in the input. Please correct this and try again.

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.

14107: Invalid Service Number.

Associated Input: custom_rate_service_no

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.

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.

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

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.

15002: coupon expired

Associated Inputs: coupon_codes, coupon_cd

15006: Duplicate surcharge number in input

Associated Inputs: acct_surcharges, mpi_surcharges, mp_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

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

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

15017: Invalid client surcharge id

Associated Inputs: surcharge_updates > client_surcharge_id

15018: Duplicate client surcharge id in input.

Associated Inputs: surcharge_updates > client_surcharge_id

16011: This account is ineligible for new contract creation because it has a universal contract in effect.

Associated Inputs: acct_no, client_acct_id

16013: Unsupported contract type

Associated Inputs: contract_type_no, type_no

16018: Universal contract cannot be created because all Plan statuses on this account are Suspended, Pending Cancellation, Cancelled or Terminated.

16019: Multi Plan instance contract cannot be created because the given Plan instance statuses on this account are Suspended, Pending Cancellation, Cancelled or Terminated.

Associated Inputs: plan_instance_no, client_plan_instance_id

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

Associated Inputs: rollover_rate_sched_no/rollover_client_rate_sched_id

16029: The contract start date must be on or after the effective date of the account (account creation date, account start date or retroactive start date) covered by the contract.

Associated Inputs: contract_start_date, start_date

16030: The contract start date must be on or after the earliest effective date (plan assignment date or retroactive start date) of the Plans covered by the contract.

Associated Inputs: contract_start_date, start_date

16033: The contract end date cannot be earlier than today (whether provided as input or calculated based on the contract term and start date).

16035: The renewal_end_date should not be on or before the initial contract period’s end date.

16036: When creating an auto renewal with a different duration (type 9), then please supply either the new renewal_end_date,  or both the new  renewal_duration_length and renewal_duration_type.

18005: Invalid Template number

Associated Inputs: alt_msg_template_no, cn_alt_msg_template_no, alt_inv_template_no, alt_stmt_template_no

18006: Invalid client template id

Associated Inputs: client_cn_alt_msg_template_id, client_alt_msg_template_id, client_alt_inv_template_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.

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.

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

25003: Provided inventory item is not bundled with the Plan definition

Associated Inputs: client_sku

Additional Comments: You have entered an invalid inventory item.

25005: Inventory item units must be equal to or greater than the minimum quantity defined in the Product Catalog

Associated Inputs: item_units, plan_no, client_plan_id

25006: Total inventory item units must equal the number of Plan units assigned

Associated Inputs: item_units, plan_no, client_plan_id

25007: Inventory item  units must be equal to or less than the maximum quantity specified in the Product Catalog

Associated Inputs: item_units, plan_no, client_plan_id

Additional Comments: The NSO type is individual and the item_units is less than the maximum quantity specified in the product catalog.

25010: One or more provided inventory items are Inactive.

Associated Inputs: client_sku

25020: Illegal characters entered

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

25023: Primary payment method is required.

Associated Inputs: pay_method_type, pay_method_name, client_pay_method_cdid,bill_agreement_id

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.

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

Associated Inputs: new pay_method_type, primary_payment_method_no, backup_payment_method_no, client_primary_payment_method_id, client_backup_payment_method_id

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

Associated Inputs: new pay_method_type, primary_payment_method_no, backup_payment_method_no, client_primary_payment_method_id, client_backup_payment_method_id

25030: When override_bill_thru_date is specified, alt_bill_day cannot be used.

Additional Comments: override_bill_thru_date, alt_bill_day

25031: When override_bill_thru_date is specified, status_until_alt_start cannot be used (defaults to Inactive).

Associated Inputs: override_bill_thru_date, status_until_alt_start

Additional Comments: If override_bill_thru_date is given, then the status_until_alt_start must be NULL.

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.

25033: When override_bill_thru_date is specified, invoicing_option must be configured to be Perform Prorated Invoicing.

Associated Inputs: override_bill_thru_date, invoicing_option

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

Associated Inputs: new pay_method_type, primary_payment_method_no, backup_payment_method_no, client_primary_payment_method_id, client_backup_payment_method_id, pay_method_type

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

25044: Secondary payment method type must match the primary.

Associated Inputs: new pay_method_type, primary_payment_method_no, backup_payment_method_no, client_primary_payment_method_id, client_backup_payment_method_id

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

26012: Invalid client-defined billing group ID.

Associated Inputs: client_billing_group_id

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

26021: Invalid billing group idx

Associated Inputs: billing_group_idx

26022: Invalid dunning group idx

Associated Inputs: dunning_group_idx

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

Associated Inputs: status_cd

26025: Invalid billing group idx or client-defined billing group id. Each Master Plan being assigned must be associated with a billing group.

Associated Inputs: billing_group_idx, client_billing_group_id

26026: Invalid dunning group idx or client-defined dunning group id. Each Master Plan being assigned must be associated with a dunning group.

Associated Inputs: dunning_group_idx, client_dunning_group_id

26028: Duplicate Plan instance index in input

Associated Inputs: plan_instance_idx

Additional Comments: The same plan_instance_idx was submitted twice.

26031: Client payment terms id not found.

Associated Inputs: client_payment_term_id

26032: Payment terms is not available for the account.

Associated Inputs: payment_terms_no, payment_terms_name, client_payment_term_id

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

26034: Payment terms not found.

Associated Inputs: payment_terms_no, payment_terms_name, client_payment_term_id

26035: Invalid Payment option.

Associated Inputs: payment_option

Additional Comments: The payment_option is not "TERMS" or "METHODS".

26036: Payment Terms Required.

Associated Inputs: payment_option, payment_terms_no, client_payment_term_id

Additional Comments: The payment_option is "TERMS" and the payment_terms_no or client_payment_term_id was not entered.

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

Associated Inputs: payment_terms_no, payment_terms_name, client_payment_term_id, ean_gln_num, ean_gln_requisition_num

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.

27004: invalid Plan unit instance id

Associated Inputs: client_plan_unit_inst_id, new client_plan_unit_inst_id

27005: The service provided is not a fulfillment based service.

Associated Inputs: service_no

Additional Comments: The entered service_no must be a  a fulfillment based service.

27007: The fulfillment date should not be provided before account creation date

Associated Inputs: fulfillment_directive, service_fulfillment_date, acct.created

Additional Comments: The fulfillment_directive is immediate and service_fulfillment_date is before the acct.created date.

27015: Plan Unit Instances is not supported because your client parameter Enable Plan Unit Instances is set to False. Please contact Aria Customer Support with questions about the Enable Plan Unit Instances client parameter.

Associated Inputs: plan_unit_instances_row

Additional Comments: The plan_unit_instances_row is not null and the client parameter "ENABLE_PLAN_UNIT_INSTANCES" is false.

27016: Since this account does not have a retroactive start date, the service fulfillment date must be the same as the current date when fulfillment_directive = 1.

Associated Inputs: fulfillment_directive, service_fulfillment_date

Additional Comments: The fulfillment_directive is immediate (1) and the service_fulfillment_date is not the current date.

27017: Eligible service no/service id is required when Eligible fulfillment date/fulfillment directive is specified.

Associated Inputs: service_fulfillment_date, fulfillment_directive, client_service_id, service_no

Additional Comments: Service_fulfillment_date and fulfillment_directive were entered and the client_service_id or service_no was not entered.

27018: Whenever fulfillment_directive = 1 is used, all service fulfillment dates provided for the fulfillment-based services associated with a given Plan instance must be the same date.

Associated Inputs: service_fulfillment_date

Additional Comments: The service_fulfillment_date must be the same for all unit instances.

27019: Invalid fulfillment directive as the account start date is in future.

Associated Inputs: fulfillment_directive (1), alt_start_date

Additional Comments: The fulfillment_directive is immediate (1) and alt_start_date is in the future.

27022: Since this account has a retroactive start date, the service fulfillment date must be on or after the account's retroactive start date and on or before the current date when fulfillment_directive = 1.

Associated Inputs: fulfillment_directive, service_fulfillment_date, retroactive_start_date

Additional Comments: The fulfillment_directive is immediate (1) and service_fulfillment_date falls before the retroactive_start_date.

29001: The service location provided is not valid.

Associated Inputs: svc_location_no, item_svc_location_no

Additional Comments: The given service location is not available for the client.

29002: The client service location id provided is not valid.

Associated Inputs: client_svc_location_id, client_item_svc_location_id

Additional Comments: The given service location ID is not available for the client.

29003: The service location provided has been disabled or deleted and cannot be associated with a Plan instance.

Associated Inputs: svc_location_no, item_svc_location_no

Additional Comments: The given service location must be active.

29004: Provided contact idx is invalid.

Associated Inputs: contact_idx, bill_contact_idx, stmt_contact_idx, dest_contact_idx, item_dest_contact_idx

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.