Glossary

A task assigned to a user with insufficient rights to undertake the task. Visma.net Approval will send an email to System Administrator explaining how to unblock the task.

A written note attached to the document visible to all approvers in the workflow and to the System Administrator.

A collection of similar cost units. Examples can include Department or Project and large organisations may require a large number of cost unit types to organise the structure of their accounts.

A financial unit to which costs can be allocated and subsequently analysed and reported. Examples of everyday cost units within a Department cost unit type are Marketing, Sales and R & D.

A user who is responsible for setting up the company, users and user groups on Visma.net.

The user marked as deputy will only receive documents to prevent other users from approving their own documents.

The content to be approved. Typically a combination of attachments and data. For example: invoice, expense claim.

The reference used by the originating service to identify the document sent to Visma.net Approval.

The specific type of document. For example: invoice, expense claim.

One possible outcome of a task when the user transfers his/her task to another approver.

The user name of the employee who requested the goods or services being invoiced, as specified in the originating service (if available). If given, this is the first person to receive the document for approval. The setting Allow editing by the initial approver (if given) determines whether or not this initial approver may edit the document within Visma.net Approval.

Approval of individual document lines.

User who is responsible for approval of one or more document lines.

An email alert which users receive when they get a new task or are appointed as substitute.

Task which is past the due date.

System generated summary email which consists of all pending tasks. Digests are sent out at user preferred intervals.

Future task that will be started when its preceding tasks are completed.

A series of steps through which a document is routed in Visma.net Approval.

One possible outcome of a task when the user disagrees with the content of the document. The process is stopped immediately and the outcome is returned to the service the document was sent from.

An email send automatically from Visma.net Approval about pending tasks.

One possible outcome of a task when the user requests another approver for an opinion. Once reviewed the task will be returned to the requester.

An administrator-configurable function (examples: "Approver", "Senior Approver", "Managing Director"), which can be assigned to one or more users at cost unit or project level.

A task currently awaiting a decision.

Steps occur between the start and end of a workflow. A step can generate one or more tasks, or be skipped if the invoice is above or below a configurable value. A step can contain multiple rules. Rules can specify how approvers are selected, for example by their roles within a cost unit combination, their role within the organisation or based on a list of specified users. Rules can be disregarded if the invoice is above or below a configurable value.

The user who is appointed to handle tasks on behalf of another approver for a period of time.

The user who is responsible for administering the system.

A task is a user-assigned obligation to approve or reject a document. If an approver does not feel able to reach a decision, then the task can be forwarded to a different approver within the organisation.