Electronic Payments Processing Sample Clauses

Electronic Payments Processing 
AutoNDA by SimpleDocs

Related to Electronic Payments Processing

  • Electronic Payments The Grantee can choose to use electronic funds transfer (EFT) to receive grant payments. All grantees wishing to receive their award through EFT must submit a Vendor Direct Deposit Authorization form (form number DFS-AI-26E, rev 6/2014), incorporated by reference, to the Florida Department of Financial Services. If EFT has already been set up for your organization, you do not need to submit another authorization form unless you have changed bank accounts. To download this form visit xxxxxxxxxxxx.xxx/Xxxxxxxx/XX/Xxxxx/XXX-X0-00X.xxx. The form also includes tools and information that allow you to check on payments.

  • Electronic Payment certificate – an electronic certificate created by the client and/or Bank which represents the basis of performing transactions on the account of the client;

  • 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 Check Conversion/Electronic Returned Check Fees If you pay for purchases or bills with a check or draft, you may authorize your check or draft to be converted to an electronic fund transfer. You may also authorize merchants or other payees to electronically debit your account for returned check fees. You are considered to have authorized these electronic fund transfers if you complete the transaction after being told (orally or by a notice posted or sent to you) that the transfer may be processed electronically or if you sign a written authorization.

  • 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 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 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 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: 1. The payment recipient does not have an account at a financial institution. 2. EFT creates a financial hardship because direct deposit will cost the payment recipient more than receiving a check. 3. The payment recipient has a physical or mental disability, or a geographic, language, or literacy barrier. In order to receive EFT payments the recipient/cooperator shall register in the System for Award Management (XXX). You may register by going to xxx.xxx.gov and following the instructions provided online. For assistance, contact the XXX User Help by contacting the supporting Federal Service Desk at (000)000-0000 or xxx.xxx.xxx .

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