System Setup Guides

Prepare, configure, and test each Accounting System supported by API.1.

Each Accounting System has different requirements for test access, vendor applications, credentials, and production approval. These guides describe the parts that differ by system and link back to the shared System Settings workflow.

System Settings are the standard setup path for new integrations wherever supported. If a system does not yet expose System Settings, its guide documents the current Zwapgrid-managed process instead.

Choose a system

System	Connection setup	Recommended test option	Guide
Billy	Current Zwapgrid-managed setup	Dedicated Billy test company	Billy
Bjorn Lunden	System Setting	Vendor-provided sandbox	Bjorn Lunden
Bokio	System Setting	Test-mode app and test company	Bokio
Business Central	System Setting	Trial or sandbox environment	Business Central
DATEV Online	System Setting	DATEV Sandbox with an eligible dataset	DATEV Online
Exact Online	System Setting	Developer account and test administration	Exact Online
Fortnox	System Setting	Developer sandbox	Fortnox
Finago Procountor	System Setting	Private test environment	Procountor
QuickBooks Online	System Setting	Intuit sandbox company	QuickBooks Online
Tripletex	Current Zwapgrid-managed setup	Tripletex API test account	Tripletex
Visma Dinero	Current Zwapgrid-managed setup	Dedicated Dinero test company	Visma Dinero
Visma e-conomic	Current Zwapgrid-managed setup	Demo agreement	Visma e-conomic
Visma Netvisor	System Setting: Zwapgrid-managed Production/Sandbox	Partner test environment	Visma Netvisor
Visma Spiris	System Setting	Partner sandbox	Visma Spiris
Xero	System Setting	Xero demo company	Xero
Kleer	Current Zwapgrid-managed setup	Kleer API access arranged with Kleer	Kleer

System Setting means that you configure the credentials or connection options supported by that system. Current Zwapgrid-managed setup means that System Settings are not yet exposed for that system; follow the existing process until a client-managed setup becomes available or Zwapgrid agrees a migration with you.

Shared testing checklist

For every system:

1. Use a test company that contains no real personal or financial data.

2. Configure the minimum permissions needed by your API.1 and Proxy.1 operations.

3. Create a Development Consent and complete the Onboarding Flow.

4. Test every read and write operation your product will use.

5. Record any vendor approval or reauthorisation requirements before production rollout.

The endpoint support matrix is maintained separately in Systems in the grid.