Release 34

• Recurring services are now billed as expected on the anniversary invoices, even when there are queued custom rates available for other services on the anniversary invoice. (TICKET-18003)

• Electronic payments are now re-applied to an invoice during credit memo application of the invoice. This will ensure the payment is applied to other open items on the invoice. (TICKET-18147)

• If a Master Plan Instance (MPI) balance is paid in full via a credit memo application applied to an invoice with an associated electronic payment, that MPI moves out of a Dunning status, and out of the Dunning process. Enhanced logic auto-applies such un-applied payments to any open charges. Previously, such an MPI would remain in a Dunning status. (TICKET-18182)
• Aria has improved contract behavior with the following changes: (TICKET-18190) Previously, invalid service numbers for contract rollovers caused the invoice batch job to return a "failed to calculate taxes" error.
  • Added validation to the API calls create_instance_contract_m and modify_instance_contract_m to ensure valid service numbers are passed when specifying custom rates for a rollover plan
  • Added logic to fail invoice generation if there is an invalid service number for a custom rollover rate.
• A General, Price Change, Invoice-Based or Cancelation type credit memo can now be created successfully against 1000 or more master plan and/or supplemental plan instances within an account (Accounts > Search > [Account Number] > Payments & Credits > Credit Memos > New). (TICKET-18215)
• Statement contact information is now populating as expected in Email Templates when statement replacement strings are used. (TICKET-18264)
• Local time zone is now correctly displayed inside the details of the batch log files (Configuration >  Audit Logs > Batch Processes > [Details of a batch log]). (TICKET-18280)
• The Aria invoicer batch job now completes successfully for an account when usage service charges exist related to a plan instance from which that usage service was removed in the middle of a billing period. Previously, the invoicer would fail with a "Could not create invoice due to a processing error" message. (TICKET-18285)
• Decimal values are now supported while updating custom rates in European format. (TICKET-18290)
• The services types that you specified when you created services and the billing intervals that you specified when you created plans are now reflected in: (TICKET-18309)
  • The Usage Based and Recurring Arrears service types service types that appear on the Add New Plan screen for an account; and
  • The Recurring and Usage billing intervals that appear on the Master Plan Instance (MPI) and Supplemental Plan Instance (SPI) Detail, Queued MPI and SPI Detail, and Execute Queued PI Detail screens.
• The pending invoices discard message has been updated to avoid confusion when you discard pending invoices with usage. The new message will list the number of pending invoices being discarded, and discarded usage records are excluded from invoicing and usage reports. (TICKET-18348)

• The "invalid plan instance number" error message is no longer returned when you call the edit_acct_plan_queued_changes_m API and pass in a <client_acct_id>. (TICKET-16582)
• The field <currency_cd> has been deprecated and removed from get_acct_coupon_details_m API because this field does not apply to coupons. (TICKET-17935)
• Aria has improved contract behaviour with the following changes: (TICKET-18190)
  • Added validation to the API calls create_instance_contract_m and modify_instance_contract_m to ensure valid service numbers are passed when specifying custom rates for a rollover plan
  • Added logic to fail invoice generation if there is an invalid service number for a custom rollover rate.
  Previously, invalid service numbers for contract rollovers caused the invoice batch job to return a "failed to calculate taxes" error.
• When update_acct_plan_multi_m is run to create deferred charges for multiple plan instances with varying anniversary dates, the deferred charges are now correctly invoiced on the anniversary dates for all plan instances. Also, when deferred charges are created for a supplemental plan instance/master plan instance and the billing group for the master plan instance is changed, the deferred charges are invoiced on the next anniversary against the new billing group. (TICKET-18238)
• Aria has improved the API call get_acct_surcharges_m by updating the underlying query. Previously, the call would return a "null" response. (TICKET-18253)
• The update_acct_plan_status_m API has been updated so unexpected errors no longer occur if <client_acct_id> is provided during the requested update instead of <acct_no>. (TICKET-18291)
• An unexpected error no longer occurs when you: (TICKET-18298):
  • Call the update_acct_plan_multi_m API and pass true into the <invoice_unbilled_usage> field; and
  • You try to replace a master plan (MP1) and supplemental plan (SP1) assignment with a new master plan (MP2) and supplemental plan (SP2) assignment; and
  • MP1 and MP2 both have SP1 and SP2 configured as supplemental plans; and
  • All four plans mentioned above have one usage service, one recurring service, and one recurring arrears service.
• The API update_acct_plan_multi_m now completes as expected when replacing, updating, assigning and canceling actions in the same call for plans with recurring arrears services. (TICKET-18313)
• Aria has improved the API call update_acct_multi_plan_m so, when specifying custom rates and <do_write>=false (for preview purposes), plans are not committed to the specified account. Previously, plans with custom rates were created in an Inactive status. (TICKET-18337)

Stage Current

Stage Future

Production

Stage Current

Stage Future

Production