1. Administering Account Reconciliation
  2. Administering Reconciliation Compliance
  3. Learning About the Reconciliation Process
  4. Sample Task Flow Scenarios for Administrators and Power Users

Sample Task Flow Scenarios for Administrators and Power Users

Scenario 1––Service Administrator

A Service Administrator configures profiles during implementation and uses the profile import feature to load profiles.

  1. From the Profile List View, the Service Administrator exports profiles, selecting the unformatted data for future import option to create a CSV file template to gather profile data.

  2. The Service Administrator copies and pastes information, including account segments, name, description, and other profile properties, into the profile import file. Because the Service Administrator doesn't have all of the information yet, some columns are unpopulated. The Service Administrator eventually updates these attributes.

  3. From the Profile List View, the Service Administrator imports the profiles, choosing the Replace option.

  4. The Service Administrator updates the profiles, combining manual edits and mass updates of profile data using the Actions panel.

  5. As the Service Administrator nears the end of the profile configuration, a policy change is implemented requiring reassignment of the risk rating values. The Service Administrator decides the easiest way to accomplish the reassignment is to configure the new values in a spreadsheet and import them. The Service Administrator exports the list of profiles from the Profile List View using the unformatted data for future import option. Then, the Service Administrator deletes the columns other than the account segment and risk rating columns.

  6. The Service Administrator imports the changes using the import Profiles feature on the Profile List View. This time, the Service Administrator selects the Update option, ensuring that only the risk rating attribute is updated.

Scenario 2––Service Administrator

A Service Administrator receives notice that an employee functioning as a preparer has changed departments and no longer performs reconciliations. The profiles and reconciliations assigned to this user must be reassigned.

  1. The Service Administrator must reassign profiles so that future reconciliations are properly assigned. From the Profile List View, the Service Administrator identifies profiles assigned to the user by applying a filter on the Preparer Name. Then, using the Actions panel on the Profile List View, the Service Administrator changes the preparer assignment by selecting the Preparer option in the Add User section and providing the new user name in the Value field. After clicking the Add button, the Service Administrator updates all records and receives confirmation that the update is successful.

  2. The Service Administrator checks on the user's reconciliations. From the Reconciliation List View, the Service Administrator again filters by Preparer Name and finds two Open and three Pending reconciliations.

  3. The Service Administrator reassigns the Pending and Open reconciliations using the Actions panel.

Scenario 3––Power User

A Power User performs maintenance on profiles in his security profile, which includes all profiles with Company Codes ranging from 50-55.

  1. The Power User receives an email notification that reviewer assignments must change for a series of profiles. These profiles are in the security profile of the Power User.

  2. From the Profile List View, the Power User creates a filter to retrieve the affected accounts and uses the Actions panel to apply changes to reviewer assignments.

  3. Later that day, the Power User receives an email from the Service Administrator informing him that new profiles must be created for general ledger account 1729 (a new account), for all company codes in the security profile of the Power User. The Power User decides the easiest way to create these profiles is to import them from a CSV file. From the Profile List View, he exports a sample profile using the Export profiles – unformatted data for future import option to create a template file. Then, he creates seven profiles in this import file, one each for company codes 50-56.

  4. The Power User imports the profiles. During import, notifies him that profile 56-1729 is outside his security profile and cannot be created. The Power User realizes he made a mistake, because his profile includes Company Codes 50-55. He confirms that these six profiles are added successfully.