Overview
Enhancements and fixes to Aria functionality for this release are described below.
Overview
Enhancements and fixes to Aria functionality for this release are described below.
Release Date
Stage Future Release Date
3-December-2021
Production Release Date
13-January-2022
System Requirements
Supported Browsers
Screen Resolution
1024 x 768 or higher
Release 40 Contents
A new client parameter, Proration on Credit Options, has been added to prevent 1-cent increases in prorated amounts after mid-period plan changes using selected Aria APIs including, for example, update_acct_plan_multi_m. The options govern whether or not the unrounded (1) or rounded amount (2) is used during prorated charge/credit calculations. By default, this option is set to use the rounded amount (2) for backward compatibility. To set in the UI, go to Configuration > Billing > Invoice Settings > Proration on credit options. It is strongly advised that this parameter should be set permanently based on a your preferred billing scheme for accounting purposes.
The Ingenico payment gateway is now renamed to Worldline within Aria for payment gateways and collection groups (Configuration > Payments > [Payment Gateways/Collection Groups] to acknowledge the integration of Ingenico with the largest European payment services company and the fourth-largest worldwide.
Click here to learn more about the Worldline payment gateway.
Aria has enhanced the Billing Group History screen (Accounts > [search for an account] > Plans > Billing Groups) to display removal of the payment method sequence number. In addition, validation has been introduced to not allow the same payment method sequence number for the account's primary and secondary pay methods while creating/updating a billing group and assigning a master plan.
Also, the following error message will now appear to avoid setting the same pay method sequence number and payment details for both a primary and secondary payment method:
"Both Primary and Secondary payment methods cannot be the same payment source."
The following Account Updater fields for the Chase Paymentech payment gateway are now honored at the collection group level as part of the Aria integration to support international divisions for clients (Configuration > Payments > Collection Groups):
Click here to learn more about the Chase Paymentech payment gateway.
Aria enhanced our Account Updater feature with Chase Paymentech by allowing configurable actions depending upon your business practices. A new Chase AU Response Code Handler Settings field called Response Code Q Action (with this response code matched to an internal Aria setting) has been added at the payment gateway (Configuration > Payments > Payment Gateways > Gateway Options) and collection group (Configuration > Payments > Collection Groups > Collection Group Options) levels.
The following selections are available at this field:
Selection | Description |
---|---|
Use Payment Gateway Setting | Honored at the Collection Group level. |
No Action Required | Default selection. |
Suspend the Payment Method | This will be honored for existing clients using this selection. |
Click here for more information on the Chase Paymentech payment gateway.
In Aria Billing Cloud, if there are any 1 cent differences (+/-) when 100 percent of service credits are applied on tax inclusive services during invoice generation, those differences will be adjusted to match the original invoice amount. This enhancement works along with Aria’s line-level invoice rounding implementation and will adjust the $0.01 difference after you set the new
client parameter Force Tax Amount on Full Credit, which works in conjunction with the existing parameters Aria Internal Tax Rounding Preference and Aria Internal Tax Rounding Method. The new parameter is an internal parameter, so it will not be displayed in the UI. To enable this capability in your Aria instance, contact Aria Support.
Advanced account searches in the UI now support new "Email Address" search options under Account Contact Fields and Billing Contact Fields sections of the Search Field dropdown. To access in the Aria UI, go to the Accounts > Search > Search | Advanced Search tab. There is a 50-character limit on email fields.
Click here to learn more about searching for accounts in the UI.
Internal tax engines were enhanced to correctly process system-generated service credits for tax inclusive plans. To prevent issues, the tax inclusive split for service credit that was occurring during this process was stopped. This enhancement impacts A6 and Aria Billing Cloud tax inclusive plans and internal tax engines.
A tool tip has been added (Analytics and Reporting > Reports > Published Reports) indicating that published reports will be available for viewing until the Available Until column header date, with that date included in a date range specified for automatic report deletion. This tool tip adds explanation as to why reports may not be deleted on the exact specified deletion day.
Click here for more information on viewing published reports in Aria.
Aria has added a new client parameter to automatically honor invoicing behavior (including bill lag days) when resetting billing dates and changing the master plan instance status from non-billable to billable (Configuration > Billing > Invoice Settings titled Invoicing Behavior For The Stack When MPI is changed from Non-Billable to Billable). When the parameter values is set as "0 - Do not modify", Aria will not modify the invoicing behavior. If the setting is "1 - Treat next invoice after bill dates reset as initial invoice," then, while resetting the billing dates and changing the status from non-billable to billable, Aria will modify the invoicing behavior; that is, the next anniversary invoice will honor any activation fees as well as bill lag days.
Learn more about changing an invoicing setting from here.
Invoice batch processing has been improved because the procedure to deactivate accounts that were cancelled/suspended was optimized to ignore the status updates of previously deactivated accounts, which had been creating longer query times. This enhancement does not affect functionality.
Aria now automatically generates zero-dollar balance transfer transactions (0.00) from a child account to an account with parent-pay responsibility whenever there is no unpaid balance amount on the invoice for the child MPI. This increases the efficiency of invoice processing for accounts with large numbers of balance transfer transactions.
Click here for more information on generating statements and invoices within Aria.
When some payments are sent to payment processors, the processor honors multiple decimal places for the affected currency used for payment during the collection. As an example, a payment processor honors two decimal places for the IDR (Indonesian Rupiah), even though the currency does not have decimal places. An issue arose where the payment processor accepted a payment with this currency type as having two decimals per ISO (16.40), which the processor interpreted as 100 times the intended amount ($1,640).
To resolve this, Aria has introduced a field called Currency Scale in the Currencies screen (Configuration > Billing > Currencies). This sets the currency scale for the respective currency, rounding the transaction based on the scale. The allowed values are Null or Empty (default), 0, 2, 3, and 4 decimal places. If the drop-down list is empty, the default currency scale for this currency defined within Aria will be used.
Note: This applies only to the Indonesian Rupiah currency type.
To provide additional granularity in service charges, the following service type values are now returned in Aria APIs noted below:
Note To Developers: Previously, "order" lines were specified as "1" for the API calls listed below. This enhancement changes the return for orders to "8".
This applies to the following APIs and associated output fields:
API | Field |
---|---|
assign_acct_plan_m | <line_type> (<acct_plan_line_items> array) |
cancel_acct_plan_m | <line_type> (<acct_plan_line_items> array) |
create_order_m | <line_type> (<cart_invoice_line_items> array) |
create_order_with_plan_m | <line_type> (<cart_inv_line_items> array) |
modify_acct_plan_unit_instances_m | <line_type> (<invoice_line_items> array) |
replace_acct_plan_m | <line_type> (<acct_plan_line_items> array) |
update_acct_plan_m | <line_type> (<acct_plan_line_items> array) |
update_acct_plan_unit_instance_m | <line_type> (<invoice_line_items> array) |
update_order_m | <line_type> (<cart_invoice_line_items> array) |
The Ingenico payment gateway is now renamed to Worldline within Aria for payment gateways and collection groups to acknowledge the integration of Ingenico with the largest European payment services company and the fourth-largest worldwide. This impacts the <processor_id> field in the record_alternative_payment_m API.
Click here to learn more about the Worldline payment gateway.
The Aria UI now displays the removal of the payment method sequence number using the remove_acct_payment_method_m API. In addition, validation has been introduced to not allow the same pay method sequence number for the primary and secondary pay methods while creating/updating a billing group and assigning a master plan from the following APIs:
Also, the following error message will now appear to avoid setting the same pay method sequence number and payment details for both a primary and secondary payment method:
Error Code | Description |
---|---|
6055 | Both Primary and Secondary payment methods cannot be the same payment source. |
The Object Query API get_account_details_m now supports new "email" and "bill_email" query parameters. These parameters will allow you to search for accounts with the account email address and any listed billing email addresses. There is a 50-character limit on email fields.
For Aria Billing Cloud, the update_acct_plan_mult_m API process execution time has been optimized when assigning plans with custom rates. This was accomplished by focusing the query only on relevant table conditions data, in the "ACCT_RATES" view.
None
Stage Current
US | https://secure.current.stage.ariasys...l_wrapped.wsdl |
EUR | None |
AUS | https://secure.current.stage.aus.ari...l_wrapped.wsdl |
Stage Future
US | https://secure.future.stage.ariasyst...l_wrapped.wsdl |
EUR | https://secure.future.stage.cph.aria...l_wrapped.wsdl |
AUS | https://secure.future.stage.aus.aria...l_wrapped.wsdl |
Production
US | https://secure.ariasystems.net/api/A...l_wrapped.wsdl |
EUR | https://secure.prod.cph.ariasystems....l_wrapped.wsdl |
AUS | https://secure.prod.aus.ariasystems....l_wrapped.wsdl |
Stage Current
US | https://secure.current.stage.ariasys...l_wrapped.wsdl |
EUR | None |
AUS | https://secure.current.stage.aus.ari...l_wrapped.wsdl |
Stage Future
US | https://secure.future.stage.ariasyst...l_wrapped.wsdl |
EUR | https://secure.future.stage.cph.aria...l_wrapped.wsdl |
AUS | https://secure.future.stage.aus.aria...l_wrapped.wsdl |
Production
US | https://secure.ariasystems.net/api/A...l_wrapped.wsdl |
EUR | https://secure.prod.cph.ariasystems....l_wrapped.wsdl |
AUS | https://secure.prod.aus.ariasystems....l_wrapped.wsdl |