With the Severa–PowerOffice integration, you can transfer sales invoices seamlessly from Severa to PowerOffice. The integration also allows you to import purchase invoices from PowerOffice into Severa as project costs. This enables you to manage project business efficiently in Severa and handle accounting in PowerOffice, minimizing the need for manual data entry.

The integration synchronizes customers, business units, regular products, projects and employees between the systems. Projects created in Severa can be transferred to PowerOffice, and sales invoices are transferred automatically based on the invoice status. The status of sent invoices and the status of paid invoices are also updated back to Severa. Purchase invoices are transferred from PowerOffice to Severa by assigning the cost in PowerOffice to the corresponding Severa project.

Data transfer in the integration works automatically in a staggered cycle based on the time of day. This optimizes system performance and ensures that the data is as up to date as possible when it is needed the most. Data is synchronized according to the following schedule (times in Finnish time):

Before the integration is enabled, it is important to ensure the following:

In the integration you choose which of the systems is the master. The master selection affects the transferred data as follows:

Customers are matched between the systems based on the customer number. The following rules apply to transferring customer data between the systems:

Once these criteria are met one time, the integration will remember the customer in the future even if the criteria change later. The headquarter address of the Severa customer is transferred to PowerOffice as the delivery address.

Severa’s regular products, work types and travel expenses are synchronized with the PowerOffice product registry. Items are matched based on the Severa product, work type and travel expense identifier and the PowerOffice product code. The following rules apply to synchronizing regular products, work types and travel expenses:

Projects are matched based on the project number. Only projects whose status in Severa is Voitettu (won) are transferred to PowerOffice. If you create a project directly in PowerOffice, it is created in Severa automatically with the status Won.

Severa business units are synchronized with PowerOffice departments. Matching is done based on the code entered in the Severa business unit details and the PowerOffice department code. Make sure that the codes match in both systems. You can find the business unit code in Severa under the cogwheel icon in Settings > Organization > Business units.

To activate the integration, you must first enable the related add-on. In Severa, go to the cogwheel icon: Settings > Subscription > Integrations and switch on the PowerOffice option.

Next, a secure connection must be established between the systems. The user activating the integration must have sufficient permissions in PowerOffice: the user must either be an administrator in PowerOffice or have the permission Settings > Organization.

Define the general rules for the integration, such as the master systems for registries and invoice statuses, according to the detailed instructions below.

Make sure that the registry check has been performed before enabling the integration using the Registry comparison report . The report calculates similarity scores for items and shows whether they will be matched correctly according to the integration logic.

When all settings have been defined and the customer, product, work type, travel expense and project registries have been checked, activate the integration by switching on the main toggle Enable integration.

Severa invoice statuses are used to trigger data transfer and to track the situation. Plan and create in Severa the invoice statuses you want to use in the integration. The following invoice statuses are required in the integration:

PowerOffice acts as the master for sales invoice numbers. Make sure that new invoice numbers do not overlap with any old numbering in the systems and that numbering continues consistently.

Purchase invoices are transferred from PowerOffice to Severa by assigning the project number to the invoice row in PowerOffice. After this, the purchase invoice rows are transferred to Severa as costs of the respective project in the Financials > Fees & other expenses section.

| Field in Severa | Field in PowerOffice | Description |
| --- | --- | --- |
| guid | Id | Unique identifier |
| productCategory | ProductGroupCode | Link to product category |
| code | Code | Primary product code or SKU |
| name | Name | Product name |
| proposalDescription | Description | More detailed product description |
| unitPrice.amount | UnitPrice | Default unit price (before VAT) |
| measurementUnit | UnitOfMeasureCode | Unit of measure |
| | | |
| isActive | IsArchived | Product status (Active / Archived) |
| type | ProductType | Logical mapping:
Severa: FixedFees + Materials = PO: Product
Severa: SubContracting = PO: Service |

| Field in Severa | Field in PowerOffice | Description |
| --- | --- | --- |
| ProjectCode | ProjectCode | Project code (required for cost billing) |
| ProductCode | ProductCode | Product code |
| Quantity | Quantity | Quantity |
| unitPrice.amount | ProductUnitPrice | Product unit price |
| Description | Description | Row description text |
| productType | FromProduct | Mapping:
Severa: FixedFees + Materials = PO: Product
Severa: SubContracting = PO: Service
​If there is no product code, the default product is used. |
| unitPrice.currencyCode | CurrencyCode | Currency code |