agentleFS
apideck-librariesapideck-libraries/api-skills/skills/dualentry/SKILL.md

dualentry

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Dualentry 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 Dualentry. Routes through Apideck with serviceId "dualentry".

  • Reads credentials

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Apideck-managed credentials: not available — Each consumer supplies their own API key.

    line 38
  2. Distinctive:

    Costs: No separate API fee — bundled into the DualEntry subscription, which lists Open API as a plan feature.

    line 42
  3. Distinctive:

    Webhooks: No webhooks — not supported by DualEntry's API.

    line 45
  4. Very specific:

    When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Dualentry directly — Apideck injects auth headers …

    line 164

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dualentry (via Apideck)

Access Dualentry 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 Dualentry plumbing.

Quick facts

At a glance

  • Implementation difficulty: moderate — API Key Authentication — Credential Generated by the Consumer's DualEntry Administrator
  • Vendor partnership required: no — Apideck holds an approved partnership with DualEntry, so no application or certification is required from you.
  • Apideck-managed credentials: not available — Each consumer supplies their own API key; there is no shared Apideck credential.
  • Account type required: Any DualEntry plan. Multi-company tenants supported; scope to a Default Company or the whole tenant.
  • Consumer access level: Organisation administrator — only an admin can generate the API key, via Settings > Organization > Developer access.
  • Sandbox: available (signup) — A separate Development environment at api-dev.dualentry.com with its own organisations and API keys; a production key will not authenticate there.
  • Costs: No separate API fee — bundled into the DualEntry subscription, which lists Open API as a plan feature.
  • Rate limits: 300 requests/min per API key across all endpoints; 60 requests/min per endpoint; invoice create/update capped at 2/min.
  • Authentication: Sent in the X-API-KEY header, not OAuth. The key is a long-lived organisation credential with no expiry.
  • Webhooks: No webhooks — not supported by DualEntry's API.

Important to know:

  • The API key is not self-service for you: the consumer's own DualEntry administrator must generate it, and DualEntry shows it only once at creation — if it is lost, a new key must be issued and the old one revoked.
  • On a multi-company tenant, a read that does not name a company returns records from every company in the tenant. Set a Default Company on the connection, or send an x-apideck-company-id header per request.
  • DualEntry offers no free trial. Every plan includes accountant-led implementation instead, so evaluating the platform means going through their onboarding rather than self-serving.

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

When to use this skill

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

  1. Which Apideck unified API covers Dualentry (Accounting)
  2. The correct serviceId to pass on every call (dualentry)
  3. Dualentry-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:

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 Dualentry
const { data } = await apideck.accounting.invoices.list({
  serviceId: "dualentry",
});

Portable across 34 Accounting connectors

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

// Today — Dualentry
await apideck.accounting.invoices.list({ serviceId: "dualentry" });

// 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 Dualentry 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.

Dualentry via Apideck Accounting

Dualentry is a cloud accounting platform offering modern, double-entry bookkeeping with comprehensive multi-entity support. Broad Apideck coverage.

Entity mapping

Dualentry entityApideck Accounting resource
Invoiceinvoices
Billbills
Bill Paymentbill-payments
Credit Notecredit-notes
Paymentpayments
Journal Entryjournal-entries
Ledger Accountledger-accounts
Customercustomers
Suppliersuppliers
Iteminvoice-items
Purchase Orderpurchase-orders
Expenseexpenses
Subsidiarysubsidiaries
Attachmentsattachments

Coverage highlights

  • ✅ Full CRUD on invoices, bills, payments (incl. bill payments)
  • ✅ Credit notes
  • ✅ Journal entries
  • ✅ Purchase orders
  • ✅ Expenses
  • ✅ Multi-subsidiary support
  • ✅ Attachments on transactions
  • ⚠️ Financial reports (P&L, Balance Sheet) — not in current mapping; use Proxy
  • ❌ Payroll — separate surface

Auth notes

  • Type: API key, managed by Apideck Vault
  • Organization binding: one Dualentry organization per connection.
  • Multi-subsidiary: subsidiaries are exposed as a first-class resource; use subsidiaries to fetch and filter.

Example: create a multi-line bill

const { data } = await apideck.accounting.bills.create({
  serviceId: "dualentry",
  bill: {
    supplier_id: "sup_abc",
    bill_date: "2026-04-18",
    due_date: "2026-05-18",
    line_items: [
      { description: "Service A", quantity: 1, unit_price: 500 },
      { description: "Service B", quantity: 2, unit_price: 250 },
    ],
    currency: "USD",
  },
});

Escape hatch: Proxy API

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

See Dualentry'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), exact-online, exact-online-nl (beta), and 25 more.

See also

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.