AMPS 3.2 Release

Automatic Conversion of Unapplied Service Credits on Subscription Cancellation (WFAMPS-4898)

Previously, when a subscription was cancelled, any unapplied compensation service credits remaining on the account were left untouched. Since no further invoices are generated for a cancelled subscription, these credits remained unused, leading to unrecoverable compensation.

To address this, a new enhancement has been introduced to automatically convert unapplied service credits into cash credits when a subscription reaches a final cancellation status. This ensures the unused value is returned to the account balance and becomes available for other subscriptions or for refunding.

The enhancement is implemented within the existing process, which handles cancellation-related ARIA events. This ensures the transformation is only triggered once cancellation is confirmed, and avoids premature credit handling if the cancellation is later reversed.

A new global parameter SubsHandleUnappliedServiceCredit has been introduced with two configuration options:

• LEAVE – Retains the unapplied credits as-is (default behavior).

• CONVERT – Automatically converts the service credits to cash credits upon cancellation.

A new subflow has been created to perform the actual conversion logic when the subscription status changes to Cancelled (-2) or Terminated (-3). Suspensions or other intermediate states do not trigger this behavior.

This change ensures consistent and recoverable handling of compensation credits in cancellation workflows, reducing manual interventions and financial discrepancies.

Dunning Group Not Updating on Billing Group Modification (WFAMPS-5294)

Resolved an issue where updating the billing group from a payment term to a payment method (or vice versa) did not correctly update the associated dunning group when both shared the same Dunning Process ID. The system now ensures that the dunning group name and description are updated consistently during such transitions.

Billing Group Incorrectly Updates on Invalid Dunning Process ID (WFAMPS-5087)

Corrected a flaw where the billing group was still being modified even though the API rightly rejected an invalid Dunning Process ID. With this fix, the system prevents any billing group changes when invalid dunning inputs are provided, maintaining consistency and avoiding partial updates.

GDPR Anonymization Fails for Archived Accounts (WFAMPS-5537)

Fixed an issue where the GDPR delete process could not complete due to a mismatch in recognizing the new "Archived" account status. The system now correctly identifies this status and allows anonymization, restoring full GDPR compliance for affected accounts.

Missing Start Notifications for Scheduled Subscriptions (WFAMPS-5557)

Resolved a case where start notifications were not sent for subscriptions with future activation. This update ensures delivery Start on plan status change from Inactive to Active.

Multiple Complaint Management Issues Fixed (WFAMPS-5309)

Multiple fixes were implemented to improve the complaint management process:

• Prevented multiple complaints for the same date using different codes.

• Blocked complaints when delivery hasn't started yet.

• Added validation to prevent complaints on non-delivery weekdays.

• Improved error messaging for clarity and accuracy.
  These changes ensure complaint records are consistent with delivery schedules and user feedback is accurate.

Incorrect ref_timing_code Assignment During Credit Note Processing (WFAMPS-5304)

Resolved an issue where applying a credit note against an invoice that had already been paid (immediately upon creation) caused a mismatch in the ref_timing_code. The original invoice transaction had ref_timing_code set to "BEFORE", but after crediting, it was incorrectly set to "AFTER". This led to inaccurate financial data in the ERP, suggesting the invoice was not paid upfront. The logic has been updated to fetch the original transaction's timing code and reuse it during the replacement process, ensuring consistency and correct historical reference.

Invoice Failures Due to Credit Balance and Schema Validation Post-Upgrade (WFAMPS-5564)

Previously, the Statement Transaction Type in the 1042 event was defaulting to "INVOICE", regardless of the actual transaction being processed. This caused incorrect reporting and inconsistency in financial records.

The issue has now been resolved by updating the logic to correctly reflect the transaction type. The system will now assign:

• PAYMENT when the event is related to a payment transaction.

• CASH CREDIT when the event is related to a cash credit transaction.

Failure of 942 Events Under Standard Price Model (WFAMPS-5541)

Fixed an issue where 942 event processing was failing inappropriately when the associated price model was 'Standard'. The failure occurred within the ApprovePendingInvoice subflow, which returned error code 3015, halting processing. The flow has been updated to detect this specific scenario and route appropriately—either continuing to process affected account plans or retrying the event as needed—ensuring stability in event handling.

Incorrect Invoice Credited During Write-Off Voiding (WFAMPS-5291)

Corrected a critical issue where the system, upon voiding an underpayment write-off to issue a cancellation credit memo, was mistakenly crediting a different invoice than the one originally tied to the underpayment. This led to reopened small balances on customer accounts and accounting inconsistencies. The fix ensures that the correct invoice is now credited in alignment with the associated write-off, preserving financial accuracy.

Self-Service Page Showing Incorrect Subscription Overview After Termination (WFAMPS-5240)

Resolved an issue where terminated subscriptions, particularly those ended due to failed payments, continued to display incorrectly as active on the self-service overview page within the Aria iframe. Although the ModifySubscriptionRequest correctly updated both Aria Core and CIM, and access was properly revoked, the overview display logic was not aligned with the actual subscription state. This has now been fixed to ensure terminated subscriptions no longer appear active to the user.

Incorrect Revenue Account Mapping in ERP Files (WFAMPS-5550)

Addressed a mismatch in ERP file postings where credit memos for certain digital titles were being assigned to incorrect revenue accounts. While invoices were correctly posted to account 3021, their corresponding credit memos were erroneously posted to 3011. The revenue mapping logic has been corrected to ensure consistency between invoice and credit memo postings for affected titles.

Error When Adding New Payment Method Due to Missing Title PayOptionCodes (WFAMPS-5442)

Fixed a critical error encountered during the addition of new payment terms. The system failed with a missing titlePayOptionID in the TitlePayOptionCodes table. The creation flow has now been updated to ensure the necessary entries are correctly generated in the associated table, allowing new payment methods to be added without error.

Missing Dunning Status in Subscription Retrieval API (WFAMPS-5446)

Corrected a gap in the SubsRetrieveSubscription API response, where MPIs in Dunning State = COMPLETED (status code 2) returned a null value for the instDunningStatus field. The logic in the SubsRetrieveSubscription_ProcessMPI has been updated to recognize and match this dunning status, ensuring that the appropriate COMPLETED state is returned.

Aria Failing to Update FarPay After Webhook Event (WFAMPS-5547)

Fixed an issue where Aria was not updating FarPay after receiving a webhook indicating a pending customer number. Although Aria responded with a 200 OK to the webhook, no subsequent update was sent to FarPay, as expected. Investigation revealed that Aria was using a POST request instead of the required PUT method, causing FarPay to reject the data. The request method has been corrected to PUT to ensure proper synchronization between Aria and FarPay going forward.

Balance Not Updating During Dunning Process (WFAMPS-5501)

Fixed an issue in the dunning flow where the balance due was not being correctly updated in the DocmDunningNoticeFee table when the FEE step was executed. The logic evaluating whether the current balance was zero had an incorrect route configuration. The true and false paths were mistakenly inverted, causing the balance update step to be bypassed. This logic has now been corrected to ensure accurate balance tracking during dunning.

Duplicate Invoices Due to Failed Batch Transfer (WFAMPS-5252)

Resolved a critical issue where failed batch runs resulted in duplicate invoices being sent, particularly affecting clients. When the DocmProcDocMainBatch process failed (e.g., due to an SFTP exception), it did not correctly flag in-process records with an error status, causing them to be picked up again on the next run. To prevent this, the process has been enhanced to mark failed records correctly. Additionally, a uniqueness constraint (u_aria_invoice_no) was added to the DocmInvoiceDetails table to prevent duplicate invoice entries in the database. This constraint has been applied in production and will be rolled out to other environments as part of operational deployment.