-
Fixed an accessibility issue on the Funds Transfer page where some content was cut-off when text spacing was adjusted. (UUX-46120)
-
Fixed an accessibility issue on the Funds Transfer page where the focus indicator for keyboard navigation was missing in the Calendar component. (UUX-45310)
-
Fixed an issue where accounts couldn't be added to an already created group when the user has over 60 accounts in their Account View. (UUX-46989)
-
Fixed an issue where the Retry button for the disable pop-up blocker warning window wasn't selectable even after users disabled their popup blockers. (UUX-47022)
-
Fixed an issue with External Transfers where an FI was sporadically provided a Funds Transfer Payment Failed error alert when they weren't configured for Q2 Sentinel (formerly RFA). (UUX-47151)
-
Fixed an issue where adding a new subcategory in the Categorize window for Transactions resulted in the dropdown menu closing. Now, the menu will stay expanded after adding a subcategory. (UUX-47495)
Businesses that encourage their customers to send payments using open payables (for example, purchase orders, bills of lading, or using a contract number) using ACH credit usually also encourage customers to include a structured addenda record with the payment. A structured addenda record conveys information to the recipient about the reason for the payment, including specific data elements such as invoice number, date, amount, and any discounts applied.
The new Structured Addenda feature provides a form that generates a structured addenda record for a payment. This feature can be used in cases where the payment is specific to accounts payable transactions and the receiver specifies payment be made using an ACH Credit CCD Plus (CCD+) addenda format.
Note
This feature does not support importing or mapping data into the structured addenda form fields through the Payment from File, File Mapper, or Upload from File workflows. The only structured addenda type supported with this feature is Payment on Remittance (RMR).
To access this feature, FIs must meet the following requirements:
-
HQ version 4.6.0.7016 or later
-
Ardent version 4.6.0.7015 or later
-
Tecton Platform version 1.46.1 or later
-
Tecton SDK version 1.46.1 or later
-
Q2 Console User Management version 2.1.8 or later
Note
No changes to ACH adapters or ACH Automation were required to support this new feature.
You can enable the Structured Addenda feature within Q2 Console User Management. This feature is available for both Treasury (Corporate) and Non-Treasury (Commercial) customers. The feature is not enabled by default. You must have the rights (permissions) to edit Groups in Q2 Console User Management in order to enable the Structured Addenda feature. Rights are configured through CSR Roles in Q2 Console Administration.
Tip
When enabled at the Group level, the right will be available to entitle to all Customers within that group.
From with Q2 Console User Management, navigate to the appropriate corporate Group. Within the Rights section, select Enable Structured Addenda.
To create an ACH payment that includes a structured addenda record, entitled users can perform the following steps:
-
Log in and follow the navigation path to create an ACH credit payment.
-
Select CCD – Cash Concentration and Disbursement from the SEC Code dropdown list.
-
Add one or more recipients using the existing method to add existing or create new recipients.
For each recipient, there is now an option to add an addenda record.
-
Select the expand
icon to display the Addenda field for each recipient. The usual Freeform Addenda field displays, or you can toggle the the new Structured Addenda option to display.
Note
Users who are not entitled to create structured addenda records will only see the Freeform Addenda field after selecting the expand
-
Select to enable the Structured Addenda option, and a new form appears, replacing the Freeform Addenda field.
-
Complete the following three required fields within the new Structured Addenda form:
-
Reference Number Qualifier, which identifies the document type or remittance type represented by the addenda record. The description is displayed and the corresponding two-letter code for the Reference Number Qualifier will be included in the addenda record. Some examples are Purchase Order Number, Bill of Lading Number, or Invoice Number.
-
Reference Identification, which is the unique identifier value corresponding to the Reference Number Qualifier. For example, if the Reference Number Qualifier selected is Purchase Order Number, then the user would input the Purchase Order Number from their vendor into the Reference Identification field.
-
Gross Amount, which is the total amount of the Accounts Payable obligation. For example, if the invoiced amount is $750.00 and there are no deductions or discounts, then the user will input 750.00 into the Gross Amount field.
If there are deductions or discounts, then those amounts should be reflected in the Discount Amount field.
Note
The user must manually calculate the net amount being paid (as reflected in the Payment amount field for the Recipient/Account, as there are no calculations performed on the amounts input in the form.
-
-
When applicable, a value can be selected from the optional Payment Action Code dropdown list to provide additional details about the payment.
As information is added within the form, the read-only Structured Addenda Details field is populated with the appropriate syntax for the record.
The three-letter code that identifies the structured addenda record type (RMR) is added automatically, as are separator characters (*) and the terminator character (\).
Tip
If the Payment Action Code and Discount Amount fields are not used, there will be two asterisks inserted into the addenda record to represent the fields not used.
After the payment is drafted or approved, the Structured Addenda Details will appear with the transaction data in the Activity Center, in the same way as it is displayed when a freeform addenda record is added to a payment.
Q2online (UUX) now includes the ability to download the ACH Reporting System (ARS) output files available from the Centrix Exact/TMS ARS module within UUX. This integration allows both ARS-only Centrix ETMS customers and customers using both UUX and Centrix ETMS the ability to find and download their ARS output reports within UUX for the last five business days that the user has permission to access. Additionally, users can use the UUX single sign-on (SSO) to authenticate into the full ETMS/ARS system from the Reports page by selecting the Launch advance settings button from within the new ExactTMS ARS Reports tab.
-
Centrix Exact/TMS version 8.8.21.0 or later
-
Centrix Exact/TMS Connect API version 8.8.21.0 or later
-
Centrix Exact/TMS ARS Module
-
UUX version 4.6.1.0 or later
The integrated ARS reporting features offers the following additional features:
-
Users can sort the following columns on the ExactTMS ARS Reports tab:
Note
When sorting a column within the ExactTMS ARS Reports tab, only the data on the current page of results is sorted.
-
Date Created—displays the date the report was run within ARS Reporting.
-
Name—displays the names of the reports, sorted alphabetically.
-
Output type – File type—displays the file type of the output, sorted alphabetically.
-
-
Users can view the ARS reports from the last five business days; however, older reports can be retrieved using the Launch advance settings button.
-
Users can select the Launch advance settings button to SSO into the full Centrix Exact/TMS ARS system.
(UUX-35450)
-
Updated the Domestic Wire and International Wire payment forms to accept 35 characters for the Reference for Beneficiary field in compliance with the ISO 20022 changes that go into effect in March 2025.
Note
The updated field length will not be reflected in payments from wire templates, nor in Activity Center, until HQ version 4.6.0.7017 , which will be available after Dec. 18, 2024.
(UUX-46370)
-
Fixed an issue in the Activity Center where the focus indicator was not visible while navigating through the rows using the Tab key. (UUX-46490)
-
Fixed an issue for mobile devices on the Reports page where, when there were no reports available to view, the +New Report hyperlink was nonfunctional.
Now, users are prompted to select Create New Report instead. (UUX-47778)
-
Fixed an issue where the titles within the print preview for check images could not be configured. This can now be configured to meet FI requirements.
(UUX-47249)
-
Added the ability to customize the sort order of statements displayed on the Statements page. Previously, statements could only be sorted by period (month) followed by year if the period was in MM format. Now, period formats other than MM are supported with a new configuration that can be changed based on your statement vendor's format.
Note
To request a configuration change, please submit a case in the Q2 Customer Portal.
(UUX-47053)
-
Updated the icon set used within UUX to allow all icons to be fillable. This resolves both accessibility issues and issues with the icons not conforming with FI designs. (TCT-2824)
-
Enhanced the select component used within the UUX UI for dropdown menus to allow the user to clear the selected value, as it might be required for input and calendar fields. This is not a default behavior but functionality that may be opted into if the feature or workflow decides to permit it.
(TCT-2518)
-
Fixed an issue where the Messages window displayed messages of another user when two different users log in to secure messages one after another from the same browser. (UUX-46843)
-
Fixed an issue where some navigation landing page (NLP) tiles, when navigating to extensions that required route parameters (queryParameters), the parameters did not pass as expected, resulting in loading issues. (UUX-46879)
-
Fixed an issue where the Retry button on the pop-up blocker did not redirect the user to the right location when user tried to navigate to an SSO. (UUX-47523)
-
Fixed an issue on the Fund transfer page where the Memo field had multiple IDs for the element, resulting in screen readers reading the field name twice. (UUX-47360)
-
Fixed an issue on the Secure Access Code (SAC) page where extra space was rendered at the top. (UUX-46709)
-
Fixed an issue on the Reset password and Forgot password pages where after selecting Submit, the target page loaded but the page was not announced by screen readers. (UUX-35686)
-
Fixed an issue where special characters were not displayed correctly in Action Links on the Dashboard Home page and Mobile Thumb Bar.
Note
Action Links are only available to FIs that are early adopters of Composable Dashboard.
(UUX-46059)
-
Updated the field label for end users to enable biometric authentication to Biometrics on the Security Preferences page.
(UUX-47125)
-
Fixed an issue where mobile menu buttons did not use the correct color when the button was focused. (UUX-46895)
-
Fixed an issue related to accessibility of the calendar and select dropdown, by updating the underlying element code to provide a better experience for users who rely on assistive technology.
(TCT-2799)
-
Fixed an issue with iOS devices where the mobile app stopped functioning when users attempted to upload a video attachment within a message. The option that is presented when users select Attach a file has been renamed from Take Photo or Video to Take Photo.
(UUX-47703)