Skip to end of banner
Go to start of banner

Templates

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Current »

Templates are used in the implementation when eg. no integration are generating content such as users, organizational structure, groups of users or prisce lists for compliance and pris match purposes.

Some modules will not have use for templates, others will use templates although being comtomized during the implementation startup and process. In such cases there will be a description and examples in combination with the module overview listet here.

The following list is build into three fields under each module title with the following information seperation idea.

Title

Description

Documents, files and video examples

Contract module

Contract template

Frame agreement structure

Order template

Price list template

Price lists are used where the customer does not have a catalog or can not get their supplier to send one. In such cases price lists can be used to do both compliance and price check on item level regarding the specific agreement with a supplier.

The price lists can also be used in combination with catalogs thereby adding eg. a few products to the compliance and/or price check.

The document displayed is a template for these pricelists whichn the customers can fill out and upload to their sFTP-server.

Supported languages are currently:

  • Danish

  • English

  • Norwegian

Procurement Module

Ordering Module

Analysis Module

sFTP-setup / structure

Invoice formats

E-commerce degeree

Catalog formats

A customer can deliver catalogs used for compliance and pris check purposes. When delivered in the correct folder on the sFTP an automated import service will import them to the organization of choice and when approved an agreement will be generated automatically where compliance and price check can be configured.

Currently we only support the following formats:

  • EHF 3.0

  • EHF 1.0

  • OIOUBL

Price list format

Accounting data format

Accounting data is used in the invoice analysis to generate an accounting line overview related to the invoice lines. These data can give the customer the “correct” spend overview.

A new feature is that we can also map accounting line or/and header data to invoice data and thereby place invoices in the correct organizational units.This remedy the fact that most invoices are not send to the unit who actually pays causing the classic invoice analysis to show a skewed spend overview.

Organizational structure

The organizational structure used in the invoice analysis for mapping eg. invoices, measuring compliance an so on is currently separate from the organisation build for the procurement module in the data administration.
Therefore it is important that the customer describe their organization with unit ID’s for import in the implementation process.

Invoice Module

Approval flow structure

Administrative Module

Users

Users can be generated one by one in the administration but can also be mass imported in the dataadministration.
The attached file is an example on the file which can be send to the customer to fill out.

Groups

Prokura

Approval flow

Organization

The organizational structure used in the

Adresses

Adresses can be imported automatically through integration services or can be added in the administration. Alterna

  • No labels