Claude DualEntry connectorWhat Claude can do in your DualEntry account.
The Claude DualEntry connector exposes 29 tools. 11 read your ledger, 4 write to it, and 14 have no description in any source. Below: what Claude can look up, what it can post, why the write tools commit at once, and what an Owner controls.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can work in your DualEntry ledger
DualEntry is an accounting platform. With the connector, a controller or an accountant asks for a record, a vendor or a schedule in plain words, and Claude looks it up in the ledger under that person's DualEntry role. It can also post a few kinds of records, which is where care matters most.
Find any record fast. You ask for journal entry JE-123 and its lines; Claude uses get_record_by_number, then get_record_history for the audit trail and get_related_records for payments against an invoice.
Post at month end. save_record creates an accounting record in the ledger, and save_entity creates an entity, such as a vendor or a customer that does not exist yet.
Check a schedule before committing it. preview_contract_schedule and preview_fixed_asset_schedule compute a revenue recognition or depreciation schedule without creating anything; create_contract and create_fixed_asset then commit it.
What Claude does not do: DualEntry says the write tools commit as soon as Claude calls them, with no draft stage and no confirmation prompt on DualEntry's side. Fourteen tools on the directory sheet are described nowhere, and this page does not guess what they do. Nothing runs on its own either: a nightly sync between systems is the job of an automation tool, a different trade introduced on the Integrations hub.
Five words before you connect
The Claude vocabulary used on this page, defined once.
- Connector
- A link you set up once between Claude and an account you already hold, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude decides which to call as it answers, and the directory lists each one by name.
- Authorization
- The sign-in screen of the service, where you hand Claude the access it will use. Given once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before changing something in an account, shown in the conversation at the right moment.
- MCP
- The common standard connectors are built on, which is what lets an assistant like Claude talk to an outside service like DualEntry.
Connect DualEntry to Claude in three steps
- 01
Find DualEntry in Claude
Open Claude's settings, go to Customize, then Connectors, and look for DualEntry. On a Team or Enterprise workspace, an Owner or Primary Owner enables it first; each member then signs in for themselves.
- 02
Start the connection
Click Connect on DualEntry's row and sign in with your DualEntry credentials in the window DualEntry opens. If the link stops working later, Disconnect and connect again.
- 03
Read the access screen
Check DualEntry's authorization screen before you approve it. That screen, not Claude, sets what the access covers. You can withdraw it later from the DualEntry side.
The 29 tools, by what they do
DualEntry gives Claude 29 tools: 11 that read your account, 4 that change something in it, and 14 no official source describes.
DualEntry's catalogue describes 15 tools; the directory sheet now lists 29. Here is each one, in three groups. Names stay as Claude shows them.
- 11 read
- 4 write
- 14 not documented
What Claude reads (11)
11 toolsEleven tools that look up, list or compute without changing your books.
get_contract_detail
Opens a revenue recognition contract in full, with its schedule and the invoices tied to it, so Claude can walk you through where revenue lands month by month.
get_record_by_number
Finds a record from its number, such as JE-123, BI-456 or IN-789, which is how people usually refer to entries in emails and tickets.
get_record_detail
Returns the full content of a record from its transaction ID, so Claude can go from a record it has found to its full content.
get_record_history
Shows the audit trail of a record, meaning who changed what along the way. Claude can summarise that trail in a few sentences for you.
get_related_records
Lists records linked to a given one, for instance the payments recorded against an invoice, which lets Claude answer whether something has been settled.
list_bank_match_suggestions
Retrieves the suggested matches for bank statement lines, so Claude can show which transactions DualEntry thinks belong together during reconciliation.
list_companies
Lists the companies of the organization that you are allowed to access, a useful first step when one DualEntry login spans several legal entities.
preview_contract_schedule
Computes the recognition schedule a contract would produce, without creating it. It takes the same input as the creation tool, so you see the outcome first.
preview_fixed_asset_schedule
Works out the depreciation schedule an asset would get, again without creating anything. It works from a fixed asset payload, so you see the outcome before anything is committed.
search_entities
Searches vendors, customers, accounts, companies, items, classifications, terms and ownership records by name, with fuzzy matching. DualEntry's directory description puts that matching forward for customers, vendors and accounts in particular.
search_records
Runs a filtered search over accounting records by type, vendor or customer, date range and amount range. It narrows a long ledger to the entries you are after.
What Claude writes (4)
4 toolsFour tools that create something in DualEntry. No source describes Claude's confirmation for them, so the general rule below applies.
create_contract
Approval: see the ruleCreates a revenue recognition contract, which then drives recognition for its whole term. Running the preview first is the step DualEntry recommends.
create_fixed_asset
Approval: see the ruleRegisters a fixed asset with its full depreciation schedule. The preview tool computes that schedule first, without creating anything.
save_entity
Approval: see the ruleAdds a new entity, such as a vendor or a customer, to DualEntry, within the entity types your role is allowed to create.
save_record
Approval: see the ruleCreates an accounting record in your DualEntry ledger, within the record types your role allows. DualEntry says it commits as soon as Claude calls it, with no draft stage.
Undocumented (14)
14 toolsThese names appeared on the directory sheet without any description. DualEntry's tool catalogue does not cover them, so this page does not say what they do.
create_bank_match
This name is on the directory sheet and in no other source. DualEntry's catalogue of 15 tools does not include it, and no Claude page covers it, so nothing official says what it does or what it touches.
delete_fixed_asset
Listed on the sheet with no official sentence attached. Since DualEntry has not described it in its guides, this page does not infer anything from how the name reads.
get_bank_match_status_counts
One of the fourteen names added to the sheet that no source explains. DualEntry's tool reference does not mention it, and Anthropic has no page on this connector at all.
get_bank_transaction
No official text describes this tool. It is absent from DualEntry's list of 15 and from Anthropic's pages, so its scope remains unknown here, and this card will not fill the gap with a guess.
get_depreciation_book
The directory publishes this name and stops there. With no publisher description and no Claude documentation, the page leaves it unexplained rather than reading meaning into a few words.
get_fixed_asset_schedule
Undescribed in every source read on 1 October 2026: the directory sheet names it, DualEntry's documentation does not, and no Claude article exists. Nothing more can be said about it honestly.
list_bank_transactions
Another name that appeared on the sheet without documentation. DualEntry's reference of 15 tools leaves it out, as do Anthropic's pages, so nothing official describes it.
list_depreciation_books
No source says what this tool does or whether it changes anything. It sits on the directory sheet only, outside DualEntry's published catalogue and outside any example the publisher gives.
patch_fixed_asset
The publisher has not documented this name anywhere we could read. Guessing its effect from the wording would be exactly that, a guess, so this card sticks to what is known: a name on a list.
trigger_bank_match
Absent from DualEntry's catalogue of 15 tools and from every Anthropic page. The sheet carries the name; no published text carries an explanation of what it is for.
unmatch_bank_match
Here too, only the directory shows the name. Without a description from DualEntry or from Anthropic, this page cannot say whether it reads the ledger or writes to it.
update_entity
No published text covers this tool, neither DualEntry's reference nor its connector guide for Claude. Its behaviour remains undocumented, and the page does not borrow a description from any other tool to fill in.
update_fixed_asset
This one was added to the directory listing after DualEntry's reference of 15 tools and has had no description since, in any source checked for this page, from the directory sheet to DualEntry's own guides.
update_record
Last of the fourteen undescribed names. DualEntry's pages stop at 15 documented tools, and this one is not among them; the directory adds nothing beyond the name itself.
What Claude checks with you first
By default, Claude stops and asks before each action it carries out on an account for someone, with the prompt shown in the conversation.
No source describes Claude's own confirmation for any DualEntry tool, so the default rule is the reference. DualEntry adds a warning on its side: save_record, save_entity, create_contract and create_fixed_asset commit as soon as they run, with no draft stage. On Team and Enterprise, owners decide whether members may let actions through without a prompt, and can close writing for the whole organization. Claude works under your DualEntry role: what you cannot reach in DualEntry, Claude cannot reach either.
Which plans include it
Not one of the 819 sheets in the official directory states plan availability, and Anthropic publishes no per-connector list.
Anthropic's general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile; on Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can connect. DualEntry's own documentation states something narrower, which the limits section below sets side by side with that rule. For the live state on your account, check DualEntry's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls DualEntry's tools while it answers, so nothing posts on its own when a bank feed lands or a period closes.
Everything here comes from DualEntry's documentation and the directory sheet; no Claude help center or developer page covers this connector. The tool list is an observed floor, not a promise, because an administrator can open actions that no public sheet shows. The partner badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor guarantees their behaviour.
Which Claude plans can use the DualEntry connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise an Owner or Primary Owner enables each one first.
- DualEntry documentation ↗October 2026The publisher says connectors require a Pro, Max, Team or Enterprise plan and that Free plans cannot add them.
What this page followsNeither side is outdated. Anthropic's rule covers every connector; DualEntry's sentence is the publisher speaking, not Anthropic, and it excludes the free plan. Neither settles it for your account: check DualEntry's sheet in the directory on your own account.
Need help connecting DualEntry to Claude?
A person reads every message.