Roles

FinaHQ has 5 predefined roles as given below:

• Corporate Controller

• Corporate Controller Team

• Corporate Controller Admin

• Finance Controller

• Entity Team

The approvals in the setup modules are as follows:

• Add Entity

  • Add, Edit, Delete, Upload,

  • Approved by corporate controller

• Add Investments – Approved by corporate controller

• Forms – Approved by corporate controller

• COA Master – Approved by corporate controller

• GL Mapping – Approved by finance controller of respective entities. If the corporate controller upload GL mapping, it will be auto approved and does not need any further approval.

When there is more than 1 user in the approvers group (corporate controller group or finance controller group), the approvals will be sent to all the members of the group.

For ex: If there are 3 users in the corporate controller group and if there is a change in ‘Forms’, then the approval request will be sent to all the 3 users.

Corporate Controller:

Setup Module:

The corporate controller will be able to do the following operations in the setup module.

• View – View the data of all entities

• Add – Add data for all entities

• Edit – Edit data of all entities

• Delete – Delete data of all entities

• Approve/Reject – Approves or rejects the data when the data is added, edited or deleted for the holding entity and for all entities except GL Mapping.

If the member of the corporate controller team adds, edits or deletes any data, the change will be auto approved and does not need any further approval.

Projects Module:

The corporate controller will be able to do the following operations in the project's module.

• View – View the data of all entities

• Add – Add data for all entities

• Edit – Edit data of all entities

• Delete – Delete data of all entities

• Upload – Upload documents for all the entities

• Approve/Reject – Approves or rejects the data when the data is added, edited or deleted for his entity

If the member of the corporate controller team adds, edits or deletes any data, the change will be auto approved and does not need any further approval.

Corporate Controller Team:

Setup Module:

The corporate controller team will be able to do the following operations in the setup module.

• View – View the data of all the entities

• Add – Add data for all the entities

• Edit – Edit data of all the entities

• Delete – Delete data of all the entities

• Upload – Upload documents for all the entities

• Download – Download templates or download data (forms, trial balance, ICO, Add Entity)

If the member of the corporate controller team adds, edits or deletes any data in the setup module, the change should be approved by the corporate controller.

This change will be effective only if the data is approved by the corporate controller.

For ex: If a member in the corporate controller team adds a new form, then the form will be visible to all the members of the team only if the corporate controller approves the change.

Projects Module:

If the project owner is the ultimate parent, then the corporate controller team will be able to do the following operations in the project's modules.

• View – View the data of his entity and all the child entities

• Add – Add data for his entity and all the child entities

• Edit – Edit data of his entity and all the child entities

• Upload – Upload documents for his entity and all the child entities

• Download – Download documents or templates for his entity and all the child entities

If the corporate controller team member adds, edits or deletes data in Load TB, Load BC, ICO or other adjustments, then this change has to be approved by the corporate controller.

Corporate Controller Admin:

• The corporate controller admin is responsible for user management.

• The corporate controller admin maps the user to a group (Corporate controller group, corporate controller team group, finance controller group, entity team group or corporate controller admin group).

• The user can also be mapped to more than one entity by the corporate controller administrator.

• However, the role of the user for all the entities will be the same.

  • For ex: If a user is mapped as a finance controller for entity A, then the same user can be mapped to other entities like entity B and entity C. However, the user will have access of a finance controller for A, B and C

Finance Controller:

Setup Module:

The finance controller will be able to do the following operations in the setup module.

• View – View the data of his entity and the entities for which he/she has data access to

• Add – Add data for his entity and the entities for which he/she has data access to

• Edit – Edit data of his entity and the entities for which he/she has data access to

• Delete – Delete data of his entity and the entities for which he/she has data access to

• Upload – Upload documents for his entity and the entities for which he/she has data access to

• Download – Download templates or download data (forms or trial balance) and the entities for which he/she has data access to

• Approve/Reject – Approve or reject the GL mapping module of his/her entity alone

• All the members of the finance controller group approve the following data

If a finance controller adds, edits or deletes the following modules, then the change has to be approved by the corporate controller.

• Add Investments (add, edit or delete)

• Forms (add, edit or delete)

If a finance controller adds or edits or deletes the GL mapping for his entity, then the change will be auto approved.

If the finance controller has entity access to another entity and any change made by the finance controller in the GL mapping has to be approved by the respective finance controller.

For ex: If entity A's finance controller has entity access to entity B and if A's finance controller adds, edits or deletes data in B's GL mapping, then B's finance controller has to approve the change done by A's finance controller.

Projects Module:

The finance controller will be able to do the following operations in the project’s module.

• View – View the data of his entity and the entities for which he/she has data access to

• Add – Add data for his entity and the entities for which he/she has data access to

• Edit – Edit data for his entity and the entities for which he/she has data access to

• Upload – Upload documents for his entity and the entities for which he/she has data access to

• Download – Download documents or templates for his entity and the entities for which he/she has data access to

• Approve/Reject – Approves or rejects the data of his entity alone. The finance controller will approve/reject the following modules.

  • Load TB of his entity

  • Load BC of his entity

  • Load ICO of his entity

  • Load Other Adjustments of his entity

If a finance controller adds or edits or deletes the TB, BC, ICO or other adjustments of his/her own entity, then the change will be auto approved.

If the finance controller has entity access to another entity and any change made by the finance controller in the project module has to be approved by the respective finance controller.

For ex: If entity A's finance controller has entity access to entity B and if A's finance controller adds, edits or deletes data in B's TB, BC, ICO or other adjustments, then B's finance controller has to approve the change done by A's finance controller.

Entity Team:

Setup Module:

The entity member will be able to do the following operations in the setup module.

• View – View the data of his entity and the entities for which he/she has data access to

• Add – Add data of his entity and the entities for which he/she has data access to

• Edit – Edit data of his entity and the entities for which he/she has data access to

• Delete – Delete data of his entity and the entities for which he/she has data access to

• Upload – Upload documents of his entity and the entities for which he/she has data access to

• Download – Download templates or download data and the entities for which he/she has data access to

If the member of the entity team adds, edits or deletes any data in the setup module, the change should be approved by the corporate controller.

This change will be effective only if the data is approved by the corporate controller.

For ex: If a member in the corporate controller team adds a new form, then the form will be visible to all the members of the team only if the corporate controller approves the change.

However, the GL mapping of each entity is approved by the respective finance controllers.

Projects Module:

The entity member will be able to do the following operations in the project's module.

• View – View the data of his entity and the entities for which he/she has data access to

• Add – Add data of his entity and the entities for which he/she has data access to

• Edit – Edit data of his entity and the entities for which he/she has data access to

• Delete – Delete data of his entity and the entities for which he/she has data access to

• Upload – Upload documents of his entity and the entities for which he/she has data access to

• Download – Download documents or templates and the entities for which he/she has data access to

If the entity team member adds, edits or deletes data in Load TB, Load BC, ICO or other adjustments, then this change has to be approved by the finance controller.