Record the lifecycle before selecting components
Map registration, account provisioning, status changes, evaluation calculations, operator review and the reporting required by the business. State which environment each account uses and which system owns each decision. Any simulated or live workflow should be clearly defined in the actual product and provider arrangements.
Evaluation rules and account-state logic may sit outside the platform or depend on integrations. Confirm the proposed implementation rather than treating them as native MT5 features or assuming every product named in a catalogue is included.
Turn the lifecycle into a delivery scope
| Area | Output to agree | Acceptance question |
|---|---|---|
| Account provisioning | Approved state model and supported platform actions | Does one approved request create the intended account exactly once? |
| Rule processing | Inputs, calculation timing and review ownership | Can a result be explained using recorded events? |
| Business-system integration | CRM/back-office actions and reconciliation | Do account state and business records agree? |
| Operations | Permissions, alerts and incident escalation | Can an operator resolve a failed workflow with the handover? |
Platform access, product permissions and any external commercial services are project-specific dependencies. They are not established by the existence of an integration or a public service description.
Validate exception handling before launch
Illustrative workflow: an approved provisioning request times out before the business system receives confirmation. The test checks how the system establishes the actual account state before retrying, so an uncertain response does not lead to duplicate records.
Also review status corrections, delayed input data and operator overrides where they are part of the approved product. Record the decision trail and the responsible role. TSG Server can scope the infrastructure and integration work around these defined workflows; the project proposal should identify the components and responsibilities explicitly.