Skip to content
TaxComposer

Bookkeeping API and MCP

Build a branded W-9 request workflow around your product

Your bookkeeping product can own the customer relationship while keeping the tax information flow clear. Separate the message, the signing experience and the stored recipient data.

By TaxComposer · Updated · 2 min read

Choose who collects the signature

The hosted TaxComposer flow collects the recipient’s information and electronic signature through a private signing page. Where branding is configured, use the supported business branding controls rather than modifying the private link or embedding taxpayer information in it.

If you run your own signing portal, you own that portal’s identity, consent, signature evidence and security design. Do not assume that importing fields into TaxComposer creates a signed W-9 or delegates your portal’s certification requirements.

Source: IRS: Instructions for the Requester of Form W-9 ↗

Send only through an authorized delivery path

A requester must have permission for the recipient contact and chosen channel. The hosted taxcomposer_request_w9 tool uses a stable request_key and explicit contact_permission. Discover its current tool schema and channel availability before creating the request.

Automated SMS availability depends on the configured service and approvals. Sharing a private link from the requester’s own Messages app is a different delivery path. Do not promise that enabling an API integration activates automated SMS.

Source: TaxComposer MCP connections ↗

Import existing data with a stable external ID

POST /v1/w9 supports owner-scoped W-9 data imports. Use external_id to map your vendor record and use the supported revision controls for updates. Keep private fields on the server and follow the current schema for permitted values.

An imported record is data, not a new certification or electronic signature. Preserve the actual signed source separately when you have one, and distinguish it from a recipient’s unverified profile entry.

Source: TaxComposer API Documentation ↗

Apply confirmed details to a return

A completed W-9 can supply recipient details for a 1099 draft. The payment amount and reporting decision still come from reviewed business records. A W-9 is not required merely to open a manual draft, and a signature alone is not a TIN match.

Electronic delivery consent for a future 1099 is a separate choice from signing a W-9. Keep that evidence and the recipient-copy workflow distinct.

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.