Visma Net
Project accounting preferences (PM101000)
This topic gives you information about the elements that you find in this window in Visma Net, such as fields, field values, buttons, and check boxes.
You use this window to set up the Projects workspace and to establish appropriate project management settings.
Here, you will find the general settings of the Projects workspace.
Element | Description |
---|---|
Transaction number series | The system uses this number to automatically assign reference numbers to project-related transactions. |
Batch number series | The system uses this number to assign reference numbers to project-related batches. |
Pro forma number series | The number series the system uses to assign reference numbers to pro forma invoices. |
Non-project code |
The project ID that indicates that a specific transaction or task is not related to any project. The default value is X. When the Projects workspace is integrated with other modules, data entry windows in those modules include the Project column, where the user must specify the project associated with the transaction. |
Empty item code |
The code to be specified as the Item ID to indicate that
no specific item is associated with a project transaction,
commitment, budget line of a project, or pro forma invoice line. The default empty item
code is <N/A>; you can specify a different code if
needed. The empty item code is treated as a real item in the Projects workspace, which gives users the opportunity to use this value in inquiries filtered by item, or to filter the rows in the windows of the Projects workspace by the empty item code you specify. In other workspaces, the empty item code is not supported
and treated as NULL. |
Invoiceable cut-off date |
In the Run project invoicing (PM503000) window, you have specified an Invoice date. Now, you can choose whether you want to include or exclude the transactions that are created on the invoice date for the automatic invoices.
|
Validate revenue budget limits for time and material |
Defines how the system validates the limits of the revenue budget of a project when you process pro forma invoices for the project. You can select one of the following options:
|
Cost budget update |
The way the system updates the cost budget of projects with cost transactions. When a cost transaction is posted to the Projects workspace, the system updates the corresponding project with this transaction. If the cost budget of the project has a line with the same project task, account group, and item, the system updates the actual quantity and actual amount of this line on the Cost budget tab of the Projects (PM301000) window with the quantity and amount of the transaction, respectively. Otherwise, the system adds a new cost budget line. The account group is the group to which the expense account
updated by the transaction is mapped.
|
Automatically post on release | A check box that determines whether project transactions will be automatically posted to General ledger once they are released. |
Automatically release allocations |
A check box that indicates whether Projects allocation transactions will be automatically released when generated. If you do not select this check box, you will be able to release the project allocation transactions manually by using the Release transactions (PM501000) window. |
Internal cost commitment tracking | If you select this check box,, purchase orders are tracked by project as cost commitment. |
Internal revenue commitment tracking | If you select this check box, sales orders are tracked by project as revenue commitment. |
By using the check boxes in this section, you can select the workspaces you want to integrate with the Projects workspace.
Option | Description |
---|---|
General ledger |
A check box that indicates whether transactions in the General ledger workspace can be associated with the project based on this template. If you select this check box, users can select the project in general ledger documents, and the release of these documents will automatically update the project data. |
Supplier ledger |
A check box that indicates whether transactions in the Supplier ledger workspace can be associated with the project based on this template. If you select this check box, users can select the project in supplier ledger documents, and the release of these documents will automatically update the project data. |
Customer ledger |
A check box that indicates whether transactions in the Customer ledger workspace can be associated with the project based on this template. If you select this check box, users can select the project in customer ledger documents, and the release of these documents will automatically update the project data. |
Sales |
A check box that indicates whether transactions in the Sales workspace can be associated with the project based on this template. If you select this check box, users can select the project in sales documents, and the release of these documents will automatically update the project data. |
Purchases |
A check box that indicates whether transactions in the Purchases workspace can be associated with the project based on this template. If you select this check box, users can select the project in purchase documents, and the release of these documents will automatically update the project data. |
Inventory |
A check box that indicates whether transactions in the Inventory workspace can be associated with the project based on this template. If you select this check box, users can select the project in inventory documents, and the release of these documents will automatically update the project data. |
Cash management |
A check box that indicates whether transactions in the Cash management workspace can be associated with the project based on this template. If you select this option, users can select the associated project and task when they enter a document in the Cash management workspace. |
Time entries |
A check box that indicates whether the transactions in the Time and expenses workspace can be associated with the task based on this template. If you select this check box, users can select the project in documents, and the release of these documents automatically updates the project data. |
Expenses |
A check box that indicates whether transactions from Expensecan be associated with the task based on this template. If you select this check box, users can select the project in documents, and the release of these documents automatically updates the project data. |
Restrict available projects in customer ledger | Select where the project selection list will be restricted, either for all projects or projects with a customer (in the customer ledger only). |
These elements define the rules for selecting the expense account and expense subaccount to be used in transactions generated in the Projects workspace on release of time cards.
Element | Description |
---|---|
Expense account source | The source of the account for the debit side of the project
transactions: The following options are available:
|
Expense sub. source | The subaccount mask that defines the rule of selecting segment
values for the expense subaccount to be used for project transactions. For a segment, the character designating the needed
option is repeated as many times as there are characters in the
segment. To set up the rule, select a segment, press F3,
and select a source of the segment value, which is one of the
following options:
This element is available only if the Subaccounts functionality is enabled in the Enable/disable functionalities (CS100000) window. |
Expense accrual account source | The source of the account for the credit side of the project transaction to be generated on release of the time cards. The following options are available:
|
Expense accrual sub. source |
The subaccount mask that defines the rule of selecting segment
values for the expense accrual subaccount to be used for the
Projects transactions generated on release of time cards. For a segment, the character designating the needed option is repeated as many times as there are characters in the segment. To set up the rule, select a segment, press F3, and select the source of the segment value, which is one of the following options:
This element is available only if the Subaccounts functionality is enabled in the Enable/disable functionalities (CS100000) window. |
The Mailing settings tab contains the list of predefined mailings that you can use for printing and electronically (by email) sending documents related to projects to customers. When a new project or a project template is created, the mailing settings specified on this tab are copied to the project or the project template.
By using the Default sources table, you can view and modify the list of active mailings that can be used to send emails for projects.
For each mailing, you can select either a report or an email template to be used by default as the body of the email.
Column | Description |
---|---|
Mailing ID | The unique identifier of the mailing. Visma Net provides two predefined system mailings:
|
Default email account |
The system email account to be used by default for sending emails for this mailing. If no account is specified, the default system account will be used. |
Report ID | The report of the Projects workspace to be used by default for printing and also as the
body or attachment of the email, if a report is used rather than an
email template. By default, the following reports are used for the predefined system mailings:
|
Notification template |
The email template to be used by default to generate personalised emails for this
mailing, if a template is used rather than a report. |
Format | The format in which the report (if applicable) will be sent by default if no preferences have been specified for a particular recipient. Select one of the following options: HTML, Excel, or PDF. |
Active |
A check box that indicates (if selected) that this mailing is active. Emails can be
generated only for active mailings. |
You use the Default recipients table to view and modify the list of
default types of recipients for the selected mailing.
The contact types
specified in the table are used as the default values for the contact types for
projects.
Column | Description |
---|---|
Contact type | The type of contact to receive emails:
|
Contact ID |
The specific contact. A particular recipient can be selected only if you have selected Employee as the Contact type. |
Format |
The format in which the report (if applicable) will be sent to recipients of this type. Select one of the following options: HTML, Excel, or PDF. |
Active |
A check box that indicates (if selected) that the contact of this type is active. Only active recipients receive the emails generated for this mailing. |
BCC | A check box that indicates (if selected) that the contact of this type will receive a blind carbon copy (BCC) of the emails. |