Configuration Setup

The following list provides examples of elements that are typically configured and changed for an individual customer.

These are, therefore, typical areas that customers need to consider during the Maconomy implementation. It may also require that some of the things mentioned in the following table are subject to some degree of data cleansing. You should also decide which fields should be available in specific parts of the Maconomy solution.

Setup Area	Description
Task lists	The lists of tasks on which an employee can make entries. There are typically different task lists depending on the project type.
Activities	A task is linked to an activity, and the activity determines the posting references to the finance system and how the postings are performed in the G/L module when creating entries in the Project Management module.
Template projects	A template project enables you to derive the task list, budget, project parameters, and other project elements automatically. You can also set up the Work Breakdown Structure (WBS) of the budget on each template.
Customers	The customers of the specific company and the information that is relevant to enter information on the given customer within the confines of available fields in Maconomy.
Projects	The projects of the company and the relevant information to enter information on the project within the confines of available fields in Maconomy.
Project types	A list of project types in the company, for instance “ERP system implementation” or “Hardware installation” if the company is an IT company. The project types are used for reporting purposes, for instance to find out what types of projects are most profitable.
Vendors	The relevant vendors of the specific company and the information to enter information on the given vendor within the confines of available fields in Maconomy.
Executing and Responsible Department	The departments in the organizational structure.
Company	The legal companies in the organizational structure.
Business Area	The business area within which the customer operates.
Chart of Accounts	The Chart of Accounts used by the company. This indicates how the P&L and Balance Sheet are broken down into accounts.
Account structure	The division of the Chart of Accounts into groups of accounts, primarily for reporting purposes.
Employees	The employees of the company and the information that is relevant to enter information on a specific employee, for instance, the employee’s cost and sales prices.
Users	A user must be defined for each employee in the company. The user is assigned to a certain role type, defining his or her access profile.
Groups	The groups specify which Maconomy windows are available for the users who are assigned to the group. This is a way to control access to the system. For each window, you indicate whether the users are allowed to create, delete, read, or update data.
Tax rules	The local tax rules for the country and the company.
Interest charge/ reminder principles	The methods by which you remind customers of late payments and the interest rate charged for late payments.
Employee categories	Grouping of employees into different employee categories. The employee categories derive the standard prices from the price lists for the projects and the project budgets.
Price lists	You can set price lists up as project-specific or customer-specific. You can also set up general price lists for the template projects that new projects can be based upon.
Approval Hierarchies and Approval Hierarchy Rules	The workflows are defined in the solution to allow you to use the best practice flows defined by other PSO clients. These flows, particularly for billing and expense reporting, are completed for you; however, you can easily create and manage your own workflow using the approval hierarchy engine.
Print layouts	Configuration of the print layouts for invoices, credit memos, and other customer-specific layouts.
Invoice layout rules	Configuration of the breakdown structure of the invoice.