Common use of Unredeemed Chip Liability Clause in Contracts

Unredeemed Chip Liability. Any and all unredeemed gaming chips and tokens in circulation, whether relating to the operation of the Business before, at or after the Closing (the "Unredeemed Chip Liability"), which are presented by patrons of the Business for payment within the applicable time periods for legal redemption. For purposes of the adjustment to the Purchase Price pursuant to Section 3.3.2.2, the Unredeemed Chip Liability shall be discounted to reflect a reasonable assumption of gaming chips and tokens which are not expected to be redeemed and which discount shall be computed in accordance with the methodology described in Schedule 3.3.3(e);

Unredeemed Chip Liability. Any and all unredeemed ------------------------- gaming chips and tokens in circulation, whether relating to the operation of the Business before, at or after the Closing (the "Unredeemed Chip Liability"), which are presented by patrons of the Business for payment within the applicable time periods for legal redemption. For purposes of the adjustment to the Purchase Price pursuant to Section 3.3.2.2, the Unredeemed Chip Liability shall be discounted to reflect a reasonable assumption of gaming chips and tokens which are not expected to be redeemed and which discount shall be computed in accordance with the methodology described in Schedule -------- 3.3.3(e);; --------

Unredeemed Chip Liability. Any and all unredeemed gaming ------------------------- chips and tokens in circulation, whether relating to the operation of the Business before, at or after the Closing (the "Unredeemed Chip Liability"), which are presented by patrons of the Business for payment within the applicable time periods for legal redemption. For purposes of the adjustment to the Purchase Price pursuant to Section 3.3.2.2, the Unredeemed Chip Liability shall be discounted to reflect a reasonable assumption of gaming chips and tokens which are not expected to be redeemed and which discount shall be computed in accordance with the methodology described in Schedule 3.3.3(e);; ------------------