Punch-out Catalog and Electronic Invoicing Sample Clauses

Punch-out Catalog and Electronic Invoicing. At the State’s option, the Contractor may be required to provide an MFMP 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 MFMP eProcurement System and a supplier’s ERP system, which can reflect real-time product inventory/availability information. Through utilization of the punch-out catalog model, a Florida buyer will “punch out” to a supplier’s website. Using the search tools on the supplier’s Florida punch-out catalog site, the user selects the desired products and services. When complete, the user 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 supplier when the user exits the supplier’s punch-out catalog site. Instead, the chosen products and services are “brought back” to MFMP as Contract line items. The user 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 buyer actually adds the line items to a requisition and the purchase order is approved and sent to the supplier. At the State's option, the Contractor may be required to invoice electronically pursuant to guidelines of the Department of Management Services. Electronic invoices may be required to be submitted to the agency through the Ariba Network (AN) in one of three mechanisms as listed below. Contractors may select the method that best meets their capabilities from the following list: • cXML (commerce eXtensible Markup Language) This standard establishes the data contents required for invoicing via cXML within the context of an electronic environment. This transaction set can be used for invoicing via the ASN for catalog and non-catalog products and services. The cXML format is the Ariba preferred method for eInvoicing. • 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 products and services. • PO Flip via ASN The online process allows suppliers to submit invoices via the ASN for catalog and non- catalog products and services. Suppliers have the abili...
Sample 1Sample 2Sample 3See All (27)
AutoNDA by SimpleDocs
Punch-out Catalog and Electronic Invoicing. 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 Florida buyer will “punch out” to a Contractor’s website. Using the search tools on the Contractor’s Florida punch-out catalog site, the user selects the desired products and services. When complete, the user exits the Contractor’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 user exits the Contractor’s punch-out catalog site. Instead, the chosen products and services are “brought back” to MFMP as Contract line items. The user 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 Contractor until the buyer actually adds the line items to a requisition and the purchase order is approved and sent to the Contractor. All Contractors who implement Punch-out catalog solutions will be subject to MFMPs Punch- out Audit functionality. MFMP has added functionality that will compare the price retrieved from a Contractor's Punch-out catalog to the corresponding contract price sheet. As items are transferred into MFMP from a monitored contract/Punch-out catalog, the item and item price will be automatically compared to the contract price sheet. The logic for the audit process includes mapping the following fields from the Punch-out catalog to the contract price sheet: Supplier Tax ID, Contract #, Supplier Part #, Supplier Aux # (if available), and Unit of Measure (UOM). When an item is evaluated, the following rules are applied: Greater than price sheet Reduced to the base price from the price sheet Less than price sheet Honored Not Found on price sheet Honored Matches price sheet N/A 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 Network (AN) in one of three mechanisms as listed below. Contractors can select the method that best meets their capab...
Sample 1Sample 2Sample 3See All (5)

Related to Punch-out 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.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

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

  • Interconnection Customer Drawings Within one hundred twenty (120) days after the date of Initial Operation, unless the Interconnection Parties agree on another mutually acceptable deadline, the Interconnection Customer shall deliver to the Transmission Provider and the Interconnected Transmission Owner final, “as-built” drawings, information and documents regarding the Customer Interconnection Facilities, including, as and to the extent applicable: a one-line diagram, a site plan showing the Customer Facility and the Customer Interconnection Facilities, plan and elevation drawings showing the layout of the Customer Interconnection Facilities, a relay functional diagram, relaying AC and DC schematic wiring diagrams and relay settings for all facilities associated with the Interconnection Customer's step-up transformers, the facilities connecting the Customer Facility to the step-up transformers and the Customer Interconnection Facilities, and the impedances (determined by factory tests) for the associated step-up transformers and the Customer Facility. As applicable, the Interconnection Customer shall provide Transmission Provider and the Interconnected Transmission Owner specifications for the excitation system, automatic voltage regulator, Customer Facility control and protection settings, transformer tap settings, and communications.

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