Visma Netvisor

Select the Netvisor production or sandbox integration and connect a company.

Netvisor is a Finnish cloud financial-management product. Netvisor System Settings select Production or Sandbox (test) while Zwapgrid manages the integration's partner credentials. You do not enter your own partner ID or partner key in these settings.

Item	Details
Client Portal configuration	A name and a Netvisor environment: Production or Sandbox
Integration credentials	Managed by Zwapgrid
Test option	Netvisor partner test environment
Vendor documentation	Implementing a Netvisor integration

This requires Netvisor environment selection to be available in your Zwapgrid deployment and the selected integration to be configured by Zwapgrid. If it is unavailable, contact support. A Development Consent alone does not select the Netvisor sandbox.

Request a test environment

Netvisor provides test environments through its software-partner process. Register through the form linked in the vendor guide and request test access.

The environment is initially empty. Add representative data through the Netvisor user interface or ask Netvisor partner support about available test-data options. Never copy real customer data into the test environment.

Connect the test company

1. In the Client Portal, enable Visma Netvisor under Systems.

2. Select Configure and create a System Setting with a descriptive name.

3. Open Manage, choose Sandbox (test), and select Save changes. Review and publish the setting. Its environment cannot change after publication.

4. Create a Consent using this published setting. You can make it the client default before creating the Consent, or select it for this Consent. For an explicit selection in Quick Start, use the Netvisor System Setting field. For an explicit API selection, provide its ID in systemsSettings:

{
  "name": "Netvisor sandbox connection",
  "systemsSettings": {
    "VismaNetvisor": "YOUR_PUBLISHED_SANDBOX_SETTING_ID"
  }
}

1. Complete the Onboarding Flow with the Netvisor test company's user ID, API key and business ID. Use the integration search key displayed by that flow when granting Netvisor access.

2. Test every required API.1 and Proxy.1 operation and record the Netvisor interface-resource permissions your use case needs.

When Sandbox is the client default, new consents without an explicit Netvisor setting use Sandbox, including consents classified as Production. An explicit setting overrides the default. Changing the default does not change existing consents or connections.

You continue using the normal Zwapgrid production endpoints; no access to Zwapgrid's internal Test deployment is required.

Consent type and Netvisor environment

A Consent's Development/Production classification and its Netvisor environment are separate choices. The public Consent API derives the classification from your API key; the Client Portal selects it when creating the Consent. The selected System Setting chooses the Netvisor integration independently of that classification.

Existing consents retain their existing integration. New consents with neither an explicit Netvisor setting nor a Netvisor client default use the deployment's legacy integration; on Zwapgrid's production deployment, that is Netvisor Production. Creating a Sandbox setting or making it the client default does not move existing connections.

To change a connection's environment, create a new System Setting and a new Consent, then complete onboarding again. Do not reuse production company credentials in a sandbox connection.

Connect a production company

Create a named Netvisor System Setting. Open Manage, choose Production, save the changes, then publish the setting. You can use it explicitly for a Consent or make it the client's default for new Netvisor consents. Production settings also use Zwapgrid-managed partner credentials.

• Confirm that the customer has activated the required Netvisor interface service.

• Confirm that the onboarding user can grant access to the required resources.

• Validate the integration with a controlled production pilot after sandbox testing.

• Review Netvisor's current production-validation requirements before rollout.

Support for supplying your own Netvisor partner credentials is not part of this setting. Environment choices for other Accounting Systems follow their own setup guides; this selector does not add sandbox support to every provider.

For a Zwapgrid connection problem, contact [e-mail] with the Consent ID, UTC timestamp, and correlation or request ID. Do not include Netvisor identifiers or keys.