Electronic Data Interchange (EDI) Requirement Sample Clauses

Electronic Data Interchange (EDI) Requirement. ( ) I/We confirm I am / we are able to comply with the Electronic Data Interchange (EDI) Requirement as required under Part II – Quotation Subject Matter. OR
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Electronic Data Interchange (EDI) Requirement. 29.7.1 The Seller shall install and use the GS1 Hong Kong’s (a new name of Hong Kong Article Numbering Association) Web-based EZ*TRADE or the Gateway Solution to receive the HA Purchase Orders, send Purchase Order Acknowledgements and other information on Vendor Managed Inventory (VMI) electronically with the Hospital Authority’s Enterprise Resources Planning System (ERPS). All the fees mentioned below are for reference only.
Sample 1See All (4)
Electronic Data Interchange (EDI) Requirement. The Seller shall install and use the GS1 Hong Kong’s (a new name of Hong Kong Article Numbering Association) Web-based EZ*TRADE or the Gateway Solution to receive the HA Purchase Orders, send Purchase Order Acknowledgements and other information on Vendor Managed Inventory (VMI) electronically with the Hospital Authority’s Enterprise Resources Planning System (ERPS). All the fees mentioned below are for reference only. Sellers are required to check the updated information from time to time published by GS1. Details of GS1 Hong Kong’s Web-based EZ*TRADE and the Gateway Solution are as follows:- The Web-based EZ*TRADE enables contractors to conduct EDI transactions by using a web browser on the Internet without involving additional set-up costs or special technical skills. The Gateway Solution, which requires communications software, internal IT support, an alignment of underlying processes and is for products which required Vendor Managed Inventory (VMI) with sophisticated transaction details. Implementation checklist for GS1 Hong Kong’s Web-based EZ*TRADE and the Gateway Solution: 1. Join GS1 Hong Kong as member
Sample 1Sample 2

Related to Electronic Data Interchange (EDI) Requirement

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

  • EDI - Electronic Data Interchange The exchange of business data in a standardized format between business computer systems.

  • 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 Visit Verification ("EVV Provider shall cooperate with State requirements for electronic visit verification for personal care services and home health services, as applicable.

  • 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 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:

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

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

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