Master Data Sample Clauses

Master Data. No less than two weeks shall have elapsed since Seller’s full compliance with its obligations under Section 6.8.
View SourceView Similar (2)
Master Data. If NCDG creates and codifies and time-invariant data objects / master tables then intellectual property of those master tables also belongs to NIC.
View Source
Master Data. With the matriculation and the registration in the degree programme the student agrees to the EDP-supported processing of the personal data in accordance with the Education Documentation Law, Federal Law Gazette I no. 2002/12 and in accordance with the stipulations of the § 6 (1) HSG 2014. The administration office of the degree programme must be informed within one week of changes to the student’s master data, in particular regarding home address, school address and telephone number.
View Source
Master Data. This will be maintained to enable the correct payment of suppliers and staff and the accurate accounting for financial transactions and data. Maintaining all ▇▇▇ specific Master Data on the system including but not limited to: Budget codes/ledgers. Chart of account codes (COA) for ▇▇▇. Business rules for establishing validating account code combinations. For example but not limited to: Pay account codes must also have an Employee analysis code; or Certain ranges of Project/Activity codes can only be used with specific Cost Centre ranges, etc. HMT OSCAR account codes for mapping expenditure between ▇▇▇ COA and the HMT OSCAR COA. Supplier groups. Trade creditor accounts including bank details. Staff creditor accounts including bank details. Debtor accounts. Authorising users and their privileges on the system but not activating or deactivating users, which would be the responsibility of the system administrator. Opening and closing accounting periods. If there were to be reorganization or other activity requiring bulk changes to the Master Data, ▇▇▇ would work with THE PROVIDER to ensure that, in these unusual circumstances, suitable arrangements were in place. Defining and assigning different levels of user privileges on the system. Providing access to Monthly Reports that show all Master Data changes together with details of the change, who made it, date/time stamp and a unique reference. This is the normal activity of recording and processing financial transactions on and from the system. Establishing and maintaining budget information on the system. Inputting and approving of supplier invoices and staff travel and subsistence claims onto the system, unless ▇▇▇ Finance request that THE PROVIDER to do otherwise on its behalf. Inputting and processing of journal entries onto the system by a variety of means including manual journals, Excel spreadsheet uploads and interface with third party applications. Reviewing, checking and approving payment proposal files for payment. Processing CHAPS, transfers and foreign exchange payments from the ▇▇▇ bank account and recording these on the system. Bank reconciliations. Reconciliation of other account and suspense balances. Providing the system administrator. Maintaining appropriate levels of security of data at all times to IL3 level. Generating BACS and Payable Order payments per the agreed target timelines from approved payment proposal files to be drawn upon the ▇▇▇ bank account. Providing a remittance advice for...
View Source
Master Data. The Contracting Authority differentiates between master data from Material Registry/FEST (Drug Master), referring to the data sourced from national registries, and other master data, corresponding to data which are not provided by national registries but that are important to deliver the required functionalities.
View Source

Related to Master Data

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • User Data We will maintain certain data that you transmit to the Services for the purpose of managing the performance of the Services, as well as data relating to your use of the Services. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Services. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.

  • Customer Data 5.1 The Customer shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data. The customer being a contractor of DSA Airport, the customer shall not own the rights, title and interest in and to the Data which belongs to DSA Airport. 5.2 The Supplier shall follow its archiving procedures for Customer Data as set out in its Back- Up Policy available at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ or such other website address as may be notified to the Customer from time to time, as such document may be amended by the Supplier in its sole discretion from time to time. In the event of any loss or damage to Customer Data, the Customer's sole and exclusive remedy shall be for the Supplier to use reasonable commercial endeavours to restore the lost or damaged Customer Data from the latest back-up of such Customer Data maintained by the Supplier in accordance with the archiving procedure described in its Back-Up Policy. The Supplier shall not be responsible for any loss, destruction, alteration or disclosure of Customer Data caused by any third party (except those third parties subcontracted by the Supplier to perform services related to Customer Data maintenance and back-up). 5.3 The Supplier shall, in providing the Services, comply with its Privacy and Security Policy relating to the privacy and security of the Customer Data available at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ or such other website address as may be notified to the Customer from time to time, as such document may be amended from time to time by the Supplier in its sole discretion. 5.4 If the Supplier processes any personal data on the Customer’s behalf when performing its obligations under this agreement, the parties record their intention that the Customer shall be the data controller and the Supplier shall be a data processor and in any such case: (a) the Customer acknowledges and agrees that the personal data may be transferred or stored outside the EEA or the country where the Customer and the Authorised Users are located in order to carry out the Services and the Supplier’s other obligations under this agreement; (b) the Customer shall ensure that the Customer is entitled to transfer the relevant personal data to the Supplier so that the Supplier may lawfully use, process and transfer the personal data in accordance with this agreement on the Customer's behalf; (c) the Customer shall ensure that the relevant third parties have been informed of, and have given their consent to, such use, processing, and transfer as required by all applicable data protection legislation; (d) the Supplier shall process the personal data only in accordance with the terms of this agreement and any lawful instructions reasonably given by the Customer from time to time; and (e) each party shall take appropriate technical and organisational measures against unauthorised or unlawful processing of the personal data or its accidental loss, destruction or damage.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.