Dualentry
Skill apideck-libraries/api-skills/providers/cursor/plugin/skills/dualentry
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".From its SKILL.md
npx -y skills add apideck-libraries/api-skills --skill dualentryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
7.0 KB, ~1.7k tokens by cl100k_base, as published. Nobody here has run it
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
- Apideck setup guide: Connection guide
- Gotchas: page
- 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:
- Which Apideck unified API covers Dualentry (Accounting)
- The correct
serviceIdto pass on every call (dualentry) - 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, orapideck-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 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 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 |
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
subsidiariesto 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
- Apideck connection guide for Dualentry
- Accounting OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- Dualentry official docs
What ships with it: 1 file
490 B alongside SKILL.md
- metadata.json490 B
Gives 0 of the 12 instructions most finance skills give in ~1.7k tokens
Counted across 469 of the 469 authors here whose files we hold, read 2026-08-07
- Extract date vendor amount and descriptionin 15 of 469, across 3 files
- Scan folder for invoice filesin 14 of 469, across 2 files
- Rename files to standard formatin 14 of 469, across 2 files
- Show organization plan before movingin 14 of 469, across 2 files
- Generate summary CSVin 14 of 469, across 2 files
- Organize files by categoryin 13 of 469, across 1 file
- Preserve original filesin 13 of 469, across 1 file
- Flag files missing critical infoin 13 of 469, across 1 file
- Produce the requested output filein 9 of 469, across 4 files
- Build best, base, and worst case scenariosin 9 of 469, across 5 files
- Implement backoff if rate limit errors occurin 8 of 469, across 3 files
- Determine the weighted average cost of capitalin 8 of 469, across 4 files
Said here and by no other author read
- route requests through the Accounting unified API
- Pass the dualentry serviceId on every API call
- Refer to the language SDK for full method surface details
- Use the Proxy API for uncovered endpoints
- Consult the official Dualentry docs for proxy endpoint targets
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.