iConnectData reportQ: How Reporting Differs From Real-Time Transaction History
iConnectData contains more than one way to inspect account activity.
The two concepts most likely to be confused are reportQ, which Comdata describes as a collection of preformatted Quick Reports, and Real Time Transaction History, which is designed to search authorized, posted, declined and other transaction statuses directly.
The distinction matters because an administrator looking for an operational transaction from today may need a different tool from someone producing a reusable card-listing or account-activity report.
Both exist within iConnectData, but they solve different reporting jobs.
What reportQ Is
Comdata’s current June 2026 documentation describes reportQ as a reporting area containing preformatted reports for reviewing specific account information.
Examples referenced by Comdata include card listings and transaction-oriented summaries.
Unlike a blank reporting environment where the user builds every field manually, reportQ starts from defined report formats.
The user chooses a report, supplies the available criteria and then generates the output.
Where reportQ Appears in iConnectData
The currently documented navigation path is:
Reporting > reportQ
Comdata’s June 2026 instructions then direct users to the Quick Reports area, where they select the desired report and enter the report criteria.
The Reporting menu itself is permissions-dependent.
If one administrator can see reportQ and another cannot, the difference may come from user access rather than a different website.
Comdata’s general ICD navigation documentation explicitly says available menu functions depend on the user’s permissions.
PDF vs Excel Output
Current reportQ documentation says output availability depends on the individual report.
A report may support:
- View Report (PDF);
- Excel Download;
- or only one of those formats.
After the report is submitted, it enters the Report Status and History area. A report that requires time to generate can temporarily show as running before a Download link becomes available.
This makes reportQ appropriate not just for viewing information on screen but also for exporting account information for internal analysis or reconciliation.
Not Every reportQ Report Is Available to Every User
Comdata documentation for several product families emphasizes that report availability can depend on the user’s setup.
For example, its Virtual Payments reporting material states that access to individual Quick Reports is determined by user configuration and advises customers to contact Comdata when a report they should have is unavailable.
So if a report name shown in documentation does not appear in your ICD account, the likely explanations include:
- product differences;
- account setup;
- registration;
- permission differences.
Creating a second ICD login will not necessarily solve any of those.
What Real-Time Transaction History Does Instead
Real Time Transaction History is accessed under:
Manage > Transactions > Real Time Transaction History
Comdata says the feature can show authorized, posted and declined transactions, along with other transaction statuses. It can also display information about certain declines and possible corrective actions.
That makes it more operational than many preformatted reports.
An administrator investigating why a card was declined fifteen minutes ago may find this tool more directly useful than running a broad monthly report.
Search Criteria in Real-Time Transaction History
Comdata’s documentation describes filters including:
- account code;
- customer ID;
- card number or other search values;
- transaction status;
- transaction or posted date;
- date range.
It currently documents statuses including Authorized, Posted, Declined, Credit and Disputed. The results can also be downloaded to Excel.
This means the feature can serve both rapid investigation and later analysis.
Why “Authorized” and “Posted” Should Not Be Treated as Synonyms
An authorization shows that a transaction passed through an authorization stage.
A posted transaction represents a later accounting state.
That distinction matters when someone asks why a card balance or invoice does not yet match an authorization they just observed.
Real-Time Transaction History exposes multiple statuses precisely because payment transactions do not all move through the system in one instantaneous final step.
Administrators should identify the status before assuming that every authorization is already final settlement.
reportQ Is Used Across More Than One Comdata Product
iConnectData is not restricted to Fintwist payroll-card administration.
Comdata currently lists reportQ among the tools available for proprietary fleet, Mastercard fleet, virtual payments and other commercial-card environments.
The exact report families can therefore differ substantially.
A fleet administrator may care about transaction, card and fuel-related reporting.
A virtual-payments administrator may need vendor or virtual-card reporting.
This broader scope is one reason the general term “iConnectData report” can refer to very different data.
reportQ vs Business Intelligence
Comdata’s main ICD navigation documentation also distinguishes reportQ from Business Intelligence.
The general description positions reportQ around preformatted account reports while Business Intelligence can contain custom reporting associated with the account.
That is another useful distinction:
reportQ = predefined reporting
Business Intelligence = potentially more customized reporting
Availability again depends on the account.
How to Choose the Right Tool
Use reportQ when:
- you know the type of standardized report you need;
- you want a repeatable PDF or Excel output;
- you are reviewing card listings or defined account summaries.
Use Real Time Transaction History when:
- you are investigating a specific transaction;
- a card was recently declined;
- you need to filter by transaction status;
- you need more immediate operational visibility.
Use My Invoices when:
- the question is specifically about billed statements or invoice reports.
Our iConnectData Invoices and Payment Center guide covers that third workflow separately.
Missing Reports Usually Point to Access, Not Search
If you know a report exists but cannot see it, first verify your ICD permissions and product configuration.
Comdata’s current materials repeatedly tie visibility to the user’s setup.
That is a much stronger troubleshooting hypothesis than searching Google for another “iConnectData reporting login.”
There is one portal, but different users can have different reporting access inside it.
