Skip to content
TaxComposer

Bookkeeping API and MCP

Import bookkeeping data from CSV, Excel or your own API

A file import is useful when a native connection is unavailable or the customer wants to inspect the source first. The same record discipline applies whether the source is a spreadsheet or structured JSON.

By TaxComposer · Updated · 2 min read

Preview the source before saving

TaxComposer separates file preview from saving an accounting source. Use the preview operation to inspect columns and sheet choices. Select the intended sheet and map its columns explicitly rather than guessing a tax field from a similar header.

The current contract limits uploaded CSV/XLSX files to 8 MiB. Structured imports have their own bounded vendor and transaction counts. Read the current schema for limits and accepted fields before batching data.

Source: TaxComposer API Documentation ↗

Preserve IDs and decimal values

Keep vendor and transaction IDs stable across imports. Use signed decimal amounts so refunds do not become additional payments. Preserve the currency, paid date, payment method and category needed for review.

An invoice date and an actual payment date are different data. A column labeled “amount” also needs context: balance due, original invoice total and paid amount cannot safely be substituted for one another.

Source: TaxComposer API Documentation ↗

Make completeness visible

Set the reporting year, accounting company, source reference and completeness flag deliberately. A January-to-June extract is not a complete annual payment history. Keep the source filename or reference available to reviewers without exposing private file contents in logs.

If two uploads overlap, reconcile them using stable source transaction IDs. Do not add both totals and hope that a later filing check will discover the duplication.

Source: TaxComposer API Documentation ↗

Review before draft preparation

Use the saved-source review step to confirm the payer, recipient mapping and proposed returns. A source can contain payments to employees, corporations, service providers or other recipients that require different analysis. Import success is not a tax-classification result.

Keep the review bound to the source version. If new transactions or recipient changes arrive, review the changed source before preparing another set of drafts.

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.