Release 74

Configure Credit Profile Alerts and Notifications in Allegro (AL-850)

Allegro adds an end-to-end alerting framework that notifies your customers when their account activity crosses a configured threshold.

Configure notification email templates, notification template groups, and credit profiles that define currency, allowance, and accumulator thresholds for each customer. When usage rating detects that a customer has reached or exceeded a threshold, such as an exhausted prepaid credit balance, a completed credit top-up, or an allowance or accumulator threshold, Allegro sends the corresponding notification to the customer through core Aria.

Use the new Allegro user interface (UI) screens to create and manage credit profiles, and view the credit profile associated with an account in the Account view and the Usage Billing Data view.

Allegro Grids Now Reset to Default Column Settings Automatically (AL-1124)

Allegro grids now reset to their default column settings automatically when you have not saved a custom column template. Previously, Allegro did not apply a consistent default when no saved template existed. This change applies the default template consistently across your users, deployments, and screens.

View Cached Configuration Data with the Allegro Cache Inspector (AL-1127)

Allegro adds a Cache Inspector screen, available from Operations > Cache Inspector, that lets you view the data currently stored in cache memory. Use this tool to review cached configuration data, primarily related to the usage rating flow. The Cache Inspector helps you diagnose issues that involve cached data.

Configure Allegro Customer Attribute Pricing by Address (AL-1130)

You can now configure customer attribute pricing based on your customers' addresses. Allegro adds support for City, State, Country, and Postal Code as pricing attributes, so you can apply pricing that varies by geography.

Configure this option at the client level, and select the Address attribute from the dropdown on the price offer. This lets you apply region-specific pricing, account for delivery costs, and segment your customers by location.

New Allegro Permissions for Recently Added Actions (AL-1135)

Allegro adds new permissions that you can assign to control access to several recently added actions and configuration screens.

• Back-out actions (undo billing and undo usage)
• Force delete
• Reset file mapping
• Field masking
• Custom attributes
• Mediation reprocess
• Credit profile
• Notification template and notification template group configuration

Assign these permissions to control which of your users can access each action or screen.

Allegro Usage Gateway Now Accepts Compressed Usage Files (AL-1146)

Allegro's usage gateway now accepts compressed usage files in .zip, .tar.gz, .tgz, and .gz formats, in addition to standard text files. When you upload a compressed file, Allegro automatically extracts and processes each file inside it, and reports processing statistics for each extracted file individually rather than for the compressed archive as a whole.

Allegro retains the original compressed file in its Amazon S3 storage folder and moves it through the standard input, in-progress, and processed stages.

Allegro Usage File Uploads Now Support Special Characters in File Names (AL-1147)

Allegro's usage file upload process now supports file names that contain special characters, such as plus signs, spaces, parentheses, square brackets, and exclamation points. Previously, some of these characters caused Allegro to reject valid usage files submitted through the Amazon S3 upload folder. Allegro now correctly restores these characters after upload, so the corresponding files upload and process without error.

Upload Compressed Usage Files from the Allegro UI (AL-1181)

You can now upload compressed usage files directly from the Allegro UI Usage Data upload screen, in addition to standard text files. Previously, the UI rejected compressed files and displayed an error message stating that the file must be a valid UTF-8 text file.

The upload screen also includes a Quick Notes section that explains the following:

• Allegro does not display a content preview for compressed files.
• Processing statistics reflect the individual files extracted after decompression.
• Allegro retains the original compressed file in Amazon S3 through the standard processing stages.

Run Multiple Batch Schedules per Day with Secondary Batch Schedule Groups (DEV-10552)

Secondary batch schedule groups let you run more than one billing batch schedule per day, so different groups of accounts can be invoiced, billed, and dunned at a time that matches their own time zone or region, instead of every account sharing one nightly run. Each group's invoices, statements, dunning notices, and reminders process independently, so one group's run never affects another group's accounts.

Use the new Batch Schedules page to view, create, and delete secondary schedules, assign a schedule to an account group, and turn individual sub-jobs on, off, or suspended. If invoice generation fails for any records, or Aria finds leftover records from a previous run, Aria sends a detailed notification email so your support team can investigate quickly. Batch activity logs and audit trails also show which schedule produced each run, making it easier to trace results back to the correct group.

Handling Negative Balance Forward (18) Transaction In Invoice Voiding Process Of Parent Child Scenario (DEV-11689)

The handling of negative balance forward transactions in parent/child account relationships has been adjusted. When a negative balance forward is created on a child account, it is now applied to that child account's own outstanding charges first. Then the remaining balance is transferred up to the parent account. Previously, the entire negative balance forward amount was transferred directly to the parent without first being applied against the child's charges, which could leave child-level charges outstanding when they should have been offset.

Account Create Part 1 (DEV-12587)

Advancements in the new CCP Account Creation wizard now add backend support and continue replacing placeholder UI data with live data:

• New REST resources:
  • Locales — returns a client's effective locale configuration, combining global system defaults with any client-specific overrides, so the wizard can present the correct locale options for that client.
  • Legal-Entities — returns the legal entities configured for a client, for use in entity-selection fields during account creation.
  Both resources are new and purely additive — they introduce no changes to existing endpoints or behavior — and both support standard RSQL filtering, sorting, and cursor-based pagination, consistent with Aria's other REST resources.
• UI progress: Continued expansion of populating the menus on Step 1 of the Account Creation form with live data pulled from these (and other) resources, as well as replacing the hardcoded placeholder values that were put in place during earlier development.

New Configuration Selection for CyberSource Legacy Integration (DEV-12703)

Aria has added a new configuration selection to its legacy integration with CyberSource to streamline refund processing. When enabled, the Send Capture Request ID Only for Refunds selection ensures that only the Capture Request ID is sent when processing a Tokenized Credit Card refund. Previously, the Subscription ID was sent also when processing this type of refund; CyberSource rejected refunds that carried both identifiers. Turn this on if your CyberSource account has network tokens enabled, or refunds will fail. This selection can be found at the following location: Configuration > Payments > Payment Gateways/Collection Groups > Processing Options tab.

The following are Allowable Options for this selection:

• Use Payment Gateway Setting (for Collection Group)
• False (default—current behavior)
• True

Payment Plan Validation and Behavior Improvements (DEV-12716)

This release closes a set of gaps in Aria's payment plan and installment framework, tightening validation and correcting edge case behavior.

• Aria now rejects a lump sum amount that exceeds the invoice total.
• Aria now rejects an update that would remove a required aligned plan instance.
• Aria now rejects a lump sum sequence change attempted through an unsupported update path.
• Aria now prevents a payment plan from using its own payment method when the associated billing group is on payment terms, because Billing Manager does not collect against net-term balances through that path.
• Aria now displays a clearer account comment when a payment plan cancellation triggers dunning.

Together, these changes make payment plans more consistent.

Add Additional Levels NTG Support to Separate XML Masterfiles (DEV-12725)

When generating daily XML master files (Batch Process 10), Aria now resolves the applicable Notification Template Group (NTG) using a priority order across the following three levels:

1. Billing Group
2. Account
3. Client

Previously, only the Billing Group level was honored for this purpose; if no Billing Group-level NTG applied, the statement fell back into the common master file even if an Account or Client-level NTG existed. Now, all three levels are checked in order, and:

• Statements that resolve to the same NTG are grouped together into the same separate master file, regardless of which level (Billing Group, Account, or Client) supplied it.
• This priority resolution applies consistently across all four Batch 10 template classes: Statement, Credit Memo, Independent Payment Plan, and Independent Due Reminder.
• Documents that have no applicable NTG, or whose NTG is not configured to use a separate master file, continue to be included in the common master file exactly as before. This change does not affect that fallback behavior.

Core MCP Server Enhancements Phase (DEV-12742)

This is Phase 1 of a set of improvements to Aria's Core MCP server, aimed at strengthening the contract presented to AI/MCP clients so that errors are caught earlier and tool usage is clearer.

• Schema and validation improvements:
  • Tool input schemas now correctly advertise which fields are required, including support for either/or identifier groups (e.g., "provide field A or field B").
  • Calls missing required data are now rejected at the MCP layer itself, before ever reaching Aria's backend, reducing wasted round-trips and unclear downstream errors.
  • Array- and object-typed parameters now generate proper nested JSON Schemas, instead of incorrectly falling back to plain string types.
  • Validation error messages now explicitly name the actual missing or invalid field(s), rather than returning a generic error.
• Documentation and usability improvements:
  • Every tool description now documents the error_code/error_msg response contract, since Aria's API returns HTTP 200 even when a business-logic failure occurs which is an important detail that AI clients need to know to correctly detect failures.
  • Enum fields now include human-readable value labels alongside their raw values, making it easier for AI clients to present or reason about valid options.
• Resources and prompts:
  • MCP resources now expose 8 Knowledge Central guides, up from just 1 previously. These are cached hourly, with automatic fallback to the last-known-good content if a fetch fails.
  • Nine new prompts have been added to help guide AI clients toward the correct tool for common lookups and for higher-risk write operations, including preview/confirm flows where the underlying tool supports them.

Additional Bug Fixes And Improvements (DEV-12746)

The following STARK/CCP fixes and improvements have been completed:

• A new "dunning-actions" REST resource exposing a subscription's dunning history.
• The Add New Subscription list now filters available plans by the account's currency.
• CCP now honors a client-level default setting for whether invoice line items are reversed on refunds.
• Quick Search results now display matching Account Field values as their own columns; for standard fields (e.g., Company Name, PO Number), every matching value is shown as an individual pill (a rounded UI element to be clicked on that displays additional values) rather than being truncated or merged.
• Newly created records now appear highlighted at the top of CCP grids immediately after creation, making them easier to locate.
• Added improved handling of partially-provisioned billing databases, preventing unnecessary query failures in that state.
• Credit Memo screens now display actual service names (with subscription/NSO tooltips) instead of generic labels.
• Corrected bug where "FDFO" payment application failed on the Make Payment screen.
• CCP search now also covers Invoice Number and Order Number, bringing its search coverage in line with Aria Billing core.
• Step 1 of a new 7-step Create Account wizard has been introduced.
• Bill Lag Days can now be edited inline directly from Subscription Details.
• The sort order shown in Quick Search's preview panel has been corrected.
• Added support for currency-scoped surcharge assignment.
• Also included is a fix for inaccurate "accessible" values returned for multi-client users via the v1/clients endpoint.

Subscription Details (Plan Instance) Part 12 (DEV-12751)

Several enhancements have been added to the Subscription Details view in the Customer Care Portal (CCP), focused on giving CSRs more direct control and visibility without leaving the page:

• Promo Code management: CSRs can now assign, change, or remove a subscription's Promo Code directly from a new drawer opened from Subscription Details. The drawer includes a "None" option specifically for clearing an existing code, so CSRs no longer need to route promo code changes through a separate workflow.
• Statement Contact drawer: A new drawer lets CSRs either select an existing account contact or create a new account contact to serve as the subscription's Statement Contact. From this drawer, CSRs can also view the payment methods associated with that contact and edit contact details inline — importantly, these edits apply only to this subscription's use of the contact and do not alter the shared contact record elsewhere on the account. Alongside this feature, a related bug has been fixed where saving an empty contact form could cause previously-entered details to persist and carry over incorrectly.
• Clickable balance fields: Both the Full Balance and Balance Due fields on Subscription Details are now clickable. Clicking Full Balance opens a drawer showing the subscription's complete transaction history, while clicking Balance Due filters that same view down to only the unpaid or past-due portion. Within the drawer, each transaction row links directly to its associated invoice and can be expanded to show exactly what the transaction was applied against.

Multi-Select Buyer and Seller Numbers Now Supported for OneSource Smart Tax (DEV-12761)

Aria adds support for multi-select Buyer and Seller Tax Registration Numbers used for tax reporting and invoicing for OneSource Smart Tax. Previously, you needed to enter these numbers as a comma-separated text string, which was an error prone and difficult-to-manage process. Now, you can enter new Seller Tax Registration Numbers and Buyer Tax Registration Numbers, select existing numbers, and edit/delete number from a list (Configuration > Integrations > Taxation Configuration > Configuration tab). Enter a maximum of 25 Buyer and 25 Seller Tax Registration Numbers (existing comma-separated text strings are supported). For Buyers, you can use a Supplemental Field Override for account-level values.

This matters because tax authorities in different countries or regions may require the correct registration numbers to be listed in order for taxes to be calculated correctly. If the wrong number is missing, you could be taxed incorrectly, which could cause billing errors or compliance headaches. Now, Aria can accommodate a single customer account that may need its own special tax number setup that's different from the company-wide default of a single number.

Prorated Charges Now Carry Over to Regenerated Invoices (DEV-12769)

Aria now carries deferred, prorated charges forward when it regenerates an invoice after you void the original invoice, so the charges are billed correctly on the regenerated invoice. Previously, a voided invoice's prorated recurring charges did not carry over to the newly generated invoice, and only the next period's regular advance charge appeared.

This ensures your customers receive a complete and accurate invoice for the billing period, reducing the need for manual corrections. The correction applies regardless of how the deferred charge was created, whether through a plan assignment, replacement, update, or cancellation.

Billie and Billie Connect version 1.74.0 (DEV-12771)

Billie and Billie Connect (version 1.74.0) have received the following updates:

• Structured data support: Converse and A2A API responses for dunning and projected-suspension-date queries now support structured data. External agents and integrating systems can request the response in TEXT, DATA, or BOTH modes, depending on whether they need a human-readable answer, machine-parseable data, or both together.
• Clearer dunning responses: Dunning responses now display the Client Plan Instance Id alongside the subscription name, helping CSRs distinguish between multiple subscriptions that happen to share the same plan name. Additionally, when only one subscription on an account is in dunning, the response now gives a clearer, more specific message reflecting that single-subscription case.
• Bill-Shock Slack agent fixes (Slack App 1.0): Several fixes were made to the Bill-Shock agent used with the new Slack App:
  • Alert headers now show the correct client-facing account name.
  • Alerts are now routed to the correct client-mapped Slack workspace.
  • The default cash/service-credit cap used by the agent has been updated.
  • Rendering is now cleaner in cases where no alternative plans are available to offer.

New Allegro REST Endpoints for Price Offers and Subscriptions (AL-1151)

Allegro's API Gateway now exposes two new REST (Representational State Transfer) endpoints.

• Get Price Offer by price offer ID
• Get Subscriptions by balance unit ID

These endpoints give you REST access to data that was previously available only through GraphQL.

Allegro PUT Balance Unit Endpoint Now Restricted to Credit Profile Updates (AL-1154)

The PUT /balance/unit endpoint in Allegro's API Gateway now allows you to update only the credit profile ID field. Previously, this endpoint accepted additional fields, such as subscription ID, parent ID, and accumulator or allowance values, but silently ignored changes to some of these fields without returning an error.

Allegro also removes the masterPlanName field from balance unit API responses, because it never returned a value.

New Tax Fields Added to the Allegro Billable Service and Price Offer APIs (AL-1194)

Allegro's Billable Service and Price Offer APIs now expose the tax attributes added to support taxation.

• Billable Service API (create, modify, get, and search endpoints)
• Price Offer API (create, modify, and get endpoints)

The Billable Service create, modify, get, and search endpoints now include the <taxable> and <tax_service_group> fields. The Price Offer create, modify, and get endpoints now include the <tax_inclusive> field. Aria updated the Swagger documentation for both APIs to reflect these fields.

Handling Negative Balance Forward (18) Transaction In Invoice Voiding Process Of Parent Child Scenario (DEV-11689)

The handling of negative balance forward transactions in parent/child account relationships has been adjusted. Voiding an invoice via the void_transaction_m API now correctly voids the associated negative balance forward (transaction type 18) in parent/child scenarios as well. Previously, this transaction type was not being unapplied when the related invoice was voided, leaving an inconsistent transaction state on the account even after the void completed.

Send Account Notification Emails with the New Create Account Message API (DEV-12683)

Aria has developed a new API method, create_acct_message_m, allowing third-party usage platforms to send account-level notification emails through Aria's existing communication framework.

Edit each notification template through the standard email template administration screen. The templates support four notification types: prepaid credit exhausted, prepaid credit top-up applied, usage allowance threshold reached, and usage accumulator threshold reached.

Use the create_acct_message_m API to send these notifications. Supply the usage details, such as resource names, amounts, and thresholds, in the request, so Aria does not need to calculate or store that usage data itself. Aria resolves the correct recipient and message template from the account, billing group, or plan instance you provide. This gives you a way to keep your customers informed about usage-based thresholds without building separate email infrastructure outside Aria.

All-Line Rebill Now Supports New Charges, Discounts, and Service Credits (DEV-12711)

This release adds a new <rb_new_lines> input array and associated fields to the gen_rb_m API method, supporting the all-line rebill feature introduced in Release 73. You can now edit any type of line item and add new line items to a rebill invoice that were not present on the original invoice. Supported new line types are recurring charges (including proration), surcharges, order-based charges, service credits, and discounts. You can also specify ship-from/to and bill-from/to addressing per new line for tax engine purposes to the associated account.

Enable the Enable All Invoice Lines Edit for Rebill client parameter to allow discount amounts, service credit amounts, and unit quantities, including decimal units, to be edited on a rebill. If you already rely on the existing rebill behavior, this parameter does not change your system behavior unless you turn it on.

With the parameter enabled, the gen_rb_m API accepts these additional line edits. Aria creates the new service credits and discounts using the same definitions as the originals, so the reissued invoice closely resembles the invoice it replaces.

The <rb_new_lines> array includes the following fields:

Two New APIs Added for Aria Internal e-invoicing—Phase 2 (DEV-12719)

Aria has added the following two APIs for the latest phase of Aria Internal e-invoicing:

• gen_einvoice_m—This API generates, sends, or resends the e-invoice document for a single invoice. This allows you to resend an e-invoice to your customer's email address in the event of an initial “send” failure. You can identify the invoice with the <invoice_no> or supply the <einvoice_seq_no> to act on a specific previously generated document for that invoice.
• get_einvoice_statement_m—This API returns the latest generated e-invoice XML for a given invoice, along with the statement's e-invoicing status, and, if the last attempt failed, its error code and message. You can identify the invoice by <invoice_no> or supply the <einvoice_seq_no> to act on a specific previously generated document for that e-invoice document without re-deriving it from raw billing data

Added Details to get_acct_statement_all_m API (DEV-12780)

Aria enhanced the get_acct_statement_all_m API so client applications can retrieve more detail about parent-pay invoices.

When Aria transfers a customer's child account invoice balance to a parent account, the API now returns the transfer details, including the originating account, the invoice number, the transfer amount, and the plan instances involved. The API also returns a custom status label, a custom status description, and any client notes recorded against an invoice. This information helps you build more informative invoice views in customer relationship management systems and self-service portals. Retrieving these details is optional, so it does not affect existing integrations that do not request them.

The <balance_transfer_details> array includes the following fields: