Obligación de información Sample Clauses

Obligación de información. El Cliente notificará inmediatamente por escrito a Liferay (o, en su caso, al Socio Comercial) en el supuesto de que el número de Unidades que efectivamente hubiera utilizado el Cliente superara el número de Unidades por las que el Cliente hubiera abonado los correspondientes Honorarios. En dicha notificación, el Cliente incluirá el número de Unidades adicionales así como la fecha o fechas en las que dichas Unidades hubieran sido utilizadas por primera vez. Liferay (o el Socio Comercial, en su caso) facturará al Cliente los Servicios correspondientes en función de dichas Unidades, y el Cliente abonará el importe de tales Servicios en un xxxxx xxxxxx de treinta (30) xxxx desde la fecha de recepción de la factura en cuestión. Los Honorarios correspondientes a dichas Unidades adicionales serán calculados de conformidad con las tarifas de Liferay vigentes a la fecha en la que el Cliente realizara la notificación prevista en la presente Cláusula 5.1.
AutoNDA by SimpleDocs
Obligación de información y verificación 5.1 Obligación de información El Cliente notificará inmediatamente por escrito a Liferay (o, en su caso, al Socio Comercial) en el supuesto de que el número de Unidades que efectivamente hubiera utilizado el Cliente superara el número de Unidades por las que el Cliente hubiera abonado los correspondientes Honorarios. En dicha notificación, el Cliente incluirá el número de Unidades adicionales utilizadas así como la fecha o fechas en las que dichas Unidades hubieran sido utilizadas por primera vez. Liferay (o el Socio Comercial, en su caso) facturará al Cliente los Servicios correspondientes en función de dichas Unidades, y el Cliente abonará el importe de tales Servicios en un xxxxx xxxxxx de treinta 5.2 Verificación Previa solicitud al respecto y, salvo que previamente se hubiera acreditado cualquier incumplimiento, con una frecuencia no superior a una vez cada doce meses, el Cliente certificará por escrito a favor de Liferay –escrito que habrá de ser suscrito por un representante debidamente autorizado del Cliente que tuviera conocimiento efectivo al respecto– el número de Unidades efectivamente utilizadas por el Cliente, así como el hecho de que la utilización por parte del Cliente de tales Servicios es acorde con los términos del presente Contrato. Durante la vigencia del presente Contrato, así como posteriormente durante un (1) año adicional, Liferay o la persona o personas designadas por Liferay podrán auditar las instalaciones y los libros y registros del Cliente a efectos de verificar el cumplimiento por el Cliente del presente Contrato. Dicha auditoría no podrá tener lugar más de una vez cada doce
Obligación de información y verificación 5.1 Obligación de información El Cliente notificará inmediatamente por escrito a Liferay (o, en su caso, al Socio Comercial) en el supuesto de que
Obligación de información y verificación

Related to Obligación de información

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • How Do I Get More Information? This Notice summarizes the Action, the terms of the Settlements, and your rights and options in connection with the Settlements. More details are in the Settlement Agreements, which are available for your review at xxx.XxxxxxxxxXxxXxxxxxxxxXxxxxxxxxx.xxx. The Settlement Website also has the Second Amended Complaint and other documents relating to the Settlements. You may also call toll-free 0-000-000-0000 or write the Claims Administrator at: Financial Aid Antitrust Settlements, c/o Claims Administrator, 0000 Xxxx Xxxxxx, Xxxxx 0000, Xxxxxxxxxxxx, XX 00000. To: Settlement Class Member Email Address From: Claims Administrator Subject: Notice of Proposed Class Action Settlement – Xxxxx, et al. x. Xxxxx University, et al. Please visit xxx.XxxxxxxxxXxxXxxxxxxxxXxxxxxxxxx.xxx for more information. • The Court has preliminarily approved proposed settlements (“Settlements”) with the following ten schools: Brown University, the University of Chicago, the Trustees of Columbia University in the City of New York, Trustees of Dartmouth College, Duke University, Emory University, Northwestern University, Xxxxxxx Xxxxx Xxxx University, Vanderbilt University, and Yale University (collectively the “Settling Universities”). • The Court has also preliminarily approved a class of students who attended one or more of the Settling Universities during certain time periods. This is referred to as the “Settlement Class,” which is defined in more detail below.

  • Inside Information Each of the Finance Parties acknowledges that some or all of the Confidential Information is or may be price-sensitive information and that the use of such information may be regulated or prohibited by applicable legislation including securities law relating to insider dealing and market abuse and each of the Finance Parties undertakes not to use any Confidential Information for any unlawful purpose.

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? Yes

  • EDD Independent Contractor Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the state.” The term is further defined by the California Employment Development Department to refer specifically to independent Contractors. An independent Contractor is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Conhecimento da Lingua O Contratado, pelo presente instrumento, declara expressamente que tem pleno conhecimento da língua inglesa e que leu, compreendeu e livremente aceitou e concordou com os termos e condições estabelecidas no Plano e no Acordo de Atribuição (“Agreement” xx xxxxxx).

  • Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? No

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!