MFMP Electronic Invoicing Sample Clauses

MFMP Electronic Invoicing. 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 authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within MFMP the Contractor's trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract. The Contractor will work with the MFMP management team to obtain specific requirements for the electronic invoicing if needed.
AutoNDA by SimpleDocs
MFMP Electronic Invoicing. 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 Customer through one of the mechanisms as listed below:
MFMP Electronic Invoicing. 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 DocuSign Envelope ID: 0142531A-654B-47C4-A357-D0AE23A5696E 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 authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within MFMP the Contractor's trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract. The Contractor will work with the MFMP management team to obtain specific requirements for the electronic invoicing if needed.
MFMP Electronic Invoicing. 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) 2) PO Flip via AN‌‌‌‌‌ The Contractor 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 Contractor’s information within MFMP. In addition, the Contractor grants the State and the third-party provider the right and license to reproduce and display within MFMP the Contractor's trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract. The Contractor will work with the MFMP management team to obtain specific requirements for the electronic invoicing if needed.

Related to MFMP 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 Invoicing (eInvoicing The Contractor may supply electronic invoices in lieu of paper-based invoices for those transactions processed through MFMP. Contractor may establish electronic invoicing within ninety (90) days of written request to the Department. Electronic invoices shall be submitted to the Customer through the Ariba Network (AN) in one of three mechanisms as listed below. The Contractor will work with the MFMP management team to obtain specific requirements for the eInvoicing.

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

  • ELECTRONIC SUBMITTALS Contractor shall obtain a license for the State to utilize Submittal Exchange for the purposes of this project. The State and its representatives will have full control of the use of Submittal Exchange by authorized users of the State.

  • Electronic Communications; Voice Mail Electronic mail and internet websites may be used only for routine communications, such as financial statements, Borrowing Base Certificates and other information required by Section 10.1.2, administrative matters, distribution of Loan Documents for execution, and matters permitted under Section 4.1.4. Agent and Lenders make no assurances as to the privacy and security of electronic communications. Electronic and voice mail may not be used as effective notice under the Loan Documents.

  • Electronic Acceptance You expressly confirm that you have read, agree to, and consent to be bound by all of the terms of this User Agreement, including all disclosures in this agreement, including those in Section 18.3. By electronically signing this User Agreement, which may be completed by all methods of “clickwrap” or “click through” including by accepting, clicking a button, or checking a box, you acknowledge and agree that such electronic signature is valid evidence of your consent to be legally bound by this User Agreement and such subsequent

  • Consent to Electronic Delivery; Electronic Signature In lieu of receiving documents in paper format, the Participant agrees, to the fullest extent permitted by law, to accept electronic delivery of any documents that the Company may be required to deliver (including, but not limited to, prospectuses, prospectus supplements, grant or award notifications and agreements, account statements, annual and quarterly reports and all other forms of communications) in connection with this and any other Award made or offered by the Company. Electronic delivery may be via a Company electronic mail system or by reference to a location on a Company intranet to which the Participant has access. The Participant hereby consents to any and all procedures the Company has established or may establish for an electronic signature system for delivery and acceptance of any such documents that the Company may be required to deliver, and agrees that his or her electronic signature is the same as, and shall have the same force and effect as, his or her manual signature.

  • Electronic Information Each Member hereby agrees that all current and future notices, confirmations and other communications may be made by the Company via email, sent to the email address of record of the Member provided to the Company as changed or updated from time to time, without necessity of confirmation of receipt, delivery or reading, and such form of electronic communication is sufficient for all matters regarding the relationship between the Company and the Members except as otherwise required by law. If any such electronically sent communication fails to be received for any reason, including but not limited to such communications being diverted to the recipients spam filters by the recipients email service provider, or due to a recipient’s change of address, or due to technology issues by the recipients service provider, the parties agree that the burden of such failure to receive is on the recipient and not the sender, and that the sender is under no obligation to resend communications via any other means, including but not limited to postal service or overnight courier, and that such communications shall for all purposes, including legal and regulatory, be deemed to have been delivered and received. Except as required by law, no physical, paper documents will be sent to Members, and a Member desires physical documents then such Member agrees to be satisfied by directly and personally printing, at such Member’s own expense, the electronically sent communication(s) and maintaining such physical records in any manner or form that a Member desires.

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