Release 14.1

Application Fixes

• When you created a service credit for specific plan instances, the credit was applied to all plan instances on an invoice instead of only the selected plan instances. (TICKET-11921)
• When using an electronic payment method for collection, and selecting specific charges to pay, the specific charges were not being collected, instead the collection on charges was based on FIFO. (TICKET-12433)
• The account holder's middle initial was not copied from the account contact details to billing contact details when your client parameter Copy Admin Contact To Empty Billing Contact Fields was set to True. (TICKET-14381)
• Accounts with a master plan instance whose next bill date was one year after the bill through date had their next bill date set to the incorrect year. (TICKET-15643) 
• When updating Processor Details for a Collection Group (e.g. login credentials) in the UI, the updated data was not saved in the database and the changes would disappear. (TICKET-15676)
• A monthly anniversary invoice for charges was not including a recurring fee charge on a plan billed quarterly. (TICKET-15691)
• When assigning to an account a Master Plan with a "recurring" flag set to "no" (that is, not billable), and Supplemental Plan was subsequently assigned to an account with "prorated invoice" specified, the Master Plan's "no" recurring flag was not honored, and an invoice was generated. (TICKET-15736)
• An existing multi-plan contract was getting discarded when a new multi-plan contract was created for the same Master Plan instance, even though the "Auto Discard" checkbox was left unchecked (TICKET-15772)
• When you removed a payment method from an account, incorrect validity dates were displayed for the disabled payment method. (TICKET-15815)
• When assigning a plan to an account, specifying an override_bill_thru_date of the 29th or 30th (i.e. the bill date of the plan is the 30th or 31st), and an alt_start_date of 28-February, an error was received (rather than an expected one-day charge for the plan). (TICKET-15845)
• Duplicate invoices were generated when you replaced an account's inactive plan (never invoiced before) with an active plan. (TICKET-15918)
• When a queued billing frequency change occurred on the billing anniversary, the service period for the anniversary invoice was incorrect. E.g., updating a monthly Master Plan and monthly Supplemental Plan to bill annually on the next billing anniversary resulted in only monthly charges on the billing anniversary. (TICKET-15949)
• Contracts scheduled to roll over to a different plan and/or rate schedule did not roll over after their bill through/anniversary dates. (TICKET-15968)
• Account was being invoiced twice after plan assignment. The overlapping bill period charges resulted when the plan assigned has mandatory plans being assigned at the same time resulting in the bill dates for the mandatory plans being lost, and the "parent" plan's bill dates to be misaligned. (TICKET-15981).
• Errors occurred during encryption/decryption of a credit card number, bank account number, or IBAN (International Bank Account Number) that was 18 characters long. (TICKET-15984)
• Clicking the left-hand navigation under Account before the Account Overview loads, after clicking an account number from the search screen, resulted in a "Data Table Warning." (TICKET-15988)
• If you used Chase Paymentech as your processor, the tax type applied was incorrectly displayed as a number on invoices instead of as the applicable tax type (examples: FED or STA). (TICKET-16001)
• Supplemental plans that were set to "Inactive" status showed "Inactive" as expected on plan detail screens, but showed "Active" on the plan hierarchy screen. (TICKET-16039)
• When performing collections using the Braintree payment processor, the actual processor status, and status text was not populating and displaying in Aria (TICKET-16041)
• When a Master Plan had mandatory plans to be assigned at the time of plan assignment, proration charge amounts were not correct if the mandatory Child Plans' recurring billing interval was longer than one month. (TICKET-16062)
• An error occurred when you tried to use an alternate one-time payment method to make a payment for an account without an existing payment method. (TICKET-16073)
• insertCCType" and "insertMaskedCCNumber" statement template replacement strings did not pull CC data onto statement template when Orders were invoiced immediately. (TICKET-16074)
• When the usage unit threshold is lowered on a plan, Aria will now send the usage unit threshold email to customers, rather than returning a "too many rows fetched" error. (TICKET-16156)
• After approving a pending invoice for an account that includes a Master Plan Instance with multiple supplemental plans, more than one of which have both queued custom rate changes and different services, bill dates among the supplemental plans are no longer out of sync. (TICKET-16280)