Reporting is a feature set within Q2 Console that provides information about digital banking engagement and performance data in real-time. Use Generated Reports within Console Reporting to obtain useful information and analyze the data you need.
Generated Reports includes two sections. The Generate report tab lists available reports you can generate. The Reports tab allows you to track the status of generated reports, download completed reports once they've finished processing, and regenerate any reports that couldn't be created.
To view and use Generated Reports in Q2 Console Reporting, you'll need specific rights (permissions) assigned to you in Q2 Console Administration. CSR rights are configured on the Administration > CSR Roles page in Q2 Console.
For more information on setting up Generated Reports entitlements in Q2 Console, see the "Generated Reports rights" section of Rights for CSR Roles in Q2 Console.
Select Generate report to view a list of available reports.
You can currently generate the following reports:
Note
This list isn't exhaustive, and your FI may not have some of the reports enabled. Additional reports may be added in the future.
Set and update the search parameters on a report to retrieve the most accurate, specific, and helpful information. Each report has its own individual search parameters.
Note
Retrieving too much data can cause a report to fail to generate. Whenever possible, limit potential results returned using available search parameters.
Most Generated Reports in Q2 Console have date parameters (Start Date and End Date) that allow for a specific date range to be selected when pulling data. Audit data is available beginning January 2024 and onwards for most FIs, but specific date availability may vary. When selecting the Start Date and End Date parameters, the calendar will define how far back data is available.
Reports using only the date parameter will return data in Universal Coordinated Time (UTC) when the data is stored. Reports using only the date parameter will display timestamps according to the FIs time zone within the 3 day draw-down period, while the data beyond 3 days will be returned in Universal Coordinated Time (UTC). This allows Q2 to convert the timestamps according to the time zone of the user's browser and return the data accordingly.
The Reports tab on the Generated Reports page lists reports that have been generated. It will be blank if no reports have been created.
Once a report is generated and appears in the Reports tab, a corresponding report status shows next to it. The report status updates every minute. The report will continue to generate if you move to another page in Q2 Console.
Note
Closing a browser tab or browser window will not cancel the report generation process.
Report statuses include:
-
Processing—the report is being generated and is not yet complete.
-
Complete—the report has generated and is ready for viewing.
-
No data—the report been generated and no data is available.
-
Failed—the report could not be generated.
A notification appears when the report is finished. This notification appears regardless of where you are in Q2 Console.
Once a report has been generated and is ready for viewing (in Complete status), you can download the report as a comma-separated-value (CSV) file or a PDF file.
To download a report, select either CSV or PDF from the Action column.
Note
The downloaded PDF file is formatted for ease of viewing, but it cannot be audited. Exporting to a PDF is not available for all reports.
The following table provides more information on terms used when indicating the UI Source or Channel in which a past audit action occurred.
These terms may appear within the following reports:
-
Audit Investigation Report
-
Auditing Summary Report
-
User Activity Report
Table 16. Explanations of UI Sources or Channels
|
UI Source (Channel) term |
Definition |
|---|---|
|
Internet |
Audit events that occurred in digital banking. |
|
Voice |
Audit events that occurred in voice banking. |
|
Back Office |
Audit events that occurred in platform back office products, such as User Management, Reporting, Administration, and Q2 Co-Pilot. |
|
Merchant Services |
Audit events that occurred in Merchant Services, a supplemental feature of Q2voice for merchant verification. This feature allows for the recipient of payments (by credit card, purchase orders, etc.), for obtaining sales information from the merchant, for receiving authorization for the transaction, for collecting funds from the bank in which issued the credit card, and for sending payment to the merchant. |
|
Fax Services |
Audit events that occurred in Fax Services, a supplemental feature of Q2voice for fax requests. |
|
Notification Services |
Audit events that occurred in Q2's notification service to send SMS, email, push and/or Secure Messaging alert notifications, as well as Secure Access Codes (SACs). |
|
Q2Api |
Audit events related to Backend APIs used by Q2 products and services, as well as Q2 automated processes. |
|
Text Banking |
Audit events that occurred in text banking. |
|
Open Banking |
Audit events that occurred in Direct Payables, a solution that allows commercial customers to originate and send payment file transactions to the Q2 platform using an accounting system integration. NoteCurrently, this product is not generally available to all FIs. |
The following table provides more information on terms used when describing the category in which the audit action occurred.
These terms may appear within the following reports:
-
Audit Investigation Report
-
Auditing Summary Report
Table 17. Audit Category terms and definitions
|
Audit Category |
Audit Category definition |
|---|---|
|
Account |
Audit events related to retrieving and updating accounts, text banking, and transaction requests to and from the FI's core provider (if applicable). |
|
Actions executed from Q2API |
Audit events related to other Q2 products or applications, such as Experience Builder (Q2 Config) and internal tooling. |
|
Alerts |
Audit events related to retrieving, managing and generating of account alerts, history alerts, transaction alerts, and date alerts. |
|
API |
Audit events related to back-end Q2 services that do automation or support another Q2 product. Examples include creating a Group, Customer, User, or Login for Interactive Test Drive or Online Account Opening, closing accounts (if applicable), creating and verifying microdeposits, associating an account to User or Customer, and executing a stored procedure or back-end request. |
|
Audit |
Audit events related to the loading of a digital banking session. |
|
Authentication |
Audit events related to authenticating the digital banking session. |
|
Bill Payment |
Audit events related to Bill Pay integration in digital banking. |
|
Cloud Lending workflows |
Audit events related to Cloud Lending integration. |
|
Console Administration |
Audit events related to retrieving and managing Q2 Console Administration CSR Users. |
|
Corporate |
Audit events related to corporate banking features and functionality. |
|
Corporate Csr |
Audit events related to retrieving and managing policy dashboard updates by a CSR user. |
|
CSR Administration |
Audit events related to CSR logging in to back office applications, retrieving and managing CSR Users, and retrieving and managing CSR Roles. |
|
Customer |
Audit events related to retrieving and managing Customers, Users, and Login profiles, subsidiaries, rights and entitlements, eStatement profiles, forms, Secure Access Codes (SACs) and targets, alerts, retrieving transactions, text banking, and interactive test drive from digital banking and/or User Management. |
|
Dashboard |
Audit events related to retrieving and managing Dashboard elements or widgets within Q2central. |
|
Group |
Audit events related to retrieving and manage Groups in User Management. |
|
Information Reporting |
Audit events related to commercial (corporate) banking's Information Reporting. |
|
Marketing Message |
Audit events related to Marketing Messages (System Notifications, ads, interstitial pages, etc.). |
|
Messaging |
Audit events related to Secure Messaging from digital banking and/or the back office applications. |
|
Open Banking |
Audit events related to Direct Payables. |
|
Patrol |
Audit events related to Secure Access Code (SAC) tokens for Q2 Patrol. |
|
Processing |
Audit events related to processing transactions. |
|
PFM |
Audit events related to Contextual Personal Finance Management (cPFM). |
|
Q2assist |
Audit events related to Q2 Co-Pilot. NoteThis category was formerly used by Q2assist before it was replaced by Q2 Co-Pilot. |
|
Q2associate |
Audit events related to the Q2associate application. |
|
Reporting |
Audit events related to reports in back office. |
|
Roles |
Audit events related to managing CSR Roles. |
|
SelfService |
Audit events related to using Self Service Forms. |
|
Single Signon Events |
Audit events related to single sign-on (SSO) with Q2 products or other third-party products. |
|
Software Development Kit |
Audit events related to products and functionality available through the SDK. |
|
System Administration |
Audit events related to retrieving and managing additional Q2 Console Administration features, including cut-off hours or holidays, password policy, marketing messages, fee plans, group access mapping (GAM) teams, and Exchange Rate Tier Management. |
|
Templates and Recipients |
Audit events related to retrieving and managing templates and recipients. |
|
Transactions |
Audit events related to retrieving, drafting, authorizing, canceling, and processing transactions, as well as validating tokens for transaction authorization, risk-fraud analytics, Remote Deposit Capture, and statements. |
|
Transaction Codes |
Audit events related to retrieving and managing the transaction code configurations between digital banking and the FI's core by using the back office. Also includes audit events related to voice banking. |