Release 69

New Events for Non-Subscription Offering Rate Schedule Changes (DEV-11535)

This enhancement adds new event notifications for Non-subscription Offering (NSO) rate schedule changes, ensuring downstream systems receive timely updates when NSO pricing is updated. Aria has added two new events, "Non-subscription Offering Rate Schedule Added" (EVENT_ID 1229) and "Non-subscription Offering Rate Schedule Modified" (EVENT_ID 1230), under the Products event group. These events fire when rate schedules are added or modified on an existing NSO, including changes to rate schedule details, rate tiers, or the default rate schedule, and can be combined into a provisioning sequence when multiple actions occur in one call.

Four New Events Supporting Service Credits (DEV-11838)

This feature adds four new Financial Transactions event notifications for the full lifecycle of service credits, improving downstream integrations and monitoring of credit activity. These events now fire when a service credit is:

1. created (event 958),
2. cancelled (event 959), 
3. consumed (event 960), or 
4. unconsumed (event 961). 

To take advantage of these new events, you must update your Financial Transactions event class to version 3.6 or later.

New Client Parameter for Single Account Notifications for Multi-Plan Contracts (DEV-11839)

This feature adds a new client parameter in Configuration > Notifications > Notification Settings, "Send Single Contract Pending Expiry/Renewal Notification per Multi-plan Contract," that allows you to send a single contract expiry/renewal notification per multi-plan contract instead of one notification per master plan instance.

When set to "true," Aria now triggers only one prior contract expiry notification for the contract, reducing redundant emails while preserving the existing per-MPI behavior as the default. The notification logic also respects billing group configuration, sending to the account contact when multiple billing groups are present, or following the existing statement > billing > account precedence when all MPIs share a billing group. In addition, Aria has improved the expiry notification batch performance.

CCP Generate Statement Page Updates (DEV-12105)

You can now manually generate account statements directly from the Transactions > Statements page in CCP. This feature allows you to create immediate statements for specific subscriptions and optionally email them to the customer in real-time.

Additionally, the Statements page has been enhanced with previews of the next scheduled statement before it is formally generated. This feature facilitates verification of upcoming charges and balance details without the need to commit a permanent statement record or emailing the customer.

CCP Account > Subscription > Details > Create Subscription Updates (DEV-12110)

The Add New Subscription drawer has been updated to streamline the subscription assignment process on the account level. This new implementation includes 4 steps: Details, Options, Billing Groups, and Add-Ons. The following has been implemented at each step:

• The Add New Subscription wizard within the Options step allows you to define and apply custom pricing tiers instead of relying solely on default existing plans.
• A new Services tab has been implemented within the Options step which allows you to view all services associated with the subscription, modify service locations, and assign specific contacts to individual services.
• Inline billing group creation is supported within the Billing Groups step. Allowing you to switch between selecting an existing billing group or configuring a completely new one directly within the subscription wizard. This new form supports both standard Payment Methods (e.g., Credit Card) and Net Terms configurations without requiring separate API calls.
• The Add-ons step allows you to view the list of add-ons pre-associated with a selected plan and perform updates to specific fields.

CCP New Service Credit Drawer Improvements (DEV-12113)

Service Credit creation from the Transactions > Credits > Service Credits tab > Create New Service Credit drawer has been improved to provide greater flexibility allowing you to configure recurring credits and define granular application scopes (e.g. specific service types) while storing your user preferences.

Along with this Service Credit update, two advanced Application Scope options have been introduced. These new scopes provide granular control, allowing users to apply credits to specifically selected subscriptions and services either from the customer's active portfolio or directly from the product catalog.

Additionally, we have integrated a Service Outage Credit Calculator directly into the New Service Credit drawer which automatically calculates the appropriate prorated credit amount based on the precise duration of an outage and the customer's recurring fees.

New Billie Configuration Section In Client Settings (DEV-12148)

A new module has been added to Aria Billing under Configuration > Client Settings > Billie Configuration. This new module allows you to configure options for Billie Connect. The module is enabled with the Billie Client Section (32) and can be further configured at the role level to allow read/edit access. This Billie Client Section displays parameters that you can change, such as Agent Configurations for Specialty Agents or general Billie Configuration parameters.

Payment Plans Phase 4 (DEV-12218)

Phase 4 of Payment Plans introduces support for configuring a custom dunning start step for payment plans and richer failed collection event notification payloads.

You can now select "Custom Dunning Step" and specify a value for the client parameter "Dunning Option for Payment Plans" at Configuration > Payments > Payment Settings. Previously, you could only take advantage of this option via a Customer Support request. This setting allows you to specify the starting dunning step for a missed payment plan relative to the invoice due date. The step is calculated as: Start Step = Last Dunning Step – <your specified value>. 

The Failed Collection Event Notification payload now supports failed collection attempts initiated against payment plans via the Aria Billing UI.

Test Connection Button Added for Avalara Smart Tax (DEV-12256)

For Avalara Smart Tax, a Test Connection button has been added at the Configuration tab for new configurations (Configuration > Integrations > Taxation Configuration > Avalara Sales/Use - Smart Tax). When the connection test passes, the '_Success_' message is shown at the top of the page. When the connection test fails, the '_Connection failed. Please check credentials for tax group “<service group name>”_' is shown at the top of the page. This feature helps to ensure that the connection is properly configured to prevent failure of invoice processing.

Ability to Update Credit Memo Qualifiers to Existing Credit Memos (DEV-12261)

This feature introduces the ability to update credit memo qualifiers after a credit memo has been created via the UI. The Credit Memo Details UI screen now includes an Add/Edit Qualifier section where you can view existing qualifiers, add new ones, or remove them. These enhancements support regional compliance needs by enabling additional data to be associated with credit memos post-creation and retrieved via UI.

CCP Additional Fixes And Improvements (DEV-12292)

The following updates have been made for CCP:

• The Custom Fields tab within the Account > Overview page has a new “Action Needed” tooltip and notification badge to identify specific fields that require attention.
• The Account > Contacts page has been updated to allow expansion of rows within the data table to view further details.
• The breadcrumb navigation for the Account > Overview page has been updated to ensure consistency within the different tabs on this page and throughout CCP.

CCP Subscription Details Plan Instance Updates (DEV-12293)

The Subscriptions section of CCP has been enhanced with the following updates:

• The Action column within the Subscription History page has been updated to ensure clear, consistent messaging for specific subscription modification events. Previously, some actions were listed with confusing messaging. Messages now map to standardized display names to improve the audit trail clarity.
• Managing dunning groups has been enhanced by allowing you to access and edit dunning group details directly from the Subscription > Details drawer, facilitating quicker adjustments to subscription assignments without navigating away.
• The Queued Changes > Execute drawer has been improved to provide greater flexibility when finalizing subscription updates. Users can now modify the Service Location and Destination Contact directly during the execution phase, ensuring accurate service provisioning without needing to cancel and recreate the queued change.

Level 2 and Level 3 Data Supported For CyberSource Legacy Payments (DEV-12304)

For CyberSource legacy payments, Aria has added the field Send Level 2/Level 3 Data in the payment request at the Processing Options tab for the AMEX and GPN back-end processors (No is the default).

The AMEX and GPN processors support the following card types:

This enables Level 2 and Level 3 data to be sent with VISA, Mastercard, and Discover payments (American Express supports Level 2 data only; Mastercard does not support $0 payments). Level 2 and Level 3 data can be enabled at the Payment Gateway and Collection Group levels. As a reminder, by providing Level 2 and Level 3 data, merchants qualify for lower interchange fees, which merchants pay to card-issuing banks for each card purchase.

CyberSource Smart Payments—Phase 2 (DEV-12311)

Aria continues to expand its Smart Payments integration with the CyberSource payment processor with this release. The following features have been added:

This pay method is supported only for the US currency type; refunds are allowed ($0 transactions are not supported).

At the Merchant Account Details tab, you can allow Credit Card verification to take place with a $0 or $1 amount and a reversal action for all supported card types (VISA, MasterCard, American Express and Discover). The screen defaults are as follows:

This has been added for the Tokenized Credit Card pay method, supporting the following card types:

• VISA 
• MasterCard
• Discover
• Maestro
• JCB (Japan Credit Bureau)

Select either Chase, Streamline or GPN as a back-end processor and use it to perform authorization and payments (Configuration > Payments > Collection Group > Create New Collection Group). This is supported for the following card types: Visa, MasterCard, American Express, Discover, Diner's Club, JCB, and Dankort. The AMEX back-end processor supports the American Express card type.

3DS Authentication 2.0 is also now supported at the Payment Gateway and Collection Group levels. To enable this, make the applicable selection at the Payer Authentication Transaction Mode field at the Processing Options tab. The allowed values are as follows:

• M: MOTO (Mail Order Telephone Order)
• R: Retail
• S: eCommerce (this is the default setting recommended by CyberSource)
• P: Mobile Device
• T: Tablet

This is now supported for 3DS and non-3DS authorizations.

Nets Netaxept Smart Payments—Phase 1 (DEV-12323)

With this release, the Nets Netaxept payment gateway is now included as part of Aria's Smart Payments integration. Credit Card payments (pay method 1) are supported for the following card brands:

• VISA 
• MasterCard
• American Express
• Diner's Club 
• Dankort
• Maestro
• Japan Credit Bureau (JCB)

The following actions are supported:

• Payment (including One-Time Payments)
• Authorization
• Capture
• Authorization Reversal
• Refund

All card types except Diners supports $0 authorization. For Diners, only $1 authorization is supported (action is reversed automatically).

Aria has introduced the soft_descriptor UI field option for Nets Netaxept (Configuration > Payments > Payment Gateways/Collection Groups > Field Options). The maximum allowed character length for soft descriptor in Nets is 1500 (truncation is handled by Nets Netaxept). This value is sent for Authorization and Payment transactions.

Cardholder-Initiated Transaction (CIT) and Merchant-Initiated Transaction (MIT) support has been added for Credit Card payments. The <recurring_process_model_indicator> input field mapping is as follows (for the collect_from_account_m  API):

*-For recurring transactions

[wk] - placeholder for FD topic

American Express Card Used for CyberSource CITs and MITs (DEV-12325)

For the CyberSource legacy payment gateway, the American Express card type can be used for Customer-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MIT). This applies to Credit Card and Tokenized Credit Card pay methods. This feature is now supported for the Visa, MasterCard, Discover and AMEX card types.

CCP Partial Invoice Dispute and Invoice Line Level Write-Off Updates (DEV-12347)

Dispute Hold transactions now have explicit labeling to ensure they are easily distinguishable from standard Write-Offs within the following CCP pages:

• Transactions
• Recent Invoices > Transactions tab
• Payments

A new Transactions filtering mechanism has been introduced to help you quickly locate specific transaction types and to filter records by specific actions, such as Invoice, Electronic Payment, or Voided Check.

Additionally, invoice-line partial dispute creation and partial write-off creation has been introduced to CCP.

• You now have the ability to create partial disputes directly at the invoice-line level by clicking on an invoice number. This allows you to apply precise dispute amounts to specific services within an invoice rather than the entire invoice total.
• You now have the ability to initiate a write-off directly from an invoice number and apply partial write-off amounts to specific line items, rather than being forced to write off the entire invoice balance.

New Client Parameters to Allow Early Payments (DEV-12415)

This feature introduces a new client parameter under Configuration > Payments > Payment Settings, "Allow Payments Prior to First Invoice and Prior to Previous External Payments." When set to "true," it allows you to record external payments on accounts that have not yet invoiced or where the payment date predates prior billing or external payments. This enables use cases such as accepting commitment payments on newly created, non-billable or inactive accounts and having those funds available to allocate to future invoices as they are generated.

If you have already completed your Aria implementation, this parameter will be set to "false," while new Aria instances will default this parameter setting to "true."

CCP List/Edit Contacts Page Updates (DEV-12444)

When editing a contact from the Update a Contact drawer, clicking on a Payment Method ID instantly opens the Update Payment Method drawer. This interface allows you to modify critical payment details including Payment Method Details, Card Information, and Billing Information directly from the Update Contact drawer.

To view the Update Payment Method drawer, navigate to Contacts and select Update a Contact for an existing contact within the contacts list. Locate the Billing Contacts section and select the Payment Method ID associated with the record you wish to modify. Make your necessary changes and save by selecting the Update Payment Method button.

Billie: New Slash Commands and Enhanced Contract Support (DEV-12477)

CSRs gain new capabilities to answer contract end‑date questions and to determine whether cancelling a subscription will incur early termination or cancellation charges.

New slash commands allow you to cancel subscriptions immediately or at the next billing cycle using subscription identifiers.

Enhanced API Support For Independent Installments (DEV-12213)

This feature ensures that installment schedules created through the APIs create_acct_complete_m, create_order_m, and create_order_with_plan_m use the correct independent installment dates when a client-specific time zone is configured in your Aria instance. Previously, when <independent_installment_date> was passed into create_order_m, Aria returned incorrect installment <notify_date> and <due_date> values when the client time zone differed from the database time zone.

Payment Plans Phase 4 (DEV-12218)

Phase 4 of Payment Plans introduces the ability to collect a lump sum or first sequence immediately when creating a payment plan via the create_payment_plan_m API with the plan only created if the immediate collection succeeds. The new API update_payment_plan_m allows you to update the aligned master plan instance, payment method, and schedule, including modifying specific sequences or recalculating remaining sequences based on a new amount. Additional enhancements include expanded outputs in the APIs get_invoice_details_m and get_payment_plan_details_m to support reporting on payment plan balances and sequences.

The new API update_payment_plan_m updates or modifies an existing payment plan, allowing you to:

• Update aligned master plan instance.
• Update payment method associated with payment plan.
• Update payment plan schedule. You can initiate two types of modifications: 
  • Modify specific sequences (dates, due amounts, or both). The number of sequences do not change.

    Notes for this type of change:

    • When you change a specified sequence due amount, Aria will recalculate and distribute the remaining amount evenly to other sequences not specified.
    • This modification does not change the number of sequences in the payment plan schedule.
    • The last sequence due amount is not modifiable.
  • Modify remaining sequences. The number of sequences can change (e.g. from 3 sequences to 5 sequences, when altering the due amount).  You specify one sequence, and Aria replicates the change to the remaining sequences. In this type of change, Aria uses the original payment plan interval and type to calculate the schedule changes. 

    Note for this type of change: When you alter a due amount, it impacts the length of the payment plan: it becomes longer if the new due amount is lower; or shorter if new due amount is higher.

Additional notes and limitations on updating a payment plan include: 

• You can only modify unnotified sequences that are neither partially nor fully paid.
• You cannot modify notify dates nor due dates for aligned payment plans.
• The amount you enter per sequence is tax inclusive. 
• When an account misses a sequence due date and Aria puts a subscription into dunning: if you modify that specific sequence due date to a future date, Aria removes the subscription from dunning the next day.

Create Zero Dollar Credit Lines With Create_cm_m API (DEV-12257)

Updates to the create_cm_m API now allow zero dollar credit lines to be inserted into the <credit_memo_detail> parameter to prevent unexpected errors. Previously, inserting zero dollar records into the <credit_memo_detail> parameter table led to a unique constraint violation in certain use cases.

Due to this update, the get_cm_details_m API also returns these zero dollar credit memo line details within the <cm_line_details> output array.

Ability to Update Credit Memo Qualifiers to Existing Credit Memos (DEV-12261)

This feature introduces the ability to update credit memo qualifiers after a credit memo has been created via the update_cm_m. This new API allows users to add, remove, or clear qualifier name–value pairs using the <cm_qualifiers_update> array and the <cm_qualifier_directive> parameter. This enhancement supports regional compliance needs by enabling additional data to be associated with credit memos post-creation and retrieved via API.

Invoice Due Date Now Returned in Two Payment APIs (DEV-12416)

This feature enhances the get_payment_application_dtls_m and get_acct_payment_history_m APIs to return the field <invoice due date> in the <payment_application_details> array, enabling downstream workflows to identify when payments are applied to overdue invoices.