Adapt the system to the way your business works.

Configuration

We use the product's capabilities and establish how they should work in your organisation.

• Selection of modules and roles
• Reference lists, numbering and templates
• Available process settings — depending on the module

Integration

We connect the data a process needs with tools you already use. We agree on imports, exports or an API connection after analysing the external system.

A custom module

We build support for a process outside the product's available scope: new objects, rules, views and actions connected to the relevant ERP data.

Example: accepting completed work before billing

If you need confirmation that work has been completed before issuing an invoice, we can analyse a work acceptance module. It would collect acceptance data, identify responsible people and pass the approved basis to billing. This is an example of a possible extension, with its scope still to be designed.

• Contract
• Work acceptance and decision
• Approved billing basis

How we define an extension

We describe the workflow, acceptance criteria and dependencies on other modules, updates and integrations.

• What business outcome should be achieved?
• What data is needed and where does it come from?
• Who performs the activity and who approves it?
• What happens when there is an exception?
• How will we verify and maintain the change?

Development after implementation

The shared product foundation provides a reference point for further development. We document configuration and extensions, and agree how they will be checked in subsequent releases as part of our cooperation.