Enterprises

Workflows > Endpoints > Dimension Entities > Enterprises

Purpose: Retrieve enterprise details.

This workflow is typically used in cases involving employments and payroll, where the enterprise dimension is of relevance for the information transferred from or to Go. A company will allways have at least one enterprise registrered for it's operations, and a company may have multiple enterprises if the operations are split in multiple employer contribution zones.

Enterprises is not a dimension that will be subject of regular changes or new additions (new enterprises) on a common basis. Nonetheless, retrieving the dimension might also be relevant in cases where the integrating party need to synchronize enterprise information to make sure that PowerOffice Go and their own systems have the same information about their enterprises.

Regardless of the direction of the data flow, we highly recommend that the integrating party store the Id's of the PowerOffice objects. In general, the id's of all the various PowerOffice entities are the preferred mapping key, as they are uniquely assigned by the system and cannot be changed.

Endpoints

Description of core flow


Synchronize from Go

  1. Check if there are any new or newly updated enterprises in Go*

  2. Retrieve the desired fields and information

Prerequisites

  • Access to the enterprise access privelige

  • The client need at least one active subscription of a PowerOffice Go module


Related workflows

General relevance for most api workflows if location is used as a dimension


Dictionary/Terminology

Enterprises are dimension only used for payroll purposes in Go. Example: The company may have operations in Bod? and Oslo, in which case the company will have two enterprises for the two different employer contribution zones that Bod? and Oslo represent. When registering employments for the company's employees, the employment must include information on which enterprise the employment relate to.