Choose your data path
Send transactions and let Taxbit compute, or send form data you compute yourself.
Reporting data reaches Taxbit one of two ways. You send transactions, and Taxbit computes cost basis, gains, and form amounts from them. Or you send form data, sent as form items: the amounts your platform has already computed, which Taxbit places on forms. The choice is made once, in your kickoff, and it shapes everything you build afterwards.
Send transactions
You send each transaction as it happens, in Taxbit's transaction data model: your identifier, the account, a type such as trade, deposit, withdraw, or income, the time it occurred, and the amounts sent and received with their prices. Posting a transaction again with the same id updates it, so you can correct history by resending.
From transactions Taxbit works out cost basis at the lot level, realized and unrealized gains, income, and the amounts for each form. It is the only path that supports the Cost Basis features, such as inventory, gains, and tax center experiences.
For historical loads, the Ingest page in the Taxbit Dashboard takes CSV and JSONL files and offers each CSV template; your implementation manager can walk you through it.
Send form items
You compute the form amounts yourself and send them per account and tax year, up to 100 form items per request. Taxbit validates them, places them on the right forms, and files and delivers those forms. Nothing is computed from activity, so there is no inventory, no gains, and no in-app tax center data.
This path suits platforms with an existing tax engine, or with data that does not fit a transaction model, that need Taxbit for filing and delivery only.
How to decide
| If you need | Choose |
|---|---|
| Cost basis, gains, or the tax center features | Transactions |
| Taxbit computes cost basis and proceeds for 1099-B or 1099-DA | Transactions |
| Filing and delivery of amounts your own systems already compute | Form data |
| Year-end reporting only, with no in-year features | Form data |
If you may want cost basis, gains, or the tax center later, start with transactions. Moving from form data later means loading your history as transactions first.
If both transactions and form data exist for an account and tax year, the form data is used on the form. Order doesn’t matter: form data sent before or after the related transactions overrides the computed amounts either way.
Where the sending happens
Sending transactions and form data is documented inside each product section, because the fields that matter differ by regime.
- US payments platforms: Send payment transactions in US Information Reporting.
- Digital asset exchanges and brokers: Send transactions and read gains in Cost Basis.
- EU, UK, and OECD digital platforms: Send seller income payments in MRDP & DAC7 Reporting.
- Form data: the Form Items reference.
The full transaction schema, including every type and subtype, is in the Transactions reference.
Updated 4 days ago