An iConnectData user can sometimes have access to more than one organizational context. In that situation, the selected account code or customer ID can affect the information and functions being viewed.
This matters because an apparent missing card, report or transaction may be a context problem rather than a data problem.
Account hierarchy is a working context
Documentation describes structures involving a single account code with multiple customer IDs or multiple account codes with multiple customer IDs. The user should confirm the relevant selection before beginning a task.
A practical pre-task check
Before:
- ordering or maintaining cards;
- reviewing activity;
- running reports;
- examining account information;
confirm the organizational scope currently selected.
Why this prevents bad decisions
A correct report for the wrong account is still operationally misleading. The same applies to transaction investigations. Context should be checked before comparing outputs or escalating an apparent discrepancy.
The account-context checklist
Ask:
- Which account code should this task use?
- Which customer ID is relevant?
- Is the expected card or activity associated with that context?
- Are the selected dates and filters also correct?
- Does the user’s permission match the intended task?
Internal Link Suggestions:
/iconnectdata-system-guide//iconnectdata-reporting//iconnectdata-transaction-history/