Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 12.0

Aria6 Release 12.0


Enhancements and fixes to Aria functionality for this release are described below.

Release Date

Production Date


System Requirements

Supported Browsers

  • Firefox 39
  • Chrome 44
  • Internet Explorer 9, 10, 11 

Java Settings

Java 7.0​​

Screen Resolution

1024 x 768 or higher







Application Features

Statement Sending Configuration Page Updates (DEV-8036)

This feature updates the Statement Sending function in the Aria UI. Previously, the function restricted certain zero-balance statements from sending. The layout of the page has changed to better reflect how the options interact with one another

The revised Statement Sending function only restricts statements if at least one of the three zero-amount invoice statement sending parameters is enabled (the main one and either/both of the two sub-selections). You can specify exceptions for certain transaction types by clicking Add Exceptions. If the exceptions are on a zero-balance statement, then the statement is still sent.
Getting Here: Click Configuration > Notification > Statement Sending

statementsending1 12.0.jpg

Check or uncheck the appropriate value based on your business needs, and click Save when you are done.

You can suppress the following types of statements:

  • Non Self-pay child accounts
  • If there is no valid form of payment
  • If the balance is zero

When you check If the Balance is zero, you see additional options that allow you to limit zero-balance statements and/or zero balance invoices. If only zero-balance statements are suppressed, then a zero-balance invoice for an account causes a statement to be generated. If only zero-balance invoices are suppressed, then a zero-balance statement is generated.

You can add exceptions when suppressing zero-balance statements and invoices. The exception checks for the existence of the selected transaction types on zero-balance statements\invoices. Note that the exception takes effect only when the primary settings are suppressing the statement. For example, if a cash credit is applied to an account, then the statement is sent because the cash credit exists. Adding an exception if zero-balance statements/invoices are not suppressed has no effect.

statementsending2 12.0.jpg

Anything other than invoice line items (service charges, discount/service credits, taxes, surcharges) are outside the invoice. So it is possible to have a zero-balance invoice, but not a zero-balance statement for the same account. The breakout between invoice and statement balances ensures backward compatibility with current functionality. Aria recommends that clients use the statement balance setting rather than the invoice balance setting.

Chase Paymentech Salem Recurring Transaction Configuration Options (DEV-7853)

This feature adds two new configuration options for use with the Chase Paymentech payment gateway. You can now specify whether initial and recurring transaction types are automatically set to recurring transaction types that may result in lower transaction fees. This option is available when creating and editing the Chase Paymentech payment gateway, and also when assigning collection groups to this payment gateway.

Getting Here: Click Configuration > Payment Gateways > New > Chase Paymentech

ChasePaymentech 12.0.jpg

When you create or edit a Chase Paymentech payment gateway, or a collection group associated with the payment gateway, you see the following options:

  • Send Transaction Type as Recurring for Initial Request Where Possible: If set to True, the initial transaction for an account when purchasing a recurring service is specified as a recurring transaction. If set to False, then the previous default behavior applies.
  • Send Transaction Type as Recurring for Subsequent Requests: If set to True, all transactions for an account that purchase a recurring service, other than the initial transaction, are specified as a recurring transaction. If set to False, then the previous default behavior applies.

When creating/editing a collection group associated with this payment gateway,  Use Payment Gateway Settings, is added to the list of options, and is the default selection.

Chase Paymentech Salem Support for Level 2 and 3 Data Processing (DEV-8239)

This feature adds level 2 and 3 data processing support to the Chase Paymentech Salem payment gateway. Level 2 data is for determining a card's Affluence, which may influence your marketing initiatives, and Level 3 includes invoice line item details that allow our clients to receive lower transactional fees from credit card processors. To receive these benefits, contact Chase Paymentech Salem to verify that they are enabled at Chase for your merchant accounts.

Deadlock Detected While Uploading Plans to Aria (DEV-8346)

This feature addresses an issue that caused an error when changing a large number of future plans. When modifying a plan using the edit_plan_m API, while the plan was being modified by an executing batch process, the update would stop before being completed. This has been corrected.

Default Rate Schedules for All Currencies in Staging Environments (DEV-8389)

This feature adds default rate schedules for all currencies to all staging environments. Previously, only some currencies had default rate schedules in staging environments, but Aria is now ensuring that all currencies have default rate schedules. This eliminates a possible error condition in staging environments that had prevented an account from being created.

Application Fixes

  • Unapplied payment not re-applying to open charges (TICKET-12612)
  • Client Bundle ID and Description not displayed fully in list page (TICKET-14896)
  • UI Credit screen was showing "Unknown" instead of custom credit reason (TICKET-15206)
  • Non-recurring master plan was generated during recurring billing (TICKET-15219)
  • Supplemental Field Type Date was not honoring Date Format Mask client setting on statement template (TICKET-15254)
  • UI format issues (TICKET-15307)

API Features

Updated Handling of Countries with USPS for Avalara (DEV-8112)

This feature updates the handling of country codes for Avalara. If any country listed below is specified as the country code in the Aria contact information, Aria updates the country code to US and adds the specific country code as the state prior to sending the information to the Avalara tax service.

This feature applies to the following country codes:

  • American Samoa (AS)
  • Guam (GU)
  • Marshall Islands (MH)
  • Micronesia (FM)
  • Northern Marianas (MP)
  • Palau (PU)
  • Virgin Islands (VI) - this is US Virgin Islands

For example, if the country code passed is 'GU' (Guam) in the contact, it is updated to country code as 'US' and state as 'GU' when sending the request to the Avalara tax engine. Note that the original country code is still included in the database tables.

API Fixes

  • Coupon not applied to invoice (TICKET-14985)

WSDL File Locations 

Stage Current

US https://secure.current.stage.ariasystems.net/api/Advanced/wsdl/12.0/complete-doc_literal_wrapped.wsdl
EUR None

Stage Future

US https://secure.future.stage.ariasystems.net/api/Advanced/wsdl/12.0/complete-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/Advanced/wsdl/12.0/complete-doc_literal_wrapped.wsdl


US https://secure.ariasystems.net/api/Advanced/wsdl/12.0/complete-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/Advanced/wsdl/12.0/complete-doc_literal_wrapped.wsdl
Last modified


This page has no custom tags.


This page has no classifications.