Exact online nl

Exact Online NL (via Apideck)

Access Exact Online NL through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Access Financials, Acumatica, banqUP and 30 other Accounting connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Exact Online NL plumbing.

Beta connector. Exact Online NL is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.

Quick facts

• Apideck serviceId: exact-online-nl
• Unified API: Accounting
• Auth type: oauth2
• Status: beta
• Gotchas: page
• Exact Online NL docs: https://support.exactonline.com
• Homepage: https://www.exact.com/nl

When to use this skill

Activate this skill when the user explicitly wants to work with Exact Online NL — for example, "create an invoice in Exact Online NL" or "reconcile payments in Exact Online NL". This skill teaches the agent:

1. Which Apideck unified API covers Exact Online NL (Accounting)
2. The correct serviceId to pass on every call (exact-online-nl)
3. Exact Online NL-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

• apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

• Accounting: https://specs.apideck.com/accounting.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List invoices in Exact Online NL
const { data } = await apideck.accounting.invoices.list({
  serviceId: "exact-online-nl",
});

Portable across 34 Accounting connectors

The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Exact Online NL to another Accounting connector is a one-string change — no rewrite, no new SDK.

// Today — Exact Online NL
await apideck.accounting.invoices.list({ serviceId: "exact-online-nl" });

// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "acumatica" });

This is the compounding advantage of using Apideck over integrating Exact Online NL directly: code against the unified Accounting API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

Exact Online NL via Apideck Accounting

Netherlands-specific variant of Exact Online, optimized for Dutch divisions and BTW (VAT) handling. Use this connector when the user's Exact instance is on the NL data center. Coverage mirrors exact-online (same entities, same methods).

When to use this vs exact-online

User scenario	Use
User's division is in the Netherlands	exact-online-nl
User's division is in Belgium or a different EU market	exact-online
User's division is in the UK	exact-online-uk
Not sure	Ask the user; they know their Exact region

Entity mapping + coverage

Identical to exact-online. See that skill for the full mapping table and coverage highlights.

Key NL-specific behaviors:

• BTW (VAT) handling: Dutch 21%, 9%, 0% rates are surfaced via tax-rates; VAT on invoices is auto-computed based on customer type (binnenland/EU/buiten-EU).
• SEPA integration: bank reconciliation and direct debit integrations more common in NL; extra fields may surface on payments.
• UBL e-invoicing: mandatory for B2G invoicing in NL. Use Proxy for UBL-specific formatting endpoints.

Auth notes

• Type: OAuth 2.0, managed by Apideck Vault
• Data center: start.exactonline.nl. Wrong-DC errors indicate the user picked the wrong variant at OAuth time — connection needs re-authorization against the correct variant.

Example: list invoices updated today

const { data } = await apideck.accounting.invoices.list({
  serviceId: "exact-online-nl",
  filter: { updated_since: new Date(new Date().setHours(0,0,0,0)).toISOString() },
});

Verifying coverage

Not every Accounting operation is supported by every connector. Always verify before assuming a method works:

curl 'https://unify.apideck.com/connector/connectors/exact-online-nl' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}"

See apideck-connector-coverage for patterns around UnsupportedOperationError and connector-specific fallbacks.

Escape hatch: Proxy API

When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Exact Online NL directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Exact Online NL's own API:

curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: exact-online-nl" \
  -H "x-apideck-downstream-url: <target endpoint on Exact Online NL>" \
  -H "x-apideck-downstream-method: GET"

See Exact Online NL's API docs for available endpoints.

Sibling connectors

Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):

access-financials (beta), acumatica (beta), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, and 25 more.

See also

• Accounting OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• Exact Online NL official docs