Integration with Client’s Billing System Sample Clauses

Integration with Client’s Billing System. At no cost to Client, Paymentus will develop one (1) file format interface with Client’s billing system using Client’s existing text file format currently used to post payments to Client’s billing system. Client will be responsible to provide Paymentus with the one file format specification and will fully cooperate with Paymentus during the development of the said interface. If Client chooses to create an automated file integration process to download the posting file, due to Paymentus security requirements, Client will use Paymentus specified integration process. Paymentus platform is an independent full service fully hosted platform per PCI-DSS requirements for a fully hosted solution. As such, Paymentus platform does and can function independent of any billing system integration. A payment posting file can be emailed or downloaded from Paymentus Agent Dashboard. If Client chooses to have Paymentus platform integrated with its billing system, Paymentus offers two options:
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Integration with Client’s Billing System. At no cost to Client, Paymentus will develop and maintain a real-time interface to interact with the MUNIS (“Client’s Supplier”) IVR Gateway, provided Client cooperates fully with Paymentus and causes Client’s Supplier to fully cooperate. Paymentus shall be responsible for maintaining compatibility with the MUNIS IVR Gateway or other real-time integrated non-custom standard MUNIS module without additional cost to what is agreed upon in this Agreement. If this compatibility is not fully implemented or fails, solely due to Paymentus’ acts or omissions despite full cooperation from Client and Client’s Supplier, the Client, at its discretion, may deem it a Material Breach as provided in Section 9.2.
Sample 1Sample 2Sample 3
Integration with Client’s Billing System. At no cost to Client, Paymentus will develop one (1) file format interface with Client’s billing system using Client’s existing text file format currently used to post payments to Client’s billing system. Client will be responsible to provide Paymentus with the one file format specification and will fully cooperate with Paymentus during the development of the said interface. If Client chooses to create an automated file integration process to download the posting file, due to Paymentus security requirements, Client will use Paymentus specified integration process.
Sample 1
Integration with Client’s Billing System. At no charge from Paymentus to Client, Paymentus will develop one (1) file format interface with Client’s billing system using Client’s existing text file format currently used to post payments to Client’s billing system. Client will be responsible to provide Paymentus with the one file format specification and will fully cooperate with Paymentus during the development of the said interface. If Client chooses to create an automated file integration process to download the posting file, due to Paymentus security requirements, Client will use Paymentus specified integration process. As such, the Paymentus platform does and can function independent of any billing system integration. A payment posting file can be emailed or downloaded from the Paymentus Agent Dashboard. If Client chooses to have the Paymentus platform integrated with its billing system, Paymentus offers two options:
Sample 1

Related to Integration with Client’s Billing System

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

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers 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 purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. 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 the system 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.

  • Third Party Billing If, prior to the Effective Date or at any time during the term of this IA LFAC contracts with a third party billing company to submit claims to the Federal health care programs on behalf of LFAC, LFAC must certify to OIG that he or it does not have an ownership or control interest (as defined in 42 U.S.C. § 1320a-3(a)(3)) in the third party billing company and is not employed by, and does not act as a consultant to, the third party billing company. LFAC also shall obtain (as applicable) a certification from any third party billing company that the company: (i) has a policy of not employing any person who is excluded from participation in any Federal health care program to perform any duties related directly or indirectly to the preparation or submission of claims to Federal health care programs; (ii) screens its prospective and current employees against the Exclusion List; and (iii) provides training in the applicable requirements of the Federal health care programs to those employees involved in the preparation and submission of claims to Federal health care programs. If applicable, a copy of these certifications shall be included in LFAC’s Implementation Report and each Annual Report required by Section V below.

  • Internet Access to Contract and Pricing Information Access by Authorized Users to Contract terms and pricing information shall be made available and publically posted on the OGS website. To that end, OGS shall publically post the Contract Pricelist, including all subsequent changes in the Contract offerings (adds, deletes, price revisions), Contractor contact information, and the Contract terms and conditions, throughout the Contract term.

  • Master Contract Sales Reporting System Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile.

  • Customer Cooperation 3.2.1. Customer shall provide and make available all Customer personnel as may be further addressed in an applicable Order Form or that SAP reasonably requires in connection with performance of the Services.

  • Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles:

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures.

Time is Money Join Law Insider Premium to draft better contracts faster.