Remittance for Non-Purchase of Receivable Customers Sample Clauses

Remittance for Non-Purchase of Receivable Customers. 1) Payments received from District of Columbia, Virginia, and Maryland will be applied in accordance with the applicable regulatory statutes. In those instances in which a Customer submits a payment without accurate or adequate account information, WG will use its best judgment to post the payments as accurately and timely as possible so that remittances can be delivered to Supplier promptly. However, WG is not responsible for any posting delays or subsequent harm caused by a Customer who does not adequately identify payment destinations.
AutoNDA by SimpleDocs

Related to Remittance for Non-Purchase of Receivable Customers

  • Instructions for Certification – First Tier Participants a. By signing and submitting this proposal, the prospective first tier participant is providing the certification set out below.

  • The OCN, From XXX, and Invoice Number will control the invoice sequencing The From XXX will be used to identify to <<customer_name>> which BellSouth XXX is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate. THE DATA WILL BE PACKED USING ATIS EMI RECORDS.

  • Shipping must be Freight On Board Destination to the delivery location designated on the Customer purchase order The Contractor will retain title and control of all goods until delivery is completed and the Customer has accepted the delivery. All risk of transportation and all related charges are the responsibility of the Contractor. The Customer will notify the Contractor and H-GAC promptly of any damaged goods and will assist the Contractor in arranging for inspection. The Contractor must file all claims for visible or concealed damage. Unless otherwise stated in the Agreement, deliveries must consist only of new and unused merchandise.

  • DELIVERY: FOB DESTINATION, INSIDE DELIVERY, FREIGHT PAID Whenever possible, contractors should give the ordering entities 3 working days prior notice of any deliveries and/or installations. Furniture contractors will not be responsible for the removal/moving of existing furnishings unless requested by the ordering entity. Contractors should verify site readiness prior to delivery. All deliveries will be made during normal working hours unless otherwise arranged with the ordering entity. Contractor will communicate any scheduling delays and/or changes immediately. Agencies will not be responsible for any freight damage, concealed or otherwise.

  • SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO.

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Comm South’s data from BellSouth’s data, the following shall apply:

  • Billing, Payment, Milestones, and Financial Security 6.1 Billing and Payment Procedures and Final Accounting

  • Instructions for Certification - Lower Tier Participants (Applicable to all subcontracts, purchase orders and other lower tier transactions requiring prior FHWA approval or estimated to cost $25,000 or more - 2 CFR Parts 180 and 1200)

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

  • Monthly Report A. A Monthly Report shall be submitted within ten (10) calendar days of the end of each calendar month of the Period of Operation. Each Monthly Report shall be signed, dated, and certified by Concessionaire, Concessionaire’s Bookkeeper, or Accountant, and contain a Statement of Total Gross Receipts, excluding New Jersey State Sales Tax, derived by Concessionaire from operation of the Concession during the previous month. Each Monthly Report shall be based on the daily “Z” tapes or Point-of-Service (POS) device equivalent for that same month showing each day’s sales activity. Failure on the part of Concessionaire to provide the Monthly Report, when due, shall constitute a material breach of this Agreement subject to Suspension of Operations and/or Termination, in accordance with the terms and conditions set forth in Paragraphs 9 and 10. Concessionaire shall provide Department with any additional written clarification and/or information necessary to confirm the accuracy of any or all of Concessionaire’s Monthly Reports.

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