Changes to Setup

Group Structure Changes:

If there are any ongoing projects, then the edits to the group structure should not be allowed.

  • The group structure edits include

  • Add Entity

  • Edit Entity Name

  • Edit Identifier

  • Edit functional currency

  • Edit investments

Changes to Forms:

  • If there are any ongoing projects and if there are any changes in the forms

Scenario 1:

  • If the financial statements are not generated before the edits in forms, then the user will hit ‘Run Consolidation’ to generate the financial statements.

Scenario 2:

  • If the financial statements are generated but not published and the forms are edited after the generation of financial statements, then the user should not be allowed to ‘Publish’ the financial statements until the financial statements are refreshed.

Scenario 3:

  • If the financial statements are generated and published and if there are any edits to the forms, then this change will not affect the published financial statements.

Changes to BC Form:

During an ongoing project, the user will not be allowed to edit the asset register and tax rate.

Changes to COA Master:

  • If there are any ongoing projects, then the user is not allowed to delete the COA master line item. However, edits to COA master line item should be allowed even if there are any ongoing projects.

  • Any edits in the COA master should flow downstream to the forms, GL mapping, ICO, Load BC and Other adjustments.

  • If there are any edits in the L3 and L4 values during an ongoing project,

Scenario 1:

  • If the financial statements are not generated before the edits in COA master, then the user will hit ‘Run Consolidation’ to generate the financial statements.

Scenario 2:

  • If the financial statements are generated but not published and the COA Master line items are edited after the generation of financial statements, then the user should not be allowed to ‘Publish’ the financial statements until the financial statements are refreshed.

Scenario 3:

  • If the financial statements are generated and published and if there are any edits to the COA Master line items, then this change will not affect the published financial statements.

  • The deletion of COA master will happen only if there are no ongoing projects.

  • If there are no ongoing projects and if the user tries to delete a line item in the COA master and if the same L3 and L4 has been used in any of the forms or GL mapping, the user will be notified with the list of all the forms and GL mapping and the user will be asked to remap the L3 and L4 in all the list of items.

  • The COA line item will be deleted if and only if the line item is not mapped anywhere in the setup module.

Changes to GL Mapping:

  • If there are any ongoing projects, then the user is not allowed to delete the GL Code. However, edits to L3 – L4 and GL Description should be allowed even if there are any ongoing projects.

  • If there are any edits in the L3 or L4 or GL Description during an ongoing project

Scenario 1:

  • If the financial statements are not generated before the edits in the GL mapping, then the user will hit ‘Run Consolidation’ to generate the financial statements.

Scenario 2:

  • If the financial statements are generated but not published and the GL mapping line items are edited after the generation of financial statements, then the user should not be allowed to ‘Publish’ the financial statements until the financial statements are refreshed.

Scenario 3:

  • If the financial statements are generated and published and if there are any edits to the GL mapping line items, then this change will not affect the published financial statements.

  • The deletion of GL mapping line item(s) will happen only if there are no ongoing projects.

PreviousFinancial StatementsNextBook Close

Last updated