<mods:mods version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mods:titleInfo><mods:title>Rollover ALEPH! Good system or, Fiscal Year Closing with ALEPH 14.2</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Christine</mods:namePart><mods:namePart type="family">Moulen</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Kathy</mods:namePart><mods:namePart type="family">Wachel</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>The fiscal year rollover is an important aspect of any acquisitions and financial system. I will discuss MIT’s experience testing and running ALEPH’s year-end processes under version 14.2.2 (hopefully by the time of NAAUG testing and preparing to run with 14.2.5) including not only the three built-in jobs that do the budget processing, but also reports we run, precautions taken to ensure no activity takes place during processing, and more.</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2003-06-02</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>