Skip to content
TaxComposer

Bookkeeping API and MCP

Keep each business separate in a bookkeeping tax integration

A bookkeeper may manage many companies through one login. The filing workflow still needs an unambiguous payer and a separate record boundary for every business.

By TaxComposer · Updated · 2 min read

Use identifiers rather than names as boundaries

Map your customer tenant, provider company or organization ID and TaxComposer business workspace ID explicitly. Store those references together. A display name is useful to a person, but it is not a dependable authorization or deduplication key.

Switching the selected business in your interface should change the scoped records and payer details together. Do not retain a hidden company ID from a previously opened tab.

Source: TaxComposer API Documentation ↗

Keep provider consent attached to its company

QuickBooks authorization identifies the company context used by API requests. Preserve that company reference and verify that the user selected the intended books before syncing. Access to one customer does not authorize another customer’s company.

Source: Intuit: authentication and authorization ↗

Handle Xero organization selection explicitly

A Xero connection has a tenant context. Keep the authorized organization and selected business aligned, and make reconnection or organization changes visible. The identity of the person signing in is not the same as the identity of the business whose records are being read.

Source: Xero: tenant connections ↗

Scope recipient records and draft review

A vendor’s external ID may only be unique within its source company. Use a company-qualified mapping when connecting it to W-9 records and drafts. Review the payer and recipient together before preparing a form.

TaxComposer’s return workflow carries workspace references and current draft revisions. Use those references when listing or resuming returns instead of building a global search that can accidentally mix unrelated businesses.

Source: TaxComposer API Documentation ↗

Make business changes reviewable

If the user changes a business address, entity detail or payer identity, identify which unfiled drafts need review. Avoid silently rewriting historical or already transmitted documents. Keep completed records and their evidence tied to the version that was actually used.

A personal workspace and a business workspace are different choices. Show the selected context clearly before an integration creates or changes records.

Source: TaxComposer developer workflow guide ↗

Primary sources

Sources checked November 12, 2026. Use the instructions for your reporting year and circumstances.

Your next step

Connect your bookkeeping workflow.

Use the current API contract and discover the tools available to your MCP connection.

API Documentation →Connect with MCP →

TaxComposer is production-ready for IRS IRIS e-filing. Prepare for free and pay $1 per form when you file.