- Brand
- Entendre
- Category
- Finance
- Primary Subcategory
- Accounting & Bookkeeping
Integration details
Description
Connect ChatGPT to Entendre’s Unified API and work across your accounting data from a single conversation—browse accounts, query transactions, review balances, classify activity, create journal entries, generate reports, and keep your general ledger in sync without exporting data or switching tools.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Accounting & Bookkeeping
- Secondary Subcategories
- None listed
- Brand
- Entendre
- Access
- Account required
- First tracked
- 2026-11-16
- Tool count
- 116
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Not discoverable in ChatGPT yet
ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen Entendre suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.
What discovery looks like

Get alerts for Entendre
Get updates when Entendre’s Discoverability Score or category rank changes.
Competing in ChatGPT Accounting & Bookkeeping
View Category116 tools agents can invoke
Apply a draft cash-application Applies an existing draft cash application in one of two modes. With `compiled_rules` it posts the journal entry, claims the deposit and, depending on settings, writes to Stripe to mark the invoice paid. With `journal_entry_id` it links a journal entry you already posted, after checking that it is posted, balanced, touches the bank account, is not linked elsewhere and has the customer tag. The compiled rules represent verified active policy; `[]` represents a verified policy without overrides. The applied match and its Stripe state.
Cancel an agent run Cancels an agent run by sending a stop request. It needs write:agents and a user-owned key or a user session; an ownerless key gets 403. `meta.cancellation_status` says what happened: `accepted` (stop signal confirmed), `pending` (not confirmed), `no_active_turn` or `no_session` (nothing was running), `owner_mismatch` (ownership not verified). The request's acceptance is not completion: check the run later with `list_agent_runs`. Work already done is not undone. The cancellation status.
Cancel request Cancels an integration request and invalidates its client links. Needs firm write access. Sources the client already connected through the request stay connected. Cancellation outcome.
Classify transactions and post eligible entries asynchronously Classifies the selected transactions with the organization's rules and posts `POSTED` journal entries at once for confident matches that have a category and a payment account; the rest stay `pending_review` or `unclassified`. Select by `sequence_numbers`, `transaction_ids`, or a date range (at most 100 transactions). Auto-posting cannot be turned off, and the entries are not synced to the GL. It returns a `cls_` job: read the result with `get_classification` in a later call. With `search_term`, send `unaccounted_only: false`. A classification job id; confident matches post.
Close an accounting period Closes an accounting period: it records closing balances, locks posted journal entries and carries the balances into the next open period. It fails when an earlier period is still open or no next period exists. Undoing it needs an admin reopen, which can change later balances. The closed period.
Complete an applied cash-application Completes an applied cash application (`applied`, `stripe_status: pending`) by marking its Stripe invoices paid; the row becomes `completed`. It is safe to repeat on a completed row. With `require_gl_sync: true`, the call returns 409 unless the linked journal entry is posted and synced to the GL. Without it, only organizations on Campfire get that check, so Stripe can show the invoice paid while the GL has no entry. It returns 400 when the row is not applied, 409 on a lock, an unpaid invoice or a disconnected Stripe connection, and 502 on a Stripe error. The completed match, or the lock, state or provider error.
Create vendor accruals Creates vendor accruals in one batch. Each row succeeds or fails on its own: the response lists `created` and `failed` rows, and each failure says why (for example a duplicate for that vendor and period, an unmapped vendor account, or a closed period). Amounts must be above zero. There is no account field: each accrual books to the vendor's mapped expense account (`default_expense_account_id` in `vault.list_vault_vendors`); a QuickBooks vendor without one uses the account of its recent bills, else the row fails. An accrual here does not show whether the vendor's bill already exists in the GL. `created` and `failed` rows.
Create and apply a cash-application in one call Creates and applies a cash application in one call: it posts the journal entry and claims the deposit; `unapply_cash_application` reverses it only before the Stripe sync. Each allocation must equal the invoice's `amount_due` (no partial payments), and all invoices must belong to one customer. The deposit rules and 400 `reason` values are the same as for `preview_cash_application`. The compiled rules represent the organization's verified active policy; `[]` represents a verified policy without overrides. Automatic application requires verified rules. The applied match with its journal entry.
Create a manual asset Creates a manual asset lot for an off-chain or manually tracked position, and adjusts the matching ledger account balance. Existing lots are available through `list_assets`. To correct an existing manual lot, use `update_asset`. The created lot and its balance adjustment.
Create client Creates a draft client and its organization; omit `name` and `web_address` to generate both. Needs firm write access, a firm administrator; client-restricted keys cannot call it. Duplicate-name comparison ignores surrounding whitespace, case and repeated spaces; similar names may identify an existing client. A failed roster read does not prove the client is absent. Creation does not activate the client. An `idempotency_key` is required for this request. Reuse it only when retrying the same request. The new draft client and its organization.
Create a journal entry Creates a journal entry in one of two ways. From a transaction: send `transaction_id`, a postable `ledger_account_id` and `transaction_type`; the lines come from the transaction's gross fiat value, direction and source, and a non-stablecoin crypto outflow books 4 lines with cost basis and realized gain or loss (cost basis must be computed first). Manual: send balanced `lines`, a `status` of `draft` or `posted`, and at most one `transaction_id`. A transaction entry is `DRAFT` unless you send `auto_post: true`. If the target account has no GL mapping (`list_account_mappings`), the entry cannot reach the GL. The new entry with its status.
Create a ledger account Creates a ledger account with a `name` and a `type` (Asset, Liability, Equity, Income or Expense). `sequence_number` defaults to the next number in that type's block, and `parent_account_id` puts the account under a parent. Ledger accounts belong to the organization, not to a legal entity: leave `legal_entity_id` out and do not ask the user for an entity. The new account.
Create a legal entity Creates a legal entity (a registered business) under the organization and returns its `le_` id. The new entity can own transactions, ledger accounts and GL mappings at once. An entity with the same name can already exist. The new entity with its id.
Create an integration request for a client and send its email immediately. Supports wallets, exchanges, banks, QuickBooks, Xero, NetSuite, Ramp, Stripe AR and Gmail. Document requests are unavailable through this connector. Requires firm write access and an idempotency_key. The email cannot be undone. email_sent reports provider acceptance, not delivery. Returns the saved request and email send result. Do not retry an uncertain write automatically.
Trigger asset revaluation Starts the requested revaluation and returns acceptance, not completion. With period_id, the period must be open, earlier periods closed and the next period present and open; existing revaluation or reversal entries conflict. An already running period job is returned. Poll list_revaluations for this variant. With legal_entity_id instead, the existing entity-wide workflow returns a job_ configuration receipt, which is not in that list. This connector has no job-configuration polling tool. A repeat write is not a status check. The in-flight guard applies to the selected scope. The accepted period job or entity-wide job configuration receipt (202), or an existing period job.
Create a source Creates a wallet or a Niural supplier source (201). For `exchange`, `bank_account` or `card`, it selects the source of an active connection with `connection_id` (200, nothing created) or starts a statement import with `document_id` (202, queued). Creating a wallet does not import its transactions. A 409 on a wallet means the address already exists on that chain: the existing source is available through `list_sources`. 201 created, 200 existing connected source, or 202 queued import.
Create a tag Creates a tag from a `key` in the closed set and a `value` label. The `key` and `value` pair is unique in the organization. Tags are labels for filters and reports; they change no balance. The new tag.
Create transaction Creates one manual fiat transaction on an existing bank, card or other fiat source; it records an event and moves no money. Crypto sources are rejected. `currency` must be the legal entity's reporting currency, amounts are unsigned (`direction` sets the sign), and a `timestamp` in a closed period returns 422. It does not classify the transaction. The new transaction; its OT number can arrive later.
Delete an agent Deletes an agent: it permanently removes the agent and all its run history, and stops its schedule at once. This cannot be undone. Pause the agent in Entendre to retain its history. Success with no body.
Delete an asset Deletes an asset lot as a soft delete and reverses its balance adjustment in the same operation. The lot then leaves lists and future cost-basis calculations; only an operator can restore it. Lot details are available through `list_assets`. Success with no body; the lot is soft-deleted and its balance adjustment reversed.
Delete a journal entry Soft-deletes one `DRAFT`, `ERROR` or `UNPOSTED` journal entry that is not synced to a GL; it leaves every list and only an operator can restore it. Posted or synced entries cannot be deleted directly. Unposting is a separate operation and is blocked by a closed period. Success with no body, or an error when the status or a GL sync blocks the delete.
Delete a ledger account Soft-deletes a ledger account and its direct child accounts. It returns 409 when the account or any account below it is used by a journal entry line, asset, template, wallet or exchange source; balances are not checked. Accounts below the direct children stay active, so delete a deeper tree from the bottom up. Success with no body, or 409 when a reference blocks the delete.
Delete a legal entity Soft-deletes a legal entity with no transactions, journal entries or linked wallets; any of those returns a conflict. Provider connections stay connected. To stop using an entity that has records, change its status with `update_legal_entity` instead. Success with no body, or a conflict when records still use the entity.
Soft-delete a memory document Deletes one memory document (`path` and `reason` required) or one operational rule (`rule_id` required, from `list_memory`). A document is soft-deleted to the trash with the reason, and `purge: true` deletes it permanently; this tool set has no restore. A rule delete stops the rule for later runs and does not undo past classifications or journal entries; an unknown id returns 404. Deletion is a separate requested action. The document or rule deletion outcome.
Delete one source Deletes one source through its type's own checks: a wallet or exchange used by journal entries, a bank account with accounted transactions, or a Niural source with non-draft invoices returns 409. A Rain or Ramp card or a Ramp bank account deletes with its transactions; one whose transactions have journal entries returns 409. Staking sources cannot be deleted (422); the user disconnects the provider instead. `confirm_source_type` must match the source's real type, and the call needs read access to sources as well as write access. Deleting a Plaid account also soft-deletes its bank transactions, and deleting the last one removes the Plaid item. Success, or 409 or 422 when a guard blocks the delete.
Delete a tag Soft-deletes a tag that is not in use, so it no longer appears in lists. A tag still assigned to journal-entry lines or templates returns 409. Deletion does not unassign references. Success with no body, or 409 when the tag is in use.
Delete a transaction Soft-deletes one transaction. A transaction booked by a posted journal entry returns a conflict; unposting is a separate operation that requires an explicit user request. A draft entry can stay in place after its transaction is deleted. Success with no body, or a conflict when a posted entry books the transaction.
Delete a document Soft-deletes one Vault document, so it no longer appears in lists; bill, receipt and statement rows that use it stay. Deletion is a separate requested action. A second delete of the same id returns 404. Success with no body.
Disconnect connection Disconnects one connection through its provider's cleanup. Plaid cleanup removes linked bank accounts and transactions while retaining journals, and accounting records can block it; other providers keep different resources. The result contains `cleanup`, `retained_resources` and `revocation_error`. Incomplete cleanup is not a complete disconnect. Cleanup results, retained resources and any revocation error.
Pre-close audit for an accounting period Returns the close blockers for one period: structural conditions, unbooked transactions and draft journal entries. It does not close the period. `safe_to_close` means only these checks passed; unposted, in-progress or failed entries, sync failures, clearing, revaluation and asset checks are not included. Preview arrays hold at most 25 rows; counts cover all matches. Blockers, recommendation, counts and short previews.
Get asset tax lots Returns acquisition lots as of a required `as_of` date: quantity, remaining quantity, cost basis, method and linked dispositions, oldest acquisition first. Disposals after `as_of` are added back. `asset_types` filters assets on the server. A refused or timed-out scan is incomplete. limit=25 — page with next_cursor Lot rows oldest first, and `context` with `as_of` and the method.
Balance sheet Returns Entendre book balances for Asset, Liability and Equity accounts in the selected periods. `data_quality` includes `negative_asset_periods`, `unbalanced_periods` and `warnings` that qualify the returned balances. Opening balances carry forward only from closed periods, so where earlier periods are open a column is period movement, not a cumulative position. Cash membership is not established by matching account names; cash and sign checks include both asset and liability types. For totals only, send `include_zero_rows: false`. No period named → send start_date and end_date for the last 3 UTC calendar months The 3 months include the current one: 1st of the UTC month 2 months back → end of this UTC month Account rows with period balances, `ledger_accounts` for the hierarchy, and `data_quality`.
Get classification status Returns a classification job: status, totals and one paginated `items` list in which each row's `status` says whether it was classified, pending review or unclassified. `posting_status` and `journal_entry_id` are set only on rows that an auto-post touched. `succeeded` means every row classified and posted; otherwise the job is `partially_succeeded` (a skipped post alone does not count). Status, `items` and totals.
Closing positions Returns the accounting position of each token from the cost-basis lot subledger: quantity, cost basis, market value and unrealized gain, fiat included. It is not current live crypto exposure; for live holdings use `get_treasury_balances`. Money fields are 2-decimal amounts in one entity's reporting currency, which the response does not name, `base_currency` is available through `list_legal_entities`. `data_quality` is at the top level (not inside `data`) and covers every matched row; `has_negative_positions` identifies a limitation on portfolio totals. Prices use floating-point arithmetic and are not exact many-decimal values. Position rows, `total_count` across pages, and top-level `data_quality`.
Get cost basis settings Reads the connected organization cost-basis method and lot-tracking scope. Check configured before treating default values as a saved setting. For firm connections, select the client organization first. The methodology, accounting_based and configured flag inside data.
Get current organization Returns the organization's name, `org_` id, web address, timezone and time format. There is no organization currency: each legal entity has its own `base_currency` (see `list_legal_entities`), so organization amounts have no single shared currency. No cost-basis policy is exposed here. Organization identity and display settings.
Financial insights Returns the requested `metrics` for a window: `revenue`, `profit`, `expenses`, `spending`, `burn_rate`, `runway`, `cash_flow`, `treasury_flow`, each with `value`, `formula`, `unit` and `details`. `basis` is required: `transactions` is cash-basis and needs no posted entries; `ledger` is the posted-entry P&L by whole month. `runway` counts fiat and stablecoins only and is `null` with `reason: cash_flow_positive` when there is no burn. With `basis: transactions`, `cash_flow` covers only P&L-classified transactions, and `details.data_quality` lists what was excluded. For money in and money out of the bank accounts, wallets and exchange accounts, use `treasury_flow` with `basis: transactions`. State the basis in the answer. No dates named → send the trailing year ending today No basis named → basis=transactions One result per requested metric with its own details and quality notes; a missing value is not zero.
Get firm settings Returns the firm name and its Entendre subdomain slug. Needs read:firms. The slug is not the company's website. The firm name and subdomain slug.
Income statement Returns Entendre income and expense balances by ledger account for the selected periods (accrual basis). This report provides accrual-basis revenue, expenses and net income, including when some transactions remain unposted. A populated report is not proof that the books are complete or reconciled, and an empty one is not proof of zero activity. Parent rows already include their children; adding every row double-counts balances. For totals only, send `include_zero_rows: false`. No period named → send start_date and end_date for the last 3 UTC calendar months The 3 months include the current one: 1st of the UTC month 2 months back → end of this UTC month Income and expense account balances, `ledger_accounts` for the hierarchy, and `data_quality`.
Get realized gains report Returns sold asset lots with their disposals for the chosen `accounting_period_ids`; with no period it covers all history. With `summary: true, limit: 1`, `summary.total_gain` equals the sum of every page. When `summary.by_currency` has more than one entry there are separate currency totals and no flat totals. Gains use a per-unit estimate (`sale_price × quantity_sold − cost_basis × quantity_sold`), not a FIFO, LIFO, HIFO or average-cost calculation. Disposed lot rows; `summary: true` adds per-currency totals.
Schedule of dispositions Returns asset lots that have disposals, with each disposal's date, proceeds, cost basis and realized gain or loss. Each lot lists its full disposal history. For totals send `summary: true`; it gives the same per-currency summary as `get_realized_gains_report` over the same filters. Disposed lot rows; `summary: true` adds the per-currency summary.
Consolidated live treasury balances Returns the organization's live treasury position: one row per internal wallet, exchange account or bank account, with its tokens nested and `total_fiat` per row. It is the answer for "how much cash do we have now"; book balances come from `get_balance_sheet_report`. Wallets and banks come from the last stored refresh (`as_of` per row); exchanges from the daily snapshot. `as_of` (YYYY-MM-DD) gives a past position: banks are left out and a missing exchange snapshot is a gap (`reason: no_snapshot`). For a named month, use its last day as `as_of`. Every connected source has a row, `"0.00"` when empty. A failed source has `total_fiat: null`; check `context.total_fiat_status` before calling the total complete. For current crypto exposure, add up the crypto and exchange token rows by asset and keep bank cash separate. One wallet can hold two rows of one symbol (two contracts), so add every row, not only the first match. Source rows sorted by `total_fiat`, and `context` with warnings and `total_fiat`.
Trial balance Returns debits, credits and the stored opening, closing and current balance for every account type over the periods in `start_date`–`end_date` (both required; a window with no periods returns 400). For one closed period, `closing_balance` is its opening balance plus its activity; it is 0 while the period is open. For more than one period, each balance field is the sum across the periods, not a position as of `end_date`. `data_quality` warnings qualify the balances; returned balances are not proof of reconciliation. An empty result means no balances in this window, not proof that the ledger recorded no activity. An end-only request uses the default window ending on that date. `as_of: true` selects explicit inception-to-date mode. Cash membership is not established by matching account names; cash and sign checks include both asset and liability types. The `ledger_accounts` array contains filtered accounts, including zero ancestors of retained accounts. `meta.account_count` is the filtered count and `meta.total_account_count` is the whole chart count. Their difference is accounts entirely zero for this period, not missing accounts. `meta`, with `zero_rows_omitted`, `omitted_account_fields` and `view`, comes back when you send `include_zero_rows: false` or `verbosity: compact`; it is absent only on the full faithful payload, where `ledger_accounts` is the whole chart. No dates named → send start_date and end_date for the last 3 UTC calendar months The 3 months include the current one: 1st of the UTC month 2 months back → end of this UTC month Account rows, `ledger_accounts`, `data_quality`, and `meta` with the returned and total account counts.
Import accounting data Imports legal entities, the chart of accounts and customer and supplier tags from a connected accounting system; it imports no journals or transactions. Progress is available through `list_imports`. Multiple provider realms require an explicit selection. Bank, card and exchange connection ids return 404. The accepted import.
Import a source's transactions Imports transactions for one source in the background. A 202 `queued` response has no status check and does not establish completion. A 200 `skipped` response means nothing was queued and includes the `reason`. Omit `start_date` for a refresh from the last cursor; send it for a dated backfill (wallets only, exchanges return 422). Bank accounts import through Plaid on their own (422). 202 queued, or 200 skipped with a reason.
Invite team member Invites a person to the firm and sends the invitation email; the send cannot be undone and the link expires after 14 days. Needs firm write access, a firm administrator. `email_sent` records whether the email provider accepted the send; a saved invitation does not prove the email went out. An `idempotency_key` is required for this request. Reuse it only when retrying the same request. The invitation and its delivery result.
List account mappings Lists which Entendre ledger account maps to which GL account on one accounting connection, 25 a page at most. A row count is not a count of mapped accounts: for coverage, read every page and count distinct non-empty `internal_ledger_account_id` values against the same chart. Bank, card and exchange connection ids return 404. Mapping rows and a count.
List accounting periods Lists accounting periods, newest first, with status (`open`, `soft_closed`, `closed`) and close details. Periods are created as transactions are imported. Some organizations have several periods for one month (one per legal entity, plus archived ones): legal entity, start date and last update distinguish them. Name each entity with the period's `legal_entity_name`; do not match entities by list order. Period rows, newest first.
List vendor accruals Lists the organization's vendor accruals whose journal entry still exists. Filter by `vendor_id`, `period` (YYYY-MM), `status` or `journal_sequence_number`. `status` defaults to `posted`; `all` returns every status but still leaves out accruals whose journal entry was deleted. Each call marks those orphaned accruals as reversed. Marks posted accruals whose journal entry was deleted as reversed. Every match in one response unless you ask for pages.
List agent runs Lists one agent's runs, newest first, with results and errors. `run_ids` and `status` filter before paging; keep the same filters across pages. The cursor anchors to the last run, so new runs do not shift later pages. Run rows with results and errors.
Entendre ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Entendre's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Entendre alternatives on ChatGPT?
As of 2026-11-16, Entendre competes with Accountable, Agenix Invoice, AgentCollect, Aikount, Akaunting, ALL-FOOD Import Calculator, AltiBooks, AuntBird Practice Management and 97 more in ChatGPT Accounting & Bookkeeping, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.


