> 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/procountor.md).

# Procountor

Request a Procountor test environment and configure its Zwapgrid System Setting.

Finago Procountor is a cloud financial-management product used in the Nordic region. Set up new Procountor integrations through Zwapgrid System Settings.

| Item                        | Details                                              |
| --------------------------- | ---------------------------------------------------- |
| Client Portal configuration | Available                                            |
| Test option                 | Private environment on Procountor's testing server   |
| Vendor documentation        | [Procountor Developers](https://dev.procountor.com/) |

## Request a test environment

Submit Procountor's [testing-environment request](https://dev.procountor.com/contact/request-testing-environment/). Procountor supplies test credentials, a company, and the client credentials required by its OAuth flow.

The redirect URI is registered against the Procountor API client. It must not contain a query string. If it changes, contact Procountor with the client ID and replacement URI.

Do not enter real or customer-specific information in the Procountor test environment.

## Configure Zwapgrid

1. In the Client Portal, open **Systems → Procountor → Configure**.
2. Create a System Setting for the test client.
3. Enter the Procountor Client ID and Client Secret.
4. Confirm that the redirect URI registered by Procountor matches the value shown by Zwapgrid.
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 test setting.
2. Connect the Procountor test company through the [Onboarding Flow](/onboarding-flow/onboarding-flow.md).
3. Test all required endpoints and user permissions.
4. Review Procountor's [API certification checkpoints](https://dev.procountor.com/api-certification/).
5. Request production API credentials when the integration is ready.
6. Store production credentials in a separate Zwapgrid System Setting.

{% hint style="warning" %}
Procountor test and production environments use different server addresses and credentials. Do not reuse a test System Setting for production.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.