Validity and content of the Order Sample Clauses

Validity and content of the Order. The Customer can submit Orders verbally, electronically in writing or in another manner separately agreed on with the Customer. The Bank may not accept an Order from the Customer before the necessary Customer identifier has been saved in the Bank's data systems. If the Customer is a legal person, it must inform the Bank of its valid LEI. With respect to private persons, the Bank requires that the Customer provides it with the necessary information on his or her nationalities and other necessary additional information. If the Customer is represented by a proxy, the corresponding informa- tion on the proxy must also be made available. The Bank may accept an Order once it has received the necessary information and it has had a reasonable amount of time to update the information into its data systems and to perform all other necessary measures to verify the correctness of the information given. The Bank has the right to send to the Customer written information concerning an Order either electronically through its online banking service, or by post or in another manner separately agreed on with the Customer. The Customer accepts that the use of electronic means of communication involves special risks. For example, the message may not arrive at its destination; the message may fall into the hands of a third party or a third party may alter the content of the message. The Bank is entitled to trust the authenticity and cor- rectness of an Order it has received by electronic means of commu- nication. The content and time of arrival of an Order sent by elec- tronic means of communication is verified from the Bank's data system or fax machine. An Order enters into force once the Bank has obtained sufficient in- formation about it and accepted it as an Order. The Bank must rec- ord the content of a verbal Order in writing, and the Bank is obliged to record its telephone conversations with the Customer related to Orders. The Customer is responsible for the arrival of an Order at the Bank. An Order given by the Customer should include the following:
Sample 1
AutoNDA by SimpleDocs

Related to Validity and content of the Order

  • Review of legality and data minimisation (a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).

  • Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • Delivery and Content of Monthly Bills/Supplementary Bills 10.2.1 The SPD shall issue to SECI hard copy of a signed Monthly Xxxx/Supplementary Xxxx for the immediately preceding Month/relevant period based on the issuance of Energy Accounts along with all relevant documents (payments made by SPD for drawal of power, payment of reactive energy charges, Metering charges or any other charges as per guidelines of SERC/CERC, if applicable. Each Monthly Xxxx shall include all charges as per this Agreement for the energy supplied for the relevant Month based on Energy Accounts issued by RPC or any other competent authority which shall be binding on both the Parties. The Monthly Xxxx amount shall be the product of the energy as per Energy Accounts and the Applicable Tariff. Energy drawn from the grid will be regulated as per the regulations of respective State the Project is located in.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • System Security and Data Safeguards When SAP is given access to Licensee’s systems and data, SAP shall comply with Licensee’s reasonable administrative, technical, and physical safeguards to protect such data and guard against unauthorized access. In connection with such access, Licensee shall be responsible for providing Consultants with user authorizations and passwords to access its systems and revoking such authorizations and terminating such access, as Licensee deems appropriate from time to time. Licensee shall not grant SAP access to Licensee systems or personal information (of Licensee or any third party) unless such access is essential for the performance of Services under the Agreement. The parties agree that no breach of this provision shall be deemed to have occurred in the event of SAP non-conformance with the aforementioned safeguard but where no personal information has been compromised.

  • Notification of Modifications of Licensed Materials From time to time Publisher may add, change, or modify portions of the Licensed Materials, or migrate the Licensed Materials to other formats. When such changes, modifications, or migrations occur, the Licensor shall give notice of any such changes to Licensee as soon as is practicable, but in no event less than sixty (60) days in advance of modification. Such a notice may also be given directly by the Publisher to the Licensee. If any of the changes, modifications, or migrations renders the Licensed Materials substantially less useful to the Licensee, the Participating Institutions or their Authorized Users, the Licensee may seek to terminate this Agreement for breach pursuant to the termination provisions of this Agreement in Section XI, below.

  • Inspection of Goods 8.1 The Buyer shall inspect the goods upon delivery.

  • Notice of Criminal Activity and Disciplinary Actions a. Xxxxxxx shall immediately report in writing to their contract manager when Xxxxxxx has knowledge or any reason to believe that they or any person with ownership or controlling interest in the organization/business, or their agent, employee, contractor or volunteer that is providing services under this Contract has:

  • Security and Validation Procedures The Scheduling Coordinator shall apply to the Meter Data of the Scheduling Coordinator Metered Entities that it represents the security and validation procedures prescribed by the relevant Local Regulatory Authority. If the relevant Local Regulatory Authority has not prescribed any such procedures, the Scheduling Coordinator shall apply the procedures set forth in the CAISO Tariff. Meter Data submitted by a Scheduling Coordinator for Scheduling Coordinator Metered Entities shall conform to these standards unless the CAISO has, at its discretion, exempted the Scheduling Coordinator from these standards.

Time is Money Join Law Insider Premium to draft better contracts faster.