|
|
|
1004: authentication error
|
<auth_key>, <client_no> |
1009: account does not exist, Account not found: AriaNo (acct_no), Account not found: Userid (userid), or Account not found: ClientId (client_acct_id)
|
<acct_no>, <client_acct_id> |
1010: missing required parameters, Missing input: (object-name) is required with assignment_directive ($AriaNo)
|
<custom_rate_per_unit>, <custom_rate_seq_no>, <acct_no>, <client_acct_id>, <assignment_directive> |
1012: invalid input format
Additional Comments: This value must be unique for a client and must be alphanumeric. A previously used client_receipt_id can be reused if all those previous calls have failed (with an error_code other than 0/OK), if the client parameter NEVER_ALLOW_USED_RECEIPT_ID = FALSE.
|
<client_receipt_id> |
1016: invalid input
Additional Comments: This error can be caused by the wrong type of input; for example, text in a numbers-only field, or specifying a value other than one of the documented allowable values.
|
<assignment_directive>, <client_def_billing_group_id>, custom_rate_service_no/custom_rate_client_service_id>, <client_plan_instance_id>, <force_master_bill_date_reset>, <offset_months>, <plan_units>, <acct_no> |
1024: invalid date format
Additional Comments: All date inputs must be in yyyy-mm-dd format.
|
<bill_birthdate>, <alt_start_date>, <stmt_birthdate>
|
1031: can not pass in an alternate starting date AND alternate billing day
|
<alt_bill_day>, <alt_start_date> |
1033: a parameter that represents a true or false value contains invalid input
|
<do_write>, <usage_pooling> |
1035: invalid assignment directive, Invalid Assignment Directive: (assignment_directive)
|
<assignment_directive> |
1049: Billing or Plan changes not allowed due to the account status, Cannot add assignment for account with status code -99, Cannot add assignment for account with status code 0
Additional Comments: This message indicates a processing problem.
|
|
1053: invalid notification template group id
|
<notify_template_group> |
1069: Long cycle (Combine invoice) is not available, since Plan instance has Plan rollover or contract rollover or future Plan changes in the middle of the cycle or while generating a pending invoice.
|
|
1500: Unsupported bank/country code for this payment method.
Additional Comments: Added in support of ACH payments via Direct Debit (country code must be US).
|
<bank_country_cd> |
3017: pro-ration period cannot be greater than Plan billing interval
|
|
3018: invalid automatic offset months option
|
|
4006: invalid pay method or alternate pay method
|
<primary_pay_method_type> |
4008: invalid expiration date
Additional Comments: Dates must be in yyyy-mm-dd format. For update_payment_method_token_m, the date must be a future date.
|
<cc_expire_mm>, <cc_expire_yyyy> |
|
|
<cc_number> |
4010: invalid bank draft info
Additional Comments:
- The client parameter BANK_DRAFT_INDICATOR must be enabled.
- Bank_acct_no and bank_routing_no are required.
- Valid bank_routing_no from Aria's ABA lookup in case of US address.
- Bank_routing_no must be numeric.
- For US, bank_routing_no should be 9 digits in length (left padded with zeros).
- Bank_routing_no must pass checksum validation.
|
<bank_acct_no>, <bank_routing_no> |
4017: duplicate payment method client defined id.
Additional Comments: This value must be unique at the client level.
|
<primary_pay_method_cdid> |
4019: Invalid Bank Account Type.
|
<bank_acct_type> |
4032: cc_id is required.
Additional Comments: cc_id is required for this payment processor.
|
<cc_id> |
4044: Missing a required value. Please check that either bank_account_no, bank_routing_number or agreement_id is present.
|
|
5003: invalid notify method
|
<notify_method> |
5004: invalid responsibility level cd
Additional Comments: Resp_level_cd=4 is not supported in Aria Billing Cloud.
|
<resp_level_cd> |
5020: alternate billing day must be between 1 and 31
|
<alt_bill_day> |
5041: Invalid invoicing option provided
|
<invoicing_option> |
5052: Product field is not mapped to the Plan you have specified. Alt: Invalid product field
Additional Comments: The field is not mapped to the Plan.
|
<plan_instance_field_name> |
5053: Missing values for required Plan instance field
Additional Comments: This field is required, but did not have a value.
|
<plan_Instance_field_value> |
5059: Invalid Product Field Value.
Additional Comments: The value must be from the configured allowed values.
|
<plan_instance_field_value> |
5061: Number of Product Field value exceeds maximum number of allowed values.
Additional Comments: The value must meet the configured maximum values.
|
<plan_instance_field_value> |
5062: Number of Product Field values does not meet required minimum number of values.
Additional Comments: The value must meet the configured minimum values.
|
<plan_instance_field_value> |
5019: error recording balance forward
Additional Comments: This indicates an error in the balance forward transaction creation.
|
<balance_forward> |
6021: Invalid state_prov entered
|
<bill_state_prov>, <stmt_state_prov> |
6027: IBAN is alphanumeric and is 15 to 34 characters in length
|
<iban> |
6029: Bank swift code is alphanumeric and is 8 or 11 characters in length
|
<bank_swift_cd> |
6031: BBAN is numeric and up to 16 digits
|
<bank_acct_no> |
6032: Bank ID code is numeric and up to 10 digits
|
|
6033: Bank branch code is numeric and up to 10 digits
|
<bank_branch_cd> |
6034: Basic bank account number or IBAN is required for Direct Debit
|
<iban>, <bank_acct_no> |
6045: Account can have only one active NETS payment method.
|
<primary_pay_method_type> |
6053:Either IBAN or Agreement ID is required for this payment method.
|
<iban>, <bill_agreement_id>, <primary_pay_method_type> |
7028: duplicate billing group client defined id.
Additional Comments: This value must be unique at the client level.
|
<client_def_billing_group_id> |
7029: The new_client_dunning_group_id field contains the ID of an existing dunning group.
Additional Comments: This value must be unique at the client level.
|
<client_dunning_group_id> |
7031: Invalid dunning_process_no
|
<dunning_process_no> |
7033: Invalid client defined dunning process id
|
<client_dunning_group_id> |
7035: The Plan selected for update is a Master Plan. The force_master_bill_date_reset input can only be used in conjunction with Supplemental Plans. Please clear the value of force_master_bill_date_reset or input a Supplemental Plan.
|
<force_master_bill_date_reset> |
12010: Client account group does not exist
|
<alt_client_acct_group_id> |
12012: Collection group does not exist
|
|
12013: Collection group identifier does not exist
|
|
12016: Billing group belongs to collections based group using same payment method
|
|
|
|
<new_plan_no> |
14006: invalid rate schedule no
|
<mpi_rate_schedule_no>, <alt_rate_schedule_no> |
14012: Alternate rate schedule's currency does not match the account's currency.
Additional Comments: The alt_rate_schedule currency does not match the account currency.
|
<alt_rate_schedule_no>, <client_alt_rate_schedule_id> |
14016: The Plan is already assigned to the account
|
<new_plan_no> |
14017: invalid alternate proration start date Alt: Date must be in YYYY-MM-DD format
Additional Comments: The alt_proration_start_date must be within the last billed period.
|
<alt_proration_start_date> |
14019: usage_accumulation_reset_months must be from 0 to 99 Alt: invalid usage accumulation reset months value
Additional Comments: The accumulation months is not between 0 and 99.
|
<usage_accumulation_reset_months> |
14022: Supplemental Plan violates Plan exclusion group
Additional Comments: The Supplemental Plan is not matched with the Master Plan exclusion group.
|
<plan_no> |
14023: Offset Interval must be greater than zero
|
<offset_interval> |
14024: Invalid Offset Interval and Assignment Directive combination.
Additional Comments: Offset_interval only applies to the anniverary date.
|
<offset_interval>, <assignment_directive> |
14025: Invalid do_write and assignment directive combination for queuing Plan.
Additional Comments: Preview cannot be done for queued anniversary date cases.
|
<assignment_directive>, <do_write> |
14026: The Effective Date must be in the future, "YYYY-MM-DD" format, and a valid date.
Associated Inputs: effective_date
|
<effective_date> |
14033: Invalid Promo Code
|
<promo_cd> |
14035: Invalid client Plan id
|
<new_client_plan_id> |
14036: Invalid client service id
|
<client_service_id>, <custom_rate_client_service_id> |
14039: Invalid client rate schedule id
|
<client_alt_rate_schedule_id> |
14042: Promo Code Expired
|
<promo_cd> |
14045: Promo code's start date is in the future
|
<promo_cd> |
14049: Invalid parent Plan instance no
|
<parent_plan_instance_no> |
14050: Parent Plan instance is required
Additional Comments: A Supplemental Plan was entered without a parent Plan.
|
<parent_plan_instance_no> or<client_parent_plan_instance_id> |
14051: Invalid Plan status for the new Plan
|
<plan_status> |
14063: duplicate Plan instance client defined id.
|
<client_plan_instance_id>, <new_client_plan_id> |
14065:Promo code not allowed for Supplemental Plan
|
<promo_cd> |
14066: Assignment directive cannot be anniversary for Master Plan
|
<assignment_directive> |
14072: Offset interval not allowed for Master Plan assignment.
|
<offset_months> |
14075: Supplemental Plan not eligible under this Plan instance.
|
<new_plan_no> |
14077: Account status not support Plan provisioning.
Additional Comment: The current status of the account does not allow provisioning.
|
<plan_status> |
14078: Master Plan Instance status not support Plan provisioning.
Additional Comments: The current status of the Master Plan does not allow provisioning.
|
<plan_status> |
14079: Supplemental Plan instance status not support Plan provisioning.
|
<plan_status> |
14084: Invalid rate schedule. Please verify start date and end date of provided rate schedule.
|
<alt_rate_schedule_no>, <client_alt_rate_schedule_id> |
14086: Plan Units cannot be below the minimum required units for this child Plan.
|
<plan_units> |
14087: The maximum number of allowable units has been exceeded.
|
|
14098: Invalid proration invoice timing
|
<proration_invoice_timing> |
14102: Invalid parent Plan instance id
|
<resp_client_master_plan_instance_id>, <client_plan_instance_id>, <client_parent_plan_instance_id> |
14108 Plan cannot be queued because parent Plan instance's status is non-provisioned
|
<assignment_directive> |
14109 Plan cannot be queued because Master Plan Instance is in dunning or has completed dunning(i.e., dunning state is 'In Progress' or 'Completed')
|
<assignment_directive> |
14110 The effective date of a queued child Plan assignment must be on or after the effective date of the queued parent Plan assignment
|
<effective_date> |
14111 Plan cannot be queued because parent Plan instance is not in scheduled queue ie. Effective date is not given
|
|
14112 Cannot update/replace/cancel any queued Plan instance which is in queued assignment
|
<client_plan_instance_id> |
14113 The Plan provided is not a valid child of the Plan that will be associated with the parent Plan instance on the effective date provided
|
<new_plan_no> |
14123: Cannot assign child Plan with assignment scope as immediate/anniversary when the parent Plan is in queue
|
|
14124 The effective date of a queued parent Plan assignment must be on or before the effective date of the queued child Plan assignment
|
|
14132: Custom rates cannot be assigned for this non-provisioned status.
|
|
14135: The Responsible Master Plan Instance provided is queued for assignment and not allowed to be used for payment responsibility.
|
|
14136: Offset months must be greater than or equal to 0.
|
|
14137: To permit usage pooling on plans the invoice settings parameter 'Allow MPI Level Usage Pooling' needs enabling.
|
|
14310: Enter a Bill Lag days between +/- Plan's Billing Interval.
Additional Comments: Invalid input: For bill lag days, Enter a number between +billing interval and - billing interval days.
|
|
14311: Enter a Bill Lag days less than/equal to Plan's Billing Interval.
Additional Comments: Invalid input: For bill lag days, Enter a number less than/equal to billing interval days.
|
|
14402: Usage Pooling is not allowed when the Rating Model rates usage on a ‘per record’ basis.
|
|
15001: invalid coupon code
|
<coupon_codes> |
|
|
<coupon_codes> |
15006: Duplicate surcharge number in input
|
<mpi_surcharges>, <mpi_surcharge_no> |
15008: Invalid surcharge rate schedule no
|
<mpi_rate_schedule_no> |
15009: Invalid surcharge number
|
<mpi_surcharges>, <mpi_surcharge_no> |
15010: Coupon code not allowed for Supplemental Plan
|
<coupon_codes> |
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.
|
<coupon_codes> |
15012: Coupon code has already been applied and cannot be used again.
|
<coupon_codes> |
15013: The surcharge provided for this Account or Master Plan does not match its specified Surcharge Applicability Scope, which determines whether the surcharge is available at the account level, Master Plan Instance level or both.
|
<mpi_surcharges>, <mpi_surcharge_no> |
15014: Duplicate Surcharges found.
|
<mpi_surcharge_no> |
15015: Surcharge can't be assigned because its application scope is payment method
|
<mpi_surcharges>, <mpi_surcharge_no> |
18005: Invalid Template number
|
<credit_memo_template>, <rebill_template>, <client_notification_template_group_id> |
18010: Invalid Credit Memo Template number
Additional Comments: The credit memo template must be mapped to the "CM" template class.
|
<credit_memo_template> |
18011: Invalid Rebill Template number
Additional Comments: The rebill template must be mapped to "RB" template class.
|
<rebill_template> |
20026: agreement id OR credit card info is required
Additional Comments: The pay_method_type is "13", the bill_agreement_id is null and cc_num is null.
|
<primary_pay_method_type>, <bill_agreement_id>, <cc_number> |
20031: agreement id is mandatory for this payment method
Additional Comments: The pay_method_type is "29" and the bill_agreement_id is null.
|
<primary_pay_method_type>, <bill_agreement_id> |
23013: Invalid usage threshold applicability
Additional Comments: The usage_threshold_applicability is not in, "ut" or "up".
|
<usage_threshold_applicability> |
25001: failed to calculate taxes
|
|
25020: Illegal characters entered
|
|
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.
Additional Comments: Override_bill_thru_date is before alt_start_date, retroactive_start_date, or effective_date.
|
<override_bill_thru_date>, <alt_start_date>, <retroactive_start_date>, <effective_date> |
25034: When override_bill_thru_date, override_dates_mp_instance_no, or override_dates_client_mp_instance_id is specified, alt_bill_day cannot be used.
|
|
25035: When override_bill_thru_date, override_dates_mp_instance_no, or override_dates_client_mp_instance_id is specified, status_until_alt_start cannot be used (defaults to Inactive).
|
|
25036: When override_bill_thru_date, override_dates_mp_instance_no, or override_dates_client_mp_instance_id is specified, invoicing_option must be configured to be Perform Prorated Invoicing.
|
|
25037: invalid override dates mp instance no or override dates client mp instance id.
|
<override_dates_mp_instance_no>, <override_dates_client_mp_instance_id> |
25039: To align the billing dates of the new Master Plan being assigned with the existing Master Plan Instance on the account, the bill_thru_date of the existing Master Plan Instance must be in the future.
|
|
25040: Effective date is required when an assignment directive is in the future and override bill thru date is used.
|
|
26003: The API execution is not supported because your client parameter Account_EOM_Enabled is set to False. Please contact Aria customer support with questions about the Account_EOM_Enabled client parameter.
|
|
26007: Provided client defined pay method ID does not exist for this account.
|
<existing_client_primary_payment_method_id>, <existing_client_backup_payment_method_id> |
26008: Provided payment_method_id does not exist for this account.
|
<existing_client_primary_payment_method_id>, <existing_client_backup_payment_method_id> |
26010: Invalid billing group number
|
<existing_billing_group_no> |
26012: Invalid client-defined billing group ID.
|
<existing_client_billing_group_id> |
26013: Invalid dunning group number
|
<existing_dunning_group_no> |
26014: Invalid client-defined dunning group ID.
|
<existing_client_def_dunning_group_id> |
26019: Provided primary payment method idx or primary payment method client defined id is invalid
|
<existing_client_primary_payment_method_id> |
26020: Provided secondary payment method idx or secondary payment method client defined id is invalid
|
<existing_client_backup_payment_method_id> |
29005: The contact number provided is invalid for the specified account.
|
<item_dest_contact_no>, <bill_contact_no>, <stmt_contact_no>, <dest_contact_no> |
