Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!

 

Home > User Documentation > Aria6 Release Notes > Aria6 Release 6.27

Aria6 Release 6.27

Release Date

Production

11/19/2014

Aria6 System Requirements

Supported Browsers  

  •  Internet Explorer 9, 10, 11
  •  Firefox 32
  • Chrome 38

Java Settings

Java 7.0​​

Screen Resolution

1024 x 768 or higher

Aria6 Features

Tax Support for Canadian Provinces that Collect Harmonized Sales Tax (DEV-3568)

Aria now supports the collection of the Harmonized Sales Tax (HST) from clients in Canadian provinces where these taxes are levied. This functionality is available only for taxation configurations that use the Aria tax method.

Canadian provinces collect consumption taxes in various ways. Some provinces collect only the Goods and Services Tax (GST), which is the Canadian national sales tax. Some provinces also collect a separate Provincial Sales Tax (PST) in addition to the GST, and other provinces combine the GST and PST into a single tax line item, known as the Harmonized Sales Tax (HST).

The Harmonized Sales Tax is in effect in five Canadian provinces, including:

  • New Brunswick
  • Newfoundland and Labrador
  • Nova Scotia
  • Ontario
  • Prince Edward Island

To access this option in Aria:

  1. Navigate to Configuration > Integrations > Taxation Configuration.
  2. Select an existing taxation configuration that uses the Aria tax method, or create a new taxation configuration that uses the Aria tax method.
  3. Click the Internal Values tab.
  4. Select the Harmonized Sales Tax option from the Service drop-down.
  5. Upon selecting the Harmonized Sales Tax option, a checkbox titled Override Federal Tax Rate appears, allowing you to override the federal tax rate for a given jurisdiction with the Harmonized Sales Tax.

Create Prorated Invoice on Mid-Billing-Period Upgrade Without Resetting Bill Dates (DEV-3593)

With this enhancement, when changes to an account's status, or to the plans associated with the account, are applied in the middle of a billing-period, and billing dates are reset, you can preserve the previously defined anniversary date.

In addition to the current option of resetting billing date to the date of the status change or plan change, you can also reset the billing date to the existing anniversary date. A previously defined anniversary date is not lost.

For example, accounts are often created in a “non-billable” account status so that trial services can be provided to customers. When the account moves into “billable status” in the middle of a billing period, you can reset the billing dates to either the account status change date, or to the current anniversary date.

Resetting the billing date to the current anniversary date generates a prorated invoice that covers the period from the date when the status change from “non-billable” to “billable” happens, to the pre-defined billing anniversary date. The next regular recurring invoice is generated on the next billing anniversary date.

Send <client_plan_id> Field with Account Status Change Event Data (DEV-3638)

Previously, when an account's status changed, only the system-assigned plan ID was returned in the event notification email. Now, the client-defined plan identifier is returned as well.

Support Tokenized Credit Cards Through Direct Post (DEV-3657)

Aria now supports the use of tokenized credit cards, which provide enhanced security for credit card-based transactions. A new field, Save Credit Card as Token, has been added to the Create New Direct Post screen. Selecting Yes from the drop-down saves the credit card as a token.

Save Prompt Displays Upon Clicking Close Button (DEV-3469)

A message now displays that prompts users to save or discard any unsaved changes made to the following screens in Aria:

  • Most Configuration > Billing screens
  • All Configuration > Integrations screens
  • All Configuration > Security screens
  • All Configuration > Payments screens
  • All Configuration > GL Code Mapping screens
  • Channel Management Channel Types
  • Channel ManagementChannel Templates > Billing screens

Extract Account and Transaction Objects Separately (DEV-3680)

Previously, when data regarding any Aria transaction was passed to an external application, the account object and any other relevant objects were extracted simultaneously. Now, the account object and other objects related to a specific transaction are extracted in separate operations. This ensures that relevant data is supplied to external applications more quickly.

Create Additional Statement Recipients in Account Creation (DEV-3770)

Account Creation templates can now contain more than one recipient for statements sent via email. A comma delimited list of email addresses can be submitted when a new account is created. The list is validated and an error message is returned if an improperly formed email address is found. The user is prompted to correct the email address errors and resubmit the list.

Aria6 Fixes  

  • Define Report Audience Was Not Working as Expected (TICKET-3748)
  • Retry Logic for Failed Transactions (TICKET-3994)
  • Unable to Save Default Country as Part of Account Creation Template (TICKET-4554)
  • Text and Radio Buttons Misaligned When Create Contract Screens are Resized (TICKET-4578)
  • Multiple Default Rate Schedules Can Be Selected for the Same Currency (TICKET-4588)
  • Creating Duplicate Product Field Does Not Return Error (TICKET-4601)
  • Promo Codes Not Working as Required (TICKET-4627)
  • Payflow Pro Does Not Support $0 Dollar Pre-authorizations for Discover Cards (TICKET-4628)
  • Oracle Errors When Creating ACCT_TRANS_APPLICATION Record (TICKET-4641)
  • Batch Log Details Not Available in UI (TICKET-4668)
  • User Name Details Not Displayed in "Save Successful" Popup Message (TICKET-4706)
  • Validation in Account's Client Defined Fields (TICKET-4774)
  • DataTables Warning Message (TICKET-4788)
  • Export Status Shows Success When Export Summary Fails (TICKET-4890)
You must to post a comment.
Last modified
12:02, 21 Sep 2015

Tags

This page has no custom tags.

Classifications

This page has no classifications.