EDI - Electronic Data Interchange Sample Clauses

EDI - Electronic Data Interchange. The exchange of business data in a standardized format between business computer systems.
Sample 1Sample 2Sample 3See All (103)
AutoNDA by SimpleDocs
EDI - Electronic Data Interchange. This standard establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used for invoicing via the ASN for catalog and non-catalog goods and services.
Sample 1Sample 2Sample 3See All (29)
EDI - Electronic Data Interchange. Inter-process (computer to computer application) communication of business information in a standardized electronic form. Manufacturer Backorder(s) (MBO) - An order placed by the Wholesaler to a manufacturer or supplier which is not shipped to the Wholesaler due to industry wide shortages or other supply issues as set forth in Section 4.5 (E.) of Attachment A. MMCAP Contract Product(s) - Any Product that appears on an MMCAP contract. MMCAP Contract File Updates – electronic files sent by the MMCAP Office to the Wholesaler which provide batched MMCAP Contract Product and MMCAP contract pricing information. The MMCAP Contract File Updates are usually sent to the Wholesaler on a weekly basis. The first file (titled “Update [sequential number]”) details the MMCAP contract changes that have occurred since the last weekly communication from the MMCAP Office. The second file (titled “[sequential number] Contract [8-digit date]”) is a listing of the entire MMCAP contract as of the date provided in the title. The third file (titled “[sequential number] Pending [8-digit date]”) is a listing of the MMCAP Contract Products with future effective dates.
Sample 1Sample 2
EDI - Electronic Data Interchange. Electronic Data Interchange (EDI) is an application-to-computer exchange of business documents in a standard format over a communications path. EDI requires the use of industry guidelines that define the format and the data content of the business transaction. This permits computers to clearly understand the transaction expected and the data necessary to conduct that transaction. Trading partners (e.g., BellSouth and the CLEC) must define the business information and supported standards that are necessary to transact business. This information is then encoded to fit a standard EDI transaction set for data transmission. EDI requires the use of industry guidelines that define the format and the data content of the business transaction. Currently, BellSouth’s EDI gateway supports specific guidelines applicable to pre-ordering and ordering.
Sample 1
EDI - Electronic Data Interchange. Inter-process (computer to computer application) communication of business information in a standardized electronic form.
Sample 1
EDI - Electronic Data Interchange. ▪ The Supplier is required to implement an identical or similar SW intermediary compatible with Alza's EDI solution and do so within 1 month after entering into the Master Agreement, unless explicitly stated otherwise. Where the Supplier fails to meet this obligation properly and in due time and keeps submitting the relevant documents other than via EDI, Alza has the right to charge the EDI fee specified in the Master Agreement. ▪ The Supplier may also send the EDI files via the web interface. XXX is a method for exchanging VAT invoices and other documents between trading partners using a standardised electronic format. ▪ Suppliers using EDI are required to submit a proper (error-free) DESADV message before the Goods are physically delivered. The message must be sent at the earliest 3 days and at the latest 12 hours prior to unloading so that Alza's system can receive it properly. Any DESADV messages returned due to errors must be corrected and sent in due course. ▪ Any serial and/or IMEI numbers placed on the Goods must as well be documented. ▪ Data on paper dispatch advice must correspond to that exchanged via EDI (DESADV) and printed on labels (SSCC). ▪ Otherwise, Alza has the right to refuse the delivery. For more details regarding XXX, please visit: xxxxx://xxx.xxxx.xx/edi-komunikace/alza-cz.
Sample 1
EDI - Electronic Data Interchange. Inter-process (computer to computer application) communication of business information in a standardized electronic form. Manufacturer Backorder(s) (MBO) - An order placed by the Wholesaler to a manufacturer or supplier which is not shipped to the Wholesaler due to industry wide shortages or other supply issues as set forth in Section 5D of Attachment A. MMCAP Contract Product(s) - Any Product that appears on an MMCAP contract. MMCAP Contract File Updates – electronic files sent by MMCAP to the Wholesaler which provide batched MMCAP Contract Product and MMCAP contract pricing information. The MMCAP Contract File Updates are usually sent to the Wholesaler on a weekly basis. The first file (titled “Update [sequential number]”) details the MMCAP contract changes that have occurred since the last weekly communication from MMCAP. The second file (titled “[sequential number] Contract [8-digit date]”) is a listing of the entire MMCAP contract as of the date provided in the title. The third file (titled “[sequential number] Pending [8- digit date]”) is a listing of the MMCAP Contract Products with future effective dates.
Sample 1
AutoNDA by SimpleDocs
EDI - Electronic Data Interchange. The computer-to-computer exchange of routine business information in a standard form. See also - Transaction Sets ESCO An entity that can supply energy and customer service functions in a competitive environment. EFT Electronic Funds Transfer.
Sample 1

Related to EDI - Electronic Data Interchange

  • Electronic Data Interchange If both Parties elect to facilitate business activities hereunder by electronically sending and receiving data in agreed formats (also referred to as Electronic Data Interchange or “EDI”) in substitution for conventional paper-based documents, the terms and conditions of this Agreement shall apply to such EDI activities.

  • Electronic Data Interchange (EDI This standard establishes the data contents of the Invoice Transaction Set (810) for use within the context of an EDI environment. This transaction set can be used for invoicing via the AN for catalog and non-catalog goods and services.

  • Electronic Data 7.1.1 The parties recognize that Contract Documents, including drawings, specifications and three-dimensional modeling (such as Building Information Models) and other Work Product may be transmitted among Owner, Design-Builder and others in electronic media as an alternative to paper hard copies (collectively “Electronic Data”).

  • Electronic Backups Subrecipient shall ensure that all electronic information is protected by performing regular backups of automated files and databases and ensure the availability of information assets for continued business. Subrecipient shall ensure that all data, files, and backup files are encrypted.

  • Electronic Devices No electronic devices that may hinder job performance or safety (especially cell phones), may be carried on employees’ person, or be used by employees during working hours.

  • ELECTRONIC WORKFLOW SYSTEM OGS reserves the right to incorporate an electronic workflow system that may include elements of the Authorized User RFQ process. OGS reserves the right to post Authorized User Contract usage of Centralized Contracts. TRAVEL, MEALS AND LODGING - LOT 4 – IMPLEMENTATION ONLY For Lot 4 only, when provided for in the RFQ and resultant Authorized User Agreement, the Authorized Users may reimburse travel expenses. All rules and regulations associated with this travel can be found at xxxx://xxx.xxxxx.xx.xx/agencies/travel/travel.htm. In no case will any travel reimbursement be charged that exceeds these rates. All travel will be paid only as specified within the Authorized User Agreement and must be billed with the associated services on the same Invoice with receipts attached. The Contractor shall receive prior approval from the Authorized User for any travel that occurs during the term of an Authorized User Agreement. Parking fees and/or parking tickets shall not be paid by an Authorized User. Unless otherwise specified in writing by the Authorized User, a vehicle will not be provided by Authorized User to the Contractor for travel. Therefore, the Contractor will be responsible for ensuring that the Contractor has access to an appropriate vehicle (e.g., personal vehicle or rental vehicle) or common carrier with which to carry out any necessary travel. For the Contractor to obtain reimbursement for the use of a rental vehicle, such use must be justified as the most cost- effective mode of transportation under the circumstances (including consideration of the most effective use of time). The Contractor is responsible for keeping adequate records to substantiate any claims for travel reimbursement. All services provided under the resultant Authorized User Agreement must be performed within CONUS. PERFORMANCE AND BID BONDS There are no BONDS for this Contract. However, an Authorized User may require in an RFQ a performance, payment or Bid bond, or negotiable irrevocable letter of credit or other form of security for the faithful performance for the resultant Authorized User Agreement. CONTRACTOR REQUIREMENTS AND PROCEDURES FOR PARTICIPATION BY NEW YORK STATE CERTIFIED MINORITY- AND WOMEN-OWNED BUSINESS ENTERPRISES AND EQUAL EMPLOYMENT OPPORTUNITIES FOR MINORITY GROUP MEMBERS AND WOMEN I. New York State Law Pursuant to New York State Executive Law Article 15-A and Parts 140-145 of Title 5 of the New York Codes, Rules and Regulations (“NYCRR”), the New York State Office of General Services (“OGS”) is required to promote opportunities for the maximum feasible participation of New York State-certified Minority- and Women-owned Business Enterprises (“MWBEs”) and the employment of minority group members and women in the performance of OGS contracts.

  • Electronic Visit Verification ("EVV Provider shall cooperate with State requirements for electronic visit verification for personal care services and home health services, as applicable.

  • ELECTRONIC FUNDS TRANSFER (EFT The recipient/cooperator shall designate a financial institution or an authorized payment agent through which a federal payment may be made in accordance with US Treasury Regulations, Money and Finance at 00 XXX 000, which requires that federal payments are to be made by EFT to the maximum extent possible. A waiver may be requested and payments received by check by certifying in writing that one of the following situations apply:

  • Responsibility for Electronic Data The Student is solely responsible for any data stored on the Computer. It is the sole responsibility of the Student to backup such data as necessary.

  • Electronic Documents We may make periodic statements, disclosures, notices, and other documents available to you electronically, and, subject to any delivery and receipt verification procedures required by law, you agree to receive such documents electronically and to check the statements for accuracy. If you believe any such statement contains incorrect information, you must follow the procedures set forth in the Related Agreement(s).

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