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
25-March-2021
15-April-2021
1024 x 768 or higher
This feature enhances Aria's integration with the Sovos tax engine, implementing the Geo code support to calculate taxes for accounts' Ship To, Bill To, Ship From, and Bill From addresses instead of the full addresses.
Unlike traditional postal codes, such as a ZIP code, a Geo Code is not a subjective descriptor, but a series of letters and/or numbers based on the physical location, or latitude and longitude coordinates, of a business, residence, or even point of interest. A Geo Code can provide every location in the world with an internationally unique and permanent "address." Beyond supplying a physical address to residents and businesses located in countries without addressing systems, a common Geo Code standard can greatly facilitate international communications and transactions.
For the Ship From, Bill From, Ship To and Bill To address types, Aria will send the Geo Codes/addresses to the Sovos tax engine in the following order:
The following outputs on the API calls listed below denote the tax address method code used to generate the geocode of the address:
API | Output Parameters |
---|---|
get_acct_billing_group_details_m |
<bill_addr_method_cd> |
get_acct_contacts_m |
<addr_method_cd> |
get_acct_details_all_m | <addr_method_cd> <bill_addr_method_cd> <stmt_addr_method_cd> |
get_acct_hierarchy_details_m | <addr_method_cd> <bill_addr_method_cd> <stmt_addr_method_cd> |
get_acct_payment_methods_and_terms_m | <bill_addr_method_cd> |
refresh_token_from_pmt_processor_m | <bill_addr_method_cd> |
Note: The Geo Code has no expiration once it is generated.
For more information on creating a taxation configuration, please click here.
The new feature "Dun Plan For Non-Electronic Payment Terms Using Cumulative Past Due Balance" introduces an optional, alternate way to dun plan instances based on the cumulative past due balance of all late statements for Payment Terms (Net Terms). You can enable this behavior by setting a new parameter "Dun Plan For Non-Electronic Payment Terms Using Cumulative Past Due Balance" to True. Cumulative past due balance is evaluated by billing group.
Aria’s latest iteration of the Data Feed Web Service includes the Discount Rule object and Chart of Accounts object. In addition, the Non-Subscription Offering (NSO) object reference has been updated to include the <client_sku> field. See the Data Feed Logical Object Model for details.
Aria has created a new Object Query API named get_usage_history_information_m to retrieve all recently uploaded usage for an account. This new API allows you to verify that usage was successfully recorded in Aria.
This feature deprecates the send_arc_threshold_email_m API call, and adds the field <client_acct_id> input as an alternate input for "acct_no" on the following API calls:
The get_acct_coupon_details_m API now returns two new output parameters (under the <discount_rules> array):
Parameter | Description |
---|---|
<total_discount_uses> | This displays the total uses of a discount rule applied to a specific master plan instance (MPI) or a specific account OR an MPI and account depending on how the coupon is applied. |
<remaining_discount_uses> | This displays the number of remaining coupon uses for the specified account and/or MPI under the discount array details for both discount rule/bundle or credit-template-based coupons. |
Note: Both values are available only when the discount rule has a maximum application number of uses specified.
This feature introduces a mechanism to enforce uniqueness of the combination of <client_record_id> and <usage_type_code> on non-discarded usage records loaded via the API call record_usage_m or bulk_record_usage_m. A new Aria client parameter "Unique Client Usage ID," in Configuration > Client Settings > Miscellaneous Settings, defines this uniqueness, and can be set to:
You can now schedule service changes by using the new <service_changes> input in the edit_plan_m API. When you call edit_plan_m, you can specify when to apply the addition or removal of services for both new and existing accounts. The change can be applied on a specific date, before the next batch billing run (for new subscriptions), or on the billing anniversary date (for existing subscriptions).
API Calls | Output Field Changes |
---|---|
|
|
|
|
|
|
Enhanced Rate Schedule Information
create_order_m, update_order_m
This feature enhances the create_order_m and update_order_m API calls to more accurately return rate schedule information. The output fields <nso_rate_schedule_no> and <nso_client_rate_schedule_id> have been deprecated; the output fields <rate_schedule_no> and <client_rate_schedule_id> have been added in the <cart_invoice_line_items> array to identify the rate schedule number of surcharges and NSOs (<rate_schedule_no>) and the client id of the rate schedule for NSOs (<client_rate_schedule_id>).
Enhanced Invoice Information Returns In <line_type> Field
create_order_m, create_order_with_plan_m, update_order_m, get_invoice_details_m
In addition, the API calls create_order_m, update_order_m, and create_order_with_plan_m API calls have been enhanced with the output field <line_type>. This new field will be an object in the <cart_invoice_line_items> array in the outputs of create_order_m and update_order_m; and an object in the <cart_inv_line_items> array in the output of create_order_with_plan_m.
Additional values (7–9 below) for <line_type> will also be returned in the API call get_invoice_details_m.
Note To Developers: For get_invoice_details_m, "order" lines were specified as "1." This enhancement changes the return for orders to "8".
The field <line_type> has the following numeric values corresponding to line types as follows:
This feature adds the following non-mandatory input parameters to the get_all_acct_contracts_m API:
Parameter | Description |
---|---|
<plan_instance_no> | The plan instance number to which a contract has been assigned. |
<client_plan_instance_id> | The client-assigned ID associated with the plan instance to which a contract has been assigned. |
Notes:
1) Either the <plan_instance_no> OR the <client_plan_instance_id> may be used to retrieve specific plan contract details.
2) Contracts that are discarded will not be shown on outputs when either the plan_instance_no OR client_plan_instance_id is used as a filter. All contracts with other statuses (e.g., active, terminated, etc.) will be shown as outputs.
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 |