Invoice Data Processing Input Possibilities Sample Clauses

Invoice Data Processing Input Possibilities. The SIS application allows the billing entities to provide invoice information in multiple electronic formats. In the case of Passenger and Cargo xxxxxxxx, the invoice information can be provided in a flat file based structure (IS-IDEC) or in an XML file format (IS-XML). Miscellaneous and UATP invoices can be submitted only in the IS-XML format. Along with the electronic mode of invoice submission, SIS will also provide a facility to manually capture and review invoice information online over the internet, named IS-WEB. The table below details the support provided by SIS for different type of transactions within each Billing Category. Table: Input possibilities for each Billing Category in SIS Transaction Types Input Option IS-IDEC IS-XML IS-WEB Passenger Xxxxxxxx Non Sample Prime Coupon Xxxxxxxx (including FIMs) X X X Non Sample Rejection Memos X X X Billing Memos and Credit Memos X X X Sampling Provisional Invoice (Form A/B) X X – Sampling Universe Adjustment (Form C) X X2 X Sample Adjustments (Form D/E) X X X Sample Rejections (Form F and XF) X X X Correspondence – – X Cargo Xxxxxxxx Original AWB Xxxxxxxx X X X Rejection Memos X X X Billing Memos and Credit Memos X X X Correspondence – – X Miscellaneous Xxxxxxxx Original Invoice – X X Rejection Invoice – X X Correspondence Invoice – X X Correspondence – – X UATP Xxxxxxxx Original Invoice – X X On successful receipt of an incoming file, SIS generates a confirmation email and sends it to the billing entity. This email alert can be configured by billing entity using the Member Profile screen on IS-WEB. In case of invoices captured over IS-WEB, SIS generates an email alert to the billing entity 24 hours before the billing period closure providing a list of open invoices yet to be submitted for further processing. Data Validation Invoice data provided by the billing entities will be validated by SIS. This process will ensure that the invoice data is of good quality and the billed entities can process the same without any issue within their internal systems. This process will take place upon receipt of each SIS billing file. The different types of validation checks performed by the SIS application are as follows:
AutoNDA by SimpleDocs
Invoice Data Processing Input Possibilities. The SIS application allows the billing entities to provide invoice information in an electronic formats (IS-XML). Along with the electronic mode of invoice submission, SIS also provides a facility to manually capture and review invoice information online over the internet, named IS-WEB. The table below details the support provided by SIS for different type of transactions. Transaction Types IS-XML IS-WEB Original Invoice X X Rejection Invoice X X Correspondence Invoice X X Correspondence - X On successful receipt of an incoming file, SIS generates a confirmation email and sends it to the billing entity. This email alert can be configured by billing entity using the User Profile screen on IS-WEB. In case of invoices captured over IS-WEB, SIS generates an email alert to the billing entity 24 hours before the billing period closure providing a list of open invoices yet to be submitted for further processing. Data Validation Invoice data provided by the billing entities will be validated by SIS. This process will ensure that the invoice data is of good quality and the billed entities can process the same without any issue within their internal systems. This process will take place upon receipt of each SIS billing file. The different types of validation checks performed by the SIS application are as follows:

Related to Invoice Data Processing Input Possibilities

  • Details of Data Processing (a) Subject matter: The subject matter of the data processing under this DPA is the Customer Data.

  • Invoice Data The Contractor shall report invoice data from each paid or remitted invoice within 30 calendar days after the end of the reporting quarter, including the invoice data on task orders issued through the GSA AAS Business System Portal. (Note: Whatever method the Contractor chooses (e.g., “each paid” or “remitted”) the Contractor must be consistent in their reporting method throughout the term of the OASIS Contract). If no Invoice Data was received during a required reporting period for a specific task order, the Contractor shall report in the “Zero Invoice Data” screen located in the CPRM system for that particular task order. Regardless of contract type, the Contractor shall report the following into the CPRM:

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5.1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Comm South’s data from BellSouth’s data, the following shall apply:

  • Data Processing Agreement The Data Processing Agreement, including the Approved Data Transfer Mechanisms (as defined in the Data Processing Agreement) that apply to your use of the Services and transfer of Personal Data, is incorporated into this Agreement by this reference. Each party will comply with the terms of the Data Processing Agreement and will train its employees on DP Law.

  • Subprocessing 1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.

  • Interconnection Customer (1) Interconnection Customer shall construct and, unless otherwise indicated, shall own, the following Interconnection Facilities: None

  • Data Processing Addendum The parties’ agreement with respect to the processing of personal information submitted to the Subscription Service is described in the Data Processing Addendum attached to this Subscription Service Guide as Exhibit A.4 and incorporated herein by reference. The Data Processing Addendum may be updated periodically.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

  • Interconnection Customer Payments Not Taxable The Parties intend that all payments or property transfers made by the Interconnection Customer to the Participating TO for the installation of the Participating TO's Interconnection Facilities and the Network Upgrades shall be non-taxable, either as contributions to capital, or as a refundable advance, in accordance with the Internal Revenue Code and any applicable state income tax laws and shall not be taxable as contributions in aid of construction or otherwise under the Internal Revenue Code and any applicable state income tax laws.

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