Home > Aria Crescendo Documentation > Aria Release Notes > Release 16

Release 16

Application Features

Send Statements at the Billing Group Level (DEV-6737)

You can now use Aria to send statements associated with an account's billing group(s) to multiple cc (carbon copy) and/or bcc (blind carbon copy) recipients. In addition, for ease of use, there are now separate boxes for you to enter cc and bcc recipients of statements at the account level. You can also use APIs to specify cc and/or bcc recipients of statements as described in the API Features section.

Performance Improvements for Account / Plan Access via the Account Overview (DEV-8527)

Performance improvements, including database handling queries, and UI changes, have been implemented to reduce response times for the retrieval of account, plan, and transaction detail via the Account Overview screen.

Getting Here:   Accounts > Search > Account Overview

Account Overview - View All Plans.jpg

To improve overall response time when accessing accounts having a large number of Master Plan Instances, the "Balance Details" section on the Account Overview screen has been modified to limit the display to ten (10) Master Plan Instances. 

The column headings and data in this view have also been modified to now include Master Plan Name, Master Plan Instance ID, Full Balance, Dunning State (new), and Master Plan Status (new).

Note: Current Balance Due, and Days Past Due have been removed from this view in order to                   optimize performance when accessing accounts having a large number of Master Plan           Instances. These fields are available on the Master Plan Instance's Plan Details screen. 

Click on any Master Plan Name from this view to access the Master Plan Instance's Plan Details screen.

A "View All Plans" link has also been added to this section in the Account Overview. The number in (parenthesis) next to this link indicates the total number of Master Plan Instances subscribed to by the account. Clicking on this link accesses the account's Plans screen. 

  1. Click on the View All Plans link 

Plans Screen.jpg

The account's Plans screen is displayed.

The Plans view displays all Master Plan Instances subscribed to by the account, grouped by Billing Group assignment, including the Billing Group's primary payment method, and each Master Plan Instance's Plan Instance ID, Plan Name, Client Defined Identifier, Units, and Status.

Note: No changes have been made to this screen.

  1. Click on any Master Plan Instance's Plan Instance ID to view the Master Plan Instance's Plan Details screen.

Plan Details Screen.jpg

The Master Plan Instance's Plan Detail screen is displayed. 

The Current Balance Due, and Days Past Due fields can be found in the shaded gray area to the right of the screen.

Note: No changes have been made to this screen.

  1. Click on the Plans tab to return to the account's Plans screen.

Credit Memo Creation In UI: Enhanced Scalability (DEV-8634)

The performance of credit memo creation in the Aria UI has been enhanced. Now, credit memos with a large number of line items are possible without timeouts.

Deprecate "valid_tlds" Table for Outgoing Emails (DEV-8808)

Aria previously validated the top-level domains of email addresses against a database table named "valid_tlds" before sending automatic email notifications to customers. We deprecated this database table and no longer filter automatic emails using its data.

Application Fixes 

  • When you delete a scheduled plan cancellation, the plan is now returned to the active status and is no longer listed as "Pending Cancellation" on the Future Plan Changes screen. (TICKET-14433)
  • Adding a new recurring in arrears service to an existing plan, while removing an existing recurring service to the same plan, now results in the appropriate invoice charges being reflected on an account’s invoice. (TICKET-15688)
  • Usage periods are now calculated correctly on invoices when a) Allow Negative Bill Lag Days to Extend Beyond One Bill Cycle is set to true and b) Automatically Rate Un-rated Usage Records at Load Time is set to false. (TICKET-15693)
  • When you have a discount rule that results in a $0 credit, the $0 credit no longer appears on statements as either a credit or a charge. (TICKET-15887)
  • The non-viable option to discard already-billed usage, or usage on a pending invoice, has been removed from the UI when clicking on a usage record within the displayed invoice. (TICKET-15924)
  • Charges on an invoice now reflect all applicable fees for the currently-assigned plans and services when: a) you remove a service from a plan and b) you add a new service to a plan. (TICKET-15991)
  • The payload for provisioning event "Account Service Plan Contract Expired" (in the Accounts and Master Plan Instances Event Group, Event 733) now only includes information about the contract that is expiring, rather than all expired contracts for the account. (TICKET-16008)
  • You no longer encounter an error when you import data from one client to another. (TICKET-16078)
  • ​An account’s master plan status is now correctly displayed on all Plan-detail screens within the UI when a master plan is assigned to an account in a pending activation status. (TICKET-16093)
  • An error no longer occurs when you navigate between pages in an account's Transactions tab. (TICKET-16094)
  • When using BillSoft as your tax engine, voiding an invoice with tax line items no longer results in an error indicating "OriginationPCode must be set!" (TICKET-16210)
  • Product plan instance fields, and their values are now correctly displayed on statements honoring the field's "Display on Statements" setting. (TICKET-16233) 
  • Statement contact is now displayed in credit note email notification instead of the account contact if configured, when creating a cash credit via the UI using the cash credit’s “Services (invoice line-items)” with/without MPI or "Invoices and other account-level charges". (TICKET-16252)
  • Creating an order that should be invoiced immediately triggers the "Invoice Created" event and not the "Pending Invoice Created" event, as expected. (TICKET-16258)
  • When you remove a plan using the "De-assign in Future" option, then go to the Future Plan Changes screen and click Execute, the plan name is now displayed. (TICKET-16374)
  • Within the Aria UI, on the Plan Instance Supp Fields screen, you can now successfully enter and save a value that has more than 300 characters. (TICKET-16375)

API Features

Send Statements to CC and BCC Recipients (DEV-6737)

You can now use APIs to specify multiple cc (carbon copy) and/or bcc (blind carbon copy) recipients of statements. This can be done at the account and/or billing group level as described in the table below. In addition, you can obtain the list of recipients of statements as described below:

APIs New Inputs or Outputs

Use these new inputs to specify cc and/or bcc recipients of an account holder's statements:

  • stmt_email_list_cc
  • stmt_email_list_bcc

Use these new inputs to specify cc and/or bcc recipients of the statements associated with a specified billing group:

  • stmt_email_list_cc
  • stmt_email_list_bcc

Use these new outputs to obtain the list of current cc and bcc recipients of an account holder's statements:

  • acct_email_list_cc
  • acct_email_list_bcc

Use these new outputs to obtain the list of current cc and bcc recipients of statements associated with an account holder's billing group(s):

  • stmt_email_list_cc
  • stmt_email_list_bcc

Additional Fraud Protection Options Available (DEV-8818)

  1. You can now apply the fraud settings from the payment gateway or collection group level when you use APIs to perform fraud filtering and/or fraud scoring. To do so, pass -1 into any of the following fields in the validate_acct_fraud_scoring_m API or the APIs listed under number 2 below:
  • fraud_filtering_enabled
  • change_status_on_fraud_filtering_failure
  • change_status_on_fraud_filtering_review
  • fraud_scoring_enabled
  • change_status_on_fraud_scoring_failure
  • change_status_on_fraud_scoring_review

Note: This feature is available only in APIs and not in a Direct Post configuration.


  1. You can now specify fraud filtering options by passing key-value pairs into the fraud_control_fields array as described in the documentation for the following APIs:

Note: Fraud protection features are available to you if your payment gateway supports them.  

New API Added to Update Account Invoice (DEV-8843)

A new API, update_acct_invoice_m is now available to update the custom status, and be able to add custom notes to an invoice. This is often used when invoice data is fed to a downstream application.

New Output Array in gen_invoice_m (DEV-8931)

In the gen_invoice_m API, the out_invoices output array has been deprecated and replaced with the new out_invoices_list array. This ensures that errors no longer occur when you use Swagger to generate code for calling the gen_invoice_m API.

New APIs for Adding/Editing Rate Schedules on a Plan (DEV-8941)

Two(2) new Admintools APIs, add_rate_schedule_on_plan_m, and edit_rate_schedule_on_plan_m are now available to add, and edit a rate schedule on an existing plan.

API Fixes 

  • When you cancel a plan then call the get_acct_plans_all_m API, any applicable cancellation fee is now returned in the early_cancel_fee field. (TICKET-10723) 
  • When calling update_payment_method_m, the payment method name, client-defined id, and description are now updated as expected. (TICKET-15758) 
  • XML Exception error: Unexpected element: CDATA was being displayed in authorize_electronic_payment_m API response instead of in the correct XML format (TICKET-16091)
  • For REST calls: The currency_cd field for create_inventory_item_m is no longer case sensitive (e.g., both "usd" and "USD" are valid inputs for currency_cd); and, the error message returned when sending an invalid currency code is now accurate. (TICKET-16101)
  • An invoice for recurring fees is no longer generated when using update_acct_plan_multi_m to assign an account a new plan instance having a retroactive_start_date, and invoicing_option = "4" (no invoice). (TICKET-16167)
  • A new field, new_client_payment_method_id, has been added to update_payment_method_m. (TICKET-16284) 
  • Future plan assignment:
  1. An error no longer occurs when you call the assign_acct_plan_m or update_acct_plan_multi_m API and you:
  • Pass in a future effective_date;
  • Pass in an override_bill_thru_date that is more than one billing cycle away from the API run date; and
  • The period between the effective_date and the override_bill_thru_date is within one billing cycle.

    Example: If a plan's billing cycle is 1 year and you call the assign_acct_plan_m API on 3/1/2019, pass in an effective_date of 4/1/2019 and an override_bill_thru_date of  3/29/2020, an error will not occur. This is because 3/29/2020 is within 1 year of 4/1/2019.
  1. Aria now returns the following new/updated error codes when you call the assign_acct_plan_m or update_acct_plan_multi_m API:
    New or Updated? Error Code Error Message
    Updated (effective_date added to the error message) 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.
    New 25040 Effective date is required when an assignment directive is in the future and override bill thru date is used.

WSDL File Locations

Stage Current

US https://secure.current.stage.ariasystems.net/api/Advanced/wsdl/16/complete_m-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/Advanced/wsdl/16/complete_m-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/Advanced/wsdl/16/complete_m-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/Advanced/wsdl/16/complete_m-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/Advanced/wsdl/16/complete_m-doc_literal_wrapped.wsdl


US https://secure.ariasystems.net/api/Advanced/wsdl/16/complete_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/Advanced/wsdl/16/complete_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/Advanced/wsdl/16/complete_m-doc_literal_wrapped.wsdl

Object Query WSDL Files

Stage Current

US https://secure.current.stage.ariasystems.net/api/AriaQuery/wsdl/16/integration_services_m-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/AriaQuery/wsdl/16/integration_services_m-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/AriaQuery/wsdl/16/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/AriaQuery/wsdl/16/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/AriaQuery/wsdl/16/integration_services_m-doc_literal_wrapped.wsdl


US https://secure.ariasystems.net/api/AriaQuery/wsdl/16/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/AriaQuery/wsdl/16/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/AriaQuery/wsdl/16/integration_services_m-doc_literal_wrapped.wsdl
Last modified


This page has no custom tags.


This page has no classifications.