Cash Register Access Code. To the greatest extent possible, all cash registers will be programmed to provide separate and distinct access codes for employees whose job duties require access.
Cash Register Access Code Sample Clauses
Related to Cash Register Access Code
USE OF TBS ACCESS CODE (a) An Account Holder may operate the TBS in relation to his Account by using his TBS Access Code.
Access Codes Tenant shall provide Landlord/Broker with all access codes to all entrance gates and security systems located on the Property.
CANCELLATION OF TBS ACCESS CODE The Account Holder may cancel his TBS Access Code by giving notice to the Bank in writing or in any other manner as may be determined by the Bank, and such notice shall only be effective upon actual receipt thereof by the relevant officer-in-charge at the Bank.
Security of Access Code You may use one (1) or more access codes with your electronic fund transfers. The access codes issued to you are for your security purposes. Any access codes issued to you are confidential and should not be disclosed to third parties or recorded on or with the card. You are responsible for safekeeping your access codes. You agree not to disclose or otherwise make your access codes available to anyone not authorized to sign on your accounts. If you authorize anyone to use your access codes, that authority shall continue until you specifically revoke such authority by notifying the Credit Union. You understand that any joint owner you authorize to use an access code may withdraw or transfer funds from any of your accounts. If you fail to maintain the security of these access codes and the Credit Union suffers a loss, we may terminate your EFT services immediately.
Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
Traditional IRA-to-Xxxx XXX Conversions If you convert to a Xxxx XXX, the amount of the conversion from your Traditional IRA to your Xxxx XXX will be treated as a distribution for income tax purposes, and is includible in your gross income (except for any nondeductible contributions). Although the conversion amount generally is included in income, the 10 percent early distribution penalty tax will not apply to conversions from a Traditional IRA to a Xxxx XXX, regardless of whether you qualify for any exceptions to the 10 percent penalty tax. If you are required to take a required minimum distribution for the year, you must remove your required minimum distribution before converting your Traditional IRA.
Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 5.1 Scope of Traffic 13 5.2 Trunk Group Architecture and Traffic Routing 13 5.3 Logical Trunk Groups 13 5.4 End Office Access 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 6.1 Meet-Point Billing Services 14 6.2 Data Format and Data Transfer 14 6.3 Errors or Loss of Access Usage Data 15 6.4 Payment 15 6.5 Additional Limitation of Liability Applicable to Meet-Point Billing Arrangements 16 ARTICLE VII BLV/BLVI TRAFFIC 16
