Invoice Queries Sample Clauses

Invoice Queries. 19.1. Where a Customer wishes to query an invoice it will notify The Company in writing within 14 days of receipt of the invoice, setting out the reasons and the amount queried. The Customer shall not be entitled to dispute an invoice where the invoice query has not been submitted in writing to The Company within 14 days of receipt of the invoice, other than for a manifest error contained in the invoice.
Sample 1Sample 2
AutoNDA by SimpleDocs
Invoice Queries. All invoice queries must be notified in writing to Head Office within 72 hours of invoice date.
Sample 1
Invoice Queries. The Hirer should notify CHILLCHASER® LTD of any queries concerning invoices in writing within 7 days of the invoice date. xxxx@xxxxxxxxxxx.xx.xx & xxxxx@xxxxxxxxxxxxxxxxxxxxxxxxxx.xxx
Sample 1
Invoice Queries. Any queries as to the amount of the invoice should be raised, in writing, within seven days of receipt, otherwise the account invoiced will be deemed to be agreed. The Client is not entitled to withhold payment of, or make deductions from, invoices by reason of any claim or alleged claim and all rights of set off are excluded.
Sample 1
Invoice Queries. In the event of an invoice query please contact NHS Shared Business Services Payables Helpdesk in the first instance – Please do not contact SWYPFT staff direct. The SBS helpdesk will forward any messages onto the correct person within SWYPFT. Tel: 0000 000 0000 Website: xxx.xxx.xxx.xx Email: XXX-X.Xxxxxxxx@xxx.xxx (please note this email is for queries only please do not email invoices to this address) If SBS have been unable to resolve your query please email xxxxxxxxxxxx@xxxx.xxx.xx – Your email MUST include your SBS call reference number otherwise we will not deal with it.
Sample 1
Invoice Queries. The Hirer should notify the Owner of any queries concerning invoices in writing within 14 days of the invoice date.
Sample 1

Related to Invoice Queries

  • Invoice Data The Contractor shall report invoice data from each paid or remitted invoice within 30 calendar days after the end of the reporting quarter, including the invoice data on task orders issued through the GSA AAS Business System Portal. (Note: Whatever method the Contractor chooses (e.g., “each paid” or “remitted”) the Contractor must be consistent in their reporting method throughout the term of the OASIS Contract). If no Invoice Data was received during a required reporting period for a specific task order, the Contractor shall report in the “Zero Invoice Data” screen located in the CPRM system for that particular task order. Regardless of contract type, the Contractor shall report the following into the CPRM:

  • Invoice System The Contractor shall submit invoices using State Form A-19 Invoice Voucher, or such other form as designated by DSHS. Consideration for services rendered shall be payable upon receipt of properly completed invoices which shall be submitted to by the Contractor not more often than monthly. The invoices shall describe and document to DSHS’ satisfaction a description of the work performed, activities accomplished, the progress of the project, and fees. The rates shall be in accordance with those set forth in Section 4, Consideration, of this Contract.

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

  • Invoice Detail Contractor’s invoice must be on Contractor’s stationary with Contractor’s name, address, and remittance address if different. Contractor’s invoice must have a date, an invoice number, a purchase order number, a description of the goods or services provided, and an amount due.

  • 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).

  • Invoice Submittal DEO shall reimburse Subrecipient in accordance with Section 6, above. In accordance with the Funding Requirements of s. 215.971(1), F.S. and Section 21 of this Agreement, Subrecipient and its subcontractors may only expend funding under this Agreement for allowable costs resulting from obligations incurred during this Agreement. To be eligible for reimbursement, costs must be in compliance with laws, rules and regulations applicable to expenditures of State funds, including, but not limited to, the Reference Guide for State Expenditures (xxxxx://xxx.xxxxxxxxxxxx.xxx/Division/AA/Manuals/documents/ReferenceGuideforStateExpenditures.pdf).

  • Unbundled Voice Xxxx XX0 (XXX-XX0) Loops are 2-wire Loop start circuits, will be non-designed, and will not have remote access test points. OC will be offered as a chargeable option on XX0 Xxxxx when reuse of existing facilities has been requested by ONS. ONS may also order OC-TS when a specified conversion time is requested. OC-TS is a chargeable option for any coordinated order and is billed in addition to the OC charge. An Engineering Information (EI) document can be ordered as a chargeable option. The EI document provides Loop Make-Up information which is similar to the information normally provided in a Design Layout Record (DLR). Upon issuance of a non-coordinated order in the service order system, XX0 Xxxxx will be activated on the due date in the same manner and time frames that BellSouth normally activates POTS-type Loops for its End Users.

  • Electronic Invoicing (eInvoicing The Contractor may supply electronic invoices in lieu of paper-based invoices for those transactions processed through MFMP. Contractor may establish electronic invoicing within ninety (90) days of written request to the Department. Electronic invoices shall be submitted to the Customer through the Ariba Network (AN) in one of three mechanisms as listed below. The Contractor will work with the MFMP management team to obtain specific requirements for the eInvoicing.

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