Visma Net
Set up and configure the workspace
Go to the Number series (CS201010) window.
Check which number series your company uses and, if necessary, create the following:
- EPCLAIM - expense claims
- TIMECARD - time cards
- PMTRAN - project transactions
- PROJECT - project numbers
Go to the Segment keys (CS202000) window and, if necessary, create the following:
- EMPLOYEE
- PROJECT
- PROTASK - project task
- ACCGROUP - account group
Go to the Reason codes (CS211000) window. You must provide reason codes when you issue stock on projects, for example:
Reason code | Description | Usage |
---|---|---|
Project | Material for project | Issue |
Before using labour rates, you have to create non-stock items of the type Labour and link them to employees. For example, you can create a labour rate called Senior consultant and link this to the employees working as senior consultants.
When creating a labour rate, you have to select an item class and a posting class.
For each item, the posting class defines the accounts and subaccounts used to post transactions to the general ledger.
Go to the Posting classes (IN206000) window.
The following posting classes are available for the Projects workspace:
ID | Description |
---|---|
9 | Services |
10 | Project expenses (Travel) |
These posting classes are linked to the item classes below.
Go to the Item classes (IN201000) window.
The following item classes are available for the Projects workspace:
ID | Description |
---|---|
8 | Services |
9 | Project expenses (Travel) |
These posting classes and item classes ensure that the labour and expense items used in the Projects workspace are linked to the correct general ledger accounts.
If the accounts that are linked to the stock and non-stock items are not linked to an account group, transactions on these accounts will not show up in the project balance.
Go to the Non-stock items (IN202000) window.
Create non-stock items with the type Labour.
Labour items provide information on hourly rates, general ledger accounts, and VAT categories you want to use to account for labour in projects.
Example:
Item ID | Description | Item class | Type | Default price |
---|---|---|---|---|
PManager | Project Manager | 8 | Labour | 1200 NOK |
On the General ledger accounts tab, check that these accounts are correct: Expense accrual account, Expense account, Purchase accrual account, Sales account and Purchase price variance account.
Go to the Work calendar (CS209000) window.
Work calendars are connected to employees and determine how many hours employees should register in their time sheets. Work calendars are also used for employees that work part-time.
On the Exceptions tab, you can register days that are considered public holidays in your country.
Go to the Employee classes (EP202000) window.
Employee classes are used to group employees with similar properties and to provide default settings for new employees. The system contains one employee class to begin with.
On the General settings tab, review the general ledger accounts and settings to make sure they are correct.
Go to the Departments (EP201500) window.
Create the departments you need for your company, for example:
Department ID | Description |
---|---|
CONSULT | Consultancy |
Go to the User roles (SM201005) window.
Create the roles you need for your company and assign the proper levels of access to the Project Accounting windows.
Go to the Positions (EP201000) window.
Create the positions you need for your company, for example:
Position ID | Description |
---|---|
PMANAGER | Project manager |
Go to the Employees (EP203000) window.
Create the employees you need for your company. You can start by creating yourself as an employee for testing purposes. For detailed guidance, see Create an employee.
Go to the Users (SM201010) window.
- In the Login field, select your own user profile. Your user profile is displayed.
- In the Linked entity field, select the employee profile you created for yourself.
- Repeat this procedure for other users if needed. If an employee profile is not linked to a user profile, it is not possible to register time sheets or expenses for the given employee.
Go to the Company tree (EP204060) window.
This window is used to set up which users will have access to employees' time sheets and expenses.
For example, if you provide a user with project-controller access in the top of the company tree, that user will have access to time sheets and expense claims of all employees working on the project.
This can, for example, be useful when an employee is not able to enter their own time sheet. The project controller can then enter the time sheet on behalf of the employee.
Go to the Project accounting preferences (PM101000) window.
Please review all the preferences for the Projects workspace. For detailed guidance on setting these preferences, see: Set preferences for projects
Select the workspaces you want to integrate with the Projects workspace. If, for example, you have not selected Time and expenses, users will not be able to register hours and expenses to projects.
Account groups make it possible to transfer information between the Projects workspace and other workspaces by associating transactions posted in other workspaces with a given project. Account groups are used to track the budget, expenses, and revenues of projects. An account group of a particular type is mapped to specific general ledger accounts of the same type.
Review the account groups and linked general ledger accounts shown in the Account groups (PM201000) window. If needed, you can create supplementary account groups. For more information, see: Create an account group
For any project, the related account groups are displayed on the Balances tab in the Projects (PM301000) window and show the accumulated transaction amounts for the linked general ledger accounts.
If you want Visma Net to display the general ledger accounts for stock items, non-stock items, expense items, and labour items in the project balance, you must make sure that you have registered the expense accounts for these items.
You can only select accounts that are linked to account groups in the Allocation rules (PM207500) window.
If your project uses a pricing model in which price may
differ depending on multiple factors, such as task and stock item, you need
to define this model in Visma Net by using rate tables that provide rates for different sets of
factors.
For more information, see: Configure a rate table
Go to the Rate tables (PM204200) window.
Use the following rate table:
Rate table | Description |
---|---|
STANDARD | Standard rate able |
Rate types define how rates should be selected for specific steps of the allocation rules.
Go to the Rate types (PM204100) window.
The Projects service comes with the following rate types.
The allocation rules provided by Visma Net use the following rate types:
Type | Description |
---|---|
1 | Invoicing rate for labour |
2 | Invoicing rate for material |
3 | Invoicing rate for subcontractors |
4 | Invoicing rate for travel expenses |
Go to the Rate lookup rules (PM205000) window.
Rate lookup rules allow you to create sequences that the service will use to find the correct rate in the rate table. For example: If you want to use different rates for different tasks, you can select the Project task check box in a sequence, and then use the Rate tables (PM204200) window to define the rate, and to specify the particular tasks you want to apply this rate for.
If you select the Project task check box, the Rate tables (PM204200) window will display the Project task tab. The same logic goes for project, account group, inventory, and employee.
Go to the Rate table maintenance (PM206000) window to specify the actual rates for each sequences or for each combination of particular factors.
On the Rate tab you set the start/end date and the actual rate for the selected combination. The second tab will depend on the factor chosen in the Rate lookup rules (PM205000) window. It can be either Project, Project task, Account group, Item or Employee. On this second tab, you specify the parameters for the given rate.
For more information about how to create project attributes, see: Create project attributes
The attributes shown in the Project attributes (PM202000) window (and on the Attributes tab in other project-related windows) can be used when you set up allocation rules for a project:
MARGIN (can be used with the allocation rule Cost plus).
If you now enter 10 as the attribute for margin in a project (with the allocation rule for cost plus projects), the system calculates a 10% margin over all costs.
In the Projects workspace, the process of allocating amounts to specific accounts, account groups (or both) to acknowledge expenses and revenues is called 'allocation'.
Each month (or other period), you can allocate amounts of the expenditures involved in the project and the predicted future revenues.
Invoicing rules are used to specify which allocated transactions in the Projects workspace that you want to include in the invoices.
You select the transaction based on the account group they are associated with.
Allocation rules are used to correctly track project expenditures and revenues.
If your project uses a complex cost accrual model, allocation rules ensure that project
expenditures and future revenues are tracked correctly. Allocation rules are managed in the Allocation rules (PM207500) window.
For more information, see: Set allocation rules
The following allocation rules are included in Projects workspace:
1 - Fixed price, unrecognised revenue | Projects your company has negotiated a fixed price with the customer for. |
2 - Time and material, unrecognised revenue | Projects you invoice the actual use of time, materials, and expenses for. |
3 - Time and material with WIP, unrecognised revenue | Same as Time and material, but when the system allocates all time, material, and expense, the system transfers the transactions to a work-in-progress (WIP) account (balance account). |
4 - Cost plus project, unrecognised revenue |
These projects do not use the rate table to calculate the sales rates, but instead use a mark-up percentage for all project transactions. You must enter the mark-up percentage in the Projects (PM301000) window, on the Attributes tab. |
5 - None | Can be used for internal projects you only register expenses for. |
Invoicing rules define which of the transactions should be used for invoicing and which accounts should be used to record the transactions that are generated in the invoicing process. Invoicing rules are managed in the Invoicing rules (PM207000) window.
For more information, see: Create an invoicing rule
The following invoicing rules are included in Projects workspace:
1 - Standard | A standard invoicing rule that has no particular functionality. You can use this to invoice the transactions that have been registered in the Not yet invoiced account group. |
2 - Guaranteed maximum price | An invoicing rule that registers the amount that was entered on the budget on account group revenue, and does not allow any invoicing transactions that could involve exceeding the revised, budgeted quantity or amount (or both). |
3 - WIP invoicing | This invoicing rule uses only allocated transactions that include accounts of the WIP account group. |
4 - None | This invoicing rule can be used for internal projects or projects that will not be invoiced. |
The following combinations of allocation and invoicing rules are supported by the Projectsworkspace:
Invoicing rules Allocation rules |
Standard | Guaranteed maximum price | WIP invoicing | None |
Fixed price, unrecognised revenue | X | X | ||
Time and material, unrecognised revenue | X | X | X | |
Time and material with WIP, unrecognised revenue | (X)* | X | ||
Cost plus project, unrecognised revenue | X | X | X | |
None | X |
* Mark WIP account group in Invoicing rules.
You can also limit users' access to and visibility of information about particular projects and related transactions. You can use roles to provide access to windows according to employees' responsibilities and restriction groups to configure the visibility of particular projects only to a responsible team.