iConnectData Invoices and Payment Center: Understanding the Billing Workflow
The Payment Center in iConnectData is the area used for billing-related functions such as retrieving invoices, reviewing credit information and, for eligible accounts, making electronic payments to Comdata.
The most important distinction is that not every ICD account has the same payment options.
Comdata states that Pay On Account is available when the customer account is configured for Electronic Bill Pay (EBP). Accounts using a different payment method may not see that module at all.
So if one administrator sees online payment controls and another does not, that difference can be intentional configuration—not necessarily a broken account.
My Invoices Is the Statement Library
Current Comdata documentation directs administrators to:
Payment Center > My Invoices
for invoice and statement retrieval.
The October 2025 instructions say ICD can search available reports using fields such as report type, account code, customer ID, date range and report name/code.
This makes My Invoices more than a single “current bill” screen.
It operates as a searchable repository of available billing documents.
The Date Search Has Limits
Comdata’s current invoice-search documentation says available dates can extend through the previous 14 months, while an individual start/end-date search is limited to a 45-day range.
That means someone searching for a much older statement may not be able to retrieve it simply by expanding the same date filter indefinitely.
Likewise, searching a full year at once may fail even though the underlying months still exist.
The solution is to use appropriately sized search windows.
Invoice, Data and Management Reports Are Different Categories
Within My Invoices, Comdata documents report-type options including:
- invoice;
- data;
- management;
- or all report types for which the user is registered.
The available report names depend on the account and user registration.
This distinction is useful because a billing administrator may be looking for detailed supporting data rather than just the amount due.
A generic “download invoice” instruction can miss those related reconciliation materials.
Searching Does Not Automatically Mean Paying
Retrieving an invoice and paying the account are separate ICD tasks.
A user can use My Invoices to locate reports even if the account does not have Electronic Bill Pay enabled.
Online payment, by contrast, depends on the account’s payment configuration.
This is another reason not to treat “Payment Center” as a single button with one universal workflow.
How Pay On Account Works
For eligible Electronic Bill Pay customers, Comdata documents the payment entry point as:
Payment Center > Pay On Account
The user is then taken to the Pay My Accounts workflow.
Comdata notes an important restriction: a user cannot initiate payment on an invoice on the same date that invoice is generated.
That can explain why a newly created invoice appears in the system but is not immediately payable through the expected workflow.
A Bank Account Must Be Configured for Electronic Payment
First-time electronic-payment users may need to establish a payment method.
Comdata’s Payment Center documentation describes adding a checking or savings account, including bank-account information and acceptance of the authorization agreement.
This bank account is used to pay the Comdata account.
It should not be confused with a Fintwist cardholder linking a personal bank account to receive money from a paycard.
Those are opposite money flows:
ICD Payment Center: company bank account → Comdata invoice
Fintwist cardholder transfer: paycard → cardholder’s bank account
Keeping the flows separate prevents substantial confusion.
Payment Amount Does Not Have to Mean “Pay Everything”
Comdata’s documented payment workflow shows the current amount due and allows the user to enter a different payment amount within documented limits.
The payment date in the described workflow is the current date rather than a freely selected future date.
It also documents a restriction of one payment per day on each account.
Organizations should therefore avoid waiting until the last possible moment to discover how their particular payment setup behaves.
Processing Hours Can Affect What You See
Comdata’s payment instructions include an operational warning concerning overnight activity.
The documentation notes that total amounts displayed during certain late-night processing hours may not immediately reflect all activity and recommends initiating payments during the normal processing window identified in the guide.
This is a useful example of information gain beyond “click Pay.”
An amount that appears temporarily stale does not automatically mean an invoice was calculated incorrectly.
Timing within the processing cycle can matter.
Payment Activity Is a Separate Audit Trail
After payments are initiated, ICD provides a Payment Activity area.
Comdata says administrators can filter activity across associated active accounts, review only payments initiated by the current user, or focus on an individual account. A Reference ID can be opened for additional payment details.
That makes Payment Activity useful for questions such as:
- Was a payment submitted?
- Which account was it applied to?
- What is the transaction status?
- Which payment should accounting investigate?
This is more useful than repeatedly resubmitting a payment because someone is unsure whether the first request worked.
Available Credit Is Not the Same as the Invoice Amount
iConnectData can also show available credit information.
Comdata explicitly warns administrators not to remit payment based solely on the available-credit balance displayed in ICD. The company says that information is for review and that customers receive an invoice for payment.
This distinction is especially important for users accustomed to consumer credit-card websites where a dashboard balance may look like an obvious payment target.
In ICD:
available credit answers a credit-capacity question.
invoice answers a billing question.
They should not automatically be treated as the same number.
Different Accounts Can Produce Different Payment Center Experiences
ICD supports several Comdata product environments, and the main navigation is permission- and configuration-dependent.
Comdata currently documents Payment Center across proprietary fleet, Mastercard fleet and virtual-payments environments, but the available functions can differ.
This explains why screenshots found online may not perfectly match your own account.
The correct question is not:
“Why doesn’t my iConnectData look exactly like this screenshot?”
It is:
“Is my user and account configured for this particular billing function?”
A Better Reconciliation Workflow
A practical business process can separate the stages:
1. Retrieve the invoice.
Use My Invoices and the appropriate report type.
2. Review supporting detail.
Identify related management or data reports when required.
3. Confirm the amount through the invoice rather than relying only on available credit.
4. Determine whether Electronic Bill Pay is enabled.
5. Submit the payment through Pay On Account when available.
6. Review Payment Activity for confirmation and status.
That sequence creates a clearer audit trail than treating every Payment Center screen as interchangeable.
Where Reporting Fits
Invoices answer billing questions, but operational transaction analysis may belong elsewhere.
If the administrator is investigating transaction activity, card listings or account summaries rather than billed statements, reportQ or Real Time Transaction History may be the better tool.
Our iConnectData reportQ and Reporting guide explains that side of ICD.
Together, the two articles separate three jobs that are often blurred into one:
transactions → reporting
statements → invoices
remittance → payments
That is a much more accurate model of iConnectData than describing it simply as a “Comdata login portal.”