Contract dates and versions: retaining evidence

The essentials

Terms change between entities and dates. A page date does not establish the current version of a downloaded PDF. Distinguish publication, effective date and personal acceptance where stated.

Understand the mechanism, not just the definition

Read conditions alongside entity, date, version and scope. A current PDF may differ from an earlier contract, and announced changes may take effect later. Keep the document and access date rather than only a link that may later change, while protecting personal information.

Example and verification

Keep document name, entity, version, date, URL and accepted copy. When support sends another, ask which applies and since when. Do not silently replace earlier clauses with an updated general page.

Worked case, step by step

Rules published today take effect in two weeks. Identify the current version and transition. Compare eligibility, amounts, schedule and cancellation. Do not assume unhighlighted provisions remain unchanged; examine incorporated references and appendices as well.

What to verify when applying this

Compare documents from equivalent stages and explain scope. An IB agreement governs the partner relationship, not the customer contract. Do not transfer its territories and permissions into undocumented trading protections.

Practice: verify it in your environment

Learn by observing the process and keeping its data. Complete this practice in demo or using documentation, without sending real orders or adding capital for the exercise. Record differences between the example and your account specifications.

1. Keep document, URL, entity, version, publication and effective date.
2. Compare appendices and references, not merely a promotion’s opening paragraph.

Test your understanding

Try the question before revealing the answer. Justify the conclusion and its assumptions rather than memorizing a number.