dualentry · diff
v1.0.0 to v1.0.0
52 added, 13 removed. Audit A to A.
---
name: dualentry
description: |
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".
license: Apache-2.0
alwaysApply: false
metadata:
author: apideck
version: "1.0.0"
serviceId: dualentry
unifiedApis: ["accounting"]
authType: apiKey
tier: "1a"
verified: true
---
# 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
- **Apideck serviceId:** `dualentry`
- **Unified API:** Accounting
- **Auth type:** apiKey
- **Dualentry docs:** https://dualentry.com
- **Homepage:** https://www.dualentry.com/
## 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`](../../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 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.
```typescript
// 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.
- ## Authentication
+ ## Dualentry via Apideck Accounting
- - **Type:** API Key
- - **Managed by:** Apideck Vault — the user pastes their Dualentry API key into the Vault modal; Apideck stores it encrypted and injects it on every request.
- - **Rotation:** if the user rotates their key, they re-enter it in Vault. No code changes needed.
+ Dualentry is a cloud accounting platform offering modern, double-entry bookkeeping with comprehensive multi-entity support. Broad Apideck coverage.
- See [`apideck-best-practices`](../../skills/apideck-best-practices/) for Vault setup, connection lifecycle, and handling re-auth flows.
+ ### Entity mapping
- ## Verifying coverage
+ | Dualentry entity | Apideck Accounting resource |
+ |---|---|
+ | Invoice | `invoices` |
+ | Bill | `bills` |
+ | Bill Payment | `bill-payments` |
+ | Credit Note | `credit-notes` |
+ | Payment | `payments` |
+ | Journal Entry | `journal-entries` |
+ | Ledger Account | `ledger-accounts` |
+ | Customer | `customers` |
+ | Supplier | `suppliers` |
+ | Item | `invoice-items` |
+ | Purchase Order | `purchase-orders` |
+ | Expense | `expenses` |
+ | Subsidiary | `subsidiaries` |
+ | Attachments | `attachments` |
- Not every Accounting operation is supported by every connector. Always verify before assuming a method works:
+ ### Coverage highlights
- ```bash
- curl 'https://unify.apideck.com/connector/connectors/dualentry' \
- -H "Authorization: Bearer ${APIDECK_API_KEY}" \
- -H "x-apideck-app-id: ${APIDECK_APP_ID}"
- ```
+ - ✅ 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
- See [`apideck-connector-coverage`](../../skills/apideck-connector-coverage/) for patterns around `UnsupportedOperationError` and connector-specific fallbacks.
+ ### 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
+
+ ```typescript
+ 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:
```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: dualentry" \
-H "x-apideck-downstream-url: <target endpoint on Dualentry>" \
-H "x-apideck-downstream-method: GET"
```
See [Dualentry's API docs](https://dualentry.com) for available endpoints.
## Sibling connectors
Other **Accounting** connectors that share this unified API surface (same method signatures, just change `serviceId`):
[`access-financials`](../access-financials/) *(beta)*, [`acumatica`](../acumatica/) *(beta)*, [`banqup`](../banqup/) *(beta)*, [`campfire`](../campfire/) *(beta)*, [`clearbooks-uk`](../clearbooks-uk/) *(beta)*, [`digits`](../digits/) *(beta)*, [`exact-online`](../exact-online/), [`exact-online-nl`](../exact-online-nl/) *(beta)*, and 25 more.
## See also
- [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
- [Dualentry official docs](https://dualentry.com)