Skip to main content
Aria Knowledge Central

Aria API Error Messages Unabridged List

-1

-1: not attempted

0

0: OK

225

225: Invalid field data

Additional Comments: Returned when field data sent to a payment processor is missing or invalid. Examples: the value for fraud_merchant_id is missing or the order_shipping_method is invalid.

227

227: Missing companion data for fraud scoring

1001

1001: unexpected error

1002

1002: no data found

1003

1003: host not permitted

1004

1004: authentication error

Associated Inputs: auth_key, client_id, client_no

1005

1005: Client not configured for API access. Contact your customer service representative for assistance.

1007

1007: destination account does not exist

1008

1008: no line items provided

Associated Inputs: invoice_no

Additional Comments: There are no payments on the invoice.

1009

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

1010

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

1011

1011: invalid session

Associated Inputs: session_id

Additional Comments: The session does not exist, has expired, or is invalidated.

1012

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

1013

1013: Object does not exist, Threshold Rule not found: AriaNo ($AriaNo) or Billing Group not found: AriaNo ($AriaNo)

Associated Inputs: billing_group_no, client_billing_group_id, threshold_billing_rule_no, client_threshold_billing_rule_id

Alternate Message Output

1013: role_no is invalid
1013: username is invalid
1013: user does not exist
1013: client_role_id is invalid

Associated APIs: create_user_m, get_user_details_m, delete_user_m, update_user_m

Associated Inputs: role_no, username, client_role_id

1014

1014: action not allowed

Alternate Message Output

1014: Maximum user limit reached
1014: This user cannot be deleted
1014: Archived users cannot be updated
1014: Status cannot be updated to Pending Activation

Associated APIs: create_user_m, delete_user_m, update_user_m

Associated Inputs: role_no, username, status

1015

1015: duplicate record found, New assignment conflicts with existing assignment

Alternate Message Output

1015: username should be unique

Associated APIs: create_user_m

Associated Inputs: username

1016

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

1017

1017: invalid password

Associated Inputs: password

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

1018

1018: invalid rate

1019

1019: file not found

1020

1020: Service not available.

1021

1021: service timeout

1022

1022: Account billing group not found, Billing group does not belong to account. Billing group: AriaNo ($AriaNo), Account: AriaNo ($AriaNo)

Associated Inputs: billing_group_no, client_billing_group_id

1023

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

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.

1025

1025: amount not positive

Associated Inputs: amount, percent_amount

Additional Comments: This error occurs when the percent amount is greater than 100.

1026

1026: Invoice: success - Collection: success - Email: failed

1027

1027: Invoice: success - Collection: failed - Email: success

1028

1028: Invoice: success - Collection: failed - Email: failed

1029

1029: Invoice: success - Email: failed

1030

1030: invalid method call

1031

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

Associated Inputs: alt_bill_day, alt_start_date

1032

1032: cannot prorate beyond one month

1033

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

1034

1034: there is no data to be modified

1035

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

Associated Inputs: master_plan_assign_directive, assignment_directive

1036

1036: invalid Supplemental Plan directive

1037

1037: invalid account group directive

Associated Inputs: collection_acct_grp_directive, functional_acct_grp_directive

1038

1038: when modifying from-to-units, all rate sequences must be included

1039

1039:  invalid action directive

Associated Inputs: action_directive

1040

1040: A maximum range of -27 to +27 days is permissible to be entered in the Adjust Days field.

Associated Inputs: adjustment_days, adjustment_date

1041

1041: Account must be a top-level parent account.

1042

1042: no response

1043

1043: external service not available

1044

1044: no response from external service

1045

1045: method not available

1046

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.

1047

1047: invalid email template class

1048

1048: Supplemental Plan change rolled back due to collection failure

1049

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.

1050

1050: Operation not allowed

1051

1051: cannot advance virtual time - batch jobs are still running

1052

1052: only 1, 2, 3, null, and tilde are valid input values for behavioral option.

Associated Inputs: behavioral_option

1053

1053: invalid notification template group id

Associated Inputs:billing_group.notify_template_group

1054

1054: Export ID does not exist

1055

1055: acct not accessible

1056

1056: Missing USS client configuration

1057

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

1058

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

Associated Inputs: N/A

1059

1059: Invalid input: invoice_mode should be either 0 or 1

Associated Inputs: invoice_mode

1060

1060: This API is not supported because the required client parameter is not enabled. Please contact Aria Customer Support with questions about this API and its related client parameter.

1061

1061: Missing required parameter Adjustment Days

Associated Inputs: adjustment_days

Additional Comments:  This is required when the action_directive equals 1 or 2.

1062

1062: Missing required parameter: Adjustment Date

Associated Inputs: adjustment_date

1063

1063: Invalid Plan directive

1064

1064: Invalid surcharge directive

Associated Inputs: surcharge_directive

1065

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

1066: Locale name does not exist in the system.

Associated Inputs: locale_name

1067

1067: Locale no does not exist in the system.

Associated Inputs: locale_no, master_plan_instance_no

1068

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

Associated Inputs: combine_invoices

1069

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.

1099

1099: invalid or previously used receipt ID

1100

1100: usage type not known

1101

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.

Associated Inputs: master_plan_assign_directive

1102

1102: A maximum range of -99 to +27 days is permissible to be entered in the Adjust Days field

Associated Inputs: adjustment_days, adjustment_date

1103

1103: Invalid adjustment days

Associated Inputs: adjustment_days

Additional Comments:  The number of days cannot be fractional.

1104

1104: Your client is not configured to use this API call. Please contact Aria for more information.

1105

1105: This API must be enabled in your organization. Please contact Aria support for additional information.

1106

1106: Active session already exists with the given client session id.

1107

1107: Account already anonymized.

1108

1108: Invalid billing group, collection group directive.

1500

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

2001

2001: transaction does not exist

Associated Inputs: invoice_no

2002

2002: transaction is a voiding transaction

2003

2003: transaction already voided

2004

2004: transaction already reinstated

2005

2005: Combine invoices can not be voided. Please contact customer support.

Associated Inputs: invoice_no

2006

2006: amount exceeds original transaction

2007

2007: amount plus previous reversal exceeds original transaction

2010

2010: The payment ID is not valid or is not associated with account number.

Associated Input: payment_transaction_id

2011

2011: The payment ID is no longer eligible for refund processing (remaining refundable amount now equal to zero).

Associated Input: payment_transaction_id

2012

2012: Could not retrieve invoice number or line number.

2013

2013: The refund amount submitted must be a valid number no less than the reversal amount but no greater than the remaining refundable payment amount.

2014

2014: The total amount of invoice line items selected for refund-related reversal amount exceeds the total designated refund amount.

Associated Inputs: invoice_no, invoice_line_no, invoice_line_reversing_amount

2015

2015: The refund amount submitted must be a valid number greater than zero but no greater than the remaining refundable payment amount.

Associated Input: total_refund_amount

2016

2016: Could not find the corresponding charge line for the reversal line item number.

Associated Inputs: invoice_no, invoice_line_no

2017

2017: Invalid refund-related reversal amount input. Please provide entries that are greater than zero and no greater than the remaining reversible amount of the invoice line item.

Associated Inputs: invoice_no, invoice_line_no

2018

2018: Refunds of non-electronically-collected payments may only be recorded if a numeric refund check number is supplied.

Associated Input: refund_check_number

2019

2019: Could not create reversal transaction.

2020

2020: The given payment is not eligible  for refund on this day.

2021

2021: Refund Check Number is longer than allowed

Associated Input: refund_check_number

Additional Comments: Maximum length is 38 characters.

2022

2022: Invalid input for refund with opening line item. Provide entries greater than zero and no greater than eligible refundable amount for the invoice line item.

2023

2023: Invoice related detail entries mismatch for refund with opening line item. One or more entries are not paid by the selected payment.

2024

2024: A tax charge cannot be refunded as a standalone. Enter a charge line item to refund with opening line item.

2025

2025: The amount entered on invoice line item for refund with opening line item exceeds the eligible refundable amount for the line item.

2026

2026: The total amount entered for refund with opening line item exceeds the total eligible refundable amount for the selected payment.

2027

2027: The total refund amount entered should match with the sum amount entered on open paid line items array for refund with opening line item.

3001

3001: Unknown or inactive SKU

3002

3002: unable to bill order

Additional Comments: An unknown error occurred when billing the order. Contact Aria Customer Support for assistance.

3003

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.

3004

3004: Invoice does not exist

Associated Input: invoice_no

3005

3005: invoice/statement message construction not permitted for this account

3006

3006: no invoice/statement message template found

3007

3007: email address required but not found

3008

3008: pending invoice was created, but auto accept failed

3009

3009: orders must reference at least one sku

3010

3010: skus must have have units greater than zero

3011

3011: pending invoice approval failed

3012

3012: pending invoice discard failed

3013

3013: pending invoice regen failed - old invoice could not be discarded

3014

3014: pending invoice regen failed - old invoice was discarded but new invoice could not be created

3015

3015: invalid pending invoice number

Associated Input: invoice_no

3016

3016: could not cancel order - order already cancelled or succesffuly billed

3017

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

3018

3018: invalid automatic offset months option

3019

3019: too many unstatementized invoice

3020

3020: Reversing date is not applicable for non-recurring service lines

Associated Input: Invoice_line_reversing_date

3021

3021: refund amount cannot be null when do_write is set to true and auto_calc_refund is set to false or auto_calc_refund cannot be set to false when do_write is set to true and refund amount is not provided

Associated Inputs: total_refund_amount, do_write, auto_calc_refund

3022

3022: Invalid refund reason code

Associated Input: reason_code

3023

3023: Amount is not in valid format

3024

3024: Invalid reason code

Associated Input: reason_code

3025

3025: Given amount should not be greater than balance amount

3026

3026: Invalid settlement action

3027

3027: Invalid dispute no

3028

3028: Writeoff or dispute does not exist

3029

3029: This order cannot be fulfilled due to its current account and/or Plan status

3030

3030: Either alt proration end date is before today's date, alt proration start date, or retroactive start date, or alt proration end date is outside the Plan instance's billing interval.

3031

3031: Check number already exists on this refund

3032

3032: Invalid Order Number

3033

3033: could not update order - order already successfully billed

3034

3034: Invalid Bill immediate option

3035

3035: could not update order - order is not in pending status

3036

3036: Invoice_line_item does not have qualifying invoice_no or transaction_no

Associated Input: invoice_line_item

Additional Comments: Invoice_no is required if invoice_line_item is specified

3037

3037: Unit discount amount cannot be greater than Inventory items unit amount

3038

3038: Invoice has already been paid

3039

3039: Duplicate Invoice found

3040

3040: Order Statement Message exceeded 1000 characters

Associated Input: statement_message

3041

3041: Invalid date format for fulfilled_date.

Associated Input: fulfilled_date

3042

3042: Order should be in placed or billed status in order to update the fulfilled date.

3043

3043: Order fulfilled date is in the past.

Associated Input: fulfilled_date

3044

3044: Client notes exceeds length limit of 1000 characters.

Associated Input: client_notes

3045

3045: Custom status value does not exist.

Associated Input: custom_status_label

3046

3046: Invalid invoice posting status code.

3047

3047: Invoice posting status cannot be changed as invoice was already manually posted or auto posted by system.

3048

3048: Invalid invoice posting method.

3049

3049: Offset months is not supported. For anniversary assignment directive, use offset interval.

3050

3050: Advance invoice generation failed.  Advance invoices must be generated within acceptable days until next billing cycle.

3051

3051: Advance invoice generation failed.  Alt Bill Day cannot be used with invoice_mode = 1.

Associated Input: alt_bill_day, invoice_mode

3052

3052: Advance invoice generation failed.  An initial invoice has not been generated for this account and is a prerequisite step.

3053

3053: Individual invoice transactions cannot be voided independent of the invoice. Use void_invoice_m API to void the entire invoice.

3054

3054: Refund related reversals cannot be voided independent of the refund transaction. Voiding the corresponding refund transaction will automatically void the reversal transaction.

3055

3055: The requested authorization you are trying to reverse is more than 72 hours old and is no longer valid for reversal.

Associated Input: auth_no

3056

3056: The authorization record you are attempting to reverse is not valid or does not exist.

Associated Input: auth_no

3057

3057: The authorization record you are attempting to reverse has already been submitted to your processor.

Associated Input: auth_no

3058

3058: Write off of child invoice cannot be processed.  Partial write off of the invoice is not currently supported.

3059

3059: Dispute transaction is not supported for child invoices.

3060

3060: Unable to apply credit memo to a pending invoice

3061

3061: Unable to apply credit memo to a child invoice when parent pay responsibility is used.

3062

3062: Unable to apply credit memo to a voided invoice

3063

3063: Unable to apply credit memo to an invoice that is in dispute hold

3064

3064: Unable to apply credit memo to an invoice that has been written off

3065

3065: Unable to apply credit memo to an invoice that has refund-related reversals applied

3066

3066: Invoice has been fully credited.  No balance available.

3067

3067: Unable to credit memo discount or service credits independently of the related service(s)

3068

3068: Unable to credit memo tax lines independently of the taxed service(s)

3069

3069: Invalid amount

3070

3070: Invalid amount. Maximum credit amount exceeded

3071

3071: One of the credit memo lines does not exist on the invoice

3072

3072: Unable to void credit memo.  The selected credit memo was created for rebilling purposes

3073

3073: Invalid invoice. The original invoice has been rebilled

3074

3074: Invalid invoice. The original invoice has been voided

3075

3075: Invalid invoice. The original invoice has been written off

3076

3076: Invalid invoice. The original invoice is in the current bill cycle

3078

3078: Invalid invoice. The original invoice has been subject to one or more reversal transactions

3079

3079: Invalid invoice. One or more Master Plan Instances on the original invoice have moved to another billing group

3080

3080: Invalid line. Line_no must refer to line details from the original invoice

3081

3081: Invalid line. Line_no must refer to an invoice charge line

3082

3082: Invalid line. Line_no must refer to a non-tax charge line

3083

3083: Invalid service. Service_no or client_service_no cannot be modified for a usage-based service

3084

3084: Invalid service. Service_no or client_service_no cannot be modified for an order based service

3085

3085: Cannot modify service to one belonging to a different service type

3086

3086: Invalid tax inputs. Tax address fields not populated on the original invoice must not be populated during rebill

3087

3087: Invalid tax inputs. All tax address fields populated on the original invoice must be populated during rebill

3088

3088: Invalid address

3089

3089: Unable to create rebill line. Rb_units is required for recurring, order_based, and usage_based services

3090

3090: Unable to create rebill line. Rb_units must be a whole number(exception: usage based services)

3091

3091: Unable to create rebill line. Rb_units cannot be zero (exception: usage based services)

3092

3092: Invalid amount.  Only zero and positive invoice line amounts are supported

3093

3093: Credit memo does not exist

3094

3094: An invoice line cannot be entered more than once in the input.

3095

3095: The invoice cannot be voided because one or more credit memos have been applied to it.

Associated Input: invoice_no

3096

3096: The invoice cannot be voided because it has been rebilled.

Associated Input: invoice_no

3097

3097: The rb option is set to an invalid value.

Associated Input:  rb_option

3098

3098: Negative Charge Line Items are not allowed.

3099

3099: Prorated invoice cannot be created as there is an existing future invoice for this Plan instance

3100

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

3101

3101: Allowed credit-ref-type are 0 or null for Invoice based CM and 1 or 2 or 3 for on-account CM.

Associated Inputs: credit_ref_type

3102

3102: Account is a parent account with child accounts with parent pay Plans. Pending invoices for these child accounts must be approved before approving the invoices for the parent account.

Additional Comments: This is currently not used in API. This is only used in Pending Invoice approval in UI.

3103

3103: The value entered for Credit Memo Type is invalid. Please use a zero or null for invoice-based credit memos or values of 1,2 or 3 for on-account credit memos.

3104

3104: No eligible or matching orders found to cancel

Associated Inputs: account_order[]

3105

3105: Invalid Client Order Identifier

Associated Inputs: account_order > client_order_id

3106

3106: Individual credit memo transactions cannot be voided independent of the credit memo. Use void_credit_memo_m API to void the entire credit memo.

3107

3107: On-account credit memos are created with one Master Plan Instance each. Please re-submit with a single Master Plan Instance.

Associated Inputs: cm_line_items > [master_plan_instance_no, client_master_plan_instance_id]

3108

3108: The invoice for this account cannot be generated at this time, since there is another invoice in progress for the same billing group.

3109

3109: Invalid Client SKU.

Associated Inputs: client_item_id, inventory_items

3113

3113: Invalid amount entered. Please enter an amount for the maximum allowed currency specific decimal places for the issue_refund_to_acct_m API.

Associated Inputs: total_refund_amount, invoice_line_reversing_amount, open_amount

3114

3114: A Refund Reversal, using a Rebill Action, is not supported for refunding NETS payments.

3115

3115: A Refund Reversal, using a Rebill Action, is not supported for reversing child account invoices.

3116

3116: Write-off of an unsettled dispute hold cannot be voided

3130

3130: alt_pay_method and refund_payment_method entries are in conflict. Re-enter correct value

3131

3131: A refund can only be issued for a reversal or for open paid line items, but not both on the same refund.

4001

4001: collection failed

4002

4002: could not create order

4003

4003: account balance is zero

4004

4004: source account balance is 0

4005

4005: is_electronic_pay_method

4006

4006: invalid pay method or alternate pay method

Associated Inputs: alt_pay_method, pay_method_type, pay_method_type

4007

4007: need_billing_contact

4008

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.

4009

4009: invalid cc number

Associated Inputs: cc_number, alt_pay_method, cc_num, pay_method_type

4010

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

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.

4012

4012: collection was successful, but account is not currently in an active status

4013

4013: collection was successful, but account status update failed

4014

4014: collection and status change were successful, but account dates reset failed

4016

4016: The payment processor does not accept refunds beyond the standard refund window

4017

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

4019: Invalid Bank Account Type.

Associated Inputs: alt_pay_method, bank_acct_type

4020

4020: Balance is less than zero

4021

4021: Payment method or alternate payment method is required.

4022

4022: invalid cc id

Associated Inputs: pay_method_type, cc_id

4023

4023: The payment method provided is currently associated with a billing group and cannot be disabled. Either remove the payment method from the billing group before disabling it, or call the remove_acct_payment_method_m API to remove that payment method from the account.

Associated Inputs: disabled_ind, payment_method_no, client_payment_method_id

4024

4024: Invalid auto collection on Plan change input

Associated Inputs: auto_collect_on_plan_chng

4025

4025: Invalid rollback_plan_chng_collect_fail input

Associated Inputs: rollback_plan_chng_collect_fail

4026

4026: Invalid auto_send_stmt_on_plan_chng input

Associated Inputs: auto_send_stmt_on_plan_chng

4027

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

Associated Inputs: do_collect

4028

4028: Invalid processor ID

4029

4029: Invalid processor and pay method combination

4030

4030: Duplicate Payment Reference Code

4031

4031: The payment processor does not support refund on this card.

Associated Inputs: alt_pay_method

Additional Comments: Refunds are not supported on all credit cards by all payment processors.

4032

4032: cc_id is required.

Associated Inputs: cc_id, pay_method_type

Additional Comments: cc_id is required for this payment processor.

4033

4033: Current form of payment is non-electronic. No collections were attempted.

4034

4034: Collection Amount less than Currency Threshold. No collections were attempted.

4035

4035: Collection Amount is zero. No collections were attempted.

4036

4036: An account number was entered multiple times. A collection attempt should only be requested once for each account or collections will be made multiple times.

4037

4037: Two identical collection attempts were entered as part of this request. A unique collection attempt should only be requested once or collections will be made multiple times.

4038

4038: Exceeds maximum records allowed in a bulk settle API call

4039

4039: Collection not attempted since a negative balance exists on the account

4040

4040: Could not find a processor for this payment method

4041

4041: No action taken since a balance inquiry was not requested for a gift card

4042

4042: Invalid attempt 3d secure input.

4043

4043: Invalid payment auth received input.

4044

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

5001

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.

5002

5002: invalid account status code

Associated Inputs: status_cd

5003

5003: invalid notify method

Associated Inputs: notify_method_no

5004

5004: invalid responsibility level cd

Associated Inputs: resp_level_cd

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

5005

5005: invalid parent account no

Associated Inputs: senior_acct_no

5006

5006: parent acct cannot assign child acct

5007

5007: invalid currency cd

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

5008

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

5009: userid contains illegal characters

Associated Inputs: user_id

Additional Comments: Only alphanumeric characters are allowed.

5010

5010: userid is reserved

Associated Inputs: user_id

Additional Comments: You must select another user ID.

5011

5011: userid is taken

Associated Inputs: user_id

Additional Comments: You must select another user ID.

5012

5012: password is too short

Associated Inputs: password

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

5013

5013: password is too long

Associated Inputs: password

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

5014

5014: password contains invalid characters

Associated Inputs: password

5015

5015: two passwords did not match

5016

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

5017: invalid iso country code

Associated Inputs country, bank_country_cd, bill_country

5018

5018: account in uneditable status

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

5019

5019: error recording balance forward

Associated Inputs: balance_forward

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

5020

5020: alternate billing day must be between 1 and 31

Associated Inputs: alt_bill_day

5021

5021: invalid test acct indicator

Associated Inputs: test_acct_ind

5022

5022: account does not have a pending invoice

Associated Inputs: invoice_no, master_plan_instance_no, client_master_plan_instance_id

Additional Comments: An invoice_no was not passed, and the Master Plan Instance did not have a pending invoice.

5023

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

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.

5025

5025: supp field is required and cannot be removed

5026

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

5029: invalid item or sku

Associated Inputs: filter_item_no, filter_client_item_id, client_sku

5030

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

Associated Inputs: currency_cd

5031

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

5033: Invalid parent account user id.

Associated Inputs: senior_acct_user_id

5034

5034: Invalid parent client account id.

Associated Inputs: senior_client_acct_id

5035

5035: Account not in dunning. Degrade date not updated

Associated Input: filter_client_item_id

5036

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.

5037

5037: If no Account Status Degrade Date, Status Code is Required

5038

5038: Client Account ID has exceeded maximum size

Associated Inputs: client_acct_id

Additional Comments: Maximum allowable length is 50 characters.

5039

5039: Invalid RevRec profile ID.

Associated Inputs: revrec_profile_id

5040

5040: Invalid RevRec client-defined ID.

Associated Inputs: revrec_client_defined_id

5041

5041: Invalid invoicing option provided

Associated Inputs: invoicing_option

5042

5042: Because the parent account is responsible for payment, the parent Master Plan Instance id is required.

5043

5043: The Plan was not assigned to the account, because the currency on the rate schedule does not match the currency specified for that account currency

5044

5044: The submitted list contains invalid email addresses.  Please correct any mistakes.

5045

5045: Status Code is mandatory

Associated Input: status_cd

5046

5046: This account could not be created because the currencies on the Master Plan(s) being assigned do not match.

5048

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.

5049

5049: The senior account is not an ancestor of the child account

5050

5050: The statement email address list exceeds the maximum size of 3000 characters

5051

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

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

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.

5054

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.

5055

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.

5056

5056: Invalid Plan unit instance directive

Associated Input: plan_unit_inst_directive

5057

5057: Invalid source account number / identifier.

5058

5058: Invalid target account number / identifier.

5059

5059: Invalid Product Field Value.

Associated Inputs: field_value

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

5060

5060: Invalid Product Field Directive.

Associated Inputs: plan_instance_field_directive

5061

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

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.

5063

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

Associated Inputs:  plan_instance_field_name

5064

5064: product field is required and cannot be removed

Associated Input:  field_name

5066

5066: The API does not support retrieving more than client defined limit.

5067

5067: limit must be between 1 and 999.

Associated Input: limit, record_limit, contract_limit

5068

5068: offset must be greater than or equal to zero.

Associated Input: offset, contract_offset

5069

5069: Include Plan service in order to retrieve Plan service supplemental fields.

5070

5070: Invalid Legal Entity no

Associated Inputs: legal_entity_no

5071

5071: Invalid Client Legal Entity ID

Associated Inputs: client_legal_entity_id

5072

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.

5073

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

Associated Inputs: legal_entity_no or client_legal_entity_id

5074

5074: Plan instance product field name(s) to be updated is missing

5075

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

5076

5076: Only child accounts can have parent-pay MPIs.

5077

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.

6001

6001: account creation failed

6002

6002: account already exists

6003

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

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

6005: invalid supplemental field

Associated Inputs: supp_field_name

Additional Comments: Unknown field name.

6006

6006: value not allowed

6007

6007: CVV Declined

Associated Inputs: backend, related to payment_method.*

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

6008

6008: Address verification declined

Associated Inputs: backend, related to payment_method.*

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

6009

6009: CVV timeout - retry

Associated Inputs: backend, related to payment_method.*

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

6010

6010: Address verification timeout - retry

Associated Inputs: backend, related to payment_method.*

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

6011

6011: AVS data is invalid

6012

6012: CVV invalid

6013

6013: CVV not matched

6014

6014: CVV should be present

6015

6015: Cardholder name, billing address and postal code are all incorrect

6016

6016: No address

6017

6017: Street address and postal code not verified

6018

6018: System unavailable or timed out

6019

6019: Zip/Postal: No Match; Plus-4: Match; Locale: No Match

6020

6020: Zip/Postal: No Match; Plus-4: No Match; Locale: No Match

6021

6021: Invalid state_prov entered

Associated Inputs: bill_state_prov, state_prov, stmt_state_prov, bill_state_prov

6022

6022: invalid supp field value

Associated Inputs: supp_field_value

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

6023

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.

6024

6024: missing minimum information for credit card authorization

6025

6025: Bank swift code and bank country code are required for IBAN

6026

6026: Bank check digit is required for French banks

6027

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

Associated Inputs:  iban, alt_pay_method_iban

6028

6028: Bank check digit is 2-digit numeric

6029

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

Associated Inputs: bank_swift_cd, alt_pay_method

6030

6030: Bank ID code and bank country code are required for BBAN

6031

6031: BBAN is numeric and up to 16 digits

Associated Inputs: alt_payment_method, bank_acct_no

6032

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

6033

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

Associated Inputs: bank_branch_cd

6034

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

Associated Inputs: iban, bank_acct_no

6035

6035: Account creation race condition encountered.

6036

6036: Missing encryption key

6039

6039: Missing values for required Plan instance field

6040

6040: Card number provided is not on the blacklist and thus cannot be removed

6041

6041: Card number provided is already on the blacklist

6042

6042: Card number provided is not on the blacklist and thus notes cannot be added

6043

6043: No text provided for the notes input

6044

6044: Error generating velocity identifier.

6045

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

Associated Inputs: payment_method_type

6046

6046: The payment method specified is not a credit card. Only credit cards can be added to the blacklist.

6047

6047: The payment method provided is not associated with the specified account.

6048

6048: All sequence numbers provided are invalid (e.g., are not associated with the specified account, are not credit cards, etc.).

6049

6049: All payment methods provided are invalid (e.g., are not associated with the specified account, are not credit cards, etc.).

6050

6050: Could not reverse authorized electronic payment.

6051

6051: Invalid Billing sequence number.

Associated Input: seq_no

6052

6052: The original payment was not made through a credit card.

Additional Comments: An alternate card is only permitted when payment was by credit card.

6053

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

Associated Inputs: iban, bill_agreement_id, pay_method_type, alt_pay_method

6054

6054: Refund cannot be processed for this payment, since its original payment method is inactive now.

6055

6055: Both Primary and Secondary payment methods cannot be the same payment source.

7001

7001: Recurring billing not allowed because account is a TEST account.

7002

7002: Recurring billing not allowed because account status prevents it.

7003

7003: Recurring billing not allowed because account does not have a billable service Plan.

7004

7004: Recurring billing not allowed. Account is a child account that does not pay for its own service.

7006

7006: Recurring billing not allowed because account has a pending invoice on file and awaiting approval.

7007

7007: Recurring billing not allowed because account's next anniversary billing date is in the future.

7008

7008: Recurring billing not allowed on this account

7011

7011: Single order billing not allowed because account is a TEST account.

7012

7012: Single order billing not allowed because account status prevents it.

7021

7021: Electronic collection not allowed because account is a TEST account.

7022

7022: Electronic collection not allowed because account status prevents it.

7025

7025: Electronic collection not allowed because no valid electronic form of payment on file.

7026

7026: Pro-ration to new bill day only supported for first invoice

7027

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

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

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

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

7031: Invalid dunning_process_no

Associated Inputs: dunning_process_no

7032

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

7033: Invalid client defined dunning process id

Associated Inputs: client_dunning_group_id

7034

7034: invalid dunning state

Associated Inputs: dunning_state

7035

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

7036

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

Associated Inputs: force_bill_date_reset

7037

7037: The Plan selected for update is a Supplemental Plan. The force_bill_date_reset input can only be used in conjunction with a status change associated with a Master Plan. Please clear the value of force_bill_date_reset or remove the Supplemental Plan status change from the queue.

Associated Inputs: force_bill_date_reset

7038

7038: A Billing Group is required for a Self-Pay Child Account's MPI.

7039

7039: Recurring billing not allowed. Account’s MPI is a child MPI that does not pay for its own service.

8001

8001: PDF conversion error

8002

8002: Invalid or missing account reference

8003

8003: Invalid or missing invoice/statement reference

8004

8004: Child account, does not receive notices of its own charges

8005

8005: No email address on file

8006

8006: No message template found

8007

8007: message size too large

8008

8008: message does not exist

8009

8009: Statement cannot be emailed. Email address under Billing Group's statement contact or primary payment method's billing contact is not found.

8010

8010: Collection attempted, email address not valid or missing.

9001

9001: failed to post transaction

9002

9002: failed to activate account

9003

9003: failed to find account

9004

9004: failed to find transaction

9005

9005: currency not assigned

9006

9006: failed to deactivate account

9007

9007: posting authorization failed

9008

9008: duplicate transaction posted

10001

10001: This client is not configured to use ARC.

10002

10002: Could not find client authentication key.

10003

10003: Unable to locate error values inside WDDX document.

10004

10004: Error reading WDDX document: unable to determine array length.

10005

10005: Error reading WDDX document.

10006

10006: Cannot decrease resource balance below zero

10008

10008: Could not retrieve arc items.

11001

11001: Invalid device ID

11002

11002: Device already assigned to account

11003

11003: Device name is longer than allowed

11004

11004: Device name is not unique to account

11005

11005: Child account already assigned to device

12001

12001: Account group does not exist

Associated Inputs: group_no, acct_group_id

Additional Comments: An invalid seq_function group_id was entered.

12002

12002: Account group is collections based

Associated Inputs: functional_acct_group_no or client_functional_acct_group_id

12003

12003: Account group is not collections based

Associated Inputs: collection_acct_group_no or client_collection_acct_group_id

12004

12004: Account already assigned to this group

Associated Inputs: collection_acct_group_no or client_collection_acct_group_id

12005

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.

12006

12006 Account i snot assigned to this group

12007

12007 cannot assign collection group without billing info

12010

12010: Client account group does not exist

Associated Inputs: collections_acct_group_no, client_acct_group_id, alt_client_acct_group_id

12011

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

Associated Inputs: collection_acct_grp_directive, collection_acct_group_no, client_collection_acct_group_id

12012

12012: Collection group does not exist

12013

12013: Collection group identifier does not exist

12014

12014: Credit Card Check Failed.

12015

12015: Collection group details missing

12016

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

12017

12017: Billing group is not assigned to this group

12018

12018: Billing group already assigned to this group

13001

13001: Invalid session

13002

13002: Active session exists

13003

13003: Session not allowed

13004

13004: Can not connect to server

13005

13005: Can not authenticate server

13006

13006: Error writing to server

13007

13007: Error reading from server

13008

13008: Timeout writing to server

13009

13009: Timeout reading from server

13010

13010: Local directory not found

13011

13011: Remote directory not found

13012

13012: Local file not found

13013

13013: Remote file not found

13014

13014: Can not write local file

13015

13015: Can not write remote file

13016

13016: File format error

13017

13017: Data format error

13018

13018: No valid data

13019

13019: File too big

13020

13020: File compression failed

13021

13021: File decompression failed

13022

13022: File rejected

13023

13023: Can not read local file

13024

13024: Can not write error file

13025

13025: Can not read error file

13026

13026: Can not write remote error file

13027

13027: No data retrieved

13028

13028: Some errors occurred

13029

13029: External program not found

13030

13030: External program not executable

13031

13031: External program could not start

13032

13032: External program command line arguments incorrect

13033

13033: External program could not open log file

13034

13034: External program could not open exception file

13035

13035: Can not read password file

13036

13036: Could not decrypt file

13038

13038: Can not read configuration file

13039

13039: Format error in configuration file

14001

14001: invalid Master Plan no

Associated Inputs: plan_no

14002

14002: invalid Supplemental Plan no

Associated Inputs: plan_no

14003

14003: error assigning Supplemental Plan

Additional Comments: Unknown error while assigning a Supplemental Plan to an account. Contact Aria Customer support for assistance.

14004

14004: Invalid_plan_no

Associated Inputs: new_plan_no, rollover_plan_no

14005

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

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

14007

14007: invalid Plan service rate_seq combination

14008

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.

14009

14009: cannot force currency change while forcing pro-ration

14010

14010: cannot force currency change while account has non-zero cost financial transactions

14011

14011: cannot force currency change while account has Supplemental Plans that do not have an available rate schedule in the target

currency

14012

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

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

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

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.

14016

14016: The Plan is already assigned to the account

Associated Inputs: new_plan_no

14017

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.

14018

14018: invalid usage accumulation Plan no

14019

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.

14020

14020: inalid usage pooling Plan no

14021

14021: usage pooling cannot be modified on Plans with billed usage

14022

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

14023: Offset Interval must be greater than zero

Associated Inputs: offset_interval

14024

14024: Invalid Offset Interval and Assignment Directive combination.

Associated Inputs: offset_interval, assignment_directive

Additional Comments: Offset_interval only applies to the anniverary date.

14025

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.

14026

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

Associated Inputs: effective_date

14027

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.

14028

14028: Tier Pricing Rule Flat Rate is not valid to configure for the Single Line Upgrade proration

14029

14029: High-Water Mark is not in scope to configure for the Single Line Upgrade proration

14030

14030: Invalid Assignment Directive provided for Single Line Upgrade proration.

Associated Inputs: assignment_directive

14031

14031: Oracle error while selecting for Single Line Upgrade proration.

14032

14032: The Assignment Directive awarding credit cannot be used with the Single Line Upgrade proration invoice service Plan.

14033

14033: Invalid Promo Code

Associated Inputs: promo_cd

14034

14034: Duplicate Plan number in input

14035

14035: Invalid client Plan id

Associated Inputs: client_plan_id, custom_rate_client_plan_instance_id

14036

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

14037

14037: Invalid client sSupplemental Plan ID

14038

14038: Invalid client Master Plan id

Associated Inputs: client_resp_master_plan_inst_id

14039

14039: Invalid client rate schedule id

Associated Inputs: client_alt_rate_schedule_id, rollover_client_rate_sched_id

14040

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

14041

14041: Eligible Plan no/plan ID is required when Eligible service no/service ID is specified

Associated Inputs: eligible_plan_no, client_eligible_plan_id, eligible_service_no, client_eligible_service_id, plan_no, service_no, client_plan_id, client_service_id

14042

14042: Promo Code Expired

Associated Inputs: promo-cd

14043

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.

14045

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

Associated Inputs: promo_cd

14046

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

Associated Inputs: plan_instance_no, master_plan_instance_id, filter_plan_instance_no, percent_eval_plan_instance_no, client_plan_instance_id

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

14047

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

Associated Inputs: client_plan_instance_id, client_master_plan_instance_id, client_percent_eval_plan_instance_id

14048

14048: Status not eligible for completion

14049

14049: Invalid parent Plan instance no

Associated Inputs: parent_plan_instance_no

14050

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.

14051

14051: Invalid Plan status for the new Plan

Associated Inputs: plan_instance_status, status_cd

14052

14052: Missing maser Plan instance number/identifier

Associated Inputs: master_plan_instance_no, client_master_plan_instance_id

Additional Comments: Either mpi_no or cdid is required.

14053

14053: Invalid Master Plan Instance number

Associated Inputs: master_plan_instance_no

14054

14054: Invalid client Master Plan Instance identifier

Associated Inputs: client_master_plan_instance_id

14055

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.

14056

14056: Invalid senior Master Plan Instance number

14057

14057: Invalid client senior Master Plan Instance identifier

14058

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

14059

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,

14060

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

14061

14061: Because the Master Plan on the parent account is in a non-provisioned status, it cannot be selected for parent-pay billing responsibility for Master Plans on the child account

14062

14062: The account Plans have different currencies

14063

14063: duplicate Plan instance client defined id.

Associated Inputs:client_plan_instance_id, new_client_plan_inst_id

14064

14064: Supplemental Plan of this Plan instance cannot be set as its parent Plan.

Associated Inputs: existing_plan_instance_no

14065

14065:Promo code not allowed for Supplemental Plan

Associated Inputs: promo_cd

14066

14066: Assignment directive cannot be anniversary for Master Plan

Associated Inputs: assignment_directive

14067

14067: Supplemental Plan cannot have resp level code and parent account Master Plan Instance number

14068

14068: invalid parent account Master Plan Instance number

Associated Inputs: parent_acct_mp_inst_no, parent_acct_master_plan_inst_id

14069

14069: Alt proration start date needs to be after previous rate schedule change date.

14070

14070: Cannot cancel Plan which is under dunning

Associated Inputs: existing_plan_instance_no

14071

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.

14072

14072: Offset interval not allowed for Master Plan assignment.

Associated Inputs: offset_months

14073

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.

14074

14074: Plan status cannot be updated because the status of the existing Plan does not allow it

Associated Inputs: plan_status_cd

14075

14075: Supplemental Plan not eligible under this Plan instance.

Associated Inputs: new_plan_no

14076

14076: invalid custom rate detail

14077

14077: Account status not support Plan provisioning.

Associated Inputs: status_cd

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

14078

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

14079: Supplemental Plan instance status not support Plan provisioning.

Associated Inputs: supp_plan.status_cd

14081

14081: Plan instance already cancelled

Associated Inputs: existing_plan_instance_no

14082

14082: Plan instance specified for contract completion rate schedule rollover is not included in the contract definition

Associated Inputs: custom_rate_plan_instance_no, custom_rate-client_plan_instance_id

14083

14083: Account or Master Plan Instance information is missing

14084

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

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

14086

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

Associated Inputs: plan_units

14087

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

14088

14088: Mandatory child Plans cannot be canceled unless their parent Plan is also canceled.

14089

14089: Mandatory child Plans have not been added as part of the contract.

Associated Inputs: cascade_action, modify_directive, contract_plan_instances_update

Additional Commetns: This error occurs when cascade_action is false and modify_directive is add.

14090

14090: This Plan cannot be removed from the contract independent of the parent Plan.

14091

14091: The target rate schedule is not active.

14092

14092: Plan can not be assigned because the selected rate schedule is not active.

14093

14093: The Plan submitted does not contain any services with the apply rates daily setting enabled.

14094

14094:Invalid Plan Instance Status CD.

Associated Inputs: plan_status_cd

14095

14095: Usage pooling will not apply for Plans that have the apply usage rates daily setting enabled.

14096

14096: For a Plan with usage that is rated daily, usage cannot be recorded for a date in the past.

14097

14097: An existing Plan instance cannot be used when assigning a new Plan to an account (plan_directive = 1).

Associated Inputs: existing_plan_instance_no, existing_client_plan_instance_id

14098

14098: Invalid proration invoice timing

Associated Inputs: mp_proration_invoice_timing, proration_invoice_timing

14099

14099: Duplicate Plan instance provided meaning the same instance cannot be provided for update/replace/cancel in the same API

Associated Inputs: existing_plan_instance_no

14100

14100: Too many Plan operations. Please reduce the number of Plan operations to be under <limit>.

14101

14101: Mandatory child Plans cannot be replaced unless their parent Plan is also modified.

14102

14102: Invalid parent Plan instance id

Associated Inputs: parent_client_plan_instance_id

14103

14103: cannot rollover queued Plan as the original initial Plan in not matching the current Plan

Associated Inputs: new_plan_no

14104

14104: invalid Plan instance service combination

14105

14105: Mandatory child Plans should be removed from the contract along with the parent Plan.

Associated Inputs: cascade_action, modify_directive, contract_plan_instances_update

Additional Comments: This eror occurs when cascade_action is false and modify_directive is remove.

14106

14106:This mandatory child Plan cannot be removed from the contract without its parent Plan and other mandatory child Plans.

Associated Inputs: cascade_action, modify_directive, contract_plan_instances_update

14107

14107: Invalid Service Number.

Associated Input: custom_rate_service_no

14108

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

Associated Input: assignment_directive

14109

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

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

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

14112

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

Associated Inputs: plan_instance_no, client_plan_instance_id

14113

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

14114

14114: Invalid queued action status

14115

14115: Invalid Plan instance specified for the queue_id provided.

14116

14116: Invalid Queue ID specified for this account

14117

14117: Invalid queued action status specified for the queue_id provided

14118

14118: Invalid queued action status specified for the Plan instance provided

14119

14119: Invalid queued action status specified for the account provided

14120

14120: Include Plan service in order to retrieve Plan service supplemental fields.

14121

14121: Include Master Plan Instances in order to retrieve Supplemental Plan instances.

Associated Inputs: include_master_plans, include_supp_plans

Additional Comments:  You must include Master Plans when retreiving suplemental Plans.

14122

14122: The assignment_directive provided is not valid for the queue_edit_directive specified

14123

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

14124

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

14125

14125: Negative Usage not allowed for Usage-based services in which Usage Pooling is enabled unless pre-rated.

14126

14126: Rate field cannot be negative if amt, billable_units, or usage_units are negative values.

14127

14127: Amount cannot be positive if the billable/usage unit is negative.

14128

14128: Supplemental Plan instance cannot be executed immediately or the date cannot be changed to before the effective date for the corresponding parent Plan instance

14129

14129: Rate per unit cannot be negative.

Associated Input: rate_per_unit

14130

14130: Ensure include_plan_services or include_surcharges is marked as true when setting include_rate_schedule as true. Requesting rate schedules while excluding services and surcharges creates a conflict where no rate schedules will be displayed.

Associated Inputs: include_rate_schedule, include_plan_services, include_surcharges

14131

14131: More than 10 inputs have been found in an array that is limited to 10 inputs. Please reduce the number of inputs.

Associated Inputs: product_catalog_plan_filter[], service_no_filter[], master_plan_instance_filter[], supplemental_field_filter[]

14132

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

14133

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

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

14135

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

14136

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

14137

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

14222

14222: Include Plan service in order to retrieve Plan service supplemental fields.

Associated Inputs: include_plan_services, include_service_supp_fields

Additional Comments: If the include_service_supp_fields is true and include_plan_services is  false then this error occurs.

14300

14300: Cannot force currency change while account has Master Plan / Supplemental Plans that do not have an available rate schedule in the target currency

Associated Input: force_currency_change

14301

14301:Force currency changes are only allowed when submitting with a Master Plan Instance with supported actions (replace, update)

Associated Input: force_currency_change

14302

14302: Pending Invoices must be discarded prior to forcing a currency change.

Associated Input: force_currency_change

14303

14303: Surcharges must be discarded or voided prior to forcing a currency change.

Associated Input: force_currency_change

14304

14304: Rated but unbilled usage records must be discarded prior to forcing a currency change.

Associated Input: force_currency_change

14305

14305: Discounts (flat rate) or Coupons in an existing currency must be discarded or voided prior to forcing a currency change.

Associated Input: force_currency_change

14306

14306: Pending Orders in an existing currency must be discarded or voided prior to forcing a currency change.

Associated Input: force_currency_change

14307

14307: Force currency change not allowed with the supplied assignment directive.

Associated Input: force_currency_change

14308

14308: Force currency change not allowed with different Plans that returns different currencies.

Associated Input: force_currency_change

14309

14309: Cannot force currency change if an Order/Surcharge/Coupon input is included.

Associated Input: force_currency_change

14310

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

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.

14313

14313: There are threshold billing rules attached to this account that will need to be removed prior to changing currency since they are not in the future currency.

Associated Input: force_currency_change

14314

14314: There is an active rollover contract for existing currency and it should be cancelled or terminated before proceeding.

Associated Input: force_currency_change

14315

14315: invalid Master Plan Instance and Billing Group combination.

14317

14317: Rollover plan does not have an active rate schedule with a currency matching the account's currency. 

14401

14401: Negative Usage Records, unless pre-rated, are not allowed when the Rating Model rates usage on a ‘per record’ basis. 

14402

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

15001

15001: invalid coupon code

Associated Inputs: coupon_codes

15002

15002: coupon expired

Associated Inputs: coupon_codes, coupon_cd

15003

15003: coupon already applied to account

Associated Inputs: coupon_cd, coupon_cd

15004

15004: coupon invalid or expired

Associated Inputs: coupon_cd

15005

15005: Surcharge already applied

15006

15006: Duplicate surcharge number in input

Associated Inputs: acct_surcharges, mpi_surcharges, mp_surcharge_no

15007

15007: surcharge_supp_plan_no not found in supp_plan_no input

15008

15008: Invalid surcharge rate schedule no

Associated Inputs: rate_schedule_no, mp_rate_schedule_no

15009

15009: Invalid surcharge number

Associated Inputs: surcharge_no, mp_surcharge_no

15010

15010: Coupon code not allowed for Supplemental Plan

Associated Inputs: coupon_cd

15011

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

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

Associated Inputs: coupon_codes

15013

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

15014: Duplicate Surcharges found.

Associated Input: mp_surcharge_no

15015

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

Associated Inputs: mpi_surcharges, mp_surcharge_no

15016

15016 Invalid coupon directive

Associated Inputs: coupon_directive

15017

15017: Invalid client surcharge id

Associated Inputs: surcharge_updates > client_surcharge_id

15018

15018: Duplicate client surcharge id in input.

Associated Inputs: surcharge_updates > client_surcharge_id

15019

15019: Discount rule no or id is invalid or blank.

Associated Inputs: rule_no > rule_id

15020

15020: Discount rule scope number is invalid or blank.

Associated Inputs: scope_no

15021

15021: Plans on override discount rule scope can not be blank.

Associated Inputs: scope_no

Additional Comments: Users enter scope_no: 11 - but Plan not provided.

15022

15022: Plans on override discount rule scope are invalid.

Associated Inputs: scope_no

Additional Comments: Users enter scope_no: 11 - but Plan not provided.

15023

15023: Services on override discount rule scope can not be blank.

Associated Inputs: scope_no

Additional Comments: Users enter scope_no: 12 - but Service not provided.

15024

15024: Services on override discount rule scope are invalid.

Associated Inputs: scope_no

Additional Comments: Users enter scope_no: 12 - but service is Invalid.

15025

15025: Service on override discount rule scope not assigned to Plan.

Associated Inputs: scope_no

Additional Comments: Users enter scope_no: 13 - but Plan and service are mismatched.

15026

15026: Items on override discount rule scope can not be blank.

Associated Inputs: scope_no

Additional Comments: Users enter scope_no: 31 - but Item not provided.

15027

15027: Items on override discount rule scope are invalid.

Associated Inputs: scope_no

Additional Comments: Users enter scope_no: 11 - but Plan is Invalid.

15028

15028: Duplicate Plans/items/services on override discount rule scope were entered.

Associated Inputs: scope_no

Additional Comments: When duplicate values of items/plans/services are entered twice in the call.

16001

16001: contract does not exist

Associated Inputs: contract_no, client_contract_id

16002

16002: invalid contract input

Associated Input: new_acct_plan_contracts[]

Additional Comments: Used in create_acct_complete API which belongs to A6; not used in Aria Billing Cloud.

16003

16003: Invalid Contract Closure Status

Associated Input: close_status

16004

16004: Invalid Filter_Status_Code.  The Filter_Status_Code must be 0=Inactive, 1=Active or Blank/Null=(Default value for both Active and Inactive)

Associated Input: filter_status_code

16005

16005: Invalid Modify_Directive.

Associated Input: modify_directive

16006

16006: This contract is ineligible for editing because its scheduled end date is in the past.

16007

16007: This contract is ineligible for editing because it is no longer in effect.

Associated Inputs: contract_no, client_contract_id

16008

16008: At least one Plan is not in this contract. No Plans were removed

16009

16009: The Plan can not be added because it is already in the contract.

16010

16010: At least one Plan must be in this contract.  Cannot remove all Plans

16011

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

Associated Inputs: acct_no, client_acct_id

16012

16012: Contract end date is less than start date

Associated Inputs: date_range_start, date_range_end, start_date, end_date, length_months

16013

16013: Unsupported contract type

Associated Inputs: contract_type_no, type_no

16014

16014: Contract could not take effect before the assignment date of the Plans

16015

16015: Plan Instance is not in this contract. No Plan instances were removed

Associated Inputs: Plan_instance_no, client_plan_instance_id

16016

16016: The Plan instance can not be added because it is already in the contract.

Associated Inputs: plan_instance_no, client_plan_instance_id

16017

16017: At least one Plan instance must be in this contract.  Cannot remove all Plan instances

Associated Inputs: modify_directive, contract_plan_instances_update

16018

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

16019

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

16020

16020: The target Plan used for contract rollovers must be a sibling of the existing Plan in the product catalog.

Associated Inputs: rollover_plan_no, client_rollover_plan_id

16021

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

16022

16022: The contract rollover target rate schedule is not associated with the contract completion rollover target Plan.

Associated Inputs: rollover_rate_sched_no, rollover_client_rate_sched_id

16023

16023: The contract completion target rate schedule rollover is not associated with the Plan instance specified.

Associated Inputs: rollover_rate_sched_no, rollover_client_rate_sched_id

16024

16024: The contract rollover target Plan no is ineligible because it must be Master Plan no

Associated Inputs: rollover_plan_no, rollover_client_plan_id

Additional Comments: The current and rollover Plan types must match.

16025

16025: The contract rollover target Plan no is ineligible because it must be Supplemental Plan

Associated Inputs: rollover_plan_no, rollover_client_plan_id

16026

16026: Contract could not take effect before the Account Created Date

16028

16028: This contract cannot be cancelled or terminated because it already was cancelled, terminated or expired.

Associated Inputs: contract_no, client_contract_id

16029

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

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

16031

16031: duplicate client contract id.

Associated Input: client_contract_id, new client_contract_id

16032

16032: Invalid client contract id.

Associated Input: client_contract_id, new client_contract_id

16033

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

17001

17001: Client not eligible to subscribe to event

18001

18001: could not create statement

18002

18002: could not send statement

18003

18003: statement could not be found

18004

18004: preview notice string unavailable

18005

18005: Invalid Template number

Associated Inputs: alt_msg_template_no, cn_alt_msg_template_no, alt_inv_template_no, alt_stmt_template_no

18006

18006: Invalid client template id

Associated Inputs: client_cn_alt_msg_template_id, client_alt_msg_template_id, client_alt_inv_template_id

18007

18007: Minimum Statement Threshold must be a positive number

18008

18008: Minimum Statement Threshold cannot be greater than the Minimum Dunning Threshold

18009

18009: Maximum Number of Statements to Defer must be a positive number

18010

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

18011: Invalid Rebill Template number

Associated Inputs: rebill_template

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

19001

19001: The source account and source MPI statuses should be "Active".

19002

19002: The destination account status should be "Active".

19003

19003: The source and destination accounts need to be of same currency.

19004

19004: The source and destination accounts need to be of same legal entity.

19005

19005: The source MPI should not have an outstanding balance.

19006

19006: The source MPI should not be in dunning.

19007

19007: The source MPI should not be a responsible MPI or a parent-pay MPI.

19008

19008: The source MPI and its SPIs should not have a service destination contact (when allow_copy_pi_service_dest_contact = false for PII compliance).

19009

19009: The source MPI should not have any pending invoice.

19010

19010: The MPI and its SPIs should not have any pending future queues, anniversary queues, or status change queues.

19011

19011: The source MPI should not have any pending orders (non-fulfilled, non-invoiced).

19012

19012: The source MPI and its SPIs should not have any pending contracts.

19013

19013: The source MPI and its SPIs should not have any recurring arrears pending charges.

19014

19014: The source MPI and its SPIs should not have any proration pending/open charges.

19015

19015: The source MPI and its SPIs should not have any unbilled usage records.

19016

19016: The source and destination accounts cannot be the same.

19017

19017: For porting_directive=1, the same source MPI should not be attempted to port more than once on the same API call.

19018

19018: For porting_directive=TBD, the same source MPI should not be attempted to port to same destination account more than once on the same API call.

20001

20001: invalid credit id

20002

20002: Usage Type or Usage Type Code must be entered

20003

20003: Invalid Usage Type

Associated Inputs: specified_usage_type_no

20004

20004: Invalid Usage Type Code

Associated Inputs: specified_usage_type_code

20005

20005: Invalid set of values for do_write and bill_immediately

Associated Inputs: bill_immediately, do_write

Additional Comments: Do_write can be ture only when bill_immediately is 1.

20006

20006: usage code or type not on active Plan

20007

20007: Limit Records number must be greater than zero

Associated Inputs: Limit, limit_records

20008

20008: No record found for the input provided

20009

20009: Percentage value should be greater than zero and less than or equal to 100.

20010

20010: End date should not be less than start date

20011

20011: No service outage in period

20012

20012: invalid credit reason code

20013

20013: Skip Records number must be greater than zero

Associated Input: offset

20014

20014: invalid service type

20015

20015: eligible service types must unique

Associated Input: eligible_service_type

20016

20016: The recurring credit ID is invalid or not associated with the given account number.

20017

20017: recurring credit is already cancelled

20018

20018: There are no recurring credits to cancel

20019

20019: credit amount cannot be negative or zero

20020

20020: Credit expiration month is mandatory when expiration indicator is given as M.

Associated Inputs: credit_expiry_type_ind, credit_expiry_months

20021

20021: Invalid credit expiration Indicator.

Associated Input: credit_expiry_type

20022

20022: Invalid credit expiration Indicator or frequency number.

Associated Inputs: credit_expiry_type_ind, frequency_interval_type

20023

20023: Invalid credit expiration date. Credit expiration date should be in future.

Associated Input: credit_expiry_date

20024

20024: Credit expiration date is mandatory when expiration indicator is given as D.

Associated Inputs: credit_expiry_type_ind, credit_expiry_date

20025

20025: The credit expiry month should be a positive integer.

Associated Input: credit_expiry_month

20026

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.

20027

20027: Invalid credit number

Associated Inputs: credit_no

20028

20028: Inputted credit id doesn't belong to Master Plan Instance

Associated Inputs:i credit_ids

20029

20029: Inputted credit doesn't belong to account

Associated Inputs: credit_ids

20030

20030: Provided credit id is invalid

Associated Inputs:i credit_ids

20031

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.

20032

20032: Cash credit amount cannot exceed account balance.

20033

20033: Credit amount exceeds available unpaid balance.

20034

20034: An unexpected value was entered in the service_code_option field. Please review this value and ensure it matches one of the allowable values.

Associated Input: service_code_option

20035

20035: The service_code_option entered suggests handling that involves alt_service_no_to_apply or client_alt_service_id_to_apply. Please either update the service_code_option or include an input for alt_service_no_to_apply or client_alt_service_id_to_apply.

Associated Input: service_code_option, alt_service_no_to_apply, client_alt_service_id_to_apply

20036

20036: The service_code_option entered suggests handling that does not involve alt_service_no_to_apply or client_alt_service_id_to_apply. Please update either the .service_code_option or remove the input from alt_service_no_to_apply or client_alt_service_id_to_apply

Associated Input: service_code_option, alt_service_no_to_apply, client_alt_service_id_to_apply

20037

20037: The percent_eval_service_no input field only accepts recurring and recurring in arrears service types.

Associated Input: percent_eval_service_no

20038

20038: Expiration date needs to be greater than application date of the last recurring service credit.

Associated Input: credit_expiry_date

20039

20039: Invalid frequency interval type.

Associated Input: frequency_interval_type

20040

20040: Credit expiry period cannot be more than 999 Days/Weeks/Months.

Associated Input: credit_expiry_period

20041

20041: Credit expiry period should be positive integer.

Associated Input: credit_expiry_period

20042

20042: Credit expiry period is required.

Associated Input: credit_expiry_period

20043

20043: Credit interval length is required.

Associated Input: frequency_interval_length

20044

20044: Credit interval length should be positive integer.

Associated Input: frequency_interval_length

20287

20287: The email address is not valid.

Associated Inputs: email, bill_email, stmt_email

21001

21001: Authentication Error

21002

21002: Tax Error

21003

21003: Server Error

21004

21004: Exception or Warning

22001

22001: invalid autoexport destination

22002

22002: invalid autoexport source

22003

22003: invalid autoexport object

22004

22004: autoexport object already mapped

22005

22005: Invalid external destination id

22006

22006: Cannot enter data for only one field!  Both the external_destination_id and external_id fields must be valued.

23001

23001: Discard usage completed with some errors

23002

23002: Usage record not found

23003

23003: Usage already billed

23004

23004: Given client_record_id associated with multiple usage records.

23005

23005: Usage already discarded.

23006

23006: End date is less than start date.

23007

23007: Start date parameter is required

23008

23008: Threshold units is required

23009

23009: Threshold level number is required

23010

23010: Threshold level value is required

23011

23011: Invalid Threshold Level Number

23012

23012: usage type not suitable for units threshold applicability set on Plan

23013

23013: Invalid usage threshold applicability

Associated Inputs: usage_threshold_applicability

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

23014

23014: There is no standard pricing rule service in Plan for usage pool

23015

23015: Invalid Usage threshold type

23016

23016: Invalid Usage threshold dest type.

23017

23017: A usage_type_no or client_usage_type_id is not required since the Plan instance being updated has pooling enabled and the unit-based usage threshold is "Set at the usage pool level".

23018

23018: A usage_type_no or client_usage_type_id is required since the Plan instance being updated either does not have pooling enabled or has pooling enabled but the Unit-Based Usage Thresholds is "Set individually by usage type".

23019

23019: Either a monetary amount or unit based threshold are required.

23020

23020: Usage unit value is too large.

23021

23021: Client record id cannot be blank

Associated Inputs: client_record_id

23022

23022: Client record id already exists

Associated Inputs: client_record_id

23023

23023: Client record id and usage type code already exists

Associated Inputs: client_record_id, usage_type_code

24000

24000: One or more queued Plan numbers entered do not exist

24001

24001: The value of remove_all_queued_plan_no must be true, false or blank

24002

24002: You must provide Plan No(s) when remove_all_plan_no is false

24003

24003: No queued Plans to delete for the given acct_no

24004

24004: Failed to find the account

24005

24005: Valid values for remove_terminate_pending are true, false or blank

24006

24006: No Plan was cancelled or undone because the inputs were not provided for remove_all_queued_plan_no, queued_plan_no and/or remove_terminate_pending

24007

24007: No queue found for the given scope.

Associated Input:  plan_scope

24008

24008: Plan is scheduled to be covered by a contract

24009

24009: Invalid Queue Date

Associated Input:  queue_date

Additional Comments: Queue date must be in the future.

24010

24010: Invalid Queue Days

Associated Input:  queue_days

Additional Comments: Queue days must not be negative

24011

24011: Invalid Queue Edit Directive.

24012

24012: Duplicate of Queue Id / Plan Instance No / Client Plan Instance Id found.

24013

24013: No Queued Plan Instance Found for the given input.

24014

24014: Not a valid Queue Id.

24016

24016: Invalid Plan scope value.

Associated Input: plan_scope

24381

24381: Bulk errors

Additional Comments: This message may be returned because of an internal system error. Please contact Aria Customer Support for assistance.

25000

25000: Bulk usage loader completed with some error(s)

25001

25001: failed to calculate taxes

25002

25002: The Plan is not active and therefore contract can't be created

25003

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

Associated Inputs: client_sku

Additional Comments: You have entered an invalid inventory item.

25004

25004: Inventory item units cannot exceed the number of Plan units

Additional Comments: item_units

25005

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

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

Associated Inputs: item_units, plan_no, client_plan_id

25007

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.

25009

25009: One or more provided inventory items are not eligible for purchase.

Associated Inputs: client_sku

Additional Comments: Inventory items are not mapped to the Plans on the account.

25010

25010: One or more provided inventory items are Inactive.

Associated Inputs: client_sku

25011

25011: Invalid Master Plan Instance information provided.

25012

25012: Invalid purchase scope input

Associated Input:  purchase_scope

25013

25013: No price has been defined for this item in the currency specified.

25014

25014: No prices have been defined for this item.

25017

25017: Missing required parameter Adjustment Days

25018

25018: Missing required parameter Adjustment Date

25020

25020: Illegal characters entered

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

25022

25022: Unsupported backup pay method provided

Associated Inputs: billing_groups_array.backup_payment_method_no/client_backup_payment_method_id

25023

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.

25024

25024:  Primary pay method does not support backup pay method

25025

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

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

25027

25027: Provided payment method is not a credit card

Associated Inputs:cc_expire_yyyy, cc_expire_mm, pay_method_type

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

25028

25028: Provided payment_method_id is already in a disabled state.

Associated Inputs: payment_method_type, payment_method_no, client_payment_method_id

25029

25029:  The payment method provided is not a tokenized credit card

25030

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

Additional Comments: override_bill_thru_date, alt_bill_day

25031

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

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

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

25034

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

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

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

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

25038

25038: override dates mp instance billing goup details and new plan billing grop details should be same

25039

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

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

25041

25041: The integration with the payment processor that generated this token does not support the retrieval of token details.

25042

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

Associated Inputs: cc_expire_yyyy, cc_expire_mm, payment_method_no, client_payment_method_id

25043

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

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.

25045

25045: One or more fraud control fields are missing or invalid fraud control field name

25046

25046: One or more fraud control fields values are missing or invalid fraud control value

25047

25047: Invalid fraud control fields name or value.

25048

25048: Fraud scoring failed.

25049

25049: Fraud scoring is not supported for the configured payment processor.

25050

25050: Invalid fraud input field names.

25051

25051: Cannot use Master Plan Instance assigned in future without effective date as override_dates_mp_instance_no or override_dates_client_mp_instance_id.

26000

26000: You should not use this API because your client parameter Account_EOM_Enabled is set to True.

26001

26001: This API is not supported because your client parameter Account_EOM_Enabled is set to True. Please contact Aria customer support with questions about the Account_EOM_Enabled client parameter.

26002

26002: This API is not supported because your client parameter Account_EOM_Enabled is set to True. Please contact Aria customer support with questions about the Account_EOM_Enabled client parameter.

26003

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.

26004

26004: Include billing groups in order to retrieve payment methods.

Associated Inputs: include_billing_groups, include_payment_methods

26005

26005: The credit expiry month should be a positive integer.

26006

26006: Invalid filter status

Associated Input: filter_status

26007

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

26008

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

26009

26009: Invalid contact Type Indicator

Associated Input: contact_ind

26010

26010: Invalid billing group number

Associated Inputs: billing_group_no

26011

26011: Missing billing group identifier

Associated Inputs: billing_group_no, client_billing_group_id

Additional Comments: Billing group is required for contact type 2, 3, and 4.

26012

26012: Invalid client-defined billing group ID.

Associated Inputs: client_billing_group_id

26013

26013: Invalid dunning group number

Associated Inputs: dunning_group_no

26014

26014: Invalid client-defined dunning group ID.

Associated Inputs: client_dunning_group_id

26016

26016: This billing group cannot be disabled because it is associated with a provisioned Master Plan

Associated Input: billing_group_directive

26017

26017: This dunning group cannot be disabled because it is associated with a provisioned Master Plan

26018

26018: Invalid dunning group directive

Associated Inputs: dunning_group_directive

26019

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

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

26021: Invalid billing group idx

Associated Inputs: billing_group_idx

26022

26022: Invalid dunning group idx

Associated Inputs: dunning_group_idx

26024

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

Associated Inputs: status_cd

26025

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

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

26027

26027: Missing Master Plan Instance and billing group inputs

26028

26028: Duplicate Plan instance index in input

Associated Inputs: plan_instance_idx

Additional Comments: The same plan_instance_idx was submitted twice.

26029

26029: Invalid billing group directive

26030

26030: The dunning state of the Master Plan Instance cannot be updated to In Progress because no applicable dunning process was found. Please review the dunning processes defined for the appropriate dunning group, Plan, payment method, and/or the client-default to ensure a dunning process exists for this scenario.

Associated Inputs: dunning_state

26031

26031: Client payment terms id not found.

Associated Inputs: client_payment_term_id

26032

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.

26033

26033: Both payment method and payment terms have been passed for the account record. You may provide either payment method or payment terms.

26034

26034: Payment terms not found.

Associated Inputs: payment_terms_no, payment_terms_name, client_payment_term_id

26035

26035: Invalid Payment option.

Associated Inputs: payment_option

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

26036

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

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.

26038

26038: Source account Master Plan Instance does not have any balance.

26039

26039: Destination account Master Plan Instance is not a self pay.

26040

26040: Source account Currency is not matching with destination account Currency.

26041

26041: Billing group details missing

26042

26042: No token available for the specific collection group

26043

26043: Invalid Collection Group at Billing Group level for Token Refresh

26044

26044: Target account has more collection groups associated than the Source account

26045

26045: Same agreement Id can not be used for multiple collection groups

26046

26046: Invalid dunning step. The dunning step does not exist in the dunning process configuration.

26047

26047: Dunning group cannot be modified since it is already disabled.

26048

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.

27001

27001: Invalid fulfilment directive

Associated Inputs: fulfillment_directive

27002

27002: The fulfilment service provided is already invoiced.

Associated Inputs: service_no, client_service_id

27003

27003: invalid Plan unit instance

Associated Inputs: plan_unit_inst_no

27004

27004: invalid Plan unit instance id

Associated Inputs: client_plan_unit_inst_id, new client_plan_unit_inst_id

27005

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.

27006

27006:The fulfillment date should not be provided in the future for the immediate fulfilment directive

Associated Inputs: service_fulfillment_date

27007

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.

27008

27008: The fulfilment date should not be provided beyond billing period. The fulfillment date must not be outside the current billing

Associated Inputs: service_fulfillment_date

27009

27009: The fulfilment date should not be provided in past when fulfilment directive provided as future

Associated Inputs: service_fulfillment_date, fulfilment_directive

27010

27010: The fulfilment date should be provided when fulfilment directive provided as futureThe fulfillment date cannot be blank when the fulfillment directive indicates a future fulfillment date

Associated Inputs: .service_fulfillment_date, fulfilment_directive

27011

27011: The API 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 Input: client_no

27012

27012: Inactive Plan unit instance

Associated Input: plan_unit_inst_no

27013

27013: Inactive Plan unit instance id

Associated Input: client_plan_unit_inst_id

27014

27014: Missing values for required Plan unit instance field

27015

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

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

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

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

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.

27020

27020: Fulfillment date cannot be earlier than start date.

Associated Inputs: service_fulfillment_date

27021

27021: Plan instance should have a minimum of 1 unit instance

27022

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.

27023

27023: Invalid Plan Unit Instance Index

27024

27024: Duplicate Plan unit instance index in input

Associated Inputs: plan_unit_inst_idx

28001

28001: This module group is not granted for access for this user

28002

28002: This outer module is not granted for access for this user.

28003

28003: The outer module number is not passed.

28004

28004: This inner module is not granted for access for this user.

28005

28005: The inner module number is not passed.

29001

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

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

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

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.

29005

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

Associated Inputs: acct_contact_no, bill_contact_no, stmt_contact_no

29006

29006: Could not create contact

29007

29007: Missing Credit Memo Comments

Associated Input: cm_comments

29008

29008: Invalid Supplemental Plan instance number

Associated Inputs: cm_line_items > [supp_plan_instance_no, client_supp_plan_instance_id]

29010

29010: Invalid responsible account no

Associated Input: resp_acct_no

29011

29011: Invalid responsible account user id

Associated Input: resp_acct_user_id

29012

29012: Invalid responsible client account id

Associated Input: resp_client_acct_id

29013

29013: Client Parameter, Dispute Hold Expiration Override Maximum Days, is invalid.

Associated Input: expire_hold_days

29014

29014: The value of Dispute hold override (Expire_Hold_Days) is invalid.

Associated Input: expire_hold_days

32001

32001: Installment term no does not exist.

32002

32001: <installment_number> cannot be updated to a non-default. Assign another installment term number as the new default installment term.

32003

32003: <installment_number> cannot be deleted. Assign another installment term number as the new default installment term.

32004

32004: Client installment term id does not exist.

32005

32005: Assign one installment term as a default using the input parameter is_default.

32006

32006: Inputs conflict: assign_installment_term input conflicts with client installment term id or installment term no.

33001

33001: Cancellation failed. This transaction is ineligible for an automated payment recovery process.

33002

33002: Could not cancel the automated payment recovery process for this transaction.

  • Was this article helpful?