A transaction question should not begin with the assumption that every apparent discrepancy is a system error. The investigation should first establish which account context, time period and operational object are involved.
Current iConnectData resources include real-time transaction-history functions as part of account management.
Step 1: identify the exact question
Are you investigating:
- one transaction?
- a card’s activity?
- a vehicle or driver-related record?
- a discrepancy between a report and a transaction view?
The answer determines the next source of information.
Step 2: confirm context
Check the relevant account code, customer ID and available date range before concluding that activity is missing.
Step 3: separate activity from reporting
A transaction-level view and a preformatted report can serve different purposes. Do not compare them as though they must always expose the same fields or timing logic.
Step 4: escalate with evidence
If escalation is necessary, provide the relevant non-sensitive identifiers and context through the verified support channel. Never publish or send credentials through an unrelated editorial website.
Internal Link Suggestions:
/iconnectdata-account-hierarchy//iconnectdata-reporting//iconnectdata-reporting-problems/