Workflows with restrictions

Additional terms

As stated in the Visma Developer Terms section 2.3, developers and integrated applications that provide insurance, or financial related products or services, will require additional terms. Access will only be granted provided the additional terms are met.

We include our debt collection workflow and debt collection agencies as part of this definition. All debt collection agencies will need additional terms before we allow access to using our api's. This includes the situation where a third party is handling the integration on behalf of a debt collection agency.

If you represent a developer or integrated application subject to insurance, financial related products or services, or debt collection - please contact the api team at an early stage to discuss the additional terms.

Other restrictions

We generally strive to provide open api's, and a general openness to all external parties wanting to integrate with PowerOffice Go. This will enrich the marketplace of systems integrated with PowerOffice Go, benefitting both our customers and us with potential customers. However, we will pursue and preserve our commercial and strategic interests, and limit any use of our api's that might come in conflict theses interests.

This currently applies to integrated applications that provide general automation of the voucher accounting process. Specifically, if the intended workflow is that the external system will receive and handle all incoming vouchers, we will not allow for the automation of posting these voucher to PowerOffice Go. We require that the endpoint <JournalEntryVoucher> is used for this particular case, in order for the last step of posting the voucher is handled by a user in PowerOffice Go.