Access Financials (via Apideck)

Access Access Financials through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Acumatica, banqUP, Campfire 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 Access Financials plumbing.

Beta connector. Access Financials 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: access-financials
• Unified API: Accounting
• Auth type: apiKey
• Status: beta
• Apideck setup guide: Connection guide
• Gotchas: page
• Access Financials docs: https://www.theaccessgroup.com/en-gb/finance/
• Homepage: https://www.theaccessgroup.com/en-gb/finance/products/access-financials/

At a glance

• Implementation difficulty: highly complex — Custom Auth + Manual Per-Consumer Token and Subscription-Key Setup
• Vendor partnership required: no — No partner programme or app review gates Financials API access.
• Apideck-managed credentials: not available — Credentials are issued per Access Financials organisation, so each consumer generates and supplies their own.
• Account type required: An Access Financials organisation with the ERP Application Register enabled.
• Consumer access level: Organisation Administrator — no other role can generate the credentials.
• Sandbox: available — No self-serve signup — request a separate Access Financials test instance from The Access Group.
• Costs: Pay-as-you-go on the Access ERP API platform, with a free tier of 1 million API calls per month.
• Rate limits: No per-minute or per-day rate limit is published for the Financials API.
• Authentication: Bearer access token plus an Ocp-Apim-Subscription-Key header — not OAuth.
• Webhooks: No webhooks — neither native nor virtual; change detection is polling-based.

Important to know:

• Invoices, payments and credit notes post as live transactions immediately, and a posted transaction cannot be updated through the API because it is already accounted for.
• Access Financials offers a Corrections module for amending already-posted records inside the application, enabled per user through a Security Profile. It is not exposed through the API, so it does not change how an integration corrects records.
• Access tokens last at most 365 days and there is no refresh flow: each consumer regenerates the token in the ERP Token Generator and re-enters it before it lapses, or the connection stops returning data.

Facts synced from Apideck's connector metadata API — GET /connector/connectors/access-financials (overview field) is the live, authoritative version.

When to use this skill

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

1. Which Apideck unified API covers Access Financials (Accounting)
2. The correct serviceId to pass on every call (access-financials)
3. Access Financials-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 Access Financials
const { data } = await apideck.accounting.invoices.list({
  serviceId: "access-financials",
});

Portable across 34 Accounting connectors

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

// Today — Access Financials
await apideck.accounting.invoices.list({ serviceId: "access-financials" });

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

This is the compounding advantage of using Apideck over integrating Access Financials 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.

Access Financials via Apideck Accounting

Access Financials (part of The Access Group) is a UK mid-market accounting platform aimed at enterprise finance teams. Apideck coverage targets the core AR/AP surface.

Entity mapping

Coverage highlights

• ✅ Sales invoices
• ✅ Credit notes
• ✅ Customers, suppliers, payments
• ✅ Chart of accounts
• ✅ Tax rates (UK VAT)
• ✅ Tracking categories
• ⚠️ Purchase invoices — may be partial; verify with connector API
• ❌ UK MTD submissions — use Proxy
• ❌ Payroll — Access offers payroll via a separate product line

Auth notes

• Type: API key, managed by Apideck Vault
• Client binding: one Access Financials client per connection.
• Enterprise-typical onboarding: integration may require coordination with the customer's Access admin team.

Example: list recent customers

const { data } = await apideck.accounting.customers.list({
  serviceId: "access-financials",
  filter: { updated_since: "2026-03-01T00:00:00Z" },
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Access Financials directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Access Financials'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: access-financials" \
  -H "x-apideck-downstream-url: <target endpoint on Access Financials>" \
  -H "x-apideck-downstream-method: GET"

See Access Financials's API docs for available endpoints.

Sibling connectors

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

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

See also

• Apideck connection guide for Access Financials
• 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
• Access Financials official docs