An iConnectData administrator looking for financial activity can encounter several different tools:
reportQ
Real Time Transaction History
My Invoices
Pay On Account
They may all involve money, but they answer different questions.
Comdata’s current documentation separates reporting, operational transaction history and invoicing into distinct workflows.
Choosing the right one can save considerable time.
reportQ: Standardized Account Reporting
Comdata’s June 2026 documentation describes reportQ as a collection of preformatted Quick Reports.
The current path is:
Reporting > reportQ
The user selects a report, enters its criteria and can receive PDF or Excel output when that format is supported by the chosen report.
Reports that take time to generate appear in Report Status and History before a download becomes available.
What reportQ Is Good For
reportQ is useful when the organization needs a defined report format rather than a one-off investigation.
Examples in current Comdata material include reporting around:
- transactions;
- card listings;
- account activity;
- other product-specific data.
The exact report catalog depends on the account.
Real Time Transaction History: Operational Investigation
Real Time Transaction History serves a different job.
Comdata says it can display:
- authorized transactions;
- posted transactions;
- declined transactions;
- credits;
- disputed transactions.
Searches can be filtered by account code, customer ID, card or another identifier, transaction status and date.
That makes it more useful when someone asks:
What happened to this specific transaction?
rather than:
Give me a standard report covering this account.
Authorized Does Not Mean Posted
Payment systems can show a transaction at different stages.
An authorization indicates that a transaction passed through an authorization process.
A posted transaction reflects a later state.
Comdata exposes these statuses separately in Real Time Transaction History.
Therefore, an administrator should identify the status before concluding that a current authorization already equals final posted activity.
Excel Downloads
Comdata’s Real Time Transaction History documentation allows results to be downloaded to Excel.
The exported information can include more fields than the screen display.
That makes the tool useful both for direct troubleshooting and follow-up analysis.
My Invoices: Billing Documents
Invoices are handled separately.
Current Comdata guidance directs users to:
Payment Center > My Invoices
The search can use criteria including:
- report type;
- account code;
- customer ID;
- start and end dates;
- report name/code.
The documentation says available dates can reach back through the previous 14 months, while an individual start/end-date search is limited to a 45-day range.
That matters when retrieving older statements.
Invoices Are Not reportQ Reports
A common conceptual error is to treat every downloadable ICD document as the same type of report.
They serve different jobs.
reportQ helps analyze standardized account information.
My Invoices retrieves billing documents.
Someone reconciling a monthly bill may use both, but one does not replace the other.
Pay On Account: Remitting Money
Payment is another separate step.
Comdata says Pay On Account is available when the account is configured for Electronic Bill Pay.
If an account uses a different payment method, the user may not see the module.
The documented path is:
Payment Center > Pay On Account
This moves from reviewing what is owed to actually remitting payment.
Why a Missing Pay Button May Be Normal
If an invoice is visible but Pay On Account is not, the account may simply not be configured for EBP.
That is an account-configuration question.
It is not necessarily:
- a browser bug;
- an iConnectData outage;
- an incorrect login;
- a missing invoice.
This is a good example of why ICD troubleshooting should start with the function that is missing, not with generic login advice.
Fintwist Employer Reports Are Another Layer
Fintwist employer administration adds program-specific reporting inside the broader ICD ecosystem.
Comdata documents card-listing, load and daily-invoice reports for Fintwist under Branded Debit.
Those reports are useful for the payroll-card program but should not be mistaken for every report available across iConnectData.
A fleet customer can see a different reporting universe from a Fintwist administrator.
Choosing the Right Tool
Use reportQ when:
- you need a standardized report;
- you want defined account or card information;
- you want PDF or Excel output from a Quick Report.
Use Real Time Transaction History when:
- investigating a specific transaction;
- checking whether something is authorized, posted or declined;
- diagnosing recent account activity.
Use My Invoices when:
- retrieving billing statements;
- reviewing charges on the Comdata account.
Use Pay On Account when:
- an invoice is ready to be paid;
- the account is configured for Electronic Bill Pay.
These are four distinct jobs.
Permissions Remain the Final Filter
Even when a function exists in the documentation, the user may not have access.
Comdata states that main-menu options depend on permissions.
Therefore, when a tool is missing:
- confirm the correct company/account;
- confirm the product supports the function;
- confirm the user has appropriate access;
- confirm any required account configuration, such as EBP.
Only then does it make sense to treat the absence as a technical problem.
Why This Structure Matters
Calling iConnectData simply “a login portal” hides most of its information architecture.
A better model is:
Manage → operations
Reporting → analysis
Payment Center → invoices and payment
Resource Center → documentation
Once administrators understand the ownership of each task, ICD becomes considerably easier to navigate.