Administrators use Tax Operations to manage tasks needed for closings. Closings require these steps:
The administrator sets up users. See Setting Up Users.
The administrator completes the required setup procedures:
Set up currencies. See Currencies.
Set up organizational units. See Managing Organizational Units for Tax Operations.
Set up global integration tokens. See .Managing Global Integration Tokens.
Set up holiday rules. See Managing Holiday Rules for Tax Operations.
Set up attachment size. See Maximum Task Attachment Size.
Enable email notifications. See Enabling Email Notifications.
The administrator reviews the tasks required for a close process and sets up Task Types to ensure consistency across tasks and to leverage predefined product integrations.
See Creating Task Types.
Because many tasks are repeatable over close periods, the administrator saves a set of tasks as a template to use for future periods. See Creating Templates.
For example, an administrator can set up a monthly or quarterly close once and then use it for all months or quarters. Tasks are defined with task predecessors, Assignees, and Approvers.
To initiate the close process for a period, administrators generate a schedule (a chronological set of tasks) by selecting a template and assigning calendar dates. The generic tasks in the template are applied to calendar dates. See Creating Schedules from Templates.
To begin the close process, the administrator changes the schedule status from Pending to Open. See Setting Schedule Status.
The administrator can also modify the schedule if needed and monitor it throughout the close cycle. See Updating Tasks in Schedules.
During the close process, users receive email notifications of assigned tasks and can click links in the email for direct access to assigned tasks.
Alternatively, users can log on to review and access assigned tasks in different types of views, for example, the Dashboard, a portal-style interface; or Calendar, Gantt, or Task List views.
When users complete tasks, the tasks are sent to approvers and can be viewed by other users.
Users can create alerts for issues, such as hardware or software issues, that they encounter during the close process. Alerts are forwarded to Assignees and Approvers for resolution.
Users can define and generate a Report Binder for a close cycle, which contains a description of the task details that were executed as part of the process. Report Binders enable administrators and others to review and adjust activities for future periods, and are also useful for audit purposes. See Using Report Binders in Tax Operations.