> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/client-portal/systems/setup-guides/visma-eaccounting.md).

# Visma Spiris

Configure Visma Spiris credentials and scopes in Zwapgrid.

Visma Spiris, previously known as Visma eAccounting and Visma Spcs, provides bookkeeping, invoicing, and payroll products. Set up new Spiris integrations with a System Setting in the Zwapgrid Client Portal.

| Item                        | Details                                                                                                             |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Client Portal configuration | Available                                                                                                           |
| Test option                 | Spiris partner sandbox                                                                                              |
| Vendor documentation        | [Spiris/eAccounting API documentation](https://developer.vismaonline.com/docs/spiris-eaccounting-api-documentation) |

## Register for partner access

Register through the [Spiris API sandbox form](https://selfservice.developer.vismaonline.com/). Spiris supplies the application credentials and a sandbox company by email.

Use the sandbox only for application development. It cannot access production customers and some connected services are mocked or unavailable.

## Choose permissions

List every API.1 and Proxy.1 operation your product will use. Select the minimum matching Spiris scopes, including the required API and offline-access scopes documented by Spiris.

Read the vendor's current [authentication and scope reference](https://developer.vismaonline.com/docs/authentication) before publishing your configuration.

## Configure Zwapgrid

1. In the Client Portal, open **Systems → Spiris → Configure**.
2. Create a System Setting for the sandbox application.
3. Enter the Spiris Client ID and Client Secret.
4. Select the scopes required by your integration and confirm they match the vendor registration.
5. Save, review, and publish the setting.

See [System Settings](/client-portal/systems/system-settings.md) for lifecycle and Consent-selection rules.

## Test and move to production

1. Create a Development Consent using the published sandbox setting.
2. Connect the sandbox company through the [Onboarding Flow](/onboarding-flow/onboarding-flow.md).
3. Test all required operations and retain any vendor error IDs for troubleshooting.
4. Contact Spiris API support when you are ready for production access.
5. Store production credentials in a separate Zwapgrid System Setting.

{% hint style="warning" %}
Never send the Spiris client secret to vendor or Zwapgrid support. Include the vendor error ID and client ID when required for troubleshooting.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zwapgrid.com/client-portal/systems/setup-guides/visma-eaccounting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.