Reporting of Errors Sample Clauses

Reporting of Errors. You must promptly view all E–statements, and immediately notify Processor in writing of any errors. Your written notice must include: (i) Merchant name and account number; (ii) the dollar amount of the asserted error; (iii) a description of the asserted error; and (iv) an explanation of why you believe an error exists and the cause of it, if known. That written notice must be received by Processor within 30 calendar days after the E–statement containing the asserted error is first made available. Your failure to notify Processor of any error within 30 days constitutes a waiver of any claim relating to that error. You may not make any claim against Processor for any loss or expense relating to any asserted error for 60 calendar days immediately following Processor’s receipt of your written notice. During that 60 day period, Processor will be entitled to investigate the asserted error and we will notify you of the results of our investigation.

Reporting of Errors. Client acknowledges that it is not possible for Services provided by Bank hereunder to be free of operator, program or equipment error, and that errors in processing and compiling Account data may occasionally occur, requiring adjustments. As such Client agrees to review and verify all results and to maintain adequate controls for insuring both the accuracy of data transmissions and the detection of errors. Unless otherwise required by law Bank’s sole responsibility for reporting errors caused by Bank will be to reprocess information and reports for the applicable period and to submit corrected reports at its own expense to Client.

Reporting of Errors. Subscriber shall document and promptly report to Sectigo any errors or malfunctions in the Certificates or SCM. Upon Sectigo’s reasonable request, Subscriber shall assist Sectigo in rectifying such errors or malfunctions.

Reporting of Errors. All errors must be reported via email ▇▇▇▇▇▇▇▇▇@▇▇▇▇▇-▇▇▇▇▇▇.▇▇▇ s When reporting an error, Merchant is required to provide sufficient information that helps identifying the problem.

Reporting of Errors. Reseller shall document and immediately report to Sectigo any errors or malfunctions associated with the Subscription Services. Reseller shall assist Sectigo in rectifying any errors or malfunctions in the Subscription Services upon Sectigo’s reasonable request.

Reporting of Errors. Reseller shall document and promptly report to Comodo any errors or malfunctions associated with the Security Solutions and promptly assist Comodo in rectifying any such errors or malfunctions upon Comodo’s request.

Reporting of Errors. If Customer notifies Supplier in writing that such Covered Software does not operate substantially in accordance with its Documentation, Customer shall provide to Supplier such information and materials as Supplier may reasonably request to document and reproduce such problem and to verify whether any proposed solution corrects such problem. Such information may include a written explanation of such problem, a written description of the operating environment, and (if permitted) a copy of any software program used with the Covered Software. Following the receipt of such information and materials, if Supplier determines that such Covered Software does not operate substantially in accordance with the related Documentation, then Supplier will use reasonable commercial efforts to correct or replace the defective Covered Software.

Reporting of Errors. CUSTOMER will make every effort to comply with sound computer data management principles including, but not limited to notification to Dorado Business Systems in the event of system errors, routine audit and reconciliation to assure the accuracy of entered information, regular review of coding and other data entry procedures and the prompt input of essential information.

Reporting of Errors. Customer shall declare an Error via the Support Helpdesk with the following information: ▪ Customer name ▪ Customer technical contact person's name ▪ Description of the Error and of the behavior of the Software Services when the Error occurred (e.g., the exact error message) ▪ Conditions under which the Error appeared and can be reproduced, including the dataset involved ▪ Measures already taken by Customer to remedy the appearance of the Error, if any ▪ Possible workaround identified by Customer, if any ▪ Error priority (as assessed by Customer) ▪ Error ID# (when specified by Provider). Provider will use reasonable efforts to acknowledge each declaration of Error made via the Support Helpdesk in writing within four (4) hours of receipt of the request during Provider’s normal business hours. Customer will assist Provider to the best of its ability in resolving the Error. This includes granting Provider access to equipment or information of Customer. Any delay on the part of Customer to provide information or assistance will produce corresponding delays in the correction provided by Provider, without the latter’s liability being invoked. If Customer doesn’t provide resonable assistance, Provider may suspend the provision of Maintenance Services. Provider may perform Maintenance Services using remote maintenance software to access Customer’s servers via desktop sharing. Such access will require Customer’s prior express authorization and be limited to a period agreed upon between the Parties. This remote access requires Customer’s activation by entering the code provided by Provider. Customer must isolate/lock all confidential information before granting such access. In order to solve a problem or perform additional configuration, Provider may need to have access to Customer's database. The priority level of an Error is assigned by Provider based on Customer's report. Errors are classified in three categories (Blocking, Major, Minor) according to their priority levels: PRIORITY LEVEL DESCRIPTION 1. Blocking An Error that completely prevents access to or use of the Software Services. 2. Major An Error that disrupts the execution of a main function of the Software Services (the Software Services are accessible and usable in degraded mode). 3. Minor An Error that has limited consequences for the User because the main functions of the Software Services are not impacted (errors that are not major or blocking). Provider will use commercially reasonable efforts to r...