Examples of Affected Accounts in a sentence
Except as set forth above, a Liquidating Fund Termination or a CIC Fund Termination shall not otherwise affect the Plan, and in particular shall have no effect on any Accounts other than the Affected Accounts.
In the event of a Liquidating Fund Termination or a CIC Fund Termination, the value of the Affected Accounts of the Affected Participants shall be paid in a lump sum no later than the last day of the calendar year in which the Liquidating Fund Termination occurs or, if later, the last day of the first calendar year in which the payment is administratively feasible.
Except as set forth above, a Liquidating Fund Termination shall not otherwise affect the Plan, and in particular shall have no effect on any Accounts other than the Affected Accounts.
In the event of a Liquidating Fund Termination, the value of the Affected Accounts of the Affected Participants shall be paid in a lump sum no later than the last day of the calendar year in which the Liquidating Fund Termination 9 occurs or, if later, the last day of the first calendar year in which the payment is administratively feasible.
The Transaction Monitoring Program was supported by processes and systems (including the FCP) designed to enable CBA to monitor transactions across CBA accounts, including the Affected Accounts.
From 20 October 2012 to 12 October 2015, Automated TM Alerts were not always generated as intended, either at all or for a period of time, in respect of778,370 accounts (together, the Affected Accounts), which accounts were otherwise intended to be subject to account-level automated transaction monitoring through the FCP.
CBA contravened s 82(1) of the AML/CTF Act from 20 October 2012 to 12 October 2015, by failing to comply with provisions of Part A of its Program relating to transaction monitoring in respect of the Affected Accounts as identified in paragraphs49 to 53 of the SAFA.
However, more should have been done to investigate its impact on its transaction monitoring of the Affected Accounts and fix the issue sooner than was done.
As set out in paragraph52 above, CBA rectified the computer coding error on or about 19 September 2014, but did not ensure that the Affected Accounts were each subject to account level automated transaction monitoring until 12 October 2015.
For a period of just under 3 years, CBA was not undertaking the intended level of transaction monitoring on the Affected Accounts, having regard to the need to identify, mitigate and manage its ML/TF risk, as reflected in its Transaction Monitoring Program.