access-financials v1.0.0A

Immutable. This exact content never changes and is served at /api/v1/blob/f3f272bc45988b41.

---
name: access-financials
description: |
  Access Financials integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Access Financials. Routes through Apideck with serviceId "access-financials".
license: Apache-2.0
alwaysApply: false
metadata:
  author: apideck
  version: "1.0.0"
  serviceId: access-financials
  unifiedApis: ["accounting"]
  authType: apiKey
  tier: "1a"
  verified: true
  status: beta
---

# 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](https://developers.apideck.com/connectors/access-financials/docs/consumer+connection)
- **Access Financials docs:** https://www.theaccessgroup.com/en-gb/finance/
- **Homepage:** https://www.theaccessgroup.com/en-gb/finance/products/access-financials/

## 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`](../../skills/apideck-node/), [`apideck-python`](../../skills/apideck-python/), [`apideck-dotnet`](../../skills/apideck-dotnet/), [`apideck-java`](../../skills/apideck-java/), [`apideck-go`](../../skills/apideck-go/), [`apideck-php`](../../skills/apideck-php/), or [`apideck-rest`](../../skills/apideck-rest/)

For the raw OpenAPI spec:

- **Accounting:** [https://specs.apideck.com/accounting.yml](https://specs.apideck.com/accounting.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=accounting)

## Minimal example (TypeScript)

```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.

```typescript
// 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

| Access entity | Apideck Accounting resource |
|---|---|
| Sales Invoice | `invoices` |
| Credit Note | `credit-notes` |
| Customer | `customers` |
| Supplier | `suppliers` |
| Payment | `payments` |
| Nominal Account | `ledger-accounts` |
| Tax | `tax-rates` |
| Tracking / Analysis Code | `tracking-categories` |

### 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

```typescript
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:

```bash
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](https://www.theaccessgroup.com/en-gb/finance/) for available endpoints.

## Sibling connectors

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

[`acumatica`](../acumatica/) *(beta)*, [`banqup`](../banqup/) *(beta)*, [`campfire`](../campfire/) *(beta)*, [`clearbooks-uk`](../clearbooks-uk/) *(beta)*, [`digits`](../digits/) *(beta)*, [`dualentry`](../dualentry/), [`exact-online`](../exact-online/), [`exact-online-nl`](../exact-online-nl/) *(beta)*, and 25 more.

## See also

- [Apideck connection guide for Access Financials](https://developers.apideck.com/connectors/access-financials/docs/consumer+connection)
- [Accounting OpenAPI spec](https://specs.apideck.com/accounting.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=accounting)
- [`apideck-connector-coverage`](../../skills/apideck-connector-coverage/) — programmatic coverage checks
- [`apideck-best-practices`](../../skills/apideck-best-practices/) — architecture, Vault, pagination, error handling
- [`apideck-node`](../../skills/apideck-node/) — TypeScript / Node SDK patterns
- [Access Financials official docs](https://www.theaccessgroup.com/en-gb/finance/)