Transactions or form data
Send transactions and Taxbit calculates the form amounts, or send form data with the amounts you've already calculated. This page explains the difference and how to choose.
You can send data through the API, as these guides describe, or upload CSV and JSONL files on the Ingest page in the Taxbit Dashboard. Most historical data is backfilled with files. Either way, you send one of two kinds of reporting data.
You send transactions, and Taxbit calculates cost basis, gains, and form amounts from them. Or you send form data, sent as form items, which is the amounts your platform has already calculated. Taxbit puts those amounts on forms. You decide this per form type with your implementation manager in your Integration Planning Session, and it determines what you build for that form. Some forms allow only one of the two. MRDP and DAC7 reporting takes transactions only, and 1099-DIV takes form data only.
Send transactions
You send each transaction as it happens, in Taxbit's transaction data model. Each transaction has 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. If you send a transaction again with the same id, Taxbit updates it, so you can correct history by resending.
From transactions, Taxbit calculates cost basis at the lot level, realized and unrealized gains, income, and the amounts for each form. Sending transactions is the only way to use 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 calculate the form amounts yourself and send them per account and tax year, up to 100 form items per request. Taxbit validates them, puts them on the right forms, and files and delivers those forms. Taxbit doesn't calculate anything from activity, so there is no inventory, no gains, and no in-app tax center data.
Send form data if you have an existing tax engine, or data that doesn't fit a transaction model, and you need Taxbit for filing and delivery only.
How to decide
| If you need | Choose |
|---|---|
| Cost basis, gains, or the tax center features | Transactions |
| Taxbit to calculate cost basis and proceeds for 1099-B or 1099-DA | Transactions |
| Filing and delivery of amounts your own systems already calculate | Form data |
| Year-end reporting only, with no in-year features | Form data |
| A form that takes only one of the two (transactions for MRDP and DAC7, form data for 1099-DIV) | The one it takes |
If you might want cost basis, gains, or the tax center later, start with transactions. To move from form data later, you first have to load your history as transactions.
If both transactions and form data exist for an account and tax year, Taxbit uses the form data on the form. Order doesn't matter. Form data sent before or after the related transactions overrides the calculated amounts either way.
Where the sending happens
Each product section documents how to send transactions and form data, because the fields that matter differ by regulation.
- 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 1 day ago
