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

# Billy

Prepare a Billy company and test its API.1 connection.

Billy is a Danish cloud-accounting product for small businesses. Billy does not yet expose a separate System Setting in the Zwapgrid Client Portal, so the current setup is Zwapgrid-managed.

| Item                        | Details                                                |
| --------------------------- | ------------------------------------------------------ |
| Client Portal configuration | No separate System Setting                             |
| Test option                 | A dedicated Billy company used only for testing        |
| Vendor access               | [Create a Billy account](https://www.billy.dk/signup/) |

## Before you start

Prepare a Billy company that does not contain live customer data. Add enough representative accounting data to test every API.1 operation your product uses.

If you need direct Billy API access outside the Zwapgrid connection, Billy documents how to create an [API access key](https://www.billy.dk/support/article/saadan-opretter-du-en-api-noegle-adgangsnoegle/). Do not send that key to Zwapgrid support.

## Connect the test company

1. In the Client Portal, enable Billy under **Systems**.
2. Create a Development Consent.
3. Generate an [Onboarding Flow](/onboarding-flow/onboarding-flow.md) link for the Consent.
4. Complete the flow with the Billy test company.
5. Use the Consent ID to test the required API.1 operations.

## Production checklist

* Use a new Production Consent for each company you connect.
* Confirm the Billy user completing onboarding can access the intended company.
* Test both empty and populated data sets where applicable.
* Keep any vendor access keys outside logs, tickets, and documentation.

{% hint style="info" %}
For connection problems, contact <support@zwapgrid.com> with the Consent ID, UTC timestamp, and correlation or request ID. Do not include credentials.
{% 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/billy.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.