Catalog and Electronic Invoicing Sample Clauses

Catalog and Electronic Invoicing. The Contractor is encouraged to provide a MFMP punchout catalog. The punchout catalog provides an alternative mechanism for suppliers to offer the State access to Products awarded under the Contract. The punchout catalog also allows for direct communication between the MFMP eProcurement System and a supplier’s Enterprise Resource Planning (ERP) system, which can reflect real-time Product inventory/availability information. Through utilization of the punchout catalog model, a Florida buyer will “punch out” to a supplier’s website. Using the search tools on the supplier’s Florida punchout catalog site, the user selects the desired Products. When complete, the user exits the supplier’s punchout catalog site and the shopping cart (full of Products) is “brought back” to MFMP. No orders are sent to a supplier when the user exits the supplier’s punchout catalog site. Instead, the chosen Products are “brought back” to MFMP as line items in a purchase order. The user can then proceed through the normal workflow steps, which may include adding/editing the Products (i.e., line items) in the purchase order. An order is not submitted to a supplier until the user approves and submits the purchase order, at which point the supplier receives an email with the order details. The Contractor may supply electronic invoices in lieu of paper-based invoices for those transactions processed through MFMP. Electronic invoices may be submitted to the agency through one of the mechanisms as listed below: 1) 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 Ariba Network (AN) for catalog and non-catalog goods and services. 2) PO Flip via AN This online process allows Contractors to submit invoices via the AN for catalog and non-catalog goods and services. Contractors have the ability to create an invoice directly from their inbox in their AN account by simply "flipping" the PO into an invoice. This option does not require any special software or technical capabilities. The Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP, a State contractor, the right and license to use, reproduce, transmit, distribute, and publicly display within MFMP. In addition, the Contractor warrants and represents that it is a...
Sample 1Sample 2Sample 3See All (10)
AutoNDA by SimpleDocs
Catalog and Electronic Invoicing. Within 60 calendar days after contract execution, the Contractor shall supply a punch-out catalog. The punch-out catalog provides an alternative mechanism for suppliers to offer the State of Florida access to Products awarded under the Contract. The punch-out catalog also allows for direct communication between the MyFloridaMarketPlace eProcurement System (MFMP) and a supplier’s ERP system, which can reflect real-time Product inventory/availability information. Through utilization of the punch-out catalog model, a Customer will “punch out” to a Contractor’s website. Using the search tools on the supplier’s Florida punch-out catalog site, the Customer selects the desired Products and services. When complete, the Customer exits the supplier’s punch-out catalog site and the shopping cart (full of Products and services) is “brought back” to MFMP. No orders are sent to a Contractor when the Customer exits the supplier’s punch-out catalog site. Instead, the chosen Products and services are “brought back” to MFMP as contract line items. The Customer can then proceed through the normal workflow steps, which may include adding/editing the items to a requisition or a purchase order. An order is not submitted to a supplier until the Customer actually adds the line items to a requisition and the purchase order is approved and sent to the supplier. The Contractor shall supply electronic invoices in lieu of paper-based invoices for those transactions processed through the MFMP. Electronic invoices shall be submitted to the agency through the Ariba Supplier Network (ASN) in one of three mechanisms as listed below. Suppliers can select the method that best meets their capabilities from the following list:
Sample 1Sample 2Sample 3See All (6)

Related to Catalog and Electronic Invoicing

  • Electronic invoicing The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232- 7003, Electronic Submission of Payment Requests and Receiving Reports.

  • Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.

  • Electronic Access Access by the Customer to certain systems, applications or products of Bank shall be governed by this Agreement and the terms and conditions set forth in Annex A Electronic Access.

  • WASHINGTON’S ELECTRONIC BUSINESS SOLUTION (WEBS). Contractor represents and warrants that Contractor is registered in Washington’s Electronic Business Solution (WEBS), Washington’s contract registration system and that, all of Contractor’s information therein is current and accurate and that throughout the term of this Contract, Contractor shall maintain an accurate profile in WEBS.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

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