About integration with other modules

If you integrate the Projects workspace with other workspaces, the active projects defined in the Projects workspace become visible in those workspaces.

All data entry windows of any integrated workspace include two additional elements, Project and Task.
Each time you enter a transaction that relates to a specific active project in the Projects workspace, you can associate the transaction with this project by selecting the appropriate project and task.

The non-project code, which is specified in the Project accounting preferences (PM101000) window, is a code that you can use to indicate that specific transactions are not associated with any project.
By default, this code is X, but you can specify a different non-project code.

• Once you activate the Projects workspace and integrate another Visma.net ERP workspace with it, users must specify Project and Task values when they enter transactions in the data entry windows of that workspace.

• If you do not want to associate a particular transaction with any project, you must select the non-project code as the Project.
  With this code selected, no information will be transferred to the Projects workspace and no project balances will be updated.

With the integration between the Projects and General ledger workspaces, in the General ledger workspace, you can directly enter transactions related to specific project tasks.

• If you plan on integrating the Projects workspace with any of the Visma.net ERP workspaces, we recommend that you integrate it with the General ledger workspace too.

• Even if the Projects workspace is not integrated with the General ledger workspace, by using account groups that are mapped to general ledger, you will be able to view the transactions that are generated in other integrated workspaces and eventually posted to General ledger.

When you integrate the Projects workspace with the Supplier ledger, Inventory, and Purchases workspaces, the mandatory Project and Task columns are added to data entry windows in the integrated workspace so that purchases of stock items, non-stock items, and services can be associated with specific project tasks, as can inventory transactions.

• Each time you enter a document in any of these workspaces, you must either specify the project and task to associate with the current transaction or select the non-project code.

• Integrated workspaces do not post transactions to Projects directly.
  A transaction originating in the Purchases workspace, on release, generates transactions in the Inventory workspace and in the Supplier ledger workspace.
  

• The transactions related to projects in the Supplier ledger and Inventory workspaces are first released and then posted to the General ledger workspace; then from the General ledger workspace, they are copied to the Projects workspace.
  

• To update the General ledger workspace with the full details of the original transactions, clear the Post summary on updating general ledger check boxes in the Supplier ledger preferences (AP101000) and Inventory preferences (IN101000) windows.

When you integrate the Projects workspace with the Sales and Customer ledger workspace, in the windows of these workspaces, the Project field is added to the top part and the Task column is added to the Details area.

• If you selects a specific project, you must also specify a particular task of this project.

• Transactions originating in the Sales workspace, on release, generate transactions in the Inventory and Customer ledger workspaces.
  The Customer ledger and Inventory workspaces do not post transactions to Projects directly.
  The original transaction is first released and then posted to General ledger, and then from General ledger it is copied to the Projects workspace.
  

• To update the Projects module with the full details of the original transactions, clear the Post summary on updating general ledger check boxes in the Customer ledger preferences (AR101000) and Inventory preferences (IN101000) windows.

When you integrate the Projects module with the Time and expenses workspace, the Project and Task columns are added on all data entry windows. These columns are mandatory.

• If your employees work on projects managed by using the Projects module, you can use the Time and expenses workspace to track the time they spend on projects, including regular time and overtime.
  By default, you use time cards for this purpose, but you can instead use expense claims.

• Once released, a time card or an expense claim associated with a specific project does not directly generate general ledger transactions; instead, Visma.net ERP generates one or more transactions in the Projects module.
  By using the options located in the Time and expenses preferences (EP101000) window, you can select whether the transactions from the Projects module will be posted to an account group of the Off-balance type or to account groups of standard types: Asset, Liability, Expense, and Income. The General ledger will be updated through the transactions generated based on the transactions posted to account groups of standard types.

• To reduce the time required for transaction processing, select the Automatically release project documents in the Time and expenses preferences (EP101000) window.

• In the Time and expenses workspace, notes and attached documents from a Time and expenses transaction can be copied to a Projects transaction if the Copy files to project documents and Copy notes to project documents check boxes are selected in the Time and expenses preferences (EP101000) window.

• You can use expense claims to track the expenses your employees incur when they work on specific projects.
  Once released, an expense claim associated with a specific project does not generate customer ledger transactions; instead, Visma.net ERP generates transactions in the Projects module that, in turn, will generate the customer ledger transactions.

• Once released, a time card associated with a specific project does not generate general ledger transactions.
  Instead, Visma.net ERP generates transactions in the Projects module.